blob: 11757364db2b0e60deb5c6d2e11248057a6d6b48 [file] [log] [blame]
<!--
Copyright 2013 The Chromium Authors. All rights reserved.
Use of this source code is governed by a BSD-style license that can be
found in the LICENSE file.
-->
<!--
This file is used to generate a comprehensive list of Chrome histograms along
with a detailed description for each histogram.
Please pretty-print and validate your edits by running the pretty_print.py
and validate_format.py scripts in the same directory as this file before
uploading your change for review.
Take a moment to page through the contents of this file. You will find
three sections:
* The histograms section describes base histograms, giving their name,
and optionally their units or enum type, a short one-line summary,
and optionally a more detailed description.
* The enums section defines and documents the enumerated types referred to by
the histograms.
* The histogram_suffixes section provides a compact way of defining histograms
by applying affixes to existing histograms. This could be done recursively
and the max recursion depth is 5. See the example below for details on how it
works.
Each histogram_suffixes tag lists the histograms that it affects. The complete
list of histograms is computed by appending (or prepending - see below) the
histogram_suffixes suffix names to each of the affected histograms. For example,
define the following:
<histogram name="FileLoadLatency"/>
<histogram_suffixes name="SuperHttpExperiment">
<suffix name="SuperHttpEnabled"/>
<suffix name="SuperHttpDisabled"/>
<affected-histogram name="FileLoadLatency"/>
</histogram_suffixes>
The complete list of histograms will be:
FileLoadLatency
FileLoadLatency_SuperHttpEnabled
FileLoadLatency_SuperHttpDisabled
histogram_suffixes can also be used to insert affix in the middle. Example:
<histogram name="Prerender.Events"/>
<histogram_suffixes name="SuperHttpExperiment" ordering="prefix">
<suffix name="HoverStats50"/>
<affected-histogram name="Prerender.Events"/>
</histogram_suffixes>
The complete list of histograms will be:
Prerender.Events
Prerender.HoverStats50_Events
When 'ordering="prefix"' is present in the histogram_suffixes tag, the suffix
will be inserted after the first dot separator of the affected-histogram name.
Therefore, the affected-histogram name has to have at least one dot in it.
Googlers: There are also a small number of private internal histograms found at
http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
-->
<histogram-configuration>
<!-- Histogram definitions -->
<histograms>
<histogram name="Accessibility.CrosAlwaysShowA11yMenu" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the Chrome OS Accessibility Menu is set to be shown regardless of
the state of a11y features.(checked once 45 secs after startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosAutoclick" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<owner>tengs@chromium.org</owner>
<summary>
Whether the Chrome OS Autoclick feature is on (checked once 45 secs after
startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosAutoclickDelay" units="milliseconds">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<owner>tengs@chromium.org</owner>
<summary>
If the user has enabled Autoclick, this is the delay set by the user for
autoclicks to occur, in milliseconds.
</summary>
</histogram>
<histogram name="Accessibility.CrosHighContrast" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the Chrome OS High Contrast mode feature is on (checked once 45 secs
after startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosLargeCursor" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the Chrome OS Large Cursor feature is on (checked once 45 secs after
startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosScreenMagnifier" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the Chrome OS Screen Magnifier feature is on (checked once 45 secs
after startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosSpokenFeedback" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the Chrome OS Spoken Feedback feature is on (checked once 45 secs
after startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosStickyKeys" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<owner>tengs@chromium.org</owner>
<summary>
Whether the Chrome OS Sticky Keys feature is on (checked once 45 secs after
startup).
</summary>
</histogram>
<histogram name="Accessibility.CrosVirtualKeyboard" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the Chrome OS Virtual Keyboard feature is on (checked once 45 secs
after startup).
</summary>
</histogram>
<histogram name="Accessibility.InvertedColors" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether Windows system settings show that high-contrast mode is enabled and
the user has selected a light-on-dark color scheme (checked once 45 secs
after startup). This causes Chrome to prompt the user with a bubble to
optionally install a High Contrast extension and theme.
</summary>
</histogram>
<histogram name="Accessibility.ManuallyEnabled" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether Chrome has enabled accessibility support because the user passed the
--force-renderer-accessibility flag on the command-line (checked once 45
secs after startup).
</summary>
</histogram>
<histogram name="Accessibility.State" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether Chrome has enabled accessibility support because it detects
supported assistive technology running, or due to being manually enabled via
a command-line flag (checked once 45 secs after startup).
</summary>
</histogram>
<histogram name="Accessibility.WinAudioDescription" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether Windows system settings show that audio descriptions are enabled
(checked once 45 secs after startup).
</summary>
</histogram>
<histogram name="Accessibility.WinJAWS" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the third-party JAWS screen reader is running (checked once 45 secs
after startup).
</summary>
</histogram>
<histogram name="Accessibility.WinNVDA" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the third-party NVDA screen reader is running (checked once 45 secs
after startup).
</summary>
</histogram>
<histogram name="Accessibility.WinSAToGo" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the third-party System Access To Go screen reader is running
(checked once 45 secs after startup).
</summary>
</histogram>
<histogram name="Accessibility.WinScreenReader" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether Windows system settings show that a screen reader is running
(checked 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.
</summary>
</histogram>
<histogram name="Accessibility.WinStickyKeys" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether Windows system settings show that Sticky Keys are enabled.
</summary>
</histogram>
<histogram name="Accessibility.WinZoomText" enum="BooleanEnabled">
<owner>dmazzoni@chromium.org</owner>
<owner>kenjibaheux@google.com</owner>
<summary>
Whether the third-party ZoomText screen magnifier is running.
</summary>
</histogram>
<histogram name="Android.ArmFpu" enum="AndroidArmFpu">
<owner>fdegans@chromium.org</owner>
<summary>
Reports the FPU capabilities of the Android ARM device. This is recorded
once per browser session during startup.
</summary>
</histogram>
<histogram name="Android.IsLastSharedAppInfoRetrieved"
enum="BooleanIsLastSharedAppInfoRetrieved">
<owner>jaekyun@chromium.org</owner>
<summary>
Signifies whether the last shared app information is retrieved successfully
or not. This is logged when configuring the direct sharing menu item.
</summary>
</histogram>
<histogram name="Android.KernelVersion" enum="AndroidKernelVersion">
<owner>rsesek@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Android.ModerateBindingCount" units="bindings">
<owner>jaekyun@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Android.SeccompStatus.Prctl" enum="AndroidSeccompStatus">
<owner>rsesek@chromium.org</owner>
<summary>
Reports the level of kernel support for the seccomp-bpf sandbox using
prctl(PR_SET_SECCOMP).
</summary>
</histogram>
<histogram name="Android.SeccompStatus.RendererSandbox"
enum="AndroidSeccompSandboxStatus">
<owner>rsesek@chromium.org</owner>
<summary>
Reports the status of the seccomp-bpf sandbox in renderer processes.
Anything other than &quot;Sandbox Engaged&quot; indicates the sandbox is not
turned on. See https://crbug.com/477049.
</summary>
</histogram>
<histogram name="Android.SeccompStatus.Syscall" enum="AndroidSeccompStatus">
<owner>rsesek@chromium.org</owner>
<summary>
Reports the level of kernel support for the seccomp-bpf sandbox using the
seccomp system call.
</summary>
</histogram>
<histogram name="Android.StrictMode.OverrideUrlLoadingTime"
units="milliseconds">
<owner>yfriedman@chromium.org</owner>
<owner>wnwen@chromium.org</owner>
<summary>
Measures the amount of time due to a StrictMode violation from calling out
to Android activity manager.
</summary>
</histogram>
<histogram name="AndroidTabCloseUndo.Toast"
enum="AndroidTabCloseUndoToastEvent">
<owner>dtrainor@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AppBanners.DismissEvent" enum="AppBannersDismissEvent">
<owner>dfalcantara@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AppBanners.DisplayEvent" enum="AppBannersDisplayEvent">
<owner>dfalcantara@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AppBanners.InstallEvent" enum="AppBannersInstallEvent">
<owner>dfalcantara@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AppBanners.UserResponse" enum="AppBannersUserResponse">
<owner>dominickn@chromium.org</owner>
<summary>
App banners promote an application related to the current website, and are
requested specifically through the current page's HTML. This stat
specifically tracks a user's response to a displayed banner.
</summary>
</histogram>
<histogram name="appcache.CheckResponseResult"
enum="AppCacheCheckResponseResult">
<owner>michaeln@chromium.org</owner>
<summary>AppCache check response result code.</summary>
</histogram>
<histogram name="appcache.CompletionQueueTime" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>
Time elapsed between a completion task being queued and run.
</summary>
</histogram>
<histogram name="appcache.CompletionRunTime" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>
The amount of time taken to run a completion task on the IO thread.
</summary>
</histogram>
<histogram name="appcache.CorruptionDetected">
<owner>michaeln@chromium.org</owner>
<summary>
Tracks the number of times corruption is detected in the sql database.
</summary>
</histogram>
<histogram name="appcache.InitResult" enum="AppCacheInitResult">
<owner>michaeln@chromium.org</owner>
<summary>AppCache initialization result code.</summary>
</histogram>
<histogram name="appcache.JobStartDelay.AppCache" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>
How long URLRequests to be retrieved from the appcache are delayed.
</summary>
</histogram>
<histogram name="appcache.JobStartDelay.Error" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>
How long URLRequests that result in a synthesized error are delayed.
</summary>
</histogram>
<histogram name="appcache.JobStartDelay.Network" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>
How long URLRequests to be retrieved over the network are delayed.
</summary>
</histogram>
<histogram name="appcache.MainPageLoad" enum="BooleanSecure">
<owner>michaeln@chromium.org</owner>
<summary>
Counts the number of appcached page loads for secure vs insecure origins.
</summary>
</histogram>
<histogram name="appcache.MainResourceResponseRetrieval" enum="BooleanSuccess">
<owner>michaeln@chromium.org</owner>
<summary>
Tracks the success rate of retrieving a main resource from the appcache.
</summary>
</histogram>
<histogram name="appcache.MissingManifestDetectedAtCallsite"
enum="AppCacheErrorSite">
<owner>michaeln@chromium.org</owner>
<summary>Identifies where a missing manifest was detected occured.</summary>
</histogram>
<histogram name="appcache.MissingManifestEntry" enum="BooleanSuccess">
<owner>michaeln@chromium.org</owner>
<summary>
Logged on each occurrence of there being no record for the manifest file in
the entries table.
</summary>
</histogram>
<histogram name="appcache.ReinitAttempt">
<owner>michaeln@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="appcache.SubResourceResponseRetrieval" enum="BooleanSuccess">
<owner>michaeln@chromium.org</owner>
<summary>
Tracks the success rate of retrieving a sub resource from the appcache.
</summary>
</histogram>
<histogram name="appcache.TaskQueueTime" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>
Time elapsed between a background task being queued and run.
</summary>
</histogram>
<histogram name="appcache.TaskRunTime" units="milliseconds">
<owner>michaeln@chromium.org</owner>
<summary>The amount of time taken to run a background task.</summary>
</histogram>
<histogram name="appcache.UpdateJobResult" enum="AppCacheUpdateJobResult">
<owner>michaeln@chromium.org</owner>
<summary>AppCache update job result code.</summary>
</histogram>
<histogram name="appcache.UpdateProgressAtPointOfFaliure" units="percent">
<owner>michaeln@chromium.org</owner>
<summary>Percent completion at point of failure of an update job.</summary>
</histogram>
<histogram name="appcache.UpdateWasOffOriginAtPointOfFailure" enum="Boolean">
<owner>michaeln@chromium.org</owner>
<summary>
Whether the resource causing the failure was from a different origin.
</summary>
</histogram>
<histogram name="appcache.UpdateWasStalledAtPointOfFailure" enum="Boolean">
<owner>michaeln@chromium.org</owner>
<summary>
Whether any progresss had been made in the 5 minutes preceeding failure.
</summary>
</histogram>
<histogram name="AppleScript.CommandEvent" enum="AppleScriptCommandEvents">
<owner>spqchan@chromium.org</owner>
<summary>The number of times an AppleScript event gets called.</summary>
</histogram>
<histogram name="Apps.AppInfoDialog.Launches" enum="AppInfoDialogLaunchOrigin">
<owner>sashab@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Apps.AppInfoDialog.OpenedForLocation" enum="AppLocation">
<owner>sashab@chromium.org</owner>
<summary>
The location of the app that the dialog was opened for. This is gathered
each time the app info dialog is opened.
</summary>
</histogram>
<histogram name="Apps.AppInfoDialog.OpenedForType" enum="ExtensionType">
<owner>sashab@chromium.org</owner>
<summary>
The type of the app that the dialog was opened for. This is gathered each
time the app info dialog is opened.
</summary>
</histogram>
<histogram name="Apps.AppLaunch" enum="AppLaunch">
<owner>tapted@chromium.org</owner>
<owner>benwells@chromium.org</owner>
<summary>
The number of times v2 packaged apps are launched grouped by
extension_misc::AppLaunchBuckets. See also Extensions.AppLaunch.
</summary>
</histogram>
<histogram name="Apps.AppLauncherPromo" enum="AppLauncherPromo">
<owner>mad@chromium.org</owner>
<summary>Interactions with the App Launcher promo dialog.</summary>
</histogram>
<histogram name="Apps.AppListCreationTime" units="milliseconds">
<owner>calamity@chromium.org</owner>
<summary>
The amount of time it takes to build the app list UI. This is logged each
time the app list is built from scratch.
</summary>
</histogram>
<histogram name="Apps.AppListDoodleAction" enum="AppListDoodleAction">
<owner>calamity@chromium.org</owner>
<summary>
The number of user interactions with the app list doodle. This is logged
once per action.
</summary>
</histogram>
<histogram name="Apps.AppListHowEnabled" enum="AppListEnableSource">
<owner>tapted@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Apps.AppListPageOpened" enum="AppListPage">
<owner>calamity@chromium.org</owner>
<summary>
The page that the app list goes to. This is gathered every time the user
initiates a transition to another page in the launcher.
</summary>
</histogram>
<histogram name="Apps.AppListSearchCommenced" units="searches">
<owner>tapted@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Apps.AppListSearchQueryLength" units="characters">
<owner>calamity@chromium.org</owner>
<summary>
The length of the app list search query when a result is opened. This is
gathered per click of a search result.
</summary>
</histogram>
<histogram name="Apps.AppListSearchResultDistanceFromOrigin" units="keystrokes">
<owner>calamity@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Apps.AppListSearchResultOpenDisplayType"
enum="AppListSearchResultDisplayType">
<owner>calamity@chromium.org</owner>
<summary>
The display type of the app list search result that was opened by the user.
This is gathered per click of a search result.
</summary>
</histogram>
<histogram name="Apps.AppListSearchResultOpenType" enum="AppListSearchResult">
<owner>tapted@chromium.org</owner>
<summary>
The type of app list search result that was opened by the user. This is
gathered per click of a search result.
</summary>
</histogram>
<histogram name="Apps.AppListTimeToDiscover" units="milliseconds">
<owner>tapted@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Apps.AppListWarmupDuration" units="milliseconds">
<owner>tapted@chromium.org</owner>
<summary>
The amount of time spent in warmup (in WarmupForProfile call). This will
tell us how long warmup blocks the UI.
</summary>
</histogram>
<histogram name="Apps.AppShimErrorVersion">
<owner>jackhou@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Accelerators.Deprecated.LockScreen"
enum="DeprecatedAcceleratorUsage">
<owner>afakhry@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Accelerators.Deprecated.NextIME"
enum="DeprecatedAcceleratorUsage">
<owner>afakhry@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Accelerators.Deprecated.ShowTaskManager"
enum="DeprecatedAcceleratorUsage">
<owner>afakhry@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.ActiveTouchPoints">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>
Number of active touch-points when a new touch-point is added.
</summary>
</histogram>
<histogram name="Ash.ActiveWindowShowTypeOverTime" enum="ActiveWindowShowType">
<owner>kuscher@google.com</owner>
<summary>
The show type of the active window tracked over time by logging on a regular
basis (30 minutes).
</summary>
</histogram>
<histogram name="Ash.AppList.TimeBetweenTaskSwitches" units="seconds">
<owner>bruthig@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Desktop.TimeBetweenNavigateToTaskSwitches" units="seconds">
<owner>bruthig@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
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 ChromeOS 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'.
</summary>
</histogram>
<histogram name="Ash.Dock.Action" enum="DockedAction">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
User-initiated action taken that affects docked windows such as docking,
undocking, minimizing, restoring, closing or just dragging a docked window.
</summary>
</histogram>
<histogram name="Ash.Dock.ActionSource" enum="DockedActionSource">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
Source (mouse, touch, keyboard or unknown) of the user-initiated action for
docked windows.
</summary>
</histogram>
<histogram name="Ash.Dock.ItemsAll">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
Number of all docked windows or panels including hidden or minimized.
Recorded on every user action that interacts with docked windows.
</summary>
</histogram>
<histogram name="Ash.Dock.ItemsLarge">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Dock.ItemsPanels">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
Number of docked visible panels. Recorded on every user action that
interacts with docked windows.
</summary>
</histogram>
<histogram name="Ash.Dock.ItemsVisible">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
Number of visible docked windows or panels. Recorded on every user action
that interacts with docked windows.
</summary>
</histogram>
<histogram name="Ash.Dock.TimeBetweenUse" units="seconds">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
Time elapsed between instances of docking, undocking or any other action
affecting docked state of a window.
</summary>
</histogram>
<histogram name="Ash.Dock.Width" units="pixels">
<owner>kuscher@google.com</owner>
<owner>varkha@chromium.org</owner>
<summary>
Width of the docked area in pixels. Recorded every time it changes after a
user window resize operation is completed.
</summary>
</histogram>
<histogram name="Ash.GestureCreated" enum="UIEventType">
<obsolete>
Deprecated 08/2014 in Issue 352654, and replaced by Event.GestureCreated.
</obsolete>
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>
The gesture-events recognized and dispatched by the browser gesture
recognizer.
</summary>
</histogram>
<histogram name="Ash.GestureTarget" enum="GestureActionType">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>
The gesture-events recognized and dispatched by the browser gesture
recognizer for various UI components.
</summary>
</histogram>
<histogram name="Ash.ImmersiveFullscreen.WindowType" enum="WindowType">
<owner>kuscher@google.com</owner>
<summary>
The type of the window which is put into immersive fullscreen. Immersive
fullscreen is entered via the F4 key.
</summary>
</histogram>
<histogram name="Ash.NumberOfVisibleWindowsInPrimaryDisplay" units="Windows">
<owner>tdanderson@google.com</owner>
<owner>bruthig@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Shelf.Menu.NumItemsEnabledUponSelection" units="Count">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Shelf.Menu.SelectedMenuItemIndex" units="Index">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.Shelf.NumberOfItems" units="Icons">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
The number of icons in the shelf, not including the App Launcher icon. This
metric is recorded every 30 minutes.
</summary>
</histogram>
<histogram name="Ash.Shelf.NumberOfPinnedItems" units="Icons">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
The number of pinned icons in the shelf, not including the App Launcher
icon. This metric is recorded every 30 minutes.
</summary>
</histogram>
<histogram name="Ash.Shelf.NumberOfUnpinnedItems" units="Icons">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
The number of unpinned icons in the shelf. This metric is recorded every 30
minutes.
</summary>
</histogram>
<histogram name="Ash.Shelf.TimeBetweenNavigateToTaskSwitches" units="seconds">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
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'.
</summary>
</histogram>
<histogram name="Ash.Shelf.TimeBetweenWindowMinimizedAndActivatedActions"
units="milliseconds">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.ShelfAlignmentOverTime" enum="ShelfAlignmentValue">
<owner>kuscher@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.ShelfAlignmentUsage" enum="ShelfAlignmentValue">
<owner>kuscher@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.StationaryTouchDuration" units="seconds">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The duration of mostly stationary long-duration touches.</summary>
</histogram>
<histogram name="Ash.Tab.TimeBetweenSwitchToExistingTabUserActions"
units="seconds">
<owner>bruthig@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
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).
</summary>
</histogram>
<histogram name="Ash.TimeBetweenTaskSwitches" units="seconds">
<owner>bruthig@google.com</owner>
<owner>tdanderson@google.com</owner>
<summary>
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).
</summary>
</histogram>
<histogram name="Ash.TouchDuration" units="milliseconds">
<obsolete>
Deprecated 12/2013 in r239809, and replaced by Ash.TouchDuration2.
</obsolete>
<owner>kuscher@google.com</owner>
<summary>The duration of a touch-sequence.</summary>
</histogram>
<histogram name="Ash.TouchDuration2" units="milliseconds">
<obsolete>
Deprecated 08/2014 in Issue 352654, and replaced by Event.TouchDuration.
</obsolete>
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The duration of a touch-sequence.</summary>
</histogram>
<histogram name="Ash.TouchMaxDistance" units="pixels">
<obsolete>
Deprecated 08/2014 in Issue 352654, and replaced by Event.TouchMaxDistance.
</obsolete>
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>
The maximum euclidean distance in dips which a touch point has travelled
away from its starting point. Only measured for single finger gestures.
</summary>
</histogram>
<histogram name="Ash.TouchMoveInterval" units="milliseconds">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The interval between touch-move events.</summary>
</histogram>
<histogram name="Ash.TouchMoveSteps" units="pixels">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The distance between touch-move events.</summary>
</histogram>
<histogram name="Ash.TouchPositionX" units="pixels">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The position of the touch-events along the X axis.</summary>
</histogram>
<histogram name="Ash.TouchPositionY" units="pixels">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The position of the touch-events along the Y axis.</summary>
</histogram>
<histogram name="Ash.TouchRadius" units="pixels">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>The radius of a touch event.</summary>
</histogram>
<histogram name="Ash.TouchStartAfterEnd" units="milliseconds">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>
The interval between the end of a touch-sequence and the start of the next
touch-sequence.
</summary>
</histogram>
<histogram name="Ash.TouchStartBurst">
<owner>kuscher@google.com</owner>
<owner>rbyers@chromium.org</owner>
<summary>
The number of rapid touch-starts that happened within a short interval.
Logged once for each such burst group.
</summary>
</histogram>
<histogram name="Ash.TouchView.TouchViewActive" units="milliseconds">
<owner>girard@chromium.org</owner>
<summary>
The length of time that TouchView is active, for each activation.
</summary>
</histogram>
<histogram name="Ash.TouchView.TouchViewActivePercentage" units="%">
<owner>girard@chromium.org</owner>
<summary>The proportion of time spent in TouchView during a session.</summary>
</histogram>
<histogram name="Ash.TouchView.TouchViewActiveTotal" units="seconds">
<owner>girard@chromium.org</owner>
<summary>The total time that TouchView is active during a session.</summary>
</histogram>
<histogram name="Ash.TouchView.TouchViewInactive" units="milliseconds">
<owner>girard@chromium.org</owner>
<summary>The length of time between TouchView activations.</summary>
</histogram>
<histogram name="Ash.TouchView.TouchViewInactiveTotal" units="seconds">
<owner>girard@chromium.org</owner>
<summary>
The total time that TouchView is not active during a session.
</summary>
</histogram>
<histogram name="Ash.Wallpaper.CustomLayout" enum="WallpaperLayout">
<owner>xdai@chromium.org</owner>
<summary>
The custom wallpaper layout type. Recorded when the user sets a new custom
wallpaper or changes the existing custom wallpaper's layout.
</summary>
</histogram>
<histogram name="Ash.Wallpaper.DefaultIndex">
<obsolete>
Deprecated as of 11/2012. Use of indices has been removed.
</obsolete>
<owner>kuscher@google.com</owner>
<summary>
The wallpaper index if one of the default wallpapers has been selected.
Recorded at user login. Currently only for the old wallpaper picker UI.
</summary>
</histogram>
<histogram name="Ash.Wallpaper.Type" enum="WallpaperType">
<owner>kuscher@google.com</owner>
<summary>The wallpaper type. Recorded at user login.</summary>
</histogram>
<histogram name="Ash.WindowCycleController.CycleTime" units="milliseconds">
<owner>flackr@chromium.org</owner>
<owner>kuscher@google.com</owner>
<summary>
The amount of time the Alt key is held after pressing Alt+Tab to begin
cycling through windows.
</summary>
</histogram>
<histogram name="Ash.WindowCycleController.TimeBetweenTaskSwitches"
units="seconds">
<owner>tdanderson@google.com</owner>
<owner>bruthig@google.com</owner>
<summary>
The number of seconds between task switches triggered by the next window and
previous window accelerator keys (ie Alt+Tab, Alt+Shift+Tab).
</summary>
</histogram>
<histogram name="Ash.WindowManager.Lock.Success" units="milliseconds">
<owner>jdufault@chromium.org</owner>
<summary>
How long it took for the screen lock process to complete. This does not
include timeouts.
</summary>
</histogram>
<histogram name="Ash.WindowManager.Lock.Timeout" units="milliseconds">
<owner>jdufault@chromium.org</owner>
<summary>
How long it took for the screen lock process to complete, for timeouts only.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.ArrowKeyPresses">
<owner>flackr@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.CycleTime" units="milliseconds">
<obsolete>
Deprecated as of 06/2014. No longer relevant since alt-tab switching was
separated from WindowSelector.
</obsolete>
<owner>flackr@chromium.org</owner>
<owner>kuscher@google.com</owner>
<summary>
The amount of time the Alt key is held after pressing Alt+Tab to begin
cycling through windows.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.Items">
<owner>flackr@chromium.org</owner>
<owner>kuscher@google.com</owner>
<summary>
The number of items (single windows or groups of windows such as panels) in
the overview mode, present at the start of each session.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.ItemsWhenTextFilteringUsed" units="items">
<owner>tdanderson@chromium.org</owner>
<owner>flackr@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.KeyPressesOverItemsRatio" units="%">
<owner>flackr@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
The ratio between the arrow key presses and the number of overview items,
expressed as a percentage for a single session.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.OverviewClosedItems">
<owner>flackr@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
The number of items closed from the window overview for a single session.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.TextFilteringStringLength"
units="characters">
<owner>tdanderson@chromium.org</owner>
<owner>flackr@chromium.org</owner>
<summary>
The length of the string entered into the text filtering textfield at the
moment when an item is selected or when selection is canceled.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.TextFilteringTextfieldCleared">
<owner>tdanderson@chromium.org</owner>
<owner>flackr@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.TimeBetweenActiveWindowChanges"
units="seconds">
<owner>bruthig@chromium.org</owner>
<owner>tdanderson@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.TimeBetweenUse" units="milliseconds">
<owner>flackr@chromium.org</owner>
<owner>kuscher@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.TimeInOverview" units="milliseconds">
<owner>flackr@chromium.org</owner>
<owner>kuscher@google.com</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Ash.WindowSelector.TimeInOverviewWithTextFiltering"
units="milliseconds">
<owner>tdanderson@chromium.org</owner>
<owner>flackr@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.AttemptCountFail">
<owner>ttuttle@chromium.org</owner>
<summary>
Count of DnsAttempts before DnsTransaction completes with failure.
</summary>
</histogram>
<histogram name="AsyncDNS.AttemptCountSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
Count of DnsAttempts before DnsTransaction completes successfully.
</summary>
</histogram>
<histogram name="AsyncDNS.ConfigChange" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
Whether DnsConfigService::OnConfigChange actually corresponded to a change
in DnsConfig.
</summary>
</histogram>
<histogram name="AsyncDNS.ConfigNotifyInterval" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time between calls to DnsConfigService::InvalidateConfig.
</summary>
</histogram>
<histogram name="AsyncDNS.ConfigParseDuration" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>Duration of time spent parsing DnsConfig.</summary>
</histogram>
<histogram name="AsyncDNS.ConfigParsePosix" enum="AsyncDNSConfigParsePosix">
<owner>ttuttle@chromium.org</owner>
<summary>
Counts of results of parsing DnsConfig in DnsConfigServicePosix.
</summary>
</histogram>
<histogram name="AsyncDNS.ConfigParseResult" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>Whether DnsConfig was parsed successfully.</summary>
</histogram>
<histogram name="AsyncDNS.ConfigParseWin" enum="AsyncDNSConfigParseWin">
<owner>ttuttle@chromium.org</owner>
<summary>
Counts of results of parsing DnsConfig in DnsConfigServiceWin.
</summary>
</histogram>
<histogram name="AsyncDNS.DNSChangerDetected" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
Whether the first valid DnsConfig included a rogue nameserver.
</summary>
</histogram>
<histogram name="AsyncDNS.DnsClientDisabledReason" enum="NetErrorCodes">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.DnsClientEnabled" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.FallbackFail" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time spent by ProcTask in failing fallback resolutions.
</summary>
</histogram>
<histogram name="AsyncDNS.FallbackSuccess" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time spent by ProcTask in successful fallback resolutions.
</summary>
</histogram>
<histogram name="AsyncDNS.HaveDnsConfig" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
Whether there was a valid DNS configuration at the start of a job which
eventually completed successfully.
</summary>
</histogram>
<histogram name="AsyncDNS.HostParseResult" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>Whether DnsHosts were parsed successfully.</summary>
</histogram>
<histogram name="AsyncDNS.HostsChange" enum="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
Whether DnsConfigService::OnHostsChange actually corresponded to a change in
DnsHosts.
</summary>
</histogram>
<histogram name="AsyncDNS.HostsNotifyInterval" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time between calls to DnsConfigService::InvalidateHosts.
</summary>
</histogram>
<histogram name="AsyncDNS.HostsParseDuration" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>Duration of time spent parsing DnsHosts.</summary>
</histogram>
<histogram name="AsyncDNS.HostsParseWin" enum="AsyncDNSHostsParseWin">
<owner>ttuttle@chromium.org</owner>
<summary>
Counts of results of parsing DnsHosts in DnsConfigServiceWin.
</summary>
</histogram>
<histogram name="AsyncDNS.HostsSize" units="bytes">
<owner>ttuttle@chromium.org</owner>
<summary>
The size of the HOSTS file observed before each attempt to parse it.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTime" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient).
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTime_HIGHEST" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTime_IDLE" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTime_LOW" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTime_LOWEST" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTime_MEDIUM" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTimeAfterChange" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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).
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTimeAfterChange_HIGHEST" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTimeAfterChange_IDLE" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTimeAfterChange_LOW" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTimeAfterChange_LOWEST" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.JobQueueTimeAfterChange_MEDIUM" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.NameServersType" enum="AsyncDNSNameServersType">
<owner>ttuttle@chromium.org</owner>
<summary>
Type of nameservers in the DNS config, recorded each time the config is read
by the DNSConfigService.
</summary>
</histogram>
<histogram name="AsyncDNS.ParseToAddressList" enum="AsyncDNSParseResult">
<owner>ttuttle@chromium.org</owner>
<summary>
Counts of results of parsing addresses out of DNS responses in successful
DnsTransactions.
</summary>
</histogram>
<histogram name="AsyncDNS.PrefDefaultSource" enum="AsyncDNSPrefDefaultSource">
<owner>ttuttle@chromium.org</owner>
<summary>
The source of the async DNS preference's default. Logged at startup, when
the IO thread is created.
</summary>
</histogram>
<histogram name="AsyncDNS.PrefSource" enum="AsyncDNSPrefSource">
<owner>ttuttle@chromium.org</owner>
<summary>
The source of the async DNS preference's value. Logged at startup, when the
IO thread is created.
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveError" enum="NetErrorCodes">
<owner>ttuttle@chromium.org</owner>
<summary>
Counts of specific error codes returned by DnsTask if a subsequent ProcTask
succeeded.
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveFail" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken by DnsTask in resolutions that failed. Excludes time
spent in the subsequent fallback.
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveStatus" enum="AsyncDNSResolveStatus">
<owner>ttuttle@chromium.org</owner>
<summary>
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).
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveSuccess" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken by DnsTask in resolutions that succeeded.
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveSuccess_FAMILY_IPV4" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Same as AsyncDNS.ResolveSuccess, but limited to pure IPv4 lookups.
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveSuccess_FAMILY_IPV6" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Same as AsyncDNS.ResolveSuccess, but limited to pure IPv6 lookups.
</summary>
</histogram>
<histogram name="AsyncDNS.ResolveSuccess_FAMILY_UNSPEC" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Same as AsyncDNS.ResolveSuccess, but limited to IPv4/IPv6 lookups.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerCount">
<owner>ttuttle@chromium.org</owner>
<summary>
Count of servers in DnsConfig. Recorded on every new DnsSession, which is
created on DNS change.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerFailureIndex">
<owner>ttuttle@chromium.org</owner>
<summary>
Index in DnsConfig of the failing server, recorded at the time of failure.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerFailuresAfterNetworkChange">
<owner>ttuttle@chromium.org</owner>
<summary>
Count of server failures after network change before first success in the
DnsSession. Recorded at the time of first success.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerFailuresAfterSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerFailuresBeforeSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
Count of server failures before success. This is NOT the first success in
the DnsSession. Recorded at the time of success.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerFailuresWithoutSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.ServerIsGood" units="BooleanSuccess">
<owner>ttuttle@chromium.org</owner>
<summary>
The current server is &quot;good&quot; and does not have to be skipped.
</summary>
</histogram>
<histogram name="AsyncDNS.SortFailure" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken in failing calls to AddressSorter in dual-stack
resolutions using DnsTask.
</summary>
</histogram>
<histogram name="AsyncDNS.SortSuccess" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken in successful calls to AddressSorter in dual-stack
resolutions using DnsTask.
</summary>
</histogram>
<histogram name="AsyncDNS.SuffixSearchDone">
<owner>ttuttle@chromium.org</owner>
<summary>
The number of names from the search name list consumed during a successful
transaction (QTYPE A only).
</summary>
</histogram>
<histogram name="AsyncDNS.SuffixSearchRemain">
<owner>ttuttle@chromium.org</owner>
<summary>
The number of names left on the search name list at the end of a successful
transaction (QTYPE A only).
</summary>
</histogram>
<histogram name="AsyncDNS.SuffixSearchStart">
<owner>ttuttle@chromium.org</owner>
<summary>
The number of names on the search name list at the start of a transaction
(QTYPE A only).
</summary>
</histogram>
<histogram name="AsyncDNS.TCPAttemptFail" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken by DnsTCPAttempt in failed attempts. Excludes
timeouts.
</summary>
</histogram>
<histogram name="AsyncDNS.TCPAttemptSuccess" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken by DnsTCPAttempt in successful attempts.
</summary>
</histogram>
<histogram name="AsyncDNS.TimeoutErrorHistogram" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Difference between RTT and timeout calculated using Histogram algorithm.
</summary>
</histogram>
<histogram name="AsyncDNS.TimeoutErrorHistogramUnder" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Difference between timeout calculated using Histogram algorithm and RTT.
</summary>
</histogram>
<histogram name="AsyncDNS.TimeoutErrorJacobson" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Difference between RTT and timeout calculated using Jacobson algorithm.
</summary>
</histogram>
<histogram name="AsyncDNS.TimeoutErrorJacobsonUnder" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Difference between timeout calculated using Jacobson algorithm and RTT.
</summary>
</histogram>
<histogram name="AsyncDNS.TimeoutSpentHistogram" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time that would be spent waiting for lost request using
Histogram algorithm.
</summary>
</histogram>
<histogram name="AsyncDNS.TimeoutSpentJacobson" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time that would be spent waiting for lost request using Jacobson
algorithm.
</summary>
</histogram>
<histogram name="AsyncDNS.TotalTime" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.TotalTime_speculative" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.TransactionFailure" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken in failing DnsTransactions. This includes server
failures, timeouts and NXDOMAIN results.
</summary>
</histogram>
<histogram name="AsyncDNS.TransactionSuccess" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.TransactionSuccess_A" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Same as AsyncDNS.TransactionSuccess but limited to A query type.
</summary>
</histogram>
<histogram name="AsyncDNS.TransactionSuccess_AAAA" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Same as AsyncDNS.TransactionSuccess but limited to AAAA query type.
</summary>
</histogram>
<histogram name="AsyncDNS.TTL" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AsyncDNS.UDPAttemptFail" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken by DnsUDPAttempt in failed attempts. Excludes
timeouts.
</summary>
</histogram>
<histogram name="AsyncDNS.UDPAttemptSuccess" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time taken by DnsUDPAttempt in successful attempts. Includes
responses arriving after timeout, if multiple attempts are allowed.
</summary>
</histogram>
<histogram name="AsyncDNS.UnchangedConfigInterval" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time since the last empty config result to the time a non-change
OnConfigChange is received.
</summary>
</histogram>
<histogram name="AsyncDNS.UnchangedHostsInterval" units="milliseconds">
<owner>ttuttle@chromium.org</owner>
<summary>
Duration of time since the last empty config result to the time a non-change
OnHostsChange is received.
</summary>
</histogram>
<histogram name="AsyncDNS.WatchStatus" enum="AsyncDNSWatchStatus">
<owner>ttuttle@chromium.org</owner>
<summary>
The result of DnsConfigService watch. Counts STARTED on every initialization
and FAILED_* on any failure.
</summary>
</histogram>
<histogram name="Aura.CreatedGpuBrowserCompositor" enum="CompositorType">
<owner>jbauman@chromium.org</owner>
<summary>
Whether the browser compositor uses GPU or the software renderer.
</summary>
</histogram>
<histogram name="Autocheckout.Bubble" enum="AutocheckoutBubble">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the frequency of user interactions with the Autocheckout bubble,
which prompts users to invoke Autocheckout on supported websites.
</summary>
</histogram>
<histogram name="Autocheckout.BuyFlow" enum="AutocheckoutBuyFlow">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the frequency of final states reached in Autocheckout buy flow.
</summary>
</histogram>
<histogram name="Autocheckout.DismissalState"
enum="AutofillDialogDismissalState">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>The state of the Autocheckout dialog when it was dismissed.</summary>
</histogram>
<histogram name="Autocheckout.FlowDuration" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the time elapsed between when the user submitted the Autocheckout
dialog and when the Autocheckout flow, or filling process, concluded.
</summary>
</histogram>
<histogram name="Autocheckout.FlowDuration.Failed" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the time elapsed between when the user submitted the Autocheckout
dialog and when the Autocheckout flow concluded, in cases where the flow
failed.
</summary>
</histogram>
<histogram name="Autocheckout.FlowDuration.Succeeded" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the time elapsed between when the user submitted the Autocheckout
dialog and when the Autocheckout flow concluded, in cases where the flow
succeeded.
</summary>
</histogram>
<histogram name="Autocheckout.InitialUserState"
enum="AutofillDialogInitialUserState">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
The initial state of a user that's interacting with a freshly shown
Autocheckout dialog.
</summary>
</histogram>
<histogram name="Autocheckout.PopupInDialog" enum="AutofillDialogPopupEvent">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
User interactions with the Autofill popup shown while filling an
Autocheckout dialog.
</summary>
</histogram>
<histogram name="Autocheckout.Security" enum="AutofillDialogSecurity">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the frequency of security warnings and errors in the Autocheckout
dialog.
</summary>
</histogram>
<histogram name="Autocheckout.UiDuration" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the duration for which an Autocheckout dialog was shown.
</summary>
</histogram>
<histogram name="Autocheckout.UiDuration.Cancel" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the duration for which an Autocheckout dialog was shown, in cases
where the user ended up canceling out of the dialog.
</summary>
</histogram>
<histogram name="Autocheckout.UiDuration.Submit" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the duration for which an Autocheckout dialog was shown, in cases
where the user ended up accepting the dialog.
</summary>
</histogram>
<histogram name="Autocheckout.UiEvents" enum="AutofillDialogUiEvents">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures how users are interacting with the Autocheckout dialog UI.
</summary>
</histogram>
<histogram name="Autocheckout.UiLatencyToShow" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the duration of time it takes for the Autocheckout UI to be
actionable by the user after it is shown.
</summary>
</histogram>
<histogram name="Autocheckout.WalletErrors" enum="WalletErrors">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the frequency of errors in communicating with the Google Online
Wallet server.
</summary>
</histogram>
<histogram name="Autocheckout.WalletRequiredActions"
enum="WalletRequiredActions">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures the frequency of required user actions returned by the Google
Online Wallet server.
</summary>
</histogram>
<histogram name="Autocheckout.WhitelistDownloadDuration" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures time taken to download the Autocheckout whitelist file.
</summary>
</histogram>
<histogram name="Autocheckout.WhitelistDownloadDuration.Failed" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures time taken to download the Autocheckout whitelist file in case the
download was failed.
</summary>
</histogram>
<histogram name="Autocheckout.WhitelistDownloadDuration.Succeeded" units="ms">
<obsolete>
Deprecated as of 8/2013.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>
Measures time taken to download the Autocheckout whitelist file in case the
download was succeeded.
</summary>
</histogram>
<histogram name="AutodetectEncoding.Attempted" enum="BooleanAttempted">
<owner>jinsukkim@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AutodetectEncoding.Detected" enum="EncodingMethod"
units="pages">
<owner>jinsukkim@chromium.org</owner>
<summary>
The number of web pages whose encoding method is found by the auto detection
logic. Grouped by the encoding methods defined in EncodingMethod.
</summary>
</histogram>
<histogram name="Autofill.AddressBook.AccessSkipped" enum="BooleanSkipped">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.AddressBookAvailable" enum="BooleanAvailable">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>isherman@chromium.org</owner>
<summary>
Whether the Mac AddressBook was available on an attempt to read data from
it.
</summary>
</histogram>
<histogram name="Autofill.AddressBookAvailableOnFirstAttempt"
enum="BooleanAvailable">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>isherman@chromium.org</owner>
<summary>
Whether the Mac AddressBook was available on the *first* attempt to read
data from it. This is only recorded once per Chrome profile.
</summary>
</histogram>
<histogram name="Autofill.AddressSuggestionsCount">
<owner>isherman@chromium.org</owner>
<summary>
The number of address suggestions shown in the Autofill popup.
</summary>
</histogram>
<histogram name="Autofill.AutomaticProfileCreation" enum="BooleanCreated">
<obsolete>
Deprecated as of 6/2015, replaced by Autofill.ProfileActionOnFormSubmitted.
</obsolete>
<owner>sebsg@chromium.org</owner>
<summary>
Whether a new Autofill profile was created automatically. In the
&quot;false&quot; case, an existing profile was used (and possibly updated).
</summary>
</histogram>
<histogram name="Autofill.CardUploadDecision" enum="AutofillCardUploadDecision">
<owner>jdonnelly@chromium.org</owner>
<summary>
Whether upload was offered upon detecting a form submission with credit card
data and a reason if it wasn't.
</summary>
</histogram>
<histogram name="AutoFill.CCInfoBarAccepted">
<obsolete>
Deprecated as of 3/2011, replaced by Autofill.CreditCardInfoBar.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>The Autofill credit card info bar was accepted.</summary>
</histogram>
<histogram name="AutoFill.CCInfoBarDenied">
<obsolete>
Deprecated as of 3/2011, replaced by Autofill.CreditCardInfoBar.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>The Autofill credit card info bar was denied.</summary>
</histogram>
<histogram name="Autofill.CreditCardInfoBar" enum="AutofillCreditCardInfoBar">
<owner>isherman@chromium.org</owner>
<summary>
The relative frequency with which users accept, deny, or ignore the Autofill
credit card info bar prompt.
</summary>
</histogram>
<histogram name="Autofill.DaysSinceLastUse.CreditCard" units="days">
<owner>sebsg@chromium.org</owner>
<summary>
Logs the number of days that have passed since the credit card was last
used.
</summary>
</histogram>
<histogram name="Autofill.DaysSinceLastUse.Profile" units="days">
<owner>sebsg@chromium.org</owner>
<summary>
Logs the number of days that have passed since the profile was last used.
</summary>
</histogram>
<histogram name="Autofill.DeveloperEngagement"
enum="AutofillDeveloperEngagement">
<owner>isherman@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.FillDuration.FromInteraction.WithAutofill">
<owner>isherman@chromium.org</owner>
<summary>
Time elapsed between the user's first interaction with a form and the form's
submission, for an autofilled form.
</summary>
</histogram>
<histogram name="Autofill.FillDuration.FromInteraction.WithoutAutofill">
<owner>isherman@chromium.org</owner>
<summary>
Time elapsed between the user's first interaction with a form and the form's
submission, for a non-autofilled form.
</summary>
</histogram>
<histogram name="Autofill.FillDuration.FromLoad.WithAutofill">
<owner>isherman@chromium.org</owner>
<summary>
Time elapsed between form load and form submission, for an autofilled form.
</summary>
</histogram>
<histogram name="Autofill.FillDuration.FromLoad.WithoutAutofill">
<owner>isherman@chromium.org</owner>
<summary>
Time elapsed between form load and form submission, for a non-autofilled
form.
</summary>
</histogram>
<histogram name="Autofill.FormEvents.Address" enum="AutofillFormEvent">
<owner>waltercacau@chromium.org</owner>
<summary>
Autofill form events for address forms. These are recorded when the user
interacts with a form requesting an address.
</summary>
<details>
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 &quot;Submitted
with server suggestion filled (once)&quot;; - The submission segmentation
works by checking what kind of data was last filled for this type of form in
the page load. So, if I user initially filled with local data and after that
filled with server, we will only emit &quot;Submitted with server suggestion
filled (once)&quot;.
</details>
</histogram>
<histogram name="Autofill.FormEvents.CreditCard" enum="AutofillFormEvent">
<owner>waltercacau@chromium.org</owner>
<summary>
Autofill form events for credit card forms. These are recorded when the user
interacts with a form requesting a credit card.
</summary>
<details>
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 &quot;Submitted
with server suggestion filled (once)&quot;; - The submission segmentation
works by checking what kind of data was last filled for this type of form in
the page load. So, if I user initially filled with local data and after that
filled with server, we will only emit &quot;Submitted with server suggestion
filled (once)&quot;.
</details>
</histogram>
<histogram name="Autofill.FormSubmittedState" enum="AutofillFormSubmittedState">
<owner>sebsg@chromium.org</owner>
<summary>The autofill state related to a submitted form.</summary>
</histogram>
<histogram name="Autofill.IcuCollatorCreationSuccess" enum="BooleanSuccess">
<owner>mathp@chromium.org</owner>
<summary>
Tracks whether Autofill was able to create the ICU collator successfully.
</summary>
</histogram>
<histogram name="Autofill.IsEnabled.PageLoad" enum="BooleanEnabled">
<owner>isherman@chromium.org</owner>
<summary>
Tracks whether Autofill is enabled on page load for a page containing forms.
</summary>
</histogram>
<histogram name="Autofill.IsEnabled.Startup" enum="BooleanEnabled">
<owner>isherman@chromium.org</owner>
<summary>Tracks whether Autofill is enabled when Chrome launches.</summary>
</histogram>
<histogram name="Autofill.KeyboardAccessoryButtonsIOS"
enum="AutofillKeyboardAccessoryButtonsIOS">
<owner>bondd@chromium.org</owner>
<summary>
[iOS] Measures the frequency of button presses on the iOS Autofill keyboard
accessory.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook" enum="AutofillMacAddressBook">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.AcceptedSuggestionIsFromAddressBook"
enum="BooleanFromAddressBook">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
This metric is emitted each time the user accepts an Autofill suggestion. It
records whether the result is from the Address Book.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.AccessTime" units="ms">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.ContainedMeCard"
enum="BooleanContainedMeCard">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
After a Chrome is given access to the Mac Address Book, whether the Address
Book contained a Me card.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.MeCard.HadAddress"
enum="BooleanHadAddress">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.MeCard.HadEmail"
enum="BooleanHadEmail">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
When Chrome is given access to the Me Card of the Address Book, whether the
card has an email.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.MeCard.HadName" enum="BooleanHadName">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
When Chrome is given access to the Me Card of the Address Book, whether the
card has a name.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.MeCard.HadPhoneNumber"
enum="BooleanHadPhoneNumber">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
When Chrome is given access to the Me Card of the Address Book, whether the
card has a phone number.
</summary>
</histogram>
<histogram name="Autofill.MacAddressBook.NumShowsBeforeSelected">
<obsolete>
Deprecated as of 8/2015.
</obsolete>
<owner>erikchen@chromium.org</owner>
<summary>
The number of times that the access Address Book prompt has been shown when
the user selects the prompt.
</summary>
</histogram>
<histogram name="Autofill.NumberOfEditedAutofilledFieldsAtSubmission"
units="fields">
<owner>mathp@chromium.org</owner>
<summary>
The number of autofilled fields that were subsequently edited prior to the
form being submitted.
</summary>
</histogram>
<histogram name="Autofill.PasswordFormQueryVolume"
enum="PasswordFormQueryVolume">
<owner>dvadym@chromium.org</owner>
<owner>gcasto@chromium.org</owner>
<obsolete>
Deprecated 10/2015.
</obsolete>
<summary>
Tracks the increased load on the Autofill server if the restriction on
querying for password forms with fewer than 3 fields were omitted.
</summary>
</histogram>
<histogram name="Autofill.PayloadCompressionRatio" units="%">
<owner>mathp@chromium.org</owner>
<summary>
Compression ratio of the query and upload payload that are sent to the
Autofill server. The payload is compressed using gzip.
</summary>
</histogram>
<histogram name="Autofill.ProfileActionOnFormSubmitted"
enum="AutofillProfileAction">
<owner>sebsg@chromium.org</owner>
<summary>
The profile action that took place when a form was submitted.
</summary>
</histogram>
<histogram name="AutoFill.ProfileCount">
<obsolete>
Deprecated as of 3/2011, replaced by Autofill.StoredProfileCount.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>The number of Autofill address profiles a user has.</summary>
</histogram>
<histogram name="AutoFill.Quality" enum="AutofillQuality">
<obsolete>
Deprecated as of 3/2011, replaced by Autofill.Quality.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>The quality of the AutoFill implementation.</summary>
</histogram>
<histogram name="Autofill.Quality" enum="AutofillQuality">
<obsolete>
Deprecated as of 2/2014 (M35), replaced by Autofill.UserHappiness.
</obsolete>
<owner>isherman@chromium.org</owner>
<summary>The quality of the Autofill implementation.</summary>
</histogram>
<histogram name="Autofill.Quality.HeuristicType" enum="AutofillTypeQuality">
<owner>isherman@chromium.org</owner>
<summary>The quality of Autofill's heuristic field type detection.</summary>
</histogram>
<histogram name="Autofill.Quality.HeuristicType.ByFieldType"
enum="AutofillTypeQualityByFieldType">
<owner>isherman@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.Quality.PredictedType" enum="AutofillTypeQuality">
<owner>isherman@chromium.org</owner>
<summary>The overall quality of the Autofill field type predictions.</summary>
</histogram>
<histogram name="Autofill.Quality.PredictedType.ByFieldType"
enum="AutofillTypeQualityByFieldType">
<owner>isherman@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.Quality.ServerType" enum="AutofillTypeQuality">
<owner>isherman@chromium.org</owner>
<summary>The quality of the Autofill server's field type detection.</summary>
</histogram>
<histogram name="Autofill.Quality.ServerType.ByFieldType"
enum="AutofillTypeQualityByFieldType">
<owner>isherman@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="AutoFill.RequestErrorimcklfaapmppdhilegjoahjbahdgfhcn">
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>TBD.</summary>
</histogram>
<histogram name="AutoFill.RequestSuccessimcklfaapmppdhilegjoahjbahdgfhcn">
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>TBD.</summary>
</histogram>
<histogram name="Autofill.SaveCreditCardPrompt"
enum="AutofillSaveCreditCardPrompt">
<owner>jdonnelly@chromium.org</owner>
<summary>
The relative frequency with which users accept or deny the Autofill save
credit card prompt.
</summary>
</histogram>
<histogram name="Autofill.ScanCreditCard.Completed" enum="BooleanCompleted">
<owner>rouslan@chromium.org</owner>
<summary>Whether a credit card scan was completed or cancelled.</summary>
</histogram>
<histogram name="Autofill.ScanCreditCard.Duration" units="ms">
<owner>rouslan@chromium.org</owner>
<summary>How long a credit card took to scan.</summary>
</histogram>
<histogram name="Autofill.ScanCreditCardPrompt"
enum="AutofillScanCreditCardPrompt">
<owner>estade@chromium.org</owner>
<summary>Usage of the &quot;Scan card&quot; control item.</summary>
</histogram>
<histogram name="Autofill.ServerExperimentId" enum="AutofillExperimentId">
<obsolete>
Deprecated as of 6/2011, replaced by Autofill.ServerExperimentId.Query.
</obsolete>
<owner>isherman@chromium.org</owner>
<summary>
The experiment ID received in response to an Autofill server query.
</summary>
</histogram>
<histogram name="Autofill.ServerExperimentId.Query" enum="AutofillExperimentId">
<obsolete>
Deprecated as of 2/2014 (M35).
</obsolete>
<owner>isherman@chromium.org</owner>
<summary>
The experiment ID received in response to an Autofill server query.
</summary>
</histogram>
<histogram name="Autofill.ServerExperimentId.Upload"
enum="AutofillExperimentId">
<obsolete>
Deprecated as of 2/2014 (M35).
</obsolete>
<owner>isherman@chromium.org</owner>
<summary>
The experiment ID received at the time of an Autofill upload.
</summary>
</histogram>
<histogram name="AutoFill.ServerQueryResponse" enum="AutofillQueryResult">
<obsolete>
Deprecated as of 3/2011, replaced by Autofill.ServerQueryResponse.
</obsolete>
<owner>Please list the metric's owners. Add more owner tags as needed.</owner>
<summary>The usefulness of AutoFill server information.</summary>
</histogram>
<histogram name="Autofill.ServerQueryResponse" enum="AutofillQueryResult">
<owner>isherman@chromium.org</owner>
<summary>The usefulness of Autofill server information.</summary>
</histogram>
<histogram name="Autofill.ServerResponseHasDataForForm"
enum="BooleanHadPredictions">
<owner>mathp@chromium.org</owner>
<summary>
Tracks whether Autofill server had at least some prediction data for a given
form at query response time.
</summary>
</histogram>
<histogram name="Autofill.StoredProfileCount">
<owner>isherman@chromium.org</owner>
<summary>
The number of Autofill addresses a user has stored, measured at launch time.
</summary>
</histogram>
<histogram name="Autofill.StoredProfileCountAtAutofillableFormSubmission">
<owner>mathp@chromium.org</owner>
<summary>
The number of Autofill addresses a user has stored, measured when an
autofillable form is submitted.
</summary>
</histogram>
<histogram name="Autofill.SuggestionAcceptedIndex" units="position">
<owner>mathp@chromium.org</owner>
<summary>The index of the accepted Autofill suggestion in the popup.</summary>
</histogram>
<histogram name="Autofill.SuggestionAcceptedIndex.Autocomplete"
units="position">
<owner>mathp@chromium.org</owner>
<summary>
The index of the accepted Autocomplete suggestion in the popup.
</summary>
</histogram>
<histogram name="Autofill.UnmaskPrompt.Duration" units="ms">
<owner>waltercacau@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.UnmaskPrompt.Events" enum="AutofillUnmaskPromptEvent">
<owner>waltercacau@chromium.org</owner>
<summary>
Events tracking the usage of the unmasking prompt. This prompt is triggered
when a user selects a masked card in a autofill dropdown.
</summary>
</histogram>
<histogram name="Autofill.UnmaskPrompt.GetRealPanDuration" units="ms">
<owner>waltercacau@chromium.org</owner>
<summary>
Duration of the GetRealPan API call. This API call is triggered by the
unmasking prompt when the user types information to verify his ownership of
the card being fetched.
</summary>
</histogram>
<histogram name="Autofill.UnmaskPrompt.GetRealPanResult"
enum="AutofillGetRealPanResult">
<owner>waltercacau@chromium.org</owner>
<summary>
Tracks the result of the GetRealPan API call. This API call is triggered by
the unmasking prompt when the user types information to verify his ownership
of the card being fetched.
</summary>
</histogram>
<histogram name="Autofill.UnmaskPrompt.TimeBeforeAbandonUnmasking" units="ms">
<owner>waltercacau@chromium.org</owner>
<summary>
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 &quot;Verify&quot; button and then
clicking &quot;Cancel&quot;.
</summary>
</histogram>
<histogram name="Autofill.UnmaskPrompt.UnmaskingDuration" units="ms">
<owner>waltercacau@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Autofill.UserHappiness" enum="AutofillUserHappiness">
<owner>isherman@chromium.org</owner>
<summary>
Measures the frequency of various events in the Autofill user interaction
flow. By comparing frequencies, we can compute several interesting
&quot;user happiness&quot; metrics.
</summary>
</histogram>
<histogram name="BackgroundMode.BackgroundApplicationsCount">
<owner>atwilson@chromium.org</owner>
<owner>mvanouwerkerk@chromium.org</owner>
<summary>
The number of background applications (extensions) for a profile that were
loaded after the profile was registered with the BackgroundModeManager.
</summary>
</histogram>
<histogram name="BackgroundMode.BackgroundModeEnabledPrefChanged"
enum="BooleanEnabled">
<owner>mvanouwerkerk@chromium.org</owner>
<summary>
Logged if BackgroundModeManager is running and listening for pref changes,
and the pref does indeed change. The new value is logged.
</summary>
</histogram>
<histogram name="BackgroundMode.MenuItemClick" enum="BackgroundModeMenuItem">
<owner>mvanouwerkerk@chromium.org</owner>
<summary>
Logged when an item in the system tray icon menu is clicked.
</summary>
</histogram>
<histogram name="BackgroundMode.OnStartup.AutoLaunchState"
enum="AutoLaunchState">
<owner>gab@chromium.org</owner>
<summary>
Logged during BackgroundModeManager's initialization. Indicates the
AutoLaunchState the current browser process was launched in.
</summary>
</histogram>
<histogram name="BackgroundMode.OnStartup.IsBackgroundModePrefEnabled"
enum="BooleanEnabled">
<owner>gab@chromium.org</owner>
<summary>
Logged during BackgroundModeManager's initialization. Indicates the state of
the kBackgroundModeEnabled pref on startup.
</summary>
</histogram>
<histogram name="BackgroundSync.Event.BatchSize">
<owner>iclelland@chromium.org</owner>
<summary>
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. Periodic syncs often run in a batch. 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.
</summary>
</histogram>
<histogram name="BackgroundSync.Event.OneShotResult" enum="BooleanSuccess">
<owner>iclelland@chromium.org</owner>
<obsolete>
As of 10/2015 this has been replaced by
BackgroundSync.Event.OneShotResultPattern.
</obsolete>
<summary>Records whether a one-shot sync event succeeded or failed.</summary>
</histogram>
<histogram name="BackgroundSync.Event.OneShotResultPattern"
enum="BackgroundSyncResultPattern">
<owner>jkarlin@chromium.org</owner>
<summary>
Records whether a periodic sync event succeeded or failed and whether the
sync event finished in the foreground or background.
</summary>
<details>
A sync event finished in the foreground if the associated Service Worker
Registration has a client at the time that the event finished.
</details>
</histogram>
<histogram name="BackgroundSync.Event.OneShotStartedInForeground"
enum="BooleanInForeground">
<owner>jkarlin@chromium.org</owner>
<summary>
Records whether a one-shot sync started firing in the foreground or
background. Called shortly before the event is fired.
</summary>
</histogram>
<histogram name="BackgroundSync.Event.PeriodicResult" enum="BooleanSuccess">
<owner>iclelland@chromium.org</owner>
<obsolete>
As of 10/2015 this has been replaced by
BackgroundSync.Event.PeriodicResultPattern.
</obsolete>
<summary>Records whether a periodic sync event succeeded or failed.</summary>
</histogram>
<histogram name="BackgroundSync.Event.PeriodicResultPattern"
enum="BackgroundSyncResultPattern">
<owner>jkarlin@chromium.org</owner>
<summary>
Records whether a one-shot sync event succeeded or failed and whether the
sync event finished in the foreground or background.
</summary>
<details>
A sync event finished in the foreground if the associated Service Worker
Registration has a client at the time that the event finished.
</details>
</histogram>
<histogram name="BackgroundSync.Event.PeriodicStartedInForeground"
enum="BooleanInForeground">
<owner>jkarlin@chromium.org</owner>
<summary>
Records whether a periodic sync event started firing in the foreground or
background. Called shortly before the event is fired.
</summary>
</histogram>
<histogram name="BackgroundSync.Event.Time" units="milliseconds">
<owner>iclelland@chromium.org</owner>
<summary>
Time taken to execute a batch of sync events. A batch is defined as the set
of sync events dispatched at the same time by the BackgroundSyncManager.
Periodic syncs often run in a batch. 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.
</summary>
</histogram>
<histogram name="BackgroundSync.LaunchTask.CancelSuccess" enum="BooleanSuccess">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to cancel a future browser launch using the
GCM Network Manager on Android.
</summary>
</histogram>
<histogram name="BackgroundSync.LaunchTask.PlayServicesAvailable"
enum="Boolean">
<owner>iclelland@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="BackgroundSync.LaunchTask.ScheduleSuccess"
enum="BooleanSuccess">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to schedule a future browser launch using
the GCM Network Manager on Android.
</summary>
</histogram>
<histogram name="BackgroundSync.NetworkObserver.HasPermission" enum="Boolean">
<owner>iclelland@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="BackgroundSync.Registration.OneShot"
enum="BackgroundSyncStatus">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to register a one-shot sync.
</summary>
</histogram>
<histogram name="BackgroundSync.Registration.OneShot.CouldFire"
enum="BooleanCouldFireImmediately">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to register a one-shot sync in a situation
where the sync could fire immediately.
</summary>
</histogram>
<histogram name="BackgroundSync.Registration.OneShot.IsDuplicate"
enum="BooleanRegistrationIsDuplicate">
<owner>iclelland@chromium.org</owner>
<summary>
Records whether a one-shot sync registration exactly duplicates an existing
registered sync.
</summary>
</histogram>
<histogram name="BackgroundSync.Registration.Periodic"
enum="BackgroundSyncStatus">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to register a periodic sync.
</summary>
</histogram>
<histogram name="BackgroundSync.Registration.Periodic.IsDuplicate"
enum="BooleanRegistrationIsDuplicate">
<owner>iclelland@chromium.org</owner>
<summary>
Records whether a periodic sync registration exactly duplicates an existing
registered sync.
</summary>
</histogram>
<histogram name="BackgroundSync.Unregistration.OneShot"
enum="BackgroundSyncStatus">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to unregister a one-shot sync.
</summary>
</histogram>
<histogram name="BackgroundSync.Unregistration.Periodic"
enum="BackgroundSyncStatus">
<owner>iclelland@chromium.org</owner>
<summary>
Records the result of attempting to unregister a periodic sync.
</summary>
</histogram>
<histogram name="BatteryStatus.NumberBatteriesLinux"
enum="BatteryStatusNumberBatteries">
<owner>timvolodine@chromium.org</owner>
<summary>
Number of batteries reported by the UPower service on Linux at the start of
the Battery Status API.
</summary>
</histogram>
<histogram name="BatteryStatus.NumberBatteriesMac"
enum="BatteryStatusNumberBatteries">
<owner>timvolodine@chromium.org</owner>
<summary>
Number of internal batteries reported by MacOS at the start of the Battery
Status API.
</summary>
</histogram>
<histogram name="BatteryStatus.NumberBatteriesWin"
enum="BatteryStatusNumberBatteriesWin">
<owner>timvolodine@chromium.org</owner>
<summary>
Number of batteries reported by Windows at the start of the Battery Status
API.
</summary>
</histogram>
<histogram name="BatteryStatus.StartAndroid" enum="BooleanSuccess">
<owner>timvolodine@chromium.org</owner>
<summary>
Whether the Battery Status API was successfully started up on Android.
</summary>
</histogram>
<histogram name="Blacklist.Blocked" enum="DllHash">
<owner>csharp@chromium.org</owner>
<summary>
Records the name hashes of all the dlls that are blocked from the browser
process.
</summary>
</histogram>
<histogram name="Blacklist.PatchedInRenderer" enum="BooleanHit">
<obsolete>
Removed at 2015 July.
</obsolete>
<owner>csharp@chromium.org</owner>
<summary>
Counts the number of times a renderer process is started with the browser
blacklist patch. This should never be hit.
</summary>
</histogram>
<histogram name="Blacklist.RetryAttempts.Success">
<owner>csharp@chromium.org</owner>
<owner>krstnmnlsn@chromium.org</owner>
<summary>
Records the number of attempts needed before the blacklist is properly set
up. This is logged immediately after a successful setup.
</summary>
</histogram>
<histogram name="Blacklist.Setup" enum="BlacklistSetup">
<owner>csharp@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="Blink.DecodedImage.Orientation" enum="DecodedImageOrientation">
<owner>rob.buis@samsung.org</owner>
<summary>Image orientation inferred during decode.</summary>
</histogram>
<histogram name="Blink.DecodedImageType" enum="DecodedImageType">
<owner>urvang@chromium.org</owner>
<summary>Image codec inferred during decode.</summary>
</histogram>
<histogram name="Blink.Fonts.ShapeCache">
<owner>eae@chromium.org</owner>
<summary>
Total number of entries in all Blink ShapeCache instances. The value is
reported each time the FontCache::purge() method is called.
</summary>
</histogram>
<histogram name="Blink.MediaElement.Autoplay" enum="MediaElementAutoPlay">
<owner>oysteine@chromium.org</owner>
<summary>
Records user observation and interaction with Media HTML elements that
feature autoplay, either script-controlled or through the attribute.
</summary>
</histogram>
<histogram name="Blink.RestoredCachedStyleSheet"
enum="RestoredCachedStyleSheet">
<owner>kouhei@chromium.org</owner>
<summary>
On each link stylesheet tag resolve, record whether a Blink MemoryCached
StyleSheetContents was reused.
</summary>
</histogram>
<histogram name="Blink.XHR.setRequestHeader.HeaderValueCategoryInRFC7230"
enum="XMLHttpRequestHeaderValueCategoryInRFC7230">
<owner>hiroshige@chromium.org</owner>
<summary>
The count of XMLHttpRequest.setRequestHeader() calls where header values are
invalid/valid but affected by normalization/valid in RFC 7230.
https://crbug.com/455099.
</summary>
</histogram>
<histogram name="BlinkGC.CollectGarbage" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>Duration of time taken to run Heap::collectGarbage().</summary>
</histogram>
<histogram name="BlinkGC.CollectionRate" units="percent">
<owner>haraken@chromium.org</owner>
<summary>
The percentage of objects that have been collected by a Blink GC. 0 is
passed if there were no objects when a Blink GC started.
</summary>
</histogram>
<histogram name="BlinkGC.CommittedSize" units="MB">
<owner>haraken@chromium.org</owner>
<summary>
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.
</summary>
</histogram>
<histogram name="BlinkGC.CompleteSweep" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>Duration of time taken to run ThreadState::completeSweep().</summary>
</histogram>
<histogram name="BlinkGC.GCReason" enum="GCReason">
<owner>haraken@chromium.org</owner>
<summary>A type of Blink GC.</summary>
</histogram>
<histogram name="BlinkGC.ObjectSizeAfterGC" units="KB">
<owner>haraken@chromium.org</owner>
<summary>
The size of allocated objects just after Blink GC is triggered.
</summary>
</histogram>
<histogram name="BlinkGC.ObjectSizeBeforeGC" units="KB">
<owner>haraken@chromium.org</owner>
<summary>
The size of allocated objects just before Blink GC is triggered.
</summary>
</histogram>
<histogram name="BlinkGC.PerformPendingSweep" units="milliseconds">
<obsolete>
Removed at 2014 Jan.
</obsolete>
<owner>haraken@chromium.org</owner>
<summary>
Duration of time taken to run ThreadState::performPendingSweep().
</summary>
</histogram>
<histogram name="BlinkGC.TimeForGlobalWeakProcessing" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>
Duration of time taken to run global weak processing of Blink GC.
</summary>
</histogram>
<histogram name="BlinkGC.TimeForInvokingPreFinalizers" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>
Duration of time taken to run ThreadState::invokePreFinalizers().
</summary>
</histogram>
<histogram name="BlinkGC.TimeForStoppingThreads" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>
Duration of time taken to stop all Blink threads before starting a GC.
</summary>
</histogram>
<histogram name="BlinkGC.TimeForSweepingAllObjects" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>Accumulated time taken to sweep all objects.</summary>
</histogram>
<histogram name="BlinkGC.TimeForThreadLocalWeakProcessing" units="milliseconds">
<owner>haraken@chromium.org</owner>
<summary>Duration of time taken to run thread-local weak processing.</summary>
</histogram>
<histogram name="BlinkGC.TotalAllocatedSpace" units="KB">
<owner>haraken@chromium.org</owner>
<summary>
The total size of allocated space in OS when a Blink GC is triggered.
</summary>
</histogram>
<histogram name="BlinkGC.TotalObjectSpace" units="KB">
<owner>haraken@chromium.org</owner>
<summary>
The total size of object space in all threads when a Blink GC is triggered.
</summary>
</histogram>
<histogram name="Bluetooth.ConnectedDeviceCount" units="devices">
<owner>keybuk@chromium.org</owner>
<summary>
Counts the number of simulataneously connected Bluetooth devices. Used to
direct testing efforts, and by our UI team to determine appropriate UI
sizes.
</summary>
</histogram>
<histogram name="Bluetooth.DiscoverySession.Start.Outcome"
enum="BluetoothDiscoveryOutcomes">
<owner>jyasskin@chromium.org</owner>
<owner>ortuno@chromium.org</owner>
<owner>scheib@chromium.org</owner>
<summary>
Records the outcome of calls to BluetoothAdapter::StartDiscoverySession.
Used to prioritize efforts to fix failures of this function.
</summary>
</histogram>
<histogram name="Bluetooth.DiscoverySession.Stop.Outcome"
enum="BluetoothDiscoveryOutcomes">
<owner>jyasskin@chromium.org</owner>
<owner>ortuno@chromium.org</owner>
<owner>scheib@chromium.org</owner>
<summary>
Records the outcome of calls to BluetoothDiscoverySession::Stop. Used to
prioritize efforts to fix failures of this function.
</summary>
</histogram>