dmazzoni@chromium.org
kenjibaheux@google.com
Whether the Chrome OS Accessibility Menu is set to be shown regardless of
the state of a11y features.(checked once 45 secs after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
tengs@chromium.org
Whether the Chrome OS Autoclick feature is on (checked once 45 secs after
startup).
dmazzoni@chromium.org
kenjibaheux@google.com
tengs@chromium.org
If the user has enabled Autoclick, this is the delay set by the user for
autoclicks to occur, in milliseconds.
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the Chrome OS High Contrast mode feature is on (checked once 45 secs
after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the Chrome OS Large Cursor feature is on (checked once 45 secs after
startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the Chrome OS Screen Magnifier feature is on (checked once 45 secs
after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the Chrome OS Spoken Feedback feature is on (checked once 45 secs
after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
tengs@chromium.org
Whether the Chrome OS Sticky Keys feature is on (checked once 45 secs after
startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the Chrome OS Virtual Keyboard feature is on (checked once 45 secs
after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
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.
dmazzoni@chromium.org
kenjibaheux@google.com
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).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether Chrome has enabled accessibility support because it detects
supported assistive technology running, or due to being manually enabled via
a command-line flag (checked once 45 secs after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether Windows system settings show that audio descriptions are enabled
(checked once 45 secs after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the third-party JAWS screen reader is running (checked once 45 secs
after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the third-party NVDA screen reader is running (checked once 45 secs
after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the third-party System Access To Go screen reader is running
(checked once 45 secs after startup).
dmazzoni@chromium.org
kenjibaheux@google.com
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.
dmazzoni@chromium.org
kenjibaheux@google.com
Whether Windows system settings show that Sticky Keys are enabled.
dmazzoni@chromium.org
kenjibaheux@google.com
Whether the third-party ZoomText screen magnifier is running.
fdegans@chromium.org
Reports the FPU capabilities of the Android ARM device. This is recorded
once per browser session during startup.
rsesek@chromium.org
Reports the kernel major and minor version from the utsname.release field.
The low 16 bits of each version are combined into a 32-bit integer. The
range is from [0x00020006,0x0004000a] to track kernel versions 2.6 through
4.10.
rsesek@chromium.org
Reports the level of kernel support for the seccomp-bpf sandbox using
prctl(PR_SET_SECCOMP).
rsesek@chromium.org
Reports the level of kernel support for the seccomp-bpf sandbox using the
seccomp system call.
dtrainor@chromium.org
When a user closes a tab an undo toast will popup on certain devices giving
the user the chance to undo closing that tab. This stat tracks how the user
interacts with that UI and what actions they take. A cold start means that
the undo bar wasn't showing when it was triggered to show again. A warm
start means that it was. Warm starts can happen when the user closes
multiple tabs close together. When the undo bar is dismissed, all closes
that were queued up to be undone are committed. This can happen either by a
timeout or by an action by the user to move to another part of the UI.
dfalcantara@chromium.org
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.
dfalcantara@chromium.org
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.
dfalcantara@chromium.org
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.
michaeln@chromium.org
AppCache check response result code.
michaeln@chromium.org
Time elapsed between a completion task being queued and run.
michaeln@chromium.org
The amount of time taken to run a completion task on the IO thread.
michaeln@chromium.org
Tracks the number of times corruption is detected in the sql database.
michaeln@chromium.org
AppCache initialization result code.
michaeln@chromium.org
How long URLRequests to be retrieved from the appcache are delayed.
michaeln@chromium.org
How long URLRequests that result in a synthesized error are delayed.
michaeln@chromium.org
How long URLRequests to be retrieved over the network are delayed.
michaeln@chromium.org
Tracks the success rate of retrieving a main resource from the appcache.
michaeln@chromium.org
Identifies where a missing manifest was detected occured.
michaeln@chromium.org
Logged on each occurrence of there being no record for the manifest file in
the entries table.
michaeln@chromium.org
Tracks the number of times the appcache reinit process occurs. The boolean
value indicates whether it was a repeated attempt to reinitialize during a
browsing session.
michaeln@chromium.org
Tracks the success rate of retrieving a sub resource from the appcache.
michaeln@chromium.org
Time elapsed between a background task being queued and run.
michaeln@chromium.org
The amount of time taken to run a background task.
michaeln@chromium.org
AppCache update job result code.
michaeln@chromium.org
Percent completion at point of failure of an update job.
michaeln@chromium.org
Whether the resource causing the failure was from a different origin.
michaeln@chromium.org
Whether any progresss had been made in the 5 minutes preceeding failure.
sashab@chromium.org
The number of times the app info dialog is launched. This is gathered each
time the app info dialog is opened, from each of the places the dialog can
be opened from.
sashab@chromium.org
The location of the app that the dialog was opened for. This is gathered
each time the app info dialog is opened.
sashab@chromium.org
The type of the app that the dialog was opened for. This is gathered each
time the app info dialog is opened.
tapted@chromium.org
benwells@chromium.org
The number of times v2 packaged apps are launched grouped by
extension_misc::AppLaunchBuckets. See also Extensions.AppLaunch.
mad@chromium.org
Interactions with the App Launcher promo dialog.
calamity@chromium.org
The amount of time it takes to build the app list UI. This is logged each
time the app list is built from scratch.
calamity@chromium.org
The number of user interactions with the app list doodle. This is logged
once per action.
tapted@chromium.org
The trigger that caused the app list to be enabled. Recorded when the user
first shows the app list. If not shown after one hour, will be recorded
then. If Chrome was not running at the one-hour mark, will be recorded
during the next Chrome startup.
calamity@chromium.org
The page that the app list goes to. This is gathered every time the user
initiates a transition to another page in the launcher.
tapted@chromium.org
The number of searches that are started in the app list. This is gathered
each time the app list search box transitions from empty to non-empty.
calamity@chromium.org
The length of the app list search query when a result is opened. This is
gathered per click of a search result.
calamity@chromium.org
The minimum number of arrow keys a user would need to press to navigate to
the opened search result. This is gathered per click of a search result.
calamity@chromium.org
The display type of the app list search result that was opened by the user.
This is gathered per click of a search result.
tapted@chromium.org
The type of app list search result that was opened by the user. This is
gathered per click of a search result.
tapted@chromium.org
Time between enabling the app list, and a user explicitly choosing to show
it. If the app list is not shown after one hour, an entry in the last bucket
is recorded. If the user installs a second packaged app within one hour, or
if the app list was not enabled by installing a packaged app from the Web
Store, no time value is recorded - only Apps.AppListHowEnabled.
tapted@chromium.org
The amount of time spent in warmup (in WarmupForProfile call). This will
tell us how long warmup blocks the UI.
jackhou@chromium.org
Counts which major milestone versions of app_mode_loader are sending
--app-shim-error. --app-shim-error is sent as a command line argument to
Chrome when app_mode_loader was unable to dyload the Chrome Framework and
call ChromeAppModeMain. For example, when Chrome updates from 32-bit to
64-bit, an older shim will find the new framework version but fail to dyload
it.
kuscher@google.com
rbyers@chromium.org
Number of active touch-points when a new touch-point is added.
kuscher@google.com
The show type of the active window tracked over time by logging on a regular
basis (30 minutes).
bruthig@chromium.org
tdanderson@chromium.org
The amount of time between selecting an item from the Ash app list. Not
recorded on the first time an item is selected from the app list after
startup.
kuscher@google.com
varkha@chromium.org
User-initiated action taken that affects docked windows such as docking,
undocking, minimizing, restoring, closing or just dragging a docked window.
kuscher@google.com
varkha@chromium.org
Source (mouse, touch or unknown) of the user-initiated action for docked
windows.
kuscher@google.com
varkha@chromium.org
Number of all docked windows or panels including hidden or minimized.
Recorded on every user action that interacts with docked windows.
kuscher@google.com
varkha@chromium.org
Number of large (wider than dock maximum width) windows that had to be
shrunk to get docked among the visible docked windows. Recorded on every
user action that interacts with docked windows.
kuscher@google.com
varkha@chromium.org
Number of docked visible panels. Recorded on every user action that
interacts with docked windows.
kuscher@google.com
varkha@chromium.org
Number of visible docked windows or panels. Recorded on every user action
that interacts with docked windows.
kuscher@google.com
varkha@chromium.org
Time elapsed between instances of docking, undocking or any other action
affecting docked state of a window.
kuscher@google.com
varkha@chromium.org
Width of the docked area in pixels. Recorded every time it changes after a
user window resize operation is completed.
Deprecated 08/2014 in Issue 352654, and replaced by Event.GestureCreated.
kuscher@google.com
rbyers@chromium.org
The gesture-events recognized and dispatched by the browser gesture
recognizer.
kuscher@google.com
rbyers@chromium.org
The gesture-events recognized and dispatched by the browser gesture
recognizer for various UI components.
kuscher@google.com
The type of the window which is put into immersive fullscreen. Immersive
fullscreen is entered via the F4 key.
tdanderson@google.com
bruthig@google.com
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.
bruthig@google.com
tdanderson@google.com
The number of icons in the shelf, not including the App Launcher icon. This
metric is recorded every 30 minutes.
bruthig@google.com
tdanderson@google.com
The number of pinned icons in the shelf, not including the App Launcher
icon. This metric is recorded every 30 minutes.
bruthig@google.com
tdanderson@google.com
The number of unpinned icons in the shelf. This metric is recorded every 30
minutes.
bruthig@google.com
tdanderson@google.com
The number of seconds between contiguous task switch user actions triggered
by the Shelf buttons where the user activates a different user-predicatble
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'.
kuscher@google.com
The current state of the shelf (alignment) tracked over time by logging on a
regular basis (30 minutes), this is used instead of log in or shelf usage to
track users that do not lock/unlock or log in frequently and use a small
number of browser instances or otherwise infrequently interact with the
shelf launcher.
kuscher@google.com
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.
kuscher@google.com
rbyers@chromium.org
The duration of mostly stationary long-duration touches.
bruthig@chromium.org
tdanderson@chromium.org
The number of seconds between tab switches triggered by a user gesture (e.g.
Ctrl+T, Ctrl+1, tapping or clicking the tab strip, etc).
Deprecated 12/2013 in r239809, and replaced by Ash.TouchDuration2.
kuscher@google.com
The duration of a touch-sequence.
Deprecated 08/2014 in Issue 352654, and replaced by Event.TouchDuration.
kuscher@google.com
rbyers@chromium.org
The duration of a touch-sequence.
Deprecated 08/2014 in Issue 352654, and replaced by Event.TouchMaxDistance.
kuscher@google.com
rbyers@chromium.org
The maximum euclidean distance in dips which a touch point has travelled
away from its starting point. Only measured for single finger gestures.
kuscher@google.com
rbyers@chromium.org
The interval between touch-move events.
kuscher@google.com
rbyers@chromium.org
The distance between touch-move events.
kuscher@google.com
rbyers@chromium.org
The position of the touch-events along the X axis.
kuscher@google.com
rbyers@chromium.org
The position of the touch-events along the Y axis.
kuscher@google.com
rbyers@chromium.org
The radius of a touch event.
kuscher@google.com
rbyers@chromium.org
The interval between the end of a touch-sequence and the start of the next
touch-sequence.
kuscher@google.com
rbyers@chromium.org
The number of rapid touch-starts that happened within a short interval.
Logged once for each such burst group.
girard@chromium.org
The length of time that TouchView is active, for each activation.
girard@chromium.org
The proportion of time spent in TouchView during a session.
girard@chromium.org
The total time that TouchView is active during a session.
girard@chromium.org
The length of time between TouchView activations.
girard@chromium.org
The total time that TouchView is not active during a session.
Deprecated as of 11/2012. Use of indices has been removed.
kuscher@google.com
The wallpaper index if one of the default wallpapers has been selected.
Recorded at user login. Currently only for the old wallpaper picker UI.
kuscher@google.com
The wallpaper type. Recorded at user login.
flackr@chromium.org
kuscher@google.com
The amount of time the Alt key is held after pressing Alt+Tab to begin
cycling through windows.
tdanderson@google.com
bruthig@google.com
The number of seconds between task switches triggered by the next window and
previous window accelerator keys (ie Alt+Tab, Alt+Shift+Tab).
flackr@chromium.org
tdanderson@chromium.org
The number of times the arrow keys are pressed in overview mode per session,
i.e. between bringing up overview mode and ending it. This is only measured
for the sessions that end by selecting a window with the enter key.
Deprecated as of 06/2014. No longer relevant since alt-tab switching was
separated from WindowSelector.
flackr@chromium.org
kuscher@google.com
The amount of time the Alt key is held after pressing Alt+Tab to begin
cycling through windows.
flackr@chromium.org
kuscher@google.com
The number of items (single windows or groups of windows such as panels) in
the overview mode, present at the start of each session.
tdanderson@chromium.org
flackr@chromium.org
The number of items showing in overview mode at the moment when an item is
selected or when selection is canceled. Only recorded if the text filtering
textfield contains a non-empty string.
flackr@chromium.org
tdanderson@chromium.org
The ratio between the arrow key presses and the number of overview items,
expressed as a percentage for a single session.
flackr@chromium.org
tdanderson@chromium.org
The number of items closed from the window overview for a single session.
tdanderson@chromium.org
flackr@chromium.org
The length of the string entered into the text filtering textfield at the
moment when an item is selected or when selection is canceled.
tdanderson@chromium.org
flackr@chromium.org
The number of times the text filtering textfield has had all of its text
removed within a single overview mode session. Measured from the time
overview mode is invoked to when an item is selected or when selection is
canceled.
bruthig@chromium.org
tdanderson@chromium.org
The amount of time between endings of overview mode sessions which were
caused by the user selecting a window which was not previously active. Only
recorded on the second and later times after startup that the user selected
a window which was not previously active.
flackr@chromium.org
kuscher@google.com
The amount of time between uses of overview mode, recorded when overview
mode is entered. Only recorded on the second and later times after startup
that the user entered overview mode.
flackr@chromium.org
kuscher@google.com
The amount of time spent in overview mode. Overview mode is engaged by
pressing the overview button. The time is measured from the moment the
windows begin animating to a thumbnail size preview to when a window is
selected or selection is canceled.
tdanderson@chromium.org
flackr@chromium.org
The amount of time spent in overview mode when text filtering is used. The
time is measured from the moment the windows begin animating to a thumbnail
size preview to when a window is selected or selection is canceled. Only
recorded if the text filtering textfield contains a non-empty string.
ttuttle@chromium.org
Count of DnsAttempts before DnsTransaction completes with failure.
ttuttle@chromium.org
Count of DnsAttempts before DnsTransaction completes successfully.
ttuttle@chromium.org
Whether DnsConfigService::OnConfigChange actually corresponded to a change
in DnsConfig.
ttuttle@chromium.org
Duration of time between calls to DnsConfigService::InvalidateConfig.
ttuttle@chromium.org
Duration of time spent parsing DnsConfig.
ttuttle@chromium.org
Counts of results of parsing DnsConfig in DnsConfigServicePosix.
ttuttle@chromium.org
Whether DnsConfig was parsed successfully.
ttuttle@chromium.org
Counts of results of parsing DnsConfig in DnsConfigServiceWin.
ttuttle@chromium.org
Whether the first valid DnsConfig included a rogue nameserver.
ttuttle@chromium.org
Counts of specific error codes returned by DnsTask if a subsequent ProcTask
succeeded, at the end of a streak of failures after which the DnsClient was
disabled.
ttuttle@chromium.org
TRUE counts the events when a valid DnsConfig is received and used to enable
DnsClient, while FALSE counts the events when DnsClient is disabled after a
series of successful fallbacks from DnsTask to ProcTask.
ttuttle@chromium.org
Duration of time spent by ProcTask in failing fallback resolutions.
ttuttle@chromium.org
Duration of time spent by ProcTask in successful fallback resolutions.
ttuttle@chromium.org
Whether there was a valid DNS configuration at the start of a job which
eventually completed successfully.
ttuttle@chromium.org
Whether DnsHosts were parsed successfully.
ttuttle@chromium.org
Whether DnsConfigService::OnHostsChange actually corresponded to a change in
DnsHosts.
ttuttle@chromium.org
Duration of time between calls to DnsConfigService::InvalidateHosts.
ttuttle@chromium.org
Duration of time spent parsing DnsHosts.
ttuttle@chromium.org
Counts of results of parsing DnsHosts in DnsConfigServiceWin.
ttuttle@chromium.org
The size of the HOSTS file observed before each attempt to parse it.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient).
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority HIGHEST when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority IDLE when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority LOW when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority LOWEST when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority MEDIUM when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient).
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority HIGHEST
when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority IDLE when
started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority LOW when
started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority LOWEST when
started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority MEDIUM when
started.
ttuttle@chromium.org
Type of nameservers in the DNS config, recorded each time the config is read
by the DNSConfigService.
ttuttle@chromium.org
Counts of results of parsing addresses out of DNS responses in successful
DnsTransactions.
ttuttle@chromium.org
The source of the async DNS preference's default. Logged at startup, when
the IO thread is created.
ttuttle@chromium.org
The source of the async DNS preference's value. Logged at startup, when the
IO thread is created.
ttuttle@chromium.org
Counts of specific error codes returned by DnsTask if a subsequent ProcTask
succeeded.
ttuttle@chromium.org
Duration of time taken by DnsTask in resolutions that failed. Excludes time
spent in the subsequent fallback.
ttuttle@chromium.org
Counts of the overall results of using asynchronous DNS in HostResolverImpl.
This only includes jobs started with valid DNS configuration and excludes
synchronous resolutions (as IP literals, from cache, and from HOSTS).
ttuttle@chromium.org
Duration of time taken by DnsTask in resolutions that succeeded.
ttuttle@chromium.org
Same as AsyncDNS.ResolveSuccess, but limited to pure IPv4 lookups.
ttuttle@chromium.org
Same as AsyncDNS.ResolveSuccess, but limited to pure IPv6 lookups.
ttuttle@chromium.org
Same as AsyncDNS.ResolveSuccess, but limited to IPv4/IPv6 lookups.
ttuttle@chromium.org
Count of servers in DnsConfig. Recorded on every new DnsSession, which is
created on DNS change.
ttuttle@chromium.org
Index in DnsConfig of the failing server, recorded at the time of failure.
ttuttle@chromium.org
Count of server failures after network change before first success in the
DnsSession. Recorded at the time of first success.
ttuttle@chromium.org
Count of server failures after success until the end of the session. Server
has reported success at some point during the session. Recorded at the end
of the DnsSession.
ttuttle@chromium.org
Count of server failures before success. This is NOT the first success in
the DnsSession. Recorded at the time of success.
ttuttle@chromium.org
Count of server failures without success until the end of the session.
Server has never reported success during the DnsSession. Recorded at the end
of the DnsSession.
ttuttle@chromium.org
The current server is "good" and does not have to be skipped.
ttuttle@chromium.org
Duration of time taken in failing calls to AddressSorter in dual-stack
resolutions using DnsTask.
ttuttle@chromium.org
Duration of time taken in successful calls to AddressSorter in dual-stack
resolutions using DnsTask.
ttuttle@chromium.org
The number of names from the search name list consumed during a successful
transaction (QTYPE A only).
ttuttle@chromium.org
The number of names left on the search name list at the end of a successful
transaction (QTYPE A only).
ttuttle@chromium.org
The number of names on the search name list at the start of a transaction
(QTYPE A only).
ttuttle@chromium.org
Duration of time taken by DnsTCPAttempt in failed attempts. Excludes
timeouts.
ttuttle@chromium.org
Duration of time taken by DnsTCPAttempt in successful attempts.
ttuttle@chromium.org
Difference between RTT and timeout calculated using Histogram algorithm.
ttuttle@chromium.org
Difference between timeout calculated using Histogram algorithm and RTT.
ttuttle@chromium.org
Difference between RTT and timeout calculated using Jacobson algorithm.
ttuttle@chromium.org
Difference between timeout calculated using Jacobson algorithm and RTT.
ttuttle@chromium.org
Duration of time that would be spent waiting for lost request using
Histogram algorithm.
ttuttle@chromium.org
Duration of time that would be spent waiting for lost request using Jacobson
algorithm.
ttuttle@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Excludes speculative requests.
ttuttle@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Speculative requests only.
ttuttle@chromium.org
Duration of time taken in failing DnsTransactions. This includes server
failures, timeouts and NXDOMAIN results.
ttuttle@chromium.org
Duration of time taken in successful DnsTransactions. This includes all
NOERROR answers, even if they indicate the name has no addresses or they
cannot be parsed.
ttuttle@chromium.org
Same as AsyncDNS.TransactionSuccess but limited to A query type.
ttuttle@chromium.org
Same as AsyncDNS.TransactionSuccess but limited to AAAA query type.
ttuttle@chromium.org
TTL of the resolved addresses, as in the response received from the server.
For results served from local cache, the TTL is from the original response.
ttuttle@chromium.org
Duration of time taken by DnsUDPAttempt in failed attempts. Excludes
timeouts.
ttuttle@chromium.org
Duration of time taken by DnsUDPAttempt in successful attempts. Includes
responses arriving after timeout, if multiple attempts are allowed.
ttuttle@chromium.org
Duration of time since the last empty config result to the time a non-change
OnConfigChange is received.
ttuttle@chromium.org
Duration of time since the last empty config result to the time a non-change
OnHostsChange is received.
ttuttle@chromium.org
The result of DnsConfigService watch. Counts STARTED on every initialization
and FAILED_* on any failure.
jbauman@chromium.org
Whether the browser compositor uses GPU or the software renderer.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the frequency of user interactions with the Autocheckout bubble,
which prompts users to invoke Autocheckout on supported websites.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the frequency of final states reached in Autocheckout buy flow.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
The state of the Autocheckout dialog when it was dismissed.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user submitted the Autocheckout
dialog and when the Autocheckout flow, or filling process, concluded.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user submitted the Autocheckout
dialog and when the Autocheckout flow concluded, in cases where the flow
failed.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user submitted the Autocheckout
dialog and when the Autocheckout flow concluded, in cases where the flow
succeeded.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
The initial state of a user that's interacting with a freshly shown
Autocheckout dialog.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
User interactions with the Autofill popup shown while filling an
Autocheckout dialog.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the frequency of security warnings and errors in the Autocheckout
dialog.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the duration for which an Autocheckout dialog was shown.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the duration for which an Autocheckout dialog was shown, in cases
where the user ended up canceling out of the dialog.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the duration for which an Autocheckout dialog was shown, in cases
where the user ended up accepting the dialog.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures how users are interacting with the Autocheckout dialog UI.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the duration of time it takes for the Autocheckout UI to be
actionable by the user after it is shown.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the frequency of errors in communicating with the Google Online
Wallet server.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures the frequency of required user actions returned by the Google
Online Wallet server.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures time taken to download the Autocheckout whitelist file.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures time taken to download the Autocheckout whitelist file in case the
download was failed.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Measures time taken to download the Autocheckout whitelist file in case the
download was succeeded.
erikchen@chromium.org
Whether an attempt to access the Mac AddressBook was skipped because doing
so would incorrectly cause the appearance of the permissions dialog. This
happens when Chrome auto-update changes the binary on disk before the first
AddressBook access attempt.
isherman@chromium.org
Whether the Mac AddressBook was available on an attempt to read data from
it.
isherman@chromium.org
Whether the Mac AddressBook was available on the *first* attempt to read
data from it. This is only recorded once per Chrome profile.
isherman@chromium.org
The number of address suggestions shown in the Autofill popup.
Deprecated as of 3/2011, replaced by Autofill.CreditCardInfoBar.
Please list the metric's owners. Add more owner tags as needed.
The Autofill credit card info bar was accepted.
Deprecated as of 3/2011, replaced by Autofill.CreditCardInfoBar.
Please list the metric's owners. Add more owner tags as needed.
The Autofill credit card info bar was denied.
isherman@chromium.org
The relative frequency with which users accept, deny, or ignore the Autofill
credit card info bar prompt.
isherman@chromium.org
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.
isherman@chromium.org
Time elapsed between the user's first interaction with a form and the form's
submission, for an autofilled form.
isherman@chromium.org
Time elapsed between the user's first interaction with a form and the form's
submission, for a non-autofilled form.
isherman@chromium.org
Time elapsed between form load and form submission, for an autofilled form.
isherman@chromium.org
Time elapsed between form load and form submission, for a non-autofilled
form.
waltercacau@chromium.org
Autofill form events for address forms. These are recorded when the user
interacts with a form requesting an address.
Important caveat about submission metrics: - Submission using autofill data
is determined by simply evaluating if there was a fill operation in this
page. So, if the user filled with local data, completed erased or modified
the data after and then submitted, we would only emit one "Submitted
with server suggestion filled (once)"; - The submission segmentation
works by checking what kind of data was last filled for this type of form in
the page load. So, if I user initially filled with local data and after that
filled with server, we will only emit "Submitted with server suggestion
filled (once)".
waltercacau@chromium.org
Autofill form events for credit card forms. These are recorded when the user
interacts with a form requesting a credit card.
Important caveat about submission metrics: - Submission using autofill data
is determined by simply evaluating if there was a fill operation in this
page. So, if the user filled with local data, completed erased or modified
the data after and then submitted, we would only emit one "Submitted
with server suggestion filled (once)"; - The submission segmentation
works by checking what kind of data was last filled for this type of form in
the page load. So, if I user initially filled with local data and after that
filled with server, we will only emit "Submitted with server suggestion
filled (once)".
isherman@chromium.org
Tracks whether Autofill is enabled on page load for a page containing forms.
isherman@chromium.org
Tracks whether Autofill is enabled when Chrome launches.
erikchen@chromium.org
When Chrome tries to access the user's Address Book, OSX presents a blocking
dialog which disrupts the user experience. A new Chrome feature has been
introduced wherein Chrome only shows this blocking dialog if the user
explicitly asked Chrome to access the user's Address Book. If a form's field
looks like it might support Autofill suggestions from the user's Address
Book and there are no other suggestions, Chrome shows an Autofill entry that
prompts the user to give Chrome access to the user's Address Book. This
histogram tracks the frequency that this Autofill entry is presented, and
the frequency that this Autofill entry is selected.
erikchen@chromium.org
This metric is emitted each time the user accepts an Autofill suggestion. It
records whether the result is from the Address Book.
erikchen@chromium.org
The amount of time spent accessing the OSX Address Book the first time after
Chrome was launched. If this time is larger than ~100ms, this it is likely
that the user was shown a blocking, modal dialog.
erikchen@chromium.org
After a Chrome is given access to the Mac Address Book, whether the Address
Book contained a Me card.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has an address that contained a street number and either a city or zip
code.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has an email.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has a name.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has a phone number.
erikchen@chromium.org
The number of times that the access Address Book prompt has been shown when
the user selects the prompt.
dvadym@chromium.org
gcasto@chromium.org
Tracks the increased load on the Autofill server if the restriction on
querying for password forms with fewer than 3 fields were omitted.
Deprecated as of 3/2011, replaced by Autofill.StoredProfileCount.
Please list the metric's owners. Add more owner tags as needed.
The number of Autofill address profiles a user has.
Deprecated as of 3/2011, replaced by Autofill.Quality.
Please list the metric's owners. Add more owner tags as needed.
The quality of the AutoFill implementation.
Deprecated as of 2/2014 (M35), replaced by Autofill.UserHappiness.
isherman@chromium.org
The quality of the Autofill implementation.
isherman@chromium.org
The quality of Autofill's heuristic field type detection.
isherman@chromium.org
The quality of Autofill's heuristic field type detection, broken down by the
specific field type. Fields with multiple possible types (based on the
stored Autofill data) are logged as having ambiguous type.
isherman@chromium.org
The overall quality of the Autofill field type predictions.
isherman@chromium.org
The overall quality of the Autofill field type predictions, broken down by
the specific field type. Fields with multiple possible types (based on the
stored Autofill data) are logged as having ambiguous type.
isherman@chromium.org
The quality of the Autofill server's field type detection.
isherman@chromium.org
The quality of the Autofill server's field type detection, broken down by
the specific field type. Fields with multiple possible types (based on the
stored Autofill data) are logged as having ambiguous type.
Please list the metric's owners. Add more owner tags as needed.
TBD.
Please list the metric's owners. Add more owner tags as needed.
TBD.
rouslan@chromium.org
Whether a credit card scan was completed or cancelled.
rouslan@chromium.org
How long a credit card took to scan.
estade@chromium.org
Usage of the "Scan card" control item.
Deprecated as of 6/2011, replaced by Autofill.ServerExperimentId.Query.
isherman@chromium.org
The experiment ID received in response to an Autofill server query.
Deprecated as of 2/2014 (M35).
isherman@chromium.org
The experiment ID received in response to an Autofill server query.
Deprecated as of 2/2014 (M35).
isherman@chromium.org
The experiment ID received at the time of an Autofill upload.
Deprecated as of 3/2011, replaced by Autofill.ServerQueryResponse.
Please list the metric's owners. Add more owner tags as needed.
The usefulness of AutoFill server information.
isherman@chromium.org
The usefulness of Autofill server information.
isherman@chromium.org
The number of Autofill addresses a user has stored, measured at launch time.
mathp@chromium.org
The number of Autofill addresses a user has stored, measured when an
autofillable form is submitted.
waltercacau@chromium.org
Duration of the interaction with the UnmaskPrompt since it was shown until
it was closed. This prompt is triggered when a user selects a masked card in
an autofill dropdown.
waltercacau@chromium.org
Events tracking the usage of the unmasking prompt. This prompt is triggered
when a user selects a masked card in a autofill dropdown.
waltercacau@chromium.org
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.
waltercacau@chromium.org
Tracks the result of the GetRealPan API call. This API call is triggered by
the unmasking prompt when the user types information to verify his ownership
of the card being fetched.
waltercacau@chromium.org
Time the user waited before abandoning an unmasking operation. In such a
scenario, the user is cancelling a pending unmasking operation (possibly
because it is taking too long). The time measured here corresponds to the
time between the user clicking the "Verify" button and then
clicking "Cancel".
waltercacau@chromium.org
Duration between the user clicking the Verify button within the unmasking
prompt until we get a response back from the server. This prompt is
triggered when a user selects a masked card in an autofill dropdown.
isherman@chromium.org
Measures the frequency of various events in the Autofill user interaction
flow. By comparing frequencies, we can compute several interesting
"user happiness" metrics.
gab@chromium.org
Logged during BackgroundModeManager's initialization. Indicates the
AutoLaunchState the current browser process was launched in.
gab@chromium.org
Logged during BackgroundModeManager's initialization. Indicates the state of
the kBackgroundModeEnabled pref on startup.
timvolodine@chromium.org
Number of batteries reported by the UPower service on Linux at the start of
the Battery Status API.
timvolodine@chromium.org
Number of internal batteries reported by MacOS at the start of the Battery
Status API.
timvolodine@chromium.org
Number of batteries reported by Windows at the start of the Battery Status
API.
timvolodine@chromium.org
Whether the Battery Status API was successfully started up on Android.
csharp@chromium.org
Records the name hashes of all the dlls that are blocked from the browser
process.
csharp@chromium.org
Counts the number of times a renderer process is started with the browser
blacklist patch. This should never be hit.
csharp@chromium.org
krstnmnlsn@chromium.org
Records the number of attempts needed before the blacklist is properly set
up. This is logged immediately after a successful setup.
csharp@chromium.org
Records the successes and failures when running the browser blacklist setup
code. Used to determine if the blacklist is working as intended during
startup (since the blacklist runs before crash reporting is set up). This
only occurs on Windows.
oysteine@chromium.org
Records user observation and interaction with Media HTML elements that
feature autoplay, either script-controlled or through the attribute.
haraken@chromium.org
Duration of time taken to run Heap::collectGarbage().
haraken@chromium.org
The committed memory size in Blink GC. The value is reported when we see the
highest memory usage we've ever seen in the renderer process.
haraken@chromium.org
Duration of time taken to run ThreadState::completeSweep().
haraken@chromium.org
A type of Blink GC.
Removed at 2014 Jan.
haraken@chromium.org
Duration of time taken to run ThreadState::performPendingSweep().
haraken@chromium.org
The total size of allocated space in OS when a Blink GC is triggered.
haraken@chromium.org
The total size of object space in all threads when a Blink GC is triggered.
keybuk@chromium.org
Counts the number of simulataneously connected Bluetooth devices. Used to
direct testing efforts, and by our UI team to determine appropriate UI
sizes.
keybuk@chromium.org
Records the method used to pair each Bluetooth Device. Used to direct our
testing efforts.
keybuk@chromium.org
Records the result of pairing each Bluetooth Device. Used to understand
whether we are having significant problems with Bluetooth pairing and seeing
errors more commonly than we should.
yfriedman@chromium.org
Logs the depth of the bookmark in the bookmark tree hiearchy every time a
bookmark is launched. Depth indicates how many levels below a permanent
bookmark folder the bookmark was found in (e.g. a bookmark immediately in
the bookmark bar has depth 1).
wfh@chromium.org
Count of renderer process crashes grouped by type.
wfh@chromium.org
Count of renderer process kills grouped by type.
wfh@chromium.org
Count of renderer process crashes that we miscounted because we took the
exit code too early. Grouped by type.
Please list the metric's owners. Add more owner tags as needed.
Records the context type names used to create canvas rendering contexts.
cpu@chromium.org
Tracks the component updater steps for the Chrome Crash Service.
meacer@chromium.org
Records the result of a captive portal probe.
alemate@chromium.org
Count of displayed and not displayed due to errors notifications about
captive portal.
alemate@chromium.org
Count of clicked, closed and ignored captive portal notifications.
alemate@chromium.org
Duration of the captive portal detection process for a particular network at
OOBE. Detection duration is recorded each time portal detection is completed
for an active network.
alemate@chromium.org
The result of captive portal detection attempts performed at OOBE. Detection
result is recorded when portal detection is completed for an active network
and when it differs from the previous result for the same network.
alemate@chromium.org
The result of captive portal detection attempts at OOBE if it diverges from
network manager results. Detection result is recorded each time portal
detection is completed for an active network.
alemate@chromium.org
Number of milliseconds passed between consecutive reports for the same
network about portal and online states.
alemate@chromium.org
Number of milliseconds between start of request to gstatic.com/generate_204
and receipt of response with redirect to captive portal login page.
alemate@chromium.org
Duration of the captive portal detection process for a particular network in
user session. Detection duration is recorded each time portal detection is
completed for an active network.
alemate@chromium.org
The result of captive portal detection attempts performed in user session.
Detection result is recorded when portal detection is completed for an
active network and when it differs from the previous result for the same
network.
alemate@chromium.org
The result of captive portal detection attempts in session if it diverges
from network manager results. Detection result is recorded each time portal
detection is completed for an active network.
alemate@chromium.org
Number of milliseconds passed between consecutive reports for the same
network about portal and online states.
cast-analytics@google.com
Records the time the network has been down on a Cast device. Recorded when
network goes up.
cast-analytics@google.com
Records the time the network has been up on a Cast device. Recorded when
network goes down.
mfoltz@chromium.org
Records the number of times the cast button was shown to the user. The value
will be true if the button is enabled, and false if the button is disabled.
Note that depending on the current UX, it's possible that we hide the button
entirely if it's disabled, so it's possible for the false values to be 0.
mfoltz@chromium.org
Records the number of times the cast button was shown to the user when the
video is fullscreened. The value will only be recorded on entering
fullscreen. The value will be true if the button is enabled, and false if
the button is disabled. Note that depending on the current UX,it's possible
that we hide the button entirely if it's disabled, so it's possible for the
false values to be 0.
miguelg@chromium.org
Records the media type of every video being cast.
maybelle@chromium.org
miguelg@chromium.org
Records the result of a request to play remotely on a per player app basis
within Chrome for Android.
Deprecated 04/2014, and replaced by Cast.Sender.CastPlayerResult.
maybelle@chromium.org
miguelg@chromium.org
Records the result of a request to play remotely. The value will be true if
the playback succeeded, and false if there was an error.
mfoltz@chromium.org
Records the percentage of the video left at the time the remote playback is
stopped. This will be recorded when the playback is stopped by the user, or
when it's stopped by the cast device.
avayvod@google.com
Records the type of the remote playback device selected by the user. This
will be recorded when the user has chosen the device from the media route
chooser dialog.
posciak@chromium.org
Indicates whether initialization of a video encode accelerator for Cast
sender was successful.
cast-analytics@google.com
The latency between when a Cast V2 connection is established and the first
message is received on that connection. "Unknown" is the peer
type, which is not known at this point in the CastV2 connection
establishment. Naming conforms to the CastV2 sender-side histogram naming
convention "CastV2.[action].[name].[peer_type]".
cast-analytics@google.com
On accepting a Cast V2 transport socket connection, if an error is
encountered, the error code is logged here. "Unknown" is the peer
type, which is not known at this point in the CastV2 connection
establishment. "SslHandshake.Error" is the name of the action.
Naming conforms to the CastV2 sender-side histogram naming convention
"CastV2.[action].[name].[peer_type]".
cast-analytics@google.com
The time taken to do the handshake during Cast V2 transport socket creation.
"Unknown" is the peer type, which is not known at this point in
the CastV2 connection establishment. Naming conforms to the CastV2
sender-side histogram naming convention
"CastV2.[action].[name].[peer_type]".
Please list the metric's owners. Add more owner tags as needed.
The count of cellular device activation failures (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of cellular device activation tries (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of cellular reconnect failures during activation (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of cellular device reconnect tries during activation (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of successful cellular plan established (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of initiated cellular device setup starts (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of failed cellular plan setup tries (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of failed cellular plan purchases (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of successfully completed cellular plan purchases (Chrome OS).
Deprecated as of 8/2013. This histogram only considered the leaf certificate
expiry date as a proxy for whether a certificate was in-scope for the BRs,
but did not consider the issuance date. As some CAs have issued long-lived
certs prior to the BRs, this disproportionately reported those certs as
being subject to the BRs, but non-compliant, when in reality they're not
subject.
Please list the metric's owners. Add more owner tags as needed.
Information about the certificate algorithms and sizes in use on the web, to
examine compliance with the CA/Browser Forum requirements and security best
practice.
Please list the metric's owners. Add more owner tags as needed.
Information about the certificate algorithms and sizes in use on the web, to
examine compliance with the CA/Browser Forum requirements and security best
practice. This histogram considers the notBefore as the issuance date, for
purposes of what requirements apply.
jam@chromium.org
Count of child processes killed because they sent an IPC that couldn't be
deserialized.
Deprecated 3/2013. Renamed to ChildProcess.Crashed2.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes that we miscounted because we took the exit
code too early. Grouped by process type.
Deprecated 10/2011. Renamed to ChildProcess.Crashed.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes grouped by process type.
Deprecated 10/2011. Renamed to ChildProcess.CrashedWasAlive.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes that we miscounted because we took the exit
code too early. Grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes for which we were not able to understand the
exit code, grouped by process type.
Deprecated 3/2013. Renamed to ChildProcess.Disconnected2.
Please list the metric's owners. Add more owner tags as needed.
Count of child process abnormal channel disconnects grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Count of child process abnormal channel disconnects grouped by process type.
Deprecated 3/2013. Renamed to ChildProcess.DisconnectedAlive2.
Please list the metric's owners. Add more owner tags as needed.
Count of child process abnormal channel disconnects that are not classified
and reported because we took the exit code too early. Grouped by process
type.
Please list the metric's owners. Add more owner tags as needed.
Count of child process abnormal channel disconnects that are not classified
and reported because we took the exit code too early. Grouped by process
type.
wfh@chromium.org
Whether the browser command line had the switch --no-startup-window when a
child process crashed due to invalid sandbox state. Recorded when a child
process crashes if the exit code from the child process is
RESULT_CODE_INVALID_SANDBOX_STATE.
Deprecated 3/2013. Renamed to ChildProcess.Killed2.
Please list the metric's owners. Add more owner tags as needed.
Count of child process kills grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Count of child process kills grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Count of child processes killed by the extension API
(experimental.processes.terminate)
Please list the metric's owners. Add more owner tags as needed.
Count of child process kills that we miscounted because we took the exit
code too early. Grouped by process type.
Deprecated 10/2011. Renamed to ChildProcess.Killed.
Please list the metric's owners. Add more owner tags as needed.
Count of child process kills grouped by process type.
Deprecated 10/2011. Renamed to ChildProcess.KilledWasAlive.
Please list the metric's owners. Add more owner tags as needed.
Count of child process kills that we miscounted because we took the exit
code too early. Grouped by process type.
Please list the metric's owners. Add more owner tags as needed.
Indicates how many times each particular type of Activity was in the
foreground when a UMA session was terminated abnormally. UMA sessions last
as long as Chrome remains in the foreground.
Please list the metric's owners. Add more owner tags as needed.
Indicates how many times each particular type of Activity was brought to the
foreground when a UMA session was active (i.e. launched at some point). UMA
sessions last as long as Chrome remains in the foreground.
Please list the metric's owners. Add more owner tags as needed.
Indicates the execution phase the browser was in when the browser crashed.
Deprecated as of 11/2013.
Please list the metric's owners. Add more owner tags as needed.
Indicates the execution phase the browser was in when browser didn't exit
cleanly.
Deprecated as of 04/2015.
Please list the metric's owners. Add more owner tags as needed.
The total number of times the browser process has attempted to generate a
crash dump. This should be the sum of Chrome.BrowserDumpsWithCrash and
Chrome.BrowserDumpsWithNoCrash.
Deprecated as of 04/2015.
Please list the metric's owners. Add more owner tags as needed.
The number of times the browser process has attempted to generate a crash
dump because of an actual browser crash.
Deprecated as of 04/2015.
Please list the metric's owners. Add more owner tags as needed.
The number of times the browser process has attempted to generate a crash
dump in a non-crashing (i.e., reporting only) context.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The default search engine selected by a user not in the search engine dialog
experiment.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The default search engine selected by a user in the search engine dialog
experiment.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The default search engine selected by a user in slot 1 of a randomized
search engine dialog.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The default search engine selected by a user in slot 2 of a randomized
search engine dialog.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The default search engine selected by a user in slot 3 of a randomized
search engine dialog.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The default search engine selected by a user in slot 4 of a randomized
search engine dialog.
Please list the metric's owners. Add more owner tags as needed.
The actions to enable or disable services sending synced notifications.
Synced Notification Sending services can be individually disabled by the
user in the Chrome Notification center settings dialog.
xiaowenx@chromium.org
mukai@chromium.org
The name of the current color calibration of the display on ChromeOS. This
value is sent when the color calibration is changed by the user.
ginkage@chromium.org
Whether a user signed in using the new WebView-based GAIA flow. This value
is sent after the GAIA screen has completed user authentication.
zeuthen@chromium.org
The number of seconds of uptime since the last time the ChromeOS machine-id
was regenerated. This is reported every time the machine-id is regenerated
except for the first time since reboot.
zeuthen@chromium.org
The reason why the ChromeOS machine-id was regenerated. This is reported
when the machine-id is re-generated.
xdai@chromium.org
The memory pressure level in ChromeOS, which is recorded periodically (once
per second). This is used to show the relative frequency of the system being
in a critical vs relaxed memory pressure state.
dkrahn@chromium.org
Whether platform verification subsystem features are available at the time a
platform verification request is made for content protection on Chrome OS.
dkrahn@chromium.org
The result of a platform verification attempt for content protection on
Chrome OS.
bartfab@chromium.org
Whether a Chrome OS login via SAML used the principals API. This is recorded
during login on Chrome OS if SAML is being used for authentication.
bartfab@chromium.org
The number of passwords that were scraped during a Chrome OS login via SAML.
This is set only when the principals API is not used.
bartfab@chromium.org
Whether one of the scraped passwords was successfully verified as the user's
password. This is set only when the principals API is not used.
simonb@chromium.org
Whether relro sharing was attempted for the browser process, and if
attempted, whether it succeeded.
Deprecated 10/2014 in Issue 419010, and replaced by
ChromiumAndroidLinker.BrowserStates.
simonb@chromium.org
Is low memory device.
petrcermak@chromium.org
Whether the device supports loading a library directly from the APK file.
The functionality is checked and reported during every Chromium browser
process start up.
Deprecated 10/2014 in Issue 419010, and replaced by
ChromiumAndroidLinker.RendererStates.
simonb@chromium.org
Load at fixed address failed.
simonb@chromium.org
Whether relro sharing was attempted for a renderer process, and if
attempted, whether it succeeded.
Please list the metric's owners. Add more owner tags as needed.
The length of time between a dangerous download appearing on the downloads
shelf, and the "Discard" button being clicked.
Please list the metric's owners. Add more owner tags as needed.
The length of time between a dangerous download appearing on the downloads
shelf, and the "Dismiss" button being clicked.
Please list the metric's owners. Add more owner tags as needed.
The length of time between the external protocol dialog being shown and the
"Launch Application" button being clicked.
Please list the metric's owners. Add more owner tags as needed.
The length of time between a download appearing on the download shelf, and
the user opening it by clicking the item or pressing return.
Please list the metric's owners. Add more owner tags as needed.
Time between "Report and Discard" button being shown and it being
clicked.
Please list the metric's owners. Add more owner tags as needed.
The length of time between a dangerous download appearing on the download
shelf, and the "Keep" button being clicked.
Deprecated as of 4/2013, experiment confirmed correctness of our patch.
Please list the metric's owners. Add more owner tags as needed.
Counts how often the user writes or reads from the clipboard and whether the
write was from an incognito window or not.
pkotwicz@chromium.org
The length of time that it takes to transfer ownership of Chrome's CLIPBOARD
selection to the clipboard manager when Chrome exits.
vitalybuka@chromium.org
Event counts in CloudPrintAuth.
vitalybuka@chromium.org
The number of printers availible for registration.
vitalybuka@chromium.org
The number of printers availible for registration in Windows Service.
vitalybuka@chromium.org
Event counts in PrinterJobHandler.
vitalybuka@chromium.org
The number of jobs successfully completed per hour.
vitalybuka@chromium.org
The number of jobs started per hour.
vitalybuka@chromium.org
Then number of job completion statuses.
vitalybuka@chromium.org
Event counts in PrintSystem.
vitalybuka@chromium.org
The amount of time needed to prepare job for spooling.
vitalybuka@chromium.org
The number of printers user has blacklisted.
vitalybuka@chromium.org
The number of printers user has whitelisted.
vitalybuka@chromium.org
The amount of time needed to finish print job.
vitalybuka@chromium.org
Event counts in ServiceProcessControl.
vitalybuka@chromium.org
Temporarily histogram with size of IPC sockets in default location.
TODO(vitalybuka) Remove after investigation http://crbug.com/466644
vitalybuka@chromium.org
The amount of time used to fail to collect printer capabilities.
vitalybuka@chromium.org
The amount of time used to collect printer capabilities.
vitalybuka@chromium.org
The amount of time the utility process runs before disconnect.
vitalybuka@chromium.org
The amount of time used to fail to generate metafile.
vitalybuka@chromium.org
The amount of time used to generate metafile.
vitalybuka@chromium.org
Event counts in ServiceUtilityProcessHost.
vitalybuka@chromium.org
The amount of time needed to spool print job.
vitalybuka@chromium.org
The number of printers to unregister.
vitalybuka@chromium.org
The amount of data downloaded on cloud print request.
vitalybuka@chromium.org
The amount of time needed for cloud print request.
vitalybuka@chromium.org
Request counts to cloud print service.
vitalybuka@chromium.org
The number of retries used to complete cloud print request.
vitalybuka@chromium.org
The amount of data uploaded with cloud print request.
vitalybuka@chromium.org
Number of tries before successful ping. 99 means giving up.
Please list the metric's owners. Add more owner tags as needed.
The turn around time taken for the async readback of pixels is measured
here.
Please list the metric's owners. Add more owner tags as needed.
The time taken for the sync readback of pixels is measured here.
dneto@chromium.org
The number of layers in the active tree for each compositor frame. This is
logged once per frame, before the frame is drawn.
paint-dev@chromium.org
Total estimated memory used by SkPictures in the layer tree, in kilobytes.
Recorded once per frame, before the frame is drawn.
weiliangc@chromium.org.
Keeps track of number of incomplete tiles in a drawn compositor frame while
scrolling. This is a rough measurement of ugliness during user interaction.
Incomplete tiles are non ideal scaled. A sample is recorded everytime a
frame is drawn while a scroll is in progress. Tracking bug 381695.
weiliangc@chromium.org.
Keeps track of number of missing tiles in a drawn compositor frame while
scrolling. This is a rough measurement of ugliness during user interaction.
Incomplete tiles are checkerboard or solid color. A sample is recorded
everytime a frame is drawn while a scroll is in progress. Tracking bug
381695.
ebeach@google.com
Connectivity Diagnostics App: WiFi signal strength recorded during
NIC_SIGNAL_STRENGTH test.
The "Strength" property of a WiFi signal is a partially-reversible
function that linearly maps the RSSI range -120dBm to -20dBm to Strength
values from 0 to 100.
ebeach@google.com
HTTP latency seen by the Connectivity Diagnostics.
HTTP latency is computed using the chrome.socket API to make an HTTP GET
request to the /generate_204 page of three randomly generated Google
hostnames (*-ccd-testing-v4.metric.gstatic.com). The time taken from issuing
the HTTP request to receiving a response is clocked in JavaScript and the
arithmetic mean of the three times is used as the HTTP latency.
ebeach@google.com
Resolution latency seen by the Connectivity Diagnostics.
Resolver latency is computed by using the chrome.dns API to query three
randomly generated Google hostnames (*-ccd-testing-v4.metric.gstatic.com).
The random hostnames guarantees that there will be no caching of DNS
hostnames. The time taken from issuing the DNS request to receiving a
response is clocked in JavaScript and the arithmetic mean of the three times
is used as the resolver latency.
ebeach@google.com
Connectivity Diagnostics App: Outcome of the connectivity tests.
ebeach@google.com
Connectivity Diagnostics App: Amount of time taken to run each of the
connectivity tests.
toyoshim@chromium.org
The default cookies setting at profile open.
Deprecated 07/2014 since it is not referenced anywhere in the code.
toyoshim@chromium.org
The default handler setting at profile open.
toyoshim@chromium.org
The default image setting at profile open.
toyoshim@chromium.org
The default JavaScript setting at profile open.
toyoshim@chromium.org
The default location setting at profile open.
toyoshim@chromium.org
The default MediaStream setting at profile open.
toyoshim@chromium.org
The default MIDI permission setting on sysex (system exclusive) messages at
profile open.
toyoshim@chromium.org
The default mouse cursor setting at profile open.
toyoshim@chromium.org
The default notification setting at profile open.
toyoshim@chromium.org
The default plugins setting at profile open.
toyoshim@chromium.org
The default popups setting at profile open.
miguelg@chromium.org
The default permission setting for push messages at profile open.
scheib@chromium.org
Numer of results of parsing WebsiteSettingsHandler::last_setting_ success or
failure in WebsiteSettingsHandler methods.
lgarron@chromium.org
Tracks whether the mixed content shield was shown, and how the user
interacted with it.
miguelg@chromium.org
Tracks whether a permission was granted, rejected, etc. The suffix of the
histogram indicates which particular permission.
miguelg@chromium.org
Tracks whether a permission was granted, rejected, etc on an insecure
origin. The suffix of the histogram indicates which particular permission.
miguelg@chromium.org
Tracks whether a permission was granted, rejected, etc on a secure origin.
The suffix of the histogram indicates which particular permission.
miguelg@chromium.org
Number of times a given permission was requested.
miguelg@chromium.org
Number of times a given permission was requested from an insecure origin.
miguelg@chromium.org
Number of times a given permission was requested from a secure origin.
Please list the metric's owners. Add more owner tags as needed.
Whether or not updates to the backing store succeeded or failed, recorded
every update.
Please list the metric's owners. Add more owner tags as needed.
Intervals between access time updates for each cookie.
tnagel@chromium.org
Records the detection of a corrupted meta table. See http://crbug.com/111376
.
Please list the metric's owners. Add more owner tags as needed.
Records a failure to recover a corrupted meta table. See
http://crbug.com/111376 .
battre@chromium.org
Number of cookies in the store (recorded every 10 minutes of active browsing
time)
dmikurube@chromium.org
The size, on disk, of the cookie database as it is being loaded.
Please list the metric's owners. Add more owner tags as needed.
For each cookie removed from the store, the reason it was removed.
Please list the metric's owners. Add more owner tags as needed.
For each domain, number of cookies in that domain (recorded every 10 minutes
of active browsing time).
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of subdomains in that top level domain
(recorded every 10 minutes of active browsing time).
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of cookies in that domain (recorded every
10 minutes of active browsing time).
Please list the metric's owners. Add more owner tags as needed.
For each evicted (not expired) cookie, the amount of time since it was last
used
battre@chromium.org
Number of minutes until cookie expires when set.
Please list the metric's owners. Add more owner tags as needed.
Whether killing the database because it was corrupted beyond repair
succeeded.
Please list the metric's owners. Add more owner tags as needed.
This histogram records the total number of cookies loaded from disk,
including any cookies that are discarded during loading (for whatever
reason).
Deprecated as of 9/2013. Experiment to measure control characters in cookies
is finished.
Please list the metric's owners. Add more owner tags as needed.
When parsing a cookie, indicates if control characters were present in any
of the cookie values and if any of the cookie values were invalid.
Specifically, checks that all of the parsed values are valid according to
the valid token definition in Section 2.2 of RFC2616 which specifies a token
must have no separators (i.e. no characters from the following string,
ignoring the starting and ending single quote: '()<>@,;:\"/[]?={}
\t') and no control characters.
erikwright@chromium.org
This histogram records the total duration of time during which at least one
web request was blocked waiting for the cookie store to load. If no requests
were affected, the value is 0. If two requests are simultaneously blocked
for 1 second, the value is 1 second. If two requests are consecutively
blocked for 1 second each, the value is two seconds.
erikwright@chromium.org
The number of distinct Effective Top-Level Domains Plus One (ETLD+1, i.e.,
google.com, bbc.co.uk) for which a priority cookie load occurred.
Please list the metric's owners. Add more owner tags as needed.
The duration in seconds between a cookie getting evicted (due to the number
of cookies exceeding a domain limit), and subsequently reinstated.
Deprecated as of 9/2013. Experiment to measure control characters in cookies
is finished.
Please list the metric's owners. Add more owner tags as needed.
Indicates whether a cookie attribute pair was set with both a valid key and
a valid attribute value or not. For the key, this implies that it was a
valid token as defined in Section 2.2 of RFC2616 which specifies a token
must have no separators (i.e. no characters from the following string,
ignoring the starting and ending single quote: '()<>@,;:\"/[]?={}
\t') and no control characters. For the value, this implies that it
contained no control characters and no semicolon.
Deprecated as of 9/2013. Experiment to measure control characters in cookies
is finished.
Please list the metric's owners. Add more owner tags as needed.
Indicates whether a cookie name was set with a valid token. A valid token is
defined in Section 2.2 of RFC2616 which specifies a token must have no
separators (i.e. no characters from the following string, ignoring the
starting and ending single quote: '()<>@,;:\"/[]?={} \t') and no
control characters.
Deprecated as of 9/2013. Experiment to measure control characters in cookies
is finished.
Please list the metric's owners. Add more owner tags as needed.
Indicates whether a cookie value was valid or invalid when there was an
attempt to set it, where a valid value is defined in RFC 6265 as ASCII
characters excluding controls, whitspace, comma, semicolon, and backslash.
erikchen@chromium.org
The number of session cookies deleted on shutdown. This metric is emitted
even if no cookies are deleted.
erikchen@chromium.org
The amount of time required to delete session cookies on shutdown. This
metric is emitted even if no cookies are deleted.
erikchen@chromium.org
The number of session cookies deleted on startup. This metric is emitted
even if no cookies are deleted. This metric is not emitted if session
cookies are restored, rather than deleted on startup.
erikchen@chromium.org
The amount of time required to delete session cookies on startup. This
metric is emitted even if no cookies are deleted. This metric is not emitted
if session cookies are restored, rather than deleted on startup.
erikwright@chromium.org
The amount of time (ms) between the cookie store load starting and
completing.
Deprecated as of 04/2015. The migration has finished for most users.
erikwright@chromium.org
The amount of time (ms) to migrate a v4 database to v5.
Deprecated as of 04/2015. The migration has finished for most users.
erikwright@chromium.org
The amount of time (ms) to migrate a v5 database to v6.
Deprecated as of 04/2015. The migration has finished for most users.
erikwright@chromium.org
The amount of time (ms) to migrate a v6 database to v7.
Deprecated as of 04/2015. The migration has finished for most users.
erikwright@chromium.org
The amount of time (ms) to migrate a v7 database to v8.
erikchen@chromium.org
The amount of time (ms) to migrate a v8 database to v9.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
The amount of time (ms) to get cookies for each URL request.
nyquist@chromium.org
The amount of time (ms) to initialize the cookies database.
nyquist@chromium.org
The amount of time (ms) to read and parse the domain map from the cookies
database.
erikwright@chromium.org
This histogram records the wall-clock delay between a priority load task
being posted to the DB-thread and its execution.
erikchen@chromium.org
This histogram records the the total amount of time spent fetching the
cookies associated with an eTLD+1 from disk, including time spent waiting in
task queues.
erikwright@chromium.org
This histogram records the sum of the durations of all initial tasks loading
cookies from the database.
erikchen@chromium.org
This histogram records the wall-clock delay between the Load task being
posted to the DB-thread and its execution.
nyquist@chromium.org
The amount of time (ms) to read the domain map from the cookies database.
nyquist@chromium.org
The amount of time (ms) to parse the domains already loaded from the cookies
database and put them in the domain map.
mkwst@chromium.org
For each cookie added to the store, record it's type(s).
hychao@chromium.org
The longest additional time CRAS(Chrome OS audio server) ever waits for a
stream exceeding the timeout threshold. This value is recorded per stream
when it gets removed and used to investigate the audio glitch/skip problem
on Chrome OS.
wfh@chromium.org
The exit codes for crashed extension processes.
wfh@chromium.org
The exit codes for crashed renderer processes.
erikwright@chromium.org
siggi@chromium.org
Reports the result of an attempt to report a crash dump via Breakpad.
Success indicates only that the out-of-process crash reporter succesfully
generated a dump. The success or failure of the eventual upload is not
measured. This stability metric is logged from the first Chrome launch
post-dump.
erikwright@chromium.org
siggi@chromium.org
Reports the result of an attempt to report a dump via Breakpad without
crashing. Success indicates only that the out-of-process crash reporter
succesfully generated a dump. The success or failure of the eventual upload
is not measured. This stability metric is logged from the first Chrome
launch post-dump.
olivierrobin@chromium.org
pkl@chromium.org
Time delta between when the crash took place and when the crash was uploaded
by the app as a background task. Only logged on iOS.
olivierrobin@chromium.org
pkl@chromium.org
The number of crash reports present when the app wakes up as a background
task to upload crash reports. Only logged on iOS.
erikwright@chromium.org
Counts crash reports that the Kasko crash reporter fails to upload and hands
off to Chrome. Kasko stores the failed reports in a location specified by
Chrome. Chrome records this metric when it detects new minidump files in
that location. Currently the reports are discarded, but they could
eventually be uploaded via the Chrome network stack.
Deprecated as of 12/2013. Default pinned apps trial is finished.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS shelf clicks.
benchan@chromium.org
The type of archive file that Chrome OS cros-disks daemon is requested to
mount.
benchan@chromium.org
The media type of removable device that Chrome OS cros-disks daemon is
requested to mount.
benchan@chromium.org
The type of file system that Chrome OS cros-disks daemon is requested to
mount.
dzhioev@chromium.org
Records the number of times when first-run dialog was shown.
dzhioev@chromium.org
Index of furthest step that was reached during tutorial. Since order of
steps could change eventially and new steps could apear we use index here
instead of step name.
dzhioev@chromium.org
The total time that user spent on first-run tutorial.
dzhioev@chromium.org
The time that user spent on some step of tutorial.
dzhioev@chromium.org
Tracks the way how user left tutorial.
dzhioev@chromium.org
Records the number of times when first-run tutorial has been launched.
dkrahn@chromium.org
Cryptohome errors.
dkrahn@chromium.org
The amount of time (ms) for Chrome OS cryptohome daemon to initialize the
PKCS#11. Initializations under 1 second represent checks on a previously
initialized PKCS#11, and should be discarded for analysis.
dkrahn@chromium.org
The amount of time (ms) for Chrome OS cryptohome to mount the encrypted home
directory asynchronously.
dkrahn@chromium.org
The amount of time (ms) for Chrome OS cryptohome to mount the encrypted
guest home directory asynchronously.
dkrahn@chromium.org
The amount of time (ms) for Chrome OS cryptohome to mount the encrypted
guest home directory synchronously.
dkrahn@chromium.org
The amount of time (ms) for Chrome OS cryptohome to mount the encrypted home
directory synchronously.
dkrahn@chromium.org
The amount of time (ms) for Chrome OS cryptohome daemon to take ownership of
the TPM.
bengr@chromium.org
marq@chromium.org
megjablon@chromium.org
Counts various events that trigger Chrome to block the fallback
configuration of the data reduction proxy.
bengr@chromium.org
marq@chromium.org
megjablon@chromium.org
Counts various events that trigger Chrome to block the primary configuration
of the data reduction proxy.
bengr@chromium.org
megjablon@chromium.org
Counts the response bytes that did not go through the data reduction proxy
as the result of a bypass event.
bengr@chromium.org
megjablon@chromium.org
Counts the response bytes that went through the data reduction proxy and
were not bypassed.
Deprecated as of 6/2014, replaced by DataReductionProxy.BypassTypeFallback.
bengr@chromium.org
marq@chromium.org
Counts various events that trigger Chrome to bypass the fallback
configuration of the data reduction proxy.
Deprecated as of 6/2014, replaced by DataReductionProxy.BypassTypePrimary.
bengr@chromium.org
marq@chromium.org
Counts various events that trigger Chrome to bypass the primary
configuration of the data reduction proxy.
bengr@chromium.org
Positive net error code that caused the fallback data reduction proxy to be
bypassed and put on the proxy retry list. Called after a failure to connect
or resolve a host name.
bengr@chromium.org
Positive net error code that caused the primary data reduction proxy to be
bypassed and put on the proxy retry list. Called after a failure to connect
or resolve a host name.
bengr@chromium.org
marq@chromium.org
megjablon@chromium.org
Counts various events that trigger Chrome to bypass the fallback
configuration of the data reduction proxy.
bengr@chromium.org
marq@chromium.org
megjablon@chromium.org
Counts various events that trigger Chrome to bypass the primary
configuration of the data reduction proxy.
jeremyim@chromium.org
bengr@chromium.org
Size of the response body. This is the actual number of bytes received,
which usually agrees with but is not necessarily the same as the size
specified by the Content-Length header. Only recorded if the request is sent
while a simulated Data Reduction Proxy configuration fetch is taking place.
jeremyim@chromium.org
bengr@chromium.org
The difference between the size specified in the X-Original-Content-Length
header and the size of the response body. Only recorded if the request is
sent while a simulated Data Reduction Proxy configuration fetch is taking
place. Only positive values are logged, so if X-Original-Content-Length is
not specified or if it equals or exceeds the content length, it is not
logged.
jeremyim@chromium.org
bengr@chromium.org
Size specified in the X-Original-Content-Length header. If this header is
not present in the response, the size of the response body is used. Only
recorded if the request is sent while a simulated Data Reduction Proxy
configuration fetch is taking place.
jeremyim@chromium.org
bengr@chromium.org
The number of failed attempts when retrieving the configuration from the
Data Reduction Proxy API before a successful attempt took place.
jeremyim@chromium.org
bengr@chromium.org
Time from when the Data Reduction Proxy configuration request starts until
it completes.
jeremyim@chromium.org
bengr@chromium.org
Count per HttpResponseCode when attempting to retrieve the Data Reduction
Proxy configuration from the Data Reduction Proxy API.
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTP responses that have been checked
for tampering. This assumes the data reduction proxy injected fingerprints
have not been tampered with. Only the data reduction proxy responses with
200 OK response code are checked.
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTPS responses that have been checked
for tampering. This assumes the data reduction proxy injected fingerprints
have not been tampered with. Only the data reduction proxy responses with
200 OK response code are checked.
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTP responses that passed the tamper
detection. This assumes the data reduction proxy injected fingerprints have
not been tampered with. Only the data reduction proxy responses with 200 OK
response code are checked.
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTPs responses that passed the tamper
detection. This assumes the data reduction proxy injected fingerprints have
not been tampered with. Only the data reduction proxy responses with 200 OK
response code are checked.
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
The total number of HTTP responses that some part (specified by suffix name)
have been tampered with. This assumes the data reduction proxy injected
fingerprints have not been tampered with. Only the data reduction proxy
responses with 200 OK response code are checked.
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
The total number of HTTPS responses that some part (specified by suffix
name) have been tampered with. This assumes the data reduction proxy
injected fingerprints have not been tampered with. Only the data reduction
proxy responses with 200 OK response code are checked.
bengr@chromium.org
sclittle@chromium.org
Counts the response bytes of responses that Chrome expected to come through
a data reduction proxy and have the data reduction proxy via header, but
where the data reduction proxy via header was missing. Note that this does
not include responses that were bypassed.
bengr@chromium.org
sclittle@chromium.org
Counts the different HTTP response codes of responses that Chrome expected
to come through a data reduction proxy and have the data reduction proxy via
header, but where the data reduction proxy via header was missing.
bengr@chromium.org
megjablon@chromium.org
Counts the number of times various events occur when the data reduction
proxy is enabled and the IP address of the client changes.
bengr@chromium.org
marq@chromium.org
Counts various outcomes of requesting the data reduction proxy's probe URL.
bengr@chromium.org
megjablon@chromium.org
Reports the type of network error when the data reduction proxy probe fails
due to a network error.
Deprecated as of 3/2015, replaced by DataReductionProxy.UIAction.
bengr@chromium.org
marq@chromium.org
Samples which method was used by the user to dismiss the proxy promo. This
is sampled when the promo leaves view, with the sampled value depending on
which of four possible controls the user used.
sclittle@chromium.org
Records the result of migrating the Data Reduction Proxy away from being
configured via a proxy preference, including cases when no migration action
was taken.
sclittle@chromium.org
bengr@chromium.org
Reports the different network errors that requests that try to use the data
reduction proxy are completing with, including OK and ABORTED.
sclittle@chromium.org
bengr@chromium.org
Reports the different network errors that main frame resource requests that
try to use the data reduction proxy are completing with, including OK and
ABORTED.
sclittle@chromium.org
bengr@chromium.org
Reports the state of the proxy server field in the response seen by the Data
Reduction Proxy bypass logic.
jeremyim@chromium.org
bengr@chromium.org
Time from when the Data Reduction Proxy secure proxy check starts until it
completes.
Deprecated as of 3/2015, replaced by DataReductionProxy.UIAction.
bengr@chromium.org
marq@chromium.org
Samples of user interactions with the ON/OFF switch in the settings menu for
reducing data usage. Only the setting changes between entering the reducing
data usage setting menu and leaving the menu will be sampled. So if a user
enters the menu with OFF and leaves it with OFF, it is counted as one OFF to
OFF conversion regardless of how many times he or she toggles the ON/OFF
switch.
bengr@chromium.org
marq@chromium.org
Samples of the state of the data reduction proxy on Chrome startup. The
proxy will either be unavailable (the feature hasn't been rolled out to this
user yet), not enabled (the feature is available but the user doesn't have
it turned on), or enabled (the feature is enabled and turned on).
bengr@chromium.org
megjablon@chromium.org
Samples of user interactions with the promo and settings menu. All samples
are mutually exclusive. These samples include:
The user interactions with the promo. On Android, there are three actions
that dismiss the promo (enable, dismiss, and learn more) and on iOS there is
a toggle to enable the proxy. This is sampled when the promo leaves view. If
the user clicks the link to the settings menu, the state of the ON/OFF
switch in the menu is sampled when the view is exited.
Any other user interaction with the the ON/OFF switch in the settings menu
for reducing data usage. Only the setting changes between entering the
reducing data usage setting menu and leaving the menu will be sampled
regardless of how many times he or she toggles the ON/OFF switch. Other
samples that report ON/OFF settings menu changes are not also reported here.
sergeyv@chromium.org
vsevik@chromium.org
pfeldman@chromium.org
Specified DevTools action has been taken.
sergeyv@chromium.org
vsevik@chromium.org
pfeldman@chromium.org
Time to load Developer Tools when user clicks Inspect Element in the context
menu.
sergeyv@chromium.org
vsevik@chromium.org
pfeldman@chromium.org
Specified DevTools panel was shown.
sergeyv@chromium.org
vsevik@chromium.org
pfeldman@chromium.org
Specified DevTools setting was changed.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the DiskSpace recovery step that runs
on recovery startups. The recovery step attempts to guarantee the DiskSpace
test, which checks that the disk space in the volume where the user data
directory normally lives is not dangerously low, would pass on the next
startup.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the JSONBookmarks recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
JSONBookmarks test, which makes sure that the JSON-encoded Bookmarks file is
properly formed, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the JSONLocalState recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
JSONLocalState test, which makes sure that the JSON-encoded Local State file
is properly formed, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the JSONPreferences recovery step
that runs on recovery startups. The recovery step attempts to guarantee the
JSONPreferences test, which makes sure that the JSON-encoded Preferences
file is properly formed, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathDictionaries recovery step
that runs on recovery startups. The recovery step attempts to guarantee the
PathDictionaries test, which makes sure that the path to the Dictionaries
directory exists and has the right permissions, would pass on the next
startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathLocalState recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
PathLocalState test, which makes sure that the path to the Local State file
exists and has the right permissions, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathResources recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
PathResources test, which makes sure that the path to the Resources
directory exists and has the right permissions, would pass on the next
startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathUserData recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
PathUserData test, which makes sure that the path to the User Data directory
exists and has the right permissions, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityAppCache recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityAppCache test, which checks the integrity of
the App Cache database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityArchivedHistory
recovery step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityArchivedHistory test, which checks the
integrity of the Archived History database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityCookie recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityCookie test, which checks the integrity of the
Cookie database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker
recovery step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityDatabaseTracker test, which checks the
integrity of the Database Tracker database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityHistory recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityHistory test, which checks the integrity of the
History database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSCert recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityNSSCert test, which checks the integrity of the
NSS Certificate database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSKey recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityNSSKey test, which checks the integrity of the
NSS Key database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityThumbnails
recovery step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityThumbnails test, which checks the integrity of
the Thumbnails database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityWebData recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityWebData test, which checks the integrity of the
Web Data database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Count of the number of times diagnostics recovery is invoked or not, and how
it was invoked. A sample is added to this histogram once for each startup
of Chrome.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the DiskSpace test
that runs on recovery startups. The DiskSpace test checks that the disk
space in the volume where the user data directory normally lives is not
dangerously low.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the JSONBookmarks
test that runs on recovery startups. The JSONBookmarks test checks to make
sure that the JSON encoded bookmarks file is properly formed.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the JSONLocalState
test that runs on recovery startups. The JSONLocalState test checks to make
sure that the JSON encoded Local State file is properly formed.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the JSONPreferences
test that runs on recovery startups. The JSONPreferences test checks to
make sure that the Preferences file is properly formed.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathDictionaries
test that runs on recovery startups. The PathDictionaries test checks makes
sure that the path to the Dictionaries folder exists and has the right
permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathLocalState
test that runs on recovery startups. The PathLocalState test checks makes
sure that the path to the Local State folder exists and has the right
permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathResources
test that runs on recovery startups. The PathResources test checks makes
sure that the path to the Resources folder exists and has the right
permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathUserData test
that runs on recovery startups. The PathUserData test checks makes sure that
the path to the User Data folder exists and has the right permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityAppCache test that
runs on recovery startups. The test checks the integrity of the App Cache
database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityArchivedHistory
test that runs on recovery startups. The test checks the integrity of the
Archived History database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityCookie test that
runs on recovery startups. The test checks the integrity of the Cookie
database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker
test that runs on recovery startups. The test checks the integrity of the
Database Tracker database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityHistory test that
runs on recovery startups. The test checks the integrity of the History
database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSCert test that
runs on recovery startups. The test checks the integrity of the NSS
Certificate database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSKey test that
runs on recovery startups. The test checks the integrity of the NSS Key
database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityThumbnails test
that runs on recovery startups. The test checks the integrity of the
Thumbnails database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityWebData test that
runs on recovery startups. The test checks the integrity of the Web Data
database.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Histogram comparing the various types of diagnostic test failures when
diagnostic tests are run. Note that some types of test failures cause the
rest of the tests to be skipped.
shrikant@chromium.org
Reports size of font cache file. This is reported every time we rebuild font
cache.
shrikant@chromium.org
Reports the total number of fonts that will be ignored while building static
font cache due to size limitation. During cache building phase if our logic
suggests that we need to put more than 70% of font file contents into cache
file then we don't cache that particular font file. These ignored font files
are directly picked up from system fonts folder during Direct Write cache
building process. Our end goal is to minimize costly open and close
operations on font files in system folder.
shrikant@chromium.org
Reports the total number of fonts that will be ignored while loading a
custom font collection. With current criteria fonts that are not in
system-font location will be ignored.
shrikant@chromium.org
Reports the total number of fonts to be loaded through a custom font
collection. This actually reports total font entries from registry excluding
font entries that point to non-system location.
shrikant@chromium.org
Measures the total time spent in loading a custom font collection in
non-cache-file mode. We load system fonts as a custom font collection to
avoid any interaction with windows font cache service from sandboxed
renderer process. Please note that windows font cache services is different
from our cache file approach (later referred here as cache-file mode).
shrikant@chromium.org
Measures the total time spent in loading a custom font collection in
cache-file mode. We load system fonts as a custom font collection to avoid
any interaction with windows font cache service from sandboxed renderer
process. Please note that windows font cache services is different from our
cache file approach (later referred here as cache-file mode)
Please list the metric's owners. Add more owner tags as needed.
Whether an extension has been wiped out.
Please list the metric's owners. Add more owner tags as needed.
How many external extensions get wiped out as a result of the Sideload
Wipeout one-time initiative.
Please list the metric's owners. Add more owner tags as needed.
Whether any extension got wiped out as a result of the Sideload Wipeout
one-time initiative.
Please list the metric's owners. Add more owner tags as needed.
The user selection in the Sideload Wipeout bubble, grouped by the
UmaWipeoutHistogramOptions enum.
brandonsalmon@chromium.org
Records information about DiskBasedCertCache operations with respect to
certificate chain positions. Zero indicates that a certificate is root, one
indicates that it is the first intermediate certificate, etc.
brandonsalmon@chromium.org
Records the outcome of requests to retrieve certificates from the disk
cache.
brandonsalmon@chromium.org
Whether or not the leaf certificate of a certificate chain was successfuly
read from the disk cache.
brandonsalmon@chromium.org
Whether or not the leaf certificate of a certificate chain was successfully
written to the disk cache.
brandonsalmon@chromium.org
Measures the wall clock time spent reading a certificate chain. The starting
time is when the read command is issued, and the ending time is when all of
the certificates in the chain have been read into memory.
brandonsalmon@chromium.org
Measures the wall clock time spent writing a certificate chain to disk. The
starting time is when the write command is issued, and the ending time is
when all the certificates in the chain have been written to disk.
rvargas@chromium.org
The age of the cache's files (wall time).
rvargas@chromium.org
The age of the cache's files (wall time). Media-specific cache.
Please list the metric's owners. Add more owner tags as needed.
The age of the cache's files (wall time). AppCache.
Please list the metric's owners. Add more owner tags as needed.
The age of the cache's files (wall time). ShaderCache.
rvargas@chromium.org
The size distribution of data stored in the HTTP cache.
Deprecated.
Please list the metric's owners. Add more owner tags as needed.
The total time it takes to perform a payload IO operation, for the regular
disk cache.
ttuttle@chromium.org
The attempt which completed after the job was already cancelled.
ttuttle@chromium.org
The attempt which completed after the job was already cancelled OR the
attempt that has finished after host resolution was already completed by an
earlier attempt.
ttuttle@chromium.org
Duration of time taken in OS resolutions for actual navigations. These
attempts which completed after the job was already canceled OR after the job
was already completed by an earlier attempt. Note that cached resolutions
may provide low (0ms?) resolution times.
ttuttle@chromium.org
The attempt that has not resolved the host successfully.
ttuttle@chromium.org
The attempt that resolved the host first and the resolution was not
successful.
ttuttle@chromium.org
The attempt that resolved the host first and the resolution was successful.
ttuttle@chromium.org
The attempt that has resolved the host successfully.
ttuttle@chromium.org
Duration of time taken in OS resolutions that succeeded and were requested
for actual navigations. These attempts which completed after the job was
already canceled OR after the job was already completed by an earlier
attempt. Note that cached resolutions may provide low (0ms?) resolution
times.
ttuttle@chromium.org
This histogram shows the time saved by having spawned an extra attempt, when
the first attempt didn't finish before retry attempt.
ttuttle@chromium.org
The time left to expiration of an entry when it is removed while compacting
the HostCache.
ttuttle@chromium.org
The time since expiration of an entry when it is removed while compacting
the HostCache.
ttuttle@chromium.org
The time since expiration of an entry when it is removed on lookup.
ttuttle@chromium.org
Error status when an empty address list was found in OnLookupComplete().
ttuttle@chromium.org
When either a pre-resolution was not done recently enough to provide
benefit, or the corresponding pre-resolution is still pending, this
histogram shows the duration of time used to resolve a hostname as not
existing during a failed attempt to navigate to (GET) a URL. In newer
versions, if the hostname has never been found as a link during a page scan,
and it has a referring URL, then it is added to referrer list data structure
(hoping we'll do better next time).
ttuttle@chromium.org
When either a pre-resolution was not done recently enough to provide
benefit, or the corresponding pre-resolution is still pending, this
histogram shows the duration of the duration of time used to resolve a
hostname to navigate to (GET) a URL. In newer versions, if the hostname has
never been found as a link during a page scan, and it has a referring URL,
then it is added to referrer list data structure (hoping we'll do better
next time).
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool).
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority HIGHEST when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority IDLE when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority LOW when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority LOWEST when started.
ttuttle@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority MEDIUM when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool).
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority HIGHEST when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority IDLE when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority LOW when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority LOWEST when started.
ttuttle@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority MEDIUM when started.
ttuttle@chromium.org
The duration of time used (most recently) to pre-resolve a hostname, when
the prefetched resolution was apparently evicted from the cache. The
included samples only list pre-resolution times when the later
navigations/fetches took in excess of 15ms.
ttuttle@chromium.org
The duration of time used (most recently) to pre-resolve a hostname, when
the prefetched resolution was apparently evicted from the cache. The
included samples only list pre-resolution times when the later
navigations/fetches took in excess of 15ms.
ttuttle@chromium.org
Replaced by DNS.PrefetchFoundNameL.
ttuttle@chromium.org
Deprecated 2/2010, and replaced by DNS.PrefetchResolution
The duration of time used by the DNS pre-resolving threads to resolve a host
name via the network. Any resolutions that are faster than 15ms are
considered to be local cache hits, not requiring network access, and are not
included in this histogram. This histogram is most useful for estimating the
typical cost of a name resolution, but it also estimates the total number of
network-based resolutions induced by this feature. Not all these
resolutions prove helpful (i.e., the user does not always actually visit the
resolved hostnames).
ttuttle@chromium.org
Replaced by DNS.PrefetchNegativeHitL.
ttuttle@chromium.org
The duration of time saved due to DNS pre-resolving in the "name not
found" case. Time "savings" shown in the histogram are
defined to be the difference between the DNS pre-resolution duration, and
the DNS resolution duration seen during a navigation. These cache hits only
list events where the DNS pre-resolve duration for a host was in excess of
15ms (i.e., the network was consulted), and the actual DNS resolution (when
a user attempted to navigate to a link with the same host name) took less
than 15ms (i.e., the network was not consulted), which means the gain was a
result of a "cache hit" in the OS cache. For some users with
LANs, all negative results (even when the DNS cache might otherwise help)
take about 2.5 seconds (due to timeouts for netbios broadcasts), and hence
no savings are possible (or shown) for such users in this category.
ttuttle@chromium.org
Replaced by DNS.PrefetchPositiveHitL.
ttuttle@chromium.org
The duration of time saved due to DNS pre-resolving in the "name was
found" case, and induced by either a page scan for a link or an omnibox
entry by the user. Time "savings" shown in the histogram are
defined to be the difference between the DNS pre-resolution duration, and
the DNS resolution duration seen during a navigation. These cache hits only
list events where the DNS pre-resolve duration for a host was in excess of
15ms (i.e., the network was consulted), and the actual DNS resolution (when
a user attempted to navigate to a link with the same host name) took less
than 15ms (i.e., the network was not consulted), which means the gain was a
result of a "cache hit" in the OS cache.
ttuttle@chromium.org
The duration of time spent by a proposed resolution waiting in the queue to
be resolved. This number is in addition to any DNS resolution time that may
come later.
ttuttle@chromium.org
The duration of time saved due to DNS pre-resolving in the "name was
found" case, and induced by predicting (using referrer lists) that a
resolution was needed. Time "savings" shown in the histogram are
defined to be the difference between the DNS pre-resolution duration, and
the DNS resolution duration seen during a navigation. These cache hits only
list events where the DNS pre-resolve duration for a host was in excess of
15ms (i.e., the network was consulted), and the actual DNS resolution (when
a user attempted to navigate to a link with the same host name) took less
than 15ms (i.e., the network was not consulted), which means the gain was a
result of a "cache hit" in the OS cache.
ttuttle@chromium.org
The duration of time used by the DNS pre-resolving threads to resolve a host
name via the network. Any resolutions that are faster than 15ms are
considered to be local cache hits, not requiring network access, and are not
included in this histogram. This histogram is most useful for estimating the
typical cost of a name resolution, but it also estimates the total number of
network-based resolutions induced by this feature. Not all these
resolutions prove helpful (i.e., the user does not always actually visit the
resolved hostnames).
ttuttle@chromium.org
When, due to congestion avoidance, a queued pre-resolution is abandoned
(recycled) without actually being resolved, this histograms records the age
in the queue of that entry. Only times over 2 seconds are recorded in this
histogram.
ttuttle@chromium.org
When, due to congestion avoidance, a queued pre-resolution is abandoned
(recycled) without actually being resolved, this histograms records the age
in the queue of that entry. Only times less than or equal to 2 seconds are
recorded in this histogram.
ttuttle@chromium.org
Counts of successes and failures of OS resolutions in various categories.
ttuttle@chromium.org
Duration of time taken in OS resolutions for actual navigations. Note that
cached OS resolutions may provide low (0ms?) resolution times.
ttuttle@chromium.org
Same as DNS.ResolveFail, but limited to pure IPv4 lookups.
ttuttle@chromium.org
Same as DNS.ResolveFail, but limited to pure IPv6 lookups.
ttuttle@chromium.org
Same as DNS.ResolveFail, but limited to IPv4/IPv6 lookups.
ttuttle@chromium.org
Duration of time taken in speculative OS resolutions. Note that cached OS
resolutions may provide low (0ms?) resolution times.
ttuttle@chromium.org
Duration of time taken in speculative OS resolution that succeeded. Note
that cached resolutions may provide low (0ms?) resolution times.
ttuttle@chromium.org
Duration of time taken in OS resolutions that succeeded and were requested
for actual navigations. Note that cached resolutions may provide low (0ms?)
resolution times.
ttuttle@chromium.org
Same as DNS.ResolveSuccess, but limited to pure IPv4 lookups.
ttuttle@chromium.org
Same as DNS.ResolveSuccess, but limited to pure IPv6 lookups.
ttuttle@chromium.org
Same as DNS.ResolveSuccess, but limited to IPv4/IPv6 lookups.
ttuttle@chromium.org
Deprecated as of 5/2013.
Counts of hits and misses in the DNS cache and DNS jobs pool of wasted
HostResolverImpl::Jobs that could be avoided by always resolving using
AF_UNSPEC.
ttuttle@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Excludes speculative requests.
ttuttle@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Speculative requests only.
ttuttle@chromium.org
In some cases, such as when content arrives with embedded references to
other servers, the prefetch system can't (or doesn't) attempt to pre-resolve
the hostnames. As an example, a visit to www.cnn.com will fetch content
with references to about 12 additional hostnames, none of which are
currently anticipated. Such resolutions are termed "Unexpected
Resolutions," and the durations associated with those DNS resolutions
are shown below. Future features may attempt to learn (from prior
experience locally, or from server provided hints), what secondary hostname
resolutions should be done when a primary resolution (or navigation) takes
place. This histogram shows what the potential savings are that
"remain on the table" until we employ some of these more advanced
features.
ttuttle@chromium.org
In some cases, such as when content arrives with embedded references to
other servers, or when a page (such as one in SSL) preclude scanning and
prefetching, the prefetch system can't (or doesn't) attempt to pre-resolve
the hostnames. As an example, a visit to www.cnn.com will fetch content
with references to about 12 additional hostnames, none of which might be
anticipated. Similarly, clicking on a link in an SSL page won't be
anticipated (since scanning in not allowed by default). Such resolutions are
termed "Unexpected Resolutions," and the durations associated with
those navigation induced DNS resolutions are shown below. If a referring
URL is available for the navigation, the relationship to the referring URL
was recorded, and future navigations to the referring hostname would have
induced a pre-resolution of hostname that caused an entry below. Such any
entry may facilitate future listing in the ReferredPositiveHit histogram.
ttuttle@chromium.org
Status of DNS probe updates sent to a DNS error page.
ttuttle@chromium.org
Renamed 7/2013 to DnsProbe.ProbeDuration.
Time between starting and finishing DNS probe.
ttuttle@chromium.org
Removed 7/2013.
Time between starting and finishing DNS probe when NCN says we're offline.
ttuttle@chromium.org
Removed 7/2013.
Result of DNS probes sent by the probe service when NCN says we're offline.
ttuttle@chromium.org
Removed 7/2013.
Time between starting and finishing DNS probe when NCN says we're online.
ttuttle@chromium.org
Removed 7/2013.
Result of DNS probes sent by the probe service when NCN says we're online.
ttuttle@chromium.org
Renamed 7/2013 to DnsProbe.ProbeResult. (Also switched to the full
DnsProbe.ProbeStatus enum.)
Result of DNS probes sent by the probe service.
ttuttle@chromium.org
Removed 7/2013.
Elapsed time of DNS probes that return PROBE_BAD_CONFIG.
ttuttle@chromium.org
Removed 7/2013.
Whether the only nameserver in the system DNS config was 127.0.0.1 when the
probe result was BAD_CONFIG.
ttuttle@chromium.org
Removed 7/2013.
The result of the system probe job when the overall probe result was
BAD_CONFIG.
ttuttle@chromium.org
Removed 7/2013.
The number of nameservers in the system DNS config when the probe result was
BAD_CONFIG.
ttuttle@chromium.org
Removed 7/2013.
Elapsed time of DNS probes that return PROBE_NO_INTERNET.
ttuttle@chromium.org
Removed 7/2013.
Elapsed time of DNS probes that return PROBE_NXDOMAIN.
ttuttle@chromium.org
Removed 7/2013.
Elapsed time of DNS probes that return PROBE_UNKNOWN.
ttuttle@chromium.org
Time between starting and finishing DNS probe.
ttuttle@chromium.org
Result of DNS probes sent by the probe service.
mariakhomenko@chromium.org
Recorded only for Android. Records on every metrics upload whether document
mode is enabled.
pstew@chromium.org
Chrome OS document scan metric that tracks whether a document scan call to
the image conversion process suceeded.
pstew@chromium.org
Chrome OS document scan metric that tracks whether a document scan call to
the sane backend process suceeded.
mattm@chromium.org
Number of certs loaded from domain bound cert database.
mattm@chromium.org
Time spent loading domain bound cert database.
mattm@chromium.org
The size, on disk, of the domain bound cert database as it is being loaded.
mattm@chromium.org
Time spent generating a domain bound cert.
mattm@chromium.org
Combined time for GetDomainBoundCert retrieval (both synchronous and
asynchronous).
mattm@chromium.org
Time for asynchronous retrieval (from the GetDomainBoundCert call until
completion callback is called).
mattm@chromium.org
Time for synchronous GetDomainBoundCert cert retrieval.
mattm@chromium.org
Result of GetDomainBoundCert function.
mattm@chromium.org
Whether the domain-bound certs sqlite database was killed succesfully when
an unrecoverable error was detected.
mattm@chromium.org
Counts of SSL client sockets broken down by support for Domain Bound
Certificates TLS extension. Counts only connections with full handshakes,
resumed sessions are not counted.
mattm@chromium.org
Longest time spent by requests waiting for load of domain bound cert
database.
mattm@chromium.org
Number of requests that waited for load of domain bound cert database.
ttuttle@chromium.org
Whether adding a beacon to a Domain Reliability context caused it to evict
an older beacon to stay within memory limits.
ttuttle@chromium.org
Whether a beacon added to a Domain Reliability context was saved to be
uploaded to the collector.
ttuttle@chromium.org
The Chrome error code included in a beacon saved to be uploaded to the
collector.
ttuttle@chromium.org
The index of the collector that a Domain Reliability upload was sent to.
(Later collectors are only used when earlier collectors have failed.)
ttuttle@chromium.org
After an upload to a collector finishes (successfully or not), the delay
before the scheduler can send another upload to that collector. (If recent
uploads were successful, this will be 0; if not, it will be based on the
BackoffEntry and any Retry-After header received.)
ttuttle@chromium.org
The elapsed time between starting and finishing a Domain Reliability upload.
ttuttle@chromium.org
Deprecated 11/2014; see UploadCollectorIndex
Whether a Domain Reliability upload was sent to a collector other than the
first one listed in the config. (This only happens when an upload to the
first collector fails.)
ttuttle@chromium.org
The time between successive Domain Reliability uploads being started in the
same context. (Can be arbitrarily long if no beacons are reported in a
while.)
ttuttle@chromium.org
The time from the first beacon in a Domain Reliability upload being recorded
and that upload completing successfully. (Note that if some beacons are
never uploaded successfully, they will not feature in this histogram at
all.)
ttuttle@chromium.org
The network error code (or OK if none) returned by the URLFetcher when a
Domain Reliability report is uploaded.
ttuttle@chromium.org
The HTTP response code returned by the Domain Reliability collector when a
report is uploaded.
ttuttle@chromium.org
Whether a Domain Reliability upload succeeded.
nyquist@chromium.org
Whether the perceived quality of the distillation of a web page was good.
cjhopman@chromium.org
Records the "Distillable Type" (not distillable, mobile-friendly
distillable, non-mobile-friendly distillable, etc) for each analyzed page.
cjhopman@chromium.org
Records the "Distillable Type" (not distillable, mobile-friendly
distillable, non-mobile-friendly distillable, etc) for each distilled page.
kuan@chromium.org
Records whether a page has distilled data.
nyquist@chromium.org
Records the number of words in a distilled page. For articles with multiple
pages, each page is counted separately.
yfriedman@chromium.org
Time spent in DomDistiller's identification of text content.
yfriedman@chromium.org
Complete time spent in DomDistiller's processing of a page.
wychen@chromium.org
Time spent in DistillPageImpl(), mostly ExecuteJavaScript(), including
compilation and execution.
yfriedman@chromium.org
Time spent in creating DomDistiller's internal representation of the HTML
document.
yfriedman@chromium.org
Time spent in DomDistiller's final processing of article content/formatting.
yfriedman@chromium.org
Time spent in DomDistiller's processing of article metadata.
Deprecated 2012.
michaeln@chromium.org
Duration to execute localStorage.clear() or sessionStorage.clear().
Deprecated 2012.
michaeln@chromium.org
Duration to execute localStorage.getItem() or sessionStorage.getItem().
Deprecated 2012.
michaeln@chromium.org
Duration to execute localStorage.key() or sessionStorage.key().
Deprecated 2012.
michaeln@chromium.org
Duration to execute localStorage.length() or sessionStorage.length().
Deprecated 2012.
michaeln@chromium.org
Duration to execute localStorage.removeItem() or
sessionStorage.removeItem().
Deprecated 2012.
michaeln@chromium.org
Duration to execute localStorage.setItem() or sessionStorage.setItem().
asanka@chromium.org
The length of downloads for serves that accept byte ranges.
asanka@chromium.org
The length of downloads for serves that do not specify whether the accept
ranges, or have invalid ranges specified.
asanka@chromium.org
The length of downloads for serves that do not accept ranges.
asanka@chromium.org
The actual bandwidth (per read) of a download.
asanka@chromium.org
Downloads extension API function calls.
asanka@chromium.org
Disk bandwidth (defined as total bytes divided by the amount of time blocked
on write or close on the file descriptor) seen for a single download.
asanka@chromium.org
Overall bandwidth seen for the download. Note that this is measured at the
point at which the file is written, and so will not take into account the
time costs of activities that occur after file write is completed (e.g. safe
browsing scanning).
asanka@chromium.org
The percentage of the potential bandwidth actually used (per read) of a
download. An entry of 100% implies that Chrome was the limiting factor in
download speed.
asanka@chromium.org
The number of downloads in history at the time it is cleared.
asanka@chromium.org
Content-Disposition header features. The presence of a Content-Disposition
header, use of 'filename' and 'filename*' parameters, and string encoding
schemes are counted for each unthrottled download. The total number
downloads is Download.Counts[5] (Initiated and Unthrottled).
asanka@chromium.org
Types of images that are downloaded.
asanka@chromium.org
Content types that are downloaded.
asanka@chromium.org
Various individual counts in the download system; see DownloadCountType for
details.
asanka@chromium.org
Various individual counts in the download system, for example the number of
downloads blocked by throttling from the DownloadRequestLimiter.
asanka@chromium.org
felt@chromium.org
User chose to save a download which was marked dangerous. Grouped by the
type of danger.
asanka@chromium.org
felt@chromium.org
User chose to save a download which was marked DANGEROUS_FILE. Grouped by
the type of file.
asanka@chromium.org
felt@chromium.org
A download which was marked DANGEROUS_FILE was discarded without the user
directly choosing, because the browser was closed. Grouped by the file
extension.
asanka@chromium.org
felt@chromium.org
User chose to discard a download which was marked DANGEROUS_FILE. Grouped by
the file extension.
asanka@chromium.org
Reason for dropping a record read in from the DB.
asanka@chromium.org
Number of downloads removed from the history at once.
asanka@chromium.org
How long it took to delete some downloads from history.
asanka@chromium.org
How long it took to delete some downloads from history, per download.
asanka@chromium.org
felt@chromium.org
A download which was marked dangerous was discarded without the user
directly choosing, because the browser was closed. Grouped by the type of
danger.
asanka@chromium.org
The percentage of the available disk bandwidth that was used by the
download. 100% indicates that the disk bandwidth was the limiting factor
for the download.
asanka@chromium.org
User actions in chrome://downloads
asanka@chromium.org
The size of successfully completed downloads.
asanka@chromium.org
A download warning was shown in the shelf. Note that some downloads may not
be shown on the shelf, e.g., if chrome://downloads is already open when the
download completes, or if an extension is using the downloads API. Grouped
by the type of danger.
asanka@chromium.org
Whether the user enables dangerous download feedback reporting after viewing
the opt-in dialog.
asanka@chromium.org
How the user interacts with the file chooser when doing a "Save
As" for non-full-page saves.
asanka@chromium.org
The amount of time in milliseconds the file thread blocks for each set of
buffers drained from the incoming pipe (ms).
asanka@chromium.org
The number of buffers in a call to DownloadManager::UpdateDownload.
asanka@chromium.org
The time between a download completing and the file being opened for the
first time.
asanka@chromium.org
The number of items in the History database, at the time a new download is
recorded.
asanka@chromium.org
The number of items in the History database, at the time a new download is
recorded. Higher maximum, more buckets than Download.HistorySize.
asanka@chromium.org
Positive net error code that caused a download to be interrupted at the
*end* of a download (when the number of bytes is known). This is only
triggered when the total content size is known before any bytes are
transferred, such as when a Content-Length header is supplied.
asanka@chromium.org
The reason that a download was interrupted at the *end* of a download (when
the number of bytes is known). This is only triggered when the total content
size is known before any bytes are transferred, such as when a
Content-Length header is supplied.
asanka@chromium.org
Positive net error code that caused a download to be interrupted.
asanka@chromium.org
The excessive number of bytes which have been received at the time that a
download is interrupted. This is only triggered when the total content size
is known before any bytes are transferred, such as when a Content-Length
header is supplied.
asanka@chromium.org
The reason that a download was interrupted.
asanka@chromium.org
The number of kilobytes received for a download at the time it is
interrupted.
asanka@chromium.org
The reported total size in kilobytes for a download at the time it is
interrupted. This is essentially the size reported by the Content-Length
header. If no size is specified up-front, it is not recorded in the
histogram. For example, a download transferred with chunked encoding will
not be recorded.
asanka@chromium.org
The total number of bytes minus the received number of bytes at the time
that a download is interrupted. This is only triggered when the total
content size is known before any bytes are transferred, such as when a
Content-Length header is supplied.
asanka@chromium.org
True if the size of an interrupted download is unknown, false if it is
known.
asanka@chromium.org
felt@chromium.org
A download has been marked as malicious. Grouped by the type of danger. Each
download can only be recorded once; it will be labeled with the first type
of danger spotted.
asanka@chromium.org
Network error that produced a DOWNLOAD_INTERRUPT_REASON_NETWORK_FAILED
result in DownloadResourceHandler::OnResponseCompleted().
asanka@chromium.org
Windows error that produced a DOWNLOAD_INTERRUPT_REASON_ACCESS_DENIED result
in MapShFileOperationCodes().
asanka@chromium.org
Windows error that produced a DOWNLOAD_INTERRUPT_REASON_FILE_FAILED result
in MapShFileOperationCodes().
asanka@chromium.org
Windows error that produced a DOWNLOAD_INTERRUPT_REASON_FILE_TRANSIENT_ERROR
result in MapShFileOperationCodes().
asanka@chromium.org
Percentage of DownloadItem::Observer::OnDownloadUpdated events that
signified a change in the extension API representation of the download.
asanka@chromium.org
Invocation count for methods of opening a download. For some file types,
Chrome defaults to opening the file in the browser instead of invoking the
system handler. The user has the option of overriding this behavior.
asanka@chromium.org
The number of unopened downloads, when one is opened.
asanka@chromium.org
The time between a download completing and the file being opened.
asanka@chromium.org
Changes observed when a response is received for a full download resumption
request.
asanka@chromium.org
Changes observed when a response is received for a partial (byte-range)
download resumption request.
asanka@chromium.org
The maximum bandwidth (per read) that Chrome could have provided for the
download. If the actual bandwidth equals the potential bandwidth, that
means that Chrome was the limiting factor for download bandwidth.
asanka@chromium.org
The percentage of the lifetime of the DownloadResourceHandler for which it
was blocked by downstream flow control. 0% indicates that the network
bandwidth was the limiting factor for the download.
asanka@chromium.org
Events (e.g. Started, Cancelled, Finished, Write to Completed file, Write to
Failed file) occuring within the state machine of a SavePackage operation.
asanka@chromium.org
The number of download items in progress on the shelf when it closes
automatically.
asanka@chromium.org
The number of download items in progress on the shelf when the user closes
it.
asanka@chromium.org
The number of download items on the shelf when it closes automatically.
asanka@chromium.org
The number of download items on the shelf when the user closes it.
asanka@chromium.org
User saw the confirm prompt to save a download which was marked dangerous.
Grouped by the type of danger.
asanka@chromium.org
The initiation source (if initiated within the content layer of chrome) for
a download.
asanka@chromium.org
The initiation source (if initiated within the above-content layer of
chrome) for a download.
asanka@chromium.org
Time between the start of a download and its completion.
asanka@chromium.org
Time elapsed until a retried download file rename operation failed for the
last time after the initial rename failed.
asanka@chromium.org
Time elapsed until a retried download file rename operation succeeded after
the initial rename failed.
asanka@chromium.org
felt@chromium.org
User chose to discard a download which was marked dangerous. Grouped by the
type of danger.
asanka@chromium.org
The number of iterations for the write loop in BaseFile::AppendDataTofile().
asanka@chromium.org
The write size for calls to BaseFile::AppendDataTofile().
Deprecated 8/2013.
joshwoodward@google.com
Status of drive cache metadata database open.
joshwoodward@google.com
Time spent to load the list of files in a single directory from Google Drive
server.
mtomasz@chromium.org
Sizes of files being downloaded from Drive. Temporary histogram for
gathering data for http://crbug.com/229650.
Deprecated 12/2013 due to the UMA stat bucket layout change. We'll use
Drive.FullFeedLoadTime instead.
joshwoodward@google.com
Time spent to load the entire file system information from the server
Deprecated 10/2012.
joshwoodward@google.com
Provides breakdown of specific formats for hosted documents. Recorded when
feed is loaded from the server.
Deprecated 10/2012.
joshwoodward@google.com
Provides breakdown of specific file formats for regular files. Recorded when
feed is loaded from the server.
joshwoodward@google.com
Time spent to load the entire file system information from the server
Deperecated 12/2013 since it did not record meaningful information.
Drive.DirectoryFeedLoadTime should be checked for measuring the time until
the user sees the first response of file lists.
joshwoodward@google.com
Time spent to load the initial part of the file system information from the
server
joshwoodward@google.com
Result of drive resource metadata database initialization.
joshwoodward@google.com
Result of attempt to open existing drive resource metadata database.
bengold@chromium.org
hashimoto@chromium.org
Reason of drive resource metadata database validity check failure. Recorded
when the validity check fails during Drive metadata initialization triggered
by profile initialization.
joshwoodward@google.com
Version number of drive resource metadata DB found on the disk before
checking whether it should be upgraded. Recorded during Drive metadata
initialization triggered by profile initialization.
joshwoodward@google.com
Number of files recovered from Drive cache directory. Recorded when file
recovery takes place after metadata DB corruption is found during metadata
DB initialization.
joshwoodward@google.com
Number of hosted documents (spreadsheets etc.) on Drive. Logged when Drive
is first accessed.
joshwoodward@google.com
Number of regualr files on Drive. Logged when Drive is first accessed.
joshwoodward@google.com
Number of total files (regualr files + hosted documents) on Drive. Logged
when Drive is first accessed.
joshwoodward@google.com
Tracks whether the push notification is initially enabled for Drive.
Recorded when the first notification is processed. Notification is emulated
by polling if the push notication is disabled.
joshwoodward@google.com
Tracks whether the push notification request is registered correctly for
Drive. Recorded when the push notification manager is initialized.
joshwoodward@google.com
Time spent to perform an incremental search for auto completion of files on
Drive. This time is collected for every partial query the user types for
auto completion. For instance, if the user types "faq",
incremental searches are performed for "f", "fa", and
"faq" respectively.
mtomasz@chromium.org
Number of jobs which have to be completed before a newly added download or
download from or to Drive is requested. Temporary histogram for gathering
data for http://crbug.com/229650.
mtomasz@chromium.org
Sizes of files being uploaded to Drive. Temporary histogram for gathering
data for http://crbug.com/229650.
joshwoodward@google.com
Outcome of enabling Google Drive offline mode automatically when a user
first logs into a Chrome OS device. This process involves opening a hidden
web page in the context of the Google Drive hosted app to perform the
initialization of offline mode.
joshwoodward@google.com
isherman@chromium.org
When Easy Unlock attempts to authenticate the secure connection between a
Chromebook (or other Chrome device) and an Android phone, whether the
authentication succeeded.
isherman@google.com
xiaowenx@google.com
xiyuan@google.com
Upon a successful Smart Lock unlock or signin, records whether the user's
phone was locked during any point while the lock screen was up. This can be
used to get a sense for whether users are using Smart Lock for Chromebook
without something like Smart Lock for Android to keep their phones unlocked.
isherman@google.com
xiaowenx@google.com
xiyuan@google.com
Measures the use of Smart Lock on the sign-in screen: records whether a
Smart Lock login succeeded or failed; or if a password fallback was used,
the reason why. Recorded upon a login attempt for users who have the Smart
Lock feature enabled.
isherman@google.com
tengs@google.com
xiaowenx@google.com
Measures the time elapsed between the user focusing her user pod and signing
in using Smart Lock.
isherman@google.com
xiaowenx@google.com
xiyuan@google.com
Measures the use of Smart Lock on the lock screen: records whether a Smart
Lock unlock attempt succeeded or failed; or if a password fallback was used,
the reason why. Recorded upon an unlock attempt for users who have the Smart
Lock feature enabled.
isherman@google.com
tengs@google.com
xiaowenx@google.com
Measures the time elapsed between the lock screen being shown and the user
unlocking the device using Smart Lock. The lock screen is typically shown
when the user opens her Chromebook's lid (or otherwise wakes the computer),
but can also be shown when the user manually locks the device.
tengs@chromium.org
xiaowenx@chromium.org
The hash of the phone model used to successfully sign in or unlock using
Smart Lock.
This hash is calculated by taking the first 4 bytes of the MD5 hash of the
device model.
tengs@chromium.org
xiaowenx@chromium.org
Measures the exponentially weighted rolling average of the received signal
strength indicator (RSSI) of the phone when the user successfully unlocks or
signs in using Smart Lock.
The exponentially weighted averaging formula is:
rollingRssi = (1 - weight) * rollingRssi + weight * currentRssi;
RSSI readings are inherently noisy, so this averaging gives a smoothed RSSI
value to work with as a heuristic for proximity.
If no RSSI was read, then a sentinel value of 127 will be recorded.
tengs@chromium.org
xiaowenx@chromium.org
Measures the time delta in milliseconds since the last zero RSSI value was
read to when the user successfully unlocks or signs in using Smart Lock.
A zero RSSI value is special because both Bluetooth devices in a connection
attempt to maintain by adjusting their transmit power levels. This time
delta can be used as a possible heuristic to determine that the phone is
close to the local device.
If no RSSI was read, then an overflow value will be recorded.
tengs@chromium.org
xiaowenx@chromium.org
Measures the difference between the current transmit power and the maximum
transmit power of the local device when the user successfully unlocks or
signs in using Smart Lock.
Devices connected using classic Bluetooth adjust their transmit power
dynamically to optimize power and signal strength. The difference between
the current transmit power and maximum transmit power can be used as a
heurstic to determine if the phone is close to the local device.
According to the Bluetooth specs, there are three classes of devices, with a
maximum transmit power of 20, 4, and 0 dBm respectively.
If no transmit power was read, then a sentinel value of 127 will be
recorded.
bcwhite@chromium.org
Reports the type of Bluetooth adapter present in the device.
Statistics about what Bluetooth capabilities are available will determine
how the EasyUnlock feature gets developed and deployed across platforms.
This value is logged only once during the lifetime of the Chrome process,
shortly after it starts up. If a Bluetooth USB adapter is inserted after
that point, the change will not be registered until Chrome restarts.
joshwoodward@google.com
tbarzic@chromium.org
Button clicked in EasyUnlock app during setup process.
joshwoodward@google.com
tbarzic@chromium.org
Deprecated 02/2015. Replaced by EasyUnlock.Setup.PromoNotificationEvent.
Tracks events related to notifications used by EasyUnlock feature. For
example a specific EasyUnlock notification being shown or clicked.
joshwoodward@google.com
tengs@chromium.org
isherman@chromium.org
Whether a lock screen and a trust agent are enabled on the remote device
(Android phone) for Easy Unlock. Recorded once per status update message
from the remote device. A status update message is expected to be sent once
when the secure channel between the local and the remote device is
established, and also each time the user-presence status changes on the
remote side.
isherman@chromium.org
xiaowenx@chromium.org
The number of eligible devices that the CryptAuth server returns during the
Smart Lock setup flow.
Note that a single user might report multiple values, for example if she
tries to complete the setup flow with a device in airplane mode, and then
tries again taking the device out of airplane mode.
isherman@chromium.org
xiaowenx@chromium.org
The number of ineligible devices that the CryptAuth server returns during
the Smart Lock setup flow.
Note that a single user might report multiple values, for example if she
tries to complete the setup flow with a device in airplane mode, and then
tries again taking the device out of airplane mode.
isherman@chromium.org
xiaowenx@chromium.org
Whether the user's phone has a secure screen lock installed. Recorded during
Smart Lock setup, when the user's phone first connects to the Chromebook.
isherman@chromium.org
xiaowenx@chromium.org
Whether the user's phone has a trust agent -- e.g. Smart Lock for Android --
enabled. Recorded during Smart Lock (for Chrome) setup, when the user's
phone first connects to the Chromebook.
Note that this histogram tracks whether the setting under Settings ~>
Security ~> Trust agents ~> Smart Lock (Google) (or any other trust
agent) is enabled. The Smart Lock trust agent is enabled by default for
users who have ascure lock screen. This metric does _not_ measure whether
users have any Smart Lock trustlets enabled.
isherman@chromium.org
xiaowenx@chromium.org
Records the most actionable reason why none of a user's devices were
eligible as unlock keys for Smart Lock. This is recorded during the Smart
Lock setup flow, only if the CryptAuth server returns no eligible devices
for the user.
To be precise, this metric tracks the _least_ actionable _reason_ why the
_most_ actionable _device_ is not eligible as an unlock key. For example,
suppose that the user has 10 ineligible devices returned. This metric tries
to identify the most likely candidate device for use as a Smart Lock key,
and then records the most confounding reason why that device is still not
eligible to be used as an unlock key.
isherman@chromium.org
xiaowenx@chromium.org
Measures user interactions with the Smart Lock promo notification.
Due to technical limitations of the implementation, it is hard to track
precisely which users opened the setup app as a result of interacting with
the promo notification. This metric measures setup app interactions from all
users who click on the promo notification, and subsequently launch the setup
app.
joshwoodward@google.com
tbarzic@chromium.org
The state of EasyUnlock setup when the app window was closed by user.
Deprecated 02/2015; replaced by EasyUnlock.AuthEvent.SignIn.
xiaowenx@google.com
xiyuan@google.com
Measures the use of Easy sign-in: records whether an Easy sign-in login
succeeded or failed; or if a password fallback was used, the reason why.
Recorded upon a login attempt for users who have the Easy sign-in feature
enabled.
joshwoodward@google.com
tengs@chromium.org
The time it takes after resuming from a suspended state (ie. opening the
Chromebook lid) to when a remote device is connected and a request is made.
Note that it is possible for the remote device not to be present when
resuming from suspend, and the device may be connected at a later time.
Therefore, large values for this metric may not be too meaningful due to
meddling users.
isherman@chromium.org
xiaowenx@chromium.org
Records when the Easy Unlock trial run is launched, and when the user
attempts to click on the lock icon during the trial run.
If a user clicks on the lock icon more than once, then the "clicked
lock icon" event counter will be incremented more than once as well.
Hence, the "user count" data shows how many users ever clicked on
the lock icon during the trial run. From the raw (non-"user
count") data, we can also see whether users click on the icon multiple
times.
Deprecated 02/2015; replaced by EasyUnlock.AuthEvent.Unlock.
joshwoodward@google.com
tbarzic@chromium.org
Screen unlock events detected while EasyUnlock was enabled.
horo@chromium.org
The time taken to allocate a process to start the EmbeddedWorkerInstance.
horo@chromium.org
The time taken to evaluate the script to start the EmbeddedWorkerInstance.
horo@chromium.org
The time taken to load the script file for the EmbeddedWorkerInstance with
network access.
horo@chromium.org
The time taken to load the script file for the EmbeddedWorkerInstance
without network access.
Removed 3/2015 along with the enhanced bookmarks sync experiment.
noyau@chromium.org
yefim@chromium.org
Captures the state the enhanced bookmark experiment is in. Recorded on
startup. To be removed once the enhanced bookmark experiment is finished.
see crbug/323423.
ianwen@chromium.org
Record which Enhanced Bookmark UI mode users are in. This will be recorded
everytime the user opens the bookmark manager UI.
mnissler@chromium.org
Time since the user logged in until the auto-enrollment protocol completed.
0 is sampled when the protocol is done by the time the user logs in.
mnissler@chromium.org
Total duration time of the auto-enrollment protocol.
mnissler@chromium.org
Network error code (if applicable) for auto-enrollment requests.
mnissler@chromium.org
URL fetcher status for auto-enrollment requests.
bartfab@chromium.org
Events for counting device policy invalidations received with and without
payloads. Invalidations indicate that a policy has been updated and should
be refreshed. Payloads provide context about the policy update, but may be
absent if dropped by the invalidation service.
bartfab@chromium.org
Events measuring effectiveness of refreshing device policy when
invalidations are received from a service. For each refresh, indicates
whether the policy changed, and whether the policy was invalidated at the
time of the refresh.
mnissler@chromium.org
Events related to fetching, saving and loading DM server tokens. These are
used to retrieve cloud policies.
atwilson@chromium.org
Temporary metric tracking which regex caused an icu::RegexMatcher
initialization failure, to help figure out the cause of
http://crbug.com/365351 which we can't repro locally.
atwilson@chromium.org
Temporary metric tracking the type of an icu::RegexMatcher initialization
failure, to help figure out the cause of http://crbug.com/365351 which we
can't repro locally.
atwilson@chromium.org
Temporary metric tracking the success of icu::RegexMatcher IcuMatcher
initialization, to help figure out the cause of http://crbug.com/365351.
tnagel@chromium.org
Whether loading of device policy from file on an enterprise-enrolled
(checked against install_attributes.pb) Chrome OS device yields an
enterprise policy with a DM token. Filled once during session startup,
after first successful device policy read.
mnissler@chromium.org
Events related to device enrollment on new installs of Chrome OS devices.
tnagel@chromium.org
Events related to forced re-enrollment (FRE) of Chrome OS devices.
tnagel@chromium.org
Events related to Chrome OS enterprise enrollment recovery. Note that this
only covers cases in which prior to recovery, the "private owner"
of the device had UMA stats enabled.
tnagel@chromium.org
Elapsed time from *after* GAIA login until enrollment was cancelled.
tnagel@chromium.org
Elapsed time from *after* GAIA login until enrollment failed.
tnagel@chromium.org
Elapsed time from *after* GAIA login until enrollment succeeded.
mnissler@chromium.org
Number of policies loaded at startup on iOS, and when a change is detected
at runtime.
mnissler@chromium.org
Result of the OpenNetworkConfiguration policy validation.
mnissler@chromium.org
A set of enterprise policy rules that are in use. This is recorded every 24
hours and at startup, if the last recording was earlier than a day before.
mnissler@chromium.org
Events related to fetching, saving and loading user policies, and also
device policies on Chrome OS.
atwilson@chromium.org
Boolean tracking whether there is a valid policy signing key on disk.
mnissler@chromium.org
Events for counting user policy invalidations received with and without
payloads. Invalidations indicate that a policy has been updated and should
be refreshed. Payloads provide context about the policy update, but may be
absent if dropped by the invalidation service.
mnissler@chromium.org
Time since startup of the cloud policy code until the policy invalidation
service first reported its online status.
mnissler@chromium.org
Load status from the policy loaders which pull policy settings from the
underlying platform, such as Windows Group Policy.
mnissler@chromium.org
Events measuring effectiveness of refreshing user policy when invalidations
are received from a service. For each refresh, indicates whether the policy
changed, and whether the policy was invalidated at the time of the refresh.
atwilson@chromium.org
Result of the attempted policy load during profile initialization.
atwilson@chromium.org
Result of validating the policy that has just been loaded from disk.
atwilson@chromium.org
Result of validating the policy sent down from the server, before writing to
disk.
mnissler@chromium.org
Initialization delay due to loading the user policy cache.
mnissler@chromium.org
Policy client error during initial policy fetch.
mnissler@chromium.org
Delay for registering the client with the policy server.
mnissler@chromium.org
Delay for minting an OAuth2 acccess token.
mnissler@chromium.org
Delay for fetching policy from the policy server.
mnissler@chromium.org
Total delay for the initial policy fetch.
mnissler@chromium.org
Service error during OAuth2 access token fetch.
mnissler@chromium.org
Network error during OAuth2 access token fetch.
mnissler@chromium.org
Source of policy validation errors on ChromeOS.
mnissler@chromium.org
Validation result when loading user policy from the policy store.
mnissler@chromium.org
Validation result when writing user policy to the policy store.
atwilson@chromium.org
Choice the user made when presented with enterprise signin dialog.
mnissler@chromium.org
Delay incurred by the token fetching step of the wildcard login check.
mnissler@chromium.org
Total delay incurred by the wildcard login check.
mnissler@chromium.org
Delay incurred by the user info fetching step of the wildcard login check.
mnissler@chromium.org
pastarmovj@chromium.org
Whether we were able to contact the AD Domain Controller. This check is
performed once at start-up on Windows.
mnissler@chromium.org
pastarmovj@chromium.org
Enum of possible things that can fail while checking for enterprise env.
This check is performed once at start-up on Windows.
mnissler@chromium.org
pastarmovj@chromium.org
Whether the machine is part of an AD domain. This check is performed once at
start-up on Windows.
mnissler@chromium.org
A set of policy rules that were ignored due to integrity violations while
parsing the policy data which happens on start-up and when the policy has
changed.
mnissler@chromium.org
pastarmovj@chromium.org
The number of disabled policy entries on Windows due to integrity violations
while parsing the policy data which happens on start-up and when the policy
has changed.
mnissler@chromium.org
pastarmovj@chromium.org
The rough Windows suite we are runnnig on. This check is performed once at
start-up on Windows.
rbyers@chromium.org
On non-mobile sites, gesture taps are delayed to prevent double taps from
sending a click event. This stat tracks the user's first action within 5
seconds after a double tap gesture when the gesture tap delay is disabled.
rbyers@chromium.org
On non-mobile sites, gesture taps are delayed to prevent double taps from
sending a click event. This stat tracks the user's first action within 5
seconds after a double tap gesture when gesture tap events are delayed.
rbyers@chromium.org
Time between initiation of any input event and the renderer receiving and
starting to process it.
rbyers@chromium.org
Number of Mouse events coalesced.
rbyers@chromium.org
Number of Touch events coalesced.
rbyers@chromium.org
Time between the first and last events in a coalesced mouse events group.
rbyers@chromium.org
Time between the first and last events in a coalesced touch events group.
mfomitchev@chromium.org
Counts the number of times the user cancelled a drag and drop operation.
mfomitchev@chromium.org
Counts the number of times the user completed a drag and drop operation.
mfomitchev@chromium.org
Counts the number of times a drag and drop operation originating outside of
a Chrome window successfuly drops.
mfomitchev@chromium.org
Counts the number of times the user started a drag and drop operation.
rbyers@chromium.org
Emitted after a renderer process main-thread fling curve animation
terminates, for any reason, reporting the average animation frequency
(animations/second) of the fling instance over its lifetime. This is
computed as the number of fling animation ticks divided by the fling
animation duration.
rbyers@chromium.org
Emitted after a renderer process impl-thread fling curve animation
terminates, for any reason, reporting the average animation frequency
(animations/second) of the fling instance over its lifetime. This is
computed as the number of fling animation ticks divided by the fling
animation duration.
kuscher@google.com
rbyers@chromium.org
The gesture-events recognized and dispatched by the browser gesture
recognizer. This replaces Ash.GestureCreated, which did not record events on
Android and Windows.
rbyers@chromium.org
Time between initiation of all input events and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between initiation of input event and browser processing.
rbyers@chromium.org
Time between touch events sent from RWH to renderer and acked by renderer.
rbyers@chromium.org
Time between touch events received by Chrome and sent from RWH to renderer.
ccameron@chromium.org
Time between wheel events sent from RWH to renderer and acked by renderer.
ccameron@chromium.org
Time between wheel events received by Chrome and sent from RWH to renderer.
rbyers@chromium.org
Time between initiation of all input events and renderer processing. This is
soon to be replaced by Event.Latency.Renderer2.*
rbyers@chromium.org
Time between input event creation and the renderer receiving and starting to
process the event. For touch events on Windows, we measure from when the
event reaches Chrome, whereas on other platforms we use the timestamp from
the kernel. On Windows, this metric is only reported when |IsHighResolution|
is true, which will introduce some sampling bias.
rbyers@chromium.org
Time between input event creation and the renderer impl thread receiving and
starting to process the event. For touch events on Windows, we measure from
when the event reaches Chrome, whereas on other platforms we use the
timestamp from the kernel. On Windows, this metric is only reported when
|IsHighResolution| is true, which will introduce some sampling bias.
Deprecated 12/2013 and replaced by Event.Latency.RendererImpl.GestureScroll2
rbyers@chromium.org
Time between initial creation of touch event and when the resulting
ScrollGesture reaches Impl thread. Maximum is 200ms.
rbyers@chromium.org
Time between touch event creation and when the resulting GestureScroll
reaches the Impl thread. Maximum is 1000ms. On Windows, we measure from when
the touch event reaches Chrome, whereas on other platforms we use the
timestamp from the kernel. On Windows, this metric is only reported when
|IsHighResolution| is true, which will introduce some sampling bias. This
supersedes the Event.Latency.RendererImpl.GestureScroll metric.
rbyers@chromium.org
Time between the browser receives the notification of a ScrollUpdate gesture
event induced renderer swap and GPU starts to swap.
rbyers@chromium.org
Time between gpu starts to swap a ScrollUpdate gesture event induced frame
and the swap finishes.
rbyers@chromium.org
Time between the ScrollUpdate gesture event is handled on main/impl thread
(specified by suffix) and before renderer starts to swap.
rbyers@chromium.org
Time between the renderer starts to swap a frame induced by ScrollUpdate
gesture event and browser receives the swap notification.
rbyers@chromium.org
Time between initial creation of a touch event and the generated
ScrollUpdate gesture event is handled on main/impl thread (specified by
suffix). If no swap was induced by the ScrollUpdate gesture event, no
recording is made.
rbyers@chromium.org
Replaced by Event.Latency.TouchToFirstScrollUpdateSwapBegin.
crbug.com/478845
Time between initial creation of a touch event and the frame swap caused by
by the generated ScrollUpdate gesture event if that ScrollUpdate is the
first such in a given scroll gesture event sequence. If no swap was induced
by the event, no recording is made.
rbyers@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
rbyers@chromium.org
Replaced by Event.Latency.TouchToScrollUpdateSwapBegin. crbug.com/478845
Time between initial creation of a touch event and the frame swap caused by
by the generated ScrollUpdate gesture event. If no swap was induced by the
event, no recording is made.
rbyers@chromium.org
Time between initial creation of a touch event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made.
rbyers@chromium.org
On non-mobile sites, gesture taps are delayed to prevent double taps from
sending a click event. This stat counts the number of taps that are delayed
by the double-tap delay versus those that are sent immediately on mobile
sites.
kuscher@google.com
rbyers@chromium.org
The duration of a touch-sequence. Only measured for single finger gestures.
This replaces Ash.TouchDuration2, which did not record events on Android and
Windows.
kuscher@google.com
rbyers@chromium.org
The maximum euclidean distance in dips (device independent pixel) which a
touch point has travelled away from its starting point. Only measured for
single finger gestures. This replaces Ash.TouchMaxDistance, which did not
record events on Android and Windows.
mfomitchev@chromium.org
Duration of touch selection sequence which finished with the user selecting
one of the text manipulation actions, such as copy, cut, or paste. The
duration is measured from the moment the text selection handles are shown,
and until the action is executed.
mfomitchev@chromium.org
Whether the touch selection sequence ended with the user selecting one of
the text manipulation actions, such as copy, cut, or paste. after startup).
Sequences ending with such action are considered successful.
mfomitchev@chromium.org
Duration of touch selection sequence which involved dragging a text
selection handle. The duration is measured from the moment the text
selection handles are shown, and until they are dismissed.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that inject at least one new ad.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that performed an action that
heuristically looks like injecting an ad, but could not be confirmed.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that performed an action that
heuristically looks like replacing an ad, but could not be confirmed.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that remove at least one ad.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that replace at least one ad.
felt@chromium.org
For each pageload, the number of extensions that inject a content script.
felt@chromium.org
For each pageload, the number of extensions that create divs to add to the
page.
felt@chromium.org
For each pageload, the number of extensions that create 'embed' elements to
add to the page.
felt@chromium.org
For each pageload, the number of extensions that create iframes to add to
the page.
felt@chromium.org
For each pageload, the number of extensions that create inputs to add to the
page.
felt@chromium.org
For each pageload, the number of extensions that create links to add to the
page.
felt@chromium.org
For each pageload, the number of extensions that create 'object' elements to
add to the page.
felt@chromium.org
For each pageload, the number of extensions that create script tags to add
to the page.
felt@chromium.org
For each pageload, the number of extensions that use document.write.
felt@chromium.org
For each www.google.com pageload, the number of extensions that inject a
content script.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create divs
to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
'embed' elements to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
iframes to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
inputs to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create links
to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
'object' elements to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
script tags to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that use
document.write.
felt@chromium.org
For each www.google.com pageload, the number of extensions that set
innerHTML.
felt@chromium.org
For each www.google.com pageload, the number of extensions that invoke DOM
methods.
felt@chromium.org
For each www.google.com pageload, the number of extensions that set the
value of DOM properties via assignments.
felt@chromium.org
For each www.google.com pageload, the number of extensions that read from
the DOM.
felt@chromium.org
For each pageload, the number of extensions that set innerHTML.
felt@chromium.org
For each pageload, the number of extensions that invoke DOM methods.
felt@chromium.org
For each pageload, the number of extensions that set the value of DOM
properties via assignments.
felt@chromium.org
For each pageload, the number of extensions that read from the DOM.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that were blacklisted when already installed,
grouped by Extension::Location. Logged when ExtensionService blackists and
unloads an installed extension.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that have been blocked from installing grouped by
Extension::Location. Logged when ExtensionService refuses to install a
blacklisted extension.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that have been silently installed in a blacklisted
state, grouped by Extension::Location. Logged when ExtensionService installs
a blacklisted extension without blocking it (ExtensionBlacklist.BlockCRX
would be logged otherwise). Typically this will be when a user has a
blacklisted extension synced.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that were unblacklisted when installed, grouped by
Extension::Location. Logged when ExtensionService unblacklists and loads a
blacklisted extension.
finnur@chromium.org
The action taken by the user when seeing the bubble, logged right after the
action is taken.
finnur@chromium.org
The total number of extensions found to be loaded under Developer Mode,
logged when the devmode bubble is shown (once per startup per profile, if
any devmode extension is found).
finnur@chromium.org
The total number of extensions found to be wiped by SideloadWipeout, logged
when the wipeout bubble is shown, which is once per startup per profile (as
long as wiped extensions were found). Not logged if no extensions of that
nature were found.
finnur@chromium.org
The action taken by the user when seeing the bubble, logged right after the
action is taken.
asargent@chromium.org
The time taken to create the computed_hashes.json file for an extension.
This happens once for each extension after we get signed values of the
expected root node of a tree hashes for each file from the webstore; we then
compute the individual block level hashes of the actual files and cache them
in computed_hashes.json (assuming we don't detect any mismatches).
asargent@chromium.org
The time taken to initialize the ContentHashReader for an extension resource
load. (The work done is to read in the verified contents and computed hashes
data, and compare them to make sure they agree.)
asargent@chromium.org
The time taken in computation (hashing actual bytes read and comparing
against expected computed hashes values) during an extension resource load.
Please list the metric's owners. Add more owner tags as needed.
Counts whether we force-disabled an installed extension at startup because a
policy provider indicated it must remain disabled.
asargent@chromium.org
This is a count of the number of ids that we asked to be signed which the
server response indicated were not in the webstore.
asargent@chromium.org
A count of the number of server requests since Chrome started running,
recorded each time we do a request. NOTE: when interpreting these values,
keep in mind that a user who did 5 server requests during one run of Chrome
will log this histogram 5 times with values 1, 2, 3, 4, and 5.
asargent@chromium.org
Whether the server result received by the extensions install signer was
valid or invalid.
asargent@chromium.org
This records the number of seconds since the last time we've done a request
to the server (only during this run of the browser).
asargent@chromium.org
Records how many seconds the browser has been running at the time a request
to the server is made to get a new install signature.
asargent@chromium.org
Logged during InstallVerifier::Init, to indicate the actual enforcement
status used (usually determined by the ExtensionInstallVerifier field trial
experiment, but possibly modified by command line flags).
asargent@chromium.org
Logged during InstallVerifier::Init to indicate the enforcement status as
determined by the ExtensionInstallVerifier field trial experiment.
asargent@chromium.org
The result of the verifier trying to get a new signature.
asargent@chromium.org
The result of initialization for the extension install verifier.
asargent@chromium.org
The outcome for each call to InstallVerifier::MustRemainDisabled.
finnur@chromium.org
The action taken by the user when seeing the bubble, notifing them of an
extension overriding their new tab page. Logged right after the action is
taken.
finnur@chromium.org
The action taken by the user when seeing the bubble, notifing them of an
extension overriding their homepage. Logged right after the action is taken.
finnur@chromium.org
The action taken by the user when seeing the bubble, notifing them of an
extension overriding their search engine. Logged right after the action is
taken.
finnur@chromium.org
The action taken by the user when seeing the bubble, notifing them of an
extension overriding their startup page. Logged right after the action is
taken.
kalman@chromium.org
rdevlin.cronin@chromium.org
The number of extensions on a page that wanted to execute a script, required
explicit user consent, and were denied permission.
kalman@chromium.org
rdevlin.cronin@chromium.org
The number of extensions on a page that wanted to execute a script, required
explicit user consent, and were granted permission.
kalman@chromium.org
rdevlin.cronin@chromium.org
The number of extensions per page that injected an ad and could have been
stopped if the user had declined script injection. This is related to the
ActivityLog metrics, ExtensionActivity.Ad*. Recorded upon page close or
navigation. Only recorded if there was at least one ad injection detected.
kalman@chromium.org
rdevlin.cronin@chromium.org
Deprecated 2/2014.
The number of extensions which would display an Active Script Running
indiciation to the user. Recorded at page close.
kalman@chromium.org
rdevlin.cronin@chromium.org
The number of extensions per page that injected an ad and that could not
have been stopped through script injection permission. This is related to
the ActivityLog metrics, ExtensionActivity.Ad*. Recorded upon page close or
navigation. Only recorded if there was at least one ad injection detected.
felt@chromium.org
rdevlin.cronin@chromium.org
The type of ad that was injected.
felt@chromium.org
rdevlin.cronin@chromium.org
The install location of an ad-injecting extension. Recorded upon page close
for any extension that injected ads on that page.
Please list the metric's owners. Add more owner tags as needed.
Records when the allocation of IDs for chrome.runtime.Port overflows.
Please list the metric's owners. Add more owner tags as needed.
Captures the results of URL resolution when relative urls are used in the
tabs/windows api.
benwells@chromium.org
tapted@chromium.org
The number of times v1 apps are launched grouped by
extension_misc::AppLaunchBuckets. See also Apps.AppLaunch for v2 apps.
benwells@chromium.org
tapted@chromium.org
Deprecated as of 12/2014, replaced by Apps.HostedAppLaunchContainer.
The number of times apps are launched grouped by
extensions::LaunchContainer.
benwells@chromium.org
cylee@chromium.org
The number of times times apps are launched grouped by
extensions::AppLaunchSource.
benwells@chromium.org
tapted@chromium.org
The number of apps loaded at startup time grouped by Extension::Location.
benwells@chromium.org
tapted@chromium.org
The actions taken in the NTP apps promo grouped by
extension_misc::AppsPromoBuckets.
benwells@chromium.org
tapted@chromium.org
The number of apps launched grouped by extensions::LaunchType.
kalman@chromium.org
Time taken to load BackgroundContents for apps at startup when the extension
system notifies that it is ready.
Replaced by Extensions.BackgroundPageLoadTime2.
kalman@chromium.org
The time for an extension's background page to load.
kalman@chromium.org
The time taken for an extension's persistent background page to load its
initial URL.
kalman@chromium.org
The type (if any) of background page the extension has. Recorded for
installed extensions on startup.
kalman@chromium.org
The number of times each Extension function call sends a bad message,
killing the renderer. This may indicate a bug in that API's implementation
on the renderer. Note a similar, aggregate metric is BadMessageTerminate_EFD
which counts the number of bad messages that are sent overall.
kalman@chromium.org
The reason a valid ExtensionSyncData could not be parsed from a SyncData
received from sync.
rkaplow@chromium.org
The amount of time that elapsed during
ExtensionService::CheckForExternalUpdates.
asargent@chromium.org
Fired each time an extension was detected to be corrupted (contents not
matching an expected content hash from the webstore) and was disabled.
rockot@chromium.org
The reason why an extension was detected to be corrupted. Recorded each time
an extension is disabled due to corruption detection.
asargent@chromium.org
Logged once at startup, this is the value of a counter that is incremented
anytime we disable a corrupted extension because its content didn't match an
expected content hash.
asargent@chromium.org
Simiar to Extensions.CorruptExtensionBecameDisabled, but fires when we're in
a bootstrapping mode and would have disabled an extension.
asargent@chromium.org
Net error results from URLFetcher.
asargent@chromium.org
Number of times chrome retried to download an extension with a url on a
google.com domain, before eventually giving up.
asargent@chromium.org
Number of times chrome retried to download an extension with a url on a non
google.com domain, before eventually giving up.
asargent@chromium.org
Number of times chrome retried to download an extension with a url on a
google.com domain, before eventually succeeding.
asargent@chromium.org
Number of times chrome retried to download an extension with a url on a non
google.com domain, before eventually succeeding.
asargent@chromium.org
Length of the path to the directory under which an extension is installed.
This directory is in the user's profile.
Please list the metric's owners. Add more owner tags as needed.
Time spent until rules storage delegate gets ready.
Please list the metric's owners. Add more owner tags as needed.
Number of extensions referenced in the depricated external extensions source
at path chrome::DIR_DEPRICATED_EXTERNAL_EXTENSIONS.
There is no such thing as an extension dialog.
Please list the metric's owners. Add more owner tags as needed.
The time for a dialog-hosted extension to load.
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per blessed
extension context (chrome-extension://... origins within Extension
processes, like background pages, options pages, popups).
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per blessed web page
context (hosted apps).
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per content script
context.
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per unblessed
extension context (chrome-extension://... origins hosted in iframes).
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings in an unknown type
of context (this should never happen other than in bizarre circumstances).
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per web page context
(just the chrome.app, chrome.webstore, and possibly chrome.runtime APIs).
kalman@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per WebUI context
(chrome://extensions and so forth).
kalman@chromium.org
Records the Chrome channel when JavaScript exceptions are not gracefully
dealt with, and suppressed by C++ instead. These are exceptions generated
(or simply not caught and gracefully recovered) in our own internal
JavaScript, not from JavaScript code written by developers (that which is
typically hosted in CRX files). This should be 0 for unstable channels like
canary and dev, because we try *not* to suppress errors and instead kill the
renderer and generate a crash report. However, at times we need to suppress
even those. Note that this histogram is intended to be tracked over time,
per channel, to observe crash rates. Comparisons between
stable/beta/dev/canary are unlikely to be meaningful.
kalman@chromium.org
The number of extensions that are disabled at browser startup.
kalman@chromium.org
The number of extensions that are disabled at browser startup due to
permissions increases.
kalman@chromium.org
User response to the dialog shown when an extension is disabled due to an
update requiring more permissions.
mek@chromium.org
User response to the dialog shown when an extension is disabled due to it
having been installed remotely.
asargent@chromium.org
The count of disabled extensions at startup grouped by disble reason from
Extension::DisableReason. When an extension is disabled, it can be for one
or more reasons (although typically just one), so the sum of these may be
greater than 'Extensions.Disabled' which is a count of the number of unique
extensions that are disabled.
kalman@chromium.org
wittman@chromium.org
The number of event listeners the Enhanced Bookmarks Manager has, measured
at profile startup. A value of 0 implies that Chrome has a general bug with
event page management, since the bookmarks manager should always have at
least one event listener - but a bug with event page management that affects
the bookmarks manager is particularly dire.
asargent@chromium.org
If opening the CRX file for unpacking fails, this integer is the error code
given by the OS.
kalman@chromium.org
The number of extensions with event pages that have no registered event
listeners at profile startup. (This may indicate something has gone wrong;
such event pages will never get started.)
Replaced by Extensions.EventPageActiveTime2.
kalman@chromium.org
The time an extension's event page has spent loaded.
kalman@chromium.org
The time between an extension's event page loading its first URL and the
event page later shutting down.
kalman@chromium.org
The time an extension's event page has spent unloaded.
Replaced by Extensions.EventPageLoadTime2.
kalman@chromium.org
The time for an extension's event page to load.
kalman@chromium.org
The time taken for an extension's event page to load its initial URL.
dpolukhin@chromium.org
Number of cached extensions on disk. Reported on Chrome OS during user
session start.
dpolukhin@chromium.org
Total size of .crx files in cache on disk. Reported on Chrome OS during user
session start.
kalman@chromium.org
The maximum number of ExtensionHosts (primarily background/event pages) that
were actively loading at any one time, within the first minute of Chrome
startup. Emitted exactly one minute after startup.
kalman@chromium.org
The maximum number of ExtensionHosts (primarily background/event pages) in
the queue awaiting being loaded (via an ExtensionHostQueue), within the
first minute of Chrome startup. Emitted exactly one minute after startup.
kalman@chromium.org
The total number of ExtensionHosts that completed loading in the first
minute of Chrome startup. Emitted exactly one minute after startup.
kalman@chromium.org
The total number of ExtensionHosts (primarily background/event pages) that
were added to a queue to start loading, within the first minute of Chrome
startup. These may or may not end up starting, let alone finishing,
depending on the queue behavior. Emitted exactly one minute after startup.
kalman@chromium.org
An extension has been installed.
kalman@chromium.org
The number of extensions loaded at startup time grouped by
Extension::Location.
rkaplow@chromium.org
The amount of time that elapsed during ExtensionManagement::Refresh.
Please list the metric's owners. Add more owner tags as needed.
Length of the Extensions dir path inside the profile directory.
kalman@chromium.org
Time taken for the ExtensionService to initialize, including the time it
takes to load the extensions for the service's profile and parse their
manifests. This happens during startup and also any time a new profile is
loaded.
kalman@chromium.org
Time taken for the ExtensionService to notify all ready listeners that the
extension system is now ready. This happens as part of the total
initialization time of ExtensionService, measured in
Extensions.ExtensionServiceInitTime.
kalman@chromium.org
An extension has been uninstalled.
Please list the metric's owners. Add more owner tags as needed.
Records what happens to extensions that are sideloaded, grouped by the
ExternalExtensionEvent enum.
Please list the metric's owners. Add more owner tags as needed.
The number of sideloaded apps/extensions loaded on startup grouped by
enabled/disabled state.
Please list the metric's owners. Add more owner tags as needed.
Number of extensions referenced in the external extensions source at path
chrome::DIR_EXTERNAL_EXTENSIONS.
rkaplow@chromium.org
The amount of time that elapsed during extensions::FeatureProvider::Static.
Only measured while in the browser process.
kalman@chromium.org
The number of extensions (and friends) that could have been given access to
the file:// scheme, and were, for users that have at least one extension
that could have been given access. This excludes anything that doesn't show
up in chrome://extensions (platform apps, hosted apps, component
extensions), policy-installed extensions, and unpacked extensions. See also
Extensions.FileAccessNotAllowed.
kalman@chromium.org
The number of extensions (and friends) that could have been given access to
the file:// scheme, but weren't, for users that have at least one extension
that could have been given access. This excludes anything that doesn't show
up in chrome://extensions (platform apps, hosted apps, component
extensions), policy-installed extensions, and unpacked extensions. See also
Extensions.FileAccessAllowed.
xiaohuic@chromium.org
Record the time taken to physically move the extention files from temporary
location to the final installation directory. It includes the time to flush
the file system if ExtensionUseSafeInstallation field trial is enabled. This
is recorded once per extension install/update.
rkaplow@chromium.org
The amount of time that elapsed during the FontSettingsEventRouter
construction.
Please list the metric's owners. Add more owner tags as needed.
Number of apps/extensions loaded on startup with an inconsistent "from
webstore" state. This means an item that is flagged as from_webstore,
but with either a non-webstore update_url or an external install location.
kalman@chromium.org
Number of calls to extension functions.
Please list the metric's owners. Add more owner tags as needed.
What happens when the extensions system tries to get a temp dir to unpack
in?
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when it is
automatically disabled due to a permission increase (e.g., after an
extension upgrade). To find places where this histogram may be emitted, look
for calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument AutoDisable. For Sync users, this may be reported for each device,
depending on whether the Sync update or the extension auto-update happen
first.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when it was
installed. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument Install. For Sync users, this is reported for each device.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when installation
was aborted (e.g. because the parent window of the confirmation dialog went
away), not including installation errors and user cancels. To find places
where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
InstallAbort.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when installation
was canceled. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument InstallCancel.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when it was
loaded (which happens at profile open or extension install). To find places
where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument Load.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when it was
re-enabled from a confirmation prompt. To find places where this histogram
may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
ReEnable.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when the
re-enable prompt was aborted (e.g. because the parent window of the
confirmation dialog went away), not including installation errors and manual
user cancels. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument ReEnableAbort.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when the
re-enable was canceled from the confirmation prompt. To find places where
this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
ReEnableCancel.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when it was
uninstalled. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument Uninstall. For Sync users, this is reported for each device.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when it was
installed through the web store. To find places where this histogram may be
emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
WebStoreInstall. Contrary to the more-general HasPermissions_Install3
histogram, this one is NOT reported for each device.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when installation
from the web store was aborted (e.g. because the parent window of the
confirmation dialog went away), not including installation errors and user
cancels. To find places where this histogram may be emitted, look for calls
to ExtensionService::RecordPermissionMessagesHistogram with the argument
WebStoreInstallAbort.
kalman@chromium.org
rpaquay@chromium.org
Whether there were any permissions present in an extension when installation
from the web store was canceled. To find places where this histogram may be
emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
WebStoreInstallCancel.
benwells@chromium.org
Records the container used for a hosted app launch. The definition of
'launch' for the purposes of this histogram is different to that used for
the launch type histograms. This definition is less inclusive, for example
it does not include navigations to the hosted app due to normal browsing,
which the other definition does include. This definition could be thought of
more as explicit launches via a launch surface such as the app launcher,
chrome://apps, or a shortcut.
rdevlin.cronin@chromium.org
The usage (in kilobytes) of persistent storage in a hosted app with the
unlimitedStorage permission. This is logged each time the storage is used*,
so this also serves as a cap of the number of calls that would fail if the
app did not have the unlimited storage permission. *Capped at once per 30
seconds so as to not impact performance.
rdevlin.cronin@chromium.org
The percentage of "normal" (that is, not unlimited) quota that a
hosted app with unlimited storage is currently using. This is logged each
time the storage is used*, so the number of times the app would use greater
than 100% of the default storage can serve as a cap for the number of calls
that would fail if the app did not have the unlimitedStorage permission.
*Capped at once per 30 seconds so as to not impact performance.
rdevlin.cronin@chromium.org
The usage (in kilobytes) of a hosted app with the unlimitedStorage api
permission, recorded once per run per app the first time we load storage for
the hosted app. This is separate from the other metrics on hosted app
unlimited storage usage because it is logged once per extension per run.
kalman@chromium.org
The number of extensions (and friends) that could have been allowed in
incognito, and were, for users that have at least one extension that could
have been allowed. This excludes anything that doesn't show up in
chrome://extensions (platform apps, hosted apps, component extensions),
policy-installed extensions, and unpacked extensions. See also
Extensions.IncognitoNotAllowed.
kalman@chromium.org
The number of extensions (and friends) that could have been allowed in
incognito, but weren't, for users that have at least one extension that
could have been allowed. This excludes anything that doesn't show up in
chrome://extensions (platform apps, hosted apps, component extensions),
policy-installed extensions, and unpacked extensions. See also
Extensions.IncognitoAllowed.
rkaplow@chromium.org
The amount of time that elapsed during
ExtensionPrefs::InitExtensionControlledPrefs.
rkaplow@chromium.org
The amount of time that elapsed during the GetExtensions call within
ExtensionPrefs::InitPrefStore.
rkaplow@chromium.org
The amount of time that elapsed during ExtensionPrefs::InitPrefStore.
kalman@chromium.org
rdevlin.cronin@chromium.org
The amount of time for a CSS file to be injected into a page.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of blocking scripts injected at document end by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of scripts injected at document end by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Time taken to inject all scripts at document end by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of blocking scripts injected at document idle by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of scripts injected at document idle by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Time taken to inject all scripts at document idle by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Time taken to inject all scripts by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of blocking scripts injected at document start by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of css files injected by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Number of scripts injected at document start by extensions.
kalman@chromium.org
rdevlin.cronin@chromium.org
Time taken to inject css/scripts at document start by extensions.
meacer@chromium.org
Whether the user accepted or aborted an extension installation.
meacer@chromium.org
Type of the extension install prompt displayed when an extension
installation is triggered.
meacer@chromium.org
Actions on the show details link grouped by action type when the install
prompt trial is running.
meacer@chromium.org
Actions on the show permissions link grouped by action type when the install
prompt trial is running.
kalman@chromium.org
Installs grouped by the location property in prefs.
kalman@chromium.org
Installs grouped by Extension::HistogramType.
kalman@chromium.org
The number of extensions and themes loaded at browser startup.
kalman@chromium.org
Time taken to load all component extensions at browser startup. This happens
as part of the total initialization time of ExtensionService, measured in
Extensions.ExtensionServiceInitTime.
kalman@chromium.org
Time taken to load all non-component extensions at browser startup. This
happens as part of the total initialization time of ExtensionService,
measured in Extensions.ExtensionServiceInitTime.
kalman@chromium.org
Time taken to load all non-component extensions at browser startup and
record metrics. This happens as part of the total initialization time of
ExtensionService, measured in Extensions.ExtensionServiceInitTime.
kalman@chromium.org
The number of apps loaded by each user at startup time.
kalman@chromium.org
The number of externally managed apps loaded by each user at startup time.
kalman@chromium.org
The number of user-installed apps loaded by each user at startup time.
kalman@chromium.org
The number of browser action extensions loaded at browser startup.
asargent@chromium.org
Deprecated as of 4/2015. Replaced by ManagedUsers.Whitelist.Count.
The number of content-pack extensions loaded at browser startup.
calamity@chromium.org
The creation flags of all extensions loaded at startup time grouped by
Extension::InitFromValueFlags.
kalman@chromium.org
The number of extensions loaded at browser startup.
kalman@chromium.org
The number of externally managed extensions loaded at browser startup.
kalman@chromium.org
The number of user-installed extensions loaded at browser startup.
kalman@chromium.org
The number of externally managed extensions and apps loaded at browser
startup.
kalman@chromium.org
The number of hosted apps loaded by each user at startup time.
kalman@chromium.org
The number of legacy packaged apps loaded by each user at startup time.
kalman@chromium.org
The number of platform apps loaded at browser startup.
kalman@chromium.org
The number of themes loaded at browser startup.
kalman@chromium.org
The number of extensions loaded at startup time grouped by
Extension::HistogramType.
kalman@chromium.org
The number of converted user scripts loaded at browser startup.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a google.com domain, before eventually giving up.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a non google.com domain, before eventually giving up.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a google.com domain, before eventually succeeding.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a non google.com domain, before eventually succeeding.
Please list the metric's owners. Add more owner tags as needed.
Number of extension loads on startup where it is necessary to reload the
mainfest because the locale has changed.
Please list the metric's owners. Add more owner tags as needed.
Number of extension loads on startup where it is not necessary to reload the
extension's manifest.
Please list the metric's owners. Add more owner tags as needed.
Number of extension loads on startup where it is necessary to reload the
manifest because the extension is unpacked.
kalman@chromium.org
The manifest version of each loaded extension.
battre@chromium.org
Time that network requests were blocked due to extensions.
battre@chromium.org
Percentage of total lifetime a network request was blocked due to an
extension.
battre@chromium.org
Time that network requests were blocked due to relevant rule registries
loading.
kalman@chromium.org
The number of apps/extensions with a non-webstore update_url loaded at
startup time grouped by Extension::Location.
Please list the metric's owners. Add more owner tags as needed.
Number of non-WebStore extensions on startup that override the new tab page.
Deprecated as of 5/2014, replaced by Extensions.Permissions_AutoDisable2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it is automatically disabled
due to a permission increase (e.g., after an extension upgrade). To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
AutoDisable.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it is automatically disabled
due to a permission increase (e.g., after an extension upgrade).
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it is automatically disabled
due to a permission increase (e.g., after an extension upgrade). To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
AutoDisable. For Sync users, this may be reported for each device, depending
on whether the Sync update or the extension auto-update happen first.
Deprecated as of 5/2014, replaced by Extensions.Permissions_Install2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
Install.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
Install. For Sync users, this is reported for each device.
Deprecated as of 5/2014, replaced by Extensions.Permissions_InstallAbort2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was aborted, not
including installation errors and user cancels. To find places where this
histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
InstallAbort.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was aborted, not
including installation errors and user cancels.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was aborted (e.g.
because the parent window of the confirmation dialog went away), not
including installation errors and user cancels. To find places where this
histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
InstallAbort.
Deprecated as of 5/2014, replaced by Extensions.Permissions_InstallCancel2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was canceled. To
find places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
InstallCancel.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was canceled.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was canceled. To
find places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
InstallCancel.
Deprecated as of 5/2014, replaced by Extensions.Permissions_Load2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was loaded.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was loaded. To find places
where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument Load.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was loaded (which happens at
profile open or extension install). To find places where this histogram may
be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument Load.
Deprecated as of 5/2014, replaced by Extensions.Permissions_ReEnable2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was re-enabled from a
confirmation prompt. To find places where this histogram may be emitted,
look for calls to ExtensionService::RecordPermissionMessagesHistogram with
the argument ReEnable.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was re-enabled from a
confirmation prompt.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was re-enabled from a
confirmation prompt. To find places where this histogram may be emitted,
look for calls to ExtensionService::RecordPermissionMessagesHistogram with
the argument ReEnable.
Deprecated as of 5/2014, replaced by Extensions.Permissions_ReEnableAbort2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable prompt was
aborted, not including installation errors and manual user cancels. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
ReEnableAbort.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable prompt was
aborted, not including installation errors and manual user cancels.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable prompt was
aborted (e.g. because the parent window of the confirmation dialog went
away), not including installation errors and manual user cancels. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
ReEnableAbort.
Deprecated as of 5/2014, replaced by Extensions.Permissions_ReEnableCancel2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable was canceled from
the confirmation prompt. To find places where this histogram may be emitted,
look for calls to ExtensionService::RecordPermissionMessagesHistogram with
the argument ReEnableCancel.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable was canceled from
the confirmation prompt.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable was canceled from
the confirmation prompt. To find places where this histogram may be emitted,
look for calls to ExtensionService::RecordPermissionMessagesHistogram with
the argument ReEnableCancel.
Deprecated as of 5/2014, replaced by Extensions.Permissions_Uninstall2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was uninstalled. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
Uninstall.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was uninstalled.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was uninstalled. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
Uninstall. For Sync users, this is reported for each device.
Deprecated as of 5/2014, replaced by
Extensions.Permissions_WebStoreInstall2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed through the
web store. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument WebStoreInstall.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed through the
web store.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed through the
web store. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument WebStoreInstall. Contrary to the more-general Permissions_Install3
histogram, this one is NOT reported for each device.
Deprecated as of 5/2014, replaced by
Extensions.Permissions_WebStoreInstallAbort2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was aborted, not including installation errors and user cancels. To find
places where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
WebStoreInstallAbort.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was aborted, not including installation errors and user cancels.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was aborted (e.g. because the parent window of the confirmation dialog went
away), not including installation errors and user cancels. To find places
where this histogram may be emitted, look for calls to
ExtensionService::RecordPermissionMessagesHistogram with the argument
WebStoreInstallAbort.
Deprecated as of 5/2014, replaced by
Extensions.Permissions_WebStoreInstallCancel2.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was canceled. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument WebStoreInstallCancel.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was canceled.
kalman@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was canceled. To find places where this histogram may be emitted, look for
calls to ExtensionService::RecordPermissionMessagesHistogram with the
argument WebStoreInstallCancel.
kalman@chromium.org
The time taken between a user clicking on a button to open a popup, and the
popup finishing loading its initial URL. This is a good way to measure the
UI responsiveness of extension popups. It will be strictly larger than
Extensions.PopupLoadTime2, which only measures the time it takes to load -
there may be a delay between clicking and starting to load, for example, if
the popup's host got caught in a queue.
Replaced by Extensions.PopupLoadTime2.
kalman@chromium.org
The time for an Extension's popup to load.
kalman@chromium.org
The time taken for an extension popup to load its initial URL. This may not
include the time taken for an extension process to start, if the extension
already has a background page running. It does not necessarily correlate
with the amount of time since the popup was *clicked* either, since there
may be a delay between the user clicking and the loading started.
Extensions.PopupCreateTime measures this instead.
kalman@chromium.org
The time taken to start up persistent background pages for extensions in
ExtensionProcessManager when the extension system notifies that it is ready.
asargent@chromium.org
The initialization latency (in milliseconds) introduced to each extension
resource request by querying the directory timestamp.
asargent@chromium.org
The difference in seconds between an extension resource's last modification
time and its extension base directory's creation time. Recorded on each
extension resource request if the difference is non-negative (i.e., the
resource's last modification time is more recent than the directory's
creation time.) For cases where the directory creation date is more recent,
see Extensions.ResourceLastModifiedNegativeDelta instead.
asargent@chromium.org
The absolute difference in seconds between an extension resource's last
modification time and extension base directory's creation time. Recorded on
each extension resource request if the difference is negative (i.e., the
directory's creation time is more recent than the resource's last
modification time.) For cases where the resource modification time is more
recent, see Extensions.ResourceLastModifiedDelta instead.
asargent@chromium.org
Count the number of times a sandboxed extension unpack fails.
asargent@chromium.org
What caused a sandboxed extension unpack to fail?
asargent@chromium.org
Time taken to unpack an extension, when the unpack fails.
ginkage@chromium.org
Whether a CRX file hash sum was the same as in an updater manifest.
asargent@chromium.org
Length of the initial path to the CRX to be unpacked.
asargent@chromium.org
Length of the normalized (link/junction free) path to the temporary copy of
a CRX made during unpacking.
asargent@chromium.org
Rate at which a CRX file is unpacked in Kilobytes per second.
asargent@chromium.org
Rate at which CRX files 1MB to 2MB are unpacked in Kilobytes per second.
asargent@chromium.org
Rate at which CRX files 2MB to 5MB are unpacked in Kilobytes per second.
asargent@chromium.org
Rate at which CRX files 50kB to 1MB are unpacked in Kilobytes per second.
asargent@chromium.org
Rate at which CRX files 5MB to 10 MB are unpacked in Kilobytes per second.
asargent@chromium.org
Rate at which CRX files larger than 10MB are unpacked in Kilobytes per
second.
asargent@chromium.org
Rate at which CRX files under 50 KB are unpacked in Kilobytes per second.
asargent@chromium.org
Count the number of times a sandboxed CRX unpack succeeds.
asargent@chromium.org
Count the number of times a sandboxed CRX unpack succeeds, but we can't get
the file size.
asargent@chromium.org
Size of the .crx file, in KB, when the unpack succeeds.
asargent@chromium.org
Time taken to unpack an extension, when the unpack succeeds.
asargent@chromium.org
Length of the path of the temporary copy of a CRX made during unpacking.
asargent@chromium.org
Length of the path under which a CRX is unpacked.
asargent@chromium.org
The time one extension delays network requests at startup.
kalman@chromium.org
The total time extensions delay network requests at startup.
rkaplow@chromium.org
The amount of time that elapsed during StorageFrontend::Init.
rdevlin.cronin@chromium.org
kalman@chromium.org
The duration by which a network request was delayed while waiting for
extension user script load. Recorded once per request that is delayed, at
the time the resource resumes loading.
rdevlin.cronin@chromium.org
kalman@chromium.org
The total number of network requests that were delayed by extension user
script load. Recorded once each time network requests may have been delayed
by user script load (i.e., once at the end of each batch of script loads).
Please list the metric's owners. Add more owner tags as needed.
Time taken to load a toolstrip.
rdevlin.cronin@chromium.org
The action that was taken from an extension uninstall dialog. Recorded once
per dialog shown. Only recorded if all possible actions (including report
abuse) were available on the dialog.
kalman@chromium.org
Uninstalls grouped by Extension::HistogramType.
asargent@chromium.org
Count failing CRX installs, grouped by the way an extension can be
installed.
asargent@chromium.org
Count successful CRX installs, grouped by the location property in prefs.
installed.
asargent@chromium.org
Count successful CRX installs, grouped by the cause of the install.
asargent@chromium.org
Count successful CRX installs, grouped by the location property in prefs.
Please list the metric's owners. Add more owner tags as needed.
The number of legacy packaged apps and hosted apps that were checked during
an update check.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that were checked during an update check.
Please list the metric's owners. Add more owner tags as needed.
Time in minutes between update checks.
Please list the metric's owners. Add more owner tags as needed.
The number of crx's with a Google-hosted update URL that were checked during
an update check.
Please list the metric's owners. Add more owner tags as needed.
The number of crx's with no update URL checked during an update check.
Please list the metric's owners. Add more owner tags as needed.
The number of crx's with a non-Google update URL that were checked during an
update check.
Please list the metric's owners. Add more owner tags as needed.
The number of packaged apps that were checked during an update check.
Please list the metric's owners. Add more owner tags as needed.
The number of themes that were checked during an update check.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that were updated at browser startup.
Deprecated 10/2013.
Please list the metric's owners. Add more owner tags as needed.
What happened when the extension updater tried to write a file?
Please list the metric's owners. Add more owner tags as needed.
Updates grouped by the location property in prefs.
Please list the metric's owners. Add more owner tags as needed.
Updates grouped by Extension::HistogramType.
xiaohuic@chromium.org
The time spent to download the crx file from the webstore to local disk.
This is recorded once per successful download.
Please list the metric's owners. Add more owner tags as needed.
The reason a webstore download was interrupted.
Please list the metric's owners. Add more owner tags as needed.
The number of KBytes received for a webstore download before it was
interrupted.
Please list the metric's owners. Add more owner tags as needed.
The total expected size in KBytes of an interrupted webstore download.
Please list the metric's owners. Add more owner tags as needed.
Tracks whether the total size of an interrupted webstore download was known.
Please list the metric's owners. Add more owner tags as needed.
Records whether adding a new/updated extension to the install verifier
succeeded.
Please list the metric's owners. Add more owner tags as needed.
The outcome of a call to ExtensionService::VerifyAllExtensions, whether it
was called for bootstrapping or another reason (extension
installed/uninstalled, etc.).
Please list the metric's owners. Add more owner tags as needed.
When loading the chrome://extensions page, this records whether we decided
to do a verification check against the server (because the user had one or
more extensions disabled due to verification failure).
finnur@chromium.org
The number of icons the Browser Actions Container knows about (visible or in
the overflow bucket). Does not count icons that have been permanently hidden
by the user. Measured once per startup per (non-incognito) profile.
finnur@chromium.org
The number of Browser Action icons the user has elected to permanently hide
(as opposed to putting them in the overflow bucket). Measured once per
startup per (non-incognito) profile.
finnur@chromium.org
The number of visible icons in the Browser Actions Container (visible as in
number of icons not in the overflow bucket). 0 means all icons are in the
overflow bucket. MAX_INT means the toolbar is always showing all icons.
Measured once per startup per (non-incognito) profile but only for those
profiles that have one or more browser actions showing in the toolbar.
asargent@chromium.org
The time taken to complete an extension url request.
asargent@chromium.org
The error code for failures of incremental reads of a file stream for a
chrome-extension:// URL. (See also ExtensionUrlRequest.OnReadCompleteResult
for the success case).
asargent@chromium.org
The result of an incremental read of a file stream for a chrome-extension://
URL, representing a byte count. Logged in success cases (see also
ExtensionUrlRequest.OnReadCompleteError).
asargent@chromium.org
When fetching a chrome-extension:// URL, this indicates the first byte
position we read from. This will be greater than 0 in cases such as XHR's
with a Range header, but will normally be 0 in the typical case of reading
the entire file. This helps identify how frequently partial file reads are
taking place.
asargent@chromium.org
The total number of bytes read for a chrome-extension:// URL, logged when
the job is finished (either successfully or not).
brucedawson@chromium.org
Records several bits of information about whether the Windows
FaultTolerantHeap might be enabled. This is logged (from a delayed task)
when the browser process starts up.
smckay@google.com
Chrome OS File Browser - Specific actions taken by user such initiating
cloud import, canceling import, selecting a directory, or opting-in to
Drive>Photos sync.
joshwoodward@google.com
Chrome OS File Browser opening mode.
joshwoodward@google.com
Chrome OS File Browser: time to scan a directory. Measured on every File
Browser directory change.
joshwoodward@google.com
Tracks whether download destination is set to a Google Drive folder when the
download destination is changed by the user in the settings page.
joshwoodward@google.com
Tracks whether download destination is set to a Google Drive folder on
startup.
joshwoodward@google.com
Chrome OS File Browser: number of files and directories in the Downloads
directory (not including the contents of nested directories). Computed every
time the File Browser current directory changes to Downloads.
joshwoodward@google.com
Chrome OS File Browser: this is recorded when the user adds a folder
shortcut.
joshwoodward@google.com
Chrome OS File Browser: number of saved folder shorcuts. This is recorded
when Files.app is launched.
joshwoodward@google.com
Chrome OS File Browser: this is recorded when the user clicks or selects a
folder shortcut and is navigated to the target folder.
joshwoodward@google.com
Chrome OS File Browser: this is recorded when the user removes a folder
shortcut.
The bug which the UMA was investigating got fixed.
hirono@chromium.org
Chrome OS File Browser: time from the SuspendDone event to the DiskRemoved
event. The UMA is added temporarily for crbug.com/433734.
The bug which the UMA was investigating got fixed.
hirono@chromium.org
Chrome OS File Browser: time from the DiskRemoved event to the Suspend
event. The UMA is added temporarily for crbug.com/433734.
joshwoodward@google.com
Chrome OS File Browser is an built-in extension without a background page.
Its main.html file is loaded every time the user opens a File Browser tab or
a file chooser dialog. The file is fairly large and the initialization is
pretty expensive.
Deprecated 4/2013, and replaced by FileBrowser.ViewingFileType.
joshwoodward@google.com
File types that were tried to be opened through browser.
joshwoodward@google.com
Chrome OS Photo Editor: time to display an image. Measured from the moment
the user selected the image till the moment it is displayed (not counting
the low resolution preview).
joshwoodward@google.com
Chrome OS Photo Editor: the type of the file opened.
joshwoodward@google.com
Chrome OS Photo Editor: the way the image has been loaded.
joshwoodward@google.com
Chrome OS Photo Editor: time to load an image from a file.
joshwoodward@google.com
Chrome OS Photo Editor: the result of a file save operation.
joshwoodward@google.com
Chrome OS Photo Editor: time to save an image to a file.
joshwoodward@google.com
Chrome OS Photo Editor: size of an image file in megabytes. Measured on
every image load.
joshwoodward@google.com
Chrome OS Photo Editor: size of an image in megapixels. Measured on every
image load.
joshwoodward@google.com
Chrome OS Photo Editor: the button which the user clicked.
joshwoodward@google.com
Chrome OS Photo Import flow: action chosen in the Action Choice dialog for
the external device.
joshwoodward@google.com
Chrome OS Photo Import flow: the number of photos imported. Measured on
every successfull import operation.
joshwoodward@google.com
Chrome OS Photo Import flow: the percent of photos imported among all the
photos on the device. Measured on every successfull import operation.
joshwoodward@google.com
Chrome OS Photo Import flow: time to load the action dialog. Measured
between the moment window appears and the moment user see all available
actions for the device.
joshwoodward@google.com
Chrome OS Photo Import flow: time to scan the external device.
joshwoodward@google.com
Chrome OS File Browser: the reason why the suggest apps dialog was closed.
joshwoodward@google.com
Chrome OS File Browser: whether the Webstore item user selected was
successfully installed or not.
joshwoodward@google.com
Chrome OS File Browser: whether the initialization of the dialog succeeded
or not.
joshwoodward@google.com
Chrome OS File Browser: time to load the suggest apps dialog. Measured
between the moment window appears and the moment all the contants in the
dialog including the Chrome Webstore widget are ready.
joshwoodward@google.com
File types that were tried to be viewed through browser. This is recorded
when the user tries to view a file from Files.app.
kinaba@chromium.org
Chrome OS File Browser: counts the number of times volumes are mounted for
each volume type.
tzik@chromium.org
The result of FileSystemDirectoryDatabase initialization.
tzik@chromium.org
The success or the cause of failure for each call to OpenFileSystem().
tzik@chromium.org
The result of FileSystemOriginDatabase initialization.
tzik@chromium.org
Number of origins that have persistent filesystem. Measured when the Quota
system queries the filesystem subsystem about its entire usage, which
usually happens when one of the storage subsystem methods is called for the
first time.
tzik@chromium.org
Number of origins that have temporary filesystem. Measured when the Quota
system queries the filesystem subsystem about its entire usage, which
usually happens when one of the storage subsystem methods is called for the
first time.
jianli@chromium.org
Number of times when gcm.unregister API is called.
jianli@chromium.org
Length of time taken to complete a GCM checkin request successfully. If the
checkin is retried multiple times, the length of time is counted for the
last successful retry.
juyik@chromium.org
Status code of the outcome of a GCM checkin request.
jianli@chromium.org
Number of retries before a GCM checkin succeeds.
zea@chromium.org
Whether the GCM connection was made via a proxy or not.
zea@chromium.org
Net error results from GCM disconnect events.
zea@chromium.org
Number of connections made to each specific MCS endpoint.
zea@chromium.org
Net error results from GCM connection attempts.
juyik@chromium.org
The time between the initiation of a connection and the successful
completion of it.
zea@chromium.org
Reasons for GCM connection resets.
zea@chromium.org
GCM connection success rate. Does not take into account login success. See
GCM.ConnectionFailureErrorCode for a breakdown of connection failure
reasons.
zea@chromium.org
Time (from login until reset) that a GCM connection was active.
juyik@chromium.org
Interval between two successive received data message bursts.
juyik@chromium.org
The time between the successful completion of the connection and the arrival
of the first data message.
zea@chromium.org
If a heartbeat was missed, the time delta by which it was missed (in system
time, not ticks).
jianli@chromium.org
Status code of loading from the persistent GCM store.
Deprecated as of 2/2015.
zea@chromium.org
Success indicates successfully loading an initialized persistent GCM store
at startup time. Failure indicates a failure loading the store.
zea@chromium.org
Number of applications hitting GCM per-app outstanding message limits at
startup time.
Deprecated as of 3/2014.
zea@chromium.org
Number of GCM users associated with this client at startup time.
jianli@chromium.org
Category of TTL specified in the outgoing message: 0, less than or equal to
1 minute, less than or equal to 1 hour and etc.
juyik@chromium.org
Number of messages in a received GCM data message burst.
juyik@chromium.org
Interval between messages within a received GCM data message burst.
jianli@chromium.org
Length of time taken to complete a GCM registration request successfully. If
the registration is retried multiple times, the length of time is counted
for the last successful retry.
juyik@chromium.org
Status code of the outcome of a GCM registration request.
jianli@chromium.org
Number of retries before a GCM registration succeeds.
jianli@chromium.org
Number of sender IDs specified in a registration request.
jianli@chromium.org
Reports the problem encountered when resetting the GCM store.
zea@chromium.org
Number of unacknowledged incoming messages restored from the persistent
store at startup.
zea@chromium.org
Number of pending outgoing messages restored from the persistent store at
startup.
jianli@chromium.org
Number of registrations restored from the persistent store at startup.
zea@chromium.org
Success indicates successfully destroying the GCM persistent store. Failure
indicates a failure destroying the persistence store. GCM store will be
destroyed when the profile has been signed out.
zea@chromium.org
Size of the GCM persistent store in kilobytes at startup.
zea@chromium.org
Success indicates successfully updating the GCM persistent store on message
update. Failure indicates a failure updating the persistence store.
jianli@chromium.org
Length of time taken to complete a GCM unregistration request successfully.
If the unregistration is retried multiple times, the length of time is
counted for the last successful retry.
juyik@chromium.org
Status code of the outcome of a GCM unregistration request.
jianli@chromium.org
Number of retries before a GCM unregistration succeeds.
jianli@chromium.org
Indicates whether the user was signed in when GCM started up.
pavely@chromium.org
Status of parsing incoming invalidations message from GCM channel.
pavely@chromium.org
Status of sending outgoing invalidations message through GCM.
Please list the metric's owners. Add more owner tags as needed.
Result of the authentication for Drive.
Deprecated 9/2012, and replaced by Drive.EntireFeedLoadTime
Please list the metric's owners. Add more owner tags as needed.
Time spent to load the entire file system information from the server
Deprecated 9/2012, and replaced by Drive.EntryKind
Please list the metric's owners. Add more owner tags as needed.
Provides breakdown of specific formats for hosted documents. Recorded when
feed is loaded from the server.
Deprecated 9/2012, and replaced by Drive.InitialFeedLoadTime
Please list the metric's owners. Add more owner tags as needed.
Time spent to load the initial part of the file system information from the
server
Deprecated 9/2012, and replaced by Drive.NumberOfHostedDocuments
Please list the metric's owners. Add more owner tags as needed.
Number of hosted documents (spreadsheets etc.) on Drive. Logged when Drive
is first accessed.
Deprecated 9/2012, and replaced by Drive.NumberOfRegularFiles
Please list the metric's owners. Add more owner tags as needed.
Number of regualr files on Drive. Logged when Drive is first accessed.
Deprecated 9/2012, and replaced by Drive.NumberOfTotalFiles
Please list the metric's owners. Add more owner tags as needed.
Number of total files (regualr files + hosted documents) on Drive. Logged
when Drive is first accessed.
mvanouwerkerk@chromium.org
Whether high accuracy geolocation information was requested.
Deprecated 9/2014, and replaced by
ContentSettings.PermissionActions_Geolocation.
mvanouwerkerk@chromium.org
Events in GeolocationInfoBarDelegate.
Deprecated 9/2014, and replaced by
ContentSettings.PermissionActions_Geolocation.
mvanouwerkerk@chromium.org
Events in GeolocationInfoBarDelegateAndroid.
mvanouwerkerk@chromium.org
Error code for the geoposition sent to the renderers.
mvanouwerkerk@chromium.org
The number of WiFi access points used to determine geolocation.
mvanouwerkerk@chromium.org
Events in NetworkLocationRequest.
mvanouwerkerk@chromium.org
Http response codes in NetworkLocationRequest.
robliao@chromium.org
skare@chromium.org
Types of cards which received an index 0 button click.
robliao@chromium.org
skare@chromium.org
Types of cards which received an index 1 button click.
robliao@chromium.org
skare@chromium.org
Types of cards which received a notification click.
robliao@chromium.org
skare@chromium.org
Events in Google Now component extension.
robliao@chromium.org
skare@chromium.org
Count of the number of Google Now notifications visible when the message
center/notification center is shown.
kmadhusu@chromium.org
Counts number of Google searches from various access points in the browser.
WARNING: Do not use this histogram as it currently fails to classify a large
percentage of Omnibox searches correctly - http://crbug.com/421631.
gab@chromium.org
The effective update policy for Chrome on Windows. Recorded once per startup
(following a 45 seconds delay).
grt@chromium.org
The HRESULT for a failed on-demand update check.
yfriedman@chromium.org
dfalcantara@chromium.org
(Android-only) Records what action the user took (if any) on the InfoBar
indicating that a new version of Chrome is available.
yfriedman@chromium.org
dfalcantara@chromium.org
(Android-only) The amount of time which the InfoBar indicating a new version
is available is visible.
grt@chromium.org
The exit code from Chrome's installer following a failed on-demand update
check. All values reported for this histogram fall in the
GOOGLE_UPDATE_ERROR_UPDATING bucket of the GoogleUpdate.UpdateErrorCode
histogram and the GOOPDATEINSTALL_E_INSTALLER_FAILED bucket of the
GoogleUpdate.ErrorHresult histogram.
grt@chromium.org
An unrecognized CurrentState value received from Google Update while polling
for the status of an on-demand update check.
grt@chromium.org
The error code for a failed on-demand update check.
Please list the metric's owners. Add more owner tags as needed.
True if the effective update policy for Chrome on Windows is the result of
an app-specific override; false if it is the default for all apps. Recorded
once per startup (following a 45 seconds delay).
grt@chromium.org
The result of an on-demand update check.
vangelis@chromium.org
Refresh rate of the display in Hz. This is recorded every time we present a
frame.
jmadill@chromium.org
An extended Windows error code returned from D3D11CreateDevice on error. Can
be almost any valid HRESULT or DXGI error code, which are listed at
https://msdn.microsoft.com/en-us/library/windows/desktop/bb509553.aspx.
jmadill@chromium.org
The time that elapses for the initial call to D3D11CreateDevice on D3D11
ANGLE. A pure system call, with no ANGLE or Chromium code, called once every
GPU process startup.
jmadill@chromium.org
The maxmium supported (or currently requested) Direct3D feature level in
D3D11 ANGLE. We support as low as 9.3, and as high as 11.1, though Chrome
should only use 10.0+ for D3D11. Gives an indication of how new a user's
video card is, what features it supports, and it's general speed tier.
jmadill@chromium.org
The result from initializing a D3D11 device in ANGLE. Can be success, or one
of several error codes which indicate different reasons for failing.
jmadill@chromium.org
The result from initializing a D3D9 device in ANGLE. Can be success, or one
of several error codes which indicate different reasons for failing.
jmadill@chromium.org
Windows computers running Windows 8+, or running Windows 7 with a platform
update, support the newer version of DXGI. This update also indicates the
computer is capable of running Direct3D 11.1 if the hardware supports it.
vangelis@chromium.org
The time that the GPU process spends collecting driver information during
startup.
sievers@chromium.org
The reason a GPU command buffer context of a given type was lost.
vangelis@chromium.org
The time that the browser process takes to create the compositor from its
point of view. One of these is created for each top-level window (browser
frame, menus, etc.).
jmadill@chromium.org
ANGLE's currently active D3D shader model version. Logged once every startup
of the GPU process, on Windows only. Note that Shader Models 2 and 3 map to
D3D9 with ANGLE, and 4+ map to D3D11 ANGLE.
reveman@chromium.org
Whether GLFence support is available. Recorded each time a new context group
is initialized and extensions are detected.
jmadill@chromium.org
The time that the GPU process spends in initializing the GL surface, and
collecting graphics information. Records times up to three minutes.
Deprecated 4/2015.
vangelis@chromium.org
The time that the GPU process spends in initializing the GL surface, and
collecting graphics information.
reveman@chromium.org
Whether RG texture support is available. Recorded each time a new context
group is initialized and extensions are detected.
erikchen@chromium.org
The number of displays present right after the user has attached or detached
a new display. Excludes mirrored displays, but includes sleeping displays.
erikchen@chromium.org
The number of displays present at start up. Excludes mirrored displays, but
includes sleeping displays.
dbeam@chromium.org
Whether a drive has a seek penalty (i.e. is a spinning disk). Emitted 0-2
times shortly after startup when constructing the initial UMA log.
dbeam@chromium.org
Whether it was possible to determine if a drive has a seek penalty. This can
fail for various reasons (device drivers don't offer this information, the
drive is still mounting, lack of access, etc.). Emitted twice shortly after
startup when constructing the initial UMA log.
dbeam@chromium.org
The amount of time it takes to determine whether a drive has a seek penalty.
Emitted twice shortly after startup when constructing the initial UMA log.
merkulova@chromium.org
Which HID were detected when user pressed Continue on OOBE dialog. This
metric is specific to ChromeOS.
merkulova@chromium.org
Whether HID detection dialog was shown on OOBE. Logged on screen show or on
screen skip respectively. This metric is specific to ChromeOS.
merkulova@chromium.org
Records number of times the dialog was shown by the time OOBE is completed.
This metric is specific to ChromeOS.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a browser for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency MAY appear time and
again as the same corrupt histogram is examined for each potenital UMA
upload.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a browser for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency will only appear at
most one time for each histogram in a single process (i.e., duplicate
corruption in a single histogram is not noted in this chart.)
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a child process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency MAY appear time and
again as the same corrupt histogram is examined for each potenital UMA
upload.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a child process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency will only appear at
most one time for each histogram in a single process (i.e., duplicate
corruption in a single histogram is not noted in this chart.)
Deprecated 7/2012.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a renderer for transmission to the browser. Inconsistent data is
NOT transmitted to the browser. Each type of inconsistency is a bit, and
all bits found in one histogram examination are added together to summarize
the inconsistent event. Note that the same inconsistency MAY appear time
and again as the same corrupt histogram is examined for each potenital UMA
upload.
Deprecated 7/2012.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a renderer for transmission to the browser. Inconsistent data is
NOT transmitted to the browser. Each type of inconsistency is a bit, and
all bits found in one histogram examination are added together to summarize
the inconsistent event. Note that the same inconsistency will only appear
at most one time for each histogram in a single renderer process (i.e.,
duplicate corruption in a single histogram is not noted in this chart.)
asvitkine@chromium.org
The number of extra samples counted in the redundant_count in a histogram
that were not found by summing the samples in the buckets.
asvitkine@chromium.org
The number of missing samples in the redundant_count in a histogram that
were found by summing the samples in the buckets.
asvitkine@chromium.org
The amount of discrepancy found when examining a single histogram's data in
the browser process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA.
asvitkine@chromium.org
The amount of discrepancy found when examining a single histogram's data in
a child process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA.
Deprecated 7/2012.
asvitkine@chromium.org
The amount of discrepancy found when examining a single histogram's data in
a renderer process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA.
Please list the metric's owners. Add more owner tags as needed.
Count of "History Index *" databases deleted. These databases
stored the full-text-search data for history, which was removed at r213442,
this histogram tracks cleanup.
rogerm@chromium.org
The wall-clock time taken to gather favicon database metrics. Metrics are
logged on initialization of the Favicon DB on 1% of starts.
rogerm@chromium.org
Size of the Favicons database in MB. This is calculated as the number of
pages consumed by the database multiplied by the page size. Logged on
initialization of the Favicon DB on 1% of starts.
rpop@google.com
Size of the recovered Favicons database relative to the original corrupt
database. Recovery is VACUUM-like, so the resulting database should always
be smaller. Substantial 100% results would indicate empty databases being
recovered, substantial low% results would indicate very little data being
recovered.
rpop@google.com
Rows recovered from [favicon_bitmaps] table in Favicons recovery.
rpop@google.com
Rows recovered from [favicons] table in Favicons recovery.
rpop@google.com
Rows recovered from [icon_mapping] table in Favicons recovery.
rpop@google.com
Track results of SQLite database recovery code in thumbnail_database.cc.
yiyaoliu@chromium.org
The count of differences between cached top sites and up-to-date top sites
when function TopSitesImpl::SetTopSites is firstly called at startup.
yiyaoliu@chromium.org
The amount of time for function
history::TopSitesBackend::UpdateTopSitesOnDBThread to execute when this
function is called during startup. Excludes the case where local
TopSitesDatabase db_ is unavailable, i.e. where the update doesn't really
happen.
rkaplow@chromium.org
The amount of time that elapsed during HistoryService::Init.
rogerm@chromium.org
The total number of favicon bitmaps (of all sizes) cached in a user's
Favicon database. A given favicon URL may be associated with multiple
bitmaps (of different sizes). Logged on initialization of the Favicon DB on
1% of starts.
rogerm@chromium.org
The number of page URL (e.g., http://www.google.com) to favicon URL (e.g.,
http://www.google.com/favicon.ico) mappings stored in a user's Favicon
database. Logged on initialization of the Favicon DB on 1% of starts.
rogerm@chromium.org
The total number of favicon URLs (e.g. http://www.google.com/favicon.ico)
tracked in a user's Favicon database. This metric tracks knowledge of a
favicon URL not whether there are cached bitmaps for that favicon URL. See
History.NumFaviconBitmapsInDB for that. Logged on initialization of the
Favicon DB on 1% of starts.
rogerm@chromium.org
The total number of large (>= 64 pixels wide) favicons being tracked in a
user's Favicon database. This is a subset of History.NumFaviconBitmapsInDB,
which includes all sizes in its count. Logged on initialization of the
Favicon DB on 1% of starts.
rogerm@chromium.org
The total number of touch icons being tracked in a user's Favicon database.
This is a subset of History.NumFaviconsInDB, which includes all icon types
in its count. Logged on initialization of the Favicon DB on 1% of starts.
Please list the metric's owners. Add more owner tags as needed.
Size of the recovered TopSites database relative to the original corrupt
database. Recovery is VACUUM-like, so the resulting database should always
be smaller. Substantial 100% results would indicate empty databases being
recovered, substantial low% results would indicate very little data being
recovered.
Please list the metric's owners. Add more owner tags as needed.
Rows recovered from [thumbnails] table in TopSites recovery.
Please list the metric's owners. Add more owner tags as needed.
The TopSites recovery code is written conservatively, with successful
recovery committed and any failure leading to rollback. This tracks the
outcomes to determine which cases are high-frequency enough to warrant
adding additional code to handle them (versus simply deleting the data).
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
Page visits to each of a user's top 50 sites. Visits to all other sites go
into the 51st bucket. Only count the page visit if it came from user
browsing and only count it once when cycling through a redirect chain.
Deprecated because only the execution time at startup is of interest. See
histogram History.UpdateTopSitesOnDBThread_Startup_Time.
yiyaoliu@chromium.org
The amount of time for function
history::TopSitesBackend::UpdateTopSitesOnDBThread to execute. Excludes the
case where local TopSitesDatabase db_ is unavailable, i.e. where the update
doesn't really happen.
rpop@google.com
Number of entries that the clicked entry is older than in History page. Last
bucket is any entry of that value or higher.
rpop@google.com
Subset of the Click Position histogram. Contains only the first smaller
subset of entries on the page. Number of entries that the clicked entry is
older than in History page. Last bucket is entries of that value or higher.
mad@chromium.org
rpop@google.com
Histogram for usage of the section in the history page that allows the user
to access tabs from other devices.
rpop@google.com
Number of entries that the deleted entry is older than in History page. Last
bucket is any entry of that value or higher. Confirmed removal is not
guaranteed, just an initiation of 'Remove selected items'.
rpop@google.com
Subset of Remove Entry Position histogram. Contains only the first smaller
subset of entries on the page. Number of entries that the deleted entry is
older than in History page. Last bucket is any entry of that value or
higher. Confirmed removal is not guaranteed, just an initiation of 'Remove
selected items'.
rlp@chromium.org
The state of the hotword audio logging preference. This value is emitted
each time the hotword availability is requested by the extension if the user
is also opted in to hotword voice search. This check typically happens each
time a hotword search is initiated.
rlp@chromium.org
The state of the hotword preference. This value is emitted during
HotwordService initialization which happens during Profile initialization.
rlp@chromium.org
Whether the external component hotword extension exists (i.e., not pending
download, disabled, etc.). This value is emitted each time the hotword
availability is requested by the extension which typically happens each time
a hotword search is initiated.
rlp@chromium.org
Errors reported by the hotword service when determining if hotwording is
available. Non-errors are also reported so that errors can be seen as a
percentage of total requests.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Success or error when attempting to open a MediaStream for the microphone.
At most one success or error will be logged for an attempt to open a stream.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Timeout occured while waiting for a message from the NaCl hotword detector
plugin. This value is the message that was expected to be received from the
plugin.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Success or error when attempting to load the NaCl hotword detector plugin.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Location of hotword trigger. Emitted every time the hotword is triggered by
the user saying 'Ok Google'.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Language, switched to by the user, that triggered a hotword shared module
reinstall.
ricea@chromium.org
The time spent performing an asynchronous revalidation that was triggered by
a Cache-Control: stale-while-revalidate directive. This is recorded when the
asynchronous revalidation completes, either after the response was
completely read or an error occurred. One entry is recorded for each
asynchronous revalidation that is performed.
jkarlin@chromium.org
The time spent waiting for write lock on a disk cache entry.
ricea@chromium.org
Count of the number of external (ie. from Blink) conditionalized requests,
and whether or not those requests could have been served from the browser
cache.
Deprecated 4/2015.
Please list the metric's owners. Add more owner tags as needed.
Result of a main page HttpCacheTransaction if offline mode had been enabled.
Please list the metric's owners. Add more owner tags as needed.
Net error results from non-restartable cache read errors.
Please list the metric's owners. Add more owner tags as needed.
Net error results from restartable cache read errors.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
The type of Vary header for a given GET response.
gab@chromium.org
The importer used on first run Auto Import.
gab@chromium.org
The importer used on import from the bookmarks file API.
gab@chromium.org
The importer used on import from the chrome://settings/importData UI.
Please list the metric's owners. Add more owner tags as needed.
The amount of time from install time to time that user opens import dialog
from BookmarkBarView.
Please list the metric's owners. Add more owner tags as needed.
The amount of time from install time to time that user opens import dialog
from NTP floating BookmarkBarView.
Deprecated and replaced by Import.ShowDialog.FromBookmarkBarView
Please list the metric's owners. Add more owner tags as needed.
The amount of time from install time to time that user opens import dialog
from BookmarkBarView.
Deprecated and replaced by Import.ShowDialog.FromFloatingBookmarkBarView
Please list the metric's owners. Add more owner tags as needed.
The amount of time from install time to time that user opens import dialog
from NTP floating BookmarkBarView.
rvargas@chromium.org
Count of various failures in ImportantFileWrite when manipulating a temp
file to write to before moving it into place (replacing another file).
timvolodine@chromium.org
Whether the Sensor.TYPE_LINEAR_ACCELERATION was available at the start of
Device Motion.
timvolodine@chromium.org
Whether the Sensor.TYPE_ACCELEROMETER was available at the start of Device
Motion.
timvolodine@chromium.org
Whether the SENSOR_TYPE_ACCELEROMETER_3D was available at the start of
Device Motion on the Windows platform.
timvolodine@chromium.org
Provides a histogram of the base sensors (if any) that are used at the start
of the Device Orientation API. Currently Sensor.TYPE_ROTATION_VECTOR is the
default sensor for orientation, if it's not available fall-back option is
provided by using Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_MAGNETIC_FIELD.
timvolodine@chromium.org
Whether the SENSOR_TYPE_GYROMETER_3D was available at the start of Device
Motion on the Windows platform.
timvolodine@chromium.org
Whether the Sensor.TYPE_GYROSCOPE was available at the start of Device
Motion.
timvolodine@chromium.org
Whether the SENSOR_TYPE_INCLINOMETER_3D was available at the start of Device
Orientation on the Windows platform.
timvolodine@chromium.org
This histogram counts the number of Device Motion API invocations in the
default implementation (Linux and CrOS). The default implementation does not
provide any sensors so the result is always false.
timvolodine@chromium.org
Whether the sudden motion sensor was available at the start of Device Motion
on the MacOS platform.
timvolodine@chromium.org
This histogram counts the number of Device Orientation API invocations in
the default implementation (Linux and CrOS). The default implementation does
not provide any sensors so the result is always false.
timvolodine@chromium.org
Whether the sudden motion sensor was available at the start of Device
Orientation on the MacOS platform.
Deprecated 11/2014 (crbug.com/347507). Replaced by
InertialSensor.DeviceOrientationSensorAndroid.
timvolodine@chromium.org
Whether the Sensor.TYPE_ROTATION_VECTOR was available at the start of Device
Orientation.
shuchen@chromium.org
The number of active input methods. Recorded when the user logs in to Chrome
OS. The active input methods are selected by user in the language settings
page.
shuchen@chromium.org
The auto-correction level for suggestion engine.
shuchen@chromium.org
The breakdown of input method usage by input method category. Recorded when
the system changes the current input method.
shuchen@chromium.org
The suggestion index (1-based) of the suggestion list item which user
chooses to commit.
Deprecated 03/2015, and replaced by InputMethod.Commit.Type2.
shuchen@chromium.org
The suggestion accuracy type which the user chooses to commit.
shuchen@chromium.org
The suggestion accuracy type which the user chooses to commit.
shuchen@chromium.org
The number of characters committed with composition text.
shuchen@chromium.org
The breakdown of input method usage by input method IDs. Recorded when the
user presses keys on physical or on-screen keyboard.
shuchen@chromium.org
The trigger type of input method switches by user.
shuchen@chromium.org
The suggestion index (1-based) of the suggestion list item which user
chooses to commit for physical keyboard autocorrect.
shuchen@chromium.org
The suggestion accuracy type which the user chooses to commit for physical
keyboard autocorrect.
shuchen@chromium.org
The number of times the backspace key was pressed on the virtual keyboard,
while the virtual keyboard was alive. Recorded when the virtual keyboard is
closed.
shuchen@chromium.org
The layout type of the virtual keyboard, recorded when backspace is pressed.
rsadam@chromium.org
ChromeOS histogram that counts the number of times the cursor was moved to
the previous word by swiping backwards on the selection track. The count is
initialized when the user starts swiping from any side of the virtual
keyboard, incremented based on how far they swipe backwards on the selection
track, and recorded when they release their finger.
rsadam@chromium.org
Counts the length of text typed by the virtual keyboard between each
backspace. This metric provides a rough approximation of an error rate for
the virtual keyboard.
rsadam@chromium.org
The total number of characters committed. Recorded when the virtual keyboard
is closed.
shuchen@chromium.org
How long the virtual keyboard was visible.
shuchen@chromium.org
The on-screen keyboard initialization latency in milliseconds.
shuchen@chromium.org
The layout of the on-screen keyboard. Logged when the specific layout is
shown.
shuchen@chromium.org
The count of layout switching actions while virtual keyboard is alive.
Recorded when the virtual keyboard window is hidden or destroyed.
rsadam@chromium.org
ChromeOS histogram that counts the number of times the cursor was moved to
the next word by swiping forward on the selection track. The count is
initialized when the user starts swiping from any side of the virtual
keyboard, incremented based on how far they swipe forwards on the selection
track, and recorded when they release their finger.
stevet@chromium.org
The number of times the virtual keyboard was tapped while the virtual
keyboard was alive. Recorded when the virtual keyboard is closed.
rsadam@chromium.org
ChromeOS histogram that tracks the total number of words that were deleted
by swiping forward on the deletion track. The count is initialized when the
user starts swiping on the backspace key, incremented based on how far they
swipe forwards on the deletion track, and recorded when they release their
finger.
rsadam@chromium.org
The number of words typed per minute. Recorded when the virtual keyboard is
closed.
rsadam@chromium.org
ChromeOS histogram that tracks the total number of words that were restored
by swiping backwards on the deletion track. The count is initialized when
the user starts swiping on the backspace key, incremented based on how far
they swipe backwards on the deletion track, and recorded when they release
their finger.
zeuthen@chromium.org
The number of update attempts until the update has been applied. This is
reported every time the device has completed an update.
zeuthen@chromium.org
Errors from update_engine process when running in dev mode.
zeuthen@chromium.org
The overhead in downloading extra bytes due to errors/interruptions.
Expressed as a percentage of the bytes that are actually needed to be
downloaded for the update to be successful.
zeuthen@chromium.org
The combinations of protocol and source server that were used to complete a
successful update.
zeuthen@chromium.org
The number of update attempts with a full update payload until the update
has been applied. This is reported on every update attempt.
zeuthen@chromium.org
The source used to provision the install-date-days value sent to Omaha with
every request. This is reported when OOBE completes (M34 or later) or when
upgrading to a version with install-date-days support.
zeuthen@chromium.org
Errors from update_engine process when running in normal mode.
zeuthen@chromium.org
The age of the OS, defined as the age of the /etc/lsb-release file. This is
reported on every update check but at most once a day.
zeuthen@chromium.org
The number of update attempts until the update has been applied. This is
reported on every update attempt.
zeuthen@chromium.org
The type of update payload used to update the device. The difference between
"Full" and "Forced Full" is that in the latter, the
request sent to Omaha included a directive saying that a delta payload
wasn't accepted. A "Full" payload is one where a delta payload was
accepted but Omaha provided a full payload. This is reported every time the
device has completed an update.
zeuthen@chromium.org
The number of consecutive times a device has failed to boot an update that
successfully applied. This metric is reported every time the firmware fails
to boot the slot with the update and fell back to the slot it originally
updated from.
zeuthen@chromium.org
Number of MBs downloaded from during an update that completed successfully.
zeuthen@chromium.org
Wall-clock duration between when an update has successfully completed (and
the user is presented with the "reboot arrow") and when the system
has booted into the new update. This is reported every time the device is
rebooted after an update has been applied.
zeuthen@chromium.org
Total number of MBs downloaded since the last successful update. This also
includes all the bytes downloaded during any prior failed attempts.
zeuthen@chromium.org
Absolute wall-clock time duration it took for the update to complete from
the time an update first began. It includes not just the time the device
was up, but also includes the time the device spent sleeping.
zeuthen@chromium.org
Uptime duration it took for the update to complete from the time an update
first began. It does not include the time the device spent sleeping, but it
does include the uptime spent in waiting for the hourly update checks to
happen.
zeuthen@chromium.org
Number of times the device was rebooted by the user since an update began
and until it completed successfully.
zeuthen@chromium.org
The number of update attempts that didn't complete because a newer update
was detected during the update operation. This is reported every time the
device has completed an update.
zeuthen@chromium.org
The number of consecutive different abandoned update payloads since the last
successful update. This is reported every time an update payload is
abandoned because a newer update payload is available.
zeuthen@chromium.org
Number of times the download URLs were switched due to failures.
Deprecated 4/2015. It appears the code at some point changed to use the
histogram name 'ExtensionInstallSigner.InvalidCount' and we forgot to update
this histogram name.
Please list the metric's owners. Add more owner tags as needed.
This is a count of the number of ids that we asked to be signed which the
server response indicated were not in the webstore.
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallSigner.ResultWasValid.
Please list the metric's owners. Add more owner tags as needed.
The extensions install signer got a well-formed result from the server but
the signature check on it failed.
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.GetSignatureResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier tried to get a new signature and received a
response but it wasn't properly signed.
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.GetSignatureResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier tried to get a new signature but was unable
to (network error contacting the server, response from server was malformed,
etc.).
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.GetSignatureResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier got a new signature from the server that was
valid.
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.InitResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier found a valid signature at startup, and this
is a count of the number of signed ids it contained.
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.InitResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier found a signature in the prefs at startup,
and it parsed properly, but it was invalid (some ids may have been
added/removed, could not verify it was signed with the correct private key,
etc.).
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.InitResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier did not find any signature in the prefs at
startup.
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.InitResult.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier found a signature in the prefs at startup,
but it wasn't parseable (missing/wrong format of required keys, etc.).
Deprecated 1/2014 (crbug.com/333934). Replaced by
ExtensionInstallVerifier.MustRemainDisabled.
Please list the metric's owners. Add more owner tags as needed.
The extension install verifier would have disabled an extension but is not
in enforcement mode.
Please list the metric's owners. Add more owner tags as needed.
Records various events of interest in the InstantController. E.g. When URLs
are blacklisted.
Please list the metric's owners. Add more owner tags as needed.
How often an Instant preview is committed onto a different tab than it was
created from.
Please list the metric's owners. Add more owner tags as needed.
The time between the first Omnibox interaction and when the Instant preview
shows. If the instant preview was already showing when the user interacted
with the omnibox, this histogram is not recorded.
beaudoin@chromium.org
Records a histogram for how often the Cacheable NTP fails to load.
Depcreated as of 10/2013. No longer relevant since the HTML overlay was
abandoned.
Please list the metric's owners. Add more owner tags as needed.
Records the cause for falling back to a local overlay at the time of
fallback.
Deprecated as of 10/2013. This histogram is no longer relevant since the
HTML overlay went away.
Please list the metric's owners. Add more owner tags as needed.
Records a histogram for instant extended (Local NTP and Online NTP) and
non-extended navigations.
Deprecated as of 11/2013.
Please list the metric's owners. Add more owner tags as needed.
Records, on startup, whether the user has chosen to opt-in to or opt-out of
InstantExtended via chrome://flags.
Deprecated 2013-06. As of m30 use InstantExtended.NewOptInState.
Please list the metric's owners. Add more owner tags as needed.
Records, on startup, whether the user has chosen to opt-in to or opt-out of
InstantExtended via chrome://flags.
Deprecated 2013-07. Please see
InstantExtended.PercentageMatchV2_QuerytoQuery instead.
Please list the metric's owners. Add more owner tags as needed.
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a search query to another search query.
Deprecated 2013-07. Please see InstantExtended.PercentageMatchV2_QuerytoURL
instead.
Please list the metric's owners. Add more owner tags as needed.
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a search query to a url. Example: Accidental search for
google.con, then navigation to google.com.
Deprecated 2013-07. Please see InstantExtended.PercentageMatchV2_URLtoQuery
instead.
Please list the metric's owners. Add more owner tags as needed.
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a url to a search query.
Deprecated 2013-07. Please see InstantExtended.PercentageMatchV2_URLtoURL
instead.
Please list the metric's owners. Add more owner tags as needed.
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a url to another url.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a search query to another search query.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a search query to a url. Example: Accidental search for
google.con, then navigation to google.com.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a url to a search query.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a url to another url.
Deprecated 2013-06. This preference has not been exposed or used for months,
and we do not plan to use it in the future.
Please list the metric's owners. Add more owner tags as needed.
Records, on startup, the value of the "Allow your search engine to
provide Instant result" preference setting for the first profile
loaded.
ksimbili@chromium.org
Records the scroll state on the preview page when instant search clicks
feature is triggered.
ksimbili@chromium.org
Records the reason that triggered the page swap when instant search clicks
feature is triggered.
ksimbili@chromium.org
The time spent by the user in preview page before swapping to original or
navigating out of preview page.
ksimbili@chromium.org
The time it took for swap to trigger for all swaps. The is the time between
preview page load start to preview page swap with the original page.
ppi@chromium.org
Estimated additive skew between processes, recorded if the browser process
is ahead (higher TimeTicks value) than the renderer process.
ppi@chromium.org
Estimated additive skew between processes, recorded if the browser process
is behind (lower TimeTicks value) than the renderer process.
ppi@chromium.org
True iff the conversion from the browser process TimeTicks to renderer
process TimeTicks is done by adding a constant, without scaling.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, which
may be either accept or deny. This is only recorded for overridable SSL
warnings with a CERT_AUTHORITY_INVALID warning. Timing begins when user
first focuses on the page.
meacer@chromium.org
User action when the user is shown a captive portal error page.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, which
may be either accept or deny. This is only recorded for overridable SSL
warnings with a CERT_COMMON_NAME_INVALID warning. Timing begins when user
first focuses on the page.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, which
may be either accept or deny. This is only recorded for overridable SSL
warnings with a CERT_DATE_INVALID warning. Timing begins when user first
focuses on the page.
felt@chromium.org
User decision when presented with a security interstitial. As of M44,
subresource interstitials were split into their own entries.
felt@chromium.org
User decision when presented with a security interstitial, on a site that
the user had previously visited. As of M44, subresource interstitials were
split into their own entries.
felt@chromium.org
User interactions with a security interstitial. As of M44, subresource
interstitials were split into their own entries.
Replaced by interstitial.ssl_overridable.* and
interstitial.ssl_nonoverridable.* in Jan 2015 (M42).
felt@chromium.org
User action when the user is shown a SSL interstitial. SHOW_ALL and MORE
refer to the total number of SSL errors; all of the other numbers pertain to
the number of actions related to SSL errors that are overridable. The counts
do not sum to 100%; SHOW_ALL is a superset of SHOW_OVERRIDABLE, which in
turn will be a supserset of the PROCEED/DONT_PROCEED variables.
SHOW_UNDERSTAND is only being used by an experimental field trial. The
interstitials due to captive portals are now recorded in the
"SSLCaptivePortal".
meacer@chromium.org
Record possible states of captive portals. This histogram is emitted
(possibly multiple times to different buckets) whenever a ssl interstitial
page is displayed and captive portal detection is enabled. The captive
portal technique forces a client on a network to see a special web page
(usually for authentication purposes) before using the internet normally.
felt@chromium.org
Possible non-attack causes of the non-overridable SSL interstitial. Many
errors are not reported in this histogram and new errors may be added over
time, therefore one should not look at the breakdown of this histogram (one
bucket divided by the sum) because that will be inaccurate. Instead, one
should look at each bucket count divided by the count of the ssl errors of
that type. E.g. WWW mismatch is recorded only when the ssl error is
CERT_COMMON_NAME_INVALID, so one should look at the bucket count of WWW
mismatch divided by the bucket count of CERT_COMMON_NAME_INVALID in the
histogram interstitial.ssl_error_type.
felt@chromium.org
Possible non-attack causes of the overridable SSL interstitial. Many errors
are not reported in this histogram and new errors may be added over time,
therefore one should not look at the breakdown of this histogram (one bucket
divided by the sum) because that will be inaccurate. Instead, one should
look at each bucket count divided by the count of the ssl errors of that
type. E.g. WWW mismatch is recorded only when the ssl error is
CERT_COMMON_NAME_INVALID, so one should look at the bucket count of WWW
mismatch divided by the bucket count of CERT_COMMON_NAME_INVALID in the
histogram interstitial.ssl_error_type.
felt@chromium.org
The histogram shows the connection types associated with SSL warnings. E.g.,
do more warnings occur on WiFi?
jww@chromium.org
Specifies when a user enters the page info menu whether or not the user
pressed the SSL decisions revoke button. This can only by done if the user
is in the "Remember Certificate Error Decisions" experiment. This
is logged when the page info UI is closed.
jww@chromium.org
Records when a user has made a decision to proceed on a nonoverridable SSL
interstitial. Also records whether a prior decision had been made but the
decision expired.
jww@chromium.org
Records when a user has made a decision to proceed on an overridable SSL
interstitial. Also records whether a prior decision had been made but the
decision expired.
jww@chromium.org
Emitted when a good certificate is seen, specifying whether the user already
gave an exception for a bad certificate for the same host.
Deprecated Jan 2015 (M42).
felt@chromium.org
The likelihood of a |CERT_AUTHORITY_INVALID| error being an attack.
Deprecated Jan 2015 (M42).
felt@chromium.org
The likelihood of a |CERT_COMMON_NAME_INVALID| error being an attack.
Deprecated Jan 2015 (M42).
felt@chromium.org
The likelihood of a |CERT_DATE_INVALID| error being an attack.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, when
the user accepts the SSL warning. This is only recorded for overridable SSL
warnings. Timing begins when user first focuses on the page.
meacer@chromium.org
The type of action that the SSL error handler takes.
felt@chromium.org
The type of SSL error that the user encounters. This is recorded for all
SSL warnings, regardless of whether they are overridable.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, when
the user rejects the SSL warning. This is only recorded for overridable SSL
warnings. Timing begins when user first focuses on the page.
pavely@chromium.org
Network channel used for invalidations.
Please list the metric's owners. Add more owner tags as needed.
The time between keystrokes in Aura text fields. The only keystrokes that
are measured are ones that produce a printable character and are not over 5
seconds apart.
Please list the metric's owners. Add more owner tags as needed.
Accept languages.
Please list the metric's owners. Add more owner tags as needed.
Application languages used for UI.
dfalcantara@chromium.org
Records how Chrome handled a launch from an Android Home screen shortcut.
dfalcantara@chromium.org
Records whether or not an invalid Android Intent was fired to launch Chrome.
(http://crbug.com/445136)
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
complex text fragments, the average number of microseconds spent laying out
each node.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
floats, the average number of microseconds spent laying out each node.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, the average number of
microseconds spent laying out each node.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
fixed or absolute positioned, the average number of microseconds spent
laying out each node.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
simple text fragments, the average number of microseconds spent laying out
each node.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
table cells, the average number of microseconds spent laying out each node.
Deprecated 2013-10. No thread-unsafety was found.
dgrogan@chromium.org
Linux and CrOS use unlocked_stdio(3). If it is used unsafely, record it
here. If there is no record of unsafety after chrome 29 has been in the
stable channel for a few weeks then revert this change.
dgrogan@chromium.org
Methods where leveldb's Chromium environment has IO errors when being used
by IndexedDB.
dgrogan@chromium.org
PlatformFileErrors encountered by a single leveldb env method.
cmumford@chromium.org
Errors (base::File::Error) encountered by a single leveldb env method.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use LevelDBEnv.IDB.IOError.BFE.NewLogger.
Errno of errors encountered in NewLogger.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use
LevelDBEnv.IDB.IOError.BFE.NewSequentialFile.
Errno of errors encountered in NewSequentialFile.
Deprecated 2013-04. As of m28 use
LevelDBEnv.IDB.IOError.NewRandomAccessFile.
dgrogan@chromium.org
File errors in leveldb IDBEnv's NewRandomAccessFile method.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use
LevelDBEnv.IDB.IOError.BFE.WritableFileAppend.
Errno of errors encountered in WritableFileAppend.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use
LevelDBEnv.IDB.IOError.BFE.WritableFileFlush.
Errno of errors encountered in WritableFileFlush.
dgrogan@chromium.org
Number of directories missing when IDB LevelDBEnv tries to create a Lock
file.
dgrogan@chromium.org
File descriptor limit recorded every time LevelDB calls NewRandomAccessFile
for IndexedDB.
dgrogan@chromium.org
Number of backup files found without corresponding ldb files. As measured by
GetChildren when used in IndexedDB.
dgrogan@chromium.org
When IDB LevelDBEnv successfully retries an operation that had failed,
record the error from the most recent failed attempt.
dgrogan@chromium.org
Success indicates a successful backup or restore operation for .ldb table
files when used in IndexedDB.
Deprecated 2013-04. As of m28 use LevelDBEnv.IDB.TimeUntilSuccessFor.
dgrogan@chromium.org
Time IDB LevelDBEnv slept before successfully completing this operation. 0
means success on the first try.
dgrogan@chromium.org
Time IDB LevelDBEnv slept before successfully completing this operation. 0
means success on the first try.
dgrogan@chromium.org
Methods where leveldb's Chromium environment has IO errors.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.
PlatformFileErrors encountered by a single leveldb method.
cmumford@chromium.org
Errors (base::File::Error) encountered by a single leveldb method.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewLogger.
Errno of errors encountered in NewLogger.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewSequentialFile.
Errno of errors encountered in NewSequentialFile.
Deprecated 2013-04. As of m28 use LevelDBEnv.IOError.NewRandomAccessFile.
dgrogan@chromium.org
File errors in leveldb ChromiumEnv's NewRandomAccessFile method.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileAppend.
Errno of errors encountered in WritableFileAppend.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileFlush.
Errno of errors encountered in WritableFileFlush.
dgrogan@chromium.org
Number of directories missing when Non-IDB LevelDBEnv tries to create a Lock
file.
dgrogan@chromium.org
File descriptor limit recorded every time LevelDB calls NewRandomAccessFile
for clients other than IndexedDB.
dgrogan@chromium.org
Number of backup files found without corresponding ldb files. As measured by
GetChildren when used in LevelDB clients other than IndexedDB.
dgrogan@chromium.org
When Non-IDB LevelDBEnv successfully retries an operation that had failed,
record the error from the most recent failed attempt.
dgrogan@chromium.org
Success indicates a successful backup or restore operation for .ldb table
files when used by LevelDB clients other than IndexedDB.
Deprecated 2013-04. As of m28 use LevelDBEnv.TimeUntilSuccessFor.
dgrogan@chromium.org
Time Non-IDB LevelDBEnv slept before successfully completing this operation.
0 means success on the first try.
dgrogan@chromium.org
Time Non-IDB LevelDBEnv slept before successfully completing this operation.
0 means success on the first try.
dgrogan@chromium.org
Bitfield that indicates errors and recovery that occurred when opening a
LevelDB preferences database.
Deprecated as of 11/2014, removed from code.
feng@chromium.org
A boolean that indicates whether the workaround of a Sony framework bug was
used. The metric is Android-specific, and is logged when the browser starts.
See more details at http://crbug.com/311644.
lizeb@chromium.org
Indicates whether the forking of a child process to prefetch the native
library succeeded. This metric is Android-specific, and is logged when the
browser starts.
thestig@chromium.org
The version of glibc used. (Linux only) Logged on each start up.
rickyz@chromium.org
The Linux sandbox status. This describes what sandboxing features are
enabled (such as the suid/namespace sandboxes, various namespaces, seccomp
bpf, ...). Emitted once at startup.
pkotwicz@chromium.org
The window manager used. (Linux only) Logged on each start up.
noamsml@chromium.org
vitalybuka@chromium.org
Records number of attempts to start local discovery.
noamsml@chromium.org
vitalybuka@chromium.org
Time between detector restarts.
noamsml@chromium.org
vitalybuka@chromium.org
Time before detector trigger notifications.
noamsml@chromium.org
vitalybuka@chromium.org
Records events related to devices page.
noamsml@chromium.org
vitalybuka@chromium.org
Windows only histogram that reports request time spend accessing firewall
rules. It's logged once per browser process lifetime, when local discovery
is used first time.
noamsml@chromium.org
vitalybuka@chromium.org
Windows only histogram that reports, whether a firewall is set, so we can
bind inbound sockets. It's logged once per browser process lifetime, when
local discovery is used first time.
noamsml@chromium.org
vitalybuka@chromium.org
Records events related to local discovery notifications.
michaeln@chromium.org
Size of the HTML5 LocalStorage DB in KB in the browser-side cache.
michaeln@chromium.org
Time to load HTML5 LocalStorage into the browser-side cache.
michaeln@chromium.org
Delay between a page making changes and those changes being written to the
DB.
michaeln@chromium.org
Size of the HTML5 LocalStorage DB in KB in the renderer-side cache.
michaeln@chromium.org
Time to load HTML5 LocalStorage into the renderer-side cache.
michaeln@chromium.org
Time to load HTML5 LocalStorage into the renderer-side cache. Note that the
name is not 'Renderer' prefixed for continuity with the old naming.
cmasone@chromium.org
sumit@chromium.org
Chrome OS histogram tracking, per consumer sign-in, whether the device owner
is allowing arbitrary accounts to be used on the device, or only those on a
specific whitelist.
alemate@chromium.org
A set of chrome flags that required browser restart on Chrome OS user sign
in.
nkostylev@chromium.org
Chrome OS login failure reason.
antrim@chromium.org
Chrome OS histogram that keeps track of the days since the least frequently
used account signed in. Reported on every boot and once a day after that.
dzhioev@chromeos.org
Records whether a new user's priority prefs sync timed out.
dzhioev@chromeos.org
Time spent waiting for priority preferences to sync after new user sign in.
The operation will time out after 10s.
cmasone@chromium.org
The state of Chrome OS owner key and device policy files.
nkostylev@chromium.org
Time from first display of the login prompt until the user completes signing
in.
ginkage@chromium.org
Tracks the reason why a user was sent through the GAIA re-auth flow.
mnissler@chromium.org
Result of a state key generation operation.
nkostylev@chromium.org
Chrome OS login success reason.
alemate@chromium.org
nkostylev@chromium.org
Chrome OS histogram that keeps track of number of users who have logged in
in the last 7 days. Reported on every boot and once a day after that.
alemate@chromium.org
nkostylev@chromium.org
Chrome OS histogram that keeps track of percentage of local users who have
logged in in the last 7 days. Reported on every boot and once a day after
that.
cmasone@chromium.org
Chrome OS histogram that keeps track of the way a user logs in and whether
Chrome OS is running normal or developer mode.
antrim@chromium.org
Chrome OS histogram that keeps track of supervised user password change
result.
treib@chromium.org
pam@chromium.org
The counts of results from supervised user URL filtering. Each entry
includes the outcome of the filter (i.e. allowed, blocked, or unknown) and
the page transition type (how the user got there, e.g. typed URL, clicked
link).
treib@chromium.org
pam@chromium.org
The extra page load delays introduced by network requests due to the
supervised user SafeSites feature, measured once per page load.
treib@chromium.org
pam@chromium.org
The counts of results from the supervised user safety filter. Each entry
includes the outcome of the filter (i.e. allowed, blocked, or unknown) and
the page transition type (how the user got there, e.g. typed URL, clicked
link). This only includes URL requests that were handled by the SafeSites
filter (both online and the static blacklist).
bauerb@chromium.org
treib@chromium.org
pam@chromium.org
The number of whitelists installed for a supervised user. Recorded at every
profile startup.
bauerb@chromium.org
treib@chromium.org
pam@chromium.org
The total amount of time taken to parse the JSON contents of a whitelist out
of process.
bauerb@chromium.org
treib@chromium.org
pam@chromium.org
The amount of time taken to read a whitelist file from disk.
bauerb@chromium.org
treib@chromium.org
pam@chromium.org
The total amount of time taken to load a whitelist from disk and parse it,
including jumps to the blocking thread.
mlamouri@chromium.org
Tracks whether the Manifest fetch succeed and why it failed if it failed.
mlamouri@chromium.org
Tracks which properties of a Manifest were present when it was parsed. If a
property can't be parsed, it will be recorded as not present. These
histograms will only be used if the Manifest was correctly fetched and
parsed and the parsed manifest is not empty.
mlamouri@chromium.org
Tracks whether the parsed Manifest is the empty Manifest.
mlamouri@chromium.org
Tracks the Manifest parsing result. A failure will be recorded if the
Manifest was incorrectly structured. This doesn't take into account parse
failures for each individual properties.
Deprecated as of July 21, 2014.
Please list the metric's owners. Add more owner tags as needed.
Whether accelerated compositing was used for HTML5 media rendering.
qinmin@chromium.org
Android: Records whether a regular media url is HLS (http live streaming)
media or not.
dalecurtis@chromium.org
Bits per channel of HTML5 audio sample data.
dalecurtis@chromium.org
Audio channel layout in HTML5 media.
dalecurtis@chromium.org
Audio codec used in HTML5 media.
henrika@chromium.org
Error codes that AudioUnitRender() returns in AUAudioInputStream on Mac.
dalecurtis@chromium.org
Measures the time taken for AudioInputController::
dalecurtis@chromium.org
Whether capture started successfully after an input stream startup was
requested.
grunell@chromium.org
The silence report for an audio input device session.
dalecurtis@chromium.org
Measures the time taken for AudioInputDeviceManager::
dalecurtis@chromium.org
Measures the time taken for AudioOutputController::
dalecurtis@chromium.org
Time spent waiting in AudioOutputController::WaitTillDataReady() if the data
was not initially available.
dalecurtis@chromium.org
Whether playback started successfully after stream startup was requested.
henrika@chromium.org
Captures if render-side audio glitches are detected or not. Sampled when a
low-latency output audio stream is destructed.
scherkus@chromium.org
Captures statistics for various AudioRendererImpl events.
dalecurtis@chromium.org
Percentage of AudioSyncReader::Read() calls where the renderer missed its
realtime deadline.
dalecurtis@chromium.org
Audio sample format in HTML5 media. Logged when Audio Decoder initializes.
dalecurtis@chromium.org
Audio samples per second in HTML5 media.
dalecurtis@chromium.org
Audio samples per second in HTML5 media (atypical values, in Hz).
State of the media stream audio track processing, sampled once during the
life time of a MediaStreamAudioProcessor.
scherkus@chromium.org
Whether a media response might be used to satisfy a future request.
mfoltz@chromium.org
The average number of delayed and dropped frames for the ChromeCast
application. Reported every 5 seconds.
mfoltz@chromium.org
The average number of displayed frames for the ChromeCast application.
Reported every 5 seconds.
mfoltz@chromium.org
Time needed to pre-buffer A/V data before the actual playback for the
ChromeCast application.
mfoltz@chromium.org
Time needed to buffer A/V data after an abort for the ChromeCast
application.
mfoltz@chromium.org
Time needed to buffer A/V data after an underrun for the ChromeCast
application.
jrummell@chromium.org
Audio codec used in HTML5 media.
jrummell@chromium.org
Container used for HTML5 media. Views that include pre-M34 data will
categorize dash (38) and smooth streaming (39) in the "Other"
bucket.
jrummell@chromium.org
Video codec used in HTML5 media.
Please list the metric's owners. Add more owner tags as needed.
Measures the actions taken in the media infobar, which prompts the users for
device permission.
prabhur@chromium.org
Count of dropped frames between pipeline start and stop. Media pipeline
starts/stops when an HTML5 video is loaded/unloaded respectively in the
browser.
scherkus@chromium.org
Duration in milliseconds of HTML5 media (when known).
xhwang@chromium.org
Size in KB of the last file sucessfully read by the CDM through CDM FileIO
before a specific error happens. This is reported only when the error
happens, which should be rare.
xhwang@chromium.org
Size in KB of the first file sucessfully read by the CDM through CDM FileIO.
This is recorded once per CDM instance.
sandersd@chromium.org
Result of promises for Clear Key key systems that were handled by Chromium
code.
xhwang@chromium.org
addKey result using the Clear Key key system.
xhwang@chromium.org
cancelKeyRequest result using the Clear Key key system.
xhwang@chromium.org
Decryption error event count using the Clear Key key system.
xhwang@chromium.org
generateKeyRequest result using the Clear Key key system.
xhwang@chromium.org
KeyAdded event count using the Clear Key key system.
xhwang@chromium.org
KeyError event count using the Clear Key key system.
xhwang@chromium.org
Key system support query status and result. Each enum value will be reported
at most once per renderer process.
xhwang@chromium.org
EME NeedKey event count.
xhwang@chromium.org
Output protection query status and result. One query and one positive (no
unprotected external links) result (if any) are reported per CDM instance.
sandersd@chromium.org
Key system support query status and result, as reported by
RequestMediaKeySystemAccess. Each value will be reported at most once per
renderer process.
sandersd@chromium.org
Result of promises for unknown key systems that were handled by Chromium
code.
xhwang@chromium.org
addKey result using an unknown key system.
xhwang@chromium.org
cancelKeyRequest result using an unknown key system.
xhwang@chromium.org
Decryption error event count using an unknown key system.
xhwang@chromium.org
generateKeyRequest result using an unknown key system.
xhwang@chromium.org
KeyAdded event count using an unknown key system.
xhwang@chromium.org
KeyError event count using an unknown key system.
xhwang@chromium.org
System code count using an unknown key system.
sandersd@chromium.org
Result of promises for Widevine key systems that were handled by Chromium
code.
xhwang@chromium.org
addKey result using the Widevine key system.
xhwang@chromium.org
cancelKeyRequest result using the Widevine key system.
xhwang@chromium.org
Decryption error event count using the Widevine key system.
xhwang@chromium.org
generateKeyRequest result using the Widevine key system.
xhwang@chromium.org
KeyAdded event count using the Widevine key system.
xhwang@chromium.org
KeyError event count using the Widevine key system.
xhwang@chromium.org
System code count using the Widevine key system.
dalecurtis@chromium.org
Bits per channel of the hardware audio device which failed to open in low
latency mode and required high latency fallback.
dalecurtis@chromium.org
Channel count of the hardware audio device which failed to open in low
latency mode and required high latency fallback.
dalecurtis@chromium.org
Channel layout of the hardware audio device which failed to open in low
latency mode and required high latency fallback.
dalecurtis@chromium.org
Samples per second of the hardware audio device which failed to open in low
latency mode and required high latency fallback.
dalecurtis@chromium.org
Samples per second of the hardware audio device (atypical values, in Hz)
which failed to open in low latency mode and required high latency fallback.
dalecurtis@chromium.org
Whether Chrome had to fallback to the high latency audio path or not.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the Fling application.
Reported every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
The average number of displayed frames for the Fling application. Reported
every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
Time needed to pre-buffer A/V data before the actual playback for the Fling
application.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an abort for the Fling application.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an underrun for the Fling application.
posciak@chromium.org
Results of attempts to GpuVideoDecoder::Initialize().
dalecurtis@chromium.org
Bits per channel of the hardware audio device.
dalecurtis@chromium.org
Channel count of the hardware audio device.
dalecurtis@chromium.org
Channel layout of the hardware audio device.
dalecurtis@chromium.org
Samples per second of the hardware audio device.
dalecurtis@chromium.org
Samples per second of the hardware audio device (atypical values, in Hz).
qinmin@chromium.org
The time it takes to perform redirect tracking and a CORS access check while
preparing to play a media file.
scherkus@chromium.org
Errors returned by LoadLibraryEx on Windows while attempting to load
ffmpegsumo.dll.
henrika@chromium.org
Duration in milliseconds of low-latency audio input streams. Sampled when
the stream is closed by the AudioInputController.
dalecurtis@chromium.org
Audio IO layer used by the Linux OS, sampled once at startup of the browser.
Please list the metric's owners. Add more owner tags as needed.
State of the WebRtc local renderer, sampled once during the lifetime of a
local renderer.
henrika@chromium.org
Heuristically detects if the user has muted the microphone or not. Measured
approximately four times per minute.
henrika@chromium.org
Level of the microphone volume measured in percent. This value can be larger
than 100% on Linux. Measured approximately four times per minute.
acolwell@chromium.org
Audio codec used in Media Source Extensions playback. Set when AddId() is
called during playback.
acolwell@chromium.org
Number of tracks specified to AddId() for Media Source Extensions playback.
May be called multiple times per element if playback is dynamically altered.
acolwell@chromium.org
Whether Media Source Extensions is specified for playback of Media elements.
Sampled when media pipeline starts.
acolwell@chromium.org
Video codec used in Media Source Extensions playback. Set when AddId() is
called during playback.
Please list the metric's owners. Add more owner tags as needed.
The audio bit rate as reported by the Netflix application. May be reported
multiple times as network conditions change during playback.
Please list the metric's owners. Add more owner tags as needed.
The number of audio channels as reported by the Netflix application. May be
reported multiple times as network conditions change during playback.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the Netflix
application. Reported every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
The average number of displayed frames for the Netflix application. Reported
every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
Video bit rate as reported by the Netflix application. May be reported
multiple times as network conditions change during playback.
Please list the metric's owners. Add more owner tags as needed.
Video height as reported by the Netflix application. May be reported
multiple times as network conditions change during playback.
ihf@chromium.org
posciak@chromium.org
Counts of video decode errors reported to plugin.
ihf@chromium.org
posciak@chromium.org
Number of PictureBuffers/textures requested per hardware decoder creation.
This value varies by platform and video. A user visible video may trigger
multiple decoder creations (sometimes every 5 seconds) but would normally
not hold more than 2 sets of buffers at any given time in memory.
ihf@chromium.org
posciak@chromium.org
Vertical video resolution rounded to the nearest bucket. (Corresponds
roughly to the number in 720p.)
prabhur@chromium.org
dalecurtis@chromium.org
Status of the media pipeline at the end of its lifecycle suffixed by stream
and video decoder type.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the PlayMovies
application. Reported every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
The average number of displayed frames for the PlayMovies application.
Reported every 5 seconds.
posciak@chromium.org
Counts of video decode errors reported to RTCVideoDecoder.
Renamed to Media.RTCVideoDecoderInitDecodeSuccess.
posciak@chromium.org
Results of attempts to RTCVideoDecoder::InitDecode().
posciak@chromium.org
Indicates whether we were successful in initializing hardware video decoder
for use in the RTC pipeline.
posciak@chromium.org
Indicates whether we were successful in initializing hardware video encoder
for use in the RTC pipeline.
posciak@chromium.org
Video codec profile used in RTC video encoder.
Removed from code 2014/6/18.
scherkus@chromium.org
Time in milliseconds from HTML5 media pipeline creation to playing event.
hajimehoshi@chromium.org
kouhei@chromium.org
scherkus@chromium.org
Size of HTML5 media (when known), in MB.
scherkus@chromium.org
Reasons a media response won't be used to satisfy a future request.
scherkus@chromium.org
URL scheme used with HTML5 media. (each URL provides one sample)
posciak@chromium.org
Error codes reported by video decode using VA-API hardware video decoder.
Deprecated as of 4/2015, partially replaced by Media.VAVDA.DecoderFailure.
posciak@chromium.org
Error codes reported by video decode using VA-API hardware video decoder.
posciak@chromium.org
Error codes reported by video encode using VA-API hardware video encoder.
mcasas@chromium.org
Video Capture Device captured aspect ratio, as a rounded integer multiplied
by 100. The collection is made in the VideoCaptureController upon reception
of the first frame.
mcasas@chromium.org
Counts appearances of Blacklisted Video Capture devices during enumeration.
This collection happens during first enumeration in the appropriate
platforms' VideoCaptureDeviceFactory.
mcasas@chromium.org
Video Capture Device frame rate requested by VideoCaptureManager on
AllocateAndStart(). The collection is made in the VideoCaptureController
upon reception of the first frame.
grunell@chromium.org
mcasas@chromium.org
Whether any frames were received during a video capture session. This metric
is recorded when a video source is stopped.
mcasas@chromium.org
Video Capture Device captured frame height in pixels. The collection is made
in the VideoCaptureController upon reception of the first frame.
Deprecated 10/2014 in Issue 660493002.
mcasas@chromium.org
Pixel format provided by a Video Capture Device. The collection is made in
the VideoCaptureController upon reception of the first frame.
mcasas@chromium.org
Video Capture Device captured frame width in pixels. The collection is made
in the VideoCaptureController upon reception of the first frame.
mcasas@chromium.org
Video Capture and device enumeration/monitoring API used for Mac OS Lion or
later. Collection is made only once when the flags are parsed and the
appropriate library selected and/or loaded, successfully or not.
mcasas@chromium.org
Measures the time taken for VideoCaptureManager::
grunell@chromium.org
mcasas@chromium.org
Counts video capture event, such as start and stop capture.
scherkus@chromium.org
Video codec used in HTML5 media.
scherkus@chromium.org
Video codec profile used in HTML5 media.
scherkus@chromium.org
Coded aspect ratio of HTML5 video.
scherkus@chromium.org
Coded width of HTML5 video.
scherkus@chromium.org
Pixel format color range of HTML5 video. Emitted on video load.
watk@chromium.org
Whether Chrome had to fall back to a secondary video decoder after the
primary decoder failed reinitialization.
mcasas@chromium.org
Pixel format used in HTML5 video. Emitted on video load.
mcasas@chromium.org
Color space or range used in HTML5 video. Emitted on video load.
Replaced by Media.VideoFormat 05/2015.
scherkus@chromium.org
Pixel format used in HTML5 video. Emitted on video load.
dalecurtis@chromium.org
Indicates how many cadence changes have occurred during playback, a zero
value is emitted at the beginning of playback. Subsequent values are emitted
during video rendering for each cadence change (up to a maximum of 10).
suderman@chromium.org
Metadata rotation in mp4 videos. Emitted during demuxing.
Replaced by Media.VideoCapture.FramesReceived 09/2014.
grunell@chromium.org
mcasas@chromium.org
If any frames were received during a video capture session. It's recorded
when a video source is stopped.
scherkus@chromium.org
Visible aspect ratio of HTML5 video.
scherkus@chromium.org
Visible width of HTML5 video.
sandersd@chromium.org
Whether a VTDecompressionSession is internally using hardware accelerated
decoding.
sandersd@chromium.org
Count of VideoToolbox initialization failure reasons. Successful
initializations are counted as a special failure type. The sum of successes
and failures gives a lower bound on the number of attempted initializations.
sandersd@chromium.org
Count of VTVDA session failure reasons. Successful initializations are
counted as a special failure type. Since only successfully initialized
session can fail, failures rates are computed as a simple ratio.
henrika@chromium.org
Whether Chrome is using Windows Core Audio for audio input or not. Updated
on Windows only when a low-latency audio input stream is created.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the YouTube
application. Reported every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
The average number of displayed frames for the YouTube application. Reported
every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
Time needed to pre-buffer A/V data before the actual playback for the
YouTube application.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an abort for the YouTube application.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an underrun for the YouTube
application.
vandebo@chromium.org
If a media scan was cancelled, the duration (in ms) it ran.
vandebo@chromium.org
The number of directories with media files found during a scan.
vandebo@chromium.org
Duration in milliseconds taken to do a media scan that ran to completion.
vandebo@chromium.org
The percentage of galleries accepted (not deselected) from the scan result
dialog.
vandebo@chromium.org
The number of galleries added or updated in preferences after a scan.
vandebo@chromium.org
Various usage counts for media galleries.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
TBD.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by the browser process. Recorded once per UMA
ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
TBD.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each chrome:// renderer process. Each
process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active chrome:// renderer processes. Recorded once per UMA
ping.
reveman@chromium.org
The discardable memory allocation size in KB. Recorded each time a new
discardable memory instance is created.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each extension process. Each process
provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The number of glyph pages present in the renderer when it commits a load.
Since this is per-sub-process, you can get the average number of glyph pages
in the system by multiplying this number with the average number of
renderers. Note that this typically won't count the glyph pages added as a
result of the load that just committed, since layout will happen after the
commit. There are 512 bytes per glyph page, but this number also very
closely approximates the number of glyph width map pages in the same
renderer. The only difference is that if you have font fallback, it will
make a new glyph page and no width page, but in most common cases there is
no fallback). Width pages are 1K each (256 floats), so you could think of
this value as being the number of "1.5K units related to glyphs per
renderer per page load".
hajimehoshi@chromium.org
jamescook@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by the GPU process. Recorded once per UMA
ping.
hajimehoshi@chromium.org
jamescook@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
System-wide graphics driver memory consumption. Recorded on Chrome OS for
platforms where it is exposed by the kernel (for example, Intel i915 and
Exynos Mali). Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Native Client loader process. Each
process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Native Client broker process. Each
process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of other various utility processes (nacl, gpu, sandbox, zygote,
utility). Recorded once per UMA ping.
thestig@chromium.org
The private working set used by each Pepper Flash plugin process. Each
plugin process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Pepper plugin process. Each plugin
process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Pepper plugin broker process. Each
process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of Pepper plugin broker processes, recorded once per metrics
services (UMA) update. See MetricsReportingScheduler for details.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active Pepper plugin processes. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each plugin process. Each plugin process
provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active plugin processes. Recorded once per UMA ping.
chrisha@chromium.org
The memory pressure level, which is recorded periodically (once per second).
This is used to show the relative time that systems spend in each of the
memory pressure states.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of all active processes. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The current process limit. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each renderer process. Each renderer
process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Growth speed of the private working set used by each renderer process per 30
minutes. The usage and growth speed is recorded at most every 30 minutes,
not every exact 30 minutes. If the interval is longer than 30 minutes, it
is normalized to a speed KB per 30 minutes. Each renderer process provides
one sample. Recorded once per UMA log unless this is the first time the UMA
log is recorded after startup of the renderer, 30 minutes have not passed
from the last recording of the renderer or the usage goes down. If the usage
goes down, the amount of the shrink will be recorded in the
Memory.RendererShrinkIn30Min histogram.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active renderer processes. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Shrink speed of the private working set used by each renderer process per 30
minutes. The usage and shrink speed is recorded at most every 30 minutes,
not every exact 30 minutes. If the interval is longer than 30 minutes, it
is normalized to a speed KB per 30 minutes. Each renderer process provides
one sample. Recorded once per UMA log unless this is the first time the UMA
log is recorded after startup of the renderer, 30 minutes have not passed
from the last recording of the renderer or the usage goes up. If the usage
goes up, the amount of the growth will be recorded in the
Memory.RendererGrowthIn30Min histogram.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each sandbox helper process. Each sandbox
helper process provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by the browser process. Recorded once per UMA ping if the
system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each chrome:// renderer process. Each process provides one
sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The amount of memory that swap was compressed into. Recorded once per UMA
ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The ratio of swapped data original size to compressed size. Recorded once
per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each extension process. Each process provides one sample.
Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by the GPU process. Recorded once per UMA ping if the system
has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Indicates that the system has swapped memory out at least once since boot.
Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The amount of memory that is used by swap, including bookkeeping. Recorded
once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Native Client loader process. Each process provides
one sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Native Client broker process. Each process provides
one sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The number of reads from swap. Recorded once per UMA ping if the system
has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The number of writes to swap. Recorded once per UMA ping if the system has
swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The amount of memory that was swapped out. Recorded once per UMA ping if
the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Pepper plugin process. Each plugin process provides
one sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Pepper plugin broker process. Each process provides
one sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each plugin process. Each plugin process provides one
sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each renderer process. Each renderer process provides one
sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each sandbox helper process. Each sandbox helper process
provides one sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The sum of all processes' swap. Recorded once per UMA ping if the system
has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each utility process. Each utility process provides one
sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each worker process. Each worker process provides one
sample. Recorded once per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The sum of all processes. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each utility process. Each utility process
provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each worker process. Each worker process
provides one sample. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
TBD.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
ppi@chromium.org
Value of getMemoryClass() recorded once upon startup. This is an integer,
device-specific constant correlated with the amount of memory available on
Android device.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
ppi@chromium.org
Reasons behind evictions of individual tabs, recorded upon each tab
eviction.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
ppi@chromium.org
Number of loaded (memory-resident) tabs when LowMemory notification is
delivered.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
ppi@chromium.org
Time between two consecutive LowMemory notification in one foreground
session.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
ppi@chromium.org
Memory notifications delivered through system callbacks to Chrome while in
the background.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
ppi@chromium.org
Memory notifications delivered through system callbacks to Chrome while in
the foreground - we count LowMemory notification vs particular levels of
TrimMemory foreground notification.
lliabraa@chromium.org
[iOS] When the OS sends a memory warning and the app evicts a tab, this
histogram records the time since the evicted tab was active.
lliabraa@chromium.org
[iOS] When the OS sends a memory warning and the app protects a tab, this
histogram records the time since the protected tab was active.
benchan@chromium.org
The result (e.g. success or the type of failure) of a modem interface switch
operation performed by mist on Chrome OS.
aruslan@chromium.org
Android: How the user left the sign-in part of the "first run
experience" activity (M-38+).
qinmin@chromium.org
Android: Records the duration that a fullscreen video is played after device
rotates from portrait to landscape mode for the first time, and before it
exits fullscreen. If there is no device rotation or if the video starts with
landscape mode, it is not recorded. If there are mutiple rotations between
portrait and landscape mode, only one record is emitted and it is equal to
the time period from the first rotation to the moment when the video exits
fullscreen.
qinmin@chromium.org
Android: Records the duration that a fullscreen video is played in landscape
mode. If a video starts playing in landscape mode, and then it is switched
back and forth between landscape and portrait mode, only the time period
before the first switch is accounted. If a video starts playing in portrait
mode, it is not recorded.
qinmin@chromium.org
Android: Records whether a fullscreen video is switched from landscape to
portrait mode at any point during playback.
qinmin@chromium.org
Android: Records the device orientation when a video enters fullscreen. The
value is true if device orientation is portrait, or false otherwise. The
video doesn't necessarily needs to be in a playing state.
qinmin@chromium.org
Android: Records the duration that a fullscreen video is played in portrait
mode. If a video starts playing in portrait mode, and then it is switched
back and forth between landscape and portrait mode, only the time period
before the first switch is accounted. If a video starts playing in landscape
mode, it is not recorded.
qinmin@chromium.org
Android: Records whether a fullscreen video is switched from portrait to
landscape mode at any point during playback.
qinmin@chromium.org
Android: Records whether a video has a larger height than width when it
enters the fullscreen mode.
dtrainor@chromium.org
Android: Number of instances of Chrome currently open during a MultiWindow
session. Emitted every time Chrome is paused. Only emitted on Android
MultiWindow devices.
A MultiWindow session is any period of time that Chrome was not used in a
full screen mode but together with another Activity that is visible at the
same time. This is only supported in a few Android models.
miguelg@chromium.org
Android: percent of the screen available for Chrome during a multi-window
session. Emitted every time chrome is paused. Only emitted on Android
MultiWindow devices.
A multiwindow session is any period of time that Chrome was not used in full
screen mode but together with some other application that is visible at the
same time. This is only supported in a few Android models.
anthonyvd@chromium.org
Represents the amount of bytes in a module that are different on disk and in
memory. Logged when the ModuleIntegrityVerifier determines that a module is
different on disk and in memory after being triggered by an incident.
Deprecated and removed from code as of 05/2015.
anthonyvd@chromium.org
Represents the difference in bytes deemed modified by the two
ModuleIntegrityVerifier code paths. The suffix indicates which path had a
higher value. Logged when the ModuleIntegrityVerifier determines that a
module is different on disk and in memory after being triggered by an
incident and the reported byte count for both methods is different.
grt@chromium.org
Logged when the relocations in a module are not ordered causing the module
verification to abort.
Deprecated 04/2015; replaced by
ModuleIntegrityVerification.RelocationsUnordered.
anthonyvd@chromium.org
Logged when the relocations in a module are not ordered causing the module
verification to abort. The value is the index of the affected module.
Please list the metric's owners. Add more owner tags as needed.
Tracks mouse sensitivity setting changes by the user. This replaces the old
Mouse.Sensitivity.Changed metric.
Please list the metric's owners. Add more owner tags as needed.
Tracks mouse sensitivity setting on startup. This replaces the old
Mouse.Sensitivity.Started metric.
Deprecated as of 6/2013, replaced by Mouse.PointerSensitivity.Changed.
Please list the metric's owners. Add more owner tags as needed.
Tracks mouse sensitivity setting.
Deprecated as of 6/2013, replaced by Mouse.PointerSensitivity.Started.
Please list the metric's owners. Add more owner tags as needed.
Tracks mouse sensitivity setting on startup.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user mousedown-ed a link and when
the user clicked a link.
Please list the metric's owners. Add more owner tags as needed.
For each click handled by an HTML anchor tag link, whether Blink saw a
mousedown event preceding it. This is only measured for clicks handled by
the anchor tag's default click event handler.
Please list the metric's owners. Add more owner tags as needed.
The number of mousedown events detected at HTML anchor-tag links' default
event handler.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user mouseover-ed a link and when
the user clicked a link.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user mouseover-ed a link and when
the user mouseout-ed a link without click.
Please list the metric's owners. Add more owner tags as needed.
The number of mouseover events detected at HTML anchor-tag links' default
event handler.
Please list the metric's owners. Add more owner tags as needed.
The tap gesture events detected before click at HTML anchor-tag links'
default event handler.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user tapdown-ed a link and when
the user clicked a link.
Please list the metric's owners. Add more owner tags as needed.
The number of gesturetapdown events detected at HTML anchor-tag links'
default event handler.
Please list the metric's owners. Add more owner tags as needed.
The number of gesturetapunconfirmed events detected at HTML anchor-tag
links' default event handler.
ppi@chromium.org
The time it takes to spawn the first child subprocess (including sandbox
init).
ppi@chromium.org
The time it takes to spawn child sub processes not counting the first one.
rvargas@chromium.org
The time spent waiting for the renderer to acknowledge an input event.
Deprecated 2/2013, renamed.
Please list the metric's owners. Add more owner tags as needed.
The time it takes to spawn the first renderer subprocess (including sandbox
init).
Deprecated 2/2013, renamed.
Please list the metric's owners. Add more owner tags as needed.
The time it takes to spawn renderer sub processes not counting the first
one.
ppi@chromium.org
The number of RenderProcessHosts (i.e. renderer processes) present when each
load completes. This is basically the average number of sub-processes over
time. See also Tabs.TabCountPerLoad.
Please list the metric's owners. Add more owner tags as needed.
renamed MPArch.IIR_InputEventDelta.
The time spent waiting for the renderer to acknowledge an input event.
Please list the metric's owners. Add more owner tags as needed.
The time spent inside RenderWidgetHost::OnMsgPaintRect.
Please list the metric's owners. Add more owner tags as needed.
The time spent inside RenderWidgetHost::OnMsgScrollRect.
Please list the metric's owners. Add more owner tags as needed.
TBD
Please list the metric's owners. Add more owner tags as needed.
TBD
jbauman@chromium.org
Time from tab switch requested to tab appearing on screen (Aura and Mac
only).
Please list the metric's owners. Add more owner tags as needed.
The time that the user sees a blank white page after switching to a
different tab, while the RenderWidgetHost receives data to paint from the
renderer process.
skuhne@chromium.org
The relation of discarded tabs vs. the amount of simultaneous users. The
counts are the number of discards and the buckets are the number of users.
Since the count values are absolute numbers, they need to be normalized
before use - so divide the counts by the percentage of users per session
found under 'MultiProfile.UsersPerSessionIncremental'.
skuhne@chromium.org
The session counter for different multi profile modes which gets stored once
per session at the beginning of the session.
skuhne@chromium.org
Count the number of times each UI path is taken for signing into a new
account in a Chrome OS multiprofile session. UI paths include the system
tray and the user account switcher on the browser frame.
skuhne@chromium.org
Count the number of times each UI path is taken for switching the active
account in a Chrome OS multiprofile session. UI paths include the system
tray and the keyboard shortcut.
skuhne@chromium.org
Counts the number of window teleportations when using separated desktop
mode.
skuhne@chromium.org
Counts the number of teleported windows by types in separated desktop mode.
Deprecated 3/2014, renamed to MultiProfile.UsersPerSessionIncremental.
skuhne@chromium.org
The number of users simultaneously signed into a multiprofile session on
Chrome OS. This is recorded upon session end.
skuhne@chromium.org
The number of users simultaneously signed into a multiprofile session on
Chrome OS. This is recorded whenever a user gets added to the session. To
get the correct count, all following counts must be subtracted. Example: If
100 single user, 20 two user and 5 three user sessions, there were
100-20-5=75 single user sessions, 100-80=20 dual user sessions and so on.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
When the browser started, what happened with the NaCl helper process?
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
When a NaCl application process was created, what had happened with the NaCl
helper process when the browser was started?
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The OS/Architecture of a nexe that was loaded.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The status code returned when trying to load a manifest inside an installed
app.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The status code returned when trying to load a manifest from a source other
than an installed app.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The status code returned when trying to load a NaCl executable inside an
installed app.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The status code returned when trying to load a NaCl executable from a source
other than an installed app.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The error code returned by NaCl's Chrome plugin.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The error code returned by NaCl's Chrome plugin, but only for installed
apps.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The error code returned by NaCl's Chrome plugin, but excluding installed
apps.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The error code returned by NaCl's sel_ldr.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The error code returned by NaCl's sel_ldr, but only for installed apps.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The error code returned by NaCl's sel_ldr, but excluding installed apps.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
Was the manifest specified as a data URI rather than a .nmf file?
Deprecated 6/2011, renamed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to download the manifset file for a Native Client module.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time a NaCl module ran before it crashed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time a NaCl module ran without crashing, at shutdown.
Deprecated 6/2011, renamed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to download the main .nexe for a Native Client module.
Deprecated 6/2011, renamed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The size of the main .nexe file downloaded for a Native Client module.
Deprecated 6/2011, renamed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took between the Native Client plugin initialization and when
proxied execution of the NaCl module begins. This is the general startup
overhead of running as a NaCl module vs a trusted PPAPI plugin.
Deprecated 6/2011, renamed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took between the Native Client plugin initialization and when
proxied execution of the NaCl module begins. This is the general startup
overhead of running as a NaCl module vs a trusted PPAPI plugin.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The optimization level set for the initial Portable Native Client
translation from bitcode to native code.
Deprecated 6/2011, renamed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The OS/Architecture of a nexe that was loaded.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
Did the Portable Native Client translation cache find an executable
translated from bitcode?
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The rate for compiling a Portable Native Client bitcode file to an object
file in Kilobytes per second.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to compile a Portable Native Client bitcode file to an
object file.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to link a Portable Native Client generated object file into
a Native Client executable.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to load and validate the Portable Native Client compiler.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to load and validate the Portable Native Client linker.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The percentage of a Portable Native Client application that is compiled by
the time the application is fully downloaded (compile and download happen in
parallel).
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The rate for completely translating a Portable Native Client bitcode file
into a Native Client executable and caching the result in Kilobytes per
second.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The total time it took to completely translate a Portable Native Client
bitcode file into a Native Client executable, and cache the result.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took the NaCl module to shut down.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The size of the manifest file.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The size of the main .nexe file downloaded for a Native Client module.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The size of the main .pexe bitcode file downloaded for a Portable Native
Client module.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The size of the main .pexe bitcode file divided by the size of the .nexe
that is the result of translating the bitcode file, times 100.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The size of the main .nexe file that is the result of translating a Portable
Native Client .pexe bitcode file. This reflects the amount of cache
consumed.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to load the NaCl module into sel_ldr.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to load the NaCl module into sel_ldr. Normalized by the
size of the .nexe, in megabytes.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to download the manifset file for a Native Client module.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took between the Native Client plugin initialization and when
proxied execution of the NaCl module begins. This is the general startup
overhead of running as a NaCl module vs a trusted PPAPI plugin.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took between the Native Client plugin initialization and when
proxied execution of the NaCl module begins. This is the general startup
overhead of running as a NaCl module vs a trusted PPAPI plugin. Normalized
by the size of the .nexe, in megabytes.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to download the main .nexe for a Native Client module.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took to download the main .nexe for a Native Client module.
Normalized by the size of the .nexe, in megabytes.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took between the Native Client plugin initialization and when
the NaCl module is ready to be used.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The time it took between the Native Client plugin initialization and when
the NaCl module is ready to be used. Normalized by the size of the .nexe,
in megabytes.
Deprecated 5/2011, data is duplicated by NaCl.NexeStartupTime, and
normalizing to 'tab opens' is unusual.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
The number of times that Native Client has been started by loading a .nexe
compared to the number of times that a tab has been opened.
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
Did a validation cache query find a previously known validation result?
jvoung@chromium.org
mackinlay@google.com
ncbray@chromium.org
Was the validation cache updated with a new validation result?
cjhopman@chromium.org
nyquist@chromium.org
Signifies whether a succesfully finished page load for the main frame
content width fits within the device width and/or has a fixed page scale.
cbentzel@chromium.org
davidben@chromium.org
The scheme of the URL for each main-frame navigation.
cbentzel@chromium.org
davidben@chromium.org
The scheme of the URL for each main-frame navigation that goes to a
different page. Transitions like fragment change or history.pushState are
excluded.
carlosk@chromium.org
Overhead time spent handling the OnBeforeUnload event from the browser
standpoint. More precisely, it is the total time between dispatch and
acknowledgment of the BeforeUnload event on the browser side, minus the
actual time spent executing the BeforeUnload handlers on the renderer side.
haitaol@chromium.org
donnd@chromium.org
Total length of the redirect URL strings in navigation entry. Logged when
entry is committed.
carlosk@chromium.org
Time between the start of a browser-started navigation request in and its
commit.
carlosk@chromium.org
Time between the start of a browser-started navigation request and the
reception of a corresponding ResourceRequest in the network stack.
clamy@chromium.org
Time between receiving an Android Intent and the navigation commit.
clamy@chromium.org
Time between clicking on a link and the navigation commit.
clamy@chromium.org
Time between receiving an Android intent and the document load complete
event for a navigation in the main frame.
clamy@chromium.org
Time between clicking on a link and the document load complete event for a
navigation in the main frame.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a 2G connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a 3G connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a 4G connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a Bluetooth
connection, before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on an Ethernet
connection, before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen while the
NetworkChangeNotifier thought there was no network connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on an unknown connection
type, before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a Wifi connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to a 2G connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to a 3G connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to a 4G connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to a Bluetooth connection and receiving the first
network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to an Ethernet connection and receiving the first
network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between disconnecting and receiving the first network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to an unknown connection type and receiving the first
network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time between switching to a Wifi connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via a 2G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via a 3G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via a 4G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via a Bluetooth connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via an Ethernet connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while the NetworkChangeNotifier thought there
was no network connection, before the NetworkChangeNotifier detected a
connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via an unknown connection type,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How much data was transfered while connected via a Wifi connection, before
the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a 2G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a 3G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a 4G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a Bluetooth connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on an Ethernet connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen while the NetworkChangeNotifier
thought there was no network connection, before the NetworkChangeNotifier
detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on an unknown connection type, before
the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a Wifi connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via a 2G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via a 3G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via a 4G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via a Bluetooth connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via an Ethernet connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent disconnected, before the NetworkChangeNotifier detected a
connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via an unknown connection type, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
How long was spent connected via a Wifi connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
pauljensen@chromium.org
Time from ConnectionTypeChanged message until IPAddressChanged message.
pauljensen@chromium.org
Time between DNS configuration change messages.
pauljensen@chromium.org
How long does each call to NetworkChangeNotifier::GetConnectionType() take.
pauljensen@chromium.org
Time between IP address change messages.
pauljensen@chromium.org
Time from IPAddressChanged message until ConnectionTypeChanged message.
pauljensen@chromium.org
Time between going online until we go offline change messages, using new
filtered signal.
pauljensen@chromium.org
Time between going offline until we go online change messages, using new
filtered signal.
bolian@chromium.org
bengr@google.com
marq@google.com
The MCC (mobile country code) and MNC (mobile network code) of the network
operator when a new metrics log is created or when the network connection is
changed. A value of zero means a non-mobile network or the operator code is
unknown.
pauljensen@chromium.org
Time between going online until we go offline change messages.
pauljensen@chromium.org
Time between when we thought we went offline and when we received some
network data (a URLRequest read completed).
pauljensen@chromium.org
Count of how many times we received network data (a URLRequest read
completed) while offline when some data was received at most five seconds
before going online.
pauljensen@chromium.org
Time between when we received the last network data (a URLRequest read
completed) while offline and when we thought we went online.
pauljensen@chromium.org
Count of how many times we polled the online/offline status before detecting
an offline to online transition.
pauljensen@chromium.org
Time between going offline until we go online change messages.
pauljensen@chromium.org
Time between when we thought we went offline and when we received some
network data (a URLRequest read completed), while polling
NetworkChangeNotifier::GetConnectionType() still told us we were offline.
rch@chromium.org
Breakdown of the locations when SetBrokenAlternateProtocol is called.
rch@chromium.org
Breakdown of how requests which could potentially make use of an alternate
protocol use or don't use the protocol.
Deprecated 10/2014.
rch@chromium.org
Breakdown of how requests which could potentially make use of an alternate
protocol use or don't use the protocol. Loaded data for 1000 servers and we
have persisted 1000 MRU servers.
Deprecated 10/2014.
rch@chromium.org
Breakdown of how requests which could potentially make use of an alternate
protocol use or don't use the protocol. Loaded data for 200 servers and we
have persisted 1000 MRU servers.
Deprecated 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The count of unacknowledged ResourceMsg_DataReceived messages. This message
is sent once per chunk of data read from the network.
Deprecated 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The count of unacknowledged ResourceMsg_DataReceived messages at the point
where we pause network loading.
Data collection finished on 2015-03-31.
bnc@chromium.org
The time between the call of AsyncResourceHandler::OnRequestRedirected and
the FollowRedirect IPC message from ResourceHost, that is, the length of the
redirect browser-renderer-browser hop.
Deprecated 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The size of a SharedIOBuffer allocation.
Deprecated 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The number of bytes copied into a SharedIOBuffer.
Deprecated 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The percentage of a SharedIOBuffer allocation that is actually used.
Deprecated 01/2011 in https://crrev.com/70740
Please list the metric's owners. Add more owner tags as needed.
The time to generate a Basic HTTP authentication token.
Deprecated 01/2011 in https://crrev.com/70740
Please list the metric's owners. Add more owner tags as needed.
The time to generate a Digest HTTP authentication token.
Deprecated 01/2011 in https://crrev.com/70740
Please list the metric's owners. Add more owner tags as needed.
The time to generate a Negotiate (or SPNEGO) HTTP authentication token.
Deprecated 01/2011 in https://crrev.com/70740
Please list the metric's owners. Add more owner tags as needed.
The time to generate an NTLM HTTP authentication token.
ellyjones@chromium.org
rdsmith@chromium.org
cbentzel@chromium.org
Number of times auto-reload has been attempted before auto-reload stopped
without succeeding, either because the stop button was pressed or because
the renderer was destroyed.
ellyjones@chromium.org
rdsmith@chromium.org
cbentzel@chromium.org
Number of times auto-reload had to attempt to reload a page before
succeeding.
ellyjones@chromium.org
rdsmith@chromium.org
cbentzel@chromium.org
Original error code that started an auto-reload which then succeeded on the
first attempt.
ellyjones@chromium.org
rdsmith@chromium.org
cbentzel@chromium.org
Error code, if any, when auto-reload stopped without succeeding, either
because the stop button was pressed or because the renderer was destroyed.
ellyjones@chromium.org
rdsmith@chromium.org
cbentzel@chromium.org
Original error code that started an auto-reload which then eventually
succeeded.
ellyjones@chromium.org
rdsmith@chromium.org
Counts of response bytes by cache state.
ellyjones@chromium.org
rdsmith@chromium.org
State of the cache for a request, delta-encoding eligible or otherwise.
ellyjones@chromium.org
rdsmith@chromium.org
Counts of response bytes by cache state for delta-encoding eligible
requests.
ellyjones@chromium.org
rdsmith@chromium.org
State of the cache for a delta-encoding eligible request.
rsleevi@chromium.org
Whether the certificate common name was used for matching the hostname,
instead of the subjectAlternativeName.
Measures results for all CAs (internal and publicly-trusted).
rsleevi@chromium.org
Whether the certificate common name was used for matching the hostname,
instead of the subjectAlternativeName.
Measures results ony for internal (non-publicly-trusted) CAs.
rsleevi@chromium.org
Whether or not SHA-1 was present in a resource fetched for the main frame,
and if so, what its maximum validity period was.
rsleevi@chromium.org
Whether or not SHA-1 was present in a subresource fetch, and if so, what its
maximum validity period was.
Renamed to Net.PublicKeyPinSuccess 28 Oct 2011.
Please list the metric's owners. Add more owner tags as needed.
A validated certificate chain may be subject to additional
"pinning" requirements on a per-domain basis. This records the
fraction of successful matches between a certificate chain and a pin list.
eranm@chromium.org
Number of valid Signed Certificate Timestamps (SCTs) present for the
main-frame resource. Emitted every time a main-frame resource is fetched.
eranm@chromium.org
The origin breakdown of Signed Certificate Timestamps (SCTs). Emitted once
for every SCT when first validated, which means 0 or more times during every
SSL connection establishment.
eranm@chromium.org
The number of Signed Certificate Timestamps (SCTs) that were available for
each SSL connection, including SCTs embedded in the certificate. This metric
measures how many SSL connections had SCTs available. Emitted during every
SSL connection establishment.
eranm@chromium.org
Breakdown of Signed Certificate Timestamps (SCTs) validation status. Emitted
once for every SCT when first validated, which means 0 or more times during
every SSL connection establishment.
davidben@chromium.org
The actual amount of time spent verifying a certificate using the underlying
cryptographic APIs. Because parallel verifications for the same certificate
may be coalesced, histograms such as Net.SSLCertVerificationTime may be
skewed, due to later verifications taking less overall time. This records
the overall time spent verifying the first job to capture initialization
costs.
rsleevi@chromium.org
The actual amount of time spent verifying a certificate using the underlying
cryptographic APIs. Because parallel verifications for the same certificate
may be coalesced, histograms such as Net.SSLCertVerificationTime may be
skewed, due to later verifications taking less overall time. This records
the overall time spent verifying a single request, regardless of how many
parallel requests are being served by the verification.
Please list the metric's owners. Add more owner tags as needed.
The number of times we sent N packets, but could have sent N-1 packets.
This experiment has concluded.
Please list the metric's owners. Add more owner tags as needed.
The amount of time taken before we failed to resolve the Comodo test DNS
record. This is an experiment, run in conjuction with Comodo, to test the
viability of a DNS based certificate revocation mechanism.
This experiment has concluded.
Please list the metric's owners. Add more owner tags as needed.
The amount of time taken to successfully resolve the Comodo test DNS record.
This is an experiment, run in conjuction with Comodo, to test the viability
of a DNS based certificate revocation mechanism.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was compressed.
Only includes requests which did not go through an explicit proxy and did
not go over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The compressed number of bytes received per request that was compressed.
Only includes requests which did not go through an explicit proxy and did
not go over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was not
compressed but appears to have been compressible. Only includes requests
which did not go through an explicit proxy and did not go over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was compressed.
Only includes requests sent through a proxy without SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The compressed number of bytes received per request that was compressed.
Only includes requests sent through a proxy without SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was not
compressed but appears to have been compressible. Only includes requests
sent through a proxy without SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was compressed.
Only includes requests sent over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The compressed number of bytes received per request that was compressed.
Only includes requests sent over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was not
compressed but appears to have been compressible. Only includes requests
sent over SSL.
The count was inaccurate (it counted transactions rather than connections)
Please list the metric's owners. Add more owner tags as needed.
Each bucket is the number of connections of a particular type that the user
has had during the session.
Renamed to match HadConnectionType.
Please list the metric's owners. Add more owner tags as needed.
Each bucket is the number of successful connections of a particular type
that the user has had during the session.
davidben@chromium.org
Each bucket is the number of successful connections of a particular type
that the user has had during the session.
No longer collected.
Please list the metric's owners. Add more owner tags as needed.
Each bucket is the number of failed connections of a particular type that
the user has had during the session.
Replaced with Net.ConnectionUsedSSLDeprecatedCipherFallback2 in Chrome 44.
davidben@chromium.org
True if an HTTPS connection was made using the deprecated cipher suite
fallback.
davidben@chromium.org
For each successful HTTPS request, whether it used the deprecated cipher
suite fallback.
Replaced by Net.ConnectionUsedSSLVersionFallback in Chrome 21.
Please list the metric's owners. Add more owner tags as needed.
True if the HTTP request was to a server which requires SSLv3 fallback
Replaced with Net.ConnectionUsedSSLVersionFallback2 in Chrome 44.
agl@chromium.org
Nonzero if the HTTP request was to a server which requires SSL version
fallback. The value indicates the SSL version the request fell back on.
davidben@chromium.org
For each successful HTTPS request, whether it used the SSL version fallback.
The value indicates the SSL version the request fell back on
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Whether or not updates to the backing store succeeded or failed, recorded
every update.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Intervals between access time updates for each cookie.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Number of cookies in the store (recorded every 10 minutes of active browsing
time)
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For each cookie removed from the store, the reason it was removed.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For each domain, number of cookies in that domain (recorded every 10 minutes
of active browsing time).
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of subdomains in that top level domain
(recorded every 10 minutes of active browsing time).
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of cookies in that domain (recorded every
10 minutes of active browsing time).
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For each evicted (not expired) cookie, the amount of time since it was last
used
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Number of minutes until cookie expires when set.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
The amount of time (ms) to get cookies for each URL request.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
The amount of time (ms) to load the persistent cookie store at browser
start.
bnc@chromium.org
rch@chromium.org
rtenneti@chromium.org
The total number of severs to which alternative protocol was used. This
counts the number of servers persisted to prefs file.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The total number of severs that support HTTP pipelining. This counts the
number of servers persisted to prefs file.
bnc@chromium.org
rch@chromium.org
rtenneti@chromium.org
The total number of SPDY server names persisted to prefs file.
bnc@chromium.org
rch@chromium.org
rtenneti@chromium.org
The total number of SPDY Settings properties persisted to prefs file.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to block to fetch one or
more revocation lists. This measures the amount of time that failures to get
CRL information take.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to block to fetch one or
more revocation lists. This records the fraction of successful requests.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to block to fetch one or
more revocation lists. This measures the amount of time that each fetch
takes.
bolian@chromium.org
The total content size in KB of all HTTP/HTTPS response bodies in the
previous calendar day. The metric is reported when the first response in the
current day is received.
bengr@chromium.org
bolian@chromium.org
The total content size in KB of all HTTP/HTTPS response bodies in the
previous calendar day while the data reduction proxy setting was enabled.
The metric is reported when the first response in the current day is
received.
bengr@chromium.org
bolian@chromium.org
The total content size in KB of all HTTPS response bodies in the previous
calendar day while the data reduction proxy setting was enabled. The metric
is reported when the first response in the current day is received.
bengr@chromium.org
bolian@chromium.org
The total content size in KB of all long-bypassed HTTP response bodies in
the previous calendar day while the data reduction proxy setting was
enabled. The metric is reported when the first response in the current day
is received.
bengr@chromium.org
bolian@chromium.org
The total content size in KB of all short-bypassed HTTP response bodies in
the previous calendar day while the data reduction proxy setting was
enabled. The metric is reported when the first response in the current day
is received.
bengr@chromium.org
bolian@chromium.org
The total content size in KB of all HTTP response bodies for requests that
were not served by the enabled data reduction proxy for unknown reasons in
the previous calendar day while the data reduction proxy setting was
enabled. The metric is reported when the first response in the current day
is received.
bengr@chromium.org
bolian@chromium.org
The total content size in KB of all HTTP/HTTPS response bodies in the
previous calendar day via the data reduction proxy. The metric is reported
when the first response in the current day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of total HTTP/HTTPS response body size while the data
reduction proxy is enabled to total HTTP/HTTPS response body size in the
previous calendar day. The metric is reported when the first response in the
current day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of total HTTPS response body size while the data reduction
proxy is enabled to total HTTP/HTTPS response body size in the previous
calendar day. The metric is reported when the first response in the current
day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of total long-bypassed response body size while the data
reduction proxy is enabled to total HTTP/HTTPS response body size in the
previous calendar day. The metric is reported when the first response in the
current day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of total short-bypassed response body size while the data
reduction proxy is enabled to total HTTP/HTTPS response body size in the
previous calendar day. The metric is reported when the first response in the
current day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of total body size of responses that were not served by the
data reduction proxy for unknown reason while the data reduction proxy is
enabled to total HTTP/HTTPS response body size in the previous calendar day.
The metric is reported when the first response in the current day is
received.
bengr@chromium.org
bolian@chromium.org
The percentage of total HTTP/HTTPS response body size via the data reduction
proxy to total HTTP/HTTPS response body size in the previous calendar day.
The metric is reported when the first response in the current day is
received.
bengr@chromium.org
bolian@chromium.org
The percentage of data saving in the previous calendar day. A negative
saving will be shown as zero. The metric is reported when the first response
in the current day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of data saving in the previous calendar day while the data
reduction proxy was enabled. A negative saving will be shown as zero. This
only counts responses while the data reduction proxy is enabled. The metric
is reported when the first response in the current day is received.
bengr@chromium.org
bolian@chromium.org
The percentage of data saving in the previous calendar day via the data
reduction proxy. A negative saving will be shown as zero. This only counts
responses via the data reduction proxy. The metric is reported when the
first response in the current day is received.
Deprecated- see Net.DailyContentLength_ViaDataReductionProxy.
bolian@chromium.org
Total size in KB of all response bodies in the previous calendar day that
were received through the data reduction proxy.
Deprecated- see Net.DailyContentLength_DataReductionProxyEnabled
bolian@chromium.org
Total size in KB of all response bodies in the previous calendar day that
were received when the data reduction proxy was enabled.
Deprecated- see Net.DailyContentSavingPercent.
bolian@chromium.org
The percentage of data saving in the previous calendar day. A negative
saving will be shown as zero.
Deprecated- see Net.DailyContentSavingPercent_DataReductionProxyEnabled.
bolian@chromium.org
The percentage of data saving in the previous calendar day when the data
reduction proxy was enabled for at least some responses during the day. A
negative saving will be shown as zero.
Deprecated- see Net.DailyOriginalContentLength.
bolian@chromium.org
Total size in KB specified in the X-Original-Content-Length headers of all
responses in the previous calendar day. If the header is not present in a
response, the size of the response body is used.
Deprecated- see Net.DailyContentLength.
bolian@chromium.org
Total size in KB of all response bodies in the previous calendar day.
bolian@chromium.org
The total size in KB specified in the X-Original-Content-Length headers of
all HTTP/HTTPS response bodies in the previous calendar day. If the header
is not present in a response, the size of the response body is used. The
metric is reported when the first response in the current day is received.
bengr@chromium.org
bolian@chromium.org
The total size in KB specified in the X-Original-Content-Length headers of
all HTTP/HTTPS response bodies in the previous calendar day while the data
reduction proxy is enabled. If the header is not present in a response, the
size of the response body is used. The metric is reported when the first
response in the current day is received.
bengr@chromium.org
bolian@chromium.org
The total size in KB specified in the X-Original-Content-Length headers of
all HTTP/HTTPS response bodies in the previous calendar day via the data
reduction proxy. If the header is not present in a response, the size of the
response body is used. The metric is reported when the first response in the
current day is received.
Deprecated- see Net.DailyContentPercent_ViaDataReductionProxy.
bengr@chromium.org
bolian@chromium.org
The percentage of Net.DailyHttpContentLengthViaDataReductionProxy in
Net.DailyHttpReceivedContentLength.
Deprecated- see Net.DailyContentPercent_DataReductionProxyEnabled.
bengr@chromium.org
bolian@chromium.org
The percentage of Net.DailyHttpContentLengthWithDataReductionProxyEnabled in
Net.DailyHttpReceivedContentLength.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Measures time from initiating a fetch of a PAC file from DHCP WPAD to
cancellation of the fetch. For a given fetch, only one of the cancellation
or completion histograms will be added to.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Measures time from initiating a fetch of a PAC file from DHCP WPAD to
completion of the fetch. For a given fetch, only one of the cancellation or
completion histograms will be added to.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Tracks the net error codes received when the DHCP WPAD fetch fails to
retrieve a PAC file (including PAC_NOT_IN_DHCP, which is not really an error
but an indication that a PAC URL was not configured in DHCP).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Tracks the frequency of each of the different known error codes of calling
the GetAdaptersAddresses Win32 API.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Measures the time taken to call the GetAdaptersAddresses Win32 API, to
validate our understanding that it should complete quickly enough to call
synchronously from the network thread.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Total number of adapters enabled for DHCP as seen when the wait timer in the
DHCP WPAD code hits. This timer fires after a timeout from when we get some
information from the first adapter to finish.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Number of adapters enabled for DHCP that we have not completed retrieving
information for, as seen when the wait timer in the DHCP WPAD code hits.
This timer fires after a timeout from when we get some information from the
first adapter to finish.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Counts the number of errors from the DhcpRequestParams API that we do not
have specific handling for, so that we can see if there is an abnormally
high rate.
Deprecated- see Net.DNS_Resolution_And_TCP_Connection_Latency2
Please list the metric's owners. Add more owner tags as needed.
Deprecated- see Net.DNS_Resolution_And_TCP_Connection_Latency2
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
The time measured before starting DNS lookup until after the connection is
complete.
Deprecated- see Net.DNS_Resolution_And_TCP_Connection_Latency2
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
The number of HTTP request responses with MS Office Docs MIME types. The
responses are classified based on their method type and cacheability (POST,
cacheable GET and non-cacheable GET). The histogram is used in Double GET
Experiment, where successful non-cacheable GET requests are intercepted
after initial response and repeated in order to determine how much reissuing
non-cacheable GET requests influences their error rate. The histogram tracks
only initial requests (not the repeated ones).
Please list the metric's owners. Add more owner tags as needed.
The response codes encountered for GET request repeated in Double GET
Experiment. In the experiment successful non-cacheable GET requests are
intercepted after initial response and repeated. The goal of the experiment
is to measure how much reissuing non-cacheable GET requests influences their
error rate.
Deprecated as of 03/2015. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
Kbps on download streams exceeding 25KB. Measures from the beginning of the
first byte received until the end of flowing data.
skonig@chromium.org
hbengali@chromium.org
Net error codes that requests for images end with, including net::OK and
net:ERR_ABORTED.
Deprecated as of 2011/5/24, replaced by Net.ErrorCodesForMainFrame2, which
measures the same data but uses a different bucket structure (adds guard
buckets).
Please list the metric's owners. Add more owner tags as needed.
Positive net error code that a page failed with. Note that this only counts
the errors in "main frames", so it is a measure of the error pages
that users actually see (it does not for example count the error codes for
subresoures on a page).
Deprecated as of 2012/5/16, replaced by Net.ErrorCodesForMainFrame3, which
measures the same data but includes ERR_ABORTED and OK.
Please list the metric's owners. Add more owner tags as needed.
Positive net error code that a page failed with. Note that this only counts
the errors in "main frames", so it is a measure of the error pages
that users actually see (it does not for example count the error codes for
subresoures on a page).
mmenke@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" (it
does not for example count the error codes for subresoures on a page).
Deprecated as of 2012/5/16, replaced by Net.ErrorCodesForSubresources2,
which measures the same data but includes ERR_ABORT and OK.
Please list the metric's owners. Add more owner tags as needed.
Positive net error code that a page failed with. Note that this only counts
the errors in "subresources".
mmenke@chromium.org
Net error codes that requests for "subresources" end with,
including net::OK and net::ERR_ABORTED.
rdsmith@chromium.org
ellyjones@chromium.org
Counts of various events that can occur on the network error page. See the
histogram for details.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Flush failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file GetSize failed with. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Open failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Read failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Seek failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file SetEof failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Write failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Flush failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Flush. The code is
OS dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file GetSize failed with. Any value other
than 0 indicates that we have received errors in a range outside of the one
in which we recorded the specific errors in Net.FileError_GetSize. The code
is OS dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Open failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Open. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Read failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Read. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Seek failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Seek. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file SetEof failed with. Any value other
than 0 indicates that we have received errors in a range outside of the one
in which we recorded the specific errors in Net.FileError_SetEof. The code
is OS dependent, so when looking at the histogram don't mix OSes.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Write failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Write. The code is
OS dependent, so when looking at the histogram don't mix OSes.
Data collection ended, corresponding feature removed.
bnc@chromium.org
Track usage of alternative services forced by the force-alt-protocols
command line flag. Triggered each time alternative services are queried for
a given origin and the command line flag would make a difference (that is,
there is no advertised alternative service for that origin).
Please list the metric's owners. Add more owner tags as needed.
Whether or not system installed trust anchors could be distinguished from
user installed trust anchors. Recorded on first certificate verification on
Android 4.2 and later.
phajdan.jr@chromium.org
The number of times each FTP Error was observed.
phajdan.jr@chromium.org
The number of Chrome sessions which encountered the indicates FTP Error.
This prevents allowing a user that retried a connection many times (getting
an error each time) from biasing the tallies.
Replaced by Net.FtpServerTypeCount2 on 2012-11-03.
phajdan.jr@chromium.org
Each bucket is the number of times the FTP server type was encountered.
phajdan.jr@chromium.org
Each bucket is the number of times the FTP server type was encountered.
Removed at some time before 2014/09/15.
Please list the metric's owners. Add more owner tags as needed.
The time spent waiting for WinHttpGetProxyForUrl to return with error.
Removed at some time before 2014/09/15.
Please list the metric's owners. Add more owner tags as needed.
The time spent waiting for WinHttpGetProxyForUrl to return with success.
davidben@chromium.org
Records a sample for each HTTPS request to a Google server that either
succeeded or received an inappropriate_fallback alert. This is used to
estimate how frequently the fallback is used to recover from a spurious
network failure.
Replaced with Net.GoogleConnectionUsedSSLVersionFallback2 in Chrome 44.
agl@chromium.org
Nonzero if the HTTP request was to a Google server which required SSL
version fallback. The value indicates the SSL version the request fell back
on. Since Google servers support TLS 1.2, any fallback is an indication of
network middleware problems.
davidben@chromium.org
For each successful HTTPS request to a Google server, whether it used the
SSL version fallback. The value indicates the SSL version the request fell
back on. Since Google servers support TLS 1.2 and FALLBACK_SCSV, any
fallback is an indication of a broken local SSL MITM proxy.
Removed around 2015/03/18. The code which implemented Gzip encoding fixup
was removed.
asanka@chromium.org
Resources are sometimes transferred with an incorrect encoding type of gzip.
net::Filter::FixupEncodingTypes() attempts to correct for these situations
by applying a set of heuristics. This histogram counts the frequency of
usage of these heuristics in the wild.
The count was inaccurate (it counted transactions rather than connections).
Please list the metric's owners. Add more owner tags as needed.
Each bucket is a boolean (0 or 1) indicating whether the user has had a
connection of that type during the session.
This statistic measures successful and failed connections, the new one only
measures successful ones.
Please list the metric's owners. Add more owner tags as needed.
Each bucket is a boolean (0 or 1) indicating whether the user has had a
connection of that type during the session.
davidben@chromium.org
Each bucket is a boolean (0 or 1) indicating whether the user has had a
successful connection of that type during the session.
Replaced by Net.HadFtpServerType2 on 2012-11-13.
phajdan.jr@chromium.org
Each bucket is the number of sessions that encountered a given FTP server
type. Each session reports a given server type at most once.
phajdan.jr@chromium.org
Each bucket is the number of sessions that encountered a given FTP server
type. Each session reports a given server type at most once.
ttuttle@chromium.org
Whether adding an entry to the HTTP auth cache evicted another entry.
ttuttle@chromium.org
When an HTTP auth cache entry is evicted, the time since it was created.
ttuttle@chromium.org
When an HTTP auth cache entry is evicted, the time since it was last used.
ttuttle@chromium.org
Whether adding a path to an entry in the HTTP auth cache evicted another
path.
ttuttle@chromium.org
When looking up an HTTP auth cache entry by path, the position (1-indexed)
of the entry on a hit, or 0 on a miss.
ttuttle@chromium.org
When looking up an HTTP auth cache entry by realm, the position (1-indexed)
of the entry on a hit, or 0 on a miss.
asanka@chromium.org
cbentzel@chromium.org
Per-authentication-scheme counts of authentication attempts and rejections.
Removed in https://crrev.com/209100
Please list the metric's owners. Add more owner tags as needed.
Count of authentication requests for top level pages vs. sub-resources, such
as images or iframes.
asanka@chromium.org
cbentzel@chromium.org
Per-authentication-scheme counts of authentication targets, such as secure
servers or proxies.
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
Time between the HttpNetworkTransaction requesting a connection and the time
it connected.
Please list the metric's owners. Add more owner tags as needed.
Length of time that a received resource will be cacheable.
bengr@chromium.org
Size of the response body. This is the actual number of bytes received,
which usually agrees with but is not necessarily the same as the size
specified by the Content-Length header.
bengr@chromium.org
Size of the response body if it is cacheable. This is the actual number of
bytes received, which usually agrees with but is not necessarily the same as
the size specified by the Content-Length header.
bengr@chromium.org
Size of the response body if it is cacheable for at least 24 hours. This is
the actual number of bytes received, which usually agrees with but is not
necessarily the same as the size specified by the Content-Length header.
bengr@chromium.org
Size of the response body if it is cacheable for at least 4 hours. This is
the actual number of bytes received, which usually agrees with but is not
necessarily the same as the size specified by the Content-Length header.
bengr@chromium.org
The difference between the size specified in the X-Original-Content-Length
header and the size of teh response body. This is zero if the
X-Original-Content-Length header is not present in the response.
bengr@chromium.org
The difference between the size specified in the X-Original-Content-Length
header and the size of the response body. Only includes resources that have
the X-Original-Content-Length header.
bengr@chromium.org
Size of the response body. Only includes resources that have the
X-Original-Content-Length header.
mmenke@chromium.org
Records the frequency with which a number of hacky HTTP header parsing rules
are invoked. This histogram should be removed after we have enough data to
know if we can remove the hacks.
tsepez@chromium.org
Count of requests which contained a basic auth username and password
embedded in the URL itself.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading, for jobs served from the cache.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until
the job is killed. Note that we didn't detect the end of the data for this
job.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading, for jobs not served from the cache.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading, for jobs when we read until no more data is available.
bengr@chromium.org
Size specified in the X-Original-Content-Length header. If this header is
not present in the response, the size of the response body is used.
bengr@chromium.org
Size specified in the X-Original-Content-Length header. Only includes
resources that have the X-Original-Content-Length header.
mmenke@chromium.org
Time it takes to request a new (unused) HTTP proxy socket.
sclittle@chromium.org
bengr@chromium.org
The network error code that the HTTP request completes with, including OK
and ABORTED.
sclittle@chromium.org
bengr@chromium.org
The network error code that the HTTP main frame resource request completes
with, including OK and ABORTED.
mmenke@chromium.org
The count of HTTP Response codes encountered.
mmenke@chromium.org
The count of HTTP Response codes encountered, in response to MAIN_FRAME
requests only; saving only the hundreds digit, e.g. 100->1, 300->3.
rtenneti@chromium.org
The location in http_server_properties_manager.cc where UpdatePrefs was
called.
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of sockets (all HTTP sockets, regardless of any proxy
used) used for HTTP[s].
mmenke@chromium.org
Time from when an HTTP request is issued to when the first byte is
processed.
Please list the metric's owners. Add more owner tags as needed.
The count of handleable socket errors (connection abort/close/reset) per
socket reuse type.
Late bindings are on by default now.
Please list the metric's owners. Add more owner tags as needed.
The count of handleable socket errors (connection abort/close/reset) per
socket reuse type. Socket late binding is disabled.
Late bindings are on by default now.
Please list the metric's owners. Add more owner tags as needed.
The count of handleable socket errors (connection abort/close/reset) per
socket reuse type. Socket late binding is enabled.
Deprecated 11/2014. No longer tracked.
bengr@chromium.org
Time from when the IOThread is created to when the first URL request is
started. Only requests that are created for a profile while Chrome is
starting up are considered.
Deprecated 1/2015. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Duration of time spent during the UDP-connect IPv6 probe.
Deprecated 03/2015. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Whether the interface-enumeration IPv6 probe method failed given that the
UDP-connect IPV6 probe failed.
Deprecated 03/2015. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Whether the interface-enumeration IPv6 probe method was successful given
that the UDP-connect IPV6 probe was successful.
Please list the metric's owners. Add more owner tags as needed.
The probe results when a test for IPv6 support is done.
Please list the metric's owners. Add more owner tags as needed.
The probe results when a test for IPv6 support is done, after a network
change event.
jkarlin@chromium.org
The distribution of storable vs "cache-control: no-store"
main-frame resources.
Counted after response headers have completed and before the content has
completed. Redirects are counted. All HTTP cache transactions are counted,
not just those that require the network.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The time that a (non-cancelled) proxy resolution request was stalled waiting
for an execution thread, for MultiThreadedProxyResolver.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that it took for a (non-cancelled) proxy resolution request
to complete, for MultiThreadedProxyResolver.
Removed in Chrome 44.
eroman@chromium.org
Counts the number of browser launches where chrome://net-internals and
chrome://net-internals/#tests are used.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download the main frame of a page in
response to specific HTTP network errors succeeds.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download a subresource in response to
specific HTTP network errors succeeds.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download the main frame of a page in
response to specific HTTP network errors returns another network error.
Histogram includes only the error code that triggered the retry.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download a subresource in response to
specific HTTP network errors returns another network error. Histogram
includes only the error code that triggered the retry.
Please list the metric's owners. Add more owner tags as needed.
On Windows, NetworkChangeNotifierWin calls NotifyAddrChange, which can fail
for unknown reasons. This records the number of times it fails in a row
before a successful call. If it never succeeds, or takes over 100 tries, a
value of 100 is recorded. See http://crbug.com/69198
Please list the metric's owners. Add more owner tags as needed.
The number of duplicate cookies that were present in the cookie store during
startup.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to make one or more HTTP
fetches to OCSP responders in order to get revocation information. This
measures the amount of time that failures to get OCSP information take.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to make one or more HTTP
fetches to OCSP responders in order to get revocation information. This
records the fraction of successful requests.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to make one or more HTTP
fetches to OCSP responders in order to get revocation information. This
measures the amount of time that each of those requests takes.
rsleevi@chromium.org
When connecting over HTTPS, a server may include an OCSP response as part of
the TLS handshake so that clients do not have to fetch it, provided the
client requested the server do so. This measures whether or not a server
included an OCSP response when it was requested.
Please list the metric's owners. Add more owner tags as needed.
Positive error code that was returned by the system library
"getaddrinfo()". This error code is platform specific, so when
there is a Windows/Linux conflict, both decodings are shown.
Please list the metric's owners. Add more owner tags as needed.
Positive error code that was returned by the system library
"getaddrinfo()".
Please list the metric's owners. Add more owner tags as needed.
Positive error code that was returned by the system library
"getaddrinfo()".
Please list the metric's owners. Add more owner tags as needed.
Positive error code that was returned by the system library
"getaddrinfo()".
Deprecated 4/16/2014. No longer tracked.
davidben@chromium.org
How long it took for an <a ping> request to receive a response. Only
recorded if a response was received.
Deprecated 4/16/2014. No longer tracked.
davidben@chromium.org
The result of an <a ping> request, whether it received a response or
timed out or failed for some other reason.
Please list the metric's owners. Add more owner tags as needed.
Indicate whether a link navigation was preceded by a recent pre-connect
trigger (within 10 seconds). There is a high chance that loading the page
used a preconnected TCP session.
Please list the metric's owners. Add more owner tags as needed.
Indicate whether a URLRequest was preceded by a recent pre-connect trigger
(within 10 seconds). There is a high chance that loading the resource used a
preconnected TCP session.
Please list the metric's owners. Add more owner tags as needed.
When a preconnection is made, indicate what the motivation was.
Currently, the most common (only?) motivations are SELF_REFERAL,
LEARNED_REFERAL and OMNIBOX. The SELF_REFERAL indicates that we made sure a
second connection was available for a resource that either was never before
seen, or has historically had no subresources. The LEARNED_REFERAL
indicates that we "learned" that a subresource was commonly
needed, and that motivated the TCP/IP preconnect. The OMNIBOX motivation
happens when a search is being suggested, and we preconnect to the search
provider. (WARNING: Prior to version 7.517.*, enums 7, 8, and 9 may be
confused, as EARLY_LOAD_MOTIVATED was inserted new 6 value.)
Please list the metric's owners. Add more owner tags as needed.
Indicate whether there was a proxy to preclude preconnection.
Please list the metric's owners. Add more owner tags as needed.
What did we decide to do about a predicted resource, based on the historical
expected number of connection that this subresource will require.
This is basically the current thresholding of the SubresourceExpectation,
relative to current static thresholds, and taking into account whether
preconnection is enabled (i.e., if preconnection is disabled, we'll never
decide to preconnect).
Please list the metric's owners. Add more owner tags as needed.
The expected number of connections, times 100, that we'll make to a given
subresource, based on learned history.
By comparing this to thresholds, we decide if we will preconnect,
preresolve, or do nothing. This histogram can be used to select those static
thresholds.
Please list the metric's owners. Add more owner tags as needed.
Indicate whether if a preconnect trigger is followed by a resource request
(from link navigations) to the host or not. This is to measure precision of
link-based preconnect triggers.
Sourced data corrected, and replaced by NetPreconnectUtilization2
Please list the metric's owners. Add more owner tags as needed.
Indicate final utilization for each attempted socket connection.
We also include stats for non-speculative sockets. Some socket connections
may never connect, and others may never be used (as the user may abort
before then).
Please list the metric's owners. Add more owner tags as needed.
Indicate final utilization for each attempted socket connection.
We also include stats for non-speculative sockets. Some socket connections
may never connect, and others may never be used (as the user may abort
before then).
jkarlin@chromium.org
The completion status of prefetches that have finished loading.
Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled
before that point are not registered.
Note that "success from cache" means that the
UrlRequest::was_cached() was true, and "success from network"
means that was_cached() was false. Validated results are considered cached,
even though a conditional network request is made.
jkarlin@chromium.org
Number of bytes read from the network on behalf of prefetch requests. This
is prefilter, so before any decompression.
jkarlin@chromium.org
Time spent on prefetch requests before the request was canceled.
jkarlin@chromium.org
Time spent on prefetch requests when fetched from cache.
jkarlin@chromium.org
Time spent on prefetch requests when fetched from the network, including
validation time.
sclittle@chromium.org
Records how many *.googlezip.net Data Reduction Proxies were removed from
the effective proxy configuration when a proxy reconfiguration occurs.
Replaced by Net.Priority_High_Latency_b.
Please list the metric's owners. Add more owner tags as needed.
Time from the start of the http transaction until the first byte of the
response for high priority (currently frame and subframe) requests. Only
times under 10 minutes are recorded.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
Time from the start of the http transaction until the first byte of the
response for high priority (currently frame and subframe) requests.
Replaced by Net.Priority_Low_Latency_b.
Please list the metric's owners. Add more owner tags as needed.
Time from the start of the http transaction until the first byte of the
response for low priority (non-frame/subframe) requests. Only times under
10 minutes are recorded.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
Time from the start of the http transaction until the first byte of the
response for low priority (non-frame/subframe) requests.
rch@chromium.org
When a PROXY_AUTH_REQUESTED error code is handled in
net::HttpStreamFactoryImpl::Job::RunLoop, this is true if connection_ has an
associated value.
Removed at some time before 2014/09/15.
Please list the metric's owners. Add more owner tags as needed.
The time in milliseconds spent fetch the system proxy configuration, when
polling it for changes.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent executing the proxy script during
"tracing" runs (executions of the script which discovered a new
DNS dependency and were subsequently abandoned).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent executing the proxy script during
"tracing" runs (executions of the script which discovered a new
DNS dependency and were subsequently abandoned).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent in the non-blocking DNS bindings
while executing PAC scripts. This includes the times for abandoned
executions.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The amount of time inside of V8 that the proxy script spent executing for
the final pass. This includes the time spent in the javascript bindings.
This does not include the time spent in abandoned execution passes.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that alert() was called in the final execution of the
script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of errors that were seen in the final execution of the script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that the PAC script execution was restarted.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that the proxy resolution took. This includes all the time
spent waiting for DNS, PAC script execution, and restarts.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that proxy resolution spent waiting for DNS. This also
includes any queuing delays on the origin thread waiting for the DNS result
to be processed.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of unique DNS hostnames that the PAC script tried to resolve. The
*Ex() versions of the bindings count separately.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent in the non-blocking DNS bindings
while executing PAC scripts. This includes the times for abandoned
executions.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The amount of time inside of V8 that the proxy script spent executing for
the final pass. This includes the time spent in the javascript bindings
(which is probably dominated by Net.ProxyResolver.DnsWaitTotalTime). This
does not include the time spent in abandoned execution passes.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that alert() was called in the final execution of the
script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of errors that were seen in the final execution of the script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that the PAC script execution was restarted.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The amount of time it took upon completion to run the final task posted back
to the IO thread.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that the proxy resolution took. This includes all the time
spent waiting for DNS, PAC script execution, and restarts.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that proxy resolution spent waiting for DNS. This also
includes any queuing delays on the origin thread waiting for the DNS result
to be processed.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that the proxy resolution took, not including the post back
to the origin thread. This includes all the time spent waiting for DNS, PAC
script execution, and restarts.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of unique DNS hostnames that the PAC script tried to resolve. The
*Ex() versions of the bindings count separately.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The length of the URL that was passed into the PAC script.
eroman@chromium.org
The time taken to resolve a URL by forwarding the request to the proxy
resolver and executing the PAC script. This includes PAC script execution,
DNS queries, and internal retries. This does not include retries initiated
by the user, such as by calling ProxyService::ReconsiderProxyAfterError().
eroman@chromium.org
Whether proxy resolution occured by forwarding the request to the proxy
resolver and executing the PAC script. This histogram records all URLs,
regardless of whether a proxy configuration is set. Note that in some cases,
the system proxy resolver is used. If so, this histogram indicates whether
the request was forwarded to the system resolver. However, on desktop
platforms, the number of users using the system resolver should be small
since the default is to use V8. Hence, the count of emissions to the 'True'
bucket on desktop caused by users of the system resolver should be small.
eroman@chromium.org
The total time taken to resolve a URL. This includes PAC script execution,
DNS queries, and internal retries. This does not include retries initiated
by the user, such as by calling ProxyService::ReconsiderProxyAfterError().
eroman@chromium.org
Whether a proxy resolution resulted in the PAC script terminating
unexpectedly. This only happens when the resolver process crashes when using
out-of-process PAC.
agl@chromium.org
Second-level domains for which we have observed public key pinning failures.
agl@chromium.org
A validated certificate chain may be subject to additional
"pinning" requirements on a per-domain basis. This records the
fraction of successful matches between a certificate chain and a pin list.
rtenneti@chromium.org
The number of active QUIC sessions before we activate a new QUIC session.
rtenneti@chromium.org
The reject reasons for QUIC's CHLO (client hello) message from server
Deprecated 08/2014, and replaced by
Net.QuicClientHelloServerConfig.InvalidDuration.
rtenneti@chromium.org
How expired server config is for sending inchoate ClientHello to the server.
rtenneti@chromium.org
The time since expiration of server config when we sent inchoate ClientHello
to the server.
Deprecated as of 11/2014. Replaced by Net.QuicInchoateClientHelloReason.
rtenneti@chromium.org
The reason (the state of the server config) for sending inchoate ClientHello
to the server.
rtenneti@chromium.org
The number of times CryptoClientConfig's CachedState is populated from
canonical config whenever we create a new CryptoClientConfig::CachedState.
rtenneti@chromium.org
Tracks number of times data read/parse/write API calls of QuicServerInfo to
and from disk cache is called.
rtenneti@chromium.org
Deprecated as of 10/2014.
Tracks the opening and closing of disk cache entries. Recorded each time a
disk cache entry is either opened or closed.
rtenneti@chromium.org
Tracks failure reasons to read/load/write of QuicServerInfo to and from disk
cache.
rch@chromium.org
The number of ports suggested per server.
rch@chromium.org
The number of QUIC packets received by a QUIC connection whose handshake was
not confirmed when that connection is closed.
rch@chromium.org
The state of a QUIC connection's crypto hanshake as it progresses from
starting to confirmation or failure.
rtenneti@chromium.org
The reason (the state of the server config) for sending inchoate ClientHello
to the server.
rch@chromium.org
The number of client hello messages sent.
see Net.QuicSession.Connect*PortForHTTP*
rch@chromium.org
The number of client hello messages sent when the crypto handshake was
confirmed.
rtenneti@chromium.org
The number of times ServerConfigUpdateMessages ignored.
rch@chromium.org
The number of stream frames bundled within a received packet.
rch@chromium.org
The number of stream frames per stream ID within a received packet.
rtenneti@chromium.org
Time spent to load QUIC server information from disk cache.
Deprecated as of 10/2014. Replaced by DiskCacheWaitForDataReadyTime.
rch@chromium.org
Time spent to load QUIC server information from disk cache.
rtenneti@chromium.org
The state of the QUIC server information when it's loaded from the disk
cache.
rtenneti@chromium.org
Time spent waiting to load QUIC server information from disk cache.
rtenneti@chromium.org
The number of times AlternateProtocolMap supports QUIC, but there is no QUIC
server information in the disk cache. This is recorded whenever QUIC server
information is loaded from the disk cache.
rtenneti@chromium.org
The elapsed time between waiting for reading of QUIC server information from
disk cache, and receiving crypto handshake confirmation from the server.
Will measure the impact of cancelling the WaitForDataReady callback. Logged
after crypto handshake is confirmed.
rtenneti@chromium.org
The ratio of the time spent waiting to load QUIC server information from
disk cache to the min rtt. Logged when session is closed.
rch@chromium.org
This histogram summarizes information about a 21 packet sequence, indicating
for each of the 21 possible prefixes of this pattern, how many packets were
received in that prefix. The first range uses buckets 0 and 1, and it
describes the 1st packet in the sequence. It indicates if the first packet
was missing (bucket 0), or the first packet was present (bucket 1). The
second range uses buckets 2 through 4, and describes the first 2 packets in
the prefix of this sequence. It indicates if there were no packets received
in the first two packets (bucket 2), or there was one out of two packets
received (bucket 3), or if there was two out of tow received (bucket 4).
etc. etc. Reading this histogram may require post-processing in a spread
sheet, but can indicate the potential value of using FEC packets to convey
data.
rch@chromium.org
Each of the 64 buckets represents a different binary pattern of 6
consecutive packets that were received by the client. The LSB of the bucket
number corresponds to the reception of the oldest packet. A bit in the
bucket-number being 1 indicates the packet was received, and a 0 means the
packet was never received (by the client).
rch@chromium.org
True if the result of reading a packet from the network was ERR_IO_PENDING.
Recorded for each packet when Read() returns.
rtenneti@chromium.org
The number of BLOCKED frames recevied by a QuicSession when the session is
closed.
rtenneti@chromium.org
The number of BLOCKED frames sent by a QuicSession when the session is
closed.
rch@chromium.org
True if the QUIC session is closed during the call to InitializeSession,
logged for each session just after InitializeSession is called.
rch@chromium.org
The network error code which resulted in the session being closed.
rch@chromium.org
Samples of the number of round-trips needed by a QUIC connection before a
request could be sent by the client.
rch@chromium.org
The QUIC error which caused a QUIC connection to be closed before the
hanshake was confirmed, in the case where no packets were received. This
provides a breakdown of the entires in
Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value
is BLACK_HOLE.
rch@chromium.org
The QUIC error which caused a QUIC connection to be closed before the
hanshake was confirmed, in the case where at least 1 packet was received.
This provides a breakdown of the entires in
Net.QuicSession.ConnectionClose.HandshakeNotConfirmed.Reason where the value
is UNKNOWN.
rch@chromium.org
The reason a QUIC handshake failed.
rch@chromium.org
The number of streams open when a QUIC session crypto handshake timed out.
rch@chromium.org
The number of streams open when a QUIC session timed out.
rch@chromium.org
The number of total streams created when a QUIC session crypto handshake
timed out.
rch@chromium.org
The QUIC error code which resulted in the connection being closed.
rch@chromium.org
The QUIC error code which resulted in the connection being closed by the
client.
rch@chromium.org
The QUIC error code which resulted in the connection being closed by the
server.
rtenneti@chromium.org
Whether QUIC session's connection is flow control blocked when a PING
message is sent to server.
rch@chromium.org
The IP Address family of this connection, as reported by the server.
rch@chromium.org
The IP Address family of this connection, as seen locally.
jri@chromium.org
Samples of the number of round-trips needed by a QUIC connection before a
request could be sent by the client, when handshake confirmation was
required. (The operating system randomly selected a source port for the
connection.)
rch@chromium.org
Logs whether channel ID was used when a cookie is sent over QUIC to
https://accounts.google.com.
jar@chromium.org
rch@chromium.org
Count of errors during attempts to create a QUIC session (before even using
the session).
rch@chromium.org
The number of duplicate packets recevied by a QuicSession when the session
is closed.
rch@chromium.org
The value of the TCP cubic sender's CWND when the session is closed.
rch@chromium.org
The elapsed time between starting the crypto handshake, and receiving
confirmation from the server.
see Net.QuicSession.Connect*PortForHTTP*
rch@chromium.org
Samples of the number of round-trips needed by a QUIC connection before a
request could be sent by the client.
rch@chromium.org
The frames received on the headers stream which arrived early.
rtenneti@chromium.org
The elapsed time between the end of resolving the DNS name of the server for
a QUIC connection, and receiving crypto handshake confirmation from the
server. Logged after crypto handshake is confirmed.
rch@chromium.org
Time spent resolving the DNS name of the server for a QUIC connection.
rch@chromium.org
The number packets recevied by a QuicSession with an incorrect connection id
when the sesesion is closed.
rch@chromium.org
If a QUIC connection timed out locally with open streams, this contains the
time since any data was read from the network until the connection was
closed. The suffix specifies whether there were any unacked packets pending
when the connection timed out.
rch@chromium.org
The maximum packet sequence number reordering observed by a QUIC connection.
rch@chromium.org
The ratio of the maximum reordering time of a QUIC packet to the min rtt.
rch@chromium.org
The ratio of the maximum reordering time of a QUIC packet to the min rtt,
only for those sessions with a min rtt larger than 100 ms.
rch@chromium.org
The number of QUIC streams opened when a new QUIC stream is created.
rch@chromium.org
The total number of streams created by the client when the session is
closed.
rch@chromium.org
The number of missing packets between the current received packet and the
previously largest received packet sequence number, when the current
received packet had a lower sequence number than the previously received
packet sequence number.
rch@chromium.org
The number of times the current received packet had a lower sequence number
than the previously received packet sequence number, and the size of the
current packet is larger than the size of the previous packet.
rch@chromium.org
The number of times the current received packet had a lower sequence number
than the previously received packet sequence number.
rch@chromium.org
The number of missing packets between the current received packet and the
previously largest received packet sequence number.
rch@chromium.org
The number of missing packets between the current received packet and the
previously largest received packet sequence number, as reported by the
remote end of the connection.
rch@chromium.org
The ratio of the number of missing packets, to the maximum packet sequence
number received, for QUIC connections longer than 21 packets received via
rch@chromium.org
Each bucket corresponds to a specific packet sequence number that was sent
by a server to Chrome at the start of a QUIC connection. This histogram is
compared, bucket by bucket, with a second histogram to compute the ratio for
each bucket (each packet sequence number).
rch@chromium.org
The time taken to Write() a QUIC packet to the socket. Recorded for each
packet when it is sent. The suffix specifies if the write completed
synchonously or asynchronously.
wtc@chromium.org
When a public reset packet is received, whether the client IP address and
port number in it differ from the client IP address and port number in the
ServerHello handshake message. In the comparison, the first address is the
one in ServerHello and the second address is the one in public reset. Note:
this histogram is obsolete because it failed to treat IPv4-mapped IPv6
addresses as IPv4 addresses.
wtc@chromium.org
When a public reset packet is received, whether the client IP address and
port number in it differ from the client IP address and port number in the
ServerHello handshake message. In the comparison, the first address is the
one in ServerHello and the second address is the one in public reset.
rch@chromium.org
Version of the QUIC protocol used for this connection.
rch@chromium.org
The network error code returned when attempting to read to a QUIC
connection.
rch@chromium.org
The QUIC error code which resulted in a stream being reset by the client.
rch@chromium.org
The QUIC error code which resulted in a stream being reset by the server.
rch@chromium.org.
The number of request for secure resources over QUIC sessions. True if the
session is secure, false if it is not.
rtenneti@chromium.org
Whether any of QUIC session's streams are flow control blocked when a PING
message is sent to server.
rch@chromium.org
The number of stream frames received which were duplicates, out of every
1000 stream frames received. Only for QUIC sessions which received at least
100 packets.
rch@chromium.org
The percentage of stream frames received which were duplicates. Only for
QUIC sessions which received at least 100 packets.
rch@chromium.org
The percentage of stream frames received which were duplicates. Only for
QUIC sessions which received fewer than 100 packets.
rch@chromium.org
The number of stream frames received which were duplicates, out of every
1000 stream frames received. Only for QUIC sessions which received fewer
than 100 packets.
rch@chromium.org
If a QUIC connection timed out with open streams, this contains a count of
consecutive RTOs.
rch@chromium.org
If a QUIC connection timed out with open streams, this contains a count of
consecutive TLPs.
rch@chromium.org
If a QUIC connection timed out with open streams, this will be true when the
connection has unacked packets.
rch@chromium.org
Deprecated 04/2015. Tracked as Net.QuicSession.TooManyOpenStreams.
True if more than 100 streams are open when a new stream is activated.
rch@chromium.org
True if more than 100 streams are open when a new stream is activated.
rch@chromium.org
The number of truncated ACK frames received.
rch@chromium.org
The number of truncated ACK frames sent.
rch@chromium.org
The number of undecryptable packets recevied by a QuicSession when the
sesesion is closed.
rch@chromium.org
The location in quic_client_session.cc where a session is unexpectedly not
going away.
rch@chromium.org
The location in quic_client_session.cc where there were unexpected
observers.
rch@chromium.org
The location in quic_client_session.cc where there were unexpected open
streams.
rch@chromium.org
The network error code returned when attempting to write to a QUIC
connection.
rtenneti@chromium.org
Recorded whenever QUIC is disabled for a port due to repeated lossy
connections (high packet loss on multiple consecutive connections). QUIC is
disabled until next reboot of Chrome.
rtenneti@chromium.org
Logged whenever proof verification fails and if the failure occurred before
or after the crypto handshake is confirmed.
Deprecated 03/2015. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
True if the HTTP request was sent to a server which supports the TLS
renegotiation extension.
rdsmith@chromium.org
The amount of time between request initiation and request completion for
success and various different errors.
clamy@chromium.org
When starting a cross-site navigation, the time between reading the headers
and body of the response.
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The time an already used socket sat idle before being used.
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The time an unused socket (all HTTP sockets, regardless of any proxy used)
sat idle before being used.
Please list the metric's owners. Add more owner tags as needed.
The time a previously used socket sat idle before encountering a recoverable
socket IO error (connection abort/reset/close).
Please list the metric's owners. Add more owner tags as needed.
The time an unused socket sat idle before encountering a recoverable socket
IO error (connection abort/reset/close).
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
Net error codes that socket initializations end with, including net::OK and
net::ERR_ABORTED.
Replaced by Net.SocketUnchangeableReceiveBuffer 3/31/2014.
jar@chromium.org
The size of a socket's receive buffer when the attempt to change it via
setsockopt failed.
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
Time in milliseconds from initial RequestSocket() call until successfully
acquiring a connected socket.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
The time from the connection start to connection establish.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
The time waiting to be ready to start connecting.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Each bucket is the number of connection type of socket stream.
Deprecated 2014-10-28. No longer generated. Replaced by
Net.WebSocket.Duration.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
The time a socket stream was open.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Each bucket is the number of protocol type on socket stream.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Number of bytes on a socket stream.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Number of reads on a socket stream.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Number of bytes on a socket stream.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Number of Write on a socket stream.
Deprecated as of 03/2015.
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of sockets returned by the socket pools.
jar@chromium.org
The size of a socket's receive buffer when the attempt to change it via
setsockopt failed.
jar@chromium.org
The size of a socket's send buffer when the attempt to change it via
setsockopt failed.
see SocketIdleTimeBeforeNextUse_ReusedSocket_SOCK
Please list the metric's owners. Add more owner tags as needed.
The time an already used SOCKS socket sat idle before being used.
see SocketIdleTimeBeforeNextUse_UnusedSocket_SOCK
Please list the metric's owners. Add more owner tags as needed.
The time an unused SOCKS socket sat idle before being used.
see SocketRequestTime_SOCK
Please list the metric's owners. Add more owner tags as needed.
Time from initial SOCKSClientSocketPool::RequestSocket() call until
successfully acquiring a connected SOCKS socket.
Please list the metric's owners. Add more owner tags as needed.
Time it takes to request a new (unused) SOCKS proxy socket.
see SocketType_SOCK
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of sockets returned by the SOCKS pool.
Replaced by Net.SpdyConnectionLatency_2 on 2014-10-21.
rch@chromium.org
Time from when the Connect() starts until it completes.
rch@chromium.org
Time from when the Connect() starts until it completes.
rch@chromium.org
The counts of the flow control state of each frame (with stream and session
flow control on).
rch@chromium.org
The counts of the flow control state of each frame (with stream flow control
on).
Obsolete as HTTP/2 standard is finalized.
bnc@chromium.org
Frequencies of characters observed in request and response headers.
Temporarily being collected to inform the construction of an optimized
Huffman code for the HTTP/2 specification. Buckets are ASCII codes offset by
1.
rch@chromium.org
Status of checking if a SPDY domain can handle a IP match. If a match is
found, we successfully used the IP Pooling. If a match is not found, we
could have used IP Pooling, except the TLS Cert didn't match the IP-pooled
domain.
rch@chromium.org
The RTT for SPDY's PING.
rch@chromium.org
The count of streams at each priority over Spdy sessions.
rch@chromium.org
The number of bytes recevied per stream.
rch@chromium.org
The number of bytes sent per stream.
rch@chromium.org
Total number of bytes recevied per session before closing session due to
EOF.
rch@chromium.org
Total number of bytes recevied per session before closing session due to an
error during read.
rch@chromium.org
Net error codes when SpdySession was closed, doesn't inlcuding net::OK.
rch@chromium.org
Socket connected status in SpdySession::CreateStream.
Replaced by SpdySessionErrorDetails2 on 2013-04-19.
rch@chromium.org
WARNING: r181910 added an enum value in the middle, so don't trust the
counts for values 9 and above for Chrome builds after that revision.
The type of SPDY Protocol error encountered.
rch@chromium.org
The type of SPDY Protocol error encountered.
Replaced by SpdySessionErrorDetails_Google2 on 2013-04-19.
rch@chromium.org
The type of SPDY Protocol error encountered when talking to a google.com
server.
rch@chromium.org
WARNING: r181910 added an enum value in the middle, so don't trust the
counts for values 9 and above for Chrome builds after that revision.
The type of SPDY Protocol error encountered when talking to a google.com
server.
rch@chromium.org
The type of SPDY Session used when looking up a session.
rch@chromium.org
Whether SpdySession::Get{Peer,Local}Address was called when the connection
had no socket.
Deprecated 7/21/2014. No longer tracked.
bengr@chromium.org
bolian@chromium.org
rch@chromium.org
The count of SPDY sessions using the data reduction proxy and the count of
other SPDY sessions.
rch@chromium.org
SpdySession::GetLocalAddress returned ERR_SOCKET_NOT_CONNECTED.
rch@chromium.org
SpdySession::GetPeerAddress returned ERR_SOCKET_NOT_CONNECTED.
rch@chromium.org
The count of SPDY Sessions with or without stalls.
rch@chromium.org
The congestion window (in pkts) received at the end of a SpdySession.
rch@chromium.org
The congestion window (in pkts) sent at the beginning of a SpdySession.
rch@chromium.org
Percentage of sessions which received settings from the server.
rch@chromium.org
The Download Retransmission Rate (%) received at the end of a SpdySession.
rch@chromium.org
The RTT received at the end of a SpdySession.
rch@chromium.org
Percentage of sessions which sent settings to the server.
rch@chromium.org
The time between receiving the first chunk and the last chunk of data on a
Spdy stream.
rch@chromium.org
The number of pushed, but abandoned streams over a single session.
rch@chromium.org
The number of streams issued over a single session.
rch@chromium.org
The number of pushed, and used streams over a single session.
rch@chromium.org
The number of push streams received over a single session.
rch@chromium.org
The number of stream stalls per session.
rch@chromium.org
The time of a Spdy stream. Measured from sending the first chunk to
receiving the last chunk of data.
rch@chromium.org
The time between sending the request and receiving the first chunk of data
on a Spdy stream.
rch@chromium.org
The percent compression achieved when compression SYN_STREAM frames.
Deprecated on 2014-09-11, because the uploaded values were changing as
protocols were removed, therefore statistics couldn't be combined accross
different builds. Replaced by Net.SpdyVersion2.
rch@chromium.org
The SPDY protocol version that is used to talk to SPDY servers.
bnc@chromium.org
The SPDY protocol version that is used to talk to SPDY servers. Logged
every time a SPDY session is initialized.
agl@chromium.org
rsleevi@chromium.org
The SSL/TLS cipher suite that was negotiated. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds.
agl@chromium.org
Counts of specific error codes returned when opening an SSL connection.
jeremyim@chromium.org
Counts of specific error codes returned when opening an SSL connection for
an endpoint which is eligible for fastradio padding.
Replaced by Net.SSL_Connection_Latency_2 on 2014-10-21.
agl@chromium.org
Time from when the Connect() starts until it completes.
agl@chromium.org
Time from when the Connect() starts until it completes.
Deprecated 7/21/2014. No longer tracked.
bengr@chromium.org
bolian@chromium.org
Time from when the Connect() starts until it completes when using the data
reduction proxy. This includes certificate retrieval and verification.
Replaced by Net.SSL_Connection_Latency_Google2 on 2014-10-21.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it. This only includes users in a 50% field trial that
disables revocation checking for certificate pinned sites.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it. This only includes users not in a 50% field trail that
disables revocation for certificate pinned sites.
eranm@chromium.org
rsleevi@chromium.org
The state of compliance with Certificate Transparency presence requirements
for each EV certificate. An EV certificate could be non-compliant (in which
case it loses the EV status), comply through inclusion in the EV whitelist
or have the required number of Signed Certificate Timestamps. This metric
will gauge adoption rate of Certificate Transparency and will help identify
when the EV whitelist is no longer needed. Emitted during every SSL
connection establishment, but only if the client is checking compliance with
Certificate Transparency requirements (currently guarded by a Finch
experiment).
eranm@chromium.org
rsleevi@chromium.org
Whether an EV certificate is present in the Certificate Transparency
whitelist. Emitted once for every EV certificate encountered (during SSL
connection establishment), but only if the client has a valid whitelist.
eranm@chromium.org
rsleevi@chromium.org
Whether the client holds a valid EV Certificates whitelist or not. Only
emitted when an EV cert that is not compliant with the Certificate
Transparency requirement is encountered. This histogram is intended to be
short-lived and help determine if EV certificates are considered
non-compliant because they are not whitelisted or if the client does not
hold a valid instance of the whitelist.
agl@chromium.org
Counts the number of times that users have hit blacklisted certificates. The
indexes match up to the indexes in
net/base/x509_certificate.cc:IsBlacklisted. The details of the certificates
in question is confidential.
rsleevi@chromium.org
Time to complete a certificate verification (success case).
rsleevi@chromium.org
Time to complete a certificate verification (error case).
davidben@chromium.org
For each successful HTTPS request which used the TLS version fallback, the
error code of the last failed attempt.
davidben@chromium.org
For each successful HTTPS request which used the TLS version fallback, the
type of handshake failure of the last failed attempt.
Please list the metric's owners. Add more owner tags as needed.
Time to complete a DNS lookup for a DNS CAA record.
Please list the metric's owners. Add more owner tags as needed.
Time that we would have wasted had we waited for a CAA lookup in order to
validate a certificate.
Please list the metric's owners. Add more owner tags as needed.
Time to complete a speculative certificate verification.
bnc@chromium.org
TLS extension used to negotiate protocol (ALPN or NPN); in case of NPN,
whether the protocol is indeed supported by both the client and the server
or is a fallback because of no overlap; and the negotiated protocol itself.
davidben@chromium.org
For each SSL connection that resumed a session, whether the session was
resumed at the same version it was established at. This is only recorded in
BoringSSL ports.
Removed on 2014-08-20.
Please list the metric's owners. Add more owner tags as needed.
The number of times that we have performed SSLv3 fallback and found a TLS
renegotiation patched server.
Please list the metric's owners. Add more owner tags as needed.
Was a speculative certificate verification used?
Please list the metric's owners. Add more owner tags as needed.
Time saved by a speculative certificate vertification.
davidben@chromium.org
The SSL/TLS version that was negotiated. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds.
Please list the metric's owners. Add more owner tags as needed.
Number of idle sockets when the Connect() succeeded.
mmenke@chromium.org
Time from when the Connect() starts until it completes. Only times under 10
minutes are logged.
mmenke@chromium.org
Time from when the Connect() starts until it completes when the network
address only contains IPv4 addresses. Only times under 10 minutes are
logged.
mmenke@chromium.org
Time from when the Connect() starts until it completes when the IPv4
fallback connection won the race against IPv6. Only times under 10 minutes
are logged.
mmenke@chromium.org
Time from when the Connect() starts until it completes when we race an IPv6
connection against an IPv4 connection with a 300ms delay. Only times under
10 minutes are logged.
mmenke@chromium.org
Time from when the Connect() starts until it completes when the network
address only contains IPv6 addresses. Only times under 10 minutes are
logged.
jri@chromium.org
For sockets for which a TCP Fast Open protocol might be used, the result of
trying to use it.
see SocketIdleTimeBeforeNextUse_ReusedSocket_TCPforSOCKS
Please list the metric's owners. Add more owner tags as needed.
The time an already used TCP socket sat idle before being used for a SOCKS
request.
see SocketIdleTimeBeforeNextUse_UnusedSocket_TCPforSOCKS
Please list the metric's owners. Add more owner tags as needed.
The time an unused TCP socket sat idle before being used for a SOCKS
request.
see SocketRequestTime_TCPforSOCKS
Please list the metric's owners. Add more owner tags as needed.
Time from initial SOCKSClientSocketPool::RequestSocket() call until
successfully acquiring a connected TCP socket.
see SocketType_TCPforSOCKS
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of sockets returned by the TCP pool used by the SOCKS
pool.
Was only used for HTTP[S] connections, renamed to Net.HTTPSocketType.
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of TCP socket returned.
Discontinued as of 4/12/09
Please list the metric's owners. Add more owner tags as needed.
Effective bandwidth in KByte/Second of transactions logged to
Transaction_Latency histogram. Note that only samples durations greater
than zero ms, and less than 1 hour are tallied into this ratio.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
Time from the when the network transaction is requested, until the first
byte of the header is received.
Replaced by Net.Transaction_Connected_New_b.
Please list the metric's owners. Add more owner tags as needed.
When a new connection is established, the time from the when the network
transaction is requested, until the first byte of the header is received.
Only items under 10 minutes are logged.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
When a new connection is established, the time from the when the network
transaction is requested, until the first byte of the header is received.
Replaced by Net.Transaction_Connected.
Please list the metric's owners. Add more owner tags as needed.
Time from the when the network transaction is requested, until the first
byte of the header is received. Only items under 10 minutes are logged.
Replaced by Net.Transaction_Latency_b.
Please list the metric's owners. Add more owner tags as needed.
Time from first byte sent until last byte received by the new network stack.
Only items under 1 hour are logged.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
Time from first byte sent until last byte received by the new network stack.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
Time from when a network transaction is requested until last byte received
by the new network stack.
Deprecated as of 11/2014.
Please list the metric's owners. Add more owner tags as needed.
When an existing TCP/IP connection is NOT reused, the time from when a
network transaction is requested until last byte received by the new network
stack.
Replaced by Net.Transaction_Latency_Total_New_Connection.
Please list the metric's owners. Add more owner tags as needed.
When an existing TCP/IP connection is NOT reused, the time from when a
network transaction is requested until last byte received by the new network
stack. Only items under 10 minutes are logged.
Replaced by Net.Transaction_Latency_Total.
Please list the metric's owners. Add more owner tags as needed.
Time from when a network transaction is requested until last byte received
by the new network stack. Only items under 10 minutes are logged.
Replaced by Net.Transaction_Latency.
Please list the metric's owners. Add more owner tags as needed.
Time from first byte sent until last byte received by the new network stack.
Only items under 10 minutes are logged.
Deprecated a long time ago.
Please list the metric's owners. Add more owner tags as needed.
Time from first byte sent until last byte received with old WinHTTP network
stack. Only items under 1 hour are logged.
Please list the metric's owners. Add more owner tags as needed.
The time an already used TCP socket sat idle before being used (either for
direct or non-socks use).
Please list the metric's owners. Add more owner tags as needed.
The time an unused TCP socket sat idle before being used (either for direct
or non-socks use).
Please list the metric's owners. Add more owner tags as needed.
Time from initial ClientSocketPool::RequestSocket() call until successfully
acquiring a connected socket (either for direct or non-socks use).
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of sockets returned by the TCP pool (either for
direct or non-socks use).
Please list the metric's owners. Add more owner tags as needed.
Posix error code from call to bind() UDP socket.
Please list the metric's owners. Add more owner tags as needed.
Windows error code from call to bind() UDP socket.
Please list the metric's owners. Add more owner tags as needed.
Chromium error code from call to RandomBind() UDP socket.
Please list the metric's owners. Add more owner tags as needed.
The time spent in closesocket call in UDPSocketWin::Close.
Deprecated 6/23/2014. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
True if a URLRequest's referrer is empty or valid when set.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Count the number of WebSockets that accepted permessage-deflate extension
for each context take over mode. Used by the new Chromium-based WebSocket
implementation.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
The time from a WebSocket is successfully opened until it's closed. Used to
study how WebSockets are used.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Positive net error codes that WebSockets end with, including OK and ABORTED.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Results of WebSocket handshakes. Use this histogram as a baseline for
investigating feature usage counters.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
All HTTP status codes seen during WebSocket handshakes.
mvanouwerkerk@chromium.org
The number of Wi-fi adapters on the computer. Because the histogram is
logged each time Chrome performs a Wi-fi scan, it's better to see results in
the "user count" view.
mvanouwerkerk@chromium.org
The time that a request to Location Based Services takes.
mvanouwerkerk@chromium.org
The time that a Wi-fi scan takes.
Please list the metric's owners. Add more owner tags as needed.
Duration of time that a failing WPAD QuickCheck takes. WPAD QuickCheck does
a name lookup for "wpad" and times out quickly to fail fast when
there's no WPAD server on the network.
Please list the metric's owners. Add more owner tags as needed.
Duration of time that a successful WPAD QuickCheck takes. WPAD QuickCheck
does a name lookup for "wpad" and times out quickly to fail fast
when there's no WPAD server on the network.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The network error, if any, of the first pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The HTTP response code, if any, of the first pipeline connectivity response.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The result of the first pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The network error, if any, of the second pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The HTTP response code, if any, of the second pipeline connectivity
response.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The result of the second pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The network error, if any, of the third pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The HTTP response code, if any, of the third pipeline connectivity response.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The result of the third pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The network error, if any, of the fourth pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The HTTP response code, if any, of the fourth pipeline connectivity
response.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The result of the fourth pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The network error, if any, of the fifth pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The HTTP response code, if any, of the fifth pipeline connectivity response.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The result of the fifth pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The network error, if any, of the stats pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The HTTP response code, if any, of the stats pipeline connectivity response.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The result of the stats pipeline connectivity request.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
True if all requests received by the pipelining test server were HTTP/1.1.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
True if the non-pipelined canary request sent immediately before the
pipelining test requests succeeded. Note that if this fails, the rest of the
NetConnectivity.Pipeline.* stats are not collected.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
The maximum depth of pipelined requests received by the test server.
Deprecated 05/2014, related field trial already long expired.
Please list the metric's owners. Add more owner tags as needed.
True if the entire pipeline connectivity trial passed.
Deprecated 6/25/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP at port 6121 as
rapidly as possible, just after successfully sending an UMA upload. Each
packet was numbered, as was its ACK sent back by Google. If no packets (of
the 21) were ever ACKed, then the port is assumed to be blocked, and no data
is recorded in this histogram. If the port is not blocked, then this
histogram shows the number of echo responses received from the first
Deprecated 6/25/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP at port 6121 as
rapidly as possible, just after successfully sending an UMA upload. Each
packet was numbered, as was its ACK sent back by Google. This histogram
records, for each packet number, how often we received an ACK for that
packet.
Deprecated 6/25/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP at port 6121 as
rapidly as possible, just after successfully sending an UMA upload. If no
packets (of the 21) were ever ACKed, then the port is assumed to be blocked.
The histogram shows if we ever got an ACK for a packet in our series of 21.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 100 bytes of TCP data unsuccessfully.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 1K bytes of TCP data successfully.
Please list the metric's owners. Add more owner tags as needed.
Status for TCP protocol for echoing
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Status for echoing 100 bytes of TCP data.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Status for echoing 1K bytes of TCP data.
Please list the metric's owners. Add more owner tags as needed.
The RTT for TCP protocol for echoing
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 100 bytes of TCP data successfully.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 1K bytes of TCP data successfully.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 100 bytes of UDP data unsuccessfully.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 1K bytes of UDP data successfully.
Deprecated 6/25/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Chrome sends 4 UDP packets in a row to test to see if there is a
probabalistic dependency in packet loss for consecutive packets. We record
a bit vector of packets received, where the least significant bit is a 1 if
the first packet was received, etc. For example, if packets 1 and 3 are
received, but packets 2 and 4 are lost, then we'd record a sample of binary
0101B, or 5.
Deprecated 6/25/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Chrome sends 6 UDP packets in a row to test to see if there is a
probabalistic dependency in packet loss for consecutive packets. We record
a bit vector of packets received, where the least significant bit is a 1 if
the first packet was received, etc. For example, if all packets other than
packet 2 and 4 are responded to, then we'd have a sample (in binary) of
110101B, or 53.
Please list the metric's owners. Add more owner tags as needed.
Status for UDP protocol for echoing
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Status for echoing 100 bytes of UDP data.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Status for echoing 1K bytes of UDP data.
Please list the metric's owners. Add more owner tags as needed.
The RTT for UDP protocol for echoing
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 100 bytes of UDP data successfully.
Deprecated 4/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
The RTT for echoing 1k bytes of UDP data successfully.
Please list the metric's owners. Add more owner tags as needed.
This histogram records how many packets (out of 6 attempted) were sent via
UDP as rapidly as possible, just after successfully sending an UMA upload.
Please list the metric's owners. Add more owner tags as needed.
Chrome sends 6 UDP packets in a row to test to see if there is a
probabalistic dependency in packet loss for consecutive packets. We record
a bit vector of packets received, where the least significant bit is a 1 if
the first packet was received, etc. For example, if all packets other than
packet 2 and 4 are responded to, then we'd have a sample (in binary) of
110101B, or 53.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP as rapidly as
possible, just after successfully sending an UMA upload. Each packet was
numbered, as was its ACK sent back by Google. If no packets (of the 21) were
ever ACKed, then the port is assumed to be blocked, and no data is recorded
in this histogram. If the port is not blocked, then this histogram shows the
number of echo responses received from the first
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP as rapidly as
possible, just after successfully sending an UMA upload. Each packet was
numbered, as was its ACK sent back by Google. This histogram records, for
each packet number, how often we received an ACK for that packet.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP as rapidly as
possible, just after successfully sending an UMA upload. If no packets (of
the 21) were ever ACKed, then the port is assumed to be blocked. The
histogram shows if we ever got an ACK for a packet in our series of 21.
Please list the metric's owners. Add more owner tags as needed.
This histogram records how many packets (out of 21 attempted) were sent via
UDP as rapidly as possible, just after successfully sending an UMA upload.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP on port 443 or
6121.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 9/2012. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
This histogram records how many packets (out of 6 attempted) were sent via
UDP as rapidly as possible, just after successfully sending an UMA upload.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, a few packets were sent from Google to clients via UDP
on port 443 or 80 to perform net connectivity test.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, a few packets were sent from Google to clients via UDP
on port 443 or 80 to perform net connectivity test.
Please list the metric's owners. Add more owner tags as needed.
Next NetConnectivity5 experiment weren't started because there is an
outstading pending write.
benchan@chromium.org
The time the Gobi modem takes to complete activation.
benchan@chromium.org
The time the Gobi modem takes to connect to the cellular network.
benchan@chromium.org
The time the Gobi modem takes to disconnect from the cellular network.
benchan@chromium.org
Number of attempts taken to install Gobi firmware.
benchan@chromium.org
The time it takes to install Gobi firmware.
benchan@chromium.org
The time the Gobi modem takes to register on the cellular network.
benchan@chromium.org
Errors experienced during Gobi device powerup.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network metric sampling the time spent using Cellular to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a 3G/Cellular
network and configure Layer 3 state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that a
3G/Cellular network is online after configuring Layer 3 state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that a
3G/Cellular network is in a captive portal after configuring Layer 3 state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS cellular usage API request status codes.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network metric sampling the time spent using Ethernet to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a wired
Ethernet network and configure Layer 3 state (typically acquire a DHCP
lease).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is online after configuring Layer 3 state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is in a captive portal after configuring Layer 3 state.
pneubeck@chromium.org
Chrome OS metric counting the number of network configurations that
contained a NSS nickname identifying a CA certificate, which triggered the
migration to PEM encoding. This metric doesn't consider whether the
migration was successful but once a migration was successful the nickname is
removed.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS connection manager service errors seen.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the number of cellular network
flakes. A network flake occurs when the signal strength goes below detection
level for a short duration.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the total amount of time spent
from the start of the first auto-connect request until when the cellular
modem successfully connects to the network.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the number of auto-connect
tries that were attempted before the cellular modem successfully connected
to the network.
zqiu@chromium.org
Chrome OS network metric that tracks the presence of a Cellular device in
the system. A sample is emitted once every 3 minutes.
Deprecated 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected.
quiche@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
quiche@chromium.org
Chrome OS network usage metric that tracks whether the cellular network was
disconnected due to an error or was explicitly disconnected by the user.
quiche@chromium.org
Chrome OS cellular network metric that tracks the number of drops based on
the network technology.
quiche@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
cellular network at the time it expired without the DHCP client being able
to renew it.
zqiu@chromium.org
Chrome OS network metric that tracks the presence of complete IPv6
configuration at the time when cellular connection is established.
zqiu@chromium.org
Chrome OS network metric that tracks the types of IP configuration used for
establishing cellular connections.
quiche@chromium.org
Chrome OS cellular network metric that tracks the number of out-of-credits
detected based on the cause that triggered the out-of-credits.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the number of portal detection
attempts per pass for a cellular network. This includes failure, timeout and
successful attempts.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the total number of portal
detection attempts performed for a cellular network between the Connected
and Online state. This includes failure, timeout and successful attempts.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the result of portal detections
for a cellular network.
quiche@chromium.org
Chrome OS network metric sampling the signal strength (0-100) of the
cellular modem before it dropped from the network.
quiche@chromium.org
Chrome OS network metric sampling the time spent using cellular to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
quiche@chromium.org
Chrome OS network performance metric sampling the time to join a cellular
network and configure Layer 3 state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to connect a cellular
modem.
quiche@chromium.org
Chrome OS network performance metric sampling the time to disable a cellular
modem.
quiche@chromium.org
Chrome OS network performance metric sampling the time to enable a cellular
modem.
quiche@chromium.org
Chrome OS network performance metric sampling the time to initialize a
cellular modem.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that a
cellular network is online after configuring Layer 3 state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that a
cellular network is in a captive portal after configuring Layer 3 state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to scan a cellular
network and register a modem.
quiche@chromium.org
Chrome OS cellular network metric that tracks the number of corrupted
profiles encountered by Shill.
samueltan@chromium.org
Chrome OS network diagnostic metric sampling the number of dark resume
actions that successfully complete or fail when shill suspends.
samueltan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes dark resume actions to complete when shill suspends.
samueltan@chromium.org
Deprecated 01/2015. Migrated to Network.Shill.DarkResumeActionsTimeTaken.
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes dark resume actions to complete when shill suspends.
samueltan@chromium.org
Chrome OS network metric sampling the number of times a dark resume scan is
retried in a single dark resume.
samueltan@chromium.org
Chrome OS network metric that tracks whether dark resume scan retries led to
the system suspending from dark resume in a connected state. This metric is
only recorded in dark resumes when at least one dark resume scan retry was
launched.
zqiu@chromium.org
Chrome OS network performance metric that tracks the connection status of
the device. A sample is emitted once every 3 minutes.
zqiu@chromium.org
Chrome OS network metric that tracks the network device removed events for
each device type.
pstew@chromium.org
Chrome OS network diagnostic metric sampling the current state of the DHCP
client. A sample is emitted each time the DHCP client state changes.
zqiu@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill for each network technology. This indicates that Shill
is using minimal DHCP options due to suspected MTU issues on the return path
from the DHCP server back to the client.
zqiu@chromium.org
Chrome OS network metric that tracks the presence of an Ethernet device in
the system. A sample is emitted once every 3 minutes.
Deprecated 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected.
quiche@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
quiche@chromium.org
Chrome OS network usage metric that tracks whether the Ethernet network was
disconnected due to an error or was explicitly disconnected by the user.
quiche@chromium.org
Chrome OS network performance metric that tracks the length of a lease for
an Ethernet network at the time it expired without the DHCP client being
able to renew it.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of LinkMonitor
broadcast errors that were accrued on an Ethernet network at the time that
the link was declaired to be failed.
quiche@chromium.org
Chrome OS metric that signals the type of failure the LinkMonitor
encountered which caused it to stop monitoring an Ethernet network.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of milliseconds
between an ARP request and a received reply on an Ethernet network.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of seconds from
the start of the LinkMonitor until failure on an Ethernet network.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of LinkMonitor
unicast errors that were accrued on an Ethernet network at the time that the
link was declaired to be failed.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the number of portal detection
attempts per pass for an Ethernet network. This includes failure, timeout
and successful attempts.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the total number of portal
detection attempts performed for an Ethernet network between the Connected
and Online state. This includes failure, timeout and successful attempts.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the result of portal detections
for an Ethernet network.
quiche@chromium.org
Chrome OS network metric sampling the time spent using Ethernet to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
quiche@chromium.org
Chrome OS network performance metric sampling the time to join a wired
Ethernet network and configure Layer 3 state (typically acquire a DHCP
lease).
quiche@chromium.org
Chrome OS network performance metric sampling the time to initialize an
Ethernet device.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is online after configuring Layer 3 state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is in a captive portal after configuring Layer 3 state.
quiche@chromium.org
Chrome OS connection manager service errors seen.
zqiu@chromium.org
Chrome OS network metric sampling the number of services that are connected
to the currently connected network.
samueltan@chromium.org
Chrome OS network diagnostic metric sampling the number of suspend actions
that successfully complete or fail when shill suspends.
samueltan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes suspend actions to complete when shill suspends.
samueltan@chromium.org
Deprecated 01/2015. Migrated to Network.Shill.SuspendActionsTimeTaken.
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes suspend actions to complete when shill suspends.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the number of termination
actions that successfully complete or fail when shill terminates. Previously
deprecated in 10/2012 and brought back in 10/2014.
quiche@chromium.org
Deprecated 10/2014. Migrated to Network.Shill.SuspendActionResult.
Chrome OS network diagnostic metric sampling the number of termination
actions that successfully complete or fail when shill suspends.
quiche@chromium.org
Deprecated 10/2014. Migrated to Network.Shill.TerminationActionResult.
Chrome OS network diagnostic metric sampling the number of termination
actions that successfully complete or fail when shill terminates.
samueltan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill terminates.
samueltan@chromium.org
Deprecated 01/2015. Migrated to Network.Shill.TerminationActionsTimeTaken.
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill terminates.
quiche@chromium.org
Deprecated 10/2014. Migrated to Network.Shill.SuspendActionTime.
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill suspends.
quiche@chromium.org
Deprecated 10/2014. Migrated to Network.Shill.TerminationActionTime.
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill terminates.
quiche@chromium.org
Chrome OS network stability metric sampling the time in seconds between the
networking going online to going offline. Offline events due to device
shutdown or suspend are ignored (along with the online time before that
offline event).
zqiu@chromium.org
Chrome OS network metric that tracks the number of user-initiated events.
quiche@chromium.org
Chrome OS network usage metric sampled on each successful VPN connection
that tracks the VPN connection type.
quiche@chromium.org
Chrome OS network usage metric sampled on each successful VPN connection
that tracks the remote authentication method.
quiche@chromium.org
Chrome OS network metric sampling the time spent using VPN to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular). A sample is emitted
every time the system transitions from primary connectivity through a VPN to
some other type of connectivity. The value of the sample is the time delta
in seconds from the instant the system transitioned to VPN connectivity.
quiche@chromium.org
Chrome OS network performance metric sampling the time to configure Layer 3
state on a VPN network (typically acquire a DHCP lease).
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that a
WiMax network is online after configuring Layer 3 state.
quiche@chromium.org
Chrome OS network usage metric sampled on each successful VPN connection
that tracks the user authentication method.
quiche@chromium.org
Chrome OS network usage metric. Reason code reported when the AP
disconnects a WiFi connection.
quiche@chromium.org
Chrome OS network usage metric. Broad category of reason AP disconnected a
WiFi connection.
quiche@chromium.org
Chrome OS network usage metric. The AP mode setting for each successful
WiFi connection.
zqiu@chromium.org
Chrome OS network metric sampling the number of wifi services available for
auto-connect when auto-connect is initiated for wifi device.
zqiu@chromium.org
Chrome OS network metric sampling the number of BSSes (endpoints) available
for the currently connecting wifi service.
quiche@chromium.org
Chrome OS network usage metric. The channel used for each successful WiFi
connection.
quiche@chromium.org
Chrome OS network usage metric. Reason code reported when the client
disconnects a WiFi connection.
quiche@chromium.org
Chrome OS network usage metric. Broad category of reason client
disconnected a WiFi connection.
samueltan@chromium.org
Chrome OS network metric that tracks whether any unmatched scan results are
received during dark resume cycles. An unmatched scan result is a set of
scan results received by shill in response to a scan request that was not
sent directly by shill in the same dark resume cycle.
samueltan@chromium.org
Chrome OS network metric that tracks the wake reason for dark resume.
zqiu@chromium.org
Chrome OS network metric that tracks the presence of a WiFi device in the
system. A sample is emitted once every 3 minutes.
Deprecated 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected.
quiche@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
quiche@chromium.org
Chrome OS network usage metric that tracks whether an 802.11 wireless
network was disconnected due to an error or was explicitly disconnected by
the user.
quiche@chromium.org
Chrome OS network usage metric sampled on each successful 802.1x wireless
connection that tracks the configured inner authentication method.
quiche@chromium.org
Chrome OS network usage metric sampled on each successful 802.1x wireless
connection that tracks the configured outer authentication method.
quiche@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
WiFi network at the time it expired without the DHCP client being able to
renew it.
zqiu@chromium.org
Chrome OS network performance metric that tracks the result of the fallback
DNS test. The fallback DNS test is performed when portal detection failed
due to DNS failure.
quiche@chromium.org
Chrome OS metric sampling the number of different frequencies (i.e.
channels) on which a device has connected to a WiFi network. This value is
sampled every time a WiFi connection is established
(WPASupplicant::kInterfaceStateCompleted). Note that the word
"Ever" in the metric name is misleading. Chrome OS actually ages
out historical information, currently after 3 weeks.
zqiu@chromium.org
Chrome OS network metric that tracks the presence of complete IPv6
configuration at the time when WiFi connection is established.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of LinkMonitor
broadcast errors that were accrued on an 802.11 wireiless network at the
time that the link was declaired to be failed.
quiche@chromium.org
Chrome OS metric that signals the type of failure the LinkMonitor
encountered which caused it to stop monitoring an 802.11 wireless network.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of milliseconds
between an ARP request and a received reply on an 802.11 wireless network.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of seconds from
the start of the LinkMonitor until failure on an 802.11 wireless network.
quiche@chromium.org
Chrome OS network performance metric that tracks the number of LinkMonitor
unicast errors that were accrued on an 802.11 wireless network at the time
that the link was declaired to be failed.
zqiu@chromium.org
Chrome OS network metric that tracks the types of IP configuration used for
establishing WiFi connections.
zqiu@chromium.org
Chrome OS network performance metric that tracks the network problems
encountered by TrafficMonitor after WiFi connection is established.
quiche@chromium.org
Chrome OS network usage metric. The channel type used for each successful
WiFi connection.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the number of portal detection
attempts per pass for an 802.11 wireless network. This includes failure,
timeout and successful attempts.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the total number of portal
detection attempts performed for an 802.11 wireless network between the
Connected and Online state. This includes failure, timeout and successful
attempts.
quiche@chromium.org
Chrome OS network diagnostic metric sampling the result of portal detections
for an 802.11 wireless network.
pstew@chromium.org
Chrome OS network diagnostic metric sampling the number of 802.11 wireless
networks known by the connection manager at the time a configuration profile
has been loaded. A configuration profile is loaded at each system startup,
and when a user logs in.
quiche@chromium.org
Chrome OS network metric sampling the number of 802.11 wireless networks
configured from the system configuration profile. This metric is sampled
each time a user configuration profile is loaded, such as when a user logs
in.
It might be surprising to have a system configuration profile metric sampled
when a user configuration profile is loaded. But this ensures that we have
equal numbers of samples for system and user configuration profiles.
quiche@chromium.org
Chrome OS network metric sampling the number of 802.11 wireless networks
configured from a user configuration profile. This metric is sampled each
time a user configuration profile is loaded, such as when a user logs in.
quiche@chromium.org
Chrome OS network usage metric describing, for a WiFi scan attempt, what
scan method is used and whether it ends in a connection.
quiche@chromium.org
Chrome OS network usage metric describing, for a WiFi scan attempt, how many
milliseconds were spent waiting to talk to the kernel/drivers.
quiche@chromium.org
Chrome OS network usage metric. The security setting for each successful
WiFi connection.
silberst@chromium.org
Chrome OS network metric indicating the negative of the dBm received signal
strength recorded at the time of a WiFi disconnect.
quiche@chromium.org
Chrome OS network metric indicating the negative of the dBm received signal
strength recorded at the time a successful WiFi connection started.
quiche@chromium.org
Chrome OS network metric indicating the maximal length of any stopped
mac80211 transmit queue. The metric is reported when a queue-status check
determines that at least one transmit queue is stopped, and has more than a
threshold number of frames queued.
quiche@chromium.org
Chrome OS network metric indicating the reason that mac80211 transmit queues
were stopped. The metric is reported when a queue-status check determines
that at least one queue is stopped, and has more than a threshold number of
frames queued.
One measurement is reported per stop reason, per queue-status check. Reasons
that apply to multiple queues are reported only once per queue-status check.
Reasons that only apply to queues that have a below-threshold number of
frames are skipped.
Note that, because we may report multiple stop reasons for a single
queue-status check, this histogram is not suitable for determining the
number of times a queue-status check found that the queues were stopped. To
determine that number, use the count of
Network.Shill.WiFi.StoppedTxQueueLength reports.
quiche@chromium.org
Chrome OS network metric sampling the time spent using WiFi to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
quiche@chromium.org
Chrome OS network performance metric sampling the time from the resume event
to the time when an 802.11 wireless network has configured its Layer 3
state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease).
quiche@chromium.org
Chrome OS network performance metric sampling the time to connect to a WiFi
Basic Service Set (which consists of the access point and associated
stations on a particular WiFi channel for a specific network).
quiche@chromium.org
Chrome OS network performance metric sampling the time to initialize an
802.11 wireless device.
quiche@chromium.org
Chrome OS network performance metric sampling the time to join (associate
plus authenticate) an 802.11 wireless network.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that an
802.11 wireless network is online after configuring Layer 3 state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that an
802.11 wireless network is in a captive portal after configuring Layer 3
state.
quiche@chromium.org
Chrome OS network performance metric sampling the time to scan WiFi until a
connection is found.
quiche@chromium.org
Chrome OS network performance metric sampling the time between the beginning
of a WiFi scan (if the scan includes both a progressive scan and a full
scan, the TimeToScanAndConnect starts with the first scan of the series) and
the completion of a successful connection.
zqiu@chromium.org
Chrome OS network performance metric that tracks the transmit bitrate in
Mbps for the wifi device when it is connected to a network. The bitrate is
reported once every minute after the wifi connection is established.
zqiu@chromium.org
Chrome OS network metric sampling the signal strength (0-100) of the wifi
network when it becomes unreliable (experiencing multiple link failures in a
short period of time).
zqiu@chromium.org
Chrome OS network performance metric that tracks the reasons of failed
user-initiated WiFi connection attempts. The result of the user-initiated
WiFi connection attempts are being tracked by
Network.Shill.WiFi.UserInitiatedConnectionResult.
zqiu@chromium.org
Chrome OS network performance metric that tracks the result of
user-initiated WiFi connection attempts.
samueltan@chromium.org
Chrome OS network diagnostic metric sampling the number of times NIC wake on
WiFi settings verification succeeds or fails in shill. This metric is
recorded every time wake on WiFi settings are requested and verified after
the NIC is programmed with wake on WiFi settings.
samueltan@chromium.org
Chrome OS network usage metric that tracks the wake on WiFi features that
are enabled in shill. Recorded once every 10 minutes.
samueltan@chromium.org
Chrome OS network metric that tracks whether wake on WiFi was disabled
during a period of system suspension because of too many dark resume wakes.
This metric is only recorded for system suspends where wake on WiFi
functionality has been programmed into the NIC.
samueltan@chromium.org
Chrome OS network metric that tracks whether a wake reason was received
during dark resume before executing WakeOnWiFi::OnDarkResume.
samueltan@chromium.org
Chrome OS network usage metric that tracks the WiFi connection status after
waking from suspend, both when wake on WiFi is enabled and disabled.
Recorded 1 second after waking from suspend.
zqiu@chromium.org
Chrome OS network metric that tracks the presence of a WiMax device in the
system. A sample is emitted once every 3 minutes.
Deprecated 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected.
quiche@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
quiche@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
WiMax network at the time it expired without the DHCP client being able to
renew it.
quiche@chromium.org
Chrome OS network performance metric sampling the time to configure Layer 3
state on a WiMax network (typically acquire a DHCP lease).
quiche@chromium.org
Chrome OS network performance metric sampling the time to initialize a WiMax
device.
quiche@chromium.org
Chrome OS network performance metric sampling the time to determine that a
WiMax network is online after configuring Layer 3 state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a 3G/Cellular
network and configure Layer 3 state. Note this metric is deprecated; see
Network.Cellular.TimeToConfig.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a wired
Ethernet network and configure Layer 3 state (typically acquire a DHCP
lease). Note this metric is deprecated; see Network.Ethernet.TimeToConfig.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease). Note
this metric is deprecated; see Network.Wifi.TimeToConfig.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network stability metric sampling the time in seconds between the
networking going online to going offline. Offline events due to device
shutdown or suspend are ignored (along with the online time before that
offline event).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join (associate
plus authenticate) an 802.11 wireless network. Note this metric is
deprecated; see Network.Wifi.TimeToJoin.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease).
Please list the metric's owners. Add more owner tags as needed.
Network metric reporting the download speed test results run at setup time.
Recorded at least once per day.
cast-analytics@google.com
Chrome OS network usage metric. The channel used for each successful WiFi
connection.
cast-analytics@google.com
Chrome OS network usage metric. The channel type used for each successful
WiFi connection.
cast-analytics@google.com
Network metric reporting the average round trip time to the WiFi gateway.
Recorded at least once per day.
cast-analytics@google.com
Chrome OS network usage metric. The security setting for each successful
WiFi connection.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network metric sampling the time spent using WiFi to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time from the resume event
to the time when an 802.11 wireless network has configured its Layer 3
state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join (associate
plus authenticate) an 802.11 wireless network.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
802.11 wireless network is online after configuring Layer 3 state.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
802.11 wireless network is in a captive portal after configuring Layer 3
state.
stevenjb@chromium.org
Number of shared remembered (preferred) networks on Chrome OS. Updated any
time the network list changes.
stevenjb@chromium.org
Number of private remembered (preferred) networks on Chrome OS. Updated any
time the network list changes.
stevenjb@chromium.org
Number of visible (in-range) networks on Chrome OS. Updated any time the
network list changes.
newt@chromium.org
Actions taken by users from the new tab page on Android. These actions may
navigate away from the NTP (e.g. searching in the omnibox or opening a
bookmark), but can also happen without navigating away from the NTP (e.g.
opening a bookmark in a new tab).
Please list the metric's owners. Add more owner tags as needed.
Histogram for the source of app page drags. For any succesful drop onto an
apps pane of the NTP, this logs where the drag originated.
Deprecated on M33 with the change to native NTP.
Please list the metric's owners. Add more owner tags as needed.
Actions taken by users on partner bookmarks (editing / renaming) on the NTP
on Android.
Please list the metric's owners. Add more owner tags as needed.
The default pane when the NTP is first opened.
Please list the metric's owners. Add more owner tags as needed.
Histogram of the time, in milliseconds, users have the cursor over a most
visited thumbnail before clicking.
Please list the metric's owners. Add more owner tags as needed.
Histogram of the time, in milliseconds, users have the cursor over a most
visited thumbnail before moving it away from the thumbnail without clicking.
newt@chromium.org
The number of most visited tiles on the new tab page that are displayed
using a fallback color (as opposed to having an icon, or simply being gray).
newt@chromium.org
The number of most visited tiles on the new tab page that are displayed as
gray (as opposed to having an icon, or a fallback color).
newt@chromium.org
The number of most visited tiles on the new tab page that are displayed with
the site's icon (as opposed using a fallback color or just gray).
fserb@chromium.org
Histogram of the time, in milliseconds, it took for the NTP to load all of
its tiles since navigation start.
Deprecated on M33 with the change to native NTP.
Please list the metric's owners. Add more owner tags as needed.
Android: Tallies counts for how the user interacted with the NTP promo page.
beaudoin@chromium.org
justincohen@chromium.org
newt@chromium.org
Histogram for user clicks of the most visited thumbnails. The value is equal
to the index of the thumbnail.
beaudoin@chromium.org
justincohen@chromium.org
newt@chromium.org
Action taken by the user on the Most Visited NTP pane. If the user switches
panes during this use of the NTP, this action is sometimes not recorded. Ask
mpearson@ for details.
beaudoin@chromium.org
justincohen@chromium.org
newt@chromium.org
Records anomalous events for the Most Visited Tile Placement experiment,
where it is unable to operate as expected. These are recorded during New Tab
Page load time, once for every NTP.
Please list the metric's owners. Add more owner tags as needed.
The number of screenshots that were cached for the non-visible but ranked
suggestions on the Suggested NTP pane.
Please list the metric's owners. Add more owner tags as needed.
Given that the user has typed a URL, and given that that specific URL was
ranked but not visible on the Suggested pane of the NTP, this is the rank
that the Suggested pane had for that URL.
beaudoin@chromium.org
The number of tiles for which we relied on external tiles as a fallback
because a local screenshot was not available to be used as a thumbnail.
External tiles are those for which the visuals are handled by the page
itself, not by the iframe. Recorded before reloading the suggestions,
navigating to a URL, switching tabs, changing the active window, or closing
the tab/shutting down Chrome.
beaudoin@chromium.org
The number of external tiles that are displayed on the NTP. External tiles
are those for which the visuals are handled by the page itself, not by the
iframe. Recorded before reloading the suggestions, navigating to a URL,
switching tabs, changing the active window or closing the tab/shutting down
Chrome.
beaudoin@chromium.org
The number of tiles for which we displayed a gray tile with the domain name
as a fallback because a local screenshot was not available to be used as a
thumbnail. Recorded before reloading the suggestions, navigating to a URL,
switching tabs, changing the active window or closing the tab/shutting down
Chrome.
beaudoin@chromium.org
The number of tiles for which no thumbnail was specified, but a domain was
so we displayed a gray tile with the domain name in it. Recorded before
reloading the suggestions, navigating to a URL, switching tabs, changing the
active window or closing the tab/shutting down Chrome.
beaudoin@chromium.org
The total number of times the user hovered the mouse over Most Visited tile
or title elements before changing focus away from the NTP, be it by
navigating to a URL, switching tabs, changing the active window or closing
the tab/shutting down Chrome.
Deprecated 01/2014. Replaced by NewTabPage.NumberOfThumbnailTiles.
Please list the metric's owners. Add more owner tags as needed.
The number of tiles for which we attempted to use a local screenshot as a
thumbnail. Recorded before reloading the suggestions, navigating to a URL,
switching tabs, changing the active window or closing the tab/shutting down
Chrome.
beaudoin@chromium.org
The number of thumbnails for which a local screenshot was not available so
we were not able to display them on the Most Visited section of the NTP.
Recorded before reloading the suggestions, navigating to a URL, switching
tabs, changing the active window or closing the tab/shutting down Chrome.
beaudoin@chromium.org
The number of tiles for which we attempted to use a local screenshot as a
thumbnail. Recorded before reloading the suggestions, navigating to a URL,
switching tabs, changing the active window or closing the tab/shutting down
Chrome.
beaudoin@chromium.org
The number of tiles that are displayed on the NTP, no matter if they are
thumbnails, gray tiles, or external tiles. Recorded before reloading the
suggestions, navigating to a URL, switching tabs, changing the active window
or closing the tab/shutting down Chrome.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 05/2015. Feature was removed.
Histogram for usage of the menu on the NTP that allows the user to access
tabs from other devices.
Please list the metric's owners. Add more owner tags as needed.
The pane that had been previously selected when the user switches panes in
the NTP.
Please list the metric's owners. Add more owner tags as needed.
Histogram for NTP bubble promo activity.
Please list the metric's owners. Add more owner tags as needed.
Histogram for NTP notification promo activity.
Please list the metric's owners. Add more owner tags as needed.
TBD.
Please list the metric's owners. Add more owner tags as needed.
The pane selected when the user switches panes in the NTP.
Please list the metric's owners. Add more owner tags as needed.
Histogram for user clicks of the Recently Closed items. The value is the
recency of the entry being restored (0 is most recent).
Please list the metric's owners. Add more owner tags as needed.
Histogram to track how many times a user switched pages in a single NTP
session.
Please list the metric's owners. Add more owner tags as needed.
Histogram for user clicks of the suggested site thumbnails. The value is
equal to the index of the thumbnail.
Please list the metric's owners. Add more owner tags as needed.
Action taken by the user on the Suggested Sites NTP pane.
Please list the metric's owners. Add more owner tags as needed.
Time to load the Suggested Sites NTP pane, in milliseconds.
Please list the metric's owners. Add more owner tags as needed.
Time spent on the Suggested Sites NTP pane, in seconds.
beaudoin@chromium.org
Histogram for impressions on the various most visited tiles. The value is
equal to the index of the thumbnail.
beaudoin@chromium.org
Indicate, for each impression of the New Tab Page, whether the suggestions
were obtained from the client or server. Recorded before changing focus away
from the NTP, be it by navigating to a URL, switching tabs, changing the
active window or closing the tab/shutting down Chrome.
Deprecated 01/2014. Replaced by NewTabPage.NumberOfThumbnailAttempts and
NewTabPage.NumberOfThumbnailErrors.
Please list the metric's owners. Add more owner tags as needed.
The percentage of errors per attempts to load image thumbnails on the New
Tab Page. When an error occurs, a grey tile is shown instead of a thumbnail
image. We measure the rate instead of the number of errors because multiple
attempts are made to load images at different times during the NTP's
lifetime. Each NTP session's error rate is logged after the user navigates
to a new URL from that NTP.
Deprecated 01/2014. Replaced by NewTabPage.NumberOfGrayTileFallbacks and
NewTabPage.NumberOfExternalFallbacks.
Please list the metric's owners. Add more owner tags as needed.
The percentage of times most visited tiles use the fallback thumbnail. Only
requests that actually specify a fallback thumbnail are considered here. We
measure the rate instead of the number of errors because multiple attempts
are made to load thumbnails at different times during the NTP's lifetime.
Each NTP session's error rate is logged after the user navigates to a new
URL from that NTP.
beaudoin@chromium.org
Records the status of the New Tab page URL when an NTP is opened.
Please list the metric's owners. Add more owner tags as needed.
The number of screenshots that were cached for the visible suggestions on
the Suggested NTP pane.
Please list the metric's owners. Add more owner tags as needed.
Given that the user has typed a URL, and given that that specific URL was
visible on the Suggested pane of the NTP, this is the rank that the
Suggested pane had for that URL.
dewittj@chromium.org
The actions taken on notifications, recorded every time they happen. This
histogram will record every single event that happens separately.
peter@chromium.org
The size, in kilobytes, of the author-provided data associated with a Web
Notification. Recorded when a persistent Web Notification is being shown by
the developer.
peter@chromium.org
Records the result status codes of deleting notification data from the Web
Notification database.
peter@chromium.org
Records the result status codes of deleting all notification data associated
with a Service Worker registration ID.
peter@chromium.org
Records the result status codes of destroying the Web Notification database
altogether.
peter@chromium.org
Records the result status codes of opening the Web Notification database
after it has been destroyed in response to data corruption.
peter@chromium.org
Records the result status codes of opening the Web Notification database.
peter@chromium.org
Records the result status codes of reading data of all notifications
associated with a Service Worker from the Web Notification database.
peter@chromium.org
Records the result status codes of reading data of a single notification
from the Web Notification database.
peter@chromium.org
Records the result status codes of writing data for a notification to the
Web Notification database.
peter@chromium.org
Records if the requesting and embedding origins are different when
requesting permission to display Web Notifications.
dewittj@chromium.org
The actions taken on notifications, recorded once per notification, when it
is closed. This differs from the Notifications.Actions histogram in that
multiple events of the same type on a single notification will only record a
single UMA event.
tbansal@chromium.org
Rough estimate of the fastest round-trip-time, before a connectivity change
is detected.
This metric is recorded when a connectivity change is detected. This will
miss data from users whose connection type never changes and will be biased
to users whose connection type changes frequently.
tbansal@chromium.org
Rough estimate of peak throughput, before a connectivity change is detected.
This metric is recorded when a connectivity change is detected. This will
miss data from users whose connection type never changes and will be biased
to users whose connection type changes frequently.
Please list the metric's owners. Add more owner tags as needed.
TBD
Deprecated 10/2011. No longer tracked, replaced with
NewTabPage.DefaultPageType
Please list the metric's owners. Add more owner tags as needed.
The default pane when the NTP is first opened.
Deprecated 10/2011. No longer tracked, replaced with
NewTabPage.SelectedPageType
Please list the metric's owners. Add more owner tags as needed.
The pane selected when the user switches panes in the NTP.
zelidrag@chromium.org
Failure reason of final OAuth2 access token retrieval call during Chrome OS
login.
zelidrag@chromium.org
Retry reason of failed OAuth2 access token retrieval call during Chrome OS
login.
zelidrag@chromium.org
Failure reason of final ListAccounts call failure during Chrome OS login.
zelidrag@chromium.org
Retry reason of failed ListAccounts call during Chrome OS login.
zelidrag@chromium.org
Failure reason of final MergeSession call during Chrome OS login.
zelidrag@chromium.org
Retry reason of failed MergeSession call during Chrome OS login.
zelidrag@chromium.org
Failure reason of final OAuthLogin (with SID+LSID) call during Chrome OS
login.
zelidrag@chromium.org
Retry reason of failed OAuthLogin (with SID+LSID) call during Chrome OS
login.
zelidrag@chromium.org
Failure reason of final OAuthLogin (with uber token) call during Chrome OS
login.
zelidrag@chromium.org
Retry reason of failed OAuthLogin (with uber token) call during Chrome OS
login.
zelidrag@chromium.org
Outcome of Chrome OS GAIA cookie post-merge session verification process. It
measures how often /MergeSession request collided with browser session
restore process resulting in partially authenticated primary GAIA session.
zelidrag@chromium.org
Outcome of Chrome OS GAIA cookie pre-merge session verification process. It
measures how often we need to perform /MergeSession request to
re-authenticated exisitng user with GAIA.
zelidrag@chromium.org
Outcome of Chrome OS GAIA cookie session restore process.
zelidrag@chromium.org
How long it takes for the session restore to fail.
zelidrag@chromium.org
How long it takes for the session restore to finish succeessfully.
Please list the metric's owners. Add more owner tags as needed.
When a page is loaded in offline mode, the percentage of resources on that
page that were successfully loaded.
Aggressive HistoryURL provider field trial deleted in spring 2012.
Please list the metric's owners. Add more owner tags as needed.
A number that indicates what omnibox ranking behavior the user is seeing as
part of the OmniboxAggressiveHistoryURLProvider field trial
(OmniboxAggressiveHistoryURLProvider).
jdonnelly@chromium.org
For each answer received in suggest responses, the number that are
well-formed and contain all the required elements.
asvitkine@chromium.org
Records the time taken between a keystroke being typed in the omnibox and
the text being painted. If there are multiple keystrokes before a paint,
logs the time since the earliest one.
mpearson@chromium.org
The number of cut or copy commands on all selected text in the omnibox.
Gathered on desktop platforms (Win, Mac, Linux, Chrome OS).
mpearson@chromium.org
The number of times users enter keyword hint mode "Search ___
for:" and how.
mpearson@chromium.org
The length of time between when a user focused on the omnibox and first
modifies the omnibox.
mpearson@chromium.org
Replaced with Omnibox.FocusToOpenTimeAnyPopupState in April 2014.
The length of time between when a user focused on the omnibox and opened an
omnibox match (which could be what they typed or a suggestion).
mpearson@chromium.org
The length of time between when a user focused on the omnibox and opened an
omnibox match (which could be what they typed or a suggestion). This is
recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open.
Deprecated 2015-01-27
mpearson@chromium.org
Whether there was at least one legal default match without an
|inline_autocompletion|. Recorded every time
AutocompleteResult::SortAndCull() is called, which could happen multiple
times on each keystroke.
mpearson@chromium.org
The kind of input the user provided when using the omnibox to go somewhere.
The type can be misleading. For example if the user typed 'http:/', it gets
marked as a query because it cannot be opened as a URL even though the user
probably wanted and selected a URL from the list of suggestions.
mpearson@chromium.org
Whether an omnibox interaction is a paste-and-search/paste-and-go action.
(This histogram records both of these in the "True" bucket for
this histogram because both of these are referred to as paste-and-go in the
code.) These typically involve right-clicking in the omnibox and selecting
that option from the dropdown.
mpearson@chromium.org
Whether the omnibox popup (a.k.a. dropdown) is open at the time the user
used the omnibox to go somewhere. It can be closed if, for instance, the
user clicked in the omnibox and hit return to reload the same page. Also,
because paste-and-search/paste-and-go actions ignore the current content of
the omnibox dropdown (if it is open) when they happen, we pretend the
dropdown is closed when logging these.
mpearson@chromium.org
Whether the user deleted text immediately before selecting an omnibox
suggestion. This is usually the result of pressing backspace or delete.
mpearson@chromium.org
The number of times users used the omnibox to go somewhere.
mpearson@chromium.org
The number of terms in the text the user entered in the omnibox when they
used the omnibox to go somewhere. Terms are defined by splitting on
whitespace. All values larger than 6 are recorded in bucket 6.
mpearson@chromium.org
What the user was viewing when the user used the omnibox to go somewhere.
mpearson@chromium.org
The number of paste commands on the text in the omnibox. Reported every time
a paste command is done.
mpearson@chromium.org
The number of paste-and-go commands on the text in the omnibox. Reported
every time a paste-and-go command is done.
mpearson@chromium.org
The length of time taken by the named provider"s synchronous pass.
Deprecated 2012-11-14. Replaced by Omnibox.ProviderTime.
Please list the metric's owners. Add more owner tags as needed.
Time the HistoryContentProvider takes to perform a bookmark search.
mpearson@chromium.org
Time it takes for the omnibox to become responsive to user input after the
user has typed N characters. This measures the time it takes to start all
the asynchronous autocomplete providers (but not wait for them to finish).
mpearson@chromium.org
When a user switches tabs, whether the omnibox had an edit in progress.
Made obsolete around Chrome 32. Use Omnibox.SearchEngineType instead.
Please list the metric's owners. Add more owner tags as needed.
The id of search engine that was used for search in omnibox. See
src/chrome/browser/search_engines/template_url_prepopulate_data.cc for more
info.
mpearson@chromium.org
The type of search engine associated with a match opened from the omnibox.
mpearson@chromium.org
Time it takes to add all the raw history results to the list of matches.
mpearson@chromium.org
Time it takes to convert all the results to matches and add them to a map,
to keep the most relevant match for each result.
mpearson@chromium.org
The number of matches returned by SearchProvider. Emitted on every call to
SearchProvider::Start(), which effectively means every key stroke in the
omnibox.
mpearson@chromium.org
The index of the item that the user selected in the omnibox popup (a.k.a.
dropdown) list. 0 means the inline suggestion shown within the omnibox.
This is also the same suggestion shown as the top item in the dropdown. The
second item in the dropdown will be recorded as bucket 1. The selected
position is always set to 0 when the popup is closed at the time of
navigation or if the user did a paste-and-search or paste-and-go action.
mpearson@chromium.org
The provider of the suggestion the user selected when the user used the
omnibox to go somewhere.
mpearson@chromium.org
The provider and result type of the suggestion the user selected when the
user used the omnibox to go somewhere.
mpearson@chromium.org
The time elapsed between the sending of a suggest request to Google until
the time the request was returned with status==failed. Ignores requests that
were canceled before being returned.
mpearson@chromium.org
The time elapsed between the sending of a suggest request to Google until
the time the request was returned with status==success. Ignores requests
that were canceled before being returned.
mpearson@chromium.org
Counts about the number of suggest requests the omnibox sent, invalidated,
and replies received.
mpearson@chromium.org
The length of the text the user entered in the omnibox when he/she used the
omnibox to go somewhere. All values larger than 500 are recorded in bucket
500.
mpearson@chromium.org
The amount of time, in milliseconds, since the user first began modifying
the text in the omnibox until the user used the omnibox to go somewhere. If
at some point after modifying the text, the user reverted the modifications
(thus seeing the current web page's URL again), then wrote in the omnibox
again, this duration starts from the time of the second series of
modification.
kenjibaheux@chromium.org
mpearson@chromium.org
Counts the number of times that the user text is cleared. IME users are
sometimes in the situation that IME was unintentionally turned on and failed
to input latin alphabets (ASCII characters) or the opposite case. In that
case, users may delete all the text and the user text gets cleared. This
histogram helps us estimate how often this scenario happens.
Note that since we don't currently correlate "text cleared" events
with IME usage, this also captures many other cases where users clear the
text; though it explicitly doesn't log deleting all the permanent text as
the first action of an editing sequence (see comments in
OnAfterPossibleChange()).
hfung@chromium.org
The number of most visited suggestions returned when ZeroSuggest would have
triggered. The suggestions appear when the user has focused but not
modified the omnibox.
hfung@chromium.org
Counts about the number of zero suggest requests (requests for suggestions
when the user has focused but not modified the omnibox) the omnibox sent,
invalidated, and replies received.
merkulova@chromium.org
Time from boot to sign-in completed.
rsorokin@chromium.org
Time spent on error screens during enrollment or autoenrollment.
rsorokin@chromium.org
Time spent on error screens during signin.
rsorokin@chromium.org
Time spent on error screens during supervised user creation.
rsorokin@chromium.org
Time spent on error screens during update.
rsorokin@google.com
Number of times error screen has appeared during enrollment or
autoenrollment.
rsorokin@google.com
Number of times error screen has appeared during signin.
rsorokin@google.com
Number of times error screen has appeared during supervised user creation.
rsorokin@google.com
Number of times error screen has appeared during update.
merkulova@chromium.org
Time spent on specific OOBE screen.
Deprecated with CL 731423002. OriginChip has been removed.
gbillock@chromium.org
The number of clicks on the origin chip.
erikchen@chromium.org
The availability and capabilities of the Bluetooth driver on OSX devices.
This metric is logged on startup.
Obselete as of Chrome 43. See OmahaProxy for more relevant statistics.
mark@chromium.org
The cat's flavor and how many bits there are in it.
mark@chromium.org
Events seen by the OSX NSException swizzle.
Deprecated as of Chrome 40. See OSX.Fullscreen.Enter.Style,
OSX.Fullscreen.Enter.WindowLocation and
OSX.Settings.ScreensHaveSeparateSpaces.
erikchen@chromium.org
This event is recorded each time a user triggers fullscreen for a browser
window. The value's bits reflect different parameters. Bit 0: Fullscreen
entry mechanism (AppKit vs Immersive). Bit 1: Whether the window was on the
primary screen (Primary vs. Secondary). Bit 2: Whether displays have
separate spaces options is enabled (Seperate vs Shared). Bit 3: Whether
there are multiple screens.
erikchen@chromium.org
This event is recorded each time a user triggers fullscreen for a browser
window. It indicates the mechanism (immersive vs. AppKit) and the type of
AppKit Fullscreen (Presentation Mode vs. Canonical Fullscreen).
erikchen@chromium.org
This event is recorded each time a user triggers fullscreen for a browser
window. It indicates the screen in which the window was fullscreened, and
the number of screens available.
erikchen@chromium.org
This event is recorded each time a Handoff is received by Chrome on OSX. The
enumeration indicates the source of the Handoff.
erikchen@chromium.org
This event records the amount of time that the browser process main thread
blocks, waiting for a frame with the right dimensions to arrive from the gpu
process.
erikchen@chromium.org
The configuration of the setting "Screens Have Separate Spaces"
available in OSX 10.9+.
erikchen@chromium.org
Whether an attempt to load the system hotkeys on a Mac was successful.
mad@chromium.org
Counts the number of times the user clicked on the later button of the
outdated upgrade bubble, before clicking on the enable updates button in the
same Chrome session.
mad@chromium.org
Counts the number of times the user clicked on the later button of the
outdated upgrade bubble, before clicking on the reinstall button in the same
Chrome session.
rbyers@chromium.org
mfomitchev@chromium.org
Overscroll gestures that were aborted before they were completed.
Deprecated as of Chrome 44 in favour of Overscroll.Cancelled and
Overscroll.Navigated2.
rbyers@chromium.org
mfomitchev@chromium.org
Completed overscroll gestures.
An overscroll gesture starts when user scrolls past the edge of the web page
and continues scrolling in the same direction. An overscroll gesture is
completed when user stops scrolling (e.g. by lifting the fingers from the
touchscreen or touchpad).
rbyers@chromium.org
mfomitchev@chromium.org
Deprecated as of Chrome 44 to switch to NavigationDirection enum.
Navigations that were triggered due to completed overscroll gesture. Note
that not all completed overscroll gestures trigger a navigation.
rbyers@chromium.org
mfomitchev@chromium.org
Navigations that were triggered due to completed overscroll gesture. Note
that not all completed overscroll gestures trigger a navigation.
rbyers@chromium.org
mfomitchev@chromium.org
Deprecated as of Chrome 44 to switch to NavigationDirection enum.
Overscroll gestures initiated by the user. Note that not all overcroll
gestures started are completed (e.g. the overscroll gesture is aborted if
user clicks or presses a key during the gesture).
rbyers@chromium.org
mfomitchev@chromium.org
Overscroll gestures initiated by the user. Note that not all overcroll
gestures started are completed (e.g. the overscroll gesture is aborted if
user clicks or presses a key during the gesture).
zeuthen@chromium.org
The wall-clock time spent until a lookup was canceled. This is reported
every time p2p is used to find a candidate but the request was canceled.
zeuthen@chromium.org
The number of candidates on the LAN, i.e. the number of peers on the LAN
offering at least N bytes of the requested file X. This is reported after
examining responses from all peers on the LAN and picking a candidate.
zeuthen@chromium.org
The number of p2p downloads of the peer that the returned URL points to.
This is reported after examining responses from all peers on the LAN and
picking a candidate.
zeuthen@chromium.org
The wall-clock time spent waiting for the LAN-wide number of p2p downloads
(i.e. the sum of p2p downloads from each peer on the LAN) to drop below the
threshold. This is reported after examining responses from all peers on the
LAN and picking a candidate.
zeuthen@chromium.org
The result of the lookup. Possible values include "Found" (if a
candidate - i.e. a peer offering at least N bytes of file X - was chosen),
"Not Found" (if no candidate could be found), "Vanished"
(if a candidate was found but vanished while waiting in line),
"Canceled" (if a candidate was found but the request was canceled
while waiting in line), and "Filtered" (if it was detected that
mDNS was filtered). This is reported after examining responses from all
peers on the LAN when p2p is used to find a candidate.
zeuthen@chromium.org
The number of peers implementing p2p file sharing on the network. This is
reported every time p2p is used to look up a resource on a network where
mDNS is not filtered.
zeuthen@chromium.org
The wall-clock time spent waiting for one or more candidates (i.e. peers
offering at least N bytes of file X) that all vanished before the LAN-wide
number of p2p downloads dropped below the threshold. This is reported every
time candidates were found using p2p but then vanished.
zeuthen@chromium.org
The number of currently connected HTTP clients. This is reported every time
a HTTP client connects.
zeuthen@chromium.org
Number of megabytes (1,000,000 bytes) served from the device (via HTTP)
where the client disconnects prematurely. This is reported every time a file
is served and the client disconnects before receiving all data.
zeuthen@chromium.org
Number of megabytes (1,000,000 bytes) served from the device (via HTTP).
This is reported every time a file have been served successfully.
zeuthen@chromium.org
The average speed at which the download was served at, in kB/s. This is
reported every time a file have been served successfully.
zeuthen@chromium.org
The number of files available via p2p. This is reported every time a file is
added or removed to the /var/cache/p2p directory.
zeuthen@chromium.org
When a client resumes a download, the HTTP request includes range specifier
to skip the bytes it already has. This metric conveys this as a percentage
of the file size. This is reported every time a file is served, even if the
request does not include a range specifier (in which case 0 is reported).
zeuthen@chromium.org
The result of the HTTP request. Possible values include "Response
Sent" (the resource was found and the response was successfully sent),
"Response Interrupted" (the resource was found but the client
disconnected), "Malformed" (the request was malformed), "Not
Found" (the request was for a resource that was not found), and
"Index" (the request was for the '/' or '/index.html' resource).
This is reported for every HTTP request handled.
finnur@chromium.org
The number of Extensions that have Page Actions. Measured once per startup
per profile.
haraken@chromium.org
The committed memory size in PartitionAlloc. The value is reported when we
see the highest memory usage we've ever seen in the renderer process.
mkwst@chromium.org
markusheintz@chromium.org
When the password management bubble opened, what state was it in?
gcasto@chromium.org
Measures the frequency of various password generation events.
Note that this histogram is logged from the renderer process, and
consequently the numbers should not be directly compared to the other
PasswordGeneration.* histograms, which are logged from the browser process.
Histograms logged in different processes are lost at different rates, which
introduces systematic bias between histograms logged in the renderer process
vs. those logged in the browser process.
gcasto@chromium.org
Measures the frequency of submission events for generated passwords. This is
similar to PasswordManager.ActionsTakenWithPsl but only tracks events which
are interesting for generated passwords.
gcasto@chromium.org
The number of times that we try to upload a form that we believe should
trigger password generation. False means that something about the form would
not allow us to try upload (not an Autofillable field, uploading disabled,
Autofill servers in backoff, etc.). True does not mean that the upload
actually completed successfully, just that it was started.
mlerman@chromium.org
Time required to create the local hash of the user's GAIA password.
gcasto@chromium.org
vabr@chromium.org
The number of accounts stored per site in the password manager (one event
per site)
Deprecated as of Chrome 32. See PasswordManagerActionsTakenWithPsl
dubroy@chromium.org
vabr@chromium.org
Stats documenting how we handle every form containing a password, bucketed
by the actions taken.
dubroy@chromium.org
vabr@chromium.org
yfriedman@chromium.org
Stats documenting how we handle every form containing a password, bucketed
by the actions taken.
Deprecated as of 3/18/2014. See PasswordManagerActionsTakenV3.
dubroy@chromium.org
vabr@chromium.org
yfriedman@chromium.org
Stats documenting how we handle every form containing a password, bucketed
by the actions taken.
engedy@chromium.org
The number of facets for which affiliation information was requested in a
network fetch. Recorded for each network fetch.
engedy@chromium.org
The time elapsed between creation of the AffiliationBackend and the first
time it needed to issue a network fetch.
engedy@chromium.org
The elapsed time between subsequent network fetches. Recorded whenever the
AffiliationBackend initiated a network fetch, regardless of success or
failure.
engedy@chromium.org
The number of facets affiliated with a dummy Web facet, according to the
affiliation information retrieved from the cache. Recorded for each dummy
Web facet, once shortly after start-up, and then periodically every hour;
but only if getting affiliations succeeded for the Web facet.
engedy@chromium.org
Whether or not affiliations of a dummy Web facet could be successfully
retrieved from the cache. Recorded for each dummy Web facet, once shortly
after start-up, and then periodically every hour.
engedy@chromium.org
The network error code, as reported by the underlying URLFetcher. Recorded
only for each network fetch that failed due to network/server errors.
engedy@chromium.org
The HTTP response code, as reported by the underlying URLFetcher. Recorded
only for each network fetch that failed due to network/server errors.
engedy@chromium.org
Whether the network fetch succeeded, failed due to network/server errors, or
contained malformed data. Recorded for each network fetch.
The bubble isn't shown anymore.
melandory@chromium.org
vasilii@chromium.org
Why was "Allow to collect URL?" bubble closed?
gcasto@chromium.org
vabr@chromium.org
The total number of sites that the user has blacklisted. Recorded by
iterating over stored passwords once per run of Chrome.
vasilii@chromium.org
Number of password forms with empty username in the Login Database. This is
recorded on startup.
msramek@chromium.org
vasilii@chromium.org
When parsing a password form, and no username field is detected, whether
this was a password change form.
vasilii@chromium.org
When offering to save a password, whether the username is empty.
vasilii@chromium.org
When parsing a password form, whether a username field is detected.
msramek@chromium.org
vasilii@chromium.org
The total number of text and password fields for password forms that do not
have a username field. This is recorded every time such a password form is
successfully parsed. Note that the parsing is attempted when the form is
encountered (i.e when the document is loaded) and also when it is submitted.
msramek@chromium.org
vasilii@chromium.org
Number of password forms with empty username in the Login Database for which
there is not another password form from the same realm with a nonempty
username. In other words, number of password forms with empty username which
we do not suspect to be reauthentication forms.
dubroy@chromium.org
vabr@chromium.org
Indicates whether the password manager is enabled when a tab is opened. This
includes prerendered tabs.
gcasto@chromium.org
dvadym@chromium.org
The success or failure of deserializing saved FormData. Failure either
indicates corrupted data or the presence of bugs in the serialization or
deserialization code.
dubroy@chromium.org
vabr@chromium.org
The distribution of responses to the "Do you want Chrome to remember
this password"? info bar prompt.
gcasto@chromium.org
dvadym@chromium.org
The success or failure of deserializing PasswordForms in KWallet. Failure
either indicates corrupted data or the presense of bugs in the
deserialization code.
dvadym@chromium.org
vabr@chromium.org
Information about usage of password storage backends on Linux. It also
includes whether a command line flag for a specific backend is given.
dubroy@chromium.org
vabr@chromium.org
Number of passwords deleted when the user chooses to clear passwords via the
clear browsing data UI.
vasilii@chromium.org
Number of passwords deleted when browsing data is cleared during rollback.
dubroy@chromium.org
vabr@chromium.org
When the user chooses to never remember passwords for a form, we remove all
previously saved credentials for that form. This is the count of those
credentials.
dubroy@chromium.org
vabr@chromium.org
The password manager only shows those credentials that are considered the
best match for a particular form. This stat keep track of the credentials
that were not as good of a match and were suppressed.
dubroy@chromium.org
vabr@chromium.org
wfh@chromium.org
Indicates whether the user's OS password is blank or not at browser startup.
dubroy@chromium.org
vabr@chromium.org
Breakdown of how other possible usernames are displayed. Recorded every time
we autofill a password form.
dubroy@chromium.org
vabr@chromium.org
Breakdown of cases where a password is submitted, but we don't even try and
save it. Recorded for every password form submit.
dubroy@chromium.org
vabr@chromium.org
yfriedman@chromium.org
Breakdown on trigger rate of providing a password form autofill entry based
on matching stored information using the public suffix list for possible
matches.
dubroy@chromium.org
vabr@chromium.org
Indicates whether the save password prompt disappeared in less than one
second. This most likely indicates that the prompt was dismissed
automatically, e.g. due to a page navigation, before the user was able to
respond to the infobar.
dubroy@chromium.org
vabr@chromium.org
Indicates whether the save password prompt was displayed.
dubroy@chromium.org
vabr@chromium.org
Breakdown of which response the user selected from the save password prompt.
vabr@chromium.org
Indicates whether submitting a password login form changes the registry
controlled domain of the main frame.
gcasto@chromium.org
vabr@chromium.org
The type (e.g. signup, login, change password) of all submitted password
forms. This is logged on form submission, but doesn't require that the
password manager saves.
gcasto@chromium.org
vabr@chromium.org
If the sync credential was removed from autofill consideration.
gcasto@chromium.org
vabr@chromium.org
Information about the user's current sync status crossed with whether their
synced password is saved.
gcasto@chromium.org
vabr@chromium.org
Deprecated as of 11/11/14. New statistic is
PasswordManager.TimesPasswordUsed.AutoGenerated.
The number of times each generated password has been used to log in.
Recorded by iterating over stored passwords once per run. This information
is persisted and synced.
gcasto@chromium.org
vabr@chromium.org
The number of times each saved password has been used to log in. Does not
include generated passwords. Recorded by iterating over stored passwords
once per run. This information is persisted and synced.
gcasto@chromium.org
vabr@chromium.org
The number of accounts stored in the password manager (across all sites)
mkwst@chromium.org
markusheintz@chromium.org
Why was the password manager's UI (bubble or infobar) closed?
mackinlay@google.com
teravest@chromium.org
The number of out-of-process plugin processes that have loaded a particular
PPB interface version.
raymes@chromium.org
jww@chromium.org
rsleevi@chromium.org
Whether a Pepper TCP connect attempt comes from a plugin in a secure or an
insecure origin.
raymes@chromium.org
jww@chromium.org
rsleevi@chromium.org
Whether a Pepper UDP bind attempt comes from a plugin in a secure or an
insecure origin.
oysteine@chromium.org
Average CPU utilization of a process, read out at each two-minute interval.
The utilization is in the 0-100% range per CPU, which is then summed up.
I.e. a quadcore system fully loaded would read as 400%.
oysteine@chromium.org
The number of times a process has continuously stayed above a certain
threshold of CPU utilization over a certain time period (currently set to
two minutes).
Please list the metric's owners. Add more owner tags as needed.
Chrome OS (ARM Chromebooks using Exynos 5250 only) Adaptive Support Voltage
Group, recorded once per bootup. Indicates which "bin" the SoC is
part of, which sets the voltage that different rails on the system will run
at. The values 0-11 are valid. A value of 12 indicates an error parsing
dmesg and should be investigated. See also Platform.LotIdEnum.
cernekee@chromium.org
Indicates whether the kernel's ACPI Smart Battery System driver logged an
error trying to find the battery on boot.
sonnyrao@chromium.org
Chrome OS number of disk sectors read at boot from kernel start to
login-prompt-ready.
sonnyrao@chromium.org
Chrome OS number of disk sectors written at boot from kernel start to
login-prompt-ready.
sonnyrao@chromium.org
Chrome OS size of allocated swap area in megabytes (before compression)
sonnyrao@chromium.org
CPU frequency as percent of the baseline frequency, sampled every 30s. This
may be throttled down from 100% due to power dissipation issues (too high
temperature). It may also be throttled up (turbo), but the kernel does not
report the actual turbo frequency, so we put such samples in the 101%
bucket.
sonnyrao@chromium.org
cast-analytics@google.com
Peak total (single core) CPU usage for the last sample interval. The sample
interval may vary from seconds to several minutes.
dkrahn@chromium.org
Generic event of interest from Chrome OS. Intended mainly to help assess
the frequency of rare error conditions.
Please list the metric's owners. Add more owner tags as needed.
Average size of user's Cache directory. Logged once a day, if disk usage is
high.
Please list the metric's owners. Add more owner tags as needed.
Maximum size of user's Cache directory. Logged once a day, if disk usage is
high.
Please list the metric's owners. Add more owner tags as needed.
Average size of user's Cache directory. Logged once a day, if disk usage is
high.
Please list the metric's owners. Add more owner tags as needed.
Maximum size of user's Cache directory. Logged once a day, if disk usage is
high.
Please list the metric's owners. Add more owner tags as needed.
Average size of user's GCache directory. Logged once a day, if disk usage is
high.
Please list the metric's owners. Add more owner tags as needed.
Maximum size of user's GCache directory. Logged once a day, if disk usage is
high.
Please list the metric's owners. Add more owner tags as needed.
Days since the least frequently used account signed in. Logged once a day,
if disk usage is high.
Please list the metric's owners. Add more owner tags as needed.
Number of users home directories on the device. Logged once a day.
Please list the metric's owners. Add more owner tags as needed.
Days since last login of the least recently user on device. Logged once a
day, if disk usage is high.
Please list the metric's owners. Add more owner tags as needed.
Number of user home dirs on device. Logged once a day, if disk usage is
high.
keescook@google.com
Chrome OS KB in use in the /home/chronos filesystem tree. Logged once a day
during log file cleanup.
keescook@google.com
Chrome OS KB in use in the /var filesystem tree. Logged once a day during
log file cleanup.
Please list the metric's owners. Add more owner tags as needed.
The maximum supported micro-architecture on an Intel platform. This value
is logged at program start time.
Please list the metric's owners. Add more owner tags as needed.
The 32-bit hash of a kernel warning. This is the hash of the
"file:line" string corresponding to the location of the warning,
for instance: "/mnt/host/source/src/third_party/kernel/files/drivers
/gpu/drm/i915/intel_dp.c:351" (ignore spurious spaces). The hash is
produced by this code: while (*string) hash = (hash << 5) + hash +
*string++; Separately each warning is also collected (with its hash) via
the crash reporter, but only its first occurrence in each boot session.
Contact semenzato@ for further info.
sonnyrao@chromium.org
Number of logical processors. This includes Hyperthreaded cores.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS (ARM Chromebooks using Exynos 5250 only) indication about whether
we're part of a special lot ID. Special lot IDs are groups of chips that
have special case handling in the kernel for the Adaptive Support Voltage
code (the normal logic doesn't work). See also Platform.AsvGroup. Note
that fused devices are never part of a special lot (currently) and only some
unfused lots are "special".
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of active memory as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS active anonymous memory (data segments) as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS active file-backed memory (executables, ...) as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of anonymous memory as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of buffer cache as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS: size of file-backed memory minus swap and buffer cache, as % of
total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of inactive memory as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS inactive anonymous memory (data segments) as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS inactive file-backed memory as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of mapped memory as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of free memory as % of total memory.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of shared memory in Kbytes.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS size of slab memory in Kbytes.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS amount of swapped-out memory in Kbytes. These, and all other
MEMINFO stats, are snapshotted every 30s.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS amount of swapped-out memory as % of total RAM. These, and all
other MEMINFO stats, are snapshotted every 30s.
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
Chrome OS unevictable memory (ramfs, SHM_LOCKED, mlocked) in Kbytes.
hajimehoshi@chromium.org
kouhei@chromium.org
cast-analytics@google.com
Peak memory bandwith (read and write) usage during the last sample interval.
The sample interval may vary from seconds to several minutes.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory 1
minute after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory 5
minutes after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory 30
minutes after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory
150 minutes after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory
750 minutes after boot.
sonnyrao@chromium.org
Page faults per second averaged over 30s interval, sampled continuously.
sonnyrao@chromium.org
Page faults per second averaged over 1s interval, sampled every 30s.
gwendal@google.com
Number of disk sectors per second read by Chrome OS in a long interval
(currently 30s)
gwendal@google.com
Number of disk sectors per second read by Chrome OS in a short interval
(currently 1s, sampled every 30s)
gwendal@google.com
Disk communication errors (SMART 199), sent at boot.
gwendal@google.com
Uncorrectable disk errors (SMART 187), sent at boot.
vpalatin@google.com
USB device ID of the charger plugged into a Spring device (if any), sent
once a minute. The Device ID is composed from the following 4 8-bit
registers of the TSU6721 chip: ADC (07h), Device Type 3 (15h), Device Type 2
(0Bh), Device Type 1 (0Ah). Device Type 1/2/3 is a bitmap and most of bits
are mutually exclusive (excepted VBUS debounce). ADC is the 5-bit value of
the ID pin, but for most types (as in Device Type), there are only one or
two possible ID pin connections/values. The datasheet can be found here:
http://www.ti.com/lit/ds/symlink/tsu6721.pdf.
Note that different brand/models of the charger can have the same ID.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS stateful partition usage level.
dehrenberg@chromium.org
cast-analytics@google.com
The number of blocks marked bad in an MTD partition. This is relevant for
devices with raw NAND flash, such as Chromecast. Sampled once daily, if the
Chromecast is on for any significant length of time in the day.
sonnyrao@chromium.org
Average pages/second swapped IN over a 30s interval, sampled every 30s.
sonnyrao@chromium.org
Average pages/second swapped IN over a 1s interval, sampled every 30s.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
CPU utilization for the specified swap group and time interval after a tab
switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
Deprecated 9/2013 when the SwapJank64vs32Parrot experiment ended.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
tab switch event. See src/chrome/browser/chromeos/swap_metrics.cc.
sonnyrao@chromium.org
Average pages/second swapped OUT over a 30s interval, sampled every 30s.
sonnyrao@chromium.org
Average pages/second swapped OUT over a 1s interval, sampled every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 0 (I2C_CPU-Die) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 1 (I2C_CPU-Object) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 2 (I2C_PCH-Die) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 3 (I2C_PCH-Object) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 4 (I2C_DDR-Die) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 5 (I2C_DDR-Object) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 6 (Charger-Die), taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 7 (Charger-Object) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 8 (ECInternal) taken every 30s.
Please list the metric's owners. Add more owner tags as needed.
Temperature reading at sensor 9 (PECI) taken every 30s.
mka@chromium.org
Temperature reading at sensor 0 of the CPU collected every few seconds (may
vary between devices).
This metric is specific to ChromeOS.
mka@chromium.org
Temperature reading at wireless interface 0 collected every few seconds (may
vary between devices).
This metric is specific to ChromeOS.
mka@chromium.org
Temperature reading at wireless interface 1 collected every few seconds (may
vary between devices).
This metric is specific to ChromeOS.
mka@chromium.org
Temperature reading at wireless interface 2 collected every few seconds (may
vary between devices).
This metric is specific to ChromeOS.
mka@chromium.org
State of the thermal zone of the CPU collected every second. State depends
on device, higher state corresponds to a higher temperature.
This metric is specific to ChromeOS.
mka@chromium.org
State of the thermal zone of wireless interface 0 collected every second.
State depends on device, higher state corresponds to a higher temperature.
This metric is specific to ChromeOS.
mka@chromium.org
State of the thermal zone of wireless interface 1 collected every second.
State depends on device, higher state corresponds to a higher temperature.
This metric is specific to ChromeOS.
mka@chromium.org
State of the thermal zone of wireless interface 2 collected every second.
State depends on device, higher state corresponds to a higher temperature.
This metric is specific to ChromeOS.
semenzato@chromium.org
Each sample is the result code of a TPM authorized command issued through
tcsd. Success is 0. For the other error codes, see
/usr/include/tss/tpm_error.h.
dkrahn@chromium.org
Each sample is the value of the TPM dictionary attack counter reported at
boot and hourly while running. Any non-zero value is unexpected.
dkrahn@chromium.org
Each sample is the status of an hourly attempt to reset the TPM dictionary
attack counter.
semenzato@chromium.org
Each sample is the result code of a TPM command issued through tcsd. Success
is 0. For the other error codes, see /usr/include/tss/tpm_error.h.
dkrahn@chromium.org
Each sample is the number of consecutive reboots performed while attempting
to clear a TPM (Trusted Platform Module) error.
Please list the metric's owners. Add more owner tags as needed.
Retries needed to enable a FET on tps65090 (AKA tpschrome). Tps65090 is a
power management unit (PMU) used on many ARM Chromebooks. Until version ES7
was rolled into production we would sometimes run into a problem where FET1
(the FET used to switch on and off the backlight) wouldn't turn on properly.
This problem was especially prevalent when the voltage was high (like when
the device was plugged into the wall). Retrying by turning the FET off and
on again is nearly always effective, so the kernel will retry up to 5 times
(currently) and will also log the fact that it needed to retry. On newest
kernels (kernel 3.8 and up) a kernel warning will be logged with WARN_ON if
the FET still failed to turn on after 5 tries. Refer to the kernel warning
reports to find that information. For more details about this bug refer to
http://crbug.com/338657 and http://crosbug.com/p/16009. Note that we log
retries on all 7 FETs even though we've only ever seen failures of FET1.
gwendal@google.com
Number of disk sectors per second written by Chrome OS in a long interval
(currently 30s)
gwendal@google.com
Number of disk sectors per second written by Chrome OS in a short interval
(currently 1s, sampled every 30s)
semenzato@google.com
Compressed swap size in megabytes. This is the actual amount of RAM used by
the system to compress memory (i.e. after compression). Snapshot every 30s.
semenzato@google.com
The ratio of compressed memory (zram) before and after compression when the
denominator at least 1 MB. Ratios of interest are between 1 and 6 (typically
between 2 and 3), and we express them as a percentage (between 100% and
600%). The size of memory before compression includes zero-filled pages.
Values close to 100% indicate low compression effectiveness. Snapshot every
30s.
semenzato@google.com
RAM savings in megabytes from using memory compression. This is the
difference between the RAM size before and after compression. Snapshot
every 30s.
semenzato@google.com
Number of zero-filled pages that the OS is compressing. A large number
suggests wasteful allocation. Snapshot every 30s.
semenzato@google.com
The fraction of compressed memory that consists of zero-filled pages.
Snapshot every 30s.
tnagel@chromium.org
The time it takes to run File::Flush().
Deprecated as of 2013-05, replaced by
PlatformFile.UnknownCreateFileErrorsWin in chrome 29.
Please list the metric's owners. Add more owner tags as needed.
Errors returned by CreateFile on windows that PlatformFileError doesn't yet
support.
dgrogan@chromium.org
Errors returned by CreateFile on POSIX that PlatformFileError doesn't yet
support.
dgrogan@chromium.org
Errors returned by CreateFile on Windows that PlatformFileError doesn't yet
support.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Distribution of actual finished pages, vs abandoned pages, where we needed
to declare a finish time prematurely since the page was being closed
(exited).
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by Abandoned_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by Abandoned_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated as of 2014-06.
vabr@chromium.org
The PLT.Abandoned histogram for pages loaded after WebRequest API was used.
Deprecated 6/2014. Replaced by Abandoned_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by Abandoned_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by Abandoned_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Diagnose why a page load was considered abandoned.
Please list the metric's owners. Add more owner tags as needed.
Time from "begin" to "commit." "Begin"==
"request" if user requested, and "start" otherwise.
"Request"== time when user requested document. "Start"==
time when renderer requested load of document, after any unload of last
document. "Commit"== time when renderer got first byte of
document.
Please list the metric's owners. Add more owner tags as needed.
TBD
Deprecated as of http://crrev.com/392823002
kouhei@chromium.org
PLT.BeginToFinish, but for pages requested just after a new preconnect
request.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinish, but for pages which contained prefetch links.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinish, but for pages which were referred to by pages which
contained prefetch links.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadNormal_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadNormal_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
vabr@chromium.org
The PLT.BeginToFinish histogram for pages loaded by following a link, after
WebRequest API was used.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadNormal_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadNormal_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadNormal_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadReload_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadReload_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
vabr@chromium.org
The PLT.BeginToFinish histogram for pages reloaded by JavaScript or by
following a link, after WebRequest API was used.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadReload_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadReload_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadReload_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
vabr@chromium.org
The PLT.BeginToFinish histogram for pages loads initiated by back/forward
buttons, or by a change of encoding, after WebRequest API was used.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by
BeginToFinish_LinkLoadStaleOk_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
vabr@chromium.org
The PLT.BeginToFinish histogram for pages loaded by entering a URL or a
search query into Omnibox, after WebRequest API was used.
Deprecated 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 6/2014. Replaced by BeginToFinish_NormalLoad_ExtensionWebRequest.
Please list the metric's owners. Add more owner tags as needed.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinish, but for pages fetched over a SPDY proxy.
Please list the metric's owners. Add more owner tags as needed.
TBD
Deprecated as of http://crrev.com/392823002
kouhei@chromium.org
PLT.BeginToFinishDoc, but for pages requested just after a new preconnect
request.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinishDoc, but for pages which contained prefetch links.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinishDoc, but for pages which were referred to by pages which
contained prefetch links.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinshDoc, but for pages fetched over a SPDY proxy.
pmeenan@chromium.org
Time from "begin" to "first paint." "Begin"==
"request" if user requested, and "start" otherwise.
"Request"== time when user requested document. "Start"==
time when renderer requested load of document, after any unload of last
document. "First paint"== time when first paint operation was
performed.
pmeenan@chromium.org
Time from "big" to "first paint after load."
"Begin"== "request" if user requested, and
"start" otherwise. "Request"== time when user requested
document. "Start"== time when renderer requested load of document,
after any unload of last document. "First paint after load"== time
after onload() when first paint operation is performed.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "finish." "Commit"==
time when renderer got first byte of document. "Finish"==after
onload() and all resources are loaded.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "finish doc." "Commit"==
time when renderer got first byte of document. "Finish doc" ==
main document loaded, before onload(). "Finish"==after onload()
and all resources are loaded.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "first paint."
"Commit"== time when renderer got first byte of document.
"First paint"== time when first paint operation was performed.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "first paint after load."
"Commit"== time when renderer got first byte of document.
"First paint after load"== time after onload() when first paint
operation is performed.
Please list the metric's owners. Add more owner tags as needed.
Time from "finish doc" to "finish." "Finish
doc"== main document loaded, before onload(). "Finish"==after
onload() and all resources are loaded.
Please list the metric's owners. Add more owner tags as needed.
Time from "finish " to "first paint after load."
"Finish"==after onload() and all resources are loaded. "First
paint after load"== time after onload() when first paint operation is
performed.
Please list the metric's owners. Add more owner tags as needed.
Probability distribution for enumerated varieties of page loads.
Deprecated as of 2014-06.
Please list the metric's owners. Add more owner tags as needed.
Diagnose error conditions in PLT reporting. A start time should always be
present.
deprecated 2012-01-19 in favour of PLT.PT_*
Please list the metric's owners. Add more owner tags as needed.
The time elapsed between the Navigation Timing metrics navigationStart and
loadEventEnd. Definitions: http://www.w3.org/TR/navigation-timing/
deprecated 2012-01-19 in favour of PLT.PT_*
Please list the metric's owners. Add more owner tags as needed.
The time elapsed between the Navigation Timing metrics navigationStart and
loadEventStart. Definitions: http://www.w3.org/TR/navigation-timing/
bolian@chromium.org
Time from connectStart to connectEnd based on Navigation Timing.
bolian@chromium.org
Time from domanLookupEnd to connectStart based on Navigation Timing.
bolian@chromium.org
Time from fetchStart to domainLookupStart based on Navigation Timing.
bolian@chromium.org
Time from responseStart to domLoading based on Navigation Timing.
bolian@chromium.org
Time from navigationStart to fetchStart based on Navigation Timing when no
redirect.
bolian@chromium.org
Time from navigationStart to fetchStart excluding time spent on redirects
based on Navigation Timing. Only page loads with redirects are considered.
bolian@chromium.org
Time from domContentLoadedEventEnd to loadEventStart based on Navigation
Timing.
bolian@chromium.org
Time from connectEnd to requestStart based on Navigation Timing.
bolian@chromium.org
Time from domainLookupStart to domainLookupEnd based on Navigation Timing.
bolian@chromium.org
Time from domContentLoadedEventStart to domContentLoadedEventEnd based on
Navigation Timing.
bolian@chromium.org
Time from domInteractive to domContentLoadEventStart based on Navigation
Timing.
bolian@chromium.org
Time from domLoading to domInteractive based on Navigation Timing.
bolian@chromium.org
Time from loadEventStart to loadEventEnd based on Navigation Timing.
bolian@chromium.org
Time from redirectStart to redirectEnd based on Navigation Timing when
redirects exist.
bolian@chromium.org
Time from requestStart to responseStart based on Navigation Timing.
bolian@chromium.org
Time from responseStart to responseEnd based on Navigation Timing.
Deprecated as of 5/02/2011.
Please list the metric's owners. Add more owner tags as needed.
Distribution of discarded and displayed prerendered pages.
Deprecated as of 5/02/2011, replaced by Prerender.RendererPLT.
Please list the metric's owners. Add more owner tags as needed.
Perceived load time of a page. For non-prerendered pages, this is just
BeginToFinish. For displayed prerendered pages, this is the time from when
the prerendered page is moved into a TabContents until finish.
"Finish" == after onload() and all resources are loaded. Note that
this is 0 if the loading finishes before the page is moved into a
TabContents.
Deprecated as of 5/02/2011, replaced by
Prerender.RendererPerceivedPLTMatched.
Please list the metric's owners. Add more owner tags as needed.
Perceived load time of a prerendered page that is displayed. This is the
time from when the prerendered page is moved into a TabContents until
finish. "Finish" == after onload() and all resources are loaded.
Note that this is 0 if the loading finishes before the page is moved into a
TabContents.
Deprecated as of 5/02/2011, replaced by Prerender.RendererTimeUntilDisplay.
Please list the metric's owners. Add more owner tags as needed.
The time elapsed between when the prerendering of a page starts and when the
page is displayed. Prerendered pages discarded without being displayed are
excluded from this count.
Deprecated as of 5/02/2011, replaced by Prerender.RendererIdleTime.
Please list the metric's owners. Add more owner tags as needed.
This is the time from when a prerendered page finishes loading to when it is
displayed. When a page is displayed before it finishes loading, no value is
recorded in this histogram.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or
navigationStart if user-initiated request.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or
navigationStart if user-initiated request. Only page loads through the data
reduction proxy are considered.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.BeginToFinish. Finish: loadEventEnd. Begin: requestStart or
navigationStart if user-initiated request.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.BeginToFinish_SpdyProxy. Finish: loadEventEnd. Begin:
requestStart or navigationStart if user-initiated request. Only page loads
through the data reduction proxy are considered.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.BeginToFinishDoc. FinishDoc: loadEventStart. Begin:
requestStart or navigationStart if user-initiated request.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.BeginToFinishDoc_SpdyProxy. FinishDoc: loadEventStart. Begin:
requestStart or navigationStart if user-initiated request. Only page loads
through the data reduction proxy are considered.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd.
Only page loads through the data reduction proxy are considered.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc:
loadEventStart.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc:
loadEventStart. Only page loads through the data reduction proxy are
considered.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc:
loadEventStart.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc:
loadEventStart. Only page loads through the data reduction proxy are
considered.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and measures the time until
the renderer got first byte of document. Commit: time when renderer got
first byte of document. Request: navigationStart.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and measures the time until
the beginning of the DOMContentLoaded event. DOMContentLoaded:
domContentLoadedEventStart. Request: navigationStart.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.RequestToFinish. Finish: loadEventEnd. Request:
navigationStart.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.RequestToFinish. Finish: loadEventEnd. Request:
navigationStart. Only page loads through the data reduction proxy are
considered.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and measures the page load
time until the beginning of the load event. Finish: loadEventStart. Request:
navigationStart.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.RequestToStart. Start: requestStart. Request:
navigationStart.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.RequestToStart. Start: requestStart. Request:
navigationStart. Only page loads through the data reduction proxy are
considered.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.StartToCommit. Start: requestStart. Commit: responseStart.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.StartToCommit. Start: requestStart. Commit: responseStart.
Only page loads through the data reduction proxy are considered.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd.
Only page loads through the data reduction proxy are considered.
Please list the metric's owners. Add more owner tags as needed.
Time from "request" to "finish." "Request" ==
time when user requested document. "Finish" == after onload() and
all resources are loaded.
Please list the metric's owners. Add more owner tags as needed.
Time from "request" to "start." "Request"==
time when user requested document. "Start"== time when renderer
requested load of document, after any unload of last document.
Please list the metric's owners. Add more owner tags as needed.
Time from "start" to "commit." "Start"== time
when renderer requested load of document, after any unload of last document.
"Commit"== time when renderer got first byte of document.
Please list the metric's owners. Add more owner tags as needed.
Time from "start" to "finish." "Start"== time
when renderer requested load of document, after any unload of last document.
"Finish"==after onload() and all resources are loaded.
Deprecated as of 07/2014.
Please list the metric's owners. Add more owner tags as needed.
StartToFinish times when using http and no proxy.
Deprecated as of 07/2014.
Please list the metric's owners. Add more owner tags as needed.
StartToFinish times when using https and no proxy.
Deprecated as of 07/2014.
Please list the metric's owners. Add more owner tags as needed.
StartToFinish times when using http over a proxy.
Deprecated as of 07/2014.
Please list the metric's owners. Add more owner tags as needed.
StartToFinish times when using https over a proxy.
pmeenan@chromium.org
This time is based on the User Timing spec and measures the time from
Navigation Timing navigationStart until the point where the page called
performance.mark().
pmeenan@chromium.org
This time is based on the User Timing spec and reports the time between two
arbitrary points defined by the page being loaded and directly matches the
measurement exposed by performance.measure().
xhwang@chromium.org
The availability status of Widevine CDM. In normal cases, this is reported
per render process if EME API is used. This is not reported if EME API is
not used. This could be reported multiple times per render process until
PLUGIN_AVAILABLE is reported (which should be a rare case).
tommycli@chromium.org
Aspect ratio of Flash plugins users click at least once. The aspect ratio is
multiplied by 100 and stored as a rounded integer.
tommycli@chromium.org
Height of Flash plugins users click at least once.
tommycli@chromium.org
Width of Flash plugins users click at least once.
tommycli@chromium.org
Collects the sizes of all loaded Flash plugin instances. This is for
determining the prevalence of tiny flash plugin instances.
Please list the metric's owners. Add more owner tags as needed.
Record usage of PPB_Flash.Navigate() Pepper API.
yzshen@chromium.org
thestig@chromium.org
Collects Flash usage data.
wfh@chromium.org
The plugin group of an NPAPI plugin that is no longer supported. Recorded
when the NPAPI removal infobar is shown for a plugin which is no longer
supported.
wfh@chromium.org
The plugin group of an NPAPI plugin that will be unsupported soon. Recorded
when the NPAPI removal infobar is shown after an NPAPI plugin first loads to
warn the user that NPAPI support for this plugin will be removed soon.
wfh@chromium.org
Records whether NPAPI plugins are supported by the platform, and if so,
whether they are enabled or disabled. Recorded once at browser startup.
tommycli@chromium.org
Record the initial decision of the Plugin Power Saver peripheral content
heuristic. For each plugin instance, this heuristic decides whether the
plugin instance is essential content or peripheral. All same-origin content
is essential. Cross-origin content is peripheral if it is small and not on
the origin whitelist.
tommycli@chromium.org
Record how many plugin object tags use poster param. This is recorded once
per plugin instance, and is currently restricted to Flash plugin instances.
tommycli@chromium.org
Record how many throttled plugins are unthrottled, and by what method.
xhwang@chromium.org
The error code of a PPAPI broker load failure.
xhwang@chromium.org
The result from an attempt to load a PPAPI broker.
xhwang@chromium.org
The error code of a PPAPI plugin load failure.
xhwang@chromium.org
The result from an attempt to load a PPAPI plugin.
gab@chromium.org
The time it took to complete a synchronous IPC made from the PPAPI process.
gab@chromium.org
Roundtrip times for synchronous IPC calls from the renderer to NPAPI plugin
processes.
bauerb@chromium.org
Error codes when parsing the built-in plugin list. Logged when the
PluginFinder singleton is created.
derat@chromium.org
The level of the backlight as a percentage when the user is on AC. Sampled
every 30 seconds.
derat@chromium.org
The level of the backlight as a percentage when the user is on battery.
Sampled every 30 seconds.
derat@chromium.org
Chrome OS battery charge health percentage. Sampled once when device starts
charging.
jeremy@chromium.org
The percentage of battery capacity used per hour relative to a full
battery. Reported once when the power adaptor is plugged back in after the
system is on battery power for more than 30 minutes. If at any point the
system is suspended or all Chrome renderers are closed the measurement is
not recorded. Anytime the user unplugs the power adaptor, a new measurement
will begin being recorded. Collection of this histogram only starts after 30
minutes of uptime at which point the clock starts (assuming the user is on
battery power at that point). The system will need to remain unplugged for
at least another 30 minutes in order for any measurement to be recorded.
Values are normalized to a percent per hour scale. This measurement is tied
tightly to hardware model/OS and is not comparable across different hardware
configurations.
derat@chromium.org
Chrome OS battery discharge rate in mW sampled every 30 seconds while the
device runs on battery.
jeremy@chromium.org
The percent of depleted battery capacity relative to a full battery over
the first 15 minutes after battery power collection information starts.
Collection of this histogram only starts after 30 minutes of uptime at which
point the clock starts (assuming the user is on battery power at that
point). The system will need to remain unplugged for at least another 15
minutes in order for any measurement to be recorded. Values are normalized
to a percent per hour scale. This measurement is tied tightly to hardware
model/OS and is not comparable across different hardware configurations.
jeremy@chromium.org
The percent of depleted battery capacity relative to a full battery over
the first 30 minutes after battery power collection information starts.
Collection of this histogram only starts after 30 minutes of uptime at which
point the clock starts (assuming the user is on battery power at that
point). The system will need to remain unplugged for at least another 30
minutes in order for any measurement to be recorded. Values are normalized
to a percent per hour scale. This measurement is tied tightly to hardware
model/OS and is not comparable across different hardware configurations.
jeremy@chromium.org
The percent of depleted battery capacity relative to a full battery over
the first 5 minutes after battery power collection information starts.
Collection of this histogram only starts after 30 minutes of uptime at which
point the clock starts (assuming the user is on battery power at that
point). The system will need to remain unplugged for at least another 5
minutes in order for any measurement to be recorded. Values are normalized
to a percent per hour scale. This measurement is tied tightly to hardware
model/OS and is not comparable across different hardware configurations.
derat@chromium.org
Chrome OS battery discharge rate in mW while the system was suspended,
sampled at resume. Only reported if the system was on battery power both
before suspending and after resuming, if the energy level didn't increase
while suspended (which would indicate that an AC adapter was connected), and
if the system was suspended for at least a minute.
derat@chromium.org
Counts the number of times we have read the battery status from sysfs and if
it gave us sensible values.
derat@chromium.org
Chrome OS remaining battery charge as percent of the maximum battery charge,
sampled at the end of a user session when the device is on AC.
derat@chromium.org
Chrome OS remaining battery charge as percent of the maximum battery charge,
sampled at the end of a user session when the device is on battery.
derat@chromium.org
Chrome OS remaining battery charge as percent of the maximum battery charge,
sampled at the start of a user session when the device is on AC.
derat@chromium.org
Chrome OS remaining battery charge as percent of the maximum battery charge,
sampled at the start of a user session when the device is on battery.
Deprecated as of 03/2012, no longer being generated by powerd.
derat@chromium.org
Chrome OS remaining battery charge as percent of the maximum battery charge
sampled when the device runs on battery.
derat@chromium.org
Chrome OS remaining battery charge as percent of the maximum battery charge,
sampled when charging starts.
Deprecated as of 03/2012, no longer being generated by powerd.
derat@chromium.org
Chrome OS remaining time to empty battery in minutes sampled when the device
runs on battery.
dianders@chromium.org
Chrome OS (Snow RO firmware 2695.90.0 only) number of 8K chunks that were
fixed (memory corruption corrected) for each suspend/resume cycle. Expect 0
around 97% of the time and a non-zero value around 3% of the time.
dianders@chromium.org
Chrome OS (Snow RO firmware 2695.90.0 only) number of 4-byte words that were
fixed (memory corruption corrected) for each suspend/resume cycle. Expect 0
around 97% of the time and a non-zero value around 3% of the time. Would be
exactly equal to Power.BitfixChunks if there were only one corrupted word in
each chunk but is sometimes several times higher.
Deprecated as of 5/2013. See Accel_BrightnessDown_F6 and
Accel_BrightnessUp_F7 user actions instead.
derat@chromium.org
Number of times the user has adjusted brightness up and down while running
on battery power.
Deprecated as of 5/2013. See Accel_BrightnessDown_F6 and
Accel_BrightnessUp_F7 user actions instead.
derat@chromium.org
Number of times the user has adjusted brightness up and down while running
on AC power.
Deprecated 11/2014 in issue 427057.
derat@chromium.org
External power supply type such as MAINS_CHARGER, USB_CHARGER,
UNCONFIRMED_SPRING_CHARGER, SAFE_SPRING_CHARGER. A sample is reported each
time a charger is connected to the device.
chirantan@chromium.org
The amount of time a system spent awake every time it woke up in dark
resume.
chirantan@chromium.org
The number of times a system woke up in dark resume in an hour. Note that
this value is scaled up or down to an hour based on the amount of time the
system spent in suspend. So if the system suspended for 20 minutes and woke
up 3 times, it would report a value of 9.
derat@chromium.org
The result of attempting to read an external display's brightness on Chrome
OS. A read attempt is made after successfully requesting the brightness (see
Power.ExternalBrightnessRequestResult).
derat@chromium.org
The result of requesting an external display's brightness on Chrome OS. A
request is sent when the user presses a brightness key and the current
brightness is not already cached. A successful request is followed shortly
thereafter by a read attempt (see Power.ExternalBrightnessReadResult).
derat@chromium.org
The result of attempting to change an external display's brightness on
Chrome OS. A request is sent when the user presses a brightness key and the
current brightness is either already cached or successfully loaded.
derat@chromium.org
The result of attempting to open an I2C device to control an external
display's brightness on Chrome OS. An attempt is made when a display is
connected to a device that lacks an internal display.
snanda@chromium.org
The time that the firmware took to resume the Chrome OS device from
suspend-to-RAM state when running on AC at pre-suspend time.
snanda@chromium.org
The time that the firmware took to resume the Chrome OS device from
suspend-to-RAM state when running on battery at pre-suspend time.
derat@chromium.org
Chrome OS user idle time since the screen dimmed sampled when the user
becomes active again if the device runs on AC.
derat@chromium.org
Chrome OS user idle time since the screen dimmed sampled when the user
becomes active again if the device runs on battery.
derat@chromium.org
Chrome OS user idle time since the screen turned off sampled when the user
becomes active again if the device runs on AC.
derat@chromium.org
Chrome OS user idle time since the screen turned off sampled when the user
becomes active again if the device runs on battery.
derat@chromium.org
Chrome OS user idle time sampled when the user becomes active again if the
device runs on AC.
derat@chromium.org
Chrome OS user idle time sampled when the user becomes active again if the
device runs on battery.
snanda@chromium.org
The time that the kernel took to resume the Chrome OS device from
suspend-to-RAM state when running on AC at pre-suspend time.
snanda@chromium.org
The time that the kernel took to resume the Chrome OS device from
suspend-to-RAM state when running on battery at pre-suspend time.
snanda@chromium.org
The time that the kernel took to suspend-to-RAM the Chrome OS device when
running on AC.
snanda@chromium.org
The time that the kernel took to suspend-to-RAM the Chrome OS device when
running on battery.
derat@chromium.org
The level of the keyboard backlight as a percentage. Sampled every 30
seconds.
derat@chromium.org
The length of time, in seconds, that a user spent in a single session.
Values for this metric are clamped to 12 hours, so the last bucket should be
considered to be including all metrics above 12 hours.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, when sync
invalidator listens to on_application_active events. Values for this metric
are per session, i.e. from battery level at application entering foreground
to returning to background, and normalized to an hourly average consumption.
This is an iOS only measurement. Due to how iOS reports battery levels, it
is likely to see many readings of 0.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, for other
sync invalidator methods. Values for this metric are per session, i.e. from
battery level at application entering foreground to returning to background,
and normalized to an hourly average consumption. This is an iOS only
measurement. Due to how iOS reports battery levels, it is likely to see many
readings of 0.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, when sync
invalidator uses peer-to-peer notifications. Values for this metric are per
session, i.e. from battery level at application entering foreground to
returning to background, and normalized to an hourly average consumption.
This is an iOS only measurement. Due to how iOS reports battery levels, it
is likely to see many readings of 0.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, when sync
invalidator uses server-based non-blocking invalidator. Values for this
metric are per session, i.e. from battery level at application entering
foreground to returning to background, and normalized to an hourly average
consumption. This is an iOS only measurement. Due to how iOS reports battery
levels, it is likely to see many readings of 0.
derat@chromium.org
The number of times that the Automatic Light Sensor (ALS) adjusted the
brightness during a session. Values for this metric are clamped to 10k
count, so the last bucket should be considered to be including all metrics
above 10k.
derat@chromium.org
The number of user sessions that occured since the last time that the device
was charged. Values for this metric are clamped at 10k, so the last bucket
should be considered to include all metrics about 10k.
derat@chromium.org
The amount of time between the user pressing the power button and Chrome
acknowledging the button-down event on Chrome OS. Values for this metric are
capped to two seconds.
derat@chromium.org
The amount of time between the user pressing the power button and releasing
it on Chrome OS.
Deprecated Feb 2014 by Power.SuspendAttemptsBeforeCancel and
Power.SuspendAttemptsBeforeSuccess.
derat@chromium.org
The number of times Chrome OS retried suspend due to previous failure.
derat@chromium.org
The reason for the Chrome OS power manager shutting down or rebooting the
system.
derat@chromium.org
snanda@chromium.org
The number of suspend attempts on Chrome OS. Samples are reported before
each attempt, so this histogram may include cases where the system crashed
instead of suspending.
derat@chromium.org
snanda@chromium.org
The number of suspend attempts performed for a single suspend request (e.g.
triggered by the lid being closed) that was eventually canceled on Chrome
OS. This also includes requests that were canceled due to the system
eventually shutting down due to repeated suspend failures.
derat@chromium.org
snanda@chromium.org
The number of suspend attempts performed for a single suspend request (e.g.
triggered by the lid being closed) that eventually succeeded on Chrome OS.
This includes the successful attempt.
derat@chromium.org
snanda@chromium.org
The results of suspend attempts on Chrome OS. Samples are reported after
each attempt.
Deprecated Jan 2014 by Power.SuspendAttempt and Power.SuspendResult.
derat@chromium.org
Chrome OS suspend status.
No longer sent.
derat@chromium.org
The percentage of aborted fan attempts out of total fan attempts per
session, where an abort is due to hysteresis. This value is computed from
boot and sent when powerd starts and then every 15 minutes afterwards.
No longer sent.
derat@chromium.org
The percentage of fan trip point passes that are more than one trip point.
This value is computed from boot and sent when powerd starts and then every
15 minutes afterwards.
derat@chromium.org
snanda@chromium.org
Chrome OS time in minutes spent in suspend-to-RAM mode sampled at boot
(i.e., the device most likely ran out of battery while in suspend).
derat@chromium.org
snanda@chromium.org
Chrome OS time in minutes spent in suspend-to-RAM mode sampled at resume.
derat@chromium.org
The number of times that the user adjusted the brightness during a session
when on AC. Values for this metric are clamped to 10k count, so the last
bucket should be considered to be including all metrics above 10k.
derat@chromium.org
The number of times that the user adjusted the brightness during a session
when on battery. Values for this metric are clamped to 10k count, so the
last bucket should be considered to be including all metrics above 10k.
bengr@chromium.org
The number of bytes that were downloaded over the network for HTTP/HTTPS
fetches that were not motivated by precaching. Logged per-request.
bengr@chromium.org
The number of bytes that were downloaded because of precaching. Logged
per-request.
bengr@chromium.org
The number of bytes during user browsing that were served from the cache,
but would have been downloaded over a network if precaching was disabled.
Logged per-request.
rkaplow@chromium.org
The amount of time that elapsed during CreateProfilePrefs.
davidben@chromium.org
tburkard@chromium.org
Time from when a prerendered page is abandoned to when it is first used due
to user navigation. If the page is swapped before begin abandoned, a zero is
recorded.
Deprecated March 13 2015.
tburkard@chromium.org
Enumeration of what types of cookies were sent for a prerender.
Deprecated March 13 2015.
tburkard@chromium.org
Enumeration of what cookie actions a prerender caused.
Deprecated Dec 12 2014.
Enumeration of what events related to prerendering have occurred.
deprecated May 10 2012
Please list the metric's owners. Add more owner tags as needed.
Hover Event counts for prerendering.
tburkard@chromium.org
Final status for prerender pages - either success, or why it was canceled.
tburkard@chromium.org
Final status for prerender pages - either success, or why it was canceled.
This is for the MatchComplete set of pages (including some pages that were
not actually prerendered), to match the control group.
Deprecated Jan 14 2014.
Please list the metric's owners. Add more owner tags as needed.
For prerenders that are swapped in, the percentage of pixels that is already
final at swap-in time compared to when the spinner stops.
deprecated May 10 2012
Please list the metric's owners. Add more owner tags as needed.
Duration that a user hovers a link before clicking on it.
This is recorded for all pages loaded in a session.
deprecated May 10 2012
Please list the metric's owners. Add more owner tags as needed.
Duration that the mouse pointer hovers on a link before the mouse pointer
moves off of it.
This is recorded for all pages loaded in a session.
Deprecated April 2015
tburkard@chromium.org
Enumeration of what events related to the local predictor have occurred
Deprecated April 2015
tburkard@chromium.org
Time to perform the LoggedIn Lookup for the local predictor. This operation
checks whether a user his likely logged into a page that we would like to
prerender.
Deprecated April 2015
tburkard@chromium.org
The PrerenderLocalPredictor uses local browsing history and the prerender
service to predict pages likely visited soon. Some of these URLs are
prefetched. When such prefetched likely next pages are visited, this
histogram records the PLT for such pages. In particular, this also happens
if prefetch is actually disabled, allowing (by pivoting on whether or not
prefetch is enabled) to compare the effect of prefetch on PLT.
Deprecated April 2015
tburkard@chromium.org
Time to perform the Service Lookup for the local predictor. This operation
queries a Google service to obtain pages to prerender, as well as whether
prerender candidate pages are likely safe for prerendering.
Deprecated April 2015
tburkard@chromium.org
Time from when a prerendered page is started to when it is first used due to
user navigation. If the page is never used, it is not included in this
histogram. This only refers to prerenders based on the local predictor.
Deprecated April 2015
tburkard@chromium.org
Time to perform the URL Lookup for the local predictor. This operation
retrieves from the user's local browsing history the URLs corresponding to
URLIDs.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
The transition type for each new visit as recorded in the local visits
database.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Size of the local visits database (number of entries).
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Enumeration of what events related to local visits have occurred
Deprecated as of 10/2013.
Please list the metric's owners. Add more owner tags as needed.
Previous version of the Prerender.PagespeedHeader.* histograms.
Deprecated May 13th 2014, use Prerender.NetworkBytesTotalForProfile instead.
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead). Reported on event of a PrerenderContents
deletion. Includes prerender bytes. Bytes are only counted when
prerendering is enabled and not in a control group. The sum of the
distribution for a single user represents all of that user's network
transfers for resource for that time period while prerendering was enabled.
Deprecated May 13th 2014, use Prerender.NetworkBytes.Used instead.
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been
used).
Deprecated May 13th 2014, use Prerender.NetworkBytes.Wasted instead.
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead) for a prerender that was not used.
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead). Reported on event of a PrerenderContents
deletion. Includes prerender bytes. Bytes are only counted when
prerendering is enabled and not in a control group. The sum of the
distribution for a single user represents all of that user's network
transfers for resource for that time period while prerendering was enabled.
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been
used).
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead) for a prerender that was not used.
tburkard@chromium.org
A boolean that indicates whether the Omnibox navigation being committed
could have been prerendered by the Omnibox Prerender system. This provides
an upper bound for Prerender.OmniboxNavigationsUsedPrerenderCount and allows
the potential for Omnibox Prerendering coverage to be understood. If Omnibox
Prerendering is disabled, this histogram will register a 'false' entry. The
total count is the equivalent of the deprecated
NetworkActionPredictor.NavigationCount histogram.
tburkard@chromium.org
The number of navigations that use a prerender initiated from the Omnibox.
The count is incremented when the Prerendered tab is swapped in if the
Prerender was initiated by the Omnibox, which obviously requires
Prerendering from the Omnibox to be enabled.
tburkard@chromium.org
The number of prerenders initiated from the Omnibox. This is incremented
when the NetworkActionPredictor suggests Prerendering as an optimal strategy
given the text the user has entered and the Autocomplete suggestion
currently selected. It is only incremented if Prerendering from the Omnibox
is enabled.
tburkard@chromium.org
The number of responses received bucketed into the range [0,4]: bucket 0 is
the total number of responses received; bucket 1 is the number of responses
received with an X-Mod-Pagespeed header [indicating a mod_pagespeed server];
bucket 2 is the number of responses received with an X-Page-Speed header and
a header value in the X-Mod-Pagespeed format (a.b.c.d-e) [indicating an
ngx_pagespeed server]; bucket 3 is the number of responses received with an
X-Page-Speed header and a header value in the PageSpeed Service format
(a_b_c) [indicating a PSS server]; and bucket 4 is the number of responses
received with an X-Page-Speed header and a header value in neither of the
preceding formats [indicating some other server; IISpeed is the only known
one at this stage].
tburkard@chromium.org
The number of responses received that either have an X-Mod-Pagespeed header
or have an X-Page-Speed header with a value in the X-Mod-Pagespeed format
(a.b.c.d-e), bucketed into the range [1,99]: bucket 1 is for header values
that aren't in the a.b.c.d-e format, the remaining buckets are an encoding
of the value: 2 + 2 * (max(c, 10) - 10) + (d > 1 ? 1 : 0). The rationale
is that 'c' is incremented with each new release and 'd' is initially 0 but
is incremented for each patch to a release.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Types of pages rendered.
deprecated March 30, 2015
tburkard@chromium.org
Indicates whether the user has ever visited (in the past) a URL for which a
prerender is launched.
Deprecated 03/24/11. Replaced by
Prerender.PerceivedPLT_ContentPrefetchPrerenderControl.
Please list the metric's owners. Add more owner tags as needed.
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This particular histogram is for all page loads for users who do not have
prerendering enabled.
Deprecated 03/24/11. Replaced by
Prerender.PerceivedPLTMatched_ContentPrefetchPrerenderControl.
Please list the metric's owners. Add more owner tags as needed.
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This particular histogram is only for pages that would have been prerendered
if the user had prerender enabled.
Deprecated 03/24/11. Replaced by
Prerender.PerceivedPLTMatched_ContentPrefetchPrerender.
Please list the metric's owners. Add more owner tags as needed.
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This particular histogram is for all prerendered page loads for users who
have prerender enabled.
Deprecated 03/24/11. Replaced by
Prerender.PerceivedPLT_ContentPrefetchPrerender.
Please list the metric's owners. Add more owner tags as needed.
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This particular histogram is for all page loads for users who have
prerendering enabled.
Deprecated 03/24/11. Replaced by
Prerender.PerceivedPLTWindowed_ContentPrefetchPrerenderControl.
Please list the metric's owners. Add more owner tags as needed.
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This particular histogram is for all page loads within 30 seconds after a
prefetch tag is seen for users who do not have prerendering enabled.
Deprecated 03/24/11. Replaced by
Prerender.PerceivedPLTWindowed_ContentPrefetchPrerender.
Please list the metric's owners. Add more owner tags as needed.
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load pre navigation.
This particular histogram is for all page loads within 30 seconds after a
prefetch tag is seen for users who have prerendering enabled.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for all pages loaded in a session.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for the first page load completing immediately after a
prerender.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
"FirstAfterMiss" means the first pageload after a prerender miss.
There are two types: Any, and Non-overlapping. The latter only applies to
page loads initiated after the prerender. This variable records cases where
only Any triggered.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
"FirstAfterMiss" means the first pageload after a prerender miss.
There are two types: Any, and Non-overlapping. The latter only applies to
page loads initiated after the prerender. This variable records cases where
both triggered.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for the first page load completing immediately after a
prerender, but which has also started after the prerender has been
initiated.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
"FirstAfterMiss" means the first pageload after a prerender miss.
There are two types: Any, and Non-overlapping. The latter only applies to
page loads initiated after the prerender. This variable records cases where
only Non-overlapping triggered.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded only for prerendered pages, or for pages which would have
been prerendered in the control case.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded only for prerendered pages, or for pages which would have
been prerendered in the control case.
In MatchedComplete, the prerender group also contains cancelled prerenders,
so as to produce a perfect match of page views attributed this group in the
prerender group with those attributed to this group in the control group.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for all page loads which happen within 30 seconds after a
prefetch tag is observed.
tburkard@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for all page loads which happen within 30 seconds after a
prefetch tag is observed and which do not correspond to a prerender tag.
tburkard@chromium.org
For prerenders that are swapped in, the percentage of the time from load
start until the onload event fires that has elapsed at the time of the
swapin.
tburkard@chromium.org
How long the cleanup portion of PrerenderManager::PeriodicCleanup takes, to
measure jank.
tburkard@chromium.org
How long the resource check portion of PrerenderManager::PeriodicCleanup
takes, to measure jank.
tburkard@chromium.org
After launching a prerender, how many simultanious prerenders are recorded
as running, out of a maximum of three.
tburkard@chromium.org
For prerenders that finish loading before they are ever swapped in, their
page load time until the onload event fires.
tburkard@chromium.org
The number of sessions that have at least X successful prerenders.
tburkard@chromium.org
For each prerender link added to a document, records the rel types present
on the link element.
tburkard@chromium.org
For each prerender in a document which starts prerendering, records the rel
types present on the link element.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
This is the time from when a prerendered page finishes loading to when it is
displayed, as measured by the renderer process. When a page is displayed
before it finishes loading, no value is recorded in this histogram.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Perceived load time of a page, as measured by the renderer process. For
non-prerendered pages, this is just BeginToFinish. For displayed prerendered
pages, this is the time from when the prerendered page is moved into a
TabContents until finish. "Finish" == after onload() and all
resources are loaded. Note that this is 0 if the loading finishes before the
page is moved into a TabContents.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Perceived load time of a prerendered page that is displayed, as measured by
the renderer process. This is the time from when the prerendered page is
moved into a TabContents until finish. "Finish" == after onload()
and all resources are loaded. Note that this is 0 if the loading finishes
before the page is moved into a TabContents.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
The time elapsed between when the prerendering of a page starts and when the
page is displayed, as measured by the renderer process. Prerendered pages
discarded without being displayed are excluded from this count.
tburkard@chromium.org
The detailed reason why a prerender is canceled with
FINAL_STATUS_UNSUPPORTED_SCHEME
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Enumeration of how prerender was used per session.
Deprecated Dec 12 2014.
tburkard@chromium.org
Time to perform the session storage namespace merge.
Deprecated April 2015
tburkard@chromium.org
For simulated local browsing prerendering, the baseline PLT of pages without
any prerendering for pages that would be prerendered.
Deprecated April 2015
tburkard@chromium.org
For simulated local browsing prerendering, the estimated PLT of pages with
prerendering enabled for pages that would be prerendered.
tburkard@chromium.org
A boolean that indicates how often we suppress a dialog from a tab when
swapping it with a prerender.
tburkard@chromium.org
A boolean that indicates how often we fail to delete an old prerendered tab
before the timeout.
Deprecated April 2015
tburkard@chromium.org
Enumeration of what events related to the TabHelper class have occurred.
tburkard@chromium.org
Time between subsequent prerender requests.
tburkard@chromium.org
The time elapsed between the most recent visit to a URL and when an
attempted prerender of the same URL is cancelled with
FINAL_STATUS_RECENTLY_VISITED.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Duration that a user hovers a link before clicking on it.
deprecated Nov 16 2012. See Prerender.TimeUntilUsed2, which has a larger
range.
Please list the metric's owners. Add more owner tags as needed.
Time from when a prerendered page is started to when it is first used due to
user navigation. If the page is never used, it is not included in this
histogram.
tburkard@chromium.org
Time from when a prerendered page is started to when it is first used due to
user navigation. If the page is never used, it is not included in this
histogram.
vitalybuka@chromium.org
Count of events in PrinterService on ChromeOS related to USB printers.
vitalybuka@chromium.org
Actions performed by the user when the print destination search widget is
shown to the user.
vitalybuka@chromium.org
Count of font file formats embeeded in print preview PDFs. These numbers are
biased by what the platforms supports in terms of detection.
vitalybuka@chromium.org
Actions performed by the user when the Google Cloud Print add-printers
promotion is shown to the user.
vitalybuka@chromium.org
Time from when print preview is intiated until the intial preview is sent to
the preview tab for rendering.
vitalybuka@chromium.org
Time from when print preview is intiated until the preview PDF generation is
started.
vitalybuka@chromium.org
Count the number of requests received to show the manage printers dialog.
vitalybuka@chromium.org
Count the total number of printers shown in destination drop down list.
vitalybuka@chromium.org
The page count of the initial print preview, a.k.a. the total number of
pages in documents to be printed.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to a cloud
printer.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to a cloud
printer using web dialog.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to PDF.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to a
printer.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to an
extension printer (using printerProvider API).
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to a privet
printer.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed using
system dialog.
vitalybuka@chromium.org
Print preview events.
vitalybuka@chromium.org
Track the popularity of print settings. (Settings when printing to PDF are
excluded from this statistic.)
alekseys@chromium.org
vitalybuka@chromium.org
Actions performed by the user interacting with print settings UI elements.
vitalybuka@chromium.org
The number of times regenerate preview requests received before the user
clicked the cancel button.
vitalybuka@chromium.org
The number of times regenerate preview requests received before the first
preview data is availible.
vitalybuka@chromium.org
The number of times regenerate preview requests received before the user
clicked the print button.
vitalybuka@chromium.org
Time taken to render and generate PDF for print preview. (Includes time to
reflow the page back to normal, but not the time to reflow the page to
prepare for printing.)
vitalybuka@chromium.org
Time taken to render and generate PDF for print preview divided by the
number of pages. (Includes time to reflow the page back to normal, but not
the time to reflow the page to prepare for printing.)
vitalybuka@chromium.org
Count how frequently a set of pre-defined print preview errors occur.
vitalybuka@chromium.org
Time taken to render each PDF page for print preview.
vitalybuka@chromium.org
Time taken to render to PDF for print preview.
vitalybuka@chromium.org
Action taken by the user in the preview tab such as print, cancel, print to
pdf and show advanced print settings dialog.
shrikant@chromium.org
Errors returned while launching sandboxed process on Windows. For decoding
error code please refer to http://goo.gl/fJJiAv.
shrikant@chromium.org
Errors returned while launching lowbox enabled sandboxed process on Windows.
For decoding error code please refer to http://goo.gl/fJJiAv.
bcwhite@chromium.org
rlp@chromium.org
The frequency of ways that new user profiles are added.
aruslan@chromium.org
Track user interactions that can be performed in the Android account
management menu.
Please list the metric's owners. Add more owner tags as needed.
The number of installed apps when a profile is opened.
bcwhite@chromium.org
Counts of authorization results when trying to open a locked profile from
the User Manager.
rlp@chromium.org
The frequency of selection of each avatar.
Please list the metric's owners. Add more owner tags as needed.
Size of the bookmarks database.
Please list the metric's owners. Add more owner tags as needed.
Size of the cookies database.
rkaplow@chromium.org
Length of time to setup profile.
rkaplow@chromium.org
The amount of time that elapsed during the CreateBrowserContextServices call
within OnPrefsLoaded.
rkaplow@chromium.org
The amount of time that elapsed during ProfileManager::CreateProfileHelper.
This is called when a profile is created synchronously (usually at startup).
pam@chromium.org
rlp@chromium.org
Result (final status) when creating a new profile.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Back-end time elapsed while creating a new profile. The max is 30 seconds,
when an external timeout was applied.
Deprecated as of 8/2013.
Please list the metric's owners. Add more owner tags as needed.
Time elapsed before the user decided to cancel creation of a new profile.
Since only managed-user profile creation can be canceled, this time comes
from managed-user registration. The max is 30 seconds, when an external
timeout was applied.
pam@chromium.org
Time elapsed from when the handler received the message that a user clicked
'Create' until the user decided to cancel creation of a new profile. Since
only managed-user profile creation can be canceled, this time comes from
managed-user registration.
pam@chromium.org
Time elapsed from when the handler received the message that a user clicked
'Create' until the creation either failed with a local error (see
Profile.CreateResult), was canceled (also recorded in
Profile.CreateTimeCanceledNoTimeout), or completed successfully.
mlerman@chromium.org
This histogram tracks the deletion of the profile. This tracks when the
cleanup actually takes place, not the UI interaction. The parameter
indicates if the profile was signed in or not; true means the profile was
signed in, false means the profile was not signed in.
mlerman@chromium.org
anthonyvd@chromium.org
This histogram tracks which UI screen was used to initiate and confirm the
deletion of a profile. This does not track when the profile is actually
deleted, which is an asynchronous process that happens later.
mlerman@chromium.org
Track user interactions that can be performed in the user menu and user
manager. The origin of the action, whether the an interaction in the content
area or some other source, is noted in the histogram suffix.
Please list the metric's owners. Add more owner tags as needed.
Size of the extension cookies database.
Please list the metric's owners. Add more owner tags as needed.
Size of the favicons database.
Deprecated 02/2015. Profile.CreateAndInitializeProfile is more useful.
rkaplow@chromium.org
Length of time to retrieve profile.
hajimehoshi@chromium.org
kouhei@chromium.org
Size of the history database.
rlp@chromium.org
Number of times users launch a browser window from either a primary or
secondary profile (i.e., each time a browser window is opened we log which
type of profile it belongs to).
mlerman@chromium.org
How long locked profiles have been locked for. This is logged each time any
profile is loaded. Note that this does not track the total time the profile
was locked, but rather the span from when the profile was locked to when the
measurement takes place.
bcwhite@chromium.org
rlp@chromium.org
Counts of users added and deleted. Percentages are not meaningful. Please
look at the ratio of the counts/percentages.
mlerman@chromium.org
Tracks user interactions with the 'Not You?' bubble that users can navigate
to from the Upgrade bubble after upgrade to the New Avatar Menu.
mlerman@chromium.org
Tracks user interactions with the signin bubble that appears in the New
Avatar Menu upon signin. This bubble appears after the user signs in using
the Inline Signin flow.
mlerman@chromium.org
Tracks user interactions with the bubble that appears for users in the new
avatar menu after upgrade.
rkaplow@chromium.org
The amount of time that elapsed during the Notify() of
NOTIFICATION_PROFILE_CREATED during ProfileImpl::DoFinalInit().
mlerman@chromium.org
Counts the number of Google-managed accounts linked to a profile. This may
be counted multiple times per profile. Please review with the "Show
user counts" option enabled on the dashboard.
pam@chromium.org
Counts the number of locally managed profiles on a user's machine at least
every 24 hours while Chrome is running, among cases with at least one
profile. Always de-dupe the results with Show User Counts.
bcwhite@chromium.org
rlp@chromium.org
Counts the number of profiles on a user's machine at least every 24 hours
while Chrome is running. Always de-dupe the results with Show User Counts.
Deprecated 2013-04-09. No longer tracked. See Profile.NumberOfProfiles.
bcwhite@chromium.org
rlp@chromium.org
Counts the number of profiles on a user's machine whenever a profile is
added or deleted.
Deprecated; replaced by Profile.NumberOfProfiles on 2013-04-09. Data are
suspect, especially after 2012-02-24: see https://crbug.com/189213.
bcwhite@chromium.org
rlp@chromium.org
Counts the number of profiles on a user's machine when Chrome starts up.
mlerman@chromium.org
Counts the type GAIA authentication errors on a user's machine when Chrome
starts up. The types of errors are broken down in Signin.AuthError.
bcwhite@chromium.org
rlp@chromium.org
Counts the number of signed-in profiles on a user's machine at least every
24 hours while Chrome is running. Always de-dupe the results with Show User
Counts.
Deprecated; replaced by Profile.NumberOfSignedInProfiles on 2013-04-09.
bcwhite@chromium.org
rlp@chromium.org
Counts the number of profiles that are signed in to Chrome when Chrome
starts up.
mlerman@chromium.org
Counts the number of signed-in profiles that are using the GAIA image as the
avatar icon. This is counted at least every 24 hours while Chrome is
running, so always de-dupe the results with Show User Counts.
anthonyvd@chromium.org
Counts the number of times profiles were switched in a browser session. This
value is incremented when a profile is switched to and the result is logged
during shutdown.
mlerman@chromium.org
Counts the number of profiles unused within the past 28 days on a user's
machine. This is counts at least every 24 hours while Chrome is running, so
always de-dupe the results with Show User Counts.
rkaplow@chromium.org
The amount of time that elapsed during ProfileImpl::OnLocaleReady. This
happens once after profile was loaded.
Deprecated 04/2015, and replaced by Profile.OnLocaleReadyTime.
rkaplow@chromium.org
The amount of time that elapsed during ProfileImpl::OnPrefsLoaded.
Deprecated because it did not present the information clearly.
Please list the metric's owners. Add more owner tags as needed.
The frequency of ways that the profiles are opened.
bcwhite@chromium.org
rlp@chromium.org
The frequency with which the user opens the different profile menus or
switches profiles. For the open statistics, this does not mean the user
necessarily opened a profile after clicking. The switch statistics indicate
how often and how the user switches profiles. They are provided together for
comparison of how often the user actually switches after opening the avatar
bubble menu.
pam@chromium.org
Tracks the percentage (0-100) of profiles that are locally managed, recorded
when Chrome starts up.
tnagel@chromium.org
The error with the current user profile that caused an error dialog to be
shown. This dialog is shown usually when there is some sort of corruption in
the user's profile data.
rkaplow@chromium.org
The amount of time that elapsed during the ProfileImpl::DoFinalInit().
Please list the metric's owners. Add more owner tags as needed.
The error code generated in the final step (registration step) of creating a
new supervised profile.
Please list the metric's owners. Add more owner tags as needed.
The error code generated in the final step (registration step) of importing
a supervised profile.
Please list the metric's owners. Add more owner tags as needed.
Time elapsed from when the handler received the message that a user clicked
'Create' to create a new supervised user profile until the registration ends
either successfully or with a failure (both recorded in
Profile.SupervisedProfileCreateResult).
Please list the metric's owners. Add more owner tags as needed.
Time elapsed from when the handler received the message that a user clicked
'Import supervised user' until the registration ends either successfully or
with a failure (both recorded in Profile.SupervisedProfileImportResult).
Please list the metric's owners. Add more owner tags as needed.
Counts of when users switch to using their GAIA photo instead of an avatar
icon or the opposite when they switch back to an avatar icon instead of
their GAIA photo.
Deprecated because it did not present the information clearly.
Please list the metric's owners. Add more owner tags as needed.
Activity of the user with regards to sync.
Please list the metric's owners. Add more owner tags as needed.
Number of times and ways the user customized the sync options of their
profile. Percentages are not meaningful. To determine percentages, take the
count of a given action over the count of number of customizations.
rpop@google.com
Number of times the user signed into sync from original or secondary
profile.
Please list the metric's owners. Add more owner tags as needed.
Size of the thumbnails database.
mlerman@chromium.org
Time required to open the UserManager, from when it started to show until
when its javascript started executing.
Please list the metric's owners. Add more owner tags as needed.
Size of the top sites database.
Please list the metric's owners. Add more owner tags as needed.
Total size of all history databases.
Please list the metric's owners. Add more owner tags as needed.
Total size of the profile data (excluding sub-folders).
rlp@chromium.org
Times a profile name and/or avatar was updated.
Deprecated 8/2014. Upgrade Promotional UI removed.
mlerman@chromium.org
The process which leads a user to enroll in New Profile Management. Also
tracks if the user chooses to opt out, and tutorials which guide the user
into New Profile Management.
anthonyvd@chromium.org
Whether the active profile is a guest profile when -validateMenuItem in the
ProfileMenuController gets an invalid value for the current profile's index.
anthonyvd@chromium.org
The count of profiles in the avatar menu when -validateMenuItem in the
ProfileMenuController gets an invalid value for the current profile's index.
anthonyvd@chromium.org
The selector associated with the menu item when -validateMenuItem in the
ProfileMenuController gets an invalid value for the current profile's index.
Please list the metric's owners. Add more owner tags as needed.
Size of the visited links database.
Please list the metric's owners. Add more owner tags as needed.
Size of the web data database.
engedy@chromium.org
vasilii@chromium.org
Signifies if the user selected "Send feedback" checkbox in the
Reset Profile dialog.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Errors that Protector detects about default search provider in Web Data.
Reported once when Web Data is loaded.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
Errors that Protector detects about protected settings in Preferences.
Reported once when profile is loaded.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
When the default search provider setting is changed outside of Chrome, which
is detected by the Protector, this histogram reports the new setting.
Deprecated 8/2013. No longer tracked.
Please list the metric's owners. Add more owner tags as needed.
When the startup settings are changed outside of Chrome, which is detected
by the Protector, this histogram reports the new setting.
johnme@google.com
mvanouwerkerk@google.com
When a Service Worker receives a push message, this records whether it was
successful, or otherwise the type of error encountered.
johnme@google.com
mvanouwerkerk@google.com
When a webpage asks for details about its current push messaging
registration, this records whether the request is successful, or otherwise
the type of error encountered.
johnme@google.com
mvanouwerkerk@google.com
When a webpage registers for push messaging, this records whether the
request is successful, or otherwise the type of error encountered.
johnme@google.com
mvanouwerkerk@google.com
When a webpage unregisters from push messaging, this records whether the
request is successful, or otherwise the type of error encountered.
johnme@google.com
mvanouwerkerk@google.com
When a Service Worker receives a push message, this records whether it
showed user-visible UX (like a notification), or whether we showed a forced
notification on its behalf.
dskelton@google.com
Records the number of cells that contain formatting data in the default
worksheet when a comma separated value spreadsheet is opened.
dskelton@google.com
Records the number of non-empty cells in the default worksheet when a comma
separated value spreadsheet is opened.
dskelton@google.com
Records the number of worksheets when a comma separated value spreadsheet is
opened.
joshwoodward@google.com
Records the page count when a compound binary format document is opened.
joshwoodward@google.com
Records the paragraph count when a compound binary format document is
opened.
joshwoodward@google.com
Records the section count when a compound binary format document is opened.
joshwoodward@google.com
Records the page count when an OOXML format document is opened.
joshwoodward@google.com
Records the paragraph count when an OOXML format document is opened.
joshwoodward@google.com
Records the section count when an OOXML format document is opened.
joshwoodward@google.com
Records the various different error types encountered when opening and
reading MS Office file formats in the Quickoffice viewer. These range from
Nacl crashes and uncaught javascript exceptions to document errors inside
Quickoffice Web Toolkit (eg QOWT). The errors are recorded against the file
format in which they occurred.
joshwoodward@google.com
Records the various different file types supported by Quickoffice (like MS
Word, Excel, Powerpoint files) when they opened in the browser to measure
which file formats are most popular.
joshwoodward@google.com
Records the number of slide masters when a compound binary format
presentation is opened.
joshwoodward@google.com
Records the slide count when a compound binary format presentation is
opened.
joshwoodward@google.com
Records the number of slide masters when an OOXML format presentation is
opened.
joshwoodward@google.com
Records the slide count when an OOXML format presentation is opened.
joshwoodward@google.com
Records the number of cells that contain formatting data in the default
worksheet when a compound binary format spreadsheet is opened.
joshwoodward@google.com
Records the number of non-empty cells in the default worksheet when a
compound binary format spreadsheet is opened.
joshwoodward@google.com
Records the number of worksheets when a compound binary format spreadsheet
is opened.
joshwoodward@google.com
Records the number of cells that contain formatting data in the default
worksheet when an OOXML format spreadsheet is opened.
joshwoodward@google.com
Records the number of non-empty cells when an OOXML format spreadsheet is
opened.
joshwoodward@google.com
Records the number of worksheets when an OOXML format spreadsheet is opened.
tzik@chromium.org
Difference between acceptable lower limit of diskspace and actual free
diskspace at beginning of an eviction round.
tzik@chromium.org
Number of errors on evicting origin by QuotaTemporaryStorageEvictor in an
hour.
tzik@chromium.org
Number of errors on getting usage and quota by QuotaTemporaryStorageEvictor
in an hour.
tzik@chromium.org
Amount of usage used by evicted origins in an eviction round.
tzik@chromium.org
Number of evicted origins in an hour.
tzik@chromium.org
Number of eviction rounds in an hour.
tzik@chromium.org
Amount of free disk space for profile directory.
tzik@chromium.org
Global usage of persistent storage.
tzik@chromium.org
Global usage of temporary storage.
tzik@chromium.org
Initial quota for global temporary storage.
tzik@chromium.org
Number of evicted origins per round.
tzik@chromium.org
Number of origins using persistent storage.
tzik@chromium.org
Number of protected origins using persistent storage.
tzik@chromium.org
Number of protected origins using temporary storage.
tzik@chromium.org
Number of origins using temporary storage.
tzik@chromium.org
Number of unlimited origins using persistent storage.
tzik@chromium.org
Number of unlimited origins using temporary storage.
tzik@chromium.org
Number of skipped eviction rounds in an hour.
tzik@chromium.org
Time between two consecutive active eviction rounds.
tzik@chromium.org
Time spent to an eviction round.
tzik@chromium.org
Overage of the temporary global storage usage at beginning of an eviction
round.
holte@chromium.org
Counts how often daily interval events were fired.
holte@chromium.org
For each Rappor log that is discarded, the reason that it was discarded.
holte@chromium.org
Net error codes for failed Rappor uploads.
Removed 2015/05/05.
holte@chromium.org
Rappor.DailyEvent.IntervalType reported under the wrong name.
holte@chromium.org
Success or errors encountered when loading Rappor cohort pref.
holte@chromium.org
Success or errors encountered when loading Rappor secret pref.
holte@chromium.org
For each upload to the Rappor server, log the response received from the
server.
robertshield@chromium.org
Log each stage of a recovery component event.
kinuko@chromium.org
Maximum number of workers (SharedWorker or ServiceWorker) that are
simultaneously hosted in a single renderer process. Recorded when the
renderer process host is being destructed.
Please list the metric's owners. Add more owner tags as needed.
Keeps track of the number of main frame scrolls with an accelerated fixed
root background, the number of main frame scrolls with an unaccelerated
fixed root background, and the total number of main frame scrolls.
hartmanng@chromium.org
Total count of the number of RenderLayers which are scrollable areas, need
to be promoted to stacking containers, and will use composited scrolling.
Each bucket is sampled at most once per RenderLayer, when the RenderLayer
first becomes scrollable, first needs to become a stacking container, and
first uses composited scrolling, respectively.
Please list the metric's owners. Add more owner tags as needed.
The time it takes for the compositor to draw a frame.
Please list the metric's owners. Add more owner tags as needed.
The amount by which the compositor's draw duration was overestimated in a
particular frame (0 if the duration was perfectly predicted or
underestimated).
Please list the metric's owners. Add more owner tags as needed.
The amount by which the compositor's draw duration was underestimated in a
particular frame (0 if the duration was perfectly predicted or
overestimated).
Please list the metric's owners. Add more owner tags as needed.
The delay between the compositor submitting a command to the GPU and that
command executing on the GPU. This delay is measured once per frame.
Please list the metric's owners. Add more owner tags as needed.
The amount by which GPU latency was overestimated in a particular frame (0
if the latency was perfectly predicted or underestimated).
Please list the metric's owners. Add more owner tags as needed.
The amount by which GPU latency was underestimated in a particular frame (0
if the latency was perfectly predicted or overestimated).
Deprecated as of 3/2015.
benjhayden@chromium.org
Duration of the FrameView::performLayout trace event, which occurs at most
once per frame.
Deprecated as of 3/2015.
benjhayden@chromium.org
Amount of time spent doing line layout during FrameView::performLayout.
Please list the metric's owners. Add more owner tags as needed.
A lower-bound on the percentage increase in memory that would result from
promoting all layers that have a webkit-transition on opacity or transform.
Deprecated as of 10/2013.
Please list the metric's owners. Add more owner tags as needed.
This measures how long all unload event handlers required to run whenever an
unload event is processed.
Please list the metric's owners. Add more owner tags as needed.
The time from when a document finished loading to when all it's resources
are also loaded.
Deprecated 6/15/09. Replaced by Renderer2.RequestToFinish_L
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to when it is fully
loaded.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to when it is fully
loaded.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to its first layout.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to when it starts loading.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page started loading to when it is fully loaded.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page starts loading to when the main document is
finished loading.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page starts loading to its first layout.
wiltzius@chromium.org
Distribution of actual finished pages, vs abandoned pages, where we needed
to declare a finish time prematurely since the page was being closed
(exited).
Deprecated 2014-05 because of impl-side painting.
wiltzius@chromium.org
Time spent by WebKit painting the page, in milliseconds, when the GPU
acceleration is active, for paints that affect non-root layers.
Deprecated 2014-05 because of impl-side painting.
wiltzius@chromium.org
WebKit paint throughput, measured in megapixels per second, when GPU
acceleration is active, for paints that affect non-root layers.
wiltzius@chromium.org
Time between frames when GPU acceleration is active.
wiltzius@chromium.org
Time spent by WebKit painting the page, in milliseconds, when the GPU
acceleration is active, for paints that affect the root layer.
wiltzius@chromium.org
WebKit paint throughput, measured in megapixels per second, when GPU
acceleration is active, for paints that affect the root layer.
wiltzius@chromium.org
Time from when the animation callback was posted to when it ran.
wiltzius@chromium.org
Time from "begin" to "commit." "Begin"==
"request" if user requested, and "start" otherwise.
"Request"== time when user requested document. "Start"==
time when renderer requested load of document, after any unload of last
document. "Commit"== time when renderer got first byte of
document.
wiltzius@chromium.org
TBD
wiltzius@chromium.org
TBD
wiltzius@chromium.org
Time from "begin" to "first paint." "Begin"==
"request" if user requested, and "start" otherwise.
"Request"== time when user requested document. "Start"==
time when renderer requested load of document, after any unload of last
document. "First paint"== time when first paint operation was
performed.
wiltzius@chromium.org
Time from "big" to "first paint after load."
"Begin"== "request" if user requested, and
"start" otherwise. "Request"== time when user requested
document. "Start"== time when renderer requested load of document,
after any unload of last document. "First paint after load"== time
after onload() when first paint operation is performed.
wiltzius@chromium.org
Time from "commit" to "finish." "Commit"==
time when renderer got first byte of document. "Finish"==after
onload() and all resources are loaded.
wiltzius@chromium.org
Time from "commit" to "finish doc." "Commit"==
time when renderer got first byte of document. "Finish doc" ==
main document loaded, before onload(). "Finish"==after onload()
and all resources are loaded.
wiltzius@chromium.org
Time from "commit" to "first paint."
"Commit"== time when renderer got first byte of document.
"First paint"== time when first paint operation was performed.
wiltzius@chromium.org
Time from "commit" to "first paint after load."
"Commit"== time when renderer got first byte of document.
"First paint after load"== time after onload() when first paint
operation is performed.
vollick@chromium.org
It's possible for compositor hit testing to determine conclusively that
compositor thread scrolling can or cannot be done. It's also possible that
the hit testing result is inconclusive. We would like to see the I-don't-
know result as little as possible. This histogram tracks the ratios.
wiltzius@chromium.org
Time between frames, as measured on the compositor thread. This is collected
once per frame while it is being drawn to the screen in the compositor.
Renamed to Renderer4.pixelCountCulled_Draw.
wiltzius@chromium.org
Number of pixels that culling prevented being drawn to the screen,
normalized to the viewport size. This is collected once per frame while it
is being drawn to the screen in the compositor.
Renamed to Renderer4.pixelCountOpaque_Draw.
wiltzius@chromium.org
Number of pixels drawn to the screen and known opaque, normalized to the
viewport size. This is collected once per frame while it is being drawn to
the screen in the compositor.
Renamed to Renderer4.pixelCountTranslucent_Draw.
wiltzius@chromium.org
Number of pixels drawn to the screen and not known opaque, normalized to the
viewport size. This is collected once per frame while it is being drawn to
the screen in the compositor.
wiltzius@chromium.org
Time from "finish doc" to "finish." "Finish
doc"== main document loaded, before onload(). "Finish"==after
onload() and all resources are loaded.
wiltzius@chromium.org
Time from "finish " to "first paint after load."
"Finish"==after onload() and all resources are loaded. "First
paint after load"== time after onload() when first paint operation is
performed.
alokp@chromium.org
Whether gpu rasterization is enabled (checked once after the page is painted
for the first time).
alokp@chromium.org
If gpu rasterization is enabled, whether the page contents are suitable for
gpu rasterization (checked once after the page is painted for the first
time).
alokp@chromium.org
If gpu rasterization is enabled, whether it was triggered (checked once
after the page is painted for the first time).
alokp@chromium.org
If gpu rasterization is enabled, whether it was actually used for the page
(checked once after the page is painted for the first time).
wiltzius@chromium.org
Number of rects inside of a PictureLayer's invalidation region per commit.
wiltzius@chromium.org
Time to determine the page language. This is done after the page has been
loaded.
Deprecated as of 02/2015. No longer generated.
wiltzius@chromium.org
The ratio of LCDText CC Layers / candidate LCDText layers. Recorded in
LayerTreeHost, after LayerTreeHostCommon::CalculateDrawProperties() has
computed the properties we need. Only recorded for the first 50 frames of
every page.
Deprecated as of 02/2015. No longer generated.
wiltzius@chromium.org
The ratio of CC Layers which are candidates for LCDText AA / total picture
or content Layers. Recorded in LayerTreeHost, after
LayerTreeHostCommon::CalculateDrawProperties() has computed the properties
we need. Only recorded for the first 50 frames of every page.
wiltzius@chromium.org
Probability distribution for enumerated varieties of page loads.
wiltzius@chromium.org
Number of pixels that culling prevented being drawn to the screen, recorded
as 10 times the percentage of the viewport that these pixels cover. This is
collected once per frame while it is being drawn to the screen in the
compositor.
wiltzius@chromium.org
Number of pixels known to be opaque, recorded as 10 times the percentage of
the viewport that these pixels cover.
wiltzius@chromium.org
Number of pixels painted by WebKit into main memory, recorded as 10 times
the percentage of the viewport that these pixels cover. This is collected
once per commit from WebKit to the compositor.
wiltzius@chromium.org
Number of pixels not known to be opaque opaque, recorded as 10 times the
percentage of the viewport that these pixels cover.
wiltzius@chromium.org
The number of render passes (or render targets) in the renderer's frame. If
the value is more than one, then an intermediate rendering target must be
used during the rendering of the frame for each render pass greater than
one.
wiltzius@chromium.org
Time from "request" to "finish." "Request"==
time when user requested document. "Finish"==after onload() and
all resources are loaded.
wiltzius@chromium.org
Time from "request" to "start." "Request"==
time when user requested document. "Start"== time when renderer
requested load of document, after any unload of last document.
wiltzius@chromium.org
Time to capture a renderer snapshot.
wiltzius@chromium.org
Time between frames when the software renderer is being used, as measured on
the compositor thread. This is collected once per frame while it is being
drawn to the screen in the compositor.
wiltzius@chromium.org
Time between frames when the page is not GPU accelerated.
wiltzius@chromium.org
Time spent by WebKit painting the page, in milliseconds, when the page is
not GPU accelerated.
wiltzius@chromium.org
WebKit paint throughput, measured in megapixels per second, when the page is
not GPU accelerated.
wiltzius@chromium.org
Time from "start" to "commit." "Start"== time
when renderer requested load of document, after any unload of last document.
"Commit"== time when renderer got first byte of document.
wiltzius@chromium.org
Time from "start" to "finish." "Start"== time
when renderer requested load of document, after any unload of last document.
"Finish"==after onload() and all resources are loaded.
reveman@chromium.org
Time between the issue of a texture copy operation and detecting that it has
completed as measured by the GPU process.
wiltzius@chromium.org
The number of microseconds it took to upload a tile's full texture as
measured on the GPU process.
wiltzius@chromium.org
Time to capture a renderer thumbnail.
wiltzius@chromium.org
Number of tiles that culling prevented being uploaded to texture memory.
This is an approximation and is recorded as a 100 times the percentage of
the number of tiles, of default size, needed to cover the viewport. This is
collected once per commit from WebKit to the compositor.
Deprecated as of 04/2012, replaced with Renderer4.tileCountCulled_Upload.
wiltzius@chromium.org
Number of pixels that culling prevented being uploaded to texture memory,
normalized to the viewport size. This is collected once per commit from
WebKit to the compositor.
Renamed to Renderer4.pixelCountOpaque_Upload.
wiltzius@chromium.org
Number of pixels uploaded to texture memory and known to be opaque,
normalized to the viewport size. This is collected once per commit from
WebKit to the compositor.
Renamed to Renderer4.pixelCountTranslucent_Upload.
wiltzius@chromium.org
Number of pixels uploaded to texture memory and not known opaque, normalized
to the viewport size. This is collected once per commit from WebKit to the
compositor.
ppi@chromium.org
Roundtrip times for synchronous IPC calls from the renderer to browser.
vitalybuka@chromium.org
Count of renderer view context menu items shown.
vitalybuka@chromium.org
Count of renderer view context menu items (Only commands now) used.
estade@chromium.org
The state of the requestAutocomplete() dialog when it was dismissed.
estade@chromium.org
The initial state of a user that's interacting with a freshly shown
requestAutocomplete() dialog.
estade@chromium.org
User interactions with the Autofill popup shown while filling an
requestAutocomplete() dialog.
estade@chromium.org
Measures the frequency of security warnings and errors in the
RequestAutocomplete dialog.
estade@chromium.org
Measures the duration for which an requestAutocomplete() dialog was shown.
estade@chromium.org
Measures the duration for which an requestAutocomplete() dialog was shown,
in cases where the user ended up canceling out of the dialog.
estade@chromium.org
Measures the duration for which an requestAutocomplete() dialog was shown,
in cases where the user ended up accepting the dialog.
estade@chromium.org
Measures how users are interacting with the requestAutocomplete() dialog UI.
estade@chromium.org
Measures the duration of time it takes for the requestAutocomplete() UI to
be actionable by the user after it is shown.
estade@chromium.org
Measures the frequency of errors in communicating with the Google Online
Wallet server.
estade@chromium.org
Measures the frequency of required user actions returned by the Google
Online Wallet server.
merkulova@chromium.org
Records the number of times the factory reset dialog was shown. Grouped by
the viewtype.
zhenw@chromium.org
A boolean that used to indicate a corner case when certain resources are not
written to the Predictor database becuase their URLs are too long. We
monitor this number to ensure that we do not discard too many resources.
Deprecated 08/2012. Replaced with ResourcePrefetchPredictorNavigationEvent.
zhenw@chromium.org
A boolean that indicates if the speculative resource prefetch predictor has
predictions for a Navigation. This is updated on each navigations and helps
us determine the coverage of the predictor.
zhenw@chromium.org
A boolean that used to indicate a corner case when we may not have prefetch
results even though prefetching is enabled and predictions are present,
because another navigation in the same tab canceled the prefetching of the
previous load.
zhenw@chromium.org
The visit count of a URL in the history database, measured when the onload
fires for the URL. Helpful in figuring out what visit count should be used
to start learning about a URL.
zhenw@chromium.org
Assuming a fixed number (25 or 50) of URLs could be prefetched max, how many
would be available for prefetch (after we apply our heuristics for picking
subresources to prefetch for a navigation).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the cache restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the network restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
zhenw@chromium.org
Similar to ResourcePrefetchPredictor.Host.PredictedPrefetchFromNetwork but
as a percent of the total number of resources the page actually fetched from
the network. This depcits the major gains that we can get.
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page not used
by the page, restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
prefetches cancelled as a percentage of the total number of resources that
the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
prefetches failed as a percentage of the total number of resources that the
predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching but were not
requested by the page, as a percentage of the total number of resources that
the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching and also came
from the cache when the page requested it, as a percentage of the total
number of resources that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching but came from
the network when the page requested it, as a percentage of the total number
of resources that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from network while prefetching but were not
requested by the page, as a percentage of the total number of resources that
the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from network while prefetching but came from
the cache when the page requested it, as a percentage of the total number of
resources that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching and also came
from the network when the page requested it, as a percentage of the total
number of resources that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of resources
that were prefetchable but were not prefetched as a percentage of
prefetchable resources.
zhenw@chromium.org
The count of number of unique hosts in the HostTable, i.e. the number of
hosts that the database has prediction data for. This data is useful for
determining the recall/precision as a function of the number of hosts that
need to be tracked by the database. Measured at startup.
zhenw@chromium.org
The count of number of rows in the HostTable. This is effecively the number
of (host, resource URL) pairs in the database. This is measured at startup
and used to get an estimate of the data size.
zhenw@chromium.org
Records stats about main frame navigations. Records the total number of
requests/responses/redirects for main frame urls along with the numbers for
how often the predictor can process such events. This is useful to figure
out what percentange of requests are handled by the predictor and also for
sanity checking the other stats.
zhenw@chromium.org
Records stats about various interesting events such as - request start,
response start, redirect, onload, etc during the load of a main frame.
Essential for understanding the complete life of a navigation request start
to the onload fire and the events that occur in between.
Deprecated 08/2012. Replaced with ResourcePrefetchPredictorNavigationEvent.
zhenw@chromium.org
The status of various navigations from the view point of the 'onload' event.
Since we measure the prediction accuracy and learn navigation subresources
on the onload event, it is useful to know how many of the navigations are
abandoned before 'onload' fires.
zhenw@chromium.org
Records the number of pages on each type of network after a page is loaded.
zhenw@chromium.org
Page load time. It starts from when the main frame URL request is sent out
to when the main frame document load is completed.
This is recorded for both prefetched and non-prefetched pages.
Deprecated 01/2013. Replaced with specific ones for Url and Host.
zhenw@chromium.org
Assuming a fixed number of URLs could be prefetched max, how many would be
available for prefetch (after we apply our heuristics for picking
subresources to prefetch for a navigation).
Deprecated 01/2013. Replaced with specific ones for Url and Host.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the cache restricted to some max predictions.
Deprecated 01/2013. Replaced with specific ones for Url and Host.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the network restricted to some max predictions.
Deprecated 01/2013. Replaced with specific ones for Url and Host.
zhenw@chromium.org
Similar to ResourcePrefetchPredictor.Predicted.PrefetchFromNetwork but as a
percent of the total number of resources the page actually fetched from the
network. This depcits the major gains that we can get.
Deprecated 01/2013. Replaced with specific ones for Url and Host.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page not used
by the page, restricted to some max predictions.
zhenw@chromium.org
Records stats about various interesting events such as - when partial or all
of history is cleared. It will include events which do not necessarily
happen during a navigation (which are reported in
ResourcePrefetchPredictor.NavigationEvent).
zhenw@chromium.org
Records stats about requests, redirects, and responses observed by the
ResourcePrefetchPredictorObserver. These stats are useful as a baseline for
other stats.
zhenw@chromium.org
The distribution of the reasons for which subresources are ignored during
prefetching. This helps us prioritze reasons we should further investigate
to increase coverage. This is reported as a bit map and every status will be
a bitwise or of the underlying reasons.
zhenw@chromium.org
Assuming a fixed number of URLs could be prefetched max (25 or 50), how many
would be available for prefetch (after we apply our heuristics for picking
subresources to prefetch for a navigation).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the cache restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the network restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
zhenw@chromium.org
Similar to ResourcePrefetchPredictor.Url.PredictedPrefetchFromNetwork but as
a percent of the total number of resources the page actually fetched from
the network. This depcits the major gains that we can get.
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page not used
by the page, restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of prefetches
cancelled as a percentage of the total number of resources that the
predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of prefetches
failed as a percentage of the total number of resources that the predictor
tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching but were not requested by
the page, as a percentage of the total number of resources that the
predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching and also came from the
cache when the page requested it, as a percentage of the total number of
resources that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching but came from the network
when the page requested it, as a percentage of the total number of resources
that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from network while prefetching but were not requested
by the page, as a percentage of the total number of resources that the
predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from network while prefetching but came from the cache
when the page requested it, as a percentage of the total number of resources
that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching and also came from the
network when the page requested it, as a percentage of the total number of
resources that the predictor tried to prefetch.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of resources
that were prefetchable but were not prefetched as a percentage of
prefetchable resources.
zhenw@chromium.org
The count of number of unique main frame urls in the UrlTable, i.e. the
number of webpages that the database has prediction data for. This data is
useful for determining the recall/precision as a function of the number of
webpages that need to be tracked by the database. Measured at startup.
zhenw@chromium.org
The count of number of unique main frame urls that are deleted from the URL
table at startup because they are no longer in history. Essential to figure
out how much data we are loosing out.
zhenw@chromium.org
Same as ResourcePrefetchPredictor.UrlTableMainFrameUrlsDeletedNotInHistory
but recording percentage of URLs in the table rather than absolute numbers.
zhenw@chromium.org
The count of number of rows in the UrlTable. This is effecively the number
of (main frame URL, resource URL) pairs in the database. This is measured at
startup and used to get an estimate of the data size.
aiolos@chromium.org
The amount of time between when the ResourceScheduler is informed of a
Client's creation or starts loading and when that Client finishes loading in
a Client which has been user-observable the entire time.
Note: Will not include time for the main resource if PlzNavigate is in use.
aiolos@chromium.org
The amount of time between when the ResourceScheduler is informed of a
Client's creation or starts loading and when that Client finishes loading in
a Client which has been background the entire time.
Note: Will not include time for the main resource if PlzNavigate is in use.
aiolos@chromium.org
The amount of time between when the ResourceScheduler is informed of a
Client's creation or starts loading and when that Client finishes loading in
a Client which has switched between Active and Background.
Note: Will not include time for the main resource if PlzNavigate is in use.
aiolos@chromium.org
The amount of time between the last time that a Client becomes
user-observable and when that Client finishes loading in a Client that was
user-observable when the load completed.
Note: Will not include time for the main resource if PlzNavigate is in use.
aiolos@chromium.org
The amount of time the ResourceScheduler is throttling a request after
WillStartRequest is called for a request in a client that was
user-observable at creation and start time.
aiolos@chromium.org
The amount of time the ResourceScheduler is throttling a request after
WillStartRequest is called for a request in a client that was background at
creation and start time.
aiolos@chromium.org
The amount of time the ResourceScheduler is throttling a request after
WillStartRequest is called on a request without a Client or a request in a
Client which is in a different state since the request was made. Note that
this won't capture requests which have switched state an even number of
times. Switching from Active to Background back to Active will be recorded
in the Active version of this histogram.
aiolos@chromium.org
The amount of time between when the request was created and when the
ResourceScheduler stops throttling the request in a client that was
user-observable at creation and start time.
aiolos@chromium.org
The amount of time between when the request was created and when the
ResourceScheduler stops throttling the request in a client that was
background at creation and start time.
aiolos@chromium.org
The amount of time between when the request was created and when the
ResourceScheduler stops throttling a request without a client or a request
in a Client which is in a different state since the request was made. Note
that this won't capture requests which have switched state an even number of
times. Switching from Active to Background back to Active will be recorded
in the Active version of this histogram.
feng@chromium.org
Records the user action that enables/disables safe browsing feature in the
Settings page on Android.
csharp@chromium.org
krstnmnlsn@chromium.org
A windows only historgram. Records when an unknown base relocation type is
encountered while reading the reloc table of a loaded module.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
The first stage check that measures the time that Chrome took to check if a
URL is present in our in-memory bloom filter.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
TBD.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
The second stage check that measures the time that Chrome took to check if a
URL is present in our SQLite database.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
The second stage check that mesures the time that Chrome took to check if a
URL is present in our SQLite database. This time includes the filter check
time.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
This measures the time that SafeBrowsing actually delayed the browsing
experience. It records the difference between the time when Chrome would
have started reading the response for a URL and when the SafeBrowsing system
completed its check of that URL.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
The first stage check that measures the time that Chrome took to check if a
URL is present in our in-memory hash table.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
The third and final stage check that mesures the time that Chrome took to
get a response from the Google SafeBrowsing servers for a particular URL.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
The third and final stage check that mesures the time that Chrome took to
get a response from the Google SafeBrowsing servers for a particular URL.
This time includes the filter and database check time.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
This measures the time that SafeBrowsing actually delayed the browsing
experience. It records the difference between the time when Chrome would
have started reading the response for a URL and when the SafeBrowsing system
completed its check of that URL.
Has not been generated for years (7/8/14).
Please list the metric's owners. Add more owner tags as needed.
TBD.
shess@chromium.org
The number of add prefixes stored in the database after the last update.
Bloom filter support deleted in October 2012.
Please list the metric's owners. Add more owner tags as needed.
Track failures when in processing the safe-browsing database bloom filter.
This became misleading around M-22 (September 2012), deleted in M-32
(November 2013).
Please list the metric's owners. Add more owner tags as needed.
All prefix misses (server returned no full hashes) and prefix misses due to
false positives in the bloom filter.
Bloom filter support deleted in October 2012.
Please list the metric's owners. Add more owner tags as needed.
Time to load the BloomFilter file.
Deprecated 12/2014. Moved to SB2.DatabaseSizeKilobytes.Browse.
shess@chromium.org
The size of the browsing SafeBrowsing database file on disk in kilobytes,
after an update has occurred.
shess@chromium.org
The time that it took to regenerate the filter after we have received all
the update chunks.
Deprecated because it was exceeding the range. Replaced by
SB2.BuildReadKilobytes.
Please list the metric's owners. Add more owner tags as needed.
The number of bytes read by the browser process during the bloom filter
generation phase.
shess@chromium.org
The number of kilobytes read by the browser process during the filter
generation phase.
shess@chromium.org
The number of read operations issued by the browser process during the
filter generation phase.
Deprecated because it was exceeding the range. Replaced by
SB2.BuildWriteKilobytes.
Please list the metric's owners. Add more owner tags as needed.
The number of bytes written by the browser process during the bloom filter
generation phase.
shess@chromium.org
The number of kilobytes written by the browser process during the filter
generation phase.
shess@chromium.org
The number of write operations issued by the browser process during the
filter generation phase.
shess@chromium.org
The time that it takes to write one redirect URL (which can contain multiple
chunks) to the database.
shess@chromium.org
The network time between the request and response for a chunk.
shess@chromium.org
The size of one chunk URL.
Deprecated because it was exceeding the range. Replaced by
SB2.DatabaseKilobytes.
Please list the metric's owners. Add more owner tags as needed.
The size of the SafeBrowsing database file on disk.
shess@chromium.org
Track failures when updating the safe-browsing database.
Replaced by SB2.BrowseDatabaseKilobytes.
shess@chromium.org
The size of the SafeBrowsing database file on disk in kilobytes.
shess@chromium.org
The time it takes to initialize the SafeBrowsing storage backend, in
milliseconds.
gab@chromium.org
The size of one of the SafeBrowsing database file on disk in kilobytes,
after a database update has occurred (once a few minutes after startup, and
every thirty minutes or so thereafter).
shess@chromium.org
The size of the update file before merging with the database file, in
kilobytes.
shess@chromium.org
The time that SafeBrowsing actually delayed the browsing experience. It
records the difference between the time when Chrome would have started
reading the response for a URL and when the SafeBrowsing system completed
its check of that URL.
Deleted in M-34 (February 2014).
Please list the metric's owners. Add more owner tags as needed.
Obsolete download BINHASH add chunks deleted.
Deleted in M-34 (February 2014).
Please list the metric's owners. Add more owner tags as needed.
Obsolete download BINHASH sub chunks deleted.
shess@chromium.org
Records results of SafeBrowsing download check, including both url check and
downloaded file hash check.
Deprecated 12/2014. Moved to SB2.DatabaseSizeKilobytes.Download.
shess@chromium.org
The size of the downloads SafeBrowsing database file on disk in kilobytes,
after an update has occurred.
shess@chromium.org
The time it takes for a download to finish.
shess@chromium.org
The time it takes for SafeBrowsing to check hash of a download file.
shess@chromium.org
The time it takes for SafeBrowsing to check a download url.
Deprecated 3/11/11, and replaced by SB2.DownloadChecks.
Please list the metric's owners. Add more owner tags as needed.
Records results of SafeBrowsing download url check.
Deprecated 03/2015. Replaced by
SecurityInterstitialInteraction::EXTENDED_REPORTING_IS_ENABLED.
felt@chromium.org
Whether the user has Safe Browsing extended reporting enabled at the time a
Safe Browsing warning was dismissed. This tracks the fraction of all SB
interstitials that had reporting enabled.
Deprecated, replaced by SB2.DatabaseFailure BROWSE_DB_UPDATE_FINISH.
Please list the metric's owners. Add more owner tags as needed.
The count of the number of times an update failed when being committed to
the database.
shess@chromium.org
The time that it took to check a URL against our in-memory filter.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
The size of the current bloom filter in kilobytes.
shess@chromium.org
Which filter file the database loaded from disk.
Deprecated, replaced by SB2.DatabaseFailure FILTER_MISSING.
Please list the metric's owners. Add more owner tags as needed.
The count of the number of times we attempted to load the bloom filter file
but it was missing.
Deprecated, replaced by SB2.DatabaseFailure FILTER_READ.
Please list the metric's owners. Add more owner tags as needed.
The count of the number of times we attempted to load the bloom filter file
but failed while reading the file on disk.
Deprecated because it was exceeding the range. Replaced by
SB2.FilterKilobytes.
Please list the metric's owners. Add more owner tags as needed.
The size of the current bloom filter.
Deprecated, replaced by SB2.DatabaseFailure FILTER_WRITE.
Please list the metric's owners. Add more owner tags as needed.
The count of the number of times we attempted to save the bloom filter file
but failed while writing the file to disk.
shess@chromium.org
Collection of boolean events for SafeBrowsingFileStore instances. Includes
corruptions detected, old versions detected, and various failures detected.
Deprecated in favor of SB2.GetHashResult STATUS_200.
Please list the metric's owners. Add more owner tags as needed.
The number of GetHash requests that returned data (valid requests).
Deprecated in favor of SB2.GetHashResult STATUS_204.
Please list the metric's owners. Add more owner tags as needed.
The number of GetHash requests that returned empty data (false positives).
mattm@chromium.org
Track return status from GetHash attempts (STATUS_200, STATUS_204,
NETWORK_ERROR, HTTP_ERROR, BACKOFF_ERROR), whether parsing a 200 result
failed (PARSE_ERROR), and dispensation of returned values (EMPTY, HIT,
MISS). EMPTY means the response had no full hashes, and should contain all
of the 204 responses plus all *_ERROR cases. HIT means that one of the full
hashes matched. MISS means that none of the hashes matched (there was a
prefix collision). (PARSE_ERROR, NETWORK_ERROR, HTTP_ERROR, and
BACKOFF_ERROR were added in M36.)
mattm@chromium.org
Track return status from GetHash attempts (STATUS_200, STATUS_204,
NETWORK_ERROR, HTTP_ERROR, BACKOFF_ERROR), whether parsing a 200 result
failed (PARSE_ERROR), and dispensation of returned values (EMPTY, HIT,
MISS). EMPTY means the response had no full hashes, and should contain all
of the 204 responses plus all *_ERROR cases. HIT means that one of the full
hashes matched. MISS means that none of the hashes matched (there was a
prefix collision). (PARSE_ERROR, NETWORK_ERROR, HTTP_ERROR, and
BACKOFF_ERROR were added in M36.)
Deprecated in favor of SB2.GetHashResult FULL_HASH_* and
SB2.BloomFilterFalsePositives. It is unclear if this histogram ever
reported useful data.
Please list the metric's owners. Add more owner tags as needed.
The number of GetHash requests returning full hashes that didn't match the
URL that initiated the request.
Deprecated, replaced by SB2.DatabaseFailure CORRUPT.
Please list the metric's owners. Add more owner tags as needed.
The count of the number of times a database was found corrupt and reset.
Deprecated, replaced by: interstitial.malware.* and interstitial.phishing.*.
felt@chromium.org
Track number of times Safe Browsing interstitials have been shown, and how
many times they have been clicked through or not.
Deprecated, replaced by: interstitial.malware.* and interstitial.phishing.*.
felt@chromium.org
Tracks the click-through rate for specific cases of the interstitial.
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user navigating away by for example, closing the tab, clicking the browser
back button or typing another URL in the address bar.
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user clicking on diagnostic page link.
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user expanding the "see more info" section of the page. (Only
applies to field trial version 2 of the interstitial.)
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user clicking on the learn more about malware link.
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user clicking on the privacy policy link.
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user clicking on the proceed link.
Deprecated 9/2014.
felt@chromium.org
The time between when we show the SafeBrowsing malware interstitial and the
user clicking on the big green back button.
shess@chromium.org
The time that it took to receive a response from the Google SafeBrowsing
servers for a GetHash request.
Deprecated 7/2014. No longer generated.
shess@chromium.org
Size of v1 database deleted from client profile.
shess@chromium.org
Indicates how sharded safe-browsing on-disk stores are. Values like 0 to 4
are reasonable.
felt@chromium.org
The time between when we show the SafeBrowsing phishing interstitial and the
user navigating away by for example, closing the tab, clicking the browser
back button or typing another URL in the address bar.
felt@chromium.org
The time between when we show the SafeBrowsing phishing interstitial and the
user expanding the "see more info" section of the page. (Only
applies to field trial version 2 of the interstitial.)
felt@chromium.org
The time between when we show the SafeBrowsing phishing interstitial and the
user clicking on the learn more link.
felt@chromium.org
The time between when we show the SafeBrowsing phishing interstitial and the
user clicking on the proceed link.
felt@chromium.org
The time between when we show the SafeBrowsing phishing interstitial and the
user clicking on the report error link.
felt@chromium.org
The time between when we show the SafeBrowsing phishing interstitial and the
user clicking on the big green back button.
shess@chromium.org
The size of the PrefixSet storage in bits, divided by the number of prefixes
represented. Should almost always be 16.
Deprecated 9/2012. No longer generated, BloomFilter being removed.
Please list the metric's owners. Add more owner tags as needed.
Records how well the PrefixSet implementation matches the BloomFilter
implementation.
Deprecated 01/2014. Replaced by suffixed SB2.PrefixSetSizeKilobytes.
shess@chromium.org
The size of one of the PrefixSet files in kilobytes.
shess@chromium.org
Time to load one of the PrefixSet files.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
For debugging PrefixSet. How many extra results GetPrefixes returns.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
For debugging PrefixSet. How many fewer results GetPrefixes returns.
shess@chromium.org
The size of one of the PrefixSet files in kilobytes. Logged after a database
update has occurred and the PrefixSet has been flushed to disk (once a few
minutes after startup, and every thirty minutes or so thereafter).
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
For debugging PrefixSet. How far unsorted deltas are from expected value.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
For debugging PrefixSet. Distance of unsorted elements from expected
location.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
For debugging PrefixSet. How far into the results unsorted elements were
found. Interesting values would be 0%, 50%, or 100%.
Deprecated 9/2012. No longer generated.
Please list the metric's owners. Add more owner tags as needed.
For debugging PrefixSet. Size of unsorted sets. To see if there is a
problem with a particular size of dataset.
shess@chromium.org
Version read from one of the PrefixSet files.
shess@chromium.org
Time to store one of the PrefixSet files.
Deprecated 06/2014. Replaced by SB2.ExtendedReportingIsEnabled.
Please list the metric's owners. Add more owner tags as needed.
Whether the user has Safe Browsing extended reporting enabled at the time a
Safe Browsing warning was dismissed. This tracks the fraction of all SB
interstitials that had reporting enabled.
Deprecated 03/2015. Replaced by
SecurityInterstitialInteraction::SET_EXTENDED_REPORTING_ENABLED.
felt@chromium.org
Tracks changes to the Safe Browsing extended reporting opt-in which is shown
in the Safe Browsing interstitial.
Deprecated 06/2014. Replaced by SB2.SetExtendedReportingEnabled.
Please list the metric's owners. Add more owner tags as needed.
Tracks changes to the Safe Browsing extended reporting opt-in which is shown
in the Safe Browsing interstitial.
Deprecated 12/2014. Merged into SB2.PrefixSetWrite.
shess@chromium.org
Time to store the Side Effect Free Whitelist PrefixSet file. Note: this
histogram was intended to be stored as
SB2.SideEffectFreeWhitelistPrefixSetWrite but was actually reported as
SB2.SideEffectFreePrefixSetWrite from its inception to its deprecation...
Deprecated 12/2014. Moved to
SB2.DatabaseSizeKilobytes.SideEffectFreeWhitelist.
shess@chromium.org
The size of the Side Effect Free Whitelist SaafeBrowsing database file on
disk in kilobytes, after an update has occurred.
Deprecated 12/2014. Moved to
SB2.PrefixSetSizeKilobytes.SideEffectFreeWhitelist.
shess@chromium.org
The size of the Side Effect Free Whitelist PrefixSet file in kilobytes,
after an udpate has occurred.
Deprecated 12/2014. Merged into SB2.PrefixSetLoad.
shess@chromium.org
Time to load the Side Effect Free Whitelist PrefixSet file.
Deprecated 4/2015.
shess@chromium.org
The instantiation status of the SideEffectFreeWhitelist.
shess@chromium.org
Version read from the store file.
shess@chromium.org
The number of sub prefixes stored in the database after the last update.
shess@chromium.org
The time from the receipt of the update request to the receipt of the final
update chunk.
shess@chromium.org
The payload size of update requests to the server.
shess@chromium.org
Result from trying to update the SafeBrowsing data.
shess@chromium.org
The size of all the chunk URLs in an update response.
feng@chromium.org
The size of all the chunk URLs in an update response when Chrome is in the
background.
feng@chromium.org
The size of all the chunk URLs in an update response when Chrome is in the
foreground.
shess@chromium.org
The number of chunk URLs in an update response.
shess@chromium.org
The operation this is tracking has been deleted as of 09/2014.
Older versions of the safe-browsing code incorrectly added additional
SBPrefix items when receiving full hashes. This caused errors when
calculating when to send gethash requests to the server. An additional pass
over the data has been added to remove the excess prefixes. This histogram
tracks progress of that code for purposes of informing a decision on when to
remove the additional pass. See http://crbug.com/361248 .
mattm@chromium.org
Records a histogram of the reason why downloads are marked as being
malicious or clean by the improved SafeBrowsing binary download protection.
Note that UNSUPPORTED_URL_SCHEME was split out of the INVALID_URL bucket in
M41. The NOT_BINARY_FILE check was moved before the UNSUPPORTED_URL_SCHEME
check in M42.
mattm@chromium.org
Records a histogram of how often users download a file with a file extension
that is possibly dangerous (e.g., exe, class).
mattm@chromium.org
Records the total time it takes for the SafeBrowsing download service to
check whether the content of a download is malicious or not, including file
feature extraction, whitelist checking, and server ping. This histogram only
includes checks that sent a ping to the SafeBrowsing server. It does not
include requests that were cancelled, but does include requests that
received a bad response.
mattm@chromium.org
The net error code for all CheckClientDownloadRequest URLFetchers.
mattm@chromium.org
Records the time it takes for the SafeBrowsing download service ping. It is
not recorded for requests that were cancelled.
mattm@chromium.org
Records the results of SafeBrowsing binary download checks which caused a
server ping.
mattm@chromium.org
The size of the upload data for CheckClientDownloadRequest URLFetchers.
mattm@chromium.org
For CheckClientDownloadRequest URLFetchers with successful status, the HTTP
response code that was received.
mattm@chromium.org
Records the portion of the SafeBrowsing download service check starting with
the point CheckClientDownloadRequest::StartTimeout() is called. It is
recorded regardless if a ping was sent or not. It is not recorded for
requests that were cancelled.
mattm@chromium.org
For SafeBrowsing binary download checks which reached the
CheckClientDownloadRequest::StartTimeout() call, records the final result
(once the check finishes or is cancelled).
grt@chromium.org
Records the time it takes for the SafeBrowsing download service to extract
image headers from a downloaded binary.
mattm@chromium.org
Records the time it takes for the SafeBrowsing download service to extract
signature info from a downloaded binary. This includes both unsigned and
signed binaries.
mattm@chromium.org
Records the time it takes for the SafeBrowsing download service to extract
info from a downloaded zip file.
mattm@chromium.org
Records the number of signed vs. unsigned executables that are downloaded.
mattm@chromium.org
Counter which is incremented whenever an executable is downloaded which is
either signed or whose URL matches the download whitelist.
mattm@chromium.org
For each zip file analyzed by the SafeBrowsing download service, records
true if the zip did not contain any executables but did contain another zip
file, false otherwise.
mattm@chromium.org
For each zip file analyzed by the SafeBrowsing download service, records if
the zip contained an executable file.
noelutz@chromium.org
The number of pages that we could have possibly classified (essentially the
number of top page navigations by users with SBClientMalware enabled). The
name is slightly misleading as it is recorded before
"Preclassification" happens.
noelutz@chromium.org
The net error code for all ClientMalwareRequest URLFetchers.
noelutz@chromium.org
The size of the upload data for ClientMalwareRequest URLFetchers.
noelutz@chromium.org
For ClientMalwareRequest URLFetchers with successful status, the HTTP
response code that was received.
noelutz@chromium.org
Records the number of malware classifications that were skipped because a
pre-classification check failed.
noelutz@chromium.org
Measures the success rate of sending malware reports. Sending a report can
fail due to a client reaching the limit on the number of reports it can send
per day or due to the report failing to be serialized.
noelutz@chromium.org
Deprecated 03/2014. That part of the code got deleted.
Counts the number of times the page ID that completed the page load does not
match the browse info page ID. We expect that number to be zero.
Please list the metric's owners. Add more owner tags as needed.
The counts for various reasons why an in-progress phishing classification
was canceled.
Please list the metric's owners. Add more owner tags as needed.
The number of times client-side phishing classifier expected to have no
pending classifications running but that check failed.
Please list the metric's owners. Add more owner tags as needed.
The number of pages that we could have possibly classified (essentially the
number of top page navigations by users with SBClientPhishing enabled). The
name is slightly misleading as it is recorded before
"Preclassification" happens.
Please list the metric's owners. Add more owner tags as needed.
The counts for various model status codes that we get after loading a new
client-side phishing model.
gab@chromium.org
The time that an individual chunk of DOM feature extraction work took.
gab@chromium.org
The number of times that DOM feature extraction finished early because the
active WebDocument's frame was removed during traversal.
gab@chromium.org
The number of iterations that the DOM feature extractor took to finish.
gab@chromium.org
The time that it took to resume DOM feature extraction for the phishing
classifier. Longer times may indicate that the page DOM changed between
chunks of work and the extractor had to re-traverse up to the saved
position.
gab@chromium.org
The number of phishing classifications that were aborted because DOM feature
extraction took too long.
gab@chromium.org
The time that the DOM feature extarctor took to finish, summed across all
chunks of work.
Please list the metric's owners. Add more owner tags as needed.
Time spent generating the thumbnail.
Please list the metric's owners. Add more owner tags as needed.
The number of features which were omitted from phishing classification
because they were added with an illegal value. This would indicate a bug.
Deprecated in Chrome 37, which now uses //net's internal matching.
mattm@chromium.org
The number of times that the phishing detection service could not be
initialized due to an error parsing the private IP networks. This would
indicate a bug.
Deprecated 12/2011. Whitelist entries are no longer part of
ClientPhishingResponse.
Please list the metric's owners. Add more owner tags as needed.
The number of whitelist_expression entries in a ClientPhishingResponse that
could not be canonicalized.
noelutz@chromium.org
Records the number of phishing classifications that were skipped because a
pre-classification check failed.
Please list the metric's owners. Add more owner tags as needed.
The number of phishing classifications that were previously cached as being
phishing but that will get re-classified (to possibly fix false positives).
Please list the metric's owners. Add more owner tags as needed.
The number of phishing classifier pingbacks that were skipped because
serializing the request protocol buffer to string failed.
Please list the metric's owners. Add more owner tags as needed.
The number of times that a cached phishing classification result was used,
rather than pinging the server.
Please list the metric's owners. Add more owner tags as needed.
Records the status when we create a scorer object for the client-side
phishing detection classifier.
Please list the metric's owners. Add more owner tags as needed.
The number of phishing classifications that were aborted because the term
feature extractor failed to initialize an ICU break iterator.
Please list the metric's owners. Add more owner tags as needed.
The time that an individual chunk of term feature extraction work took.
Please list the metric's owners. Add more owner tags as needed.
The number of iterations that the term feature extractor took to finish.
Please list the metric's owners. Add more owner tags as needed.
The number of phishing classification that were aborted because term feature
extraction took too long.
Please list the metric's owners. Add more owner tags as needed.
The time that the term feature extarctor took to finish, summed across all
chunks of work.
Please list the metric's owners. Add more owner tags as needed.
The number of times that the limit on the number of phishing classifier
features for a page was reached. This may indicate a bug, or that
kMaxFeatureSize is too small.
Please list the metric's owners. Add more owner tags as needed.
The time taken to extract URL features for the phishing classifier.
mattm@chromium.org
Count of times download feedback has been started, broken down by danger
type.
mattm@chromium.org
When a new download feedback request is added, records the number of
download requests currently active and/or pending.
mattm@chromium.org
Count of times eligible download notifications are shown. Broken down by
danger type.
Starting with M32, replaced by SBDownloadFeedback.Eligible.
mattm@chromium.org
Count of times download feedback button has been shown, broken down by
danger type.
mattm@chromium.org
Size of downloads that were of the correct danger type, regardless if they
meet the max file size check or if they are actually uploaded or not.
mattm@chromium.org
Size of downloads that failed to be uploaded to the feedback service.
mattm@chromium.org
Size of downloads that were successfully uploaded to the feedback service.
mattm@chromium.org
Final result of attempt to upload binary to download feedback service.
grt@google.com
The elapsed time to compute the hash of a blacklisted module.
grt@google.com
The elapsed time to validate the signature of a blacklisted module.
grt@google.com
The type of incident discarded by the safe browsing incident reporting
service as a result of profile or service destruction.
grt@chromium.org
The result of deleting a profile's download metadata file.
grt@chromium.org
The result of reading a profile's download metadata file.
grt@chromium.org
The result of writing a profile's download metadata file.
grt@google.com
The type of incident given to the safe browsing incident reporting service
but dropped as a result of not participating in safe browsing.
grt@google.com
The elapsed time to collect environmental data for a safe browsing incident
report.
grt@google.com
The elapsed time to find the most recent binary download from all loaded
profiles when creating a safe browsing incident report.
grt@google.com
The type of incident included in an incident report by the safe browsing
incident reporting service.
grt@google.com
The number of incidents collated into a single safe browsing incident report
before pruning.
grt@google.com
The elapsed time between two successive incidents collated into the same
incident report by the safe browsing incident reporting service.
grt@google.com
The type of incident pruned from a report in the safe browsing incident
reporting service as a result of having previously been reported.
grt@google.com
The percentage of incidents pruned from a safe browsing incident report on
account of having been previously reported.
grt@google.com
The type of incident received by the safe browsing incident reporting
service.
grt@google.com
The size, in bytes, of a safe browsing incident report.
grt@google.com
The elapsed time to upload a safe browsing incident report.
grt@google.com
The result of an attempted report upload by the safe browsing incident
reporting service.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis was aborted. This histogram is suffixed with the abort
reason.
Deprecated 01/2015.
gab@chromium.org
Logs the resource type of each resource request for which an off-domain
inclusion was detected by the OffDomainInclusionDetector.
Deprecated 01/2015. Moved to SBOffDomainInclusion.Abort.EmptyMainFrameURL.
gab@chromium.org
Logs the resource type of each resource request for which the main frame URL
was unexpectedly empty in the OffDomainInclusionDetector.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis concluded in no inclusion whitelist hit but a browsing
history hit.
Deprecated 01/2015 (was never reported, confirming experiment that handling
it is irrelevant).
gab@chromium.org
Logs the resource type of each resource request for which the main frame URL
was unexpectedly invalid (and not empty) in the OffDomainInclusionDetector.
gab@chromium.org
Logs the resource type of each resource request analyzed by the
OffDomainInclusionDetector.
gab@chromium.org
Logs the resource type of each resource request for which an off-domain
inclusion was detected by the OffDomainInclusionDetector and considered
suspicious.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis concluded in an inclusion whitelist hit.
ellyjones@chromium.org
Whether an SDCH dictionary was advertised over a secure scheme or not. This
histogram is logged inside SdchManager at advertisement time.
rdsmith@chromium.org
The number of dictionaries advertised in an HTTP GET transaction that
supports SDCH. Note that only non-zero advertisements are logged.
rdsmith@chromium.org
The reason why a blacklist blocking a request from advertising SDCH was
implemented. There is one entry in this histogram per inhibited request.
rdsmith@chromium.org
Each sample is the byte count for a dictionary that is loaded by Chrome. A
dictionary is loaded shortly after the first Google query performed in each
session, and allows future SDCH transactions to be encoded/decoded using
that dictionary.
rdsmith@chromium.org>
The fate, both on input and output, of dictionary requests. There is
intended to be two entries in this histogram for each Get-Dictionary seen
(except failed requests are not currently tracked).
rdsmith@chromium.org
The number of times a dictionary has been successfully used for decoding,
recorded at the time it is evicted from the manager.
Replaced by Sdch3.Experiment3_Holdback.
rdsmith@chromium.org
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of an SDCH encoded transmission made after the link had proven it
was capable of handling SDCH compression.
Replaced by Sdch3.Experiment3_Holdback.
rdsmith@chromium.org
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of a holdback, which precluded SDCH despite the fact that the link
had proven it was capable of handling SDCH compression.
rdsmith@chromium.org
Duration in time from the first byte of a request was received, until all
bytes were received. During the running of an SDCH latency experiment,
these packets were part of an SDCH encoded transmission made after the link
had proven it was capable of handling SDCH compression.
rdsmith@chromium.org
Duration in time from the first byte of a request was received, until all
bytes were received. During the running of an SDCH latency experiment,
these packets were part of a holdback, which precluded SDCH despite the fact
that the link had proven it was capable of handling SDCH compression.
Replaced by Sdch3.Experiment2_Decode.
rdsmith@chromium.org
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of an SDCH encoded transmission made after the link had proven it
was capable of handling SDCH compression.
Replaced by Sdch3.Experiment2_Holdback.
rdsmith@chromium.org
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of a holdback, which precluded SDCH despite the fact that the link
had proven it was capable of handling SDCH compression.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
rdsmith@chromium.org
The duration between receipt of the 1st holdback (non-SDCH encoded) packet
and receipt of the last packet. Only groups that are part of the holdback
(i.e., could have been sdch encoded) are sampled.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
rdsmith@chromium.org
If SDCH decoding was disabled client side, this records how many URLs were
processed by the SDCH filter before disabling this feature. The most common
number is 1, which happens when there is one home-page tab that contains
SDCH encoded data, for which there is no dictionary loaded into the Chrome
process (yet), since Chrome was just restarted. Large values in this
histogram are indicative of flaky decompression, that works for a while, and
then is disabled. Values of 2 or 3 may appear if a user has more than one
home page with a query, and restarts there browser.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 1st SDCH encoded packet and receipt of the 2nd packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
The duration between receipt of the 1st SDCH encoded packet and receipt of
the last packet, for processing by the SDCH filter.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 2nd SDCH encoded packet and receipt of the 3rd packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 3rd SDCH encoded packet and receipt of the 4th packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 4th SDCH encoded packet and receipt of the 5th packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
(discontinued 7/29/2009, and replaced by
Sdch3.Network_Decode_Bytes_Processed_b) The number of bytes processed
(received over the net or from cache) by the SDCH filter chain.
rdsmith@chromium.org
The number of bytes processed (received over the net or from cache) by the
SDCH filter chain.
rdsmith@chromium.org
The number of bytes emitted after decoding by the SDCH filter.
rdsmith@chromium.org
The duration between putting the first byte of a request (such as a GET) on
the wire, until the last by of compressed SDCH encoded content is received
(with durations over 10 minutes discarded). During a planned latency
experiment, some clients will receive encoded SDCH data, and other will
received mere gzip'ed data (that passes through the SDCH filter unchanged).
rdsmith@chromium.org
An approximation to the total number of SDCH encoded packets received for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
The ratio of the number of bytes read from the network (or cache) and fed to
the filter chain (usually the gunzip filter) vs. the number of bytes emitted
by the SDCH filter to be rendered. This is commonly described as the SDCH
compression ratio.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
The duration between receipt of the 1st **NON**-SDCH encoded packet to
receipt of the last packet, for processing by the SDCH filter.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
rdsmith@chromium.org
The duration between putting the first byte of a request (such as a GET) on
the wire, until the last by gzip compressed content is received and
passed-through unchanged by the SDCH filter (with durations over 10 minutes
discarded). During a planned latency experiment, some clients will receive
encoded SDCH data, and other will received mere gzip'ed data (that passes
through the SDCH filter unchanged).
rdsmith@chromium.org
The total number of **NON**-SDCH encoded packets received for processing by
the SDCH filter in one URL fetch. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
ellyjones@chromium.org
The absolute difference in bytes between the amount of data entering the
SDCH filter and the amount of data exiting the SDCH filter.
ellyjones@chromium.org
Absolute sizes, in bytes, of SDCH dictionaries fetched over the network.
These are logged in SdchOwner when dictionary fetches complete.
rdsmith@chromium.org
If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF
decoder still has internally buffered data that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to the start of the filter chain (usually to the
gunzip filter).
rdsmith@chromium.org
If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF
decoder still has internally buffered data that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to VCDIFF decoder (usually after gunzipping).
rdsmith@chromium.org
If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF
decoder still has internally buffered data that has never been read, this
histogram reports the number of bytes that were output by the VCDIFF decoder
(and sent toward the renderer).
rdsmith@chromium.org
Tracks failures that occur when reading in or writing out persisted
dictionary information.
Deprecated 2014-11. Sdch3.ProblemCodes_5 used instead.
rdsmith@chromium.org
Each sample is the report of a distinct problem code.
Deprecated 2014-11. Sdch3.ProblemCodes_5 used instead.
rdsmith@chromium.org
Each sample is the report of a distinct problem code.
rdsmith@chromium.org
Each sample is the report of a distinct problem code.
rdsmith@chromium.org
Attempted SDCH decoding can fail at the Read() filter processing stage. In
some of those cases, the request is corrupted enough that it must be either
retried or failed completely. This histogram records the details of why the
request was considered corrupted, for results returned from the cache.
rdsmith@chromium.org
Attempted SDCH decoding can fail at the Read() filter processing stage. In
some of those cases, the request is corrupted enough that it must be either
retried or failed completely. This histogram records the details of why the
request was considered corrupted for results returned from the network.
ellyjones@chromium.org
Measures the time-weighted memory use of SDCH dictionaries, in bytes. The
numerator is bytes of dictionary times seconds that dictionary was in
memory, and the denominator is seconds that the Chrome process lives.
rdsmith@chromium.org
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were in that buffer.
rdsmith@chromium.org
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to the start of the filter chain (usually to the
gunzip filter).
rdsmith@chromium.org
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to VCDIFF decoder (usually after gunzipping).
rdsmith@chromium.org
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were output by the VCDIFF decoder
(and sent toward the renderer).
mathp@chromium.org
The origin/cause of a change to the default search provider.
Made obsolete around Chrome 32. Use Search.DefaultSearchProviderType
instead.
Please list the metric's owners. Add more owner tags as needed.
The id of the default search engine that is loaded after Chrome startup. See
src/chrome/browser/search_engines/prepopulate_engines.json for more info.
mpearson@chromium.org
The type of the default search engine that is loaded when a profile is
opened or after a profile reset. Note that at least one profile is opened
on startup. Due to an error, there was a period from roughly May 9 2014 to
May 23 2014 during which this was not being logged.
erikwright@chromium.org
The number of times that a user-selected DSE was migrated from separate
String/List/..Value preferences to the new single DictionaryValue used in
M36.
dpolukhin@chromium.org
Records result of fetching and parsing OEM customization manifest. See
ServicesCustomizationDocument class for more info. Used only on Chrome OS.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for
waitUntil() promise to settle.
falken@chromium.org
The result of dispatching the activate event to the worker.
nhiroki@chromium.org
Records result of destroy database operations in ServiceWorkerDatabase.
nhiroki@chromium.org
Records result of opening a database for ServiceWorkerDatabase.
nhiroki@chromium.org
Records result of read operations in ServiceWorkerDatabase.
nhiroki@chromium.org
Records result of write operations in ServiceWorkerDatabase.
nhiroki@chromium.org
Records result of opening a disk cache for ServiceWorkerDiskCache.
nhiroki@chromium.org
Records result of reading response from ServiceWorkerDiskCache.
nhiroki@chromium.org
Records result of writing response into ServiceWorkerDiskCache.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for
the respondWith() promise to settle.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.oninstall. Includes the time for
the waitUntil() promise to settle.
falken@chromium.org
The result of dispatching the install event to the worker.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onmessage.
peter@chromium.org
Execution time of ServiceWorkerGlobalScope.onnotificationclick.
johnme@chromium.org
Execution time of ServiceWorkerGlobalScope.onpush.
horo@chromium.org
The length of cached metadata of Service Worker scripts. Logged on each load
of Service Worker script only when the cached metadata is available. It
doesn't include the size of imported scripts.
horo@chromium.org
The total length of cached metadata of Service Worker scripts. Logged on
each start of Service Worker only when the cached metadata is available. It
includes the main script and imported scripts.
horo@chromium.org
The counts of scripts per Service Worker. Logged on each start of Service
Worker. It includes the main script and imported scripts.
ksakamoto@chromium.org
The length of Service Worker scripts. Logged on each load of Service Worker
script. It doesn't include the size of imported scripts.
horo@chromium.org
The total length of Service Worker scripts. Logged on each start of Service
Worker. It includes the main script and imported scripts.
falken@chromium.org
The result of trying to start a Service Worker that has not yet installed.
See also ServiceWorker.StartWorker.Status for installed workers.
falken@chromium.org
The time taken to start a Service Worker that has not yet installed, from
process allocation to ACK of started from the renderer (which occurs after
script execution). This may include script download time. The metric is not
recorded if DevTools was ever attached to the Service Worker during startup.
See also ServiceWorker.StartWorker.Time for installed workers.
falken@chromium.org
The result of trying to start a Service Worker that is already installed.
See also ServiceWorker.StartNewWorker.Status for new workers.
falken@chromium.org
The time taken to start a Service Worker that is already installed, from
process allocation to ACK of started from the renderer (which occurs after
script execution). The metric is not recorded if DevTools was ever attached
to the Service Worker during startup. See also
ServiceWorker.StartNewWorker.Time for new workers.
falken@chromium.org
The phase the EmbeddedWorker was in when ServiceWorker startup timed out.
nhiroki@chromium.org
Records result of storage recovery operations in ServiceWorkerStorage.
kinuko@chromium.org
Records the ratio of unhandled events to all events that are dispatched to
each ServiceWorker. Recorded when each ServiceWorkerVersion is destructed.
dmurph@chromium.org
The time to perform operations on the Cache object in the ServiceWorker
Cache API.
dmurph@chromium.org
The time to perform operations on the CacheStorage object in the
ServiceWorker Cache API.
jkarlin@chromium.org
Whether a new ServiceWorkerCacheStorage and its directory were successfully
created on disk.
jkarlin@chromium.org
The result of opening the backend in the ServiceWorker Cache API.
mariakhomenko@chromium.org
fqian@chromium.org
The length of a session (launch/foregrounding to backgrounding) on mobile.
yiyaoliu@chromium.org
How did the user interact with the SessionCrashed Bubble?
jeremy@chromium.org
sky@chromium.org
The time from SessionRestore start until all tabs have finished loading.
jeremy@chromium.org
sky@chromium.org
The size of the commands written to disk. See SessionBackend for details.
Deprecated 2014-10 in favor of SessionRestore.ForegroundTabFirstPaint.
jeremy@chromium.org
sky@chromium.org
TBD
jeremy@chromium.org
sky@chromium.org
The time from SessionRestore start until a visible tab has finished loading.
jeremy@chromium.org
sky@chromium.org
Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2.
jeremy@chromium.org
sky@chromium.org
The time from SessionRestore start until a visible tab's first paint.
jeremy@chromium.org
sky@chromium.org
The size, in k, of the last session file on disk.
jeremy@chromium.org
sky@chromium.org
Like NavEntryCommittedPeriod, but specifically to provide a clearer
breakdown of samples in the 10 minutes - 8 hours range.
jeremy@chromium.org
sky@chromium.org
Milliseconds between subsequent Save() operations due to a nav entry being
committed (new tab created + nav initiated).
jeremy@chromium.org
sky@chromium.org
Like NavListPrunedPeriod, but specifically to provide a clearer breakdown of
samples in the 10 minutes - 8 hours range.
jeremy@chromium.org
sky@chromium.org
Milliseconds between subsequent Save() operations due to the navigation list
being pruned (typically a change in back/forward stacks).
jeremy@chromium.org
sky@chromium.org
The number of tabs that were loaded simultaneously when restoring a session.
jeremy@chromium.org
sky@chromium.org
Amount of time to read and assemble the commands from the last session.
jeremy@chromium.org
sky@chromium.org
Like SavePeriod, but specifically to provide a clearer breakdown of samples
in the 10 minutes - 8 hours range.
jeremy@chromium.org
sky@chromium.org
Amount of time between subsequent SessionService Save() operations (aka
updates to session data).
Periods longer than 10 minutes are grouped together; see SaveLongPeriod for
resolution.
jeremy@chromium.org
sky@chromium.org
TabClosedPeriod, but specifically to provide a clearer breakdown of samples
in the 10 minutes - 8 hours range.
jeremy@chromium.org
sky@chromium.org
Milliseconds between subsequent Save() operations due to a tab being closed.
michaeln@chromium.org
The result (success, failure, or database recreated) of trying to open the
LevelDB database for sessionStorage.
Deprecated in Chrome 30. Use Search.DefaultSearchProviderType instead.
Please list the metric's owners. Add more owner tags as needed.
The id of the default search engine domain that is specified in user
preferences when a profile is loaded.
gab@chromium.org
Whether the SettingsEnforcement group was successfully determined from the
field trial or if it had to revert to the hardcoded default.
gab@chromium.org
The amount of time it took to run PrefHashFilter::FilterOnLoad on startup.
gab@chromium.org
The amount of time it took to run PrefHashFilter::FilterSerializeData on the
UI thread prior to writing the Preferences file to disk. Only logged when
PrefHashFilter::FilterSerializeData actually had work to do.
mpearson@chromium.org
Whether or not the home page user preference is set to the default NTP value
when a profile is loaded. This is only logged if the home button is shown.
csharp@chromium.org
gab@chromium.org
Logged on profile load. Indicates whether the hashes dictionary for this
profile is trusted.
Deprecated in Chrome 30. Replaced by Settings.HomePageEngineType.
Please list the metric's owners. Add more owner tags as needed.
The id of the home page domain that is specified in user preferences when a
profile is loaded.
mpearson@chromium.org
Tries to pretend the home page URL is a search URL, and records the search
engine type of that URL by comparing the TLD+1 of the home page URL with
those of the different known search engines. Recorded when a profile is
opened, if a home page URL has been set. Note that at least one profile is
opened on startup.
Deprecated 08/05/2013. Replaced by
Settings.GivenShowHomeButton_HomePageIsNewTabPage.
Please list the metric's owners. Add more owner tags as needed.
Whether or not the home page user preference is set to the default NTP value
when a profile is loaded.
Please list the metric's owners. Add more owner tags as needed.
The value of the home-page-is-new-tab-page pref when pulled down from sync
to update an out-of-sync local pref store.
Please list the metric's owners. Add more owner tags as needed.
The value of the home-page-is-new-tab-page pref when pushed up to sync from
a change made locally.
csharp@chromium.org
gab@chromium.org
Logged on first run when generating the Preferences file from
master_preferences. True if serializing the generated Preferences file to
disk was successful, false otherwise. Note: this event does not occur if
there is no master_preferences file on first run.
gab@chromium.org
The size (in kilobytes) of the JSON settings read from disk on startup.
Suffixed with the name of the corresponding JSON file.
Deprecated 02/2015. Replaced by Settings.JsonDataReadSizeKilobytes.
gab@chromium.org
The size of the JSON settings content about to be written to disk in
kilobytes. Suffixed with the name of the JSON file being written to disk.
raymes@chromium.org
The number of writes of a JSON file that occur in every 5 minute period of
running Chrome. Suffixed with the name of the corresponding JSON file.
csharp@chromium.org
gab@chromium.org
Whether, while loading a profile, any preference hashes were migrated from
Local State to either Preferences or Protected Preferences.
mpearson@chromium.org
Tries to pretend pinned tab URLs are search URLs, and records the search
engine types of those URLs by comparing the TLD+1s of the URLs with those of
the different known search engines. Recorded when a profile is opened, if
there are pinned tabs. Note that at least one profile is opened on startup.
mpearson@chromium.org
The number of pinned tabs opened when a profile is loaded.
rkaplow@chromium.org
The amount of time that elapsed during RegisterProfilePrefs.
mpearson@chromium.org
Whether or not the home button is enabled in user preferences when a profile
is loaded.
mpearson@chromium.org
The enabled state of the Home button pref when pulled down from sync to
update an out-of-sync local pref store.
mpearson@chromium.org
The enabled state of the Home button pref when pushed up to sync from a
change made locally.
Deprecated in Chrome 30. Replaced by Settings.StartupPageEngineTypes.
Please list the metric's owners. Add more owner tags as needed.
The ids of startup page domains that are specified in user preferences when
a profile is loaded.
mpearson@chromium.org
Tries to pretend the startup page URLs are search URLs, and records the
search engine types of those URLs by comparing the TLD+1s of the URLs with
those of the different known search engines. Recorded when a profile is
opened, if startup page URLs have been set. Note that at least one profile
is opened on startup.
mpearson@chromium.org
The startup page settings when a profile is loaded.
mpearson@chromium.org
The startup page setting when pulled down from sync to update an out-of-sync
local pref store.
mpearson@chromium.org
The startup page setting when pushed up to sync from a change made locally.
mpearson@chromium.org
The number of URLs to be loaded on startup when a profile is loaded, if the
startup page setting is set to load URLs.
mad@chromium.org
The startup URLs pref migration steps.
mad@chromium.org
The time elapsed in milliseconds in between startup URLs pref migration. A
value of 0 indicates that the last migration time was in the future due to
e.g. an incorrect system time.
gab@chromium.org
The id of a tracked preference whose value has been changed since the last
time Chrome set it.
gab@chromium.org
The id of a tracked preference whose value has been cleared since the last
time Chrome set it.
gab@chromium.org
The id of a tracked preference whose last value isn't known. We may be just
starting to track the preference, or local state may have been changed
outside of Chrome. This should only happen once per pref per profile.
Deprecated 2014-07.
gab@chromium.org
Logs the tracked preference id when it is migrated to the new MAC algorithm.
This should only happen once per pref per profile.
gab@chromium.org
The id of a tracked preference whose value has not changed since the last
time Chrome set it, but which was last set using a legacy device ID. Each
user should report this at most once per preference id and immediately be
migrated to the latest hashing model.
gab@chromium.org
The id of a tracked preference which was initialized despite the absence of
a MAC as its value was NULL.
gab@chromium.org
The id of a tracked preference which was reset by Chrome.
Deprecated 2014-06.
gab@chromium.org
The version of a PrefHashStore, reported once for each alternate
PrefHashStore (not associated to the default profile) from a delayed task on
startup.
Deprecated 2014-06.
gab@chromium.org
The previous version of an alternate PrefHashStore (not associated to the
default profile) that was updated from a delayed task on startup. This
should match Settings.TrackedPreferencesAlternateStoreVersion fairly closely
for all versions but VERSION_LATEST which should never be reported here.
Deprecated 2014-02 in favor of
Settings.TrackedPreferencesAlternateStoreVersionUpdatedFrom.
gab@chromium.org
Preference tracking was initialized for an unloaded profile. This should
happen at most once per profile.
gab@chromium.org
Whether settings enforcement was cancelled for a machine joined to a domain.
Reported once per session on browser startup (note: this histogram was
disabled for part of M40).
gab@chromium.org
The id of a tracked preference which was initialized despite the absence of
a MAC as the current MACs are trusted, infering that this is a newly tracked
pref.
gab@chromium.org
The id of a tracked preference whose value has not changed since the last
time Chrome set it.
gab@chromium.org
The id of a tracked preference which Chrome would have reset had the config
allowed it.
gab@chromium.org
The number of items that had changed in a dictionary pref when
Settings.TrackedPreferenceChanged is reported for that pref.
wjmaclean@chromium.org
Tracks migration to per-partition zoom-level preferences during profile
initialization.
mad@chromium.org
Counts the number of times the user clicked on the No Thanks button of the
settings reset bubble before clicking on the Reset button in the same Chrome
session.
horo@chromium.org
A survival time of RenderProcessHostImpl for the In-renderer Shared Worker
from when FastShutdownIfPossible() is called.
horo@chromium.org
The lifetime of a SharedWorkerHost. This roughly corresponds to the lifetime
of SharedWorker.
horo@chromium.org
The time from the creation of SharedWorkerHost until when WorkerScriptLoaded
is called.
horo@chromium.org
The time from the creation of SharedWorkerHost until when
WorkerScriptLoadFailed is called.
davidben@chromium.org
The time it takes for the ShortcutsProvider to perform a query after the
user has typed N characters.
mlerman@chromium.org
Tracks user interactions as they sign in through a flow. The suffix of the
histogram indicates what UI widget or application flow triggered the signin
flow.
mlerman@chromium.org
Track when chrome successfully adds an account. Failures are not tracked.
guohui@chromium.org
Track how a user interfacts with the android signin promo.
mlerman@chromium.org
Log the type of GAIA authentication error that occur whenever the error
state changes.
mlerman@chromium.org
Track if the profile sign in took place during First Run or not. Logged at
signin time. True means signin took place during First Run, False means
anytime after.
mlerman@chromium.org
Track how many minutes of local system time elapsed from when Chrome was
installed to when Signin occured for this profile.
noms@chromium.org
Count of the ways users interact with the confirmation dialogs of the new
web based sign in to Chrome flow (accessed via the one click signin).
noms@chromium.org
Tracks events related to the reauthentication Gaia page.
Deprecated 2014-09 because chrome no longer tries to reconcile from the
cookie jar to the browser.
mlerman@chromium.org
How many accounts were added to the browser's token service because they
were in the cookie jar.
mlerman@chromium.org
How many accounts were added to the cookie jar because they were in the
browser's token service.
mlerman@chromium.org
Records whether all external connections have been successfully checked (a
value of "true") or not ("false") when the reconciler
attempts to perform MergeSession.
mlerman@chromium.org
After execution of the account reconcilor, compares the primary account in
the token service to the primary GAIA account of the cookie jar.
mlerman@chromium.org
Records the time it took to successfully check all external connections
whenever the reconciler performs a reconciliation.
mlerman@chromium.org
Records the time it took to check only a portion of external connections
whenever the reconciler performs a reconciliation. This means that either a
network error occured while checking some sites or the site did not respond
before the check timeout.
mlerman@chromium.org
How many accounts were removed from the cookie jar because they were not in
the browser's token service.
pavely@chromium.org
Track when chrome successfully sends RefreshTokenAnnotationRequest.
mlerman@chromium.org
Track how many minutes of real time (not browser active time) elapsed
between profile signin and signout.
noms@chromium.org
Logs the original source that displayed the signin or reauth Gaia page,
before the page is displayed.
mlerman@chromium.org
Track how a profile gets signed out.
anthonyvd@chromium.org
mlerman@chromium.org
How long a browsing session was measured to be. Logged when a Browser window
becomes active if the previous activation was longer than the minimum
configured in the "CrossDevicePromo" experiment. Desktop only.
anthonyvd@chromium.org
mlerman@chromium.org
How often browsers are considered activated, which in turn triggers the
CrossDevicePromo. Logged every time a Browser window becomes active. We need
this to estimate QPS for RPC calls. Desktop only.
anthonyvd@chromium.org
mlerman@chromium.org
The reasons for which a profile is or is not eligible for the Desktop Cross
Device Sign In Promo. Logged every time a new Browsing session is detected
as part of a Browser window becoming active. Desktop only.
anthonyvd@chromium.org
mlerman@chromium.org
Tracks if profiles initialized the XDevicePromo, and if not, why. Logged at
Profile startup and (if not initialized then) when a new browsing session is
detected during Browser window activation. Desktop only.
gavinp@chromium.org
Whether or not the CRC was checked at the moment when the last reference to
a read-only entry stream is closed.
gavinp@chromium.org
The time from the creation of the simple cache backend until the index has
been loaded from disk.
gavinp@chromium.org
The time from the creation of the simple cache backend until the index fails
to load.
gavinp@chromium.org
Whether, upon creation of a new cache entry, the file for stream 2 was
omitted since that stream was empty.
gavinp@chromium.org
For entry creation operations that were sent to the disk, the result of
creation.
gavinp@chromium.org
The time, in ms, spent creating a new entry on disk.
gavinp@chromium.org
Whether, upon opening of an existing cache entry, stream 2 was empty and the
file for that stream was therefore removed.
gavinp@chromium.org
At the time that operations are run, the number of pending operations on a
particular entry.
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
gavinp@chromium.org
The number of entries to be erased in an eviction.
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
gavinp@chromium.org
The result of an eviction.
gavinp@chromium.org
The number of bytes to be erased in an eviction.
gavinp@chromium.org
The amount of memory freed in an eviction.
gavinp@chromium.org
The size of the cache after running an eviction.
gavinp@chromium.org
The size of the cache after running an eviction.
gavinp@chromium.org
Time spent completing an eviction.
gavinp@chromium.org
Time spent selecting entries for eviction.
gavinp@chromium.org
The maximum limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (This
is the highest value we could raise the current limit to if we liked.)
gavinp@chromium.org
The current limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (We can
raise this to the maximum limit if we like, without root access.)
gavinp@chromium.org
The result of trying to get the file descriptor limit. Emitted each time
the browser is launched.
gavinp@chromium.org
The number of open entries across all caches backed by the Simple Cache. An
entry is opened whenever a caller asks to open it to read or write cache
data, and remains open until the last caller asks to close it. Logged
whenever an entry is opened or closed.
gavinp@chromium.org
The size of the header stream of a Simple Cache entry, emitted every time
the headers are written or rewritten.
gavinp@chromium.org
How the header size has changed in a Simple Cache entry, emitted every time
a write operation occurs on the header stream. (This includes the initial
write, rewrites, and other writes that we couldn't classify.)
gavinp@chromium.org
The absolute size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
gavinp@chromium.org
The relative size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
gavinp@chromium.org
The absolute size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
gavinp@chromium.org
The relative size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
gavinp@chromium.org
For each index load, whether the index file was corrupt.
gavinp@chromium.org
The number of entries in a newly created index file.
gavinp@chromium.org
Number of entries loaded from the index file on start.
gavinp@chromium.org
Number of entries restored from disk when there was no index or the index
was corrupted.
gavinp@chromium.org
The state the index file is at when an attempt is made to load from it.
gavinp@chromium.org
At the time of index initialization, the number of enqueued jobs awaiting
index initialization.
gavinp@chromium.org
The method used to initialize the simple cache index.
gavinp@chromium.org
Time (as measured on the worker pool) spent loading the index file.
gavinp@chromium.org
The number of entries written to the index on a flush.
gavinp@chromium.org
Time (as measured on the worker pool) spent restoring the index file by
iterating directory entries.
gavinp@chromium.org
The interval between index saves, for apps in the background.
gavinp@chromium.org
The interval between index saves, for apps in the foreground.
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
background, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
foreground, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
gavinp@chromium.org
For each call to OpenEntry, whether the key on disk matched the request key.
gavinp@chromium.org
For each file in the Simple Cache, the percentage of disk space used by the
cluster loss, the unused disk space in the last 4096 byte cluster of the
file.
gavinp@chromium.org
For each file in the Simple Cache, the number of bytes in the last 4096 byte
cluster when the entry is saved to disk.
gavinp@chromium.org
At the time that an entry is opened, the state of that entry in the index.
gavinp@chromium.org
For each Read operation, whether it could have been issued in parallel of a
previous Read operation.
gavinp@chromium.org
The outcome of Entry::ReadData in the simple cache.
gavinp@chromium.org
For each EOFRecord found with a valid magic number, indicates if the record
also contains a CRC.
gavinp@chromium.org
The result, at the synchronous layer, of checking the EOF record of a cache
entry.
gavinp@chromium.org
The result, at the synchronous layer, of closing a cache entry.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not yet initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has already initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has not yet initialized.
gavinp@chromium.org
The age of the entry (time since last modified), when opened at the
synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has already initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has not yet initialized.
gavinp@chromium.org
The result, at the synchronous layer, of writing to a cache entry.
gavinp@chromium.org
Shows whether a write operation depends on the previous operation in queue
particularly in the aspect of its possibility to run in parallel.
Replaced 2013/09/03 by WriteResult2, which adds "fast empty
return", which previously showed up as "success".
gavinp@chromium.org
The outcome of Entry::WriteData in the simple cache.
gavinp@chromium.org
The outcome of Entry::WriteData in the simple cache.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Whether or not the CRC was checked at the moment when the last reference to
a read-only entry stream is closed.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The time from the creation of the simple cache backend until the index has
been loaded from disk.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The time from the creation of the simple cache backend until the index fails
to load.
rdsmith@chromium.org
The time to access (open and read headers from all files) the cache entry on
disk.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For entry creation operations that were sent to the disk, the result of
creation.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The time, in ms, spent creating a new entry on disk.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
At the time that operations are run, the number of pending operations on a
particular entry.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The number of entries to be erased in an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result of an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The number of bytes to be erased in an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The amount of memory freed in an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The size of the cache after running an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The size of the cache after running an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Time spent completing an eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Time spent selecting entries for eviction.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The maximum limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (This
is the highest value we could raise the current limit to if we liked.)
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The current limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (We can
raise this to the maximum limit if we like, without root access.)
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result of trying to get the file descriptor limit. Emitted each time
the browser is launched.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The number of open entries across all caches backed by the Simple Cache. An
entry is opened whenever a caller asks to open it to read or write cache
data, and remains open until the last caller asks to close it. Logged
whenever an entry is opened or closed.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The size of the header stream of a Simple Cache entry, emitted every time
the headers are written or rewritten.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
How the header size has changed in a Simple Cache entry, emitted every time
a write operation occurs on the header stream. (This includes the initial
write, rewrites, and other writes that we couldn't classify.)
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The absolute size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The relative size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The absolute size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The relative size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
Whether or not the CRC was checked at the moment when the last reference to
a read-only entry stream is closed.
gavinp@chromium.org
The time from the creation of the simple cache backend until the index has
been loaded from disk.
gavinp@chromium.org
The time from the creation of the simple cache backend until the index fails
to load.
gavinp@chromium.org
Whether, upon creation of a new cache entry, the file for stream 2 was
omitted since that stream was empty.
gavinp@chromium.org
For entry creation operations that were sent to the disk, the result of
creation.
gavinp@chromium.org
The time, in ms, spent creating a new entry on disk.
gavinp@chromium.org
Whether, upon opening of an existing cache entry, stream 2 was empty and the
file for that stream was therefore removed.
gavinp@chromium.org
At the time that operations are run, the number of pending operations on a
particular entry.
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
gavinp@chromium.org
The number of entries to be erased in an eviction.
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
gavinp@chromium.org
The result of an eviction.
gavinp@chromium.org
The number of bytes to be erased in an eviction.
gavinp@chromium.org
The amount of memory freed in an eviction.
gavinp@chromium.org
The size of the cache after running an eviction.
gavinp@chromium.org
The size of the cache after running an eviction.
gavinp@chromium.org
Time spent completing an eviction.
gavinp@chromium.org
Time spent selecting entries for eviction.
gavinp@chromium.org
The maximum limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (This
is the highest value we could raise the current limit to if we liked.)
gavinp@chromium.org
The current limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (We can
raise this to the maximum limit if we like, without root access.)
gavinp@chromium.org
The result of trying to get the file descriptor limit. Emitted each time
the browser is launched.
gavinp@chromium.org
The number of open entries across all caches backed by the Simple Cache. An
entry is opened whenever a caller asks to open it to read or write cache
data, and remains open until the last caller asks to close it. Logged
whenever an entry is opened or closed.
gavinp@chromium.org
The size of the header stream of a Simple Cache entry, emitted every time
the headers are written or rewritten.
gavinp@chromium.org
How the header size has changed in a Simple Cache entry, emitted every time
a write operation occurs on the header stream. (This includes the initial
write, rewrites, and other writes that we couldn't classify.)
gavinp@chromium.org
The absolute size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
gavinp@chromium.org
The relative size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
gavinp@chromium.org
The absolute size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
gavinp@chromium.org
The relative size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
gavinp@chromium.org
For each index load, whether the index file was corrupt.
gavinp@chromium.org
The number of entries in a newly created index file.
gavinp@chromium.org
Number of entries loaded from the index file on start.
gavinp@chromium.org
Number of entries restored from disk when there was no index or the index
was corrupted.
gavinp@chromium.org
The state the index file is at when an attempt is made to load from it.
gavinp@chromium.org
At the time of index initialization, the number of enqueued jobs awaiting
index initialization.
gavinp@chromium.org
The method used to initialize the simple cache index.
gavinp@chromium.org
Time (as measured on the worker pool) spent loading the index file.
gavinp@chromium.org
The number of entries written to the index on a flush.
gavinp@chromium.org
Time (as measured on the worker pool) spent restoring the index file by
iterating directory entries.
gavinp@chromium.org
The interval between index saves, for apps in the background.
gavinp@chromium.org
The interval between index saves, for apps in the foreground.
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
background, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
foreground, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
gavinp@chromium.org
For each call to OpenEntry, whether the key on disk matched the request key.
gavinp@chromium.org
For each file in the Simple Cache, the percentage of disk space used by the
cluster loss, the unused disk space in the last 4096 byte cluster of the
file.
gavinp@chromium.org
For each file in the Simple Cache, the number of bytes in the last 4096 byte
cluster when the entry is saved to disk.
gavinp@chromium.org
At the time that an entry is opened, the state of that entry in the index.
gavinp@chromium.org
For each Read operation, whether it could have been issued in parallel of a
previous Read operation.
gavinp@chromium.org
The outcome of Entry::ReadData in the simple cache.
gavinp@chromium.org
For each EOFRecord found with a valid magic number, indicates if the record
also contains a CRC.
gavinp@chromium.org
The result, at the synchronous layer, of checking the EOF record of a cache
entry.
gavinp@chromium.org
The result, at the synchronous layer, of closing a cache entry.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not yet initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has already initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has not yet initialized.
gavinp@chromium.org
The age of the entry (time since last modified), when opened at the
synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has already initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has not yet initialized.
gavinp@chromium.org
The result, at the synchronous layer, of writing to a cache entry.
gavinp@chromium.org
Shows whether a write operation depends on the previous operation in queue
particularly in the aspect of its possibility to run in parallel.
Replaced 2013/09/03 by WriteResult2, which adds "fast empty
return", which previously showed up as "success".
gavinp@chromium.org
The outcome of Entry::WriteData in the simple cache.
gavinp@chromium.org
The outcome of Entry::WriteData in the simple cache.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For each index load, whether the index file was corrupt.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The number of entries in a newly created index file.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Number of entries loaded from the index file on start.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Number of entries restored from disk when there was no index or the index
was corrupted.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The state the index file is at when an attempt is made to load from it.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
At the time of index initialization, the number of enqueued jobs awaiting
index initialization.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The method used to initialize the simple cache index.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Time (as measured on the worker pool) spent loading the index file.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The number of entries written to the index on a flush.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Time (as measured on the worker pool) spent restoring the index file by
iterating directory entries.
Deprecated 07/2013, and replaced by IndexFileStateOnLoad.
gavinp@chromium.org
For each index load, whether the index file was stale.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The interval between index saves, for apps in the background.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The interval between index saves, for apps in the foreground.
Deprecated 2013-05 in favour of
SimpleCache.SimpleIndexWriteToDiskTime.Background and
SimpleCache.SimpleIndexWriteToDiskTime.Foreground.
gavinp@chromium.org
The amount of time spend writing the index file to disk, measured starting
at the beginning of the write on the callback thread, and calculated using
the completion time on the worker pool.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
background, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
foreground, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For each call to OpenEntry, whether the key on disk matched the request key.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For each file in the Simple Cache, the percentage of disk space used by the
cluster loss, the unused disk space in the last 4096 byte cluster of the
file.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For each file in the Simple Cache, the number of bytes in the last 4096 byte
cluster when the entry is saved to disk.
gavinp@chromium.org
Whether or not the CRC was checked at the moment when the last reference to
a read-only entry stream is closed.
gavinp@chromium.org
The time from the creation of the simple cache backend until the index has
been loaded from disk.
gavinp@chromium.org
The time from the creation of the simple cache backend until the index fails
to load.
gavinp@chromium.org
Whether, upon creation of a new cache entry, the file for stream 2 was
omitted since that stream was empty.
gavinp@chromium.org
For entry creation operations that were sent to the disk, the result of
creation.
gavinp@chromium.org
The time, in ms, spent creating a new entry on disk.
gavinp@chromium.org
Whether, upon opening of an existing cache entry, stream 2 was empty and the
file for that stream was therefore removed.
gavinp@chromium.org
At the time that operations are run, the number of pending operations on a
particular entry.
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
gavinp@chromium.org
The size of the cache at the beginning of an eviction.
gavinp@chromium.org
The number of entries to be erased in an eviction.
The maximum allowed size of the cache at the beginning of an eviction.
gavinp@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
gavinp@chromium.org
The result of an eviction.
gavinp@chromium.org
The number of bytes to be erased in an eviction.
gavinp@chromium.org
The amount of memory freed in an eviction.
gavinp@chromium.org
The size of the cache after running an eviction.
gavinp@chromium.org
The size of the cache after running an eviction.
gavinp@chromium.org
Time spent completing an eviction.
gavinp@chromium.org
Time spent selecting entries for eviction.
gavinp@chromium.org
The maximum limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (This
is the highest value we could raise the current limit to if we liked.)
gavinp@chromium.org
The current limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (We can
raise this to the maximum limit if we like, without root access.)
gavinp@chromium.org
The result of trying to get the file descriptor limit. Emitted each time
the browser is launched.
gavinp@chromium.org
The number of open entries across all caches backed by the Simple Cache. An
entry is opened whenever a caller asks to open it to read or write cache
data, and remains open until the last caller asks to close it. Logged
whenever an entry is opened or closed.
gavinp@chromium.org
The size of the header stream of a Simple Cache entry, emitted every time
the headers are written or rewritten.
gavinp@chromium.org
How the header size has changed in a Simple Cache entry, emitted every time
a write operation occurs on the header stream. (This includes the initial
write, rewrites, and other writes that we couldn't classify.)
The absolute size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
gavinp@chromium.org
The relative size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
gavinp@chromium.org
The absolute size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
gavinp@chromium.org
The relative size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
gavinp@chromium.org
For each index load, whether the index file was corrupt.
gavinp@chromium.org
The number of entries in a newly created index file.
gavinp@chromium.org
Number of entries loaded from the index file on start.
gavinp@chromium.org
Number of entries restored from disk when there was no index or the index
was corrupted.
gavinp@chromium.org
The state the index file is at when an attempt is made to load from it.
gavinp@chromium.org
At the time of index initialization, the number of enqueued jobs awaiting
index initialization.
gavinp@chromium.org
The method used to initialize the simple cache index.
gavinp@chromium.org
Time (as measured on the worker pool) spent loading the index file.
gavinp@chromium.org
The number of entries written to the index on a flush.
gavinp@chromium.org
Time (as measured on the worker pool) spent restoring the index file by
iterating directory entries.
gavinp@chromium.org
The interval between index saves, for apps in the background.
gavinp@chromium.org
The interval between index saves, for apps in the foreground.
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
background, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
gavinp@chromium.org
The amount of time spend writing the index file to disk, for apps in the
foreground, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
gavinp@chromium.org
For each call to OpenEntry, whether the key on disk matched the request key.
gavinp@chromium.org
For each file in the Simple Cache, the percentage of disk space used by the
cluster loss, the unused disk space in the last 4096 byte cluster of the
file.
gavinp@chromium.org
For each file in the Simple Cache, the number of bytes in the last 4096 byte
cluster when the entry is saved to disk.
gavinp@chromium.org
At the time that an entry is opened, the state of that entry in the index.
gavinp@chromium.org
For each Read operation, whether it could have been issued in parallel of a
previous Read operation.
gavinp@chromium.org
The outcome of Entry::ReadData in the simple cache.
gavinp@chromium.org
For each EOFRecord found with a valid magic number, indicates if the record
also contains a CRC.
gavinp@chromium.org
The result, at the synchronous layer, of checking the EOF record of a cache
entry.
gavinp@chromium.org
The result, at the synchronous layer, of closing a cache entry.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not yet initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has already initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has not yet initialized.
gavinp@chromium.org
The age of the entry (time since last modified), when opened at the
synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has already initialized.
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has not yet initialized.
gavinp@chromium.org
The result, at the synchronous layer, of writing to a cache entry.
gavinp@chromium.org
Shows whether a write operation depends on the previous operation in queue
particularly in the aspect of its possibility to run in parallel.
The outcome of Entry::WriteData in the simple cache.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
At the time that an entry is opened, the state of that entry in the index.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For each Read operation, whether it could have been issued in parallel of a
previous Read operation.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The outcome of Entry::ReadData in the simple cache.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
For each EOFRecord found with a valid magic number, indicates if the record
also contains a CRC.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, of checking the EOF record of a cache
entry.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, of closing a cache entry.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not yet initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has already initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry when the index has not yet initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The age of the entry (time since last modified), when opened at the
synchronous layer.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has already initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer when the index has not initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has already initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry when the index has not yet initialized.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The result, at the synchronous layer, of writing to a cache entry.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
Shows whether a write operation depends on the previous operation in queue
particularly in the aspect of its possibility to run in parallel.
Deprecated 2013-08 in favor of cache type specific version (App or Http).
gavinp@chromium.org
The outcome of Entry::WriteData in the simple cache.
alemate@chromium.org
Events in reqests processing of IP-based SimpleGeolocation.
alemate@chromium.org
Http response codes in IP-based SimpleGeolocation.
alemate@chromium.org
The time elapsed between the sending of the first API request and the time
the final (failed) response was recorded. Includes all retries.
alemate@chromium.org
The time elapsed between the sending of the first API request and the time
the final (successfull) response was recorded. Includes all retries.
alemate@chromium.org
Result of SimpleGeolocationRequest.
alemate@chromium.org
Number of retries until the final response was recorded.
creis@chromium.org
The count of all network responses received by a renderer. Each response is
corresponding to one URL requested by a renderer. Incremented when the first
network packet of a response of this type is received.
creis@chromium.org
The count of all current BrowsingInstances. Recorded once per UMA ping.
creis@chromium.org
The count of all renderer processes, including WebUI and extensions.
Recorded once per UMA ping.
creis@chromium.org
The upper bound of the predicted renderer process count if we isolated all
sites, subject to the process limit. Recorded once per UMA ping.
creis@chromium.org
The lower bound of the predicted renderer process count if we isolated all
sites, subject to the process limit. Happens to be the number of unique
sites. Recorded once per UMA ping.
creis@chromium.org
The predicted renderer process count if we isolated all sites and if there
were no process limit. Recorded once per UMA ping.
creis@chromium.org
The predicted total process count if we isolated all sites, subject to the
process limit. Recorded once per UMA ping.
creis@chromium.org
The upper bound of the predicted renderer process count if we isolated only
HTTPS (not HTTP) sites, subject to the process limit. Recorded once per UMA
ping.
creis@chromium.org
The lower bound of the predicted renderer process count if we isolated only
HTTPS (not HTTP) sites, subject to the process limit. Happens to be the
number of isolated sites. Recorded once per UMA ping.
creis@chromium.org
The predicted renderer process count if we isolated only HTTPS (not HTTP)
sites and if there were no process limit. Recorded once per UMA ping.
creis@chromium.org
The predicted total process count if we isolated only HTTPS (not HTTP)
sites, subject to the process limit. Recorded once per UMA ping.
creis@chromium.org
The number of bytes in the first network packet for a response with headers
that imply potential illegal cross-site access. Recorded when the first
network packet of a response of this type is received.
creis@chromium.org
The count of blocked cross-site document responses due to having HTML
content type header and contents sniffed as HTML. Sampled with value of 1
when the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their HTML contents. Sampled with value
1 when the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.) among blocked
cross-site document responses due to their HTML contents. Sampled with a
resource type (0-14) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having HTML content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having HTML content type and nosniff
headers. Sampled with a resource type (0-14) when the first network packet
of a response of this type is received.
creis@chromium.org
The count of not blocked responses despite having an HTML content type
header due to the failure of content sniffing. Sampled with value 1 when the
first network packet of a response of this type is received.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses. Sampled with value 1 when the first network packet of a response
of this type is received.
creis@chromium.org
The count of blocked cross-site document responses due to having JSON
content type header and contents sniffed as JSON. Sampled with value 1 when
the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their JSON contents. Sampled with value
1 when the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their JSON contents. Sampled with a
resource type (0-14) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having JSON content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having JSON content type and nosniff
headers. Sampled with a resource type (0-14) when the first network packet
of a response of this type is received.
creis@chromium.org
The count of not blocked responses despite having an JSON content type
header due to the failure of content sniffing. Sampled with value 1 when the
first network packet of a response of this type is received.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses with a JSON content type header. Sampled with value 1 when the
first network packet of a response of this type is received.
creis@chromium.org
MIME type codes for content type header values of potentially cross-site
document responses, excluding same-site or not http(s) urls. Sampled with a
MIME type code (0-4) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of blocked cross-site document responses due to having Plain
content type header and contents sniffed as HTML. Sampled with value 1 when
the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
responses due to their Plain.HTML contents. Sampled with value 1 when the
first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.HTML contents. Sampled with
a resource type (0-14) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of blocked cross-site document responses due to having Plain
content type header and contents sniffed as JSON. Sampled with value 1 when
the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their Plain.JSON contents. Sampled with
value 1 when the first network packet of a response of this type is
received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.JSON contents. Sampled with
a resource type (0-14) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having Plain content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having Plain content type and nosniff
header. Sampled with a resource type (0-14) when the first network packet of
a response of this type is received.
creis@chromium.org
The count of not blocked responses despite having an Plain content type
header due to the failure of content sniffing. Sampled with value 1 when the
first network packet of a response of this type is received.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses with a Plain content type header. Sampled with value 1 when the
first network packet of a response of this type is received.
creis@chromium.org
The count of blocked cross-site document responses due to having Plain
content type header and contents sniffed as XML. Sampled with value 1 when
the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their Plain.XML contents. Sampled with
value 1 when the first network packet of a response of this type is
received.
creis@chromium.org
The count of responses with renderable HTTP status codes sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.XML contents. Sampled with
a resource type (0-14) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of blocked cross-site document responses due to having XML content
type header and contents sniffed as XML. Sampled with value 1 when the first
network packet of a response of this type is received.
creis@chromium.org
The count of responses with nonrenderable HTTP status codes among blocked
cross-site document responses due to their XML contents. Sampled with value
1 when the first network packet of a response of this type is received.
creis@chromium.org
The count of responses with renderable HTTP status codes sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their XML contents. Sampled with a
resource type (0-14) when the first network packet of a response of this
type is received.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having XML content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having XML content type and nosniff
headers. Sampled with a resource type (0-14) when the first network packet
of a response of this type is received.
creis@chromium.org
The count of not blocked responses despite having an XML content type header
due to the failure of content sniffing. Sampled with value 1 when the first
network packet of a response of this type is received.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses with an XML content type. Sampled with value 1 when the first
network packet of a response of this type is received.
mad@chromium.org
Whether the software reporter cleaner tool has finished execution, otherwise
assume it has crashed.
mad@chromium.org
Whether a reboot happened since the software reporter cleaner tool has
finished execution with a pre-reboot exit code.
mad@chromium.org
How long it took to run the software reporter cleaner tool.
mad@chromium.org
The build version of the software reporter cleaner tool.
mad@chromium.org
Whether there was an error reading the registry key containing UwS found by
the Software Removal Tool.
mad@chromium.org
The result of the most recent SRT log upload.
mad@chromium.org
As SoftwareReporter.MinorVersion, but a double word combination of the other
components of the version of the software reporter. The high word is the
first component when there are more than one, and the low word is either the
second or third one, depending if there are at least 3, or 4 components.
mad@chromium.org
The last component of the version of the software reporter that was executed
so we can identify when users are not getting their component updated as
quickly as we expect it.
mad@chromium.org
Usage of the Software Removal Tool (SRT) Prompt.
mad@chromium.org
The registration and execution steps for the software reporter.
mad@chromium.org
The total count of SRT log upload failures experienced by this machine for
all time. This value is reported at startup by Chrome and is capped at 64.
mad@chromium.org
The longest run of upload failures logged by SRT runs. This value is
reported at startup by Chrome and is capped at 64.
mad@chromium.org
The total count of successful SRT log uploads experienced by this machine
for all time. This value is reported at startup by Chrome and is capped at
64.
groby@chromium.org
rlp@chromium.org
Whether the user has opted in to asking Google for spelling suggestions.
Recorded both when spelling is initialized and when the preference is
changed.
Moved to Sqlite.Error.AppCache in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the appcache db.
shess@chromium.org
Error which prevented database close.
Moved to Sqlite.Error.Cookie in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the cookie db.
Moved to Sqlite.Error.DatabaseTracker in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the websqldb tracker db.
shess@chromium.org
Annotations for which bits of sql::MetaTable::CheckDeprecated() fire.
Moved to Sqlite.Error.DomainBoundCerts in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the domain-bound certs db.
Moved to Sqlite.Error.DomStorageDatabase in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the domstorage db.
shess@chromium.org
SQLite extended error codes.
Replaced 5/14/2013 by expanded Sqlite.Error histogram.
Please list the metric's owners. Add more owner tags as needed.
SQLite extended SQLITE_IOERR codes for all databases.
Moved to Sqlite.Error.History in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the history db.
shess@chromium.org
Error which prevented database open.
shess@chromium.org
Error from first read of the database.
Moved to Sqlite.Error.Quota in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the quota db.
shess@chromium.org
Errors attempting to Raze() database.
shess@chromium.org
Errors on second attempt to Raze() database.
shess@chromium.org
Errors truncating database for Raze().
shess@chromium.org
Records specific failure and success cases in sql::Recovery implementation,
to determine which cases (if any) might be worth writing additional
automated recovery code for, versus which should lead to clearing databases.
shess@chromium.org
Error from sqlite3_backup_init() in sql::Recovery.
shess@chromium.org
Error from sqlite3_backup_step() in sql::Recovery.
peria@chromium.org
shess@chromium.org
Size in kilobytes of pre-existing database at startup.
Moved to Sqlite.Error.Text in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the full text db.
Moved to Sqlite.Error.Thumbnail in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the thumbnail db.
shess@chromium.org
Version of pre-existing database at startup.
Moved to Sqlite.Error.Web in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the web db.
lgarron@chromium.org
Keeps track of various insecure content events, such as loading an HTTP
script from an HTTPS page.
jam@chromium.org
jamescook@chromium.org
Count of child processes killed because they sent an IPC that couldn't be
properly handled. Categories are the reasons (code locations) for the kills.
kalman@chromium.org
jamescook@chromium.org
Count of extension processes killed because they sent an IPC that couldn't
be properly handled. Categories are the reasons (code locations) for the
kills.
siggi@chromium.org
erikwright@chromium.org
Records the exit code of the browser process (on Windows) from the previous
launch. On crash, the exit code will indicate the exception code of the
crash. This is emitted in stability data with the first report on a
subsequent launch.
siggi@chromium.org
Temporary instrumentation to record the Windows browser's exit path. See
http://crbug.com/412384.
yefim@chromium.org
Percentage of clips with Google related urls (points to internal Google
resources). Logs every time user goes to chrome://bookmarks.
yefim@chromium.org
Percentage of clips with Google related urls within first 20 (points to
internal Google resources). Logs every time user goes to chrome://bookmarks.
yefim@chromium.org
Percentage of clips with images. Logs every time user goes to
chrome://bookmarks.
yefim@chromium.org
Percentage of clips with images within first 20. Logs every time user goes
to chrome://bookmarks.
yefim@chromium.org
Percentage of clips without images or snippets. Logs every time user goes to
chrome://bookmarks.
yefim@chromium.org
Percentage of clips without images or snippets within first 20. Logs every
time user goes to chrome://bookmarks.
michaeln@chromium.org
The number of after-startup tasks that were queued prior to startup
completion and deferred until that time.
michaeln@chromium.org
Time from the process creation until deferred after-startup tasks began
running.
tapted@chromium.org
Time for a newly created browser process to perform the first paint of the
app launcher, when started with the --show-app-list flag and with no
currently running Chrome processes.
tapted@chromium.org
Time for a running browser process to perform the first paint of the app
launcher. Measured from the time a second Chrome process started, which sent
its --show-app-list command line argument to the already-running process and
will soon exit.
chrisha@chromium.org
The number of hard faults incurred in the browser process from startup to
start of the main thread's message loop, not including first runs of the
browser. This is only reported on Windows 7 and greater.
chrisha@chromium.org
The number of hard faults incurred in the browser process from startup to
start of the main thread's message loop on first run. This is only reported
on Windows 7 and greater.
chrisha@chromium.org
If OS support was detected (Windows 7 and greater) indicates whether it was
possible to determine the number of hard faults that have occurred in the
process from startup to start of the main thread's message loop. This can
fail because the underlying call is inherently racy.
jeremy@chromium.org
Time from browser startup to the start of the main thread's message loop.
jeremy@chromium.org
Time from main entry to the start of the main thread's message loop. This
stat is only recorded after 7 minutes of OS uptime to try to mitigate the
variance resulting from Chrome being autostarted.
csharp@chromium.org
gab@chromium.org
jeremy@chromium.org
Time from main entry to the start of the main thread's message loop on first
run. This stat is only recorded after 7 minutes of OS uptime to try to
mitigate the variance resulting from Chrome being autostarted.
jeremy@chromium.org
Time taken to open the initial tab or to restore tabs from previous session.
rkaplow@chromium.org
The amount of time that elapsed during
BrowserProcessImpl::PreMainMessageLoopRun.
jeremy@chromium.org
Time from browser startup to the time the browser window initially becomes
visible.
jeremy@chromium.org
The elapsed time from the ChromeCast application launch to the first video
frame displayed.
jeremy@chromium.org
How long it takes to load the original profile synchronously on the UI
thread.
Removed in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first main frame load of
the first web contents. Uses significantly more buckets, with reduced
ranges.
Moved to Startup.FirstWebContents.MainFrameLoad in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first main frame load of
the first web contents. Uses standard bucket ranges.
Removed in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first non-empty paint of
the first web contents. Uses significantly more buckets, with reduced
ranges.
Moved to Startup.FirstWebContents.NonEmptyPaint in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first non-empty paint of
the first web contents. Uses standard bucket ranges.
pasko@chromium.org
The time from the earliest entry point in the browser process to the moment
the first navigation is committed, i.e. when renderer gets the first byte of
the document.
erikchen@chromium.org
Measure the elapsed time from process launch to the first main frame load of
the first web contents.
erikchen@chromium.org
Measure the elapsed time from process launch to the first non-empty paint of
the first web contents.
jeremy@chromium.org
The elapsed time from the Fling application launch to the first video frame
displayed.
Deprecated 12/2011. Merged into MobileSessionStartType.
jeremy@chromium.org
Whether a startup is a resume (vs a cold start).
jeremy@chromium.org
Time from the main() function in chrome.exe to chrome.dll's main().
jeremy@chromium.org
Time from the process creation to chrome.dll's main().
jeremy@chromium.org
Time from the process creation to executing the main() function in
chrome.exe.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
-[AppControllerMac awakeFromNib].
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
-[AppControllerMac didFinishLaunching:]. At that point, the dock icon will
finish its current animation and stop bouncing.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PostMainMessageLoopStart.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PostProfileInit.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PreMainMessageLoopStart.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PreProfileInit.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
-[AppControllerMac willFinishLaunching:].
rkaplow@chromium.org
The amount of time that elapsed during
ChromeBrowserMainParts::PreMainMessageLoopRunImpl.
rkaplow@chromium.org
The amount of time that elapsed during the first untracked section of
ChromeBrowserMainParts::PreMainMessageLoopRunImpl.
rkaplow@chromium.org
The amount of time that elapsed during the second untracked section of
ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android.
rkaplow@chromium.org
The amount of time that elapsed during the third untracked section of
ChromeBrowserMainParts::PreMainMessageLoopRunImpl. Not written for Android.
Deprecated as of 2/2015.
rkaplow@chromium.org
The amount of time that elapsed during
ChromeBrowserMainParts::PreMainMessageLoopRunImpl.
jeremy@chromium.org
tapted@chromium.org
Time for a newly created browser process to reach the code that starts
showing the app launcher, when started with the --show-app-list flag and
with no currently running Chrome processes.
jeremy@chromium.org
tapted@chromium.org
Time for a running browser process to reach the code that starts showing the
app launcher. Measured from the time a second Chrome process started, which
sent its --show-app-list command line argument to the already-running
process and will soon exit.
jeremy@chromium.org
Time it takes to load bookmarks from disk. This measurement is only sent for
startups that take >10 seconds after an uptime of 7 minutes.
jeremy@chromium.org
Time it takes to finish initialization of the extension service including
loading built-in extensions. This measurement is only sent for startups that
take >10 seconds after an uptime of 7 minutes.
jeremy@chromium.org
Time the final stages of profile initialization taking including
initialization of profile keyed services. This measurement is only sent for
startups that take >10 seconds after an uptime of 7 minutes.
jeremy@chromium.org
Time it takes to load the NSS libraries and initialize it. This measurement
is only sent for startups that take >10 seconds after an uptime of 7
minutes.
jeremy@chromium.org
Time it takes to load preferences from disk. This measurement is only sent
for startups that take >10 seconds after an uptime of 7 minutes.
jeremy@chromium.org
Time it takes to initialize the ProfileIOData object - this includes
initialization of the cookie store. This measurement is only sent for
startups that take >10 seconds after an uptime of 7 minutes.
jeremy@chromium.org
Time it takes to load the safe browsing database from disk. This measurement
is only sent for startups that take >10 seconds after an uptime of 7
minutes.
jeremy@chromium.org
Time it takes to initialize the safe browsing service. This measurement is
only sent for startups that take >10 seconds after an uptime of 7
minutes.
jeremy@chromium.org
Time it takes for session restore to finish initiating creation of restored
tabs and windows. This measurement is only sent for startups that take
>10 seconds after an uptime of 7 minutes.
Deprecated 02/2015. Startup.StartupBrowserCreator_Start is more useful.
rkaplow@chromium.org
The amount of time that elapsed during
StartupBrowserCreator::ProcessCmdLineImpl.
rkaplow@chromium.org
The amount of time that elapsed during StartupBrowserCreator::Start().
jeremy@chromium.org
Time for a running browser process to start processing the command line
passed in by a second Chrome process, which just sent its command line
arguments to the already-running process and will soon exit. Measured from
the time the second Chrome process started.
rtenneti@chromium.org
Deprecated as of 10/2014.
Time duration measured from the time the startup timebomb was started and
when it went off.
dmurph@chromium.org
True if a created blob exceeded the internal in-memory storage memory limit
for blobs.
dmurph@chromium.org
The number of blob items in a blob, recorded at blob construction. (Blobs
are immutable, so this won't change afterwards).
dmurph@chromium.org
True if we reuse an item for a blob created from using Blob.slice, recorded
in BlobStorageContext on blob creation.
dmurph@chromium.org
Records the total in-memory storage size of blobs before a blob item is
appended. Can be subtracted by Storage.Blob.StorageSizeBeforeAppend to find
the true distribution of blob storage sizes.
dmurph@chromium.org
Records the total in-memory storage size of blobs before a blob item is
appended. Can be subtracted from Storage.Blob.StorageSizeAfterAppend to
find the true distribution of blob storage sizes.
dmurph@chromium.org
The total in-memory size in KB of finished blobs. Recorded in
BlobStorageContext when the blob is finished being created. This can include
memory that is shared with other blobs or memory from repeated internal
items.
dmurph@chromium.org
The total amount of unique memory used to create a blob. Recorded in
BlobStorageContext when the blob is finished being created. This does not
include memory that is shared with other blobs. If multiple of the same blob
item is present, then this number will reflect the size of the single item.
dmurph@chromium.org
The size in KB of items (or parts of items) appended to blobs.
dmurph@chromium.org
The size in KB of items (or parts of items) appended to blobs that come from
the slicing of other blobs. This happens when using Blob.slice, where we
are using a part of an item in the original blob (not the whole item).
dmurph@chromium.org
True if the file size on blob append is unknown (which means the full file),
or false if a specific file length was populated. Recorded in
BlobStorageContext when we are adding a file item to a blob.
dmurph@chromium.org
True if the file size of a filesystem object on blob append is unknown
(which means the full file), or false if a specific file length was
populated. Recorded in BlobStorageContext when we are adding a filesystem
item to a blob.
mathp@chromium.org
The counts of network error codes encountered by SuggestionsService when an
attempt to fetch suggestions from the server fails.
mathp@chromium.org
The counts of HTTP response codes encountered by SuggestionsService when
attempting to fetch suggestions from the server.
mathp@chromium.org
The latency of a SuggestionsService fetch that results in a success
response.
manzagop@chromium.org
Number of URLs present in the Suggestions local blacklist when the
Suggestions service is created.
mathp@chromium.org
The counts of response states (such as empty or invalid) encountered by
SuggestionsService when attempting to fetch suggestions from the server.
zea@chromium.org
Time taken during app association (M18 and earlier were mispelled with this
histogram).
Deprecated as of m19.
zea@chromium.org
Count of apps run failures, used to compare failure rates between data types
for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during app association.
zea@chromium.org
Enumeration of types of app configuration failures.
zea@chromium.org
Time taken during app settings association.
zea@chromium.org
Enumeration of types of app settings configuration failures.
Replaced by AppSettingsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of app settings association failures.
Replaced by AppsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of app association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of app association failures (M18 and earlier were
mispelled with this histogram).
maxbogue@chromium.org
Whether attachment checksums match on download or not.
maxbogue@chromium.org
Response or error codes from downloading sync attachments.
maxbogue@chromium.org
The total time a download takes including request and server overhead.
maxbogue@chromium.org
The result of initializing the sync attachment store.
maxbogue@chromium.org
Response or error codes from uploading sync attachments.
zea@chromium.org
Enumeration of results from attempting to migrate Sync's nigori node and its
encryption keys to support keystore.
zea@chromium.org
Age of all auth tokens rejected by the invalidation server. Measured from
the time they were created.
zea@chromium.org
Age of auth tokens younger than one hour that were rejected by the
invalidation server. Measured from the time they were created.
zea@chromium.org
Time taken during initial authorization.
zea@chromium.org
Age of all auth tokens rejected by the sync server. Measured from the time
they were created.
zea@chromium.org
Age of auth tokens younger than one hour that were rejected by the sync
server. Measured from the time they were created.
zea@chromium.org
Time taken during autofill association.
zea@chromium.org
Enumeration of types of autofill configuration failures.
zea@chromium.org
Time taken during autofill profile association (M18 and earlier were
mispelled with this histogram).
Deprecated as of m19.
zea@chromium.org
Count of autofill profiles run failures, used to compare failure rates
between data types for a particular profile (see other Sync*RunFailures
histograms).
zea@chromium.org
Time taken during autofill profile association.
zea@chromium.org
Enumeration of types of autofill profile configuration failures.
Replaced by AutofillProfilesConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of autofill profile association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of autofill profile association failures (M18 and
earlier were mispelled with this histogram).
Deprecated as of m19.
zea@chromium.org
Count of autofill (autocomplete) run failures, used to compare failure rates
between data types for a particular profile (see other Sync*RunFailures
histograms).
Replaced by AutofillConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of autofill association failures.
zea@chromium.org
Number of times this client has overwritten the nigori node to update the
encryption keys without a user action (during this instantiation of Chrome).
zea@chromium.org
Tracks sync backend initialization time during initial sync setup.
zea@chromium.org
Tracks sync backend initialization success rate during initial sync setup.
zea@chromium.org
Compares sync's has_setup_completed pref against the set of types actually
restored from the sync DB. Mismatches should be rare.
zea@chromium.org
Tracks sync backend initialization success rate in cases where sync was
previously initialized.
zea@chromium.org
Tracks sync backend initialization time in cases where sync was previously
initialized.
zea@chromium.org
Number of bad requests since application startup, when the Sync error
infobar asking the user to update his account details is displayed.
Deprecated as of m18
zea@chromium.org
Time taken during bookmark association.
Deprecated as of m19.
zea@chromium.org
Count of bookmark run failures, used to compare failure rates between data
types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during bookmark association.
zea@chromium.org
Enumeration of types of bookmark configuration failures.
stanisc@chromium.org
Estimated number of bookmark duplications after bookmark association.
stanisc@chromium.org
Estimated number of new bookmark duplications after bookmark association.
Replaced by BookmarksConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of bookmark association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of bookmark association failures (M18 and earlier were
mispelled with this histogram).
zea@chromium.org
Count of model association failures for each type.
Replaced by Sync.ConfigureTime_Long.ABORTED in m21.
zea@chromium.org
Time spent configuring data types in the case where configuration is
aborted.
Replaced by Sync.ConfigureTime_Long.OK in m21.
zea@chromium.org
Time spent configuring data types in the case where configuration succeeds.
Replaced by Sync.ConfigureTime_Long.PARTIAL_SUCCESS in m21.
zea@chromium.org
Time spent configuring data types in the case where only some data types
succeed.
Replaced by Sync.ConfigureTime_Long.UNRECOVERABLE_ERROR in m21.
zea@chromium.org
Time spent configuring data types in the case where configuration encounters
an unrecoverable error.
zea@chromium.org
Time spent configuring data types in the case where configuration is
aborted.
zea@chromium.org
Time spent configuring data types in the case where configuration succeeds.
zea@chromium.org
Time spent configuring data types in the case where only some data types
succeed.
zea@chromium.org
Time spent configuring data types in the case where configuration encounters
an unrecoverable error.
Deprecated 12/2011. No longer tracked. See crbug.com/107816.
zea@chromium.org
Number of times we fix a circularity sync conflict. This is not expected to
be hit anymore.
Deprecated 12/2011. No longer tracked. See crbug.com/107816.
zea@chromium.org
Number of times we fix a removed directory with content sync conflict. This
is not expected to be hit anymore
zea@chromium.org
Whether or not we detected missing credentials during startup. This may be
related to crbug.com/121755.
zea@chromium.org
Breakdown of sync users whose cryptographer has pending keys.
zea@chromium.org
Breakdown of sync users whose cryptographer is fully ready for encryption
and decryption (initialized and no pending keys).
zea@chromium.org
Histogram that keeps track of how users encrypt their sync data. All users
start off with default encryption during initial setup, while a subset of
users go on to encrypt their sync data with a custom passphrase.
Deprecated as of m26.
zea@chromium.org
Boolean histogram for whether a custom passphrase was entered during sync
setup. Samples are taken every time sync is (re)configured, and the unique
userid count shows how many users entered a custom passphrase.
zea@chromium.org
Samples are taken every time sync is (re)configured, and the unique userid
count shows how many users explicitly chose to sync this data type via the
"Advanced Sync Preferences" dialog.
zea@chromium.org
Number of clients that have fixed themselves up from a datatype preference
loss. Clients are not expected to have this happen more than once. This
value can be compared to Sync.BackendInitializeRestoreSuccess to determine
what percentage of users are still recovering.
zea@chromium.org
Histogram of the run failures for the different sync datatypes. These are
failures that occur after startup while the datatype is syncing. Note: Due
to an enumeration reordering, pre-M23 labels are inaccurate (see
sync/internal_api/public/base/model_type.h).
zea@chromium.org
Histogram of the startup failures for the different sync datatypes. These
are failures due to missing top level sync nodes or model association Note:
Due to an enumeration reordering, pre-M23 labels are inaccurate (see
sync/internal_api/public/base/model_type.h).
pavely@chromium.org
When signin_scoped_device_id from pref doesn't match the one in
DeviceInfoSpecfics this histogram tells if sync or pref copy was empty. This
will indicate how often such mismatch happens and what was the state before.
zea@chromium.org
Time taken during dictionary association.
zea@chromium.org
Enumeration of types of dictionary configuration failures.
Replaced by DictionaryConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of dictionary association failures.
maniscalco@chromium.org
Whether the Sync Directory encountered a catastrophic error.
Deprecated 11/2011. No longer tracked.
zea@chromium.org
Number of failures trying to open the sync database on mac.
Deprecated 11/2011. No longer tracked.
zea@chromium.org
Number of failures trying to open the sync database on a non-windows non-mac
platform.
Deprecated 11/2011. No longer tracked.
zea@chromium.org
Number of failures trying to open the sync database on windows.
zea@chromium.org
Tracks success of failure of sync directory initialization.
Deprecated as of m26.
zea@chromium.org
Boolean histogram for whether the "Encrypt all synced data" radio
button was selected during sync setup. Samples are taken every time sync is
(re)configured, and the unique userid count shows how many users chose to
encrypt their sync data.
zea@chromium.org
A UI event occured.
zea@chromium.org
Time taken during extension association (M18 and earlier were mispelled with
this histogram).
Deprecated as of m19.
zea@chromium.org
Count of extension run failures, used to compare failure rates between data
types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during extension association.
zea@chromium.org
Enumeration of types of extension configuration failures.
zea@chromium.org
Time taken during extension settings association.
zea@chromium.org
Enumeration of types of extension settings configuration failures.
Replaced by ExtensionSettingsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of extension settings association failures.
Replaced by ExtensionsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of extension association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of extension association failures (M18 and earlier were
mispelled with this histogram).
zea@chromium.org
Whether a sync favicon cache lookup succeeded or not.
zea@chromium.org
Number of synced favicons at initialization time.
zea@chromium.org
Time taken during favicon images association.
zea@chromium.org
Enumeration of types of favicon images configuration failures.
Replaced by FaviconImagesConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of favicon images association failures.
zea@chromium.org
Number of client that have filled their sync favicon cache and must evict
old favicons vs those whose cache is not full.
zea@chromium.org
Time taken during favicon tracking association.
zea@chromium.org
Enumeration of types of favicon tracking configuration failures.
Replaced by FaviconTrackingConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of favicon tracking association failures.
zea@chromium.org
Time between updates to a synced favicon's visit time.
Deprecated 11/2011. Was counted incorrectly. Replaced by
Sync.BackendInitializeFirstTimeSuccess.
zea@chromium.org
Tracks sync backend initialization success rate during initial sync setup.
haitaol@chromium.org
First sync delay casued by backing up user data.
zea@chromium.org
Time between nudges for apps. Used as estimate of datatype commit frequency.
Logged when a sync cycle is performed for apps.
zea@chromium.org
Time between nudges for autofill entries. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for autofill
entries.
zea@chromium.org
Time between nudges for autofill profiles. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for autofill
profiles.
zea@chromium.org
Time between nudges for bookmarks. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for boomarks.
zea@chromium.org
Time between nudges for dictionary. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for dictionary.
zea@chromium.org
Time between nudges for extensions. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for extensions.
zea@chromium.org
Time between nudges for favicon images. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for favicon images.
zea@chromium.org
Time between nudges for favicon tracking. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for favicon
tracking.
zea@chromium.org
Time between nudges for nigori. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for nigori.
zea@chromium.org
Time between nudges for passwords. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for passwords.
zea@chromium.org
Time between nudges for preferences. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for preferences.
zea@chromium.org
Time between nudges for search engines. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for search engines.
zea@chromium.org
Time between nudges for sessions. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for sessions.
zea@chromium.org
Time between nudges for synced notifications. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for synced
notifications.
zea@chromium.org
Time between nudges for themes. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for themes.
zea@chromium.org
Time between nudges for typed urls. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for typed urls.
zea@chromium.org
Time between nudges for WiFi credentials. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for WiFi
credentials.
zea@chromium.org
The reason for a failure decrypting the keystore decryptor token.
zea@chromium.org
Counts instances of out of sync local models detected during startup.
gangwu@chromium.org
Counts the number of times a user's sync service received a
MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down
cleanly. The sync service emits this number the next time the user's sync
service is started, which will likely happen the next time the user's
profile is opened after a Chrome restart. This count is emitted once per
user/profile. Things like browser crashes that implicitly bring down all
users' sync services will cause unclean shutdown tags to appear on all open
profiles, meaning that there will be multiple emissions to this histogram as
those profiles are re-opened.
gangwu@chromium.org
Counts the number of times a user's sync service received a
MEMORY_PRESSURE_LEVEL_CRITICAL warning before the sync service shut down
uncleanly. The sync service emits this number the next time the user's sync
service is started, which will likely happen the next time the user's
profile is opened after a Chrome restart. This count is emitted once per
user/profile. Things like browser crashes that implicitly bring down all
users' sync services will cause unclean shutdown tags to appear on all open
profiles, meaning that there will be multiple emissions to this histogram as
those profiles are re-opened.
zea@chromium.org
Breakdown of sync's nigori node keystore migration state.
zea@chromium.org
Number of partially synced types (those with a progress marker but no
initial sync ended bit) that exist at sync startup.
zea@chromium.org
Whether a passphrase decryption attempt succeeded or not.
zea@chromium.org
Enumeration of how a user dismissed the passphrase dialog.
maxbogue@chromium.org
The active sync passphrase type at sync startup.
zea@chromium.org
Time taken during password association (M18 and earlier were mispelled with
this histogram).
Deprecated as of m19.
zea@chromium.org
Count of passwords run failures, used to compare failure rates between data
types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during password association.
zea@chromium.org
Enumeration of types of password configuration failures.
Replaced by PasswordsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of password association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of password association failures (M18 and earlier were
mispelled with this histogram).
zea@chromium.org
Time taken during preference association (M18 and earlier were mispelled
with this histogram).
Deprecated as of m19.
zea@chromium.org
Count of preferences run failures, used to compare failure rates between
data types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during preference association.
zea@chromium.org
Enumeration of types of preference configuration failures.
Replaced by PreferencesConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of preference association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of preference association failures (M18 and earlier
were mispelled with this histogram).
zea@chromium.org
Time taken from startup for the user to reauthorize.
zea@chromium.org
Whether OAuth2 refresh token was available at the time when
ProfileSyncService was starting backend.
zea@chromium.org
Enumeration of types of simple conflict resolutions.
Deprecated 11/2011. Was counted incorrectly. Replaced by
Sync.BackendInitializeRestoreSuccess.
zea@chromium.org
Tracks sync backend initialization success rate in cases where sync was
previously initialized.
zea@chromium.org
Time taken during search engine association (M18 and earlier were mispelled
with this histogram).
Deprecated as of m19.
zea@chromium.org
Count of search engine run failures, used to compare failure rates between
data types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during search engine association.
zea@chromium.org
Enumeration of types of search engine configuration failures.
Replaced by SearchEnginesConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of search engine association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of search engine association failures (M18 and earlier
were mispelled with this histogram).
zea@chromium.org
Time spent on first-time configure. May include time spent on retries.
zea@chromium.org
Time spent on non-first-time configure. May include time spent on retries.
zea@chromium.org
Time taken during session association (M18 and earlier were mispelled with
this histogram).
Deprecated as of m19.
zea@chromium.org
Count of sessions run failures, used to compare failure rates between data
types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during session association.
zea@chromium.org
Enumeration of types of session configuration failures.
Replaced by SessionsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of session association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of session association failures (M18 and earlier were
mispelled with this histogram).
zea@chromium.org
Time taken from the start of sync shutdown (in ProfileSyncService) until the
backend (SyncBackendHost) is fully destroyed.
zea@chromium.org
Amount of time the UI thread waits (at shutdown) to stop the
SyncBackendRegistrar.
zea@chromium.org
Amount of time the UI thread waits (at shutdown) to stop the sync thread.
zea@chromium.org
The type of event that triggered sync initialization.
Deprecated, see TimeDeferred2.
jeremy@chromium.org
zea@google.com
Time spent after ProfileSyncService *creation* but before SyncBackendHost
initialization.
jeremy@chromium.org
zea@google.com
Time spent after ProfileSyncService *creation* but before SyncBackendHost
initialization.
zea@chromium.org
Data type that first requests sync initialization.
zea@chromium.org
Counts the number of times sync clients have encountered an auth error and
number of times auth errors are fixed.
zea@chromium.org
Time taken during synced notifications association.
zea@chromium.org
Enumeration of types of synced notifications configuration failures.
Replaced by SyncedNotificationsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of synced notifications association failures.
Deprecated 12/2011. No longer tracked. See crbug.com/107816.
zea@chromium.org
Number of times the sync conflict resolver gets stuck. This is not expected
to be hit anymore.
droger@chromium.org
zea@chromium.org
Enumeration of error conditions that displays an infobar to the user.
zea@chromium.org
Boolean histogram for whether the "Sync Everything" option was
selected during sync setup. Samples are taken every time sync is
(re)configured, and the unique userid count shows how many users chose to
sync all available data types.
Deprecated as of m19
zea@chromium.org
Time taken during theme association (M18 and earlier were mispelled with
this histogram).
Deprecated as of m19.
zea@chromium.org
Count of theme run failures, used to compare failure rates between data
types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during theme association.
zea@chromium.org
Enumeration of types of theme configuration failures.
Replaced by ThemesConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of theme association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of theme association failures (M18 and earlier were
mispelled with this histogram).
zea@chromium.org
Time taken during typed url association (M18 and earlier were mispelled with
this histogram).
zea@chromium.org
The percentage of history DB operations initiated by the typed URL change
processor that return an error. The cumulative count for the current sync
session is logged after every typed URL change.
zea@chromium.org
The percentage of history DB operations during model association that return
an error. This is logged at the end of typed URL model association, which
happens once each time sync starts up.
Deprecated as of m19.
zea@chromium.org
Count of typed url run failures, used to compare failure rates between data
types for a particular profile (see other Sync*RunFailures histograms).
zea@chromium.org
Time taken during typed url association.
zea@chromium.org
Enumeration of types of typed url configuration failures.
Replaced by TypedUrlsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of typed url association failures.
Deprecated as of m19.
zea@chromium.org
Enumeration of types of typed url association failures (M18 and earlier were
mispelled with this histogram).
zea@chromium.org
Enumeration of the different reasons for unrecoverable errors and how often
they have occurred.
zea@chromium.org
Time spent waiting for a sync cycle to complete the url fetch.
zea@chromium.org
Whether a url fetch timed out or not. Timing out implies the fetch was
stalled for an unknown reason.
zea@chromium.org
Time the user spends looking at the authorization dialog.
zea@chromium.org
Time taken during bookmark association.
zea@chromium.org
Time taken during WiFi credentials association.
zea@chromium.org
Enumeration of types of WiFi credentials configuration failures.
Replaced by WifiCredentialsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of WiFi credentials association failures.
petewil@chromium.org
zea@chromium.org
The actions taken on synced notifications, recorded every time they happen.
This histogram will record every single event that happens separately.
tzik@chromium.org
Overridden conflict resolution policy of Sync FileSystem API. Recorded for
each API call to override the policy.
tzik@chromium.org
The number of cached backing remote file metadata in the Sync FileSystem
database. Recorded at the initialization phase of Sync FileSystem.
tzik@chromium.org
The number of Chrome Apps that uses Sync FileSystem with V2 backend.
Recorded at the initialization phase of Sync FileSystem.
tzik@chromium.org
The result of the registration of Chrome App to Sync FileSystem.
peria@chromium.org
tzik@chromium.org
Time elapsed to register a Chrome App to SyncFilesystem. Recorded for each
registration request by apps.
tzik@chromium.org
The number of the directory tree node that maps backing files to local files
in the Sync FileSystem database. Recorded at the initialization phase of
SyncFileSystem.
dbeam@chromium.org
Shows actions taken on the "Not signed in? You're misssing out"
link on the top right of chrome://apps. Logged once per visit of
chrome://apps as well as on each click of the sync promo.
lliabraa@chromium.org
Age (time since the last display in previous sessions) of a tab being
restored due to the first tab switch after the browser cold start, recorded
upon such restore. When the browser is started from cold, this metric is not
recorded for the foreground, automatically restored tab, so that the metric
tracks only the restores triggered by direct user decision to switch tabs.
ppi@chromium.org
Mobile-specific metric: when a tab that was opened in background (via
"Open link in new tab") is switched to, we record whether the
eagerly loaded tab was still memory resident, or we lost the loaded page due
to memory pressure.
lliabraa@chromium.org
[iOS] When switching to an evicted tab, this histogram records whether or
not the tab had ever been active. For example, the tab was opened via
"Open in new tab" but evicted before being viewed for the first
time.
lliabraa@chromium.org
A count of form activity (e.g. fields selected, characters typed) in a tab.
Recorded only for tabs that are evicted due to memory pressure and then
selected again.
lliabraa@chromium.org
beaudoin@chromium.org
Tracks the different ways users are opening new tabs. Does not apply to
opening existing links or searches in a new tab, only to brand new empty
tabs. Note: Currently the "Regular menu option" includes some
programmatic actions in addition to user actions.
lliabraa@chromium.org
beaudoin@chromium.org
The time for the new tab page to fire the "DOMContentLoaded"
event.
lliabraa@chromium.org
beaudoin@chromium.org
The time for the new tab page to fire the "load" event.
lliabraa@chromium.org
beaudoin@chromium.org
The time for the new tab page to start executing JavaScript.
lliabraa@chromium.org
User-perceived load time for a successful tab restore, measured from the
first time the user sees the tab being restored until the load completes.
lliabraa@chromium.org
When the browser restores a tab, whether the load was successful. Loads can
fail for instance when there is no connectivity.
lliabraa@chromium.org
Load time for a successful tab restore.
lliabraa@chromium.org
When the browser restores a tab, whether the user waits for completion of
the load or if the user gives up by switching to another tab or leaving
Chrome.
lliabraa@chromium.org
ppi@chromium.org
The status of a tab collected each time the tab is displayed on Android,
including user switching to the tab and displays of newly created tabs, such
as NTP or tabs opened to handle intents.
lliabraa@chromium.org
ppi@chromium.org
The status of a tab collected each time the user switches to it on mobile.
That does not include tabs being created at the time the user switches to
them, such as NTP or tabs opened to handle intents.
lliabraa@chromium.org
marq@chromium.org
ppi@chromium.org
The status of a tab collected each time the user switches to it on mobile
with the data reduction proxy enabled. This is populated identically, and in
addition to Tab.StatusWhenSwitchedBackToForeground for any given tab
switching event if the proxy is enabled.
lliabraa@chromium.org
Age (in ms) when the tab was switched to foreground.
Deprecated as of 04/2014.
lliabraa@chromium.org
Each time a tab is brought to the foreground, this histogram indicates if
chrome was launched without an URL (i.e., from the launcher), or with an URL
(i.e., from another app).
Deprecated as of 04/2014.
lliabraa@chromium.org
Rank in MRU order (0 being first) when the tab was switched to foreground.
lliabraa@chromium.org
Count of all tabs when a tab is switched.
Deprecated as of 04/2014.
lliabraa@chromium.org
Each time a tab is brought to the foreground, this histogram indicates if
this is the first viewing of the tab since Chrome was put into foreground,
or if it was a return to a tab that has already been shown in this session.
lliabraa@chromium.org
[iOS] When an existing tab becomes active, this histogram records the time
since it was made inactive.
lliabraa@chromium.org
[iOS] When an evicted tab becomes active, this histogram records the time
since it was made inactive.
lliabraa@chromium.org
Time elapsed since there was form activity (e.g. fields selected, characters
typed) in a tab. Recorded only for tabs that are evicted due to memory
pressure and then selected again.
lliabraa@chromium.org
Age (time since the last display in previous sessions) of the foreground tab
being restored on the browser cold start.
lliabraa@chromium.org
ppi@chromium.org
Applicability of speculative tab restore, recorded every time a tab is
switched. This allows to estimate the fraction of tab restores experienced
on mobile that can be mitigated using speculative restore. Options higher in
the enum take precedence over the lower ones (i.e. low-memory tablet will be
accounted as tablet).
lliabraa@chromium.org
ppi@chromium.org
Accuracy of the tab switch predictions made when the user begins the side
swipe gesture.
lliabraa@chromium.org
ppi@chromium.org
Accuracy of the tab switch predictions made when the user enters the tab
switcher.
lliabraa@chromium.org
ppi@chromium.org
Status of a tab recorded when the tab is targeted with speculative restore.
lliabraa@chromium.org
ppi@chromium.org
Time between starting the speculative load and actual tab switch for correct
speculative load predictions made when the user begins the side swipe
gesture.
lliabraa@chromium.org
ppi@chromium.org
Time between starting the speculative load and actual tab switch for correct
speculative load predictions made when the user enters the tab switcher.
simonb@chromium.org
Time between the event that closes a tab and the start of rendering.
simonb@chromium.org
Time between the event that exits an app and the start of rendering.
simonb@chromium.org
Time between the event that creates a tab and the start of rendering.
simonb@chromium.org
Time between the event that selects a tab and the start of rendering.
bruthig@chromium.org
tdanderson@chromium.org
The number of tabs open in the active window when a load completes.
bruthig@chromium.org
tdanderson@chromium.org
The number of tabs open in all browsers (counting app-mode windows) when a
load completes.
This is basically the average number of tabs over time.
See also MPArch.RPHCountPerLoad for the number of processes used by these
tabs.
bruthig@chromium.org
tdanderson@chromium.org
The number of tabs open per window (counting app-mode windows) when a load
completes.
This value will be recorded multiple times per load if more than one window
is open.
rtenneti@chromium.org
The time it takes indicated thread to respond with a pong message for a ping
message from WatchDog thread.
rtenneti@chromium.org
This is the total number of watched threads that are responding when we got
no response from the watched thread.
rtenneti@chromium.org
This is the total unresponsive time since last pong message for the
indicated thread when we got no response from the watched thread.
rtenneti@chromium.org
This is the total number of watched threads that are not responding when we
got no response from the watched thread.
reveman@chromium.org
vmpstr@chromium.org
Measures whether the tile manager exceeded the hard GPU memory budget
(OOMed). Recorded each time the tile manager assigns GPU memory to tiles.
Events in TimeZoneRequest.
Http response codes in TimeZoneRequest.
The time elapsed between the sending of the first API request and the time
the final (failed) response was recorded. Includes all retries.
The time elapsed between the sending of the first API request and the time
the final (successfull) response was recorded. Includes all retries.
Result of TimeZoneRequest.
Number of retries until the final response was recorded.
Please list the metric's owners. Add more owner tags as needed.
The number of times TopSitesImpl::ApplyBlacklist is called.
Please list the metric's owners. Add more owner tags as needed.
The number of items in the user Most Visited blacklist every time
TopSitesImpl::ApplyBlacklist is called.
pthammaiah@google.com
Tracks touchpad device state.
pthammaiah@google.com
Tracks unusual CrOS touchpad operational states (e.g. running into the noisy
ground issue). This is sampled at every touchpad event.
pthammaiah@google.com
Tracks touchpad natural scroll setting changes by the user.
pthammaiah@google.com
Tracks touchpad natural scroll setting on startup.
pthammaiah@google.com
Tracks touchpad sensitivity setting changes by the user. This replaces the
old Touchpad.Sensitivity.Changed metric.
pthammaiah@google.com
Tracks touchpad sensitivity setting on startup. This replaces the old
Touchpad.Sensitivity.Started metric.
Deprecated as of 6/2013, replaced by Touchpad.PointerSensitivity.Changed.
pthammaiah@google.com
Tracks touchpad sensitivity setting changes by the user.
Deprecated as of 6/2013, replaced by Touchpad.PointerSensitivity.Started.
pthammaiah@google.com
Tracks touchpad sensitivity setting on startup.
pthammaiah@google.com
Tracks touchpad TapDragging setting changes by the user.
pthammaiah@google.com
Tracks touchpad TapDragging setting on startup.
pthammaiah@google.com
Tracks touchpad TapToClick setting changes by the user.
pthammaiah@google.com
Tracks touchpad TapToClick setting on startup.
Deprecated as of 7/2013.
pthammaiah@google.com
Deprecated as of 7/2013.
pthammaiah@google.com
kenjibaheux@google.com
The number of times the always translate option was selected in the
translate infobar.
kenjibaheux@google.com
The time spent capturing plain text from the DOM. This is reported by
ChromeRenderViewObserver when a page is loaded completely.
kenjibaheux@google.com
A page may provide a Content-Language HTTP header or a META tag. For each
page load, measures whether the Content-Language header exists and is valid.
kenjibaheux@google.com
The number of times the "Nope" (don't translate) or the infobar's
X button was clicked in the translate infobar.
kenjibaheux@google.com
The number of times the translate infobar was closed by clicking the X
button without the user translating the page.
kenjibaheux@google.com
The number of times the translate UI was closed without translating in the
way that the user doesn't deny translating explicityly, like pressing 'Nope'
button. This is counted on both the infobar and the bubble UI. We are
comparing this on infobar to that on bubble by A/B testing and expecting
that the user will click 'Nope' button on bubble less times than infobar. We
won't delete this histogram after the experiment.
kenjibaheux@google.com
A page may provide a lang attribute in html tag. For each page load,
measures whether the lang attribute exists and is valid.
Deprecated as of 11/2013, and replaced by Translate.InitiationStatus.v2.
kenjibaheux@google.com
The reason why Chrome decided to perform the next action (e.g., to show
infobar, to translate a page without any prompting, and so on) when Chrome
Translate is ready to translate a page.
kenjibaheux@google.com
The reason why Chrome decided to perform the next action (e.g., to show
infobar, to translate a page without any prompting, and so on) when Chrome
Translate is ready to translate a page.
andrewhayden@chromium.org
For each page load, records whether language detection occurs on time or
gets deferred. If deferred language detection later completes, this is also
recorded. This allows measuring the UX impact of using a non-static CLD data
source.
kenjibaheux@google.com
For each page load, measures whether the provided Content-Language header
matches the language determined by CLD. Beyond directly matching or
mismatching the Content-Language header, CLD can complement the
Content-Language. For example, suppose the Content-Language header
specifies 'zh' (general Chinese), a language code that the Translate server
does not support. In this case, CLD can detect a subcode like '-TW' or
'-CN', resulting in language codes 'zh-TW' and 'zh-CN', which the Translate
server supports. This is referred to as "complementing a language
subcode".
kenjibaheux@google.com
Logs the user locale when the Translate feature is disabled by the user.
This is recorded each time a webpage is loaded and prefs for translation is
checked. This allows us to investigate the correlation between the user
locale and the usage rates of the Translate.
kenjibaheux@google.com
The number of times the original language in the translate infobar has been
changed.
kenjibaheux@google.com
The number of times the target language in the translate infobar has been
changed.
kenjibaheux@google.com
The number of times the never translate option was selected in the translate
infobar.
kenjibaheux@google.com
The number of times the never translate site was selected in the translate
infobar.
kenjibaheux@google.com
Counts translation target page schemes.
kenjibaheux@google.com
The number of times the "report this error" of options menu is
selected in the translate infobar.
kenjibaheux@google.com
The number of times the show original button was clicked in the translate
infobar.
Deprecated 5/2013 by Translate.UndisplayableLanguage
kenjibaheux@google.com
The number of times the detected language is not supported by Translate
Element.
Deprecated 7/2010. No longer tracked.
kenjibaheux@google.com
The number of times an infobar proposing to translate a page has been shown.
kenjibaheux@google.com
Chrome Translate shows an error infobar when an error happens on translation
and the infobar message depends on what kind of error happens. This metric
counts how often each error message is shown.
kenjibaheux@google.com
Chrome Translate shows an error UI (infobar or bubble) when an error happens
on translation and the UI message depends on what kind of error happens.
This metric counts how often each error message is shown.
kenjibaheux@google.com
This metrics is logged whenever a page is loaded. The logged value is
"Mathced" when the CLD-detected language differs from the page
language code , and the two languages are such similar languages. In that
case, Chrome ignore the CLD-determined language and instead uses the page
language code. The page language code is decided by Content-Language and
HTML lang attribute.
kenjibaheux@google.com
The time from injecting scripts for Chrome Translate to being ready to
perform translation.
kenjibaheux@google.com
The time from injecting scripts for Chrome Translate to the finishing loads
of all depending libraries.
kenjibaheux@google.com
The time from starting translation to the completion.
kenjibaheux@google.com
The number of times the translate button was clicked in the translate
infobar.
kenjibaheux@google.com
Logs an undisplayable language included in the language list sent by the
Translate server. The Translate server sends the list each time the user
runs Chrome. This metrics tells us that there is a language which UI should
support but doesn't.
kenjibaheux@google.com
Logs an unsupported source language detected during initiation of the
Translate feature. This is reported when the language detector successfully
detects the language of the webpage, but the language is not supported by
the translation server because it is too minor. This metric allows us to
assess how important the unsupported language is for Google translate.
kenjibaheux@google.com
The time from a page content language being determined to user requesting
Chrome Translate.
Please list the metric's owners. Add more owner tags as needed.
Whether the scroll is executed on main thread.
asvitkine@chromium.org
The actual interval between log upload start and previous log upload
finished within the same process.
erikwright@chromium.org
Reports the combined state of distinct clean exit beacons stored in Local
State and the Windows registry. They are normally expected to be identical.
gab@chromium.org
Recorded when we are somehow missing the client ID stored in Local State yet
are able to recover it from a backup location along with the backed up
installation date. This report carries the age in hours of the recovered
client id.
asvitkine@chromium.org
Recorded when the one-time UMA client id reset was performed (and the client
id of this user was migrated).
asvitkine@chromium.org
The time to run the external metrics collection task (Chrome OS).
asvitkine@chromium.org
yiyaoliu@chromium.org
Records attempts to compute the current the signin status and error
encountered when computing.
asvitkine@chromium.org
The number of events discarded at log transmission time because the event
count was already too large.
asvitkine@chromium.org
kaznacheev@chromium.org
Logs the device enrollment status for Chrome OS device. Logged with every
UMA upload.
asvitkine@chromium.org
Logs the entropy source type that was used for field trial randomization.
Logged once at each start up.
Deprecated 2012. No longer tracked.
asvitkine@chromium.org
Log whether the --enable-benchmarking flag was set, which causes field
trials to only use the default group.
asvitkine@chromium.org
For each attempt to generate the low entropy source, log whether or not the
load required generating a new low entropy source.
asvitkine@chromium.org
Logged during MetricsService initialization whether the init task or the
initial log timer completed first. The expectation is the vast majority of
the time, the init task should complete first. If metrics show otherwise,
then it may indicate there's a bug in the MetricsService init sequence and
that it should be investigated.
asvitkine@chromium.org
Number of bytes in an excessively large log that was discarded at shutdown
instead of being saved to disk to retry during next chrome run.
asvitkine@chromium.org
Number of bytes in a log was was rejected by server, and then discarded.
asvitkine@chromium.org
The time spent to load (de-serialize) unsent logs from local state, recorded
during the MetricsService startup sequence.
asvitkine@chromium.org
Simple counter of the number of times LogLoadComplete was called (bug
demonstration, as we're called more often than once per page load :-/ )
asvitkine@chromium.org
Size in kilobytes (after compression) of an uploaded UMA log. Recorded after
a successful UMA upload.
asvitkine@chromium.org
gayane@chromium.org
The network connection type for each successful metrics log upload.
asvitkine@chromium.org
Distribution of the low entropy source value used for field trial
randomization, recorded on startup.
jwd@chromium.org
Tracks if the machine ID is generated successfully and if it changes from
one run to the next. The machine ID is a 24-bit hash of machine
characteristics. It is expected to change if an install of Chrome is copied
to multiple machines. This check happens once per browser startup.
jwd@chromium.org
A count of the number of times the metrics ids (client id and low entropy
source) have been reset due to a cloned install being detected.
asvitkine@chromium.org
Logged when user successfully enables/disables MetricsReporting or when an
error occurs.
asvitkine@chromium.org
A count of successes and various failure modes related to collecting and
processing performance data obtained through "perf" on Chrome OS.
asvitkine@chromium.org
yiyaoliu@chromium.org
Record the number of loaded profiles when a profile is erased from the
profiles map kept by profile manager.
asvitkine@chromium.org
yiyaoliu@chromium.org
An enum representing the signin status of all opened profiles during one UMA
session.
asvitkine@chromium.org
Compression ratio of the serialized protobuf that will be uploaded to the
UMA server. This serialized protobuf is compressed using gzip.
Deprecated as of Sep, 2013. Gzipping protobufs is now the default.
asvitkine@chromium.org
Was the UMA protobuf uploaded earlier compressed or not.
asvitkine@chromium.org
Kilobytes saved from gzipping the protobufs before uploading them.
asvitkine@chromium.org
The time spent to store unsent logs to local state, which is done
periodically and also during start up if there was an initial stability log.
asvitkine@chromium.org
The number of synthetic field trials added to the UMA log when the system
profile is recorded. Since this is done prior to capturing the histograms
from the current process, this will generally be logged once per UMA log.
Deprecated as of May, 2012 (i.e. Chrome 21+). Replaced by the
UMA.UploadResponseStatus.XML and UMA.UploadResponseStatus.Protobuf
histograms.
asvitkine@chromium.org
The server returned a 400 code, and we discarded a log.
This tends to indicate that a syntax error is present in a log, such as
would appear when a bogus XML tag is included, or the XML is not balanced
and well structured.
asvitkine@chromium.org
For each attempted UMA upload, log whether the upload was successfully
constructed. An upload might fail to be constructed, for example, if we try
to upload before the system is fully initialized; or if serialization of the
data fails.
asvitkine@chromium.org
For each upload to the protocol buffer (v2) UMA server, log whether the
upload was successful, or whether there was an error.
Deprecated 2013. No longer tracked.
asvitkine@chromium.org
For each upload to the XML (v1) UMA server, log whether the upload was
successful, or whether there was an error.
asvitkine@chromium.org
Log whether the --reset-variation-state flag was set before the low entropy
source was requested.
Deprecated 2013. No longer tracked.
asvitkine@chromium.org
The time spent in converting the XML tree into a character buffer when
closing a metrics log (Chrome OS).
Deprecated 2013. No longer tracked.
asvitkine@chromium.org
The time spent in freeing the XML writer and tree when closing a metrics log
(Chrome OS).
zeuthen@chromium.org
The network connection type when the attempt begins. Possible values include
"Unknown", "Ethernet", "Wifi",
"Wimax", "Bluetooth", "Cellular",
"Tethered Ethernet", "Tethered Wifi".
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
A more detailed description of the last Payload transfer error when
downloading the payload.
This is reported when an attempt ends with the "Payload Download
Error" result.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The download source used, possible values include "HTTPS Server",
"HTTP Server" and "HTTP Peer".
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of minutes the update attempt took including the time the device
spent sleeping.
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of minutes the update attempt took excluding the time the device
spent sleeping.
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
A more detailed description of the last internal error. The possible values
correspond to the ErrorCode enumeration in the update_engine source code.
This is reported when an attempt ends with the InternalError result.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The attempt number which starts at 0 for the initial attempt and keeps
increasing for subsequent attempts.
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of payload mebibytes (1048576 bytes) actually download.
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The payload download speed, in kilobytes per second (1000 bytes/second).
This is calculated as the number of bytes downloaded divided by the duration
of the attempt (excluding time spent sleeping).
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The payload size, in mebibytes (1048576 bytes).
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The payload type, possible values include "Delta" (if Omaha
specified to download a delta payload); and "Full" (if Omaha
specified to download a full payload); and "ForcedFull" (if the
client specified that it would only accept a full payload).
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The result of the update attempt.
This is reported when an update attempt ends.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of minutes since the last attempt including the time the device
spent sleeping.
This is reported when an update attempt ends but only if there was a
previous attempt for the same update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of minutes since the last attempt excluding the time the device
spent sleeping.
This is reported when an update attempt ends but only if there was a
previous attempt for the same update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
If unable to download a response from Omaha, a more detailed error code is
reported in this metric.
This is reported on every update check resulting in "Download
error".
This metric is specific to ChromeOS.
zeuthen@chromium.org
If there is an update available, this metric will track what the device does
with the information. Possible values include "Applying update",
"Deferring update", "Ignoring update", and "Backing
off".
This is reported on update checks resulting in "Update available".
This metric is specific to ChromeOS.
zeuthen@chromium.org
The response from Omaha. Possible values include "No update
available", "Update available", "Download error",
"Response parsing error", and "Reboot pending".
This is reported on every update check.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of minutes since the last check including the time the device
spent sleeping.
This is reported on every update check except for the first one.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of minutes since the last check excluding the time the device
spent sleeping.
This is reported on every update check except for the first one.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The age of the OS in days, defined as the age of the /etc/lsb-release file.
This is reported on every update check but at most once a day.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The number of consecutive times a device has failed to boot an update that
successfully applied.
This is reported every time the firmware fails to boot the slot with the
update and fell back to the slot it originally updated from.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The source used to provision the install-date-days value sent to Omaha with
every request.
This is reported when OOBE (Out Of Box Experience) completes (M34 or later)
or when upgrading to a version with install-date-days support.
This metric is specific to ChromeOS.
zeuthen@chromium.org
Whether rollback worked.
This is reported every time there's a rollback request.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of update attempts required to update the device.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of bytes downloaded in mebibytes (1048576 bytes) using all
available sources (e.g. HTTP, HTTPS, HTTP Peer).
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of bytes downloaded in mebibytes (1048576 bytes) using HTTP
from a local peer.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of bytes downloaded in mebibytes (1048576 bytes) using
HTTP.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of bytes downloaded in mebibytes (1048576 bytes) using
HTTPS.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The ratio between bytes downloaded and payload size minus 100.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The various download sources used - this is a combination of the values
"HTTPS Server", "HTTP Server" and "HTTP Peer".
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The size of the payload, in mebibytes (1048576 bytes).
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The payload type ("Delta", "Full",
"ForcedFull") used.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of reboots during the update.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of minutes from when an update was detected until an update
(possibly another update) was applied. This includes the time waiting for
update checks and time the device spent sleeping.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of updates that were abandoned since the last successful
update.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The total number of times the URL was switched (from e.g. HTTPS to HTTP)
because of failures.
This is reported on every successful update.
This metric is specific to ChromeOS.
zeuthen@chromium.org
The duration between when an update has successfully completed and the user
is presented with the "reboot arrow" and when the system has
booted into the new update.
This is reported every time the device is rebooted after an update has been
applied.
This metric is specific to ChromeOS.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when Chrome is started, and
when the login prompt is again visible after a logout. This statistic is
only collected when preceeded by a logout.
derat@chromium.org
The system uptime on Chrome OS when the dbus-daemon process crashes,
resulting in a reboot.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS for setting up for a login after a
logout. More specifically, it is the time between when the Cryptohome is
unmounted (the last step in the logout process) and when the login prompt is
again visible after a logout.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS when performing a logout. More
specifically, it is the time between when a logout is initiated and when the
Cryptohome is unmounted, signaling the last step in the logout process. This
statistic is not collected when the logout is part of a restart or shutdown.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between initiating a logout and the
next time the login prompt is visible again. This statistic is not
collected if the machine is shutdown between the logout initiation and the
prompt becoming visible.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when a logout is initiated
and the UI has stopped (and Chrome has exited) during the logout process.
This statistic is not collected if the logout is part of a restart or
shutdown.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when all user-associated
processes (including the X server) have been terminated during the logout
process. This statistic is not collected if the logout is part of a restart
or shutdown.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when the UI has stopped
(Chrome has exited), and when all other associated processes have been
terminated during the logout process. This statistic is not collected if the
logout is part of a restart or shutdown.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when the X server has been
terminated from a previous logout and when Chrome is started again to show
the login screen.
nkostylev@chromium.org
Distribution of the default images that users choose in Change Picture
dialog (Chrome OS). One sample is taken each time the user changes picture.
nkostylev@chromium.org
Distribution of the default images chosen on user image screen during
out-of-the-box experience (Chrome OS). One sample is taken each time the
user confirms the choice by clicking OK button.
nkostylev@chromium.org
Distribution of the default images that existing users login with (Chrome
OS). One sample is taken each time the user logs in.
nkostylev@chromium.org
Profile image download result for UserManager (either on behalf of the
Change Picture prefs page, OOBE or scheduled refresh after user login).
nkostylev@chromium.org
The time it took to download user's profile picture.
nkostylev@chromium.org
Time histogram of the "Choose Picture" OOBE screen display delay.
nkostylev@chromium.org
The number of users of different types that log in to the system (Chrome
OS).
alemate@chromium.org
nkostylev@chromium.org
Please list the metric's owners. Add more owner tags as needed.
The time between one regular user logging out and a different regular user
logging in (Chrome OS). Delays above thirty minutes or which span system
reboots or non-regular-user logins are not reported.
ginkage@chromium.org
Whether the user pods were enabled during login, and what could disable
them.
This histogram is no longer present in V8.
jochen@chromium.org
TBD
yangguo@chromium.org
Reason code data has been rejected when attempting to deserialize.
yangguo@chromium.org
Cache size to source size ratio when caching compiled code.
This histogram is no longer present in V8.
jochen@chromium.org
TBD
This histogram is no longer present in V8.
jochen@chromium.org
Time spent generating native code for functions.
jochen@chromium.org
rmcilroy@chromium.org
Fraction of the total generated code which was generated using the
Crankshaft optimizing compiler, after each GC in percent.
This histogram has been replaced by V8.CompileMicroSeconds.
jochen@chromium.org
yangguo@chromium.org
Time spent in V8 compiler (full codegen).
yangguo@chromium.org
Time spent compiling a script that may be subject to caching.
This histogram has been replaced by V8.CompileDeserializeMicroSeconds.
vogelheim@chromium.org
Time spent deseriailzing code, used by V8 code caching.
vogelheim@chromium.org
Time spent deseriailzing code, used by V8 code caching.
This histogram has been replaced by V8.CompileEvalMicroSeconds.
jochen@chromium.org
yangguo@chromium.org
Time spent in V8 compiler (full codegen) for eval.
jochen@chromium.org
yangguo@chromium.org
Time spent in V8 compiler (full codegen) for eval.
This histogram has been replaced by V8.CompileLazyMicroSeconds.
jochen@chromium.org
Time spent compiling functions lazily on first run.
jochen@chromium.org
Aggregated time spent compiling functions lazily during a single script
execution.
jochen@chromium.org
yangguo@chromium.org
Time spent in V8 compiler (full codegen) excluding parser.
yangguo@chromium.org
Time spent compiling a script that cannot be subject to caching.
This histogram has been replaced by V8.CompileScriptMicroSeconds.
yangguo@chromium.org
Total time spent in compiling a script (incl. parsing/caching).
yangguo@chromium.org
Total time spent in compiling a script (incl. parsing/caching).
This histogram has been replaced by V8.CompileSerializeMicroSeconds.
vogelheim@chromium.org
Time spent serializing code, used by V8 code caching.
vogelheim@chromium.org
Time spent serializing code, used by V8 code caching.
This histogram is no longer present in V8
jochen@chromium.org
Time spent generating deferred code stubs.
ulan@chromium.org
Number of garbage collections that a detached global context survives,
recorded after each major garbage collection. Values greater than 7 indicate
a memory leak.
This histogram is no longer present in V8
jochen@chromium.org
The maximum memory used to store V8 compiled code on a given process.
jochen@chromium.org
hpayer@chromium.org
Time spent in mark-sweep phase of GC.
jochen@chromium.org
hpayer@chromium.org
Time spent doing a full GC during an IdleNotification.
jochen@chromium.org
hpayer@chromium.org
Time spent in IdleNotifications.
jochen@chromium.org
hpayer@chromium.org
Idle time passed to V8 via IdleNotifications.
jochen@chromium.org
hpayer@chromium.org
Milliseconds the idle time limit was overshot by the IdleNotification.
jochen@chromium.org
hpayer@chromium.org
Milliseconds the idle time limit was undershot by the IdleNotification.
jochen@chromium.org
hpayer@chromium.org
Time spent doing incremental marking steps during GC.
jochen@chromium.org
hpayer@chromium.org
Time spent in LowMemoryNotifications.
jochen@chromium.org
hpayer@chromium.org
Time spent in scavenging phase of GC.
oth@chromium.org
Results from snapshot loading.
oth@chromium.org
Results from opening V8 snapshot files.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the cell space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the code space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the large object space after each GC in
percent.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the map space after each GC in percent.
This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the old data space after each GC in
percent.
This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the old pointer space after each GC in
percent.
jochen@chromium.org
hpayer@chromium.org
External memory fragmentation in the old space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
Total external memory fragmentation after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the cell space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the code space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the lo space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the map space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the new space after each GC in percent.
This histogram has been replaced by V8.MemoryHeapFractionOldSpace.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the old data space after each GC in
percent.
This histogram has been replaced by V8.MemoryHeapFractionOldSpace.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the old pointer space after each GC in
percent.
jochen@chromium.org
hpayer@chromium.org
Fraction of the total heap used by the old space after each GC in percent.
jochen@chromium.org
hpayer@chromium.org
The size of committed memory in the cell space after each GC in KB.
jochen@chromium.org
hpayer@chromium.org
The size of committed memory in the code space after each GC in KB.
jochen@chromium.org
hpayer@chromium.org
The size of committed memory in the map space after each GC in KB.
jochen@chromium.org
hpayer@chromium.org
The total size of committed memory used by V8 after each GC in KB.
jochen@chromium.org
hpayer@chromium.org
The total size of live memory used by V8 after each GC in KB.
This histogram has been replaced by V8.ParseMicroSeconds.
jochen@chromium.org
marja@chromium.org
Time spent in V8 parser.
This histogram has been replaced by V8.ParseLazyMicroSeconds.
jochen@chromium.org
marja@chromium.org
Time spent parsing functions when they are lazily compiled on first run.
jochen@chromium.org
marja@chromium.org
Time spent parsing functions when they are lazily compiled on first run.
jochen@chromium.org
marja@chromium.org
Time spent in V8 parser.
This histogram has been replaced by V8.PreParseMicroSeconds.
jochen@chromium.org
marja@chromium.org
Time spent preparsing source code.
jochen@chromium.org
marja@chromium.org
Time spent preparsing source code.
This histogram is no longer present in V8.
jochen@chromium.org
Time spent on rewriting ASTs before compilation.
This histogram is no longer present in V8.
jochen@chromium.org
TBD
This histogram is no longer present in V8.
jochen@chromium.org
TBD
This histogram is no longer present in V8.
jochen@chromium.org
yangguo@chromium.org
The generation a compiled script was found in the compilation cache.
This histogram is no longer present in V8.
jochen@chromium.org
Time spent analysing the usage of variables.
This histogram is no longer present in V8.
jochen@chromium.org
TBD
Deprecated 1/2013. No longer tracked.
asvitkine@chromium.org
A count of the number of times we hit the code where a field trial is
disabled because no entropy provider was provided.
asvitkine@chromium.org
The counts of network error codes encountered by VariationsService when an
attempt to fetch a variations seed from the server fails.
Deprecated 2/2014. No longer tracked.
asvitkine@chromium.org
The latency of a VariationsService seed fetch that results in a not modified
response.
Deprecated 2/2014. No longer tracked.
asvitkine@chromium.org
The latency of a VariationsService seed fetch that results in neither a
success nor not modified response.
Deprecated 2/2014. No longer tracked.
asvitkine@chromium.org
The latency of a VariationsService seed fetch that results in a success
response.
asvitkine@chromium.org
How long it took to create the X-Client-Data header.
asvitkine@chromium.org
Records number of experiment ids in the X-Client-Data header at the time the
header is constructed.
sclittle@chromium.org
Records how the country code saved in prefs used for filtering permanent
consistency studies compares to the country code in the variations seed.
This is recorded each time the saved country code is loaded from the pref.
asvitkine@chromium.org
The result of verifying the variations seed signature, recorded when the
variations seed is stored to Local State after being retrieved from the
server.
Deprecated 9/2012. No longer tracked.
asvitkine@chromium.org
Whether or not the network was available when requested by the
VariationsService.
asvitkine@chromium.org
Number of previous requests to the variations server in the same session,
logged each time a new request is attempted to the variations server. For
example, the value of the 0th bucket indicates the number of initial
requests to the server that took place.
asvitkine@chromium.org
Counts the number of times the VariationsService is allowed or not allowed
to make a request due to the ResourceRequestAllowedNotifier.
jwd@chromium.org
Counts if a response from the variations server is the first response of the
day or not. This is counted when a new valid seed or a 304 is received. The
date line is computed in UTC and the times being compared are the server
time from the server response and the stored server time from the last
successful request.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
build time is ahead of or within 24 hours of the kVariationsSeedDate. Used
as an experiment to see whether the build time could be used to discard very
old seeds.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
build time is behind the kVariationsSeedDate by a day or more. Used as an
experiment to see whether the build time could be used to discard very old
seeds.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
system clock is ahead of or within 24 hours of the kVariationsSeedDate. Used
as an experiment to see whether the system clock could be used to discard
very old seeds.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
system clock is behind the kVariationsSeedDate by a day or more. Used as an
experiment to see whether the system clock could be used to discard very old
seeds.
asvitkine@chromium.org
Records whether the variations seed in local state is empty (does not exist)
on startup.
asvitkine@chromium.org
The counts of HTTP response codes encountered by VariationsService when
attempting to fetch a variations seed from the server.
asvitkine@chromium.org
The time interval between when the variations seed was last downloaded and
when it was used.
asvitkine@chromium.org
Records the result of storing the variations seed that was received from the
server.
Deprecated 11/2012. No longer tracked.
asvitkine@chromium.org
Whether or not the 1-Percent uniformity trial from the Variations server was
expired when loaded.
asvitkine@chromium.org
Records the time taken to perform variations seed simulation.
Recorded on every variation seed simulation, which follows a fetch.
asvitkine@chromium.org
Records the result of variations seed simulation. Logs the number of
experiment groups in the "kill best effort" category that are
expected to change on a restart of the browser with the received seed.
Recorded on every variation seed simulation, which follows a fetch.
asvitkine@chromium.org
Records the result of variations seed simulation. Logs the number of
experiment groups in the "kill critical" category that are
expected to change on a restart of the browser with the received seed.
Recorded on every variation seed simulation, which follows a fetch.
asvitkine@chromium.org
Records the result of variations seed simulation. Logs the number of
experiment groups in the "normal" category that are expected to
change on a restart of the browser with the received seed.
Recorded on every variation seed simulation, which follows a fetch.
asvitkine@chromium.org
The result of verifying the variations seed signature, recorded when the
variations seed is loaded from Local State.
asvitkine@chromium.org
The time since the previous attempt to fetch the variations seed within the
same session, with 0 indicating that this is the first attempt. Recorded
when a variations seed fetch is attempted by the VariationsService.
Deprecated 1/2013. No longer tracked.
asvitkine@chromium.org
A count of the number of times we hit the code where the
UMA-Uniformity-Trial-1-Percent field trial is disabled as a result of the
expiration check.
Deprecated 1/2013. No longer tracked.
asvitkine@chromium.org
Tracks whether the UMA-Uniformity-Trial-1-Percent field trial was not active
and which factors contributed to it.
asvitkine@chromium.org
Log the user channel assigned at browser startup used for evaluating the
variations seeds.
yoshiki@chromium.org
Chrome OS Video Player: the results of the cast API extension load. This is
recorded after the initialization of the extension is finished.
yoshiki@chromium.org
Chrome OS Video Player: the length of casted video (in seconds).
yoshiki@chromium.org
Chrome OS Video Player: the number of cast devices. This is recorded when
the cast extension finishes the discovery.
yoshiki@chromium.org
Chrome OS Video Player: the number of files being opened on launch.
yoshiki@chromium.org
Chrome OS Video Player: type of playback (eg. local play, cast). This is
recorded when a video starts playing.
bokan@chromium.org
The viewport meta tag type seen on each page load. Only recorded on Android.
bokan@chromium.org
The screen width as a percentage of viewport width (i.e. zoom at which we
can see the whole page). Only recorded on Android and for viewport meta tags
with constant width.
Please list the metric's owners. Add more owner tags as needed.
A count of various control events that can occur on the virtual keyboard,
such as showing and hiding.
Please list the metric's owners. Add more owner tags as needed.
Counts the number of keys typed by the virtual keyboard between each
backspace. This metric provides a rough approximation of an error rate for
the virtual keyboard.
estade@chromium.org
Measures the time taken by Google Online Wallet server's accept legal
document API call.
estade@chromium.org
Measures the time taken by Google Online Wallet server's authenticate
instrument API call.
estade@chromium.org
Measures the time taken by Google Online Wallet server's get full wallet API
call.
estade@chromium.org
Measures the time taken by Google Online Wallet server's get wallet items
API call.
Deprecated as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet.
estade@chromium.org
Measures the time taken by Google Online Wallet server's save address API
call.
Deprecated as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet.
estade@chromium.org
Measures the time taken by Google Online Wallet server's save instrument API
call.
Deprecated as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet.
estade@chromium.org
Measures the time taken by Google Online Wallet server's save instument and
address API call.
estade@chromium.org
Measures the time taken by Google Online Wallet server's save to wallet API
call.
estade@chromium.org
Measures the time taken by Google Online Wallet server's send status API
call.
estade@chromium.org
Measures the time taken by Google Online Wallet server's unknown API calls.
Deprecated as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet.
estade@chromium.org
Measures the time taken by Google Online Wallet server's update address API
call.
Deprecated as of 7/2013, replaced by Wallet.ApiCallDuration.SaveToWallet.
estade@chromium.org
Measures the time taken by Google Online Wallet server's update instument
API call.
estade@chromium.org
Counts the number of times each Wallet API failed due to being unable to
parse the response.
estade@chromium.org
HTTP response codes seen by Wallet client.
ajuma@chromium.org
Counts the number of times each CSS property is animated. There is no limit
on the number of times each property is counted per page view -- a property
that is animated multiple times during a single page view is counted each
time it animates.
yoichio@chromium.org
Counts the number of times each document.execCommand is executed. This
doesn't count commands not supported by Blink.
yoichio@chromium.org
Counts the number of times each Editor::Command::execute is called. This
doesn't count commands not supported by Blink.
eseidel@chromium.org
Count of how many instances of WebCore::Page use various features. Each
WebCore::Page instance has a WebCore::UseCounter instance. It records and
reports feature usage (e.g. via UseCounter::count() method). NOTE: dev
numbers from 34.0.1800.1 to 34.0.1833.4 are wrong (see crbug.com/341631).
eseidel@chromium.org
mikelawther@chromium.org
Records usage of CSS properties used on a page, either statically or
dynamically, from the time the page is initialised to when it is closed or
navigated away from. Each property is counted at most once per page per
view.
Every time a CSS property is parsed on a page, that property is recorded as
having been used. The histogram is updated with this data whenever a page is
closed, or a page navigation happens. Each histogram bucket corresponds to a
CSS property (eg width, border-radius). The exception is the bucket numbered
'1' - this counts the number of pages that CSS properties were counted on.
These numbers give the percentage of pages that use a CSS property. For
example, if the 'border-radius' histogram bucket has a count of 250, and the
page count bucket (i.e. bucket number 1) has a count of 1000 - this means
that 1000 pages were recorded, and border-radius was used on 25% of those
pages.
Internally, each WebCore::Page has a WebCore::UseCounter instance, with
booleans recording use of each CSS property - one boolean per property. Upon
destruction of the WebCore::Page (e.g. by the user closing the tab), or a
page navigation happening, the histogram is updated. For each boolean that
is set to True, the corresponding histogram bucket for that CSS property is
incremented by 1. The page count bucket (i.e. bucket number 1) is always
incremented by 1 on each histogram update.
dgrogan@chromium.org
Methods that encountered consistency errors. Such errors probably point to a
bug in our code.
As of chrome 26, use {Consistency, Read, Write}Error instead.
dgrogan@chromium.org
Count of internal IndexedDB errors (data corruption, I/O errors, etc)
encountered.
dgrogan@chromium.org
Count of the different success and failure modes when opening an IndexedDB
backing store - clean open, successful open with recovery, failed recovery,
etc. Includes all hosts.
dgrogan@chromium.org
Count of the different success and failure modes when opening an IndexedDB
backing store - clean open, successful open with recovery, failed recovery,
etc. Only for docs.google.com.
dgrogan@chromium.org
Length of leveldb directories that cause paths to not fit in the filesystem,
either because the individual component is too long or the overall path is
larger than MAX_PATH.
dgrogan@chromium.org
Methods that encountered leveldb errors while trying to read from disk.
dgrogan@chromium.org
Methods that encountered leveldb errors while trying to write to disk.
dgrogan@chromium.org
The reason that a forced-close of a backing store occurred.
dgrogan@chromium.org
Count total number of front end API calls of IndexedDB methods.
dgrogan@chromium.org
Count of how many times LevelDBDatabase got an error trying to check free
disk space.
dgrogan@chromium.org
Amount of free disk space on the partition/volume/etc where LevelDB failed
to open.
dgrogan@chromium.org
Amount of free disk space on the partition/volume/etc where LevelDB was
successfully opened.
cmumford@chromium.org
The time that it takes to open IndexedDB's LevelDB backing store.
cmumford@chromium.org
The time that it takes to write the data IndexedDB to the LevelDB backing
store for a put operation.
cmumford@chromium.org
The time that it takes to commit an IndexedDB transaction to its LevelDB
backing store.
cmumford@chromium.org
The time that it takes to write data to an IndexedDB's LevelDB backing
store.
dgrogan@chromium.org
Error classes returned by LevelDB when it failed to open a database.
cmumford@chromium.org
Errors (base::File::Error) encountered by a single LevelDBEnv method when
opening an IndexedDB instance.
dgrogan@chromium.org
Types of corruption that LevelDB encounters when opening a database.
dgrogan@chromium.org
LevelDBEnv methods that generated IO errors when opening a database.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE.
Errno errors encountered by a single LevelDBEnv method when opening an
IndexedDB instance.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE.
PlatformFileErrors encountered by a single LevelDBEnv method when opening an
IndexedDB instance.
dgrogan@chromium.org
Error classes returned by LevelDB when it failed to read a database.
cmumford@chromium.org
Errors (base::File::Error) encountered by a single LevelDBEnv method when
reading from an IndexedDB instance.
dgrogan@chromium.org
Types of corruption that LevelDB encounters when reading a database.
dgrogan@chromium.org
LevelDBEnv methods that generated IO errors when reading a database.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE.
Errno errors encountered by a single LevelDBEnv method when reading an
IndexedDB instance.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE.
PlatformFileErrors encountered by a single LevelDBEnv method when opening an
IndexedDB instance.
dgrogan@chromium.org
Error classes returned by LevelDB when it failed to write to a database.
cmumford@chromium.org
Errors (base::File::Error) encountered by a single LevelDBEnv method when
writing to an IndexedDB instance.
dgrogan@chromium.org
Types of corruption returned by LevelDB when it failed to write to a database.
dgrogan@chromium.org
LevelDBEnv methods that generated IO errors when writing to a database.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE.
Errno errors encountered by a single LevelDBEnv method when writing to an
IndexedDB instance.
dgrogan@chromium.org
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE.
PlatformFileErrors encountered by a single LevelDBEnv method when writing to
an IndexedDB instance.
cmumford@chromium.org
The delay between the receipt of the request to open an IndexedDB database
and the firing of the blocked event.
cmumford@chromium.org
The delay between the receipt of the request to open an IndexedDB database
and the firing of the error event.
cmumford@chromium.org
The delay between the receipt of the request to open an IndexedDB database
and the firing of the success event.
cmumford@chromium.org
The delay between the receipt of the request to open an IndexedDB database
and the firing of the upgradeneeded event.
jsbell@chromium.org
Records the 'keyPath' type (none, string, or array) during IDBObjectStore's
createIndex operation. See http://www.w3.org/TR/IndexedDB/
jsbell@chromium.org
Records the 'multiEntry' flag value during IDBObjectStore's createIndex
operation. See http://www.w3.org/TR/IndexedDB/
jsbell@chromium.org
Records the 'unique' flag value during IDBObjectStore's createIndex
operation. See http://www.w3.org/TR/IndexedDB/
jsbell@chromium.org
Records the 'autoIncrement' flag value during IDBDatabase's
createObjectStore operation. See http://www.w3.org/TR/IndexedDB/
jsbell@chromium.org
Records the 'keyPath' type (none, string, or array) during IDBDatabase's
createObjectStore operation. See http://www.w3.org/TR/IndexedDB/
Please list the metric's owners. Add more owner tags as needed.
The delay between when the preload scanner discovers a resource on the
parser thread and when the preload request is issued on the main thread.
clamy@chromium.org
The resulting action (e.g. load resource, use resource from in-memory
cache...) upon a resource request.
clamy@chromium.org
Number of dead resources found in the memory cache over the lifetime of the
ResourceFetcher.
clamy@chromium.org
Number of resources that needed to be loaded by the ResourceFetcher over its
lifetime.
clamy@chromium.org
Whether the resource in the cache is being used by at least one client (live
resource) or not (dead resource) upon a cache hit.
clamy@chromium.org
The type of the resource (e.g. image, script...) upon a cache hit.
clamy@chromium.org
Number of dead resources that needed to be revalidated by the
ResourceFetcher over its lifetime.
marja@chromium.org
Reason for not streaming an async script.
marja@chromium.org
Whether an async script was streamed or not.
marja@chromium.org
Reason for not streaming a deferred script.
marja@chromium.org
Whether a deferred script was streamed or not.
Deprecated as this data was needed for streaming investigations, no longer
needed.
marja@chromium.org
Whether a parsing blocking script was already preloaded from the net or the
cache by the time it was needed.
marja@chromium.org
Reason for not streaming a parsing blocking script.
marja@chromium.org
Whether a parsing blocking script was streamed or not.
Deprecated as this data was needed for streaming investigations, no longer
needed.
marja@chromium.org
Time between the events "script is loaded" and "script is
compiled" for parsing blocking scripts.
Deprecated 05/2013, we no longer have the code that uses this metric.
Please list the metric's owners. Add more owner tags as needed.
Duration of time taken to create a V8 Context for an isolated world.
Deprecated 05/2013, we no longer have the code that uses this metric.
Please list the metric's owners. Add more owner tags as needed.
Duration of time taken to create a V8 Context for the main world.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Count the number of WebSocket handshake for each result. Use this histogram
as a baseline for investigating feature usage counters.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Count the number of WebSockets that accepted permessage-deflate extension
for each context take over mode. Used by the old Blink-based WebSocket
implementation.
yhirano@chromium.org
ricea@chromium.org
tyoshino@chromium.org
Count the number of send() method calls on WebSockets for each argument
type.
Deprecated as of 7/2014. This histogram was used to determine when it would
be ok to remove the deprecated XMLHttpRequest.send(ArrayBuffer) overload.
The support for ArrayBuffer was un-deprecated in the WHATWG spec for XHR,
and subsequently un-deprecated in Blink.
tyoshino@chromium.org
costan@gmail.com
Count the number of XHR.send() calls for each argument type to see when we
can deprecate the ArrayBuffer type support.
kenjibaheux@chromium.org
ksakamoto@chromium.org
A histogram tracking the time we spent showing blank text because a web font
wasn't available by the time we needed it. Measured once per @font-face that
ended up showing blank text.
hajimehoshi@chromium.org
kenjibaheux@chromium.org
kouhei@chromium.org
ksakamoto@chromium.org
Recorded upon web fonts load. Counts the number of times web font is loaded
from cache (disk cache or memory cache), fetched over network, or served
from data URL.
bashi@chromium.org
kenjibaheux@chromium.org
The success or failure of web fonts CORS-enabled fetching.
kenjibaheux@chromium.org
ksakamoto@chromium.org
Uncompressed font image size divided by the duration of time OTS takes to
decode the font image, in kilobytes per second.
kenjibaheux@chromium.org
ksakamoto@chromium.org
Recorded upon an eviction of a cache entry for a font in Google Fonts.
Records the age of the cache entry.
kenjibaheux@chromium.org
ksakamoto@chromium.org
Recorded upon a cache hit for a font in Google Fonts. Records the age of the
cache entry.
kenjibaheux@chromium.org
ksakamoto@chromium.org
When a cache entry for a font in Google Fonts is evicted, records the reuse
count of the cache entry.
kenjibaheux@chromium.org
ksakamoto@chromium.org
Recorded upon a cache hit for a font in Google Fonts. Records the reuse
count of the cache entry.
kenjibaheux@chromium.org
ksakamoto@chromium.org
Whether the font was in the cache or not. "Previously in the
cache" means there was an evicted entry for the font in the cache.
Recorded upon a disk cache query for a font in Google Fonts.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of under
10KB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of
10KB-50KB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of
50KB-100KB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of
100KB-1MB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of over
1MB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time taken for a webfont download that failed. Includes aborted
requests.
kenjibaheux@chromium.org
ksakamoto@chromium.org
This metrics is logged when a page that use web fonts is loaded. The value
is whether we had to wait on at least one web font and ended up showing
blank text, or not.
Renamed to WebFont.StyleRecalcToDownloadLatency for clarity.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time from when the webfont was referenced by a calculated style for the
first time to the start of the font download.
Deprecated as of 8/2013, replaced by WebFont.DownloadTime.0.Under10KB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of under
10KB.
Deprecated as of 8/2013, replaced by WebFont.DownloadTime.1.10KBTo50KB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of
10KB-50KB.
Deprecated as of 8/2013, replaced by WebFont.DownloadTime.2.50KBTo100KB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of
50KB-100KB.
Deprecated as of 8/2013, replaced by WebFont.DownloadTime.3.100KBTo1MB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of
100KB-1MB.
Deprecated as of 8/2013, replaced by WebFont.DownloadTime.4.Over1MB.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time it takes for a webfont download to finish, for webfonts of over
1MB.
Deprecated as of 8/2013, replaced by WebFont.DownloadTime.LoadError.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time taken for a webfont download that failed. Includes aborted
requests.
hajimehoshi@chromium.org
kenjibaheux@chromium.org
kouhei@chromium.org
ksakamoto@chromium.org
Whether a locallly installed font is actually used when @font-face had local
sources.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The packaging format of the font file (e.g. SFNT, WOFF ...) upon a webfont
load.
Deprecated 11/2013. No longer tracked.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time from when the webfont was referenced by a calculated style for the
first time to the start of the font download. Recorded at most once for each
FontResource object (not recorded if the font is retrieved from the memory
cache).
Deprecated 11/2013. No longer tracked.
kenjibaheux@chromium.org
ksakamoto@chromium.org
For each webfont, this records (a) if the font was 'styled', i.e. referenced
by a calculated style for a RenderText before the font data was used, and
(b) if the font was actually used or not, i.e. the renderer requested the
font data or not. (A Font can be used without being styled, for example when
drawn by a Canvas 2D Context.) This is recorded upon a download request of a
webfont, or destruction of a FontResource object. Recorded at most once for
each FontResource object in the renderer's memory cahce.
Deprecated as of 9/2013, replaced by
WebFont.Resource.StyleRecalcToDownloadLatency.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time from when the webfont was referenced by a calculated style for the
first time to the start of the font download.
Deprecated as of 9/2013, replaced by WebFont.Resource.UsageType.
kenjibaheux@chromium.org
ksakamoto@chromium.org
For each webfont, this records (a) if the font was 'styled', i.e. referenced
by a calculated style for a RenderText before the font data was used, and
(b) if the font was actually used or not, i.e. the renderer requested the
font data or not. (A Font can be used without being styled, for example when
drawn by a Canvas 2D Context.) This is recorded upon a download request of a
webfont, or destruction of a CSSFontFaceSource object. Recorded at most once
for each url() source of @font-face CSS rule.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The number of webfonts used in a page. This is recorded when the first
layout is done, and so will not count webfonts dynamically loaded by
scripts.
Please list the metric's owners. Add more owner tags as needed.
Percentage of results that are present locally but are not returned by the
web history API call. Recorded every time a signed-in user visits the
chrome://history page and the results from the web history are received.
Please list the metric's owners. Add more owner tags as needed.
Whether getting the OAuth token was successful for a web history query. On
visits to the chrome://history page this token is obtained and then used to
get the user's synced web history.
Please list the metric's owners. Add more owner tags as needed.
HTTP Response code returned by the server when trying to fetch the OAuth
token for a web history query.
Please list the metric's owners. Add more owner tags as needed.
Whether the web history API call was successful. Every time a signed-in user
visits the chrome://history page this query is executed to get the user's
synced web history. If successful, the local and remote results are merged
and shown in the history page.
Please list the metric's owners. Add more owner tags as needed.
Time it took for the web history to reply. Recorded when the web history API
call triggered by visiting chrome://history receives the data, measuring how
much time it took for the server to reply.
bjornv@chromium.org
Captures if the estimated delay between rendered and captured audio is out
of bounds which can cause the Echo Cancellation to fail. This is logged
roughly once every 5 seconds. The values are logged in four buckets
reflecting how well the Echo Cancellation likely performs based on the
estimated delay.
Deprecated as of 12/2014, replaced by
WebRTC.ApplicationMaxConsecutiveBytesDiscard.v2.
guoweis@chromium.org
The maximum consecutive discarded bytes caused by not enough buffer
available in WebRTC's socket implementation. This happens when WebRTC
IpcPacketSocket's throttling mechanism kicks in.
guoweis@chromium.org
The maximum consecutive discarded bytes caused by not enough buffer
available in WebRTC's socket implementation. This happens when WebRTC
IpcPacketSocket's throttling mechanism kicks in. The maximum bucket is
expanded from previous version to provide more insight when upper layer
feeds a lot of packets.
guoweis@chromium.org
The percentage of packets discarded by WebRTC's socket layer due to
EWOULDBLOCKs when WebRTC IpcPacketSocket's throttling mechanism kicks in.
Removed from code 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Duration in milliseconds of WebRTC audio capture session.
xians@chromium.org
Audio input channel layout in WebRTC.
No longer exists in the code as of 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Size of WebRTC audio input buffers (in audio frames).
No longer exists in the code as of 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Size of WebRTC audio input buffers (atypical values, in audio frames).
xians@chromium.org
Audio input sample rate for WebRTC (in Hz).
xians@chromium.org
Audio input sample rate for WebRTC (atypical values, in Hz).
Removed from code on 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Audio output channel layout in WebRTC.
xians@chromium.org
Size of WebRTC audio output buffers (in audio frames).
xians@chromium.org
Size of WebRTC audio output buffers (atypical values, in audio frames).
xians@chromium.org
Audio output sample rate for WebRTC (in Hz).
xians@chromium.org
Audio output sample rate for WebRTC (atypical values, in Hz).
Removed from code 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Duration in milliseconds of WebRTC audio render session.
henrika@chromium.org
Measures the time spent in WebRtcAudioRenderer::SourceCallback. Sampled 10
times per second.
holmer@chromium.org
The bandwidth estimate 2 seconds into a WebRTC call.
holmer@chromium.org
The number of video packets lost durig the first 2 seconds in a WebRTC call.
holmer@chromium.org
The round-trip time as measured 2 seconds into a WebRTC call.
holmer@chromium.org
The difference between the bandwidth estimate at 2 seconds and 20 seconds
into a WebRTC call, with a min at 0, which is supposed to capture the how
much the initial bandwidth estimate overshot the actual bandwidth available.
holmer@chromium.org
The time it takes the estimated bandwidth to reach 1000 kbps from the first
RTCP packet received. Used to measure the bandwidth ramp-up time.
holmer@chromium.org
The time it takes the estimated bandwidth to reach 2000 kbps from the first
RTCP packet received. Used to measure the bandwidth ramp-up time.
holmer@chromium.org
The time it takes the estimated bandwidth to reach 500 kbps from the first
RTCP packet received. Used to measure the bandwidth ramp-up time.
perkj@chromium.org
Counters on creation, opening, and a few main attributes of data channels.
perkj@chromium.org
The maximum number of retransmissions that are attempted in unreliable mode.
It is set to the value used in the configuration when a RTCDataChannel is
created.
perkj@chromium.org
The length of the time window during which transmissions and retransmissions
may occur in unreliable mode. It is set to the value used in the
configuration when a RTCDataChannel is created.
jiayl@chromium.org
Counters on creation of DesktopCaptureDevice and the first capture call.
perkj@chromium.org
Number of data channels created per PeerConnection. Sample added to the
histogram when the PeerConnection is destroyed. Note that this is done
purely on the renderer side, so no sample will be generated when the
renderer process is destroyed (as in the fast shutdown path for the
renderer) before the PeerConnection is destroyed.
mallinath@chromium.org
Counters on IPv4 and IPv6 usage in PeerConnection. These values are logged
once per PeerConnection.
mallinath@chromium.org
Number of IPv4 network interfaces discovered in a PeerConnection Session.
guoweis@chromium.org
Number of IPv4 local Candidates gathered in a PeerConnection Session once
the ICE address gathering process reaches the Completed status. To avoid
miscounting, this only includes the first m line's first component.
mallinath@chromium.org
Number of IPv6 network interfaces discovered in a PeerConnection Session.
guoweis@chromium.org
Number of IPv6 local Candidates gathered in a PeerConnection Session once
the ICE address gathering process reaches the Completed status. To avoid
miscounting, this only includes the first m line's first component.
mallinath@chromium.org
Time to setup a peer to peer call with PeerConnection.
perkj@chromium.org
Durations of audio tracks received over a PeerConnection. The stopwatch
starts when the track first becomes connected, and ends when it is
disconnected or very soon thereafter.
perkj@chromium.org
Durations of video tracks received over a PeerConnection. The stopwatch
starts when the track first becomes connected, and ends when it is
disconnected or very soon thereafter.
perkj@chromium.org
Sizes of messages sent over reliable data channels. The size of an
individual message is added to the histogram as a sample immediately when a
message is sent.
jiayl@chromium.org
Time for capturing one frame in screen capturing.
perkj@chromium.org
Durations of audio tracks sent over a PeerConnection. The stopwatch starts
when the track first becomes connected, and ends when it is disconnected or
very soon thereafter.
perkj@chromium.org
Durations of video tracks sent over a PeerConnection. The stopwatch starts
when the track first becomes connected, and ends when it is disconnected or
very soon thereafter.
guoweis@chromium.org
The maximum of consecutive delayed bytes caused by EWOULDBLOCKs from system.
This happens when system can't send any packet synchronously at that moment.
guoweis@chromium.org
The percentage of packets delayed due to ERR_IO_PENDING from system in a
WebRTC socket. This happens when system can't send any packet synchronously
at that moment.
guoweis@chromium.org
The duration that it takes to send out a packet in system layer. This
includes both the queuing time (under the condition when socket returns
EWOULDBLOCK from system) as well as the time system takes to finish the
asynchronous send. For UDP, it's the time from P2PSocketHostUdp::Send to
P2PSocketHostUdp::HandleSendResult. Tcp part is to be implemented.
perkj@chromium.org
Sizes of messages sent over unreliable data channels. The size of an
individual message is added to the histogram as a sample immediately when a
message is sent.
andresp@chromium.org
The state of a UserMediaRequest when it gets destroyed before having a
result.
Note: "Explicitly Cancelled" means
MediaStreamImpl::cancelUserMediaRequest was called and not necessarily that
the user cancelled. Those are likely tracked as UserMediaRequest with a
result of permission denied.
andresp@chromium.org
Counters for UserMediaRequests results such as failure reasons.
asapersson@chromium.org
The number of received bits per second for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The number of sent bits per second for a sent video stream. Recorded when a
stream is removed.
asapersson@chromium.org
The number of complete frames received per second for a received video
stream. Recorded when a stream is removed.
asapersson@chromium.org
The number of decoded frames per second for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
Percentage of delayed frames to renderer for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The average delay of delayed frames to renderer for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
Percentage of discarded packets by the jitter buffer due to arriving too
late for a received video stream. Recorded when a stream is removed.
asapersson@chromium.org
Percentage of duplicated packets in the jitter buffer for a received video
stream. Recorded when a stream is removed.
asapersson@chromium.org
The number of received FEC bits per second for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of sent FEC bits per second for a sent video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The number of received RTCP FIR packets per minute for a sent video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent RTCP FIR packets per minute for a received video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
Permille of frames that are key frames for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
Permille of frames that are key frames for a sent video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The number of received media payload bits per second for a received video
stream. Recorded when a stream is removed.
asapersson@chromium.org
The number of sent media payload bits per second for a sent video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of received RTCP NACK packets per minute for a sent video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent RTCP NACK packets per minute for a received video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of received padding bits per second for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of sent padding bits per second for a sent video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The number of received RTCP PLI packets per minute for a sent video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent RTCP PLI packets per minute for a received video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
Percentage of received FEC packets for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
Percentage of received packets lost for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
Percentage of recovered media packets from FEC packets for a received video
stream. Recorded when a stream is removed.
asapersson@chromium.org
The number of retransmitted bits per second for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of retransmitted bits per second for a sent video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of received bits over RTX per second for a received video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of sent bits over RTX per second for a sent video stream.
Recorded when a stream is removed.
asapersson@chromium.org
Percentage of sent packets lost for a sent video stream. Recorded when a
stream is removed.
asapersson@chromium.org
Percentage of unique RTCP NACK requests that are received in response to a
sent video stream. Recorded when a stream is removed.
asapersson@chromium.org
Percentage of unique RTCP NACK requests that are sent in response to a
received video stream. Recorded when a stream is removed.
perkj@chromium.org
Counts number of calls to WebRTC APIs from JavaScript.
perkj@chromium.org
Counts the number of calls to WebRTC APIs from JavaScript once per session.
A session is a crude estimate since its implemented as the lifetime of the
render process that called the WebRTC API.
Deprecated as of r253828 (27 Feb 2014).
tommi@chromium.org
Counts number of calls to WebRTC APIs from JavaScript, once per origin per
renderer process.
jiayl@chromium.org
Time for capturing one frame in window capturing.
lgarron@chromium.org
Tracks actions with the website setting (a.k.a. page info / origin info)
bubble, such as opening it up or clicking on the Connection tab.
lgarron@chromium.org
Tracks WebsiteSettings actions that take place on an HTTPS URL. This
completely disregards security status.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is changed using the
content settings menu.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is set to 'Allowed'
using the content settings menu.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is set to 'Blocked'
using the content settings menu.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is reset to the
default value using the content settings menu.
sashab@chromium.org
felt@chromium.org
Count of how often a specific content type (permission) is changed using the
Origin Info dialog.
sashab@chromium.org
felt@chromium.org
Count of how often a specific content type (permission) is set to 'Allowed'
using the Origin Info dialog.
sashab@chromium.org
felt@chromium.org
Count of how often a specific content type (permission) is set to 'Blocked'
using the Origin Info dialog.
Deprecated 12/2014 in Issue 433776, and replaced by
WebsiteSettings.OriginInfo.PermissionChanged.
lgarron@chromium.org
sashab@chromium.org
Count of how often a specific content type (permission) is changed using the
Website Settings UI.
jackhou@chromium.org
The success or failure of all extension installs from the webstore. This
includes those initiated by sync.
zturner@chromium.org
Count of page loads in each of the 2 different environments (metro/desktop)
on Windows 8.
kuscher@chromium.org
The number of app windows open when a load completes. This includes windows
opened by an app shortcut, or apps opened in a popup. This only counts v1
apps.
Deprecated 4/2013. No longer tracked.
kuscher@chromium.org
The number of panel windows open when a load completes. Panels are windows
docked to the bottom of the OS desktop, which are visible to the user even
while the user is interacting with other applications.
kuscher@chromium.org
The number of popup windows open when a load completes. Popup windows only
have one content area (no multiple tabs) and a stripped down toolbar
consisting only of a read-only address bar.
kuscher@chromium.org
The number of tabbed windows open when a load completes. A tabbed window is
a normal browser window which can have one or more tabs.
zturner@chromium.org
Count of browser launches from a Windows tablet pc.
wfh@chromium.org
Count of browser launches where Win32k renderer lockdown is enabled.
noms@chromium.org
The type of category clicked in the Windows Jumplist
Please list the metric's owners. Add more owner tags as needed.
Incremented each time the TimeTicks field trial runs on a machine with
multiple cores, but failed to change thread affinity. Broken down by Windows
version.
Please list the metric's owners. Add more owner tags as needed.
The smallest non-zero delta reported by subsequent calls to
QueryPerformanceCounter.
Please list the metric's owners. Add more owner tags as needed.
True if the CPU's timestamp counter ticks at a constant rate regardless of
CPU frequency.
Please list the metric's owners. Add more owner tags as needed.
The number of times the TimeTicks field trial failed because
QueryPerformanceCounter ticked backwards. Broken down by Windows version.
Please list the metric's owners. Add more owner tags as needed.
The number of times the TimeTicks field trial succeeded. Broken down by
Windows version.
Please list the metric's owners. Add more owner tags as needed.
The number of times the TimeTicks field trial ran for comparison with
WinTimeTicks.VersionSuccess. Broken down by Windows version.
ainslie@chromium.org
edwardjung@chromium.org
Number of times that each menu item is clicked.
kkimlabs@chromium.org
Frame times of the Android wrench menu opening animation. For example, if
the menu opening animation runs exactly at 60fps for a second, then each
frame time is 16ms, and a total of 60 values of 16ms are recorded. If the
animation is janky, we will see values greater than 16ms in the histogram.
rpop@chromium.org
The number of times each tab or window restore option in the Recent Tabs
submenu is clicked.
ainslie@chromium.org
edwardjung@chromium.org
The time a user takes to select a menu item after opening the menu.
kkimlabs@chromium.org
Time difference between touch down and touch up on Android wrench button.
hfung@chromium.org
The number of results (either query or URL) from ZeroSuggest. This is set
every time a successful response from ZeroSuggest is recieved, which can be
every time the user focuses on the omnibox.
hfung@chromium.org
The number of query results returned from ZeroSuggest. This is set every
time a successful response from ZeroSuggest is recieved, which can be every
time the user focuses on the omnibox.
hfung@chromium.org
The number of URL results returned from ZeroSuggest. This is set every time
a successful response from ZeroSuggest is recieved, which can be every time
the user focuses on the omnibox.
The Android signin promo was enabled to show on next startup.
The Android signin promo was shown.
User declined the Android signin promo.
User completed signin through the Android signin promo flow successfully.
User completed signin through the Android signin promo flow successfully and
chose to configure sync settings.
Identifies the point of failure, see sources.
Type of nameservers in the DNS config.
No nameservers configured.
All nameservers are Google Public DNS servers.
All nameservers have public IP addresses (and aren't Google Public DNS
servers).
All nameservers have private IP addresses (loopback, link-local, or RFC
1918).
Nameservers are a mix of types (Google Public DNS, public, private).
Results of DnsResponse::ParseToAddressList.
Succeeded with async DNS.
Succeeded with getaddrinfo after async DNS failed.
Both async DNS and getaddrinfo failed.
Same as PROC_SUCCESS except the hostname fits NetBIOS name criteria.
Started.
Failed to start watching config.
Failed to start watching HOSTS.
Failed during watching config.
Failed during watching HOSTS.
Deprecated as of 8/2013.
Deprecated as of 8/2013.
The user selected a masked server card that triggered an unmask attempt.
The user selected a masked server card that triggered an unmask attempt at
least once.
Closed with successful unmask on the first attempt.
Closed with successful unmask after failed attempts.
See ui/display/display_constants.h for the variation.
Possible results of a platform verification attempt. See
chrome/browser/chromeos/attestation/platform_verification.h.
Indices of the default images as defined in
chrome/browser/chromeos/login/default_user_images.cc. The last three values
are for taken photo, downloaded file and the image previously used by user.
Connection type as defined in net/base/connection_type_histograms.h
Any connection (SSL, HTTP, SPDY, etc.)
An SSL connection
An SSL connection with an MD5 certificate in the certificate chain
(excluding root)
An SSL connection with an MD2 certificate in the certificate chain
(excluding root)
An SSL connection with an MD4 certificate in the certificate chain
(excluding root)
An SSL connection with an MD5 CA certificate in the certificate chain
(excluding root)
An SSL connection with an MD2 CA certificate in the cerfificate chain
(excluding root)
An HTTP connection
A SPDY connection
An SSL connection that uses SSL 2.0
An SSL connection that uses SSL 3.0
An SSL connection that uses TLS 1.0
An SSL connection that uses TLS 1.1
An SSL connection that uses TLS 1.2
The reason for losing a GPU context.
Reason why a cookie was removed from the cookie store
The user explicitly requested that we delete a cookie
The value of the cookie was overwritten by a new value
The cookie expiration time passed
The cookie was evicted during garbage collection (replaced by
domain_evicted/global_evicted below)
The backing store had two copies of the cookie so one was removed (i.e.
problems writing the backing store database)
The cookie deletion should not be recorded because it occurred, e.g., during
shutdown (the fact that these values showed up in the histogram is a bug,
since fixed)
The cookie was evicted during per-domain/eTLD+1 garbage collection
The cookie was evicted during whole store garbage collection.
The cookie evicted during per-domain/eTLD+1 garbage collection, and would
have been evicted by the global garbage collection process (because they
hadn't been accessed recently enough).
The cookie evicted during per-domain/eTLD+1 garbage collection, and would
not have been evicted by global metrics as well (because they had been
accessed recently enough to save).
The cookie deletion occurred because the server overwrote it with an already
expired cookie (this is a common idiom for server deletions of cookies).
The type of a cookie when its added to the cookie store.
The reason why content verification flagged an extension as corrupted. See
ContentVerifyJob::FailureReason in
src/extensions/browser/content_verify_job.h.
Deprecated as of 12/2013. Default pinned apps trial is finished.
Echo Cancellation quality most likely good.
Echo Cancellation may suffer.
Echo Cancellation likely fails unless user is using headset.
Insufficient amount of data.
127.0.0.1 was not the only nameserver in the system DNS config.
127.0.0.1 was the only nameserver in the system DNS config.
Channel ID was enabled, but the client did not support elliptic curve key
generation.
Channel ID was enabled, but the client had an invalid system time which
prevented using it.
The SSLClientSocket was created without a ServerBoundCertService.
The server reported a reason that the client is not aware of. This should
only be recorded if the client's list of possible reasons is out of date.
The server returned the value "Unknown".
Defined as DomainCheckErrors in
components/policy/core/common/policy_loader_win.cc.
Status codes produced by DeviceManagementService for requests made to the
device management server as defined in
components/policy/core/common/cloud/cloud_policy_constants.h.
Result of DMToken operations as defined in
components/policy/core/common/cloud/enterprise_metrics.h.
A cached token was successfully loaded from disk.
Reading a cached token from disk failed.
A token fetch request was sent to the DM server.
The request was invalid, or the HTTP request failed.
Error HTTP status received, or the DM server failed in another way.
A response to the fetch request was received.
The response received was invalid. This happens when some expected data was
not present in the response.
DM server reported that management is not supported.
DM server reported that the given device ID was not found.
DM token successfully retrieved.
Successfully cached a token to disk.
Caching a token to disk failed.
The Device-ID is not unique.
Serial number rejected by DMServer.
No more licenses available for that domain.
Which domain regex generated an ICU error.
Result of device enrollment as defined in
components/policy/core/common/cloud/enterprise_metrics.h.
User pressed 'Cancel' during the enrollment process.
The user submitted valid GAIA credentials to start the enrollment process.
OAuth token fetch failed: network error.
OAuth token fetch failed: login error.
Registration / policy fetch failed: DM server reports management not
supported.
UNUSED: Enrollment failed because it failed to apply device policy.
UNUSED: Enrollment failed due to an unexpected error. This currently happens
when the GAIA auth token is not issued for the DM service, the device cloud
policy subsystem isn't initialized, or when fetching GAIA tokens fails for
an unknown reason.
Enrollment was successful.
Registration / policy fetch failed: DM server reports that the serial number
we try to register is not assigned to the domain used.
UNUSED: Auto-enrollment started automatically after sign-in.
UNUSED: Auto-enrollment failed.
UNUSED: Auto-enrollment started again after a failure.
UNUSED: User opted-out of auto-enrollment.
UNUSED: Auto-enrollment OK.
Registration failed: DM server returns unknown/disallowed enrollment mode.
UNUSED: Auto-enrollment is not supported for the mode supplied by the
server. This presently means trying to auto-enroll in kiosk mode.
Lockbox initialization took too long to complete.
Lockbox error on re-enrollment: domain does not match install attributes.
Registration / policy fetch failed: DM server reports licenses expired or
exhausted.
Failed to fetch device robot authorization code from DM Server.
Failed to fetch device robot refresh token from GAIA.
Failed to persist robot account refresh token on device.
Registration / policy fetch failed: DM server reports administrator
deprovisioned the device.
Registration / policy fetch failed: DM server reports domain mismatch.
Enrollment has been triggered, the webui login screen has been shown.
The user submitted valid GAIA credentials to start the enrollment process
for the second (or further) time.
Failed to store DM token and device ID.
Failed to obtain FRE state keys.
Failed to validate policy.
Failed due to error in CloudPolicyStore.
UNUSED: Failed to lock device.
Registration / policy fetch failed: DM server reports invalid request
payload.
Registration / policy fetch failed: DM server reports device not found.
Registration / policy fetch failed: DM server reports DM token invalid.
Registration / policy fetch failed: DM server reports activation pending.
Registration / policy fetch failed: DM server reports device ID conflict.
Registration / policy fetch failed: DM server can't find policy.
Registration / policy fetch failed: HTTP request failed.
Registration / policy fetch failed: DM server reports temporary problem.
Registration / policy fetch failed: DM server returns non-success HTTP
status code.
Registration / policy fetch failed: can't decode DM server response.
OAuth token fetch failed: account not signed up.
OAuth token fetch failed: account deleted.
OAuth token fetch failed: account disabled.
Re-enrollment pre-check failed: domain does not match install attributes.
Lockbox backend failed to initialize.
Lockbox backend (TPM) already locked.
Lockbox failure setting attributes.
Lockbox failure during locking.
Lockbox read back is inconsistent.
Failed to update device attributes.
Lockbox error on re-enrollment: mode does not match install attributes.
Defined as PolicyInvalidationType in
components/policy/core/common/cloud/enterprise_metrics.h.
Status codes produced by the policy loaders that pull policy settings from
the platform-specific management infrastructure, such as Windows Group
Policy. Defined as PolicyLoadStatus in
components/policy/core/common/policy_load_status.h.
Policy load attempt started. This gets logged for each policy load attempt
to get a baseline on the number of requests, and an arbitrary number of the
below status codes may get added in addition.
System failed to determine whether there's policy.
No policy present.
Data inaccessible, such as non-local policy file.
Data missing, such as policy file not present.
Trying with Wow64 redirection disabled.
Data read error, for example file reading errors.
Data too large to process.
Parse error.
Defined as MetricPolicyRefresh in
components/policy/core/common/cloud/enterprise_metrics.h.
Result of Policy operations as defined as MetricPolicy in
components/policy/core/common/cloud/enterprise_metrics.h.
A cached policy was successfully loaded from disk.
Reading a cached policy from disk failed.
A policy fetch request was sent to the DM server.
The request was invalid, or the HTTP request failed.
Error HTTP status received, or the DM server failed in another way.
Policy not found for the given user or device.
DM server didn't accept the token used in the request.
A response to the policy fetch request was received.
The policy response message didn't contain a policy, or other data was
missing.
Failed to decode the policy.
The device policy was rejected because its signature was invalid.
Rejected policy because its timestamp is in the future.
Device policy rejected because the device is not managed.
The policy was provided for a username that is different from the device
owner, and the policy was rejected.
The policy was rejected for another reason. Currently this can happen only
for device policies, when the SignedSettings fail to store or retrieve a
stored policy.
The fetched policy was accepted.
The policy just fetched didn't have any changes compared to the cached
policy.
Successfully cached a policy to disk.
Caching a policy to disk failed.
Deprecated 10/2013.
Reasons the sandboxed extension unpacker can fail. See enum FailureReason
in src/chrome/browser/extensions/sandboxed_extension_unpacker.h .
SSL version fallback did not occur.
Fell back on SSL 3.0.
Fell back on TLS 1.0.
Fell back on TLS 1.1.
FTH is completely off.
FTH is enabled in HKLM.
FTH is enabled in HKCU.
FTH is enabled in HKCU and HKLM.
AcLayers.dll is loaded.
AcLayers.dll is loaded and FTH is enabled in HKLM.
AcLayers.dll is loaded and FTH is enabled in HKCU.
AcLayers.dll is loaded and FTH is enabled in HKCU and HKLM.
AcXtrnal is loaded.
AcXtrnal is loaded and FTH is enabled in HKLM.
AcXtrnal is loaded and FTH is enabled in HKCU.
AcXtrnal is loaded and FTH is enabled in HKCU and HKLM.
AcXtrmal and AcLayers.dll are loaded.
AcXtrmal and AcLayers.dll are loaded and FTH is enabled in HKLM.
AcXtrmal and AcLayers.dll are loaded and FTH is enabled in HKCU.
AcXtrmal and AcLayers.dll are loaded and FTH is enabled in HKCU and HKLM.
Number of browser processes that have started at least one NPAPI Flash
process during their lifetime.
Number of browser processes that have started at least one PPAPI Flash
process during their lifetime.
Total number of browser processes.
Data connection successful
Local firewall blocked the connection
Connection timed out
Connection has been established, but then got broken (either reset or
aborted)
Connection has been refused
Other kind of error
Deprecated 2012-11-13. No longer generated.
Old FTP server type as previously defined in
net/ftp/ftp_server_type_histograms.h
Unknown (could be a server we don't support, a broken server, or a security
attack)
Server using /bin/ls -l and variants
Server using /bin/dls
Server using EPLF format
WinNT server configured for old style listing
VMS (including variants)
IBM VM/CMS, VM/ESA, z/VM formats
OS/2 FTP Server
win16 hosts: SuperTCP or NetManage Chameleon
FTP server type as defined in net/ftp/ftp_server_type_histograms.h
Deprecated 9/2012, and replaced by DriveEntryKind
Deprecated 9/2014, and replaced by PermissionAction.
For the Android platform the count for this event should be exactly the same
as the corresponding event in the GeolocationInfoBarDelegateEvent enum.
Deprecated 9/2014, and replaced by PermissionAction.
Perf data was collected, parsed and attached to the UMA protobuf
successfully.
Could not add perf data to the UMA protobuf because no perf data was ready
to be uploaded.
Perf timer triggered but the perf provider already had a perf data proto to
be added to the UMA protobuf.
Perf timer triggered but an incognito window was open.
Perf data was collected but an incognito window was opened during the
collection.
Perf data was collected and sent to Chrome as a serialized protobuf but it
could be deserialized by Chrome.
Represents a card type ID. See cardTypeId in
chrome/browser/resources/google_now/background.js.
Events in Google Now component extension. See GoogleNowEvent in
chrome/browser/resources/google_now/background.js.
Possible detected devices combination on leaving dialog
Error states noted in thumbnail_database.cc recovery code.
Successful recovery.
sql::Recovery failed init.
Query failed against recovery meta table.
No version row in recovery meta table.
Recovery meta table has version 6.
Recovery meta table has version 5.
Recovery meta table has an unexpected version.
Failed to create recovery meta table.
Failed to copy recovery meta table.
Failed to init target schema.
Failed to create recovery favicons table.
Failed to copy recovery favicons table.
Failed to create recovery favicon_bitmaps table.
Failed to copy recovery favicon_bitmaps table.
Failed to create recovery icon_mapping table.
Failed to copy recovery icon_mapping table.
Successful recovery of version 6 database.
Failed sql::MetaTable::Init().
Failed sql::Recovery::SetupMeta() or GetMetaVersionNumber().
Recovery found deprecated version and razed.
Failed v5 recovery loading schema.
Failed v5 recovery on favicons.
Failed v5 recovery on icon_mapping.
Successful recovery of version 6 database.
Failed v6/7 recovery on favicons.
Failed v6/7 recovery on favicon_bitmaps.
Failed v6/7 recovery on icon_mapping.
Failed sql::Recovery::Recovered().
Error states noted in top_sites_database.cc recovery code.
Successful recovery.
Recovery found deprecated version and razed.
sql::Recovery failed init.
Failed sql::Recovery::SetupMeta() or GetMetaVersionNumber().
Recovery meta table has an unexpected version.
Failed sql::MetaTable::Init().
Failed to init target schema.
Failed recovery on thumbnails table.
Failure from sql::Recovery::Recovered().
Rows were deleted because |url_rank| and |last_forced| didn't agree. Does
not prevent recovery.
Rows were deleted because |redirects| did not contain |url|. Does not
prevent recovery.
|url_rank| was renumbered due to missing rows. Does not prevent recovery.
newly connected socket
connected unused socket (idle prior to use)
previously used (keep-alive?) socket
A request was made to delete the data for an origin.
An unrecoverable error occurred accessing the backing store.
A forced close was requested from the indexeddb-internals page.
No key path.
Key path is a string.
Key path is an array of strings.
IndexedDB encountered an error attempting to read or decode a value from the
leveldb backing store, indicative of corruption or I/O error. Unused as of
M26.
IndexeDB encountered an error attempting to write or commit a value to the
leveldb backing store, indicative of I/O error. Unused as of M26.
IndexedDB encountered a consistency error in the leveldb backing store,
indicative of corruption or an coding error. Unused as of M26.
An in-memory backing store was opened successfully.
An on-disk backing store was opened successfully.
An on-disk backing store could not be opened or created because the
directory could not be opened or created. Cleanup will not be attempted.
An on-disk backing store was opened but had an unknown schema version, due
to corruption or reverting to a previous version of Chrome. Cleanup will be
attempted.
An on-disk backing store failed to open; cleanup was attempted but the
database could not be destroyed.
An on-disk backing store failed to open; cleanup was attempted but
re-opening the database failed.
An on-disk backing store failed to open; cleanup was attempted and the
database was then opened successfully.
An on-disk backing store was opened but leveldb failed to read the schema
version.
An in-memory backing store failed to open.
A database with non-ascii characters in its path was opened (with either
success or failure).
An open failed on a machine with a full disk. No cleanup was attempted.
Open failed because either a path component or the overall path was too
long.
An open attempt failed with an I/O error that doesn't necessitate a recovery
attempt.
The corrupted open database was deleted.
Open failed because the blob journal could not be cleaned up.
Deprecated 03/2015, and replaced by IMECommitType2.
Types X, commits X as the top suggestion.
Types X, commits Y as the top suggestion.
Types X, commits X as the non-top suggestion.
Types X, commits Y as the non-top suggestion.
Commits a prediction suggestion.
Reverts the previous auto-corrected and committed word.
Types X, commits X as the top suggestion.
Types X, commits Y as the top suggestion.
Types X, commits X as the 2nd suggestion.
Types X, commits Y as the 2nd suggestion.
Types X, commits X as the 3rd/other suggestion.
Types X, commits Y as the 3rd/other suggestion.
Commits a prediction suggestion.
Reverts the previous auto-corrected and committed word.
The commit is triggered by voice input.
IME switches by tray menu
IME switches by accelerator
IE (Windows-only)
Firefox 2
Firefox 3 (and later)
Safari (Mac-only)
Google Toolbar
A bookmarks.html file
XKeyboard
Multilingualization
Transliteration
Armenian Phonetic keyboard
Belgian keyboard
Belgian keyboard
Belgian keyboard
Bulgarian keyboard
Bulgarian Phonetic keyboard
Brazilian keyboard
Belarusian keyboard
Canadian French keyboard
Canadian English keyboard
Canadian Multilingual keyboard
Swiss keyboard
Swiss French keyboard
Czech keyboard
Czech QWERTY keyboard
German keyboard
German NEO 2 keyboard
Danish keyboard
Estonian keyboard
Spanish keyboard
Catalan keyboard
Finnish keyboard
French keyboard
UK Dvorak keyboard
UK keyboard
Georgian keyboard
Greek keyboard
Croatian keyboard
Hungarian keyboard
Irish keyboard
Hebrew keyboard
Icelandic keyboard
Italian keyboard
Japanese keyboard
Latin American keyboard
Lithuanian keyboard
Latvian keyboard
Mongolian keyboard
Norwegian keyboard
Polish keyboard
Portuguese keyboard
Romanian keyboard
Romanian Standard keyboard
Serbian keyboard
Russian keyboard
Russian Phonetic keyboard
Swedish keyboard
Slovenian keyboard
Slovakian keyboard
Turkish keyboard
Ukrainian keyboard
US keyboard
US keyboard
US keyboard
US keyboard
US Extended keyboard
US Colemak keyboard
US Dvorak keyboard
US International keyboard
US International keyboard
US International keyboard
Array input method
Cangjie input method
Quick input method
Dayi input method
Traditional Pinyin input method
Pinyin input method
Zhuyin input method
Wubi input method
Google Japanese Input (for Japanese keyboard)
Google Japanese Input (for US keyboard)
Hangul 2 Set
Hangul 3 Set (390)
Hangul 3 Set (Final)
Hangul 3 Set (No Shift)
Hangul Ahnmatae
Hangul Romaja
Arabic keyboard
Bengali keyboard (Phonetic)
Sorani Kurdish Arabic-based keyboard
Sorani Kurdish English-based keyboard
Devanagari keyboard (Phonetic)
Ethiopic keyboard
Persian keyboard
Gujarati keyboard (Phonetic)
Khmer keyboard
Kannada keyboard (Phonetic)
Lao keyboard
Malayalam keyboard (Phonetic)
Myanmar keyboard
Myanmar Myansan keyboard
Nepali keyboard (InScript)
Nepali keyboard (Phonetic)
Sinhala keyboard
Tamil keyboard (InScript)
Tamil keyboard (itrans)
Tamil keyboard (Phonetic)
Tamil keyboard (Tamil99)
Tamil keyboard (Typewriter)
Telugu keyboard (Phonetic)
Thai keyboard (Kedmanee)
Thai keyboard (Pattachote)
Thai keyboard (TIS 820-2531)
Vietnamese keyboard (TCVN)
Vietnamese keyboard (Telex)
Vietnamese keyboard (VIQR)
Vietnamese keyboard (VNI)
Transliteration Amharic
Transliteration Arabic
Transliteration Bengali
Braille Keyboard
Transliteration Greek
Transliteration Persian
Transliteration Gujarati
Transliteration Hebrew
Transliteration Hindi
Transliteration Kannada
Transliteration Malayalam
Transliteration Marathi
Transliteration Nepali
Transliteration Oriya
Transliteration Punjabi
Transliteration Sanskrit
Transliteration Serbian
Transliteration Tamil
Transliteration Telugu
Transliteration Tigrinya
Transliteration Urdu
Deprecated as of 10/2013.
Deprecated 2013-06.
getifaddrs or GetAdaptersAddresses failed
ISO 639 Language Codes.
obsolete
obsolete
obsolete
Not yet initialized
User pressed reload
Back or forward
User entered URL, or omnibox search
(deprecated) Included next 4 categories
Commonly following of link
JS/link directed reload
back/forward or encoding change
Allow stale data (avoid doing a re-post)
Speculative prerendering of a page
Any user can sign in
Whitelisted users only
Chrome flags that lead to chrome restart on ChromeOS.
Command-line flag doesn't start with two dashes.
None
Could not mount cryptohome
Could not mount tmpfs
Could not unmount cryptohome
Data removal failed
Login timed out
Unlock failed
Network auth failed
Policy/owner key file state.
Healthy, pre-R11
Unused
Healthy
Reserved
Key OK, policy bad, pre-R11
Unused
Key OK, policy bad
Reserved
Key OK, no policy, pre-R11 user (http://crosbug.com/24916)
Unused
Key OK, no policy
Reserved
Reserved
Reserved
Reserved
Reserved
Key bad, policy OK, pre-R11
Unused
Key bad, policy OK
Reserved
Key bad, policy bad, pre-R11
Unused
Key bad, policy bad
Reserved
Key bad, policy bad, pre-R11
Unused
Key bad, policy bad
Reserved
Reserved
Reserved
Reserved
Reserved
No key, policy OK, pre-R11
Unused
No key, policy OK
RESERVED
No key, policy bad, pre-R11
Unused
No key, bad policy
Reserved
Un-owned, pre-R11
Unused
Un-owned
Reserved
No reason recorded so far, nothing to report. This value should never be
reported in histogram.
Legacy profile holders.
Password changed, revoked credentials, account deleted.
Incorrect password entered 3 times at the pod.
Incorrect password entered by a SAML user once. OS would show a tooltip
offering user to complete the online sign-in.
Company policy required re-auth for SAML users.
Cryptohome is missing, most likely due to deletion during garbage
collection.
After prior login, OS failed to connect to the sync with the existing RT.
This could be due to a deleted account, password changed, account revoked,
etc.
User cancelled the password change prompt. Chrome OS has to continue to send
the user through the online flow until user updates their cryptohome
password or agrees to start the new cryptohome.
The result of a state key generation operation.
Successfully generated state keys from machine identifiers.
Successfully generated state keys from stable device secret.
Failed due to missing machine IDs.
Failed due to invalid device secret input.
HMAC initialization failed.
HMAC computation failed.
Login success offline and online
Login success offline only
Incognito Normal
Owner Normal
Other Normal
Incognito Dev
Owner Dev
Other Dev
Changed in manager session
Changed in supervised user session
Master key not found
Signature or encryption key not found
Password data not found
Manager key authorization failed
Could not load new password data upon supervised user signin
Incomplete password data loaded upon supervised user signin.
Authentication failure while changing password during supervised user
signin.
Could not store new password data for supervised user.
Error occurred while updating MetricsReporting
These values are defined inside the MobileFreSignInChoice enum
chrome/browser/android/metrics/uma_bridge.cc and reference possible ways of
completing the sign-in part of the First Run Experience.
Direction of the overscroll gesture.
Did not scroll
Scrolled forward
Scrolled back
These error indexes are produced by QCErrorToMetricIndex() in
gobi-cromo-plugin.
A signal loss in the cellular service was detected and a delayed connection
drop request was posted. This request causes the cellular connection to be
dropped if it is not cancelled within the delay provided.
Signal strength returned to normal soon after a delayed drop request was
made, causing the request to be canceled. This indicates a flaky network.
Status code that we received in response to a cellular usage API request.
This value is distinct from the others in that it indicates that we were
unable to issue a request or that we received no reply. The other values
represent the status code contained in a reply.
The DHCP client will attempt to identify the default gateway using a unicast
ARP to the gateway's MAC address. This may help speed up the re-connection
process.
The DHCP client will attempt to ARP for the IP address that it was supplied.
This indicates that the client is unsure whether the address it was assigned
is valid.
The DHCP client has successfully acquired an IP address.
The DHCP client has inititated a DHCP DISCOVER, a broadcast request for any
server to provide it with an address.
The DHCP client has received more than one offer in response to its DHCP
DISCOVER request.
The DHCP client has received an offer in response to its DHCP DISCOVER which
is the same as an address it previously failed to validate via an "Arp
Self" test.
The DHCP client has received an offer in response to its DHCP DISCOVER which
is either an all-zeros or all-ones IP address, and therefore invalid.
The DHCP client has received a response to its DHCP DISCOVER which is not
actually a DHCP OFFER.
The DHCP client has issued a DHCP INFORM message for an IP address it has
self-assigned.
The DHCP client is intializing its internal state.
The DHCP client has received a DHCP NAK and will defer processing this
response for a receive interval.
The DHCP client is performing the second level "rebind" lease
renewal stage, and has presumably failed the first level "renew"
stage.
The DHCP client is attempting to re-acquire a lease on a network where it
had previously been connected at some time in the past.
The DHCP client is releasing its current lease to its assigned IP address.
The DHCP client is performing a first level renewal of its current lease.
The DHCP client is performing a DHCP REQUEST for a lease it has been
offered.
The portal result types come from PortalResult in shill/metrics.h
The stop reasons come from shill/mac80211_monitor.h.
The security types come from the connman_service_security enum in
flimflam/include/service.h
These values are defined in PartnerBookmarkAction enum in
chrome/browser/ui/webui/ntp/android/bookmarks_handler.cc.
These values are defined inside the PromoImpressionBuckets enum in
chrome/browser/ui/webui/ntp/android/promo_handler.cc
NPAPI is not supported on this platform
NPAPI is disabled
NPAPI is enabled
The types of actions performed by the Most Visited Tile Placement
experiment, used to identify the cases where the experiment could not
operate as expected, and the reason for it.
Deprecated 4/2015.
Errno values with the same meanings on Mac/Win/Linux.
No error
Operation not permitted
No such file or directory
No such process
Interrupted function call
Input/output error
No such device or address
Arg list too long
Exec format error
Bad file descriptor
No child processes
Resource deadlock avoided
Cannot allocate memory
Permission denied
Bad address
Not a block device
Resource busy
File exists
Improper link
Operation not supported by device
Not a directory
Is a directory
Invalid argument
Too many open files in system
Too many open files
Inappropriate ioctl for device
Text file busy
File too large
Device out of space
Illegal seek
Read-only file system
Too many links
Broken pipe
Numerical argument out of domain
Numerical result out of range
Object does not support accessibility attributes
Forced crash due to menu item bounds checking failure
Forced crash due to view not in a window requiring a window
Whitelisted exception for bug 85463. Suspect ImageKit conversions for media
browser in open or save panel.
Whitelisted exception for bug 316759. Suspect background address detection,
field unknown.
Whitelisted exception for bug 466076. Suspect background address detection,
field unknown.
INVALID
INVALID
Immersive Mechanism + Primary Screen + Shared Spaces + Single Screen
AppKit Mechanism + Primary Screen + Shared Spaces + Single Screen
INVALID
INVALID
Immersive Mechanism + Primary Screen + Separate Spaces + Single Screen
AppKit Mechanism + Primary Screen + Separate Spaces + Single Screen
Immersive Mechanism + Secondary Screen + Shared Spaces + Multiple Screens
AppKit Mechanism + Secondary Screen + Shared Spaces + Multiple Screens
Immersive Mechanism + Primary Screen + Shared Spaces + Multiple Screens
AppKit Mechanism + Primary Screen + Shared Spaces + Multiple Screens
Immersive Mechanism + Secondary Screen + Separate Spaces + Multiple Screens
AppKit Mechanism + Secondary Screen + Separate Spaces + Multiple Screens
Immersive Mechanism + Primary Screen + Separate Spaces + Multiple Screens
AppKit Mechanism + Primary Screen + Separate Spaces + Multiple Screens
The window was fullscreened using the immersive mechanism.
The window was fullscreened using the AppKit mechanism, in Presentation
Mode.
The window was fullscreened using the AppKit mechanism, in Canonical
Fullscreen.
The window was located on the primary screen, and there is only a single
screen available.
The window was located on the primary screen, and there are multiple screens
available.
The window was located on a secondary screen, and there are multiple screens
available.
The "Screens Have Separate Spaces" option is unavailable.
The "Screens Have Separate Spaces" option is on.
The "Screens Have Separate Spaces" option is off.
Direction of the overscroll gesture.
Scrolled from bottom towards top
Scrolled from top towards the bottom
Scrolled from right towards left
Scrolled from left towards right
The version of PageSpeed. Values up to 1.6.29.x are in use as of 2013-10-01
while later values may adjust 'a' and/or 'b' arbitrarily.
Deprecated as of 9/2013. Experiment to measure control characters in cookies
is finished.
Deprecated as of Chrome 32. See PasswordManagerActionsTakenWithPsl
The value is a combination of three different options - what did the
password manager do, what did the user do, and was the form submitted (and
submitted successfully or not). The meaning of each value can be determined
from the values in chrome/browser/password_manager/password_form_manager.h
The value is a combination of three different options - what did the
password manager do, what did the user do, and was the form submitted (and
submitted successfully or not). The meaning of each value can be determined
from the values in chrome/browser/password_manager/password_form_manager.h
Deprecated as of 3/18/2014. See PasswordManagerActionsTakenV3.
The value is a combination of three different options - what did the
password manager do, what did the user do, and was the form submitted (and
submitted successfully or not). The meaning of each value can be determined
from the values in chrome/browser/password_manager/password_form_manager.h
The value indicates whether an entry returned by password autofill contains
a value that was found by matching against the public suffix list.
The value is a combination of the current sync state and if the user has
their sync password saved.
An operation was attempted during an incompatible decoder state.
Invalid argument was passed to an API method.
Encoded input is unreadable.
A failure occurred at the browser layer or lower. Examples of such failures
include GPU hardware failures, GPU driver failures, GPU library failures,
browser programming errors, and so on.
Deprecated March 13 2015.
Deprecated March 13 2015.
Deprecated Dec 12 2014.
deprecated May 10 2012
Deprecated April 2015
Deprecated Nov 16 2012
Deprecated Nov 16 2012
deprecated Nov 16 2012
deprecated Nov 16 2012
Deprecated April 2015
Deprecated 3/2013. No longer generated.
The value for type comes from the ProcessType enum in
content/public/common/process_type.h.
The value for type comes from the ProcessType enum in
content/public/common/process_type.h.
User arrived at the Account management screen.
User arrived at the Account management screen, and clicked Add account.
User arrived at the Account management screen, and clicked Go incognito.
User arrived at the Account management screen, and clicked on primary.
User arrived at the Account management screen, and clicked on secondary.
User arrived at the Account management screen, toggled Chrome signout.
User toggled Chrome signout, and clicked Signout.
User toggled Chrome signout, and clicked Cancel.
The user confirmed deletion of a profile from the settings page.
The user confirmed deletion of a profile from the User Manager.
The user clicked 'Remove this person' in the user manager and was shown the
profile deletion warning. No profile deletion action has been started yet.
The user clicked 'Remove...' or the 'X' in the settings page and was shown
the profile deletion warning. No profile deletion action has been started
yet.
User opened the user menu, and clicked lock.
User opened the user menu, and removed an account.
User opened the user menu, and started adding an account.
User opened the user menu, and changed the profile name.
User opened the user menu, and started selecting a new profile image.
User opened the user menu, and opened the User Manager.
User opened the user menu, and selected Go Incognito.
Reported when image download succeeds and the image is newer than what we
already have so we update it.
Reported anytime we download profile image successfully.
Download failed because of network errors.
We didn't download the image because it's the default one.
User views the 'Not You?' bubble.
User selects back from within the 'Not You?' bubble.
User adds a person from within the 'Not You?' bubble.
User chooses to disconnect (sign out) from within the 'Not You?' bubble.
User viewed the signin bubble after successfully using the inline signin.
User selected ok to dismiss the signin bubble.
User opened the settings from the signin bubble.
User views the upgrade bubble.
User dismissed the upgrade bubble.
User selects 'What's New' in the upgrade bubble.
User selects 'Not You?' in the upgrade bubble.
Deprecated 8/2013. No longer generated.
Codes for errors Protector detects about settings it protects. See
chrome/browser/protector/histograms.h for the corresponding enum.
A report was created and uploaded
A report was not uploaded because the CSD Whitelist killswitch was present
A report was not uploaded because it could not be serialized
A report upload was cancelled due to service shutdown
A report upload failed
The response from a report upload was invalid
A report was not uploaded because no binary download was found to report
Running in a IPv4-only configuration. No waste.
Cache contained an UNSPEC result for this IPv4 lookup. Waste.
Cache contained an IPv4 result for this UNSPEC lookup. Waste.
Job pool contained an UNSPEC job for this IPv4 lookup. Waste.
Job pool contained an IPv4 job for this UNSPEC lookup. Waste.
A new job was needed for this IPv4 lookup. No waste.
A new job was needed for this UNSPEC lookup. No waste.
Bloom filter support deleted in October 2012.
Bloom filter support deleted in October 2012.
Track information for various error cases in the safe-browsing store.
Store corruption detected
SQLite store orruption detected (obsolete)
SQLite store found (obsolete)
Store format unknown at open
Deleted SQLite-format store (obsolete)
Deletion of SQLite-format store failed (obsolete)
Deleted pre-release SQLite store (obsolete)
Deletion of pre-release SQLite store failed (obsolete)
Failed explicit checksum check on failed update from server
Failed checksum check while merging new data into store
Failed header checksum check when opening store
Store with valid magic number has deprecated version number
Deprecated 9/2014.
Deprecated 9/2014.
Deprecated 9/2012. No longer generated.
Fate of an Sdch dictionary, on load and eviction. See
net/sdch/sdch_owner.cc.
Errors that can occur when reading in or writing out persisted dictionary
information. See enum PersistenceFailureReason in net/sdch/sdch_owner.cc for
more information.
SDCH problem codes, listed in net/base/sdch_problem_code_list.h
Recorded in separate histogram; see Sdch3.DictionaryFate.
Recorded in separate histogram; see Sdch3.DictionaryFate.
DICTIONARY_PREVIOUSLY_SCHEDULED_TO_DOWNLOAD used instead
DICTIONARY_PREVIOUSLY_SCHEDULED_TO_DOWNLOAD used instead
Used to indicate a broken false return from URLRequest::Read(); no longer
checking that return value.
Almost the same as META_REFRESH_UNSUPPORTED
Almost the same as CACHED_META_REFRESH_UNSUPPORTED
PASSING_THROUGH_NON_SDCH plus DISCARD_TENTATIVE_SDCH
Now tracked by ResponseCorruptionDetection.* histograms.
SDCH decode corruption detection cases, listed in net/filter/sdch_filter.cc.
See also comments in SdchFilter::ReadFilteredData in the same file.
Deprecated 8/2013. No longer generated.
Indices of most popular prepopulated search engines as defined in
components/search_engines/search_engine_type.h.
Deprecated 8/2013. No longer generated.
Succesfully opened the database.
Failed to open the existing db, deleted it, and created a new empty db.
Failed to open the database and also failed to delete and start over.
Whether or not SHA-1 was present in a certificate chain and, if it was, when
the leaf certificate expired.
The GPU's Direct3D shader model version.
The alignment of the shelf area (see ash/launcher/launcher_view.cc).
The termination/suspend/dark resume action result types come from
SuspendActionResult in shill/metrics.h
The reason that the Chrome OS power manager shut down or rebooted the
system.
The signin flow was shown to the user.
The user pressed accept to sign in.
The user pressed the reject to sign in.
The user pressed the X button to dismiss the signin promo.
The user completely ignored the signin promo. Either they navigated away, or
they used the page as is.
The user clicked on the learn more link in the signin promo.
The sync was started with default settings.
The sync was started with advanced settings.
The sync was started through auto-accept with default settings.
The sync was started through auto-accept with advanced settings.
The sync was aborted with an undo button.
The preference or policy controlling if signin is valid has changed.
The valid username pattern for signing in to the Google service changed.
The preference or policy controlling if signin is valid changed during the
signin process.
User clicked to signout.
The signin process was aborted, but signin had succeeded, so signout. This
may be due to a server response, policy definition or user action.
The sync server caused the profile to be signed out.
The credentials are being transfered to a new profile, so the old one is
signed out.
The user is eligible for the promo.
The profile has previously opted out of the promo.
The profile is already signed in.
The profile does not have a single, peristent GAIA cookie.
Yet to determine how many devices the user has.
An error was returned trying to determine the account's devices.
The call to get device activity was throttled, and never executed.
The user has no devices.
The user has no device that was recently active.
The promo was initialized successfully.
The profile is opted out, so the promo didn't initialize.
Unable to read the variations configuration.
SPDY protocol version identifier, including major and minor protocol
numbers, and draft versions where appropriate.
Legacy error codes still returned by |ShFileOperation()|
Error codes returned by SQLite - see sqlite3.h
Successful result
SQL error or missing database
NOT USED. Internal logic error in SQLite
Access permission denied
Callback routine requested an abort
The database file is locked
A table in the database is locked
A malloc() failed
Attempt to write a readonly database
Operation terminated by sqlite3_interrupt()
Some kind of disk I/O error occurred
The database disk image is malformed
NOT USED. Table or record not found
Insertion failed because database is full
Unable to open the database file
NOT USED. Database lock protocol error
Database is empty
The database schema changed
String or BLOB exceeds size limit
Abort due to contraint violation
Data type mismatch
Library used incorrectly
Uses OS features not supported on host
Authorization denied
Auxiliary database format error
2nd parameter to sqlite3_bind() out of range
File opened that is not a database file
Notifications from sqlite3_log()
Warnings from sqlite3_log()
sqlite3_step() has another row ready
sqlite3_step() has finished executing
TBD
TBD
TBD
Error reading from file
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
TBD
Short read from file
Database file is directory
TBD
TBD
Cannot rollback due to readonly file
Error writing to file (other than SQLITE_FULL)
TBD
Constraint failure due to foreign key violation
Readonly because database file was moved or unlinked while open
Error syncing to disk
TBD
TBD
Error syncing directory changes to disk
NOTNULL constraint violated
Error truncating file
Primary key not unique
Error reading file metadata
Constraint failed due to trigger raise
Error unlocking file
Unique constraint failed
Error getting read lock - should not be possible
TBD
Error deleting file
Rowid not unique
Deadlock due to other process access to SQLite files
Error mapping shared memory
Error getting file attributes (other than not found)
Error while querying lock status
Error acquiring lock
Error closing file
Unused
Error mmapping file
Error in stat while mmapping file
Unused
TBD
TBD
TBD
TBD
TBD
TBD
Replaced 5/14/2013 by expanded Sqlite.Error histogram.
Extended error codes returned by SQLite - see sqlite3.h
No extended code given
Error reading from file
Short read from file
Error writing to file (other than SQLITE_FULL)
Error syncing to disk
Error syncing directory changes to disk
Error truncating file
Error reading file metadata
Error unlocking file
Error getting read lock - should not be possible
Error deleting file
Deadlock due to other process access to SQLite files
Error mapping shared memory
Error getting file attributes (other than not found)
Error while querying lock status
Error acquiring lock
Error closing file
Unused
Error mmapping file
Error in stat while mmapping file
Unused
Track successful completion or failure of sql::Recovery implementation.
sql::Recovery::Init() (helper for Begin()) completely successfully.
Failed to open temporary database to recover into.
Failed to initialize recover vtable subsystem for connection.
USE_SYSTEM_SQLITE in force, recovery virtual table not available.
Failed to enable writable_schema.
Failed to attach corrupt database to recovery database.
sql::Recovery::Backup() (helper for Recovered()) completely successfully.
Failed sqlite3_backup_init(). Error code in Sqlite.RecoveryHandle.
Failed sqlite3_backup_step(). Error code in Sqlite.RecoveryStep.
sql::Recovery::AutoRecoverTable() completed successfully.
Failed sqlite3_backup_step(). Error code in Sqlite.RecoveryStep.
AutoRecoverTable() could not find the target table.
AutoRecoverTable() failed creating recovery vtable.
AutoRecoverTable() failed copying data from recovery to target table.
AutoRecoverTable() failed to drop recovery table.
sql::Recovery::SetupMeta() completed successfully.
SetupMeta() failed to create meta recovery table.
GetMetaVersionNumber() found no version row in meta table.
GetMetaVersionNumber() failed querying recovery meta table.
GetMetaVersionNumber() found no version row in meta table.
Sqlite database version deprecation status
Database has tables, but no meta table.
Failure figuring out if database has tables.
Failed querying meta table.
No version row in meta table.
Raze succeeded.
Raze failed.
This is a subset of CAPTIVE_PORTAL_DETECTION_ENABLED (bucket 1), the only
difference is that it is for overridable errors.
Was the captive portal probe completed before the interstitial was closed?
Captive Portal won't be detected unless ::Observe is triggered which might
be a few seconds later.
This is a subset of CAPTIVE_PORTAL_PROBE_COMPLETED (bucket 3), the only
difference is that it is for overridable errors.
This is a subset of CAPTIVE_PORTAL_DETECTED (bucket 7), the only difference
is that it is for overridable errors.
SSL/TLS cipher suites from the IANA registry
This cause is recorded if the ssl error is CERT_COMMON_NAME_INVALID and the
hostname differs from one of the DNS names in the certificate (CN or SANs)
only by the presence or absence of the single-label prefix "www".
This case is not recored if the host name is not a known TLD.
This cause is recorded if the ssl error is CERT_COMMON_NAME_INVALID and the
difference between the URL and the DNS name is not "www". This
case is not recorded if the host name is not a known TLD.
This cause is recorded if the ssl error is CERT_COMMON_NAME_INVALID and the
difference between the DNS name and the URL is not "www". This
case is not recorded if the host name is not a known TLD.
This cause is recorded only if the ssl error is CERT_COMMON_NAME_INVALID, we
have received a wildcard certificate and the scope of a wildcard certificate
is too narrow for the hostname. This case is not recorded if the host name
is not a known TLD.
This cause is recorded only for CERT_COMMON_NAME_INVALID errors.
This cause is recorded only for CERT_COMMON_NAME_INVALID errors. It is
possible that this error overlaps with others but it is not likely because
of the heuristics which decide as to what constitutes a shared certificate.
In cases of overlap, we emit to only one bucket.
This cause is recorded only for CERT_AUTHORITY_INVALID errors.
This cause is recorded only for CERT_AUTHORITY_INVALID errors. The user did
not receive a certificate signed by a valid CA.
This cause is recorded only for CERT_AUTHORITY_INVALID errors.
This cause is recorded only for CERT_AUTHORITY_INVALID errors.
As of M40, this now also includes dotless domains.
As of M40, this now also includes dotless domains.
Link; Allowed as safe
Typed URL; Allowed as safe
Bookmark; Allowed as safe
Subframe navigation; Allowed as safe
Manual subframe navigation; Allowed as safe
Generated from Omnibox; Allowed as safe
Automatic toplevel navigation; Allowed as safe
Form submission; Allowed as safe
Reload; Allowed as safe
Omnibox keyword; Allowed as safe
URL generated from Omnibox keyword; Allowed as safe
Other navigation; Allowed as safe
Link; Allowed by default (safety state unknown)
Typed URL; Allowed by default (safety state unknown)
Bookmark; Allowed by default (safety state unknown)
Subframe navigation; Allowed by default (safety state unknown)
Manual subframe navigation; Allowed by default (safety state unknown)
Generated from Omnibox; Allowed by default (safety state unknown)
Automatic toplevel navigation; Allowed by default (safety state unknown)
Form submission; Allowed by default (safety state unknown)
Reload; Allowed by default (safety state unknown)
Omnibox keyword; Allowed by default (safety state unknown)
URL generated from Omnibox keyword; Allowed by default (safety state
unknown)
Other navigation; Allowed by default (safety state unknown)
Link; Blocked by static blacklist
Typed URL; Blocked by static blacklist
Bookmark; Blocked by static blacklist
Subframe navigation; Blocked by static blacklist
Manual subframe navigation; Blocked by static blacklist
Generated from Omnibox; Blocked by static blacklist
Automatic toplevel navigation; Blocked by static blacklist
Form submission; Blocked by static blacklist
Reload; Blocked by static blacklist
Omnibox keyword; Blocked by static blacklist
URL generated from Omnibox keyword; Blocked by static blacklist
Other navigation; Blocked by static blacklist
Link; Blocked by SafeSites
Typed URL; Blocked by SafeSites
Bookmark; Blocked by SafeSites
Subframe navigation; Blocked by SafeSites
Manual subframe navigation; Blocked by SafeSites
Generated from Omnibox; Blocked by SafeSites
Automatic toplevel navigation; Blocked by SafeSites
Form submission; Blocked by SafeSites
Reload; Blocked by SafeSites
Omnibox keyword; Blocked by SafeSites
URL generated from Omnibox keyword; Blocked by SafeSites
Other navigation; Blocked by SafeSites
Link; Blocked by manual exception
Typed URL; Blocked by manual exception
Bookmark; Blocked by manual exception
Subframe navigation; Blocked by manual exception
Manual subframe navigation; Blocked by manual exception
Generated from Omnibox; Blocked by manual exception
Automatic toplevel navigation; Blocked by manual exception
Form submission; Blocked by manual exception
Reload; Blocked by manual exception
Omnibox keyword; Blocked by manual exception
URL generated from Omnibox keyword; Blocked by manual exception
Other navigation; Blocked by manual exception
Link; Blocked by global settings
Typed URL; Blocked by global settings
Bookmark; Blocked by global settings
Subframe navigation; Blocked by global settings
Manual subframe navigation; Blocked by global settings
Generated from Omnibox; Blocked by global settings
Automatic toplevel navigation; Blocked by global settings
Form submission; Blocked by global settings
Reload; Blocked by global settings
Omnibox keyword; Blocked by global settings
URL generated from Omnibox keyword; Blocked by global settings
Other navigation; Blocked by global settings
Sync data type configure results. The codes are listed in
data_type_controller.h with more details.
Possible outcomes of an attempt to load the sync directory.
Possible events that delete a synced search engine.
Possible errors that can trigger a sync error infobar.
Sync UI events. The codes are listed in profile_syncer_service.h with more
details.
Sync simple conflict resolutions. The codes are listed in
conflict_resolver.h, and correspond to the different methods we have for
resolving simple sync conflicts.
Sync data type start results. The codes are listed in data_type_controller.h
with more details.
Reasons for sync unrecoverable errors.
Deprecated as of 04/2014.
Deprecated as of 04/2014.
No touchpad detected on a device without built-in touchpad
External touchpad detected on a device without built-in touchpad
Built-in touchpad not detected at boot time on a device with built-in
touchpad (touchpad failure at boot time)
Built-in touchpad detected at boot time on a device with built-in touchpad
Built-in touchpad not detected at resume time on a device with built-in
touchpad (touchpad failure at resume time)
Built-in touchpad detected at resume time on a device with built-in touchpad
All observed input events from touchpad. Serves as a reference.
The touchpad noise events (e.g. abrupt cursor jumps) caused by the noisy
ground.
Reject due to magic number mismatch
Reject due to version hash mismatch
Reject due to source hash mismatch
Reject due to CPU features mismatch
Reject due to flags hash mismatch
Reject due to checksum mismatch
Load succeeded
Failure to open snapshot file
Failed to map snapshot
Failed to verify snapshot
Opened without issue
Opened after one or more retries
Failed because file in use
Failed for other reason
The result of NIC wake on WiFi settings verification. Corresponds to
VerifyWakeOnWiFiSettingsResult in shill/metrics.h
Deprecated as of 05/2015. Substituted by VideoFormat.
The wake on WiFi features enabled in shill, which come from
WakeOnWiFiFeaturesEnabledState in shill/metrics.h
Whether or not wake on WiFi was disabled during suspend because of excessive
dark resume wakes. Corresponds to WakeOnWiFiThrottled in shill/metrics.h
Failed
Succeeded
Timed out
Incomplete
Connected
Failed
rsleevi@chromium.org
Deprecated as of 8/2013. This histogram only considered the leaf certificate
expiry date as a proxy for whether a certificate was in-scope for the BRs,
but did not consider the issuance date. As some CAs have issued long-lived
certs prior to the BRs, this disproportionately reported those certs as
being subject to the BRs, but non-compliant, when in reality they're not
subject.
Deprecated as of 12/2013. Default pinned apps trial is finished.
Replaced by GenerateRequest.
kmadhusu@chromium.org
macourteau@chromium.org
ppi@chromium.org
cmumford@chromium.org
Deprecated 2013-04 in favor of LevelDBEnvRetry.
Deprecated and removed from code as of 05/2015.
Replaced by the likely named entry. It had a misleading name as it also
has the before-unload time discounted.
rtenneti@chromium.org
rch@chromium.org
rch@chromium.org
rch@chromium.org
rch@chromium.org
rtenneti@chromium.org
deprecated May 10 2012
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated 8/2013. No longer tracked.
rch@chromium.org
rch@chromium.org
Deprecated 4/2015.
deprecated November 10 2012 crrev.com/167056
Deprecated as of 12/2014.
Deprecated as of 03/2015.
Deprecated as of 07/2014.
willchan@chromium.org
shess@chromium.org
Deprecated as of 10/2014.
Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenBookmark
instead.
Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenRecentTab
instead.