dmazzoni@chromium.org
paulmiller@chromium.org
Tracks flags and capabilities of enabled accessibility services. Recorded
every time an Android web content view first creates a virtual view
hierarchy, indicating that some accessibility service is running. The number
of emits of this histogram won't be as useful as the unique user counts. The
primary purpose of this is to guide optimization by determining what
capabilities of accessibility services are widespread and which ones are
relatively rare.
dmazzoni@chromium.org
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
Whether the Chrome OS caret highlighting is on (checked once 45 secs after
startup).
dmazzoni@chromium.org
Set when a Chrome OS user has spoken feedback enabled, recorded once each
time ChromeVox starts up. True if the user has enabled "ChromeVox
Next", a new ChromeVox experience that became the default in Chrome 56
(but can be toggled on or off by the user), false otherwise.
dmazzoni@chromium.org
Whether the Chrome OS cursor highlighting is on (checked once 45 secs after
startup).
zhelfins@chromium.org
dtseng@chromium.org
Whether the ChromeOS dictation feature is enabled (checked once 45 secs
after startup).
zhelfins@chromium.org
dtseng@chromium.org
Records how users invoke Dictation.
dmazzoni@chromium.org
Whether the Chrome OS focus highlighting is on (checked once 45 secs after
startup).
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).
yawano@chromium.org
lpalmaro@chromium.org
Cursor size of the Chrome OS Large Cursor (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
Whether the Chrome OS select-to-speak is on (checked once 45 secs after
startup).
katie@chromium.org
The speech pitch setting when Select-to-Speak was activated. It is stored as
a sparse histogram with values (100 * speech_pitch). For example, a speech
pitch of 1.0 (default) will be seen as 100.
katie@chromium.org
The speech rate setting when Select-to-Speak was activated. It is stored as
a sparse histogram with values (100 * speech_rate). For example, a speech
rate of 1.0 (default) will be seen as 100.
katie@chromium.org
A user may activate Select-to-Speak by holding down 'search' and clicking or
dragging a region with the mouse, or by highlighting an area and using
search + s to read just the highlighted area. Track the methods here.
katie@chromium.org
A user has tapped a button in the tray to change Select-to-Speak's state.
The tap was interpreted by Select-to-Speak as a request to start selection,
to cancel speech, or to cancel selection, depending on Select-to-Speak's
internal state when the tap occured. This tracks when the button was tapped
and the event that it generated.
katie@chromium.org
Whether Select-to-Speak had per-word highlighting enabled when activated.
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
Whether the Chrome OS switch access 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.
mrsuyi@chromium.org
When a web page reloads or user changes text size category in Settings,
FontSizeTabHelper gets the category and maps it to a scaling number. This is
hit if the category is not listed in the map defined in
/ios/chrome/browser/web/font_size_tab_helper.mm. In that case, we should
update the code by adding an entry for the new category in that map.
ellyjones@chromium.org
Whether the "differentiate without color" Mac system setting is
enabled. This is checked once, 45 seconds after startup.
ellyjones@chromium.org
Whether the "full keyboard access" Mac system setting is enabled.
This is checked once, 45 seconds after startup.
ellyjones@chromium.org
Whether the "increase contrast" Mac system setting is enabled.
This is checked once, 45 seconds after startup.
ellyjones@chromium.org
Whether the "reduce transparency" Mac system setting is enabled.
This is checked once, 45 seconds after startup.
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
aboxhall@chromium.org
Whether individual accessibility mode flags are set. Tracked when each mode
flag is flipped from false to true. These flags are flipped automatically
when software communicates with Chrome via accessibility APIs. Flags can
only be flipped off by advanced users or for debugging using
chrome://accessibility/ - and that isn't tracked in this histogram.
lpalmaro@chromium.org
alemate@chromium.org
Delay between login_prompt_visible and Chrome OS OOBE startup sound
playback. Depends on sound subsystem initialization time.
Deprecated 12/2016 in Issue 672205 with the addition of
Accessibility.ModeFlag.
dmazzoni@chromium.org
kenjibaheux@google.com
Whether Chrome has enabled accessibility support because it detects
supported assistive technology running, or due to being manually enabled via
a command-line flag (checked once 45 secs after startup).
dmazzoni@chromium.org
nektar@chromium.org
Tracks usage of all public Windows accessibility APIs.
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.
manzagop@chromium.org
The analyzer creation error code. Logged each time analyzer creation fails,
at most once per processed stability debug file.
manzagop@chromium.org
Status of the initialization to collect stability debug files. Logged once,
during the initialization of the stability debug file collection.
manzagop@chromium.org
Number of files found during stability file collection. Logged each time the
stability file collection proceeds (at most once per launch).
manzagop@chromium.org
Status for the collection of a stability debug file. Logged each time a
debug file collection attempt is made.
manzagop@chromium.org
Status for the analysis of the system session state. Logged each time a
debug file is collected.
manzagop@chromium.org
Time spent collecting stability debug information. Logged each time a
collection is performed.
Deprecated 05/2017 in favor of ActivityTracker.Collect.Status.
manzagop@chromium.org
Number of unclean shutdowns, as derived from the stability instrumentation.
Logged each time stability file collection is performed.
Deprecated 05/2017 in favor of ActivityTracker.Collect.Status.
manzagop@chromium.org
Number of unclean shutdowns that can potentially be attributed to system
instability. This should be smaller or equal to UncleanShutdownCount. Logged
each time stability file collection is performed.
manzagop@chromium.org
Status of the minidump writing. Logged each time a writing a minidump is
attempted.
manzagop@chromium.org
Events that occur during crash collection of the debug file. Logged each
time an event of interest occurs during crash debug file collection.
Deprecated 05/2017 in favor of ActivityTracker.CollectCrash.Event.
manzagop@chromium.org
Success of the attempt to open the debug file for deletion. Logged each time
a debug file is opened for deletion during collection from the crash
handler.
manzagop@chromium.org
Status for the collection of a stability debug file. Logged each time a
debug file collection attempt is made from the crash handler.
manzagop@chromium.org
Events pertaining to recording to the debug file. Logged each time an event
of interest occurs wrt debug file recording.
Deprecated 05/2017 in favor of ActivityTracker.Record.Event.
manzagop@chromium.org
Status of internal activity tracking initialization. Logged once, during the
activity tracking initialization.
manzagop@chromium.org
Time spent setting up the stability debugging instrumentation. Logged once,
during setup of the stability debugging instrumentation.
bcwhite@chromium.org
The number of threads being tracked for activities such as waiting for a
lock/event, a thread to join, or a task to run. Analysis of this data can
reveal why a thread will not exit. This value is updated every time a new
thread gets an activity tracked for the first time so will show one count
for every permanent thread but multiple counts for a thread than exits and
is replaced.
bcwhite@chromium.org
The limit on the number of thread trackers that could be allocated from the
persistent memory segment. Trackers beyond this number were allocated from
the heap and thus were not available for analysis. This value is updated on
every "memory full" failure.
csharrison@chromium.org
jkarlin@chromium.org
For a given ad request, logs information related to whether it is isolated
from the top-level context. Logged per ad subresource request.
csharrison@chromium.org
jkarlin@chromium.org
For a given request, logs information related to whether it is marked as an
ad, and whether it is secure (e.g. https). Logged per subresource request.
chelu@chromium.org
True if the anchor element contains an image element, false if it is not.
This histogram is recorded when the anchor element is clicked.
Deprecated 07/2018. Replaced with
AnchorElementMetrics.Clicked.HrefEngagementScore2.
chelu@chromium.org
The target link (href) engagement score of an anchor element. The score is
retrived from the site engagement service. Currently all scores reported are
set to 0. This will soon change. This histogram is recorded when the anchor
element is clicked.
chelu@chromium.org
The site engagement score of the target link (href) of an anchor element.
The score is retrived from the site engagement service. This histogram is
recorded when the anchor element is clicked.
chelu@chromium.org
The site engagement score of the target link (href) of an anchor element.
The score is retrived from the site engagement service. This histogram is
recorded when the anchor element is clicked, and the score is larger than 0.
chelu@chromium.org
True if the anchor element is within an iframe, false if it is not. This
histogram is recorded when the anchor element is clicked.
chelu@chromium.org
True if the target link of the anchor element has the same host as the root
document. This histogram is recorded when the anchor element is clicked.
chelu@chromium.org
True if the target URL of the anchor element and the URL of the root
document only differ by one number, and the number in the target URL equals
the number in the the URL of the root document plus one. This histogram is
recorded when the anchor element is clicked.
chelu@chromium.org
The ratio times 100 between the clickable region area of an anchor element,
and the viewport area. This histogram is recorded when the anchor element is
clicked.
chelu@chromium.org
The ratio times 100 between the distance from the center of the clickable
region of an anchor element to the top edge of the visible region, and the
viewport height. This histogram is recorded when the anchor element is
clicked.
chelu@chromium.org
The ratio times 100 between the distance from the bottom of the clickable
region of an anchor element to the bottom edge of the root frame, and the
viewport height. This histogram is recorded when the anchor element is
clicked.
chelu@chromium.org
The ratio times 100 between the distance from the top of the clickable
region of an anchor element to the top edge of the root frame, and the
viewport height. This histogram is recorded when the anchor element is
clicked.
chelu@chromium.org
The ratio times 100 between the distance from the top of the clickable
region of an anchor element to the top edge of the visible region, and the
viewport height. This histogram is recorded when the anchor element is
clicked.
chelu@chromium.org
The ratio times 100 between the visible clickable region area of an anchor
element, and the viewport area. This histogram is recorded when the anchor
element is clicked.
dfalcantara@chromium.org
What caused ChromeTabbedActivity#onStop() to be called, which indicates that
Chrome is sent to the background.
dfalcantara@chromium.org
What happened when the user hit the system back button in
ChromeTabbedActivity.
fdegans@chromium.org
Reports the FPU capabilities of the Android ARM device. This is recorded
once per browser session during startup.
fgorski@chromium.org
nyquist@chromium.org
Records that a specific background task has been canceled.
fgorski@chromium.org
nyquist@chromium.org
Records that a specific background task has loaded native.
fgorski@chromium.org
nyquist@chromium.org
Records that a specific background task has failed to be scheduled.
fgorski@chromium.org
nyquist@chromium.org
Records that a specific background task has been successfully scheduled.
fgorski@chromium.org
nyquist@chromium.org
Records that a specific background task has been started.
fgorski@chromium.org
nyquist@chromium.org
Records that a specific background task has been stopped by Background Task
Scheduler before it was able to complete itself.
Deprecated 08/2017. Made decision in issue 736066 with already acquired
data. So this is no longer needed.
boliu@chromium.org
Measure time from bindService call to onServiceConnected. This is part of
launching child services on Android that's under Android's control. Recorded
in the first onServiceConnected of a connection.
Deprecated 08/2017. Made decision in issue 736066 with already acquired
data. So this is no longer needed.
boliu@chromium.org
Boolean histogram that records whether bindServiced timed out. Timeout is
recorded in a delayed task, and success is recorded in onServiceConnected
callback.
yfriedman@chromium.org
Android: Count of requests to Chrome browser which are granted to other apps
to read/write user's bookmarks and history. Only records cases when the app
has permission according to Android's permission manager.
yfriedman@chromium.org
Android: Count of requests to Chrome browser which are granted to other apps
to read/write user's bookmarks and history. Only records cases where the app
is a system app or signed by Google.
mdjones@chromium.org
twellington@chromium.org
The duration the Chrome Home bottom sheet was open.
mdjones@chromium.org
twellington@chromium.org
The reason the bottom sheet was opened.
Deprecated 03/2018. Chrome Home is being deprecated.
mdjones@chromium.org
twellington@chromium.org
Records the reciprocal of the velocity of a swipe that did not result in the
bottom sheet opening. This value is recorded in microseconds per dp traveled
and is only recorded if the "chrome-home-swipe-logic" experiment
is set to "velocity".
Deprecated 03/2018. Chrome Home is being deprecated.
mdjones@chromium.org
twellington@chromium.org
Records the reciprocal of the velocity of a swipe that resulted in the
bottom sheet opening and the user navigating to a URL or a different sheet
content. This value is recorded in microseconds per dp traveled.
Deprecated 03/2018. Chrome Home is being deprecated.
mdjones@chromium.org
twellington@chromium.org
Records the reciprocal of the velocity of a swipe that resulted in the
bottom sheet opening but the user taking no action (i.e. the next action is
the sheet closing). This value is recorded in microseconds per dp traveled.
Deprecated 03/2018. Chrome Home is being deprecated.
mdjones@chromium.org
twellington@chromium.org
Records the reciprocal velocity of a swipe that resulted in the bottom sheet
opening. This value is recorded in microseconds per dp traveled and is only
recorded if the "chrome-home-swipe-logic" experiment is set to
"velocity".
Deprecated 01/2018 with the removal of the first version of Chrome Home.
mdjones@chromium.org
twellington@chromium.org
The result of showing the Chrome Home promo when launched from the overflow
menu. This action can only be performed if Chrome Home is enabled.
Deprecated 01/2018 with the removal of the first version of Chrome Home.
mdjones@chromium.org
twellington@chromium.org
The result of showing the Chrome Home promo when launched from the NTP. This
action can only be performed if Chrome Home is disabled.
Deprecated 01/2018 with the removal of the first version of Chrome Home.
mdjones@chromium.org
twellington@chromium.org
The result of showing the Chrome Home promo when launched from startup. This
action can only be performed if Chrome Home is disabled.
Deprecated 01/2018 with the removal of the first version of Chrome Home.
mdjones@chromium.org
twellington@chromium.org
The reason the Chrome Home promo was shown.
Deprecated 04/2018. Replaced with Android.Survey.DownloadResponseCode.
danielpark@chromium.org
The response code of the completed survey download request.
Deprecated 04/2018. Replaced with Android.Survey.InfoBarClosingState.
danielpark@chromium.org
If the infobar was visible when it was closed and if it was closed directly
or not.
Deprecated 04/2018. Replaced with Android.Survey.ShowSurvey.
danielpark@chromium.org
Whether or not the survey was successfully shown after its download.
Deprecated 04/2018. Replaced with Android.Survey.SurveyFilteringResults.
danielpark@chromium.org
The result of the survey filtering process. Each enum represents a different
filter that caught the user. This is recorded on cold starts when we check
if a user qualifies for a survey.
mdjones@chromium.org
twellington@chromium.org
The time between the last time the Chrome Home bottom sheet was closed and
the next time it was opened.
mdjones@chromium.org
twellington@chromium.org
The time between app creation and the first open of the Chrome Home bottom
sheet for this run of Chrome.
mdjones@chromium.org
twellington@chromium.org
Records whether or not the user preference for Chrome Home is set to
enabled. This is recorded whenever the browser is restarted and the state of
Chrome Home is first checked. This metric is only recorded if the user's
preference is set.
estevenson@chromium.org
agrieve@chromium.org
The amount of time Chrome spends blocked on resource extraction. Generally,
extraction is completed in the background but in certain cases a main-thread
getResources() call may block on resource extraction.
estevenson@chromium.org
agrieve@chromium.org
Describes the result of Android resource extraction, and is recorded once
per browser start as part of deferred startup (not at time of extraction).
estevenson@chromium.org
agrieve@chromium.org
The amount of time spent on resource extraction, whether or not extraction
was performed in the background or foreground.
jwanda@chromium.org
Recorded when the user selects a category button when in the Custom Feedback
UI.
jwanda@chromium.org
Recorded when a user selects an option related to their problem within the
Custom Feedback UI.
twellington@chromium.org
tedchoc@chromium.org
Records the largest display dimension in dp during deferred startup. The
display size is not affected by Android N multi-window mode. Clamped at
200dp to 1200dp.
twellington@chromium.org
tedchoc@chromium.org
Records the smallest display dimension in dp during deferred startup. The
display size is not affected by Android N multi-window mode. Clamped at 0 to
1000dp.
shaktisahu@chromium.org
Records the state of the download infobar when the user taps on the
infobar's close button.
shaktisahu@chromium.org
Records various types of messages representing the state of the downloads as
they are shown on the download infobar.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
Recorded when the user selects a filter from the Chrome download manager
navigation drawer.
jming@chromium.org
xingliu@chromium.org
Records instances where the foreground undergoes a lifecycle change (when
the foreground starts, changes pinned notification, or stops).
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
The number of non-incognito download items displayed when the download UI is
initialized.
xingliu@chromium.org
The number of non-incognito download items displayed that are already viewed
by the user at any time, recorded when the download UI is initialized.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
Recorded when a download fails to open.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
Recorded when a download is opened.
dtrainor@chromium.org
The count of Download Home list entry actions taken.
dtrainor@chromium.org
The count of Download Home top level menu actions taken.
dtrainor@chromium.org
The number of items selected when performing a multi-delete action.
dtrainor@chromium.org
The number of items selected when performing a multi-share action.
jming@chromium.org
xingliu@chromium.org
Records instances where a user interacts with a download notification (ie.
clicks on, pauses, resumes, cancels).
jming@chromium.org
xingliu@chromium.org
Records instances when a notification is being launched for the first time
or relaunched due to the need to dissociate the notification from the
foreground (only on API less than 24).
jming@chromium.org
xingliu@chromium.org
Records the number of notifications that are already existing (presumably
displayed) when a new notification is being launched to help understand the
frequency of multiple downloads with downloads as a foreground service
disabled.
jming@chromium.org
xingliu@chromium.org
Records the number of notifications that are already existing (presumably
displayed) when a new notification is being launched to help understand the
frequency of multiple downloads with downloads as a foreground service
enabled.
xingliu@chromium.org
Records how users open audio download files on Android.
xingliu@chromium.org
Records how users open video download files on Android.
dfalcantara@chromium.org
twellington@chromium.org
The extension type for non-incognito download items that match the
"other" filter type. Recorded when the download UI is initialized.
dfalcantara@chromium.org
twellington@chromium.org
The extension type for downloads that match the "other" filter
type. Recorded when a download fails to open.
dfalcantara@chromium.org
twellington@chromium.org
The extension type for downloads that match the "other" filter
type. Recorded when a download is opened.
dfalcantara@chromium.org
twellington@chromium.org
The extension type for downloads that match the "other" filter
type. Recorded when downloads are shared through the download manager.
jming@chromium.org
xingliu@chromium.org
Records instances of DownloadForegroundService stops. The number of
expected stops (stopped) and unexpected stops (task removed, low memory,
etc) can be compared to get a sense of how often the service crashes to see
how it handles restarts. For example, the number of times the service is
stopped because of low memory can be compared to the number of times the
service has been destroyed to see how frequently it occurs. Or, the number
of start sticky's will indicate how often the service is able to restart due
to an unexpected stop.
jming@chromium.org
xingliu@chromium.org
Records instances of DownloadNotificationService stops. The number of
expected stops (stopped) and unexpected stops (task removed, low memory,
etc) can be compared to get a sense of how often the service crashes to see
how it handles restarts. For example, the number of times the service is
stopped because of low memory can be compared to the number of times the
service has been destroyed to see how frequently it occurs. Or, the number
of start sticky's will indicate how often the service is able to restart due
to an unexpected stop.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
The number of downloads shared at the same time.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
Recorded when downloads are shared through the download manager. A recorded
value of "All" indicates that multiple types of downloads were
shared.
shaktisahu@chromium.org
Recorded when the user clicks the info button on download home to toggle the
storage info. The state recorded is after the visibility is toggled.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
The percentage of total storage downloads consume.
xingliu@chromium.org
The duration between when an audio file is downloaded and when the file is
opened, only recorded when the user opens the file in download home UI.
xingliu@chromium.org
The duration between when a video file is downloaded and when the file is
opened, only recorded when the user opens the file in download home UI.
twellington@chromium.org
The number of selected items the user opened in new tabs from the native
Android history page.
twellington@chromium.org
The number of selected items the user removed from the native Android
history page.
Not being recorded as of 2017.
mariakhomenko@chromium.org
Measures the amount of time spent in the getInstantAppIntent() API call.
thildebr@chromium.org
Measures the amount of time spent in the getInstantAppIntent() API call when
the API was able to find an Instant App for the URL. This is recorded for
external intents coming into Chrome only and measures the delay before we
dispatch the intent to Instant Apps.
thildebr@chromium.org
Measures the amount of time spent in the getInstantAppIntent() API call when
the API was not able to find an Instant App for the URL. This is recorded
for external intents coming into Chrome that get checked for their Instant
Apps eligibility, but end up being loaded in Chrome. It's critical to keep
this latency low for our startup performance.
thildebr@chromium.org
For intents to load a web page in browser from Instant Apps, records where
the request to load came from.
thildebr@chromium.org
Records events that occur when a user clicks on an intent:// URL that is
dispatched to instant apps. The intent:// URLs to the Instant Apps are
explicitly disabled unless they are launched from Google SERP, but we record
other attempts as well.
thildebr@chromium.org
Records whether any given successful page load (for http and https schemes
only) could have been handled by an Instant App.
thildebr@chromium.org
Measures the time from when we first received an eligible intent for Instant
Apps to the time we processed it in the case where the Instant Apps activity
had to invoke a fallback intent. This happens only on Android N and older.
thildebr@chromium.org
Measures the amount of time spent triaging an incoming event to decide
whether it needs to be routed to Instant Apps. This is time from
ChromeLauncherActivity.onCreate() call to the time either startActivity() is
called or the request proceeds. This is a superset of
Android.InstantApps.ApiCallDurationWith[out]App.
thildebr@chromium.org
Logs the reasons the banner is shown or hidden on an instant apps eligible
pages. Triggered every time asynchronous Instant Apps API indicates the
currently loaded page is instant apps eligible. Does not include Instant
Apps eligible pages loaded directly through the omnibox.
tedchoc@chromium.org
thildebr@chromium.org
When an external application was launched as a result of a form submit, this
tracks whether there was a user gesture associated with the submit.
jaekyun@chromium.org
Signifies whether the last shared app information is retrieved successfully
or not. This is logged when configuring the direct sharing menu item.
rsesek@chromium.org
Reports the kernel major and minor version from the utsname.release field.
The low 16 bits of each version are combined into a 32-bit integer. The
range is from [0x00020006,0x0004000a] to track kernel versions 2.6 through
4.10.
dskiba@chromium.org
Whether VIEW intent sent explicitly to .Main activity was dispatched by
onCreate().
dskiba@chromium.org
Whether VIEW intent sent explicitly to .Main activity was dispatched by
onNewIntent().
dskiba@chromium.org
Sources (ExternalAppId) of undispatched VIEW intents sent explicitly to
.Main activity alias.
dmurph@chromium.org
Recorded when the user presses a button in the 'Manage Space' screen for
Chrome. Note: the 'Clear App Data' option is likely incorrect, as the result
of that button disables UMA recording (as we factory reset the app).
dskiba@chromium.org
The duration of each failed ActivityManager.getMyMemoryState() call made by
MemoryPressureMonitor.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
dskiba@chromium.org
The duration of each successful ActivityManager.getMyMemoryState() call made
by MemoryPressureMonitor.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
dskiba@chromium.org
Memory pressure notifications sent by Android through ComponentCallbacks2.
This metric was added 04/2018; for prior data for the browser process see
MemoryAndroid.NotificationBackground and
MemoryAndroid.NotificationForeground.
jaekyun@chromium.org
The number of moderate bindings which were kept while Chrome process is in
the foreground. This is logged right before Chrome process goes into the
background.
twellington@chromium.org
tedchoc@chromium.org
Renaming the old tab metadata file failed during multi-instance migration.
Only true is recorded.
twellington@chromium.org
tedchoc@chromium.org
The new tab metadata file already existed when multi-instance migration was
attempted. Only true is recorded.
twellington@chromium.org
tedchoc@chromium.org
Records on every metrics upload whether the activity is running in Android N
multi-window mode or not.
twellington@chromium.org
tedchoc@chromium.org
Records whether the screen width is below 600dp when the activity is in
Android N multi-window mode. True if the screen width is less than 600dp and
false if is greater than or equal to 600dp.
twellington@chromium.org
tedchoc@chromium.org
Records the screen height in dp when the activity is in Android N
multi-window mode. Clamped at 200dp to 1200dp.
twellington@chromium.org
tedchoc@chromium.org
Records the screen width in dp when the activity is in Android N
multi-window mode. Clamped at 200dp to 1200dp.
twellington@chromium.org
tedchoc@chromium.org
Records the screen width in dp when the activity is in Android N
multi-window mode and the width is below 600dp.
michaelbai@chromium.org
The return value of NativeLibraryPreloader.loadLibrary() in browser process,
is recorded once per browser process start.
michaelbai@chromium.org
The return value of NativeLibraryPreloader.loadLibrary() in renderer
process, is recorded once per renderer process start.
finkm@chromium.org
Counts impressions of the NTP on Android. It also counts potential
impressions. A potential impression is a place where it would make sense to
open the NTP instead of the current view. E.g. the no-tab view is counted as
a potential impression since this view could be replaced with the NTP. For
better comparison regular impressions are also counted. The no-tab view
counting happens right after the user closed the last tab and the regular
impression counting happens at construction time of the NTP (=whenever a new
tab is opened).
chili@chromium.org
State of a download or offline page request at user-initiated cancel.
tedchoc@chromium.org
Recorded every time AutocompleteController.java interacts with
autocomplete_controller_android.cc via an index reference to an item.
Indicates how often the match referenced by Java is different from the match
referenced by C++ at that position.
mdjones@chromium.org
twellington@chromium.org
amaralp@chromium.org
Records how the omnibox was focused.
nyquist@chromium.org
Records the size of the user's cache at startup on Android O and above.
nyquist@chromium.org
At startup, records the space on disk taken by Chrome application including
APK resources, compiled libraries, and extracted native code. Only recorded
for Android O and above.
nyquist@chromium.org
Records the size of the user's data directory at startup on Android O and
above. Does not include cache size.
finnur@chromium.org
twellington@chromium.org
Measures the amount of time the BitmapScaler spent scaling a bitmap.
finnur@chromium.org
twellington@chromium.org
Measures the total number of images served from the high-res cache during
the lifetime of the dialog.
finnur@chromium.org
twellington@chromium.org
Measures the total number of images sent for decoding during the lifetime of
the dialog.
finnur@chromium.org
twellington@chromium.org
The percentage of out-of-memory decoding failures, per batch of photos
decoded. Intended to help identify if there are browsers where decoding
fails 100% of the time. Be wary at looking at other numbers in the
histogram, as a value emitted at, say, 50% may represent one failure in a
two-item decoding or 50 failures in a hundred-item decoding. These are
qualitatively different experiences for a user.
finnur@chromium.org
twellington@chromium.org
The percentage of runtime error decoding failures, per batch of photos
decoded. Intended to help identify if there are browsers where decoding
fails 100% of the time. Be wary at looking at other numbers in the
histogram, as a value emitted at, say, 50% may represent one failure in a
two-item decoding or 50 failures in a hundred-item decoding. These are
qualitatively different experiences for a user.
finnur@chromium.org
twellington@chromium.org
Records which action the user takes in the PhotoPickerDialog.
finnur@chromium.org
twellington@chromium.org
Measures the total number of files returned from the enumeration operation.
Measured once at the end of the enumeration operation.
finnur@chromium.org
twellington@chromium.org
Measures the enumeration rate (files per tenths of a second). Measured once
at the end of the enumeration operation.
finnur@chromium.org
twellington@chromium.org
Measures the amount of time the BitmapScaler spent enumerating files on
disk. Measured once at the end of the enumeration operation.
finnur@chromium.org
Records whether the EXIF orientation directive is present and what it is set
to. Collected once per decoded image, but only on Android N and above (and
when no IO error occurs).
finnur@chromium.org
twellington@chromium.org
Measures the byte count of a decoded image. Only recorded on successful
decodes.
finnur@chromium.org
twellington@chromium.org
Measures the amount of time it takes the decoder to decode one image. Only
recorded on successful decodes.
finnur@chromium.org
twellington@chromium.org
Measures the amount of time it takes to process one decode request end to
end (RPC and actual decoding of the bits by utility process). Recorded
whether or not the RPC/decode request was successful.
finnur@chromium.org
twellington@chromium.org
Measures the amount of time it takes to upscale a bitmap from the low-res
cache. Recorded only when there a cache miss from the high-res bitmap but a
cache hit from the low-res (placeholder) bitmap.
hanxi@chromium.org
pkotwicz@chromium.org
Measures the amount of time spent querying for whether a WebAPK is already
installed.
huayinz@chromium.org
Records the number of other devices listed in recent tabs page when recent
tabs page is loaded.
huayinz@chromium.org
Records the number of recently-closed tabs shown in recent tabs page when
recent tabs page is loaded.
huayinz@chromium.org
Records the total number of tabs listed in recent tabs page (sum of all tab
from other devices plus recently-closed tabs) when recent tabs page is
loaded.
aberent@chromium.org
Whether Chrome tried to restore its settings from a previous device or
installation, and what happened when it did. Only recorded on first run.
peter@chromium.org
rsesek@chromium.org
Reports the status of the seccomp-bpf sandbox in photo picker decoding
processes. Anything other than "Sandbox Engaged" indicates the
sandbox is not turned on. See https://crbug.com/477049.
rsesek@chromium.org
Reports the level of kernel support for the seccomp-bpf sandbox using
prctl(PR_SET_SECCOMP).
rsesek@chromium.org
Reports the status of the seccomp-bpf sandbox in renderer processes.
Anything other than "Sandbox Engaged" indicates the sandbox is not
turned on. See https://crbug.com/477049.
rsesek@chromium.org
Reports the level of kernel support for the seccomp-bpf sandbox using the
seccomp system call.
finnur@chromium.org
peter@chromium.org
Records the number of images selected in either the new Photo Picker or the
standard Android file picker. Note: Only recorded in situations determined
to warrant the new Photo Picker (not, for example, if mixed content, like
images and text files, was requested).
peter@chromium.org
Records the scope of accepted content for a select file dialog when shown by
a Web developer.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from checking for
whether play services is available.
estevenson@chromium.org
wnwen@chromium.org
Measures the amount of time due to a StrictMode violation from checking for
whether a package is Google signed.
Deprecated 05/2016 in Issue 582539 with the removal of document mode.
hartmanng@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from fetching the
DocumentMode shared preferences file.
Deprecated 05/2016 in Issue 582539 with the removal of document mode.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from document mode
loading its prioritized tab's state.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from fetching and
possibly creating the downloads directory.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from custom
notification builder through date formatting.
yfriedman@chromium.org
wnwen@chromium.org
Measures the amount of time due to a StrictMode violation from calling out
to Android activity manager.
wnwen@chromium.org
peconn@chromium.org
Measures the amount of time due to a StrictMode violation from snippet UI
through date formatting.
wnwen@chromium.org
yfriedman@chromium.org
Measures time spent during StrictMode-whitelisted code in
TabPersistentStore.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from fetching for
the thumbnail cache directory.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from looking up a
webapp's MAC on startup.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from fetching for
creating the webapp directory.
wnwen@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from reading and
saving webapp state.
hartmanng@chromium.org
yfriedman@chromium.org
Measures the amount of time due to a StrictMode violation from fetching the
Webapp shared preferences file.
danielpark@chromium.org
The response code of the completed survey download request.
danielpark@chromium.org
If the infobar was visible when it was closed and if it was closed directly
or not.
danielpark@chromium.org
Whether or not the survey was successfully shown after its download.
danielpark@chromium.org
The result of the survey filtering process. Each enum represents a different
filter that caught the user. This is recorded on cold starts when we check
if a user qualifies for a survey.
ssid@chromium.org
Measures whether Chrome low-end detection logic based on RAM size matches
the Android system utility value for isLowRamDevice(). This is recorded once
per browser start and may be recorded in the renderer if isLowEndDevice()
bit is checked.
thildebr@chromium.org
The distribution of results when running ExternalNavigationHandler, this
shows how often we send intents to be handled by other applications.
twellington@chromium.org
The number of bytes read for the other tab state's metadata file when
merging tab states in Android N+.
twellington@chromium.org
The number of normal and incognito tabs merged (for Android N+
multi-instance). This will be logged for both cold-start and non-cold-start
merging assuming that the native library is loaded.
twellington@chromium.org
Measures the amount of time it takes to restore state for each merged tab
(for Android N+ multi-instance). This will only be logged for non-cold-start
merging, because restoring merged tabs is not distingushed from restoring
regular tabs on cold start.
wnwen@chromium.org
dfalcantara@chromium.org
The number of bytes written for the tab metadata file.
jamwalla@chromium.org
Records whether the historyUrl parameter to loadDataWithBaseUrl is empty/
null, the same as the baseUrl parameter, or different from baseUrl.
smcgruer@chromium.org
Records if a data url passed to loadUrl had a '#' character. This is to be
used in the effort to deprecate the incorrect treatment of '#' characters in
data URIs; see http://crbug.com/823666#c30.
changwan@chromium.org
How long it takes to initialize a WebViewChromiumFactoryProvider. This is
the first major phase of the WebViewChromium construction.
changwan@chromium.org
How long it takes to initialize a WebViewProvider, the first time that one
is initialized. WebViewProvider initialization is the second major phase of
WebViewChromium construction. The first initialization is recorded
separately because it is usually much slower than subsequent ones.
changwan@chromium.org
How long it takes to initialize a WebViewProvider, the first time that one
is initialized. WebViewProvider initialization is the second major phase of
WebViewChromium construction. When it is not the first time, it is faster
and thus recorded separately.
changwan@chromium.org
The version of the target SDK of the app WebView is running in. This is
recorded at WebView creation.
paulmiller@chromium.org
changwan@chromium.org
Indicates whether variations is enabled. We want to know how enabling
variations affects metrics, but we can't enable variations as a variations
study, since variations can't enable/disable itself. Instead, WebView
hard-codes a random variable for enabling variations, and reports the result
in this histogram.
dtrainor@chromium.org
When a user closes a tab an undo toast will popup on certain devices giving
the user the chance to undo closing that tab. This stat tracks how the user
interacts with that UI and what actions they take. A cold start means that
the undo bar wasn't showing when it was triggered to show again. A warm
start means that it was. Warm starts can happen when the user closes
multiple tabs close together. When the undo bar is dismissed, all closes
that were queued up to be undone are committed. This can happen either by a
timeout or by an action by the user to move to another part of the UI.
khushalsagar@chromium.org
If the frame rate for the image animation can not be reached, frames in the
animation are skipped to catch up to the desired frame. This metric tracks
the number of frames skipped during catch up, and can be used to assess the
smoothness of these animations. It records the number of frames skipped each
time the animation is ticked forward to draw the next frame. In the ideal
case, where the animation can be drawn at the desired rate, 0 frames should
be skipped. Note that skipping of frames can also be triggered if the
animation was intentionally paused (on becoming off-screen, or the tab being
hidden).
dominickn@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
usage of the BeforeInstallPromptEvent, which allows developers to control
when an app banner appears. The events in this histogram are not mutually
exclusive - for example, preventDefault() must be called if prompt() is
called.
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.
dominickn@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 status code logged by the app banner system as it processes a site's
eligibility for an app banner. Every request for a banner will be logged in
a bucket of this histogram.
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.
dominickn@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 number of minutes between the first recorded visit to an origin and the
time when the banner is actually shown.
dominickn@chromium.org
App banners promote an application related to the current website, and are
requested specifically through the current page's HTML. This stat
specifically tracks a user's response to a displayed banner.
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
Counts the number of appcached page loads for secure vs insecure origins.
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.
spqchan@chromium.org
The number of times an AppleScript event gets called.
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.
Deprecated 11/2017 in issue 600915 with the removal of app list on platforms
other than Chrome OS.
mad@chromium.org
Interactions with the App Launcher promo dialog.
newcomer@chromium.org
The number of apps launched from the launcher. This is logged each time an
app is launched.
newcomer@chromium.org
The number of apps launched from the fullscreen launcher. This is logged
each time an app is launched. The bucket denotes whether the app is
suggested.
weidongg@chromium.org
The different ways to move an app in app list's apps grid. Logged when the
app moving succeeds.
vadimt@chromium.org
Number of apps (including ones in folders) with Chrome badge, across all
Launcher pages. This is gathered per open-launcher event.
calamity@chromium.org
The amount of time it takes to build the app list UI. This is logged each
time the app list is built from scratch.
App list doesn't support doodles anymore.
calamity@chromium.org
The number of user interactions with the app list doodle. This is logged
once per action.
wutao@chromium.org
Relative smoothness of animations of showing and hiding app list folder.
100% represents ideally smooth 60 frames per second. 50% represents only 30
frames per second is achieved during the animations. 0% should not happen.
This metric is recorded exactly once when the user starts the folder
animation in the launcher.
newcomer@chromium.org
The number of times folders are opened in the app list. This is logged when
the folder is clicked.
wutao@chromium.org
Elapsed time from the input event to hide the launcher UI. This is logged
each time the launcher is dismissed by pressing search key, clicking shelf
button, or focusing out side of the launcher.
Deprecated 03/2018 with Mash AppList refactoring.
tapted@chromium.org
The trigger that caused the app list to be enabled. Recorded when the user
first shows the app list. If not shown after one hour, will be recorded
then. If Chrome was not running at the one-hour mark, will be recorded
during the next Chrome startup.
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.
newcomer@chromium.org
The source used to switch pages in the app list's app grid. Logged when the
page switch succeeds.
Replaced with Apps.AppListPeekingToFullscreenSource on 9/2017.
newcomer@chromium.org
The source which transitions the app list from Peeking to Fullscreen. This
is logged when the transition method is used.
hejq@chromium.org
The state of a Play Store app search request.
newcomer@chromium.org
The number of times the applist searchbox has been activated. This is split
by keystroke, mouse press, and gesture tap activations. This is gathered
each time the searchbox goes from inactive to active, not necessarily empty
to non-empty.
tapted@chromium.org
The number of searches that are started in the app list. This is gathered
each time the app list search box transitions from empty to non-empty.
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.
newcomer@chromium.org
The state of the app list when a search result was opened.
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.
wutao@chromium.org
Elapsed time from the input event to show the launcher UI. This is logged
each time the app list is shown by pressing search key, clicking shelf
button, or swiping from shelf.
newcomer@chromium.org
The number of times the different sources for showing the app list are used.
This is logged when the app list is shown.
newcomer@chromium.org
The number of transitions from the different AppListStates. This is gathered
each time the launcher transitions from various states in
AppListView::SetState (Peeking, Half, Fullscreen All Apps, Fullscreen
Search, and Closed). Not all state transitions are collected because they
are not meaningful in measuring user activity. This metric is only recorded
when the Fullscreen App List feature is enabled.
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.
Deprecated 07/2016 in Issue 600915 with the removal of the app list on
Windows.
tapted@chromium.org
The amount of time spent in warmup (in WarmupForProfile call). This will
tell us how long warmup blocks the UI.
jackhou@chromium.org
Counts which major milestone versions of app_mode_loader are sending
--app-shim-error. --app-shim-error is sent as a command line argument to
Chrome when app_mode_loader was unable to dyload the Chrome Framework and
call ChromeAppModeMain. For example, when Chrome updates from 32-bit to
64-bit, an older shim will find the new framework version but fail to dyload
it.
newcomer@chromium.org
The total number of apps in folders ignoring OEM folders. This is logged
each time the app list is initialized. The
"FullscreenAppListDisabled" suffix has been deprecated.
=newcomer@chromium.org
The number of times a certain command was executed by a context menu, split
by whether the context menu came from an app, or another part of the system
UI.
=newcomer@chromium.org
The show source (touch, mouse, keyboard, etc) for a context menu. Split by
the component from which the context menu originated.
=newcomer@chromium.org
The user journey time for a ContextMenu, defined as the time between
launching a context menu and the context menu's close callback being
activated. Not recorded whenever the context menu is not for an app icon on
the shelf.
tbarzic@chromium.org
The amount of time needed to create a lock screen apps profile. This metric
is recorded only if the profile creation was successful. The lock screen
apps profile is created if the user has an app enabled on Chrome OS lock
screen, and is used as the context in which the app is launched on top of
the lock screen.
tbarzic@chromium.org
Boolean indicating whether the lock screen apps profile creation succeeded.
The lock screen apps profile is created if the user has an app enabled on
Chrome OS lock screen, and is used as the context in which the app is
launched on top of the lock screen.
tbarzic@chromium.org
The size of a data item stored in the lock screen data item storage using
chrome.lockScreen.data API as sent from the app - the item will be encrypted
before getting stored in the storage.
tbarzic@chromium.org
The size of an encrypted data item stored in the lock screen data item
storage using chrome.lockScreen.data API.
tbarzic@chromium.org
The amount of time it took to complete a lock screen data item storage
operation. Reported only on the operation failure.
tbarzic@chromium.org
The amount of time it took to complete a lock screen data item storage
operation. Reported only on the operation success.
tbarzic@chromium.org
The result of a lock screen data item storage operation returned through
chrome.lockScreen.data extension API.
tbarzic@chromium.org
The number of data items saved in the lock screen data item storage per app.
This is recorded on startup, when the app attempts to use the
chrome.lockScreen.data API.
tbarzic@chromium.org
Reported when a user attempts to launch a note taking app on the lock
screen. It reports the note taking app state in the lock screen apps profile
at the launch attempt time - for example, whether the app was enabled, or
whether the app had been terminated and an app reload was attempted.
tbarzic@chromium.org
tbuckley@chromium.org
The amount of time a lock screen enabled app window spent in a certain state
during the app window activity. The state to which the histogram refers to
is defined by the suffix. The metric is logged upon leaving the associated
state.
tbarzic@chromium.org
tbuckley@chromium.org
The note taking action availability state on the lock screen, recorded when
the user session is locked.
tbarzic@chromium.org
tbuckley@chromium.org
The state in which lock screen enabled note taking app was when the note
taking session ended.
tbarzic@chromium.org
tbuckley@chromium.org
The amount time a lock screen app had been launching when the app launch was
canceled. Logged if the lock screen app session ends before the lock screen
app window is shown.
tbarzic@chromium.org
tbuckley@chromium.org
Ordinal number of a note taking app launch request from a lock screen within
a lock screen session. If a note taking app is launched n times during a
single lock screen session, this histogram will be reported with values 1
through n. The launch counter is reset on screen unlock.
tbarzic@chromium.org
tbuckley@chromium.org
The user action that launched note taking from the lock screen.
tbarzic@chromium.org
Reported when a note taking app is unloaded from the lock screen apps
profile while lock screen note taking is available. Reports the unload
reason type, which can be used to deduce whether the app can be reloaded in
the profile. The app unload event is not reported if the app is unloaded due
to lock screen note taking becoming unavailble (e.g. when the user unlocks
the screen).
tbarzic@chromium.org
tbuckley@chromium.org
Amount of time needed to install a copy of a lock screen note taking app
into lock screen apps profile.
tbarzic@chromium.org
tbuckley@chromium.org
The reason the note taking on lock screen was ended (and lock screen app
window was closed).
tbarzic@chromium.org
Reported when a note taking app is terminated in the lock screen apps
profile. It reports the number of times the app was reloaded in the lock
screen apps profile during the current lock screen session (prior to the
termination).
tbarzic@chromium.org
tbuckley@chromium.org
The amount of time needed to load a note taking app window contents on the
lock screen - i.e. the time passed from the user requesting an app launch to
the app window contents being loaded.
tbarzic@chromium.org
tbuckley@chromium.org
The amount of time needed to launch a note taking app window from the lock
screen - i.e. the time passed from the user requesting an app launch to the
app window appearing on the screen.
tbarzic@chromium.org
tbuckley@chromium.org
The action the user took on the lock screen UI shown when lock screen app
window is in background, shown under the lock screen.
derat@chromium.org
jdufault@chromium.org
The result of attempting to launch a default note-taking app on Chrome OS.
Only reported if the preferred app was unspecified or failed to launch.
derat@chromium.org
jdufault@chromium.org
The result of attempting to launch the user-specified preferred note-taking
app, if any, on Chrome OS.
newcomer@google.com
The number of folders that users have in their Launcher. Includes the OEM
folder. This metric is recorded every time the launcher is shown.
weidongg@chromium.com
The number of pages that users have in the top level apps grid of their
Launcher. This metric is recorded every time the launcher is shown.
weidongg@chromium.com
The number of pages that are not full in the top level apps grid of
Launcher. This metric is recorded every time the launcher is shown.
wutao@chromium.org
Relative smoothness of animations of launcher pagination transitions. 100%
represents ideally smooth 60 frames per second. 50% represents only 30
frames per second is achieved during the animations. 0% should not happen.
This metric is recorded exactly once when the user starts the pagination
transition animation of the launcher.
vadimt@chromium.org
Relative smoothness of animations of peeking launcher state transitions.
100% represents ideally smooth 60 frames per second. 50% represents only 30
frames per second is achieved during the animations. 0% should not happen.
This metric is recorded exactly once when the user switches states of the
launcher.
stevenjb@chromium.org
The type of app window opened (through the chrome.app.window API).
elijahtaylor@google.com
shihuis@google.com
The time elapsed for booting up the ARC instance.
elijahtaylor@google.com
shihuis@google.com
The number of ARC apps open at any given time. Collected every 5 minutes.
This indicates both how many users are engaging with apps and, when they do
engage, how many apps they are engaging with at a time.
warx@chromium.org
Record the time to build ARC app shortcut items on menu model. We get the
needed metadata from Android and decode icons in the utility process. It is
an asynchronous procedure so we need to know the longest waiting time.
elijahtaylor@google.com
shihuis@google.com
Total number of ARC apps installed on a device measured at startup. Note:
This includes launchable apps that are installed by default, such as Play
Store and Settings, as well as any vendor specific apps.
elijahtaylor@google.com
shihuis@google.com
The relative time of a boot progress event since the ARC starts.
elijahtaylor@google.com
xzhou@google.com
Code installation result for ARC boot continue.
elijahtaylor@google.com
xzhou@google.com
Total time needed to check the integrity of host generated code. If
signature checking fails, it also includes the time to regenerate and sign
the code.
elijahtaylor@google.com
xzhou@google.com
Host code relocation result.
elijahtaylor@google.com
xzhou@google.com
Time needed to relocate boot*.art files.
elijahtaylor@google.com
xzhou@google.com
Time needed to sign boot*.art files.
elijahtaylor@google.com
xzhou@google.com
Code verification result for host generated code for boot for login screen.
elijahtaylor@google.com
xzhou@google.com
Time needed to verify host generated code.
alexchau@google.com
emaxx@google.com
Elapsed time from the policy update notification sent to ARC to the
corresponding successfully obtained compliance report from CloudDPS.
elijahtaylor@google.com
yusukes@google.com
The number of ARC container lifetime events. One START event and up to one
non-START event are recorded per ARC session, which ends when the user opts
out from ARC or signs out.
elijahtaylor@google.com
yusukes@google.com
The number of times ARC container crashes and automatically restarts in one
ARC session, which ends when the user opts out from ARC or signs out.
elijahtaylor@google.com
shihuis@google.com
ARC use time. The use time is incremented in regular intervals while android
container is active. Reported at most once a day, at which point accumulated
time is reset (which means that sum of reported times for a OS version would
give an estimate of ARC usage time per OS version).
yusukes@google.com
khmel@google.com
How long the user sees the spinning icon waiting for ARC container boot.
Zero when the container has already been up and running when the user
launches the ARC app.
yusukes@google.com
khmel@google.com
Elapsed time from the when UI is shown after login to when the user
activates first ARC app.
alexchau@google.com
emaxx@google.com
Elapsed time from the signing in process start to a successfully obtained
compliance report from CloudDPS.
alexchau@google.com
emaxx@google.com
Elapsed time from ARC startup to a successfully obtained compliance report
from CloudDPS. This value is not reported during the first startup when
signing in happens.
Deprecated April 2018 and replaced by ChromeOS.Apps.IntentPickerAction.
elijahtaylor@google.com
shihuis@google.com
ARC intent handler action taken by user.
Deprecated April 2018 and replaced by
ChromeOS.Apps.IntentPickerDestinationPlatform.
elijahtaylor@google.com
shihuis@google.com
ARC intent handler destination platform. The destination may be specified
due to the user explicit selection or a previously stored preference.
elijahtaylor@google.com
shihuis@google.com
Cumulative count of low memory kills in one user session.
cywang@google.com
elijahtaylor@google.com
shihuis@google.com
When Chrome OS is in low memory state, TabManager kills some victims to free
memory. This value is the elapsed time between TabManager receiving the low
memory notification and the first kill.
elijahtaylor@google.com
shihuis@google.com
The memory size freed by each low memory kill event.
elijahtaylor@google.com
shihuis@google.com
The elapsed time to last low memory kill event.
elijahtaylor@google.com
levarum@google.com
Native bridge used for ARC. Can be unknown and none. This is collected along
with Arc.State during every metrics recording interval, so it is in every
record uploaded to the server. This is required because this value is used
to categorize all other data in the dashboard as collected with specific
native bridge in use.
elijahtaylor@google.com
shihuis@google.com
Cumulative count of OOM kills in one user session.
elijahtaylor@google.com
shihuis@google.com
The oom_badness score of a OOM killed process as reported by kernel.
elijahtaylor@google.com
shihuis@google.com
The elapsed time since last OOM kill event.
elijahtaylor@google.com
shihuis@google.com
Arc OptIn action taken by user.
elijahtaylor@google.com
shihuis@google.com
Arc OptIn cancelation reason.
elijahtaylor@google.com
khmel@google.com
Arc OptIn flow result.
elijahtaylor@google.com
Arc Silent Auth Code status. This status is set during the ARC OptIn flow.
khmel@google.com
Arc Silent Auth Code status. This status is set during the ARC
reauthorization flow.
hejq@chromium.org
Time between sending an Play Store app discovery request and the storing
returned results.
hejq@chromium.org
The total number of returned apps of a Play Store app discovery query.
hejq@chromium.org
The number of returned instant apps of a Play Store app discovery query.
hejq@chromium.org
The number of returned uninstalled apps of a Play Store app discovery query.
yusukes@google.com
khmel@google.com
Elapsed time from the when the user agrees ToS to when the Play Store window
is shown to the user.
alexchau@google.com
phweiss@google.com
The result (success or the type of failure) of ARC provisioning. The base
value has been deprecated on 2016-09-15 in favour of per user type values.
alexchau@google.com
phweiss@google.com
Elapsed time from the signing in process start to call to onSignInFailed.
alexchau@google.com
phweiss@google.com
Elapsed time from the signing in process start to successful call to
onSignInComplete.
khmel@google.com
The result (success or the type of failure) of ARC reauthorization.
elijahtaylor@google.com
The time it takes for ARC to shut down. This value is recorded on ARC
shutdown as the time is takes for the init process to exit after setting
'sys.powerctl shutdown'. It is reported on the next ARC startup to avoid
sending data during shutdown.
elijahtaylor@google.com
shihuis@google.com
Whether ARC is enabled or not. Before M56 this was collected only on login
and when ARC was enabled or disabled. From M56 forward this is collected
during every metrics recording interval, so it is in every record uploaded
to the server. This is required because this value is used to categorize
all other data in the dashboard as collected with ARC enabled or not. This
is true even for users who are running on ecryptfs and skipped Ext4
migration; even though ARC Apps do not run until migration is complete on N
or later systems.
elijahtaylor@google.com
shihuis@google.com
khmel@google.com
Similar to "Arc.State" metric but has separation by user type.
phongo@google.com
brunokim@google.com
The result (success or the type of failure) of ARC supervision transition
events.
jhorwich@chromium.org
elijahtaylor@chromium.org
shihuis@google.com
maajid@chromium.org
Counts user interactions with ARC by type, such as ARC app launches via the
shelf or launcher.
elijahtaylor@google.com
The status of account check before GMS Sign-in.
elijahtaylor@chromium.org
Elapsed time waiting for the account status check to be completed. This is
not recorded in case of account status check failure.
elijahtaylor@chromium.org
Number of attempts done while waiting for the check-in task to be completed.
0 means that device was already checked-in. This is recorded in case
check-in task is completed successfully.
elijahtaylor@chromium.org
Elapsed time waiting for the check-in task to be completed. This is recorded
in case check-in task is completed successfully.
elijahtaylor@chromium.org
Elapsed time waiting for network connection before starting other
authorization operations.
elijahtaylor@chromium.org
Elapsed time waiting for GMS sign-in to complete.
Renamed to Arc.LowMemoryKiller.FreedSize on 2016/03/24.
elijahtaylor@google.com
The memory size freed by each low memory kill event.
Renamed to Arc.LowMemoryKiller.TimeDelta on 2016/03/24.
elijahtaylor@google.com
The elapsed time to last low memory kill event.
afakhry@chromium.org
The lock screen action has two accelerators: - Ctrl+Shift+L which is
deprecated. - Search+L which is new. This histogram shows the number of
times each accelerator (deprecated and new) is used.
Deprecated 01/2017 for Issue 672905.
afakhry@chromium.org
The switch to the next IME action has two accelerators: - Shift+Alt which is
deprecated. - Ctrl+Shift+Space which is new. This histogram shows the
number of times each accelerator (deprecated and new) is used.
afakhry@chromium.org
Showing the IME menu bubble has two accelerators: - Alt+Shift+K which is
deprecated. - Search+Shift+K which is new. This histogram shows the number
of times each accelerator (deprecated and new) is used.
afakhry@chromium.org
Opening the task manager has two accelerators: - Shift+Esc which is
deprecated. - Search+Esc which is new. This histogram shows the number of
times each accelerator (deprecated and new) is used.
afakhry@chromium.org
Toggling the high contrast display mode has two accelerators: -
Search+Shift+H which is deprecated. - Ctrl+Search+H which is new. This
histogram shows the number of times each accelerator (deprecated and new) is
used.
Deprecated 02/2017 due to lack of usage.
kuscher@google.com
rbyers@chromium.org
Number of active touch-points when a new touch-point is added.
kuscher@google.com
The show type of the active window tracked over time by logging on a regular
basis (30 minutes).
Deprecated 10/2016 for Issue 616581.
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.
bruthig@chromium.org
tdanderson@chromium.org
The number of seconds between task window activations triggered by users
clicking or tapping on a window, as recorded by the Desktop_SwitchTask user
action. Recorded on Chrome OS only. Task switches from other sources are
ignored and do not affect this metric. In other words, if a user performs
the following steps (1) click on task window 'A' (2) Alt+Tab to task 'Z'(3)
click on task window 'B', then this will result in a sample recorded for the
time delta between activating task window 'A'and 'B'.
mcasas@chromium.org
dcastagna@chromium.org
Whether a display has a "CTM" matrix properties that can be used
to set a color transform matrix. Recorded every time there is a display
configuration update.
mcasas@chromium.org
dcastagna@chromium.org
This boolean keeps track if an ICC file was downloaded correctly (if true)
or a local file was reused instead.
Deprecated 10/2017, replaced by Ash.DisplayColorManager.IccFileDownloaded
mcasas@chromium.org
dcastagna@chromium.org
This boolean keeps track if a request for an ICC for a specific product id
has been successful or not.
mcasas@chromium.org
dcastagna@chromium.org
This boolean keeps track if a Display update (i.e. when connecting a new
one) carried valid ColorSpace information.
mcasas@chromium.org
dcastagna@chromium.org
Whether we could parse a valid product id from a display EDID. Recorded
every time there is a display configuration update.
kuscher@google.com
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, keyboard 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 for UI components owned by Ash.
For browser gestures, see Event.Touch.GestureType.
kuscher@google.com
The type of the window which is put into immersive fullscreen. Immersive
fullscreen is entered via the F4 key.
xiaoyinh@google.com
The count of auth method switching actions in ChromeOS lock screen.
xiaoyinh@google.com
The usage of different auth methods (PIN / Password / Smartlock) in ChromeOS
lock screen clamshell mode.
xiaoyinh@google.com
The usage of different auth methods (PIN / Password / Smartlock) in ChromeOS
lock screen tablet mode.
xiaoyinh@google.com
The number of incorrect password entered in ChromeOS lock screen until the
user gives up (switch pods or user sign out the current session or shutdown
the device).
xiaoyinh@google.com
The number of incorrect password entered in ChromeOS lock screen until a
successful attempt.
xiaoyinh@google.com
The numbers of times that users click on the shelf buttons, trays and lock
screen note on the ChromeOS lock screen.
agawronska@google.com
The numbers of times that users click on the shelf buttons and trays on the
ChromeOS login screen.
afakhry@chromium.org
The type of CRTC color transorm matrix support for the currently connected
displays. Emitted when cursor compositing status is refreshed, but only when
Night Light is on. The cursor compositing status is refreshed whenever there
is a change in Night Light status or color temperature.
afakhry@chromium.org
The selected Night Light schedule type. Emitted when the user changes the
Night Light schedule type from the Display System Settings.
afakhry@chromium.org
The ranges in which the selected values of the Night Light color temperature
reside. Emitted when the user drags the Night Light color temperature slider
to change its value from the Display System Settings.
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.
warx@chromium.org
The number of windows restored in multi-display scenario, such as due to
disconnecting and reconnecting display, enabling and disabling mirror mode,
entering and leaving dock mode. Zero is not recorded.
warx@chromium.org
Record the delay when power button and volume down key are both pressed,
which indicates user might want to use accelerator to take screenshot. This
will help us determine the best chord delay among metrics.
sky@chromium.org
The delta between when chrome main starts to when the Chrome OS system UI
(ash) is visible to the user (specifically the first time pixels are lit up
on the primary display showing the Chrome OS system UI).
wutao@chromium.org
Relative smoothness of animations when rotating screen. 100% represents
ideally smooth 60 frames per second. 50% represents only 30 frames per
second is achieved during the animations. 0% should not happen. This metric
is recorded exactly once when the user rotates the screen.
bruthig@google.com
tdanderson@google.com
Tracks the number of menu items that are enabled in a shelf item's secondary
menu. This metric is only recorded when a menu item is selected.
bruthig@google.com
tdanderson@google.com
Tracks the index of the selected menu item in a shelf item's secondary menu.
This metric is only recorded when a menu item is selected.
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.
kaznacheev@chromium.org
The percentage of the screen area circled by the Assistant pen. Recorded
when the "closed shape" gesture is recognized.
kaznacheev@chromium.org
The duration of an Assistant pen gesture. Recorded at the end of every
gesture.
kaznacheev@chromium.org
The interval between subsequent Assistant pen gestures within a session.
Session is defined as the period while the Assistant tool is enabled.
Recorded at the end of each gesture except for the first one in the session.
The interval is computed excluding the gesture duration.
kaznacheev@chromium.org
The number of Assistant pen gestures per session. Session is defined as the
period while the Assistant tool is enabled. Recorded at the end of the
session.
kaznacheev@chromium.org
The number of recognized Assistant pen gestures per session. Session is
defined as the period while the Assistant tool is enabled. Recorded at the
end of the session.
kaznacheev@chromium.org
The type of the Assistant pen gesture. Recorded at the end of each gesture.
kaznacheev@chromium.org
The length of a recognized "horizontal stroke" Assistant pen
gesture. Recorded at the and of the gesture.
kaznacheev@chromium.org
The amount of time spent in Palette Assistant mode. Recorded when the
Assistant mode is exited.
xiaoyinh@chromium.org
The amount of time spend in Palette Laser pointer mode. Recorded when the
Laser pointer mode is exited.
xiaoyinh@chromium.org
The amount of time spend in Palette Magnify mode. Recorded when the Magnify
mode is exited.
xiaoyinh@chromium.org
Tracks the number of times a palette mode is explicitly cancelled or
switched out of.
xiaoyinh@chromium.org
Recorded every time that the palette option has been selected from the
palette that has been opened manually (not via a stylus eject event).
xiaoyinh@chromium.org
Recorded every time that the palette option has been selected from the
palette that has been opened automatically (by a stylus eject event).
kaznacheev@chromium.org
Recorded every time that the palette option has been selected by means other
that the palette menu (e.g. stylus barrel button or a keyboard accelerator).
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-predictable
task. Task switches from other sources are ignored and do not affect this
metric. In other words, if a user performs the following steps (1) launch
task 'A' from the Shelf (2) Alt+Tab to task 'Z' (3) launch task 'B' from the
Shelf, then this will result in a sample recorded for the time delta between
launching tasks 'A' and 'B'.
bruthig@google.com
tdanderson@google.com
Tracks the amount of time between a window being minimized by the shelf and
subsequently activated. In other words this metric is only recorded if a
shelf button pressed action causes a window to be minimized and the very
next shelf button pressed action causes the same window to be activated.
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.
xdai@chromium.org
The amount of time that the user spent in split view mode. The time is
measured from the moment a window is snapped to one side of the screen to
when split view mode is ended.
Deprecated 02/2017 due to lack of usage.
kuscher@google.com
rbyers@chromium.org
The duration of mostly stationary long-duration touches.
bruthig@chromium.org
tbuckley@chromium.org
The visible rows displayed in the system menu's default view. Recorded each
time the menu is opened.
tdanderson@chromium.org
tbuckley@chromium.org
The height of the system menu divided by the height of the Ash desktop work
area; a value over 100% indicates that a portion of the system menu is not
visible to the user. Recorded each time the menu is opened.
tdanderson@chromium.org
tbuckley@chromium.org
The number of user-visible rows in the system menu's default view. Recorded
each time the menu is opened.
Deprecated 10/2016 for Issue 616581.
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).
bruthig@google.com
tdanderson@google.com
The number of seconds between contiguous task switch user actions triggered
by any of the other task switch actions that are tracked. (e.g.,
Ash.Shelf.TimeBetweenNavigateToTaskSwitches,
Ash.Tab.TimeBetweenSwitchToExistingTabUserActions,
Ash.WindowCycleController.TimeBetweenTaskSwitches,
Ash.AppList.TimeBetweenTaskSwitches,
Ash.WindowSelector.TimeBetweenActiveWindowChanges, etc). Note the
Ash.AppList.TimeBetweenTaskSwitches and
Ash.Tab.TimeBetweenSwitchToExistingTabUserActions histograms were deprecated
and removed in 10/2016.
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.
Deprecated 02/2017 due to lack of usage.
kuscher@google.com
rbyers@chromium.org
The interval between touch-move events.
kuscher@google.com
rbyers@chromium.org
The distance between touch-move events.
Deprecated 07/2018 due to lack of usage.
tdanderson@chromium.org
kuscher@google.com
The position of the touch-events along the X axis.
Deprecated 07/2018 due to lack of usage.
tdanderson@chromium.org
kuscher@google.com
The position of the touch-events along the Y axis.
Deprecated 07/2018 due to lack of usage.
tdanderson@chromium.org
kuscher@google.com
The radius of a touch event.
tdanderson@chromium.org
kuscher@google.com
The interval between the end of a touch-sequence and the start of the next
touch-sequence.
Deprecated 02/2017 due to lack of usage.
kuscher@google.com
rbyers@chromium.org
The number of rapid touch-starts that happened within a short interval.
Logged once for each such burst group.
derat@chromium.org
Chrome OS only. The computed angle between the lid and the keyboard panel.
These values are imprecise and may be tens of degrees off from reality.
Reported once per hour that the system is awake, and not reported if the
system doesn't have two accelerometers.
girard@chromium.org
The length of time that TouchView is active, for each activation.
girard@chromium.org
The proportion of time spent in TouchView during a session.
girard@chromium.org
The total time that TouchView is active during a session.
girard@chromium.org
The length of time between TouchView activations.
girard@chromium.org
The total time that TouchView is not active during a session.
Deprecated as of 2/2018. Currently there is only one type of Wallpaper App.
xdai@chromium.org
The Wallpaper App that the user is using right now on Chrome OS. It's the
app that is used when the user right clicks on desktop and selects "Set
wallpaper" or when the user selects "Set wallpaper" from
chrome://settings page. This is recorded at user login.
bruthig@chromium.org
tbuckley@chromium.org
The time taken to extract colors from wallpapers. Recorded each time the
wallpaper image changes. It may contain multiple colors extracted.
bruthig@chromium.org
tbuckley@chromium.org
The time taken to extract colors from 'expensive' wallpapers. Recorded each
time the wallpaper image changes and the color extraction is expected to be
expensive, e.g. image size > 100 pixels. This includes time spent
switching threads. It may contain multiple colors extracted.
Deprecated as of 6/2017.
bruthig@chromium.org
tbuckley@chromium.org
Tracks the success rate for wallpaper color extraction. Recorded each time
the wallpaper image changes.
warx@chromium.org
tbuckley@chromium.org
Tracks the success rate for wallpaper color extraction. Recorded each time
the wallpaper image changes for each extracted wallpaper prominent color.
xdai@chromium.org
The custom wallpaper layout type. Recorded when the user sets a new custom
wallpaper or changes the existing custom wallpaper's layout.
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.
xdai@chromium.org
Recorded when a new wallpaper is set, either by the built-in Wallpaper
Picker App, or by a third party App. Note the wallpaper change triggered by
Sync file system event doesn't count.
Deprecated as of 04/2017 in favor of Ash.Wallpaper.ColorExtraction.Durations
and Ash.Wallpaper.ColorExtraction.UserDelay.
bruthig@chromium.org
tbuckley@chromium.org
The time taken to extract colors from wallpapers. Recorded each time the
wallpaper image changes. NOTE, this measure also included the time spent
jumping between threads, thus it was deprecated in favor of
Ash.Wallpaper.ColorExtraction.Durations.
bruthig@chromium.org
tbuckley@chromium.org
The time taken to resize wallpapers. Recorded once each time the wallpaper
changes (e.g. initial wallpaper loading at boot, switching user avatar at
login screen, switching between logged in users, user selects new wallpaper,
etc).
kuscher@google.com
The wallpaper type. Recorded at user login.
wutao@chromium.org
Relative smoothness of cross fade animation when setting window bounds. 100%
represents ideally smooth 60 frames per second. 50% represents when only 30
frames per second is achieved during the animations. 0% should not happen.
This metric is recorded exactly once when SetBoundsDirectCrossFade is
called, such as when window is maximized.
wutao@chromium.org
Relative smoothness of hiding window animation. 100% represents ideally
smooth 60 frames per second. 50% represents when only 30 frames per second
is achieved during the animations. 0% should not happen. This metric is
recorded exactly once when AnimateHideWindowCommon is called, such as when
window is closed.
varkha@chromium.org
tbuckley@google.com
The amount of time the Alt key is held after pressing Alt+Tab to begin
cycling through windows.
varkha@chromium.org
tbuckley@google.com
The number of windows in the Alt+Tab selector. Only recorded once when
cycling starts, not every time when Tab is pressed without releasing Alt.
varkha@chromium.org
tbuckley@google.com
When a window is selected after pressing Alt+Tab, records that window's
position in the global MRU ordering. 1 represents the most-recently used
window, 2 represents the next most-recently used window, and so on. Recorded
when Alt+Tab cycling stops, i.e., when Alt key is released.
varkha@chromium.org
tbuckley@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).
jdufault@chromium.org
How long it took for the screen lock process to complete. This does not
include timeouts.
jdufault@chromium.org
How long it took for the screen lock process to complete, for timeouts only.
varkha@chromium.org
tdanderson@chromium.org
Relative smoothness of animations when closing a window in overview mode.
100% represents ideally smooth 60 frames per second.
varkha@chromium.org
tdanderson@chromium.org
Relative smoothness of animations when entering overview mode. 100%
represents ideally smooth 60 frames per second.
varkha@chromium.org
tdanderson@chromium.org
Relative smoothness of animations when exiting overview mode. 100%
represents ideally smooth 60 frames per second.
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.
varkha@chromium.org
tdanderson@chromium.org
tbuckley@chromium.org
When a window is selected in overview mode, records that window's position
in the global MRU ordering. 1 represents the most-recently used window, 2
represents the next most-recently used window, and so on.
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.
mgersh@chromium.org
Count of DnsAttempts before DnsTransaction completes with failure.
mgersh@chromium.org
Count of DnsAttempts before DnsTransaction completes successfully.
mgersh@chromium.org
Whether DnsConfigService::OnConfigChange actually corresponded to a change
in DnsConfig.
mgersh@chromium.org
Duration of time between calls to DnsConfigService::InvalidateConfig.
mgersh@chromium.org
Duration of time spent parsing DnsConfig.
mgersh@chromium.org
Counts of results of parsing DnsConfig in DnsConfigServicePosix.
Deprecated as of 9/2017.
mgersh@chromium.org
Whether DnsConfig was parsed successfully.
mgersh@chromium.org
Counts of results of parsing DnsConfig in DnsConfigServiceWin.
Deprecated as of 9/2017.
mgersh@chromium.org
Whether the first valid DnsConfig included a rogue nameserver.
mgersh@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.
mgersh@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.
mgersh@chromium.org
Duration of time spent by ProcTask in failing fallback resolutions.
mgersh@chromium.org
Duration of time spent by ProcTask in successful fallback resolutions.
mgersh@chromium.org
Whether there was a valid DNS configuration at the start of a job which
eventually completed successfully.
mgersh@chromium.org
Whether DnsHosts were parsed successfully.
mgersh@chromium.org
Whether DnsConfigService::OnHostsChange actually corresponded to a change in
DnsHosts.
mgersh@chromium.org
Duration of time between calls to DnsConfigService::InvalidateHosts.
mgersh@chromium.org
Duration of time spent parsing DnsHosts.
mgersh@chromium.org
Counts of results of parsing DnsHosts in DnsConfigServiceWin.
mgersh@chromium.org
The size of the HOSTS file observed before each attempt to parse it.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient).
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority HIGHEST when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority IDLE when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority LOW when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority LOWEST when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (using DnsClient). Includes only Jobs which had
priority MEDIUM when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient).
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority HIGHEST
when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority IDLE when
started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority LOW when
started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority LOWEST when
started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (using DnsClient). Includes only Jobs which had priority MEDIUM when
started.
Deprecated as of 4/2016.
mgersh@chromium.org
Type of nameservers in the DNS config, recorded each time the config is read
by the DNSConfigService.
mgersh@chromium.org
Counts of results of parsing addresses out of DNS responses in successful
DnsTransactions.
Deprecated as of 9/2017.
mgersh@chromium.org
The source of the async DNS preference's default. Logged at startup, when
the IO thread is created.
Deprecated as of 9/2017.
mgersh@chromium.org
The source of the async DNS preference's value. Logged at startup, when the
IO thread is created.
Deprecated as of 9/2017. Replaced by Net.DNS.DnsTaskError.
mgersh@chromium.org
Counts of specific error codes returned by DnsTask if a subsequent ProcTask
succeeded.
Deprecated as of 9/2017. Replaced by Net.DNS.DnsTaskFail.
mgersh@chromium.org
Duration of time taken by DnsTask in resolutions that failed. Excludes time
spent in the subsequent fallback.
Deprecated as of 9/2017.
mgersh@chromium.org
Counts of the overall results of using asynchronous DNS in HostResolverImpl.
This only includes jobs started with valid DNS configuration and excludes
synchronous resolutions (as IP literals, from cache, and from HOSTS).
Deprecated as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess.
mgersh@chromium.org
Duration of time taken by DnsTask in resolutions that succeeded.
Deprecated as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess.
mgersh@chromium.org
Same as AsyncDNS.ResolveSuccess, but limited to pure IPv4 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess.
mgersh@chromium.org
Same as AsyncDNS.ResolveSuccess, but limited to pure IPv6 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.DnsTaskSuccess.
mgersh@chromium.org
Same as AsyncDNS.ResolveSuccess, but limited to IPv4/IPv6 lookups.
mgersh@chromium.org
Count of servers in DnsConfig. Recorded on every new DnsSession, which is
created on DNS change.
mgersh@chromium.org
Index in DnsConfig of the failing server, recorded at the time of failure.
mgersh@chromium.org
Count of server failures after network change before first success in the
DnsSession. Recorded at the time of first success.
mgersh@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.
mgersh@chromium.org
Count of server failures before success. This is NOT the first success in
the DnsSession. Recorded at the time of success.
mgersh@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.
Deprecated as of 9/2017.
mgersh@chromium.org
The current server is "good" and does not have to be skipped.
mgersh@chromium.org
Duration of time taken in failing calls to AddressSorter in dual-stack
resolutions using DnsTask.
mgersh@chromium.org
Duration of time taken in successful calls to AddressSorter in dual-stack
resolutions using DnsTask.
mgersh@chromium.org
The number of names from the search name list consumed during a successful
transaction (QTYPE A only).
mgersh@chromium.org
The number of names left on the search name list at the end of a successful
transaction (QTYPE A only).
mgersh@chromium.org
The number of names on the search name list at the start of a transaction
(QTYPE A only).
mgersh@chromium.org
Duration of time taken by DnsTCPAttempt in failed attempts. Excludes
timeouts.
mgersh@chromium.org
Duration of time taken by DnsTCPAttempt in successful attempts.
mgersh@chromium.org
Difference between RTT and timeout calculated using Histogram algorithm.
mgersh@chromium.org
Difference between timeout calculated using Histogram algorithm and RTT.
mgersh@chromium.org
Difference between RTT and timeout calculated using Jacobson algorithm.
mgersh@chromium.org
Difference between timeout calculated using Jacobson algorithm and RTT.
mgersh@chromium.org
Duration of time that would be spent waiting for lost request using
Histogram algorithm.
mgersh@chromium.org
Duration of time that would be spent waiting for lost request using Jacobson
algorithm.
Deprecated as of 9/2017. Replaced by Net.DNS.TotalTime.
mgersh@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Excludes speculative requests.
Deprecated as of 9/2017. Replaced by Net.DNS.TotalTime_speculative.
mgersh@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Speculative requests only.
mgersh@chromium.org
Duration of time taken in failing DnsTransactions. This includes server
failures, timeouts and NXDOMAIN results.
mgersh@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.
mgersh@chromium.org
Same as AsyncDNS.TransactionSuccess but limited to A query type.
mgersh@chromium.org
Same as AsyncDNS.TransactionSuccess but limited to AAAA query type.
mgersh@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.
mgersh@chromium.org
Duration of time taken by DnsUDPAttempt in failed attempts. Excludes
timeouts.
mgersh@chromium.org
Duration of time taken by DnsUDPAttempt in successful attempts. Includes
responses arriving after timeout, if multiple attempts are allowed.
mgersh@chromium.org
Duration of time since the last empty config result to the time a non-change
OnConfigChange is received.
mgersh@chromium.org
Duration of time since the last empty config result to the time a non-change
OnHostsChange is received.
mgersh@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.
ljusten@chromium.org
Result from an attempt to authenticate a user to an Active Directory domain.
ljusten@chromium.org
Result from automatic background machine password renewal.
ljusten@chromium.org
Result from automatic background ticket-granting-ticket renewal.
ljusten@chromium.org
Result of an attempt to get an Active Directory user's Kerberos
ticket-granting-ticket and configuration data.
ljusten@chromium.org
Result of an attempt to get the status of an Active Directory user's
Kerberos ticket, password and account.
ljusten@chromium.org
Result from an attempt to join a machine to an Active Directory domain.
ljusten@chromium.org
Result from an attempt to fetch device policy from an Active Directory
domain and store it on disk.
ljusten@chromium.org
Result from an attempt to fetch user policy from an Active Directory domain
and store it on disk.
ljusten@chromium.org
Number of times 'kinit' failed until the next try succeeded or the method
gave up because a maximum number of tries was exceeded. 'kinit' is run for
Active Directory enrolled devices during user authentication and device
policy fetch.
ljusten@chromium.org
Number of times 'smbclient' failed until it the next try succeeded or the
method gave up because a maximum number of tries was exceeded. 'smbclient'
is run for Active Directory enrolled devices during policy fetch.
ljusten@chromium.org
Number of group policy objects attached to a specific user or machine on an
Active Directory domain. This value is recorded when user or device policy
is fetched from an Active Directory server.
ljusten@chromium.org
Time in milliseconds to authenticate a user to an Active Directory domain.
The value is recorded no matter if the operation was successful or not.
ljusten@chromium.org
Time in milliseconds to get the Kerberos ticket-granting-ticket and
configuration data of an Active Directory user. The value is recorded no
matter if the operation was successful or not.
ljusten@chromium.org
Time in milliseconds to get status information of an Active Directory user.
The value is recorded no matter if the operation was successful or not.
ljusten@chromium.org
Time in milliseconds to join a machine to an Active Directory domain. Domain
join is part of the Active Directory enrollment process. The value is
recorded no matter if the operation was successful or not.
ljusten@chromium.org
Time in milliseconds to fetch device policy from an Active Directory domain
and store it on disk. The value is recorded no matter if the operation was
successful or not.
ljusten@chromium.org
Time in milliseconds to fetch user policy from an Active Directory domain
and store it on disk. The value is recorded no matter if the operation was
successful or not.
ljusten@chromium.org
Time in milliseconds to call 'kinit' (request Kerberos ticket-granting-
ticket). TGTs are requested regularly for accessing services on Active
Directory domains. The value is recorded no matter if the operation was
successful or not.
ljusten@chromium.org
Time in milliseconds to call 'klist' (print Kerberos ticket-granting-ticket
information). The command reveals a TGT's lifetime, which is used to
determine TGT status in GetUserStatus() called periodically by Chrome. The
value is recorded no matter if the operation was successful or not.
ljusten@chromium.org
Time in milliseconds to call 'kpasswd' (change Active Directory password).
The command is used to change the machine account password. By default, it
is run every 30 days by the AuthPolicy daemon. The value is recorded no
matter if the operation was successful or not.
ljusten@chromium.org
Time in milliseconds to call 'net ads gpo list' (list Active Directory group
policy objects). The value is recorded no matter if the operation was
successful or not.
ljusten@chromium.org
Time in milliseconds to call 'net ads info' (query Active Directory
information). The value is recorded no matter if the operation was
successful or not.
ljusten@chromium.org
Time in milliseconds to call 'net ads join' (join machine to an Active
Directory domain). The value is recorded no matter if the operation was
successful or not.
ljusten@chromium.org
Time in milliseconds to call 'net ads search' (query information about an
Active Directory account). The value is recorded no matter if the operation
was successful or not.
ljusten@chromium.org
Time in milliseconds to call 'net ads workgroup' (query Active Directory
workgroup). The value is recorded no matter if the operation was successful
or not.
ljusten@chromium.org
Time in milliseconds to call 'smbclient' (download policy from an Active
Directory domain). The value is recorded no matter if the operation was
successful or not.
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.
Deprecated as of 2/2016.
jinsukkim@chromium.org
Whether the text encoding auto detection logic was attempted for a web page.
The logic is triggered when the parser fails to find the encoding method
from other signals such as http header, meta tag, BOM, etc.
If the logic successfully detects a new encoding method which is different
from the default one, the result is reported through
AutodetectEncoding.Detected with the encoding method (see below). Otherwise
- i.e. detection logic somehow fails to work for the page or the detected
one is same as the default - no result is reported.
Deprecated as of 2/2016.
jinsukkim@chromium.org
The number of web pages whose encoding method is found by the auto detection
logic. Grouped by the encoding methods defined in EncodingMethod.
Deprecated as of 8/2015.
erikchen@chromium.org
Whether an attempt to access the Mac AddressBook was skipped because doing
so would incorrectly cause the appearance of the permissions dialog. This
happens when Chrome auto-update changes the binary on disk before the first
AddressBook access attempt.
Deprecated as of 8/2015.
isherman@chromium.org
Whether the Mac AddressBook was available on an attempt to read data from
it.
Deprecated as of 8/2015.
isherman@chromium.org
Whether the Mac AddressBook was available on the *first* attempt to read
data from it. This is only recorded once per Chrome profile.
wuandy@chromium.org
The number of unverified autofill addresses deleted because they have not
been used for a long time, and are not used as billing addresses of valid
credit cards. Note the deletion only happens once per major version upgrade.
rogerm@chromium.org
The number of address suggestions not shown in the Autofill popup because
they have not been used recently enough. Note that suppression only applies
when the user has not typed any text into the field. If any text is in the
field, all matching addresses are displayed, regardless of how recently they
have been used.
isherman@chromium.org
The number of address suggestions shown in the Autofill popup.
Deprecated as of 6/2015, replaced by Autofill.ProfileActionOnFormSubmitted.
sebsg@chromium.org
Whether a new Autofill profile was created automatically. In the
"false" case, an existing profile was used (and possibly updated).
Deprecated as of 2/2016, replaced by Autofill.CardUploadDecisionMetric.
jdonnelly@chromium.org
Whether upload was offered upon detecting a form submission with credit card
data and a reason if it wasn't.
Deprecated as of 5/2017, replaced by Autofill.CardUploadDecisionMetric.
jdonnelly@chromium.org
Whether upload was offered upon detecting a form submission with credit card
data and a detailed reason if it wasn't.
csashi@google.com
jsaul@google.com
sebsg@chromium.org
Whether upload was offered upon detecting a form submission with credit card
data, a detailed reason if upload was offered even with some missing fields
and detailed reasons if it wasn't.
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.
mathp@chromium.org
The relative frequency with which users accept, deny, or ignore the Autofill
credit card assisted filling infobar prompt.
isherman@chromium.org
The relative frequency with which users accept, deny, or ignore the Autofill
credit card info bar prompt.
wuandy@chromium.org
The number of credit card deleted during a major version upgrade because
they have not been used recently enough and are expired.
wuandy@chromium.org
The number of credit card suggestions not shown in the Autofill popup
because they have not been used recently enough and are expired. Note that
suppression only applies when the user has not typed any text into the
field. If any text is in the field, all matching cards are displayed,
regardless of how recently they have been used and their expiration status.
jsaul@google.com
When a credit card is not allowed to be offered upload save due to its
network, logs what the card network was.
sebsg@chromium.org
Logs the number of days that have passed since the credit card was last
used.
sebsg@chromium.org
Logged at the time of autofill address use, this histogram captures the
number of days that have passed since the address was last used. I.e., the
distribution of time between uses of an "active" autofill address.
rogerm@chromium.org
Logs the number of days that have passed since each credit card belonging to
a given Chrome Profile was last used. This is logged for each Autofill
credit card once per Chrome User Profile load.
rogerm@chromium.org
This histogram captures the number of days that have passed since each
stored address profile belonging to a given Chrome Profile was last used.
This is logged for each Autofill address profile once per Chrome User
Profile load.
csashi@google.com
jsaul@google.com
sebsg@chromium.org
Logs the number of days between most recent use without modification and the
penultimate use of the profile when submitting a credit card form.
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.
kolos@chromium.org
rogerm@chromium.org
Number of fields in a form that Autofill encounters.
rogerm@chromium.org
Predicted and actual form field type. This is a computed sparse histogram
where the value is ((predicted << 16)| actual). Predicted and actual
are taken from the autofill::ServerFieldType enumeration.
rogerm@chromium.org
Aggregate Autofill field-type prediction outcomes. See
https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the
values.
rogerm@chromium.org
Autofill field-type prediction outcomes, broken down by field type. See
https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the
values.
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 a 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 a user initially filled with local data and after that
filled with server, we will only emit "Submitted with server suggestion
filled (once)".
szhangcs@google.com
Autofill form events for credit card forms. These are recorded when the user
interacts with a form requesting a credit card, a dropdown of suggestions is
shown and at least one of the suggestions has a bank name. Form events are
logged at most once per page load.
These metrics are used to measure the impact of the bank name experiment.
They are used to calculate the CTR of the autofill UI with bank names
available. Not all credit cards will have bank names even if we launch the
experiment. With these metrics we can run the experiment on 2 groups. For
one group, we will show bank names if available. For the other, we won't
shown.
estark@chromium.org
Autofill form events for credit card forms on nonsecure pages. These are
recorded when the user interacts with a form requesting a credit card.
Important caveat about submission metrics: - Submission using autofill data
is determined by simply evaluating if there was a fill operation in this
page. So, if the user filled with local data, completed erased or modified
the data after and then submitted, we would only emit one "Submitted
with server suggestion filled (once)"; - The submission segmentation
works by checking what kind of data was last filled for this type of form in
the page load. So, if a user initially filled with local data and after that
filled with server, we will only emit "Submitted with server suggestion
filled (once)".
sebsg@chromium.org
The autofill state related to a submitted form.
csashi@google.com
jsaul@google.com
sebsg@chromium.org
Whether user modified an address profile shortly before submitting a credit
card form.
parastoog@chromium.org
Logs when a hidden or presentational field is autofilled. The hidden or
presentational fields are only autofilled for 'select' fields to support
synthetic fields.
mathp@chromium.org
Tracks whether Autofill was able to create the ICU collator successfully.
rogerm@chromium.org
Tracks whether or not autofill suppressed sending votes or calculating
quality metrics because the profile data was marked as invalid. Logged
during field-type validation if/when a field marked as invalid is found to
match the submitted data.
rogerm@chromium.org
Tracks whether or not autofill suppressed offering an autofill suggestion
because the profile data was marked as invalid. Logged during autofill
suggestion generation when a suggestion is about to generated based on a
field marked as invalid.
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.
mahmadi@chromium.org
[iOS] Measures the frequency of button presses on the iOS Autofill keyboard
accessory view when VoiceOver is off.
mahmadi@chromium.org
[iOS] Measures the frequency of button presses on the iOS Autofill keyboard
accessory view when VoiceOver is on.
siyua@chromium.org
Record events related to bubble showing. Logged when bubble is requested or
is actually shown to users.
siyua@chromium.org
Record how bubble is closed by different user interactions.
Deprecated as of 8/2015.
erikchen@chromium.org
When Chrome tries to access the user's Address Book, OSX presents a blocking
dialog which disrupts the user experience. A new Chrome feature has been
introduced wherein Chrome only shows this blocking dialog if the user
explicitly asked Chrome to access the user's Address Book. If a form's field
looks like it might support Autofill suggestions from the user's Address
Book and there are no other suggestions, Chrome shows an Autofill entry that
prompts the user to give Chrome access to the user's Address Book. This
histogram tracks the frequency that this Autofill entry is presented, and
the frequency that this Autofill entry is selected.
Deprecated as of 8/2015.
erikchen@chromium.org
This metric is emitted each time the user accepts an Autofill suggestion. It
records whether the result is from the Address Book.
Deprecated as of 8/2015.
erikchen@chromium.org
The amount of time spent accessing the OSX Address Book the first time after
Chrome was launched. If this time is larger than ~100ms, this it is likely
that the user was shown a blocking, modal dialog.
Deprecated as of 8/2015.
erikchen@chromium.org
After a Chrome is given access to the Mac Address Book, whether the Address
Book contained a Me card.
Deprecated as of 8/2015.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has an address that contained a street number and either a city or zip
code.
Deprecated as of 8/2015.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has an email.
Deprecated as of 8/2015.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has a name.
Deprecated as of 8/2015.
erikchen@chromium.org
When Chrome is given access to the Me Card of the Address Book, whether the
card has a phone number.
Deprecated as of 8/2015.
erikchen@chromium.org
The number of times that the access Address Book prompt has been shown when
the user selects the prompt.
mathp@chromium.org
The number of autofilled fields that were subsequently edited prior to the
form being submitted.
mathp@chromium.org
The number of Autofill profiles that have been considered for deduplication.
mathp@chromium.org
The number of Autofill profiles that have been removed during deduplication.
rogerm@chromium.org
Records whether the number of fillable form elements matches the number of
fields in the form's description. Instances where this is recorded as False,
denote cases where autofill failed to preview/fill an autofill suggestion.
This can happen when a fields is filtered out of a formless form.
Deprecated 10/2015.
dvadym@chromium.org
gcasto@chromium.org
Tracks the increased load on the Autofill server if the restriction on
querying for password forms with fewer than 3 fields were omitted.
Deprecated as of 1/2016, autofill payload compression was removed.
mathp@chromium.org
Compression ratio of the query and upload payload that are sent to the
Autofill server. The payload is compressed using gzip.
sebsg@chromium.org
The profile action that took place when a form was submitted.
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.
Deprecated as of 6/2017, replaced by
Autofill.FieldPredictionQuality.Aggregate.Heuristic.
isherman@chromium.org
The quality of Autofill's heuristic field type detection.
Deprecated as of 6/2017, replaced by
Autofill.FieldPredictionQuality.ByFieldType.Heuristic.
isherman@chromium.org
The quality of Autofill's heuristic field type detection, broken down by the
specific field type. Fields with multiple possible types (based on the
stored Autofill data) are logged as having ambiguous type.
Deprecated as of 6/2017, replaced by
Autofill.FieldPredictionQuality.Aggregate.Overall.
isherman@chromium.org
The overall quality of the Autofill field type predictions.
Deprecated as of 6/2017, replaced by
Autofill.FieldPredictionQuality.ByFieldType.Overall.
isherman@chromium.org
The overall quality of the Autofill field type predictions, broken down by
the specific field type. Fields with multiple possible types (based on the
stored Autofill data) are logged as having ambiguous type.
Deprecated as of 6/2017, replaced by
Autofill.FieldPredictionQuality.Aggregate.Server.
isherman@chromium.org
The quality of the Autofill server's field type detection.
Deprecated as of 6/2017, replaced by
Autofill.FieldPredictionQuality.ByFieldType.Server.
isherman@chromium.org
The quality of the Autofill server's field type detection, broken down by
the specific field type. Fields with multiple possible types (based on the
stored Autofill data) are logged as having ambiguous type.
mathp@chromium.org
For credit card forms that are queried for Autofill, a ratio of how many are
within secure contexts (which includes mixed passive content).
rogerm@chromium.org
The number of bytes that were sent in a query that subsequently failed. This
is to help determine the appropriate threshold at which autofill queries
should switch from GET to POST, and if there are certain sizes of queries
which are prone to failure.
rogerm@chromium.org
The HTTP response code returned on a query.
rogerm@chromium.org
The HTTP method used to query the autofill server.
rogerm@chromium.org
Was the autofill query response retrieved from the HTTP cache.
wuandy@chromium.org
The quality of fields rationalization, putting rationalization result into
good/ok/bad categories.
sebsg@chromium.org
The number of full server cards that were reset.
sebsg@chromium.org
The number of full server cards that would have been reset.
sebsg@chromium.org
Records whether a sync service in a not active state is passed to Autofill
OnSyncServiceInitialized.
sebsg@chromium.org
Records whether a null sync service is passed to Autofill
OnSyncServiceInitialized.
sebsg@chromium.org
Records the sync service state when OnStateChanged is called.
jsaul@google.com
If the cardholder name fix flow is shown when credit card upload is offered,
records if the cardholder name textfield was prefilled with the name from
the user's Google Account.
jsaul@google.com
If the cardholder name fix flow is shown during credit card upload and the
user accepts upload, logs whether the final cardholder name was changed from
its prefilled value or not.
sebsg@chromium.org
Records if a card was saved from a form that had split name fields.
sebsg@chromium.org
Records if a card was offered to be saved from a form that had split name
fields.
jdonnelly@chromium.org
The relative frequency with which users accept or deny the Autofill save
credit card prompt.
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.
mathp@chromium.org
Tracks whether Autofill server had at least some prediction data for a given
form at query response time.
rogerm@chromium.org
The number of credit cards a user has stored, measured at Chrome profile
launch time.
rogerm@chromium.org
The number of disused credit cards a user has stored, measured at Chrome
profile launch time. This is only reported for users who have at least one
stored credit card.
mathp@chromium.org
The number of local credit cards a user has stored, measured at Chrome
profile launch time.
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.
rogerm@chromium.org
The number of stored Autofill address profiles which have not been used in a
sufficiently long time for autofill to consider them disused. Measured once
per Chrome user profile launch.
mathp@chromium.org
The number of server credit cards a user has stored, measured at Chrome
profile launch time.
dlkumar@google.com
Metric to measure credit card state when form is submitted, specifically if
it had a valid card number and/or expiration date.
jsaul@google.com
Metric to measure if a submitted card's expiration date matches the same
server card's expiration date (unmasked or not). Cards are considered to be
the same if they have the same card number (if unmasked) or if they have the
same network and last four digits (if masked).
mathp@chromium.org
The index of the accepted Autofill suggestion in the popup.
mathp@chromium.org
The index of the accepted Autocomplete suggestion in the popup.
kenjitoyama@chromium.org
Number of milliseconds passed between the start and end of
FormStructure::DetermineHeuristicTypes().
kenjitoyama@chromium.org
Number of milliseconds passed between the start and end of parsing a single
form.
rogerm@chromium.org
The number of bytes that were sent in a request for which the download
manager seems to have lost the request type. This should never be logged.
rogerm@chromium.org
The HTTP response code returned on a request for which the download manager
seems to have lost the request type. This should never be logged.
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 their 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 their
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.
rogerm@chromium.org
Records incidents where an implicit (formless) form has elements filtered
out of it. This happens to unowned fields (directly embedded in the page
with no enclosing <form> tag) without autocomplete attributes if
formless forms are restricted to "checkout" pages. Logged when
parsing forms/fields.
rogerm@chromium.org
The number of bytes that were sent in an upload that subsequently failed.
This is to help determine if there are certain upload sizes which are prone
to failure.
rogerm@chromium.org
The HTTP response code returned on an upload.
jsaul@google.com
Measures if a card for which upload was accepted is already stored as a
local card on the device or if it has not yet been seen.
jsaul@google.com
Measures if a card for which upload was offered is already stored as a local
on the device or if it has not yet been seen.
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.
sebsg@chromium.org
Tracks how the different wallet addresses are converted to local autofill
profiles.
sebsg@chromium.org
treib@chromium.org
The number of Wallet addresses that were added to Chrome via Sync. Recorded
when receiving an AUTOFILL_WALLET_DATA update from the Sync server.
Can probably be removed around Q1 2019, after project Dice has rolled out.
sebsg@chromium.org
treib@chromium.org
The total number of Wallet addresses that were added to or removed from
Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from
the Sync server.
Can probably be removed around Q1 2019, after project Dice has rolled out.
sebsg@chromium.org
treib@chromium.org
The number of Wallet addresses that were removed from Chrome via Sync.
Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server.
Can probably be removed around Q1 2019, after project Dice has rolled out.
sebsg@chromium.org
treib@chromium.org
The number of Wallet credit cards that were added to Chrome via Sync.
Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server.
Can probably be removed around Q1 2019, after project Dice has rolled out.
sebsg@chromium.org
treib@chromium.org
The total number of Wallet credit cards that were added to or removed from
Chrome via Sync. Recorded when receiving an AUTOFILL_WALLET_DATA update from
the Sync server.
Can probably be removed around Q1 2019, after project Dice has rolled out.
sebsg@chromium.org
treib@chromium.org
The number of Wallet credit cards that were removed from Chrome via Sync.
Recorded when receiving an AUTOFILL_WALLET_DATA update from the Sync server.
Can probably be removed around Q1 2019, after project Dice has rolled out.
michaelbai@chromium.org
Records the state of an autofill session.
michaelbai@chromium.org
Whether the autofill is created by activity context.
michaelbai@chromium.org
Whether the autofill service is enabled in Android platform.
michaelbai@chromium.org
Records the source of form submission.
michaelbai@chromium.org
The time taken to display suggestion.
michaelbai@chromium.org
Whether the user changed autofilled field.
peter@chromium.org
Records the Service Worker status code that caused a Background Fetch API
event to fail dispatching whilst trying to dispatch an event on the active
Service Worker.
peter@chromium.org
Records the Service Worker status code that caused a Background Fetch API
event to fail dispatching whilst trying to find the Service Worker.
peter@chromium.org
Records the Service Worker status code that caused a Background Fetch API
event to fail dispatching whilst trying to start the active Service Worker.
peter@chromium.org
Records the result of dispatching one of the Background Fetch API events to
the Service Worker associated with the event.
peter@chromium.org
rayankans@chromium.org
Records the error after the Background Fetch Data Manager creates a
registration.
peter@chromium.org
rayankans@chromium.org
Records the error after the Background Fetch Data Manager deletes a
registration.
peter@chromium.org
rayankans@chromium.org
Records the error after the Background Fetch Data Manager marks a
registration for deletion. This is called when the Scheduler Controller is
finished.
atwilson@chromium.org
mvanouwerkerk@chromium.org
The number of background applications (extensions) for a profile that were
loaded after the profile was registered with the BackgroundModeManager.
mvanouwerkerk@chromium.org
Logged if BackgroundModeManager is running and listening for pref changes,
and the pref does indeed change. The new value is logged.
mvanouwerkerk@chromium.org
Logged when an item in the system tray icon menu is clicked.
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.
dgn@chromium.org
The duration of a session before the browser got restarted in the background
by the BackgroundOptimizer to purge the memory.
iclelland@chromium.org
Records the number of sync events which were fired in a batch. A batch is
defined as the set of sync events dispatched at the same time by the
BackgroundSyncManager. One-shots usually run individually (a batch of one),
unless the device was offline and multiple are waiting for the device to go
back online.
As of 10/2015 this has been replaced by
BackgroundSync.Event.OneShotResultPattern.
iclelland@chromium.org
Records whether a one-shot sync event succeeded or failed.
jkarlin@chromium.org
Records whether a periodic sync event succeeded or failed and whether the
sync event finished in the foreground or background.
A sync event finished in the foreground if the associated Service Worker
Registration has a client at the time that the event finished.
jkarlin@chromium.org
Records whether a one-shot sync started firing in the foreground or
background. Called shortly before the event is fired.
As of 10/2015 this has been replaced by
BackgroundSync.Event.PeriodicResultPattern.
iclelland@chromium.org
Records whether a periodic sync event succeeded or failed.
Stopped recording as of 1/2016.
jkarlin@chromium.org
Records whether a one-shot sync event succeeded or failed and whether the
sync event finished in the foreground or background.
A sync event finished in the foreground if the associated Service Worker
Registration has a client at the time that the event finished.
Stopped recording as of 1/2016.
jkarlin@chromium.org
Records whether a periodic sync event started firing in the foreground or
background. Called shortly before the event is fired.
iclelland@chromium.org
Time taken to execute a batch of sync events. A batch is defined as the set
of sync events dispatched at the same time by the BackgroundSyncManager.
Periodic syncs often run in a batch. One-shots usually run individually (a
batch of one), unless the device was offline and multiple are waiting for
the device to go back online.
iclelland@chromium.org
Records the result of attempting to cancel a future browser launch using the
GCM Network Manager on Android.
iclelland@chromium.org
Records whether Google Play Services is available to the Background Sync
system on Android, for scheduling future sync events when the browser is not
running. This will be logged at most once per run.
iclelland@chromium.org
Records the result of attempting to schedule a future browser launch using
the GCM Network Manager on Android.
iclelland@chromium.org
Records whether the browser has sufficient permissions to create a
BackgroundSyncNetworkObserver object on Android, at the point when it tries
to create it. This should never be false, but is being tracked in order to
help resolve crbug.com/545473.
iclelland@chromium.org
Records the result of attempting to register a one-shot sync.
iclelland@chromium.org
Records the result of attempting to register a one-shot sync in a situation
where the sync could fire immediately.
iclelland@chromium.org
Records whether a one-shot sync registration exactly duplicates an existing
registered sync.
Stopped recording as of 1/2016.
iclelland@chromium.org
Records the result of attempting to register a periodic sync.
Stopped recording as of 1/2016.
iclelland@chromium.org
Records whether a periodic sync registration exactly duplicates an existing
registered sync.
Stopped recording as of 2/2016.
iclelland@chromium.org
Records the result of attempting to unregister a one-shot sync.
Stopped recording as of 1/2016.
iclelland@chromium.org
Records the result of attempting to unregister a periodic sync.
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.
Removed at 2015 July.
csharp@chromium.org
Counts the number of times a renderer process is started with the browser
blacklist patch. This should never be hit.
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.
shaktisahu@chromium.org
Records the size of the uncompressed commit messages received by Blimp
compositor.
shaktisahu@chromium.org
Records whether connection attempt to the Blimp engine was successful.
shaktisahu@chromium.org
Records whether Blimp is supported.
shaktisahu@chromium.org
Records whenever a Blimp tab toggles visibility.
peria@chromium.org
Time spent to create a v8::Context instance during a page loading in the
main-frame window.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
peria@chromium.org
Time spent to create a v8::Context instance during a page loading in a
non-main-frame window, e.g. iframe.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
peria@chromium.org
Time spent initializing LocalWindowProxy during a page loading in main
windows.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
peria@chromium.org
Time spent initializing RemoteWindowProxy during a page loading in main
frame of OOPIF.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated as of 03/2017. This metric was split into two metrics depending
if it figures time for local window proxies or remote ones.
peria@chromium.org
Time spent initializing WindowProxy during a page loading in main windows.
peria@chromium.org
Time spent initializing LocalWindowProxy during a page loading in non-main
windows, e.g. iframe.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
peria@chromium.org
Time spent initializing RemoteWindowProxy during a page loading in OOPIF.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated as of 03/2017. This metric was split into two metrics depending
if it figures time for local window proxies or remote ones.
peria@chromium.org
Time spent initializing WindowProxy during a page loading in non-main
windows, e.g. iframe.
Deprecated as of 10/2016. This metric was split into two metrics depending
if it figures time for main windows.
peria@chromium.org
Time spent initializing WindowProxy during a page loading.
peter@chromium.org
Whenever the Budget API framework receives a query for the current budget,
this records the total budget available to the origin, which is an internal
Chrome value for the amount of background processing an origin can do
without visibly alerting the user. Scale for the budget is 0 to 100. Care
should be taken when drawing conclusions from this metric, as budget is
based on both engagement and usage, so could vary significantly based on
user behaviour and origin.
peter@chromium.org
Whenever the Budget API framework receives a request to reserve budget for a
future background operation, this records whether the reserve request
succeeded or not.
junov@chromium.org
Time spent on 2D canvas drawImage API call.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
junov@chromium.org
Time spent on 2D canvas getImageData API call.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
junov@chromium.org
xidachen@chromium.org
Wall clock durations of OffscreenCanvas.commit() calls.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
junov@chromium.org
Time spent on 2D canvas putImageData API call.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
junov@chromium.org
xlai@chromium.org
This metric measures the total time spent on completing encoding all the
rows of an image (jpeg or png), as part of a canvas.toBlob API call.
Encoding occurs during one or more idle periods on the main thread and the
waiting time of the next idle period is included in the measurement. If the
code has swtiched to force encoding path, we will not measure the delay in
this metric.
This metric is useful in helping us adjust the IdleTaskCompleteTimeoutDelay
in canvas.toBlob. When the encoding idle task is delayed for longer than
IdleTaskCompleteTimeoutDelay, the browser will switch to a non-idle task to
force encoding to happen on the main thread.
In addition, metric values from OffscreenCanvas.convertToBlob API call are
also gathered into this histogram, because the logic flow is exactly the
same as canvas.toBlob. It's worth to note that the values can come from idle
tasks on either main or worker thread.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced with Blink.Canvas.ToBlob.CompleteEncodingDelay in 2017/12.
junov@chromium.org
xlai@chromium.org
This metric measures the total time spent on encoding all the rows of an
image (jpeg or png), excluding the waiting time of next idle periods. This
is part of a canvas.toBlob API call. Encoding occurs during one or more idle
periods on the main thread.
junov@chromium.org
xlai@chromium.org
Records the status of the idle task when finishing a toBlob call.
In addition, metric values from OffscreenCanvas.convertToBlob API call are
also gathered into this histogram, because the logic flow is exactly the
same as canvas.toBlob. It's worth to note that the values can come from idle
tasks on either main or worker thread.
junov@chromium.org
xlai@chromium.org
This metric measures the time spent from initiating image encoding (jpeg or
png) on idle task to the actual execution time of initiation, as part of a
canvas.toBlob API call.
This metric is useful in helping us adjust the IdleTaskStartTimeoutDelay in
canvas.toBlob. When the initialization idle task is delayed for longer than
IdleTaskStartTimeoutDelay, the browser will switch to a non-idle task to
force initialization and encoding to occur on the main thread.
In addition, metric values from OffscreenCanvas.convertToBlob API call are
also gathered into this histogram, because the logic flow is exactly the
same as canvas.toBlob. It's worth to note that the values can come from idle
tasks on either main or worker thread.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
junov@chromium.org
xlai@chromium.org
Time spent on 2D canvas toBlob API call.
In addition, metric values from OffscreenCanvas.convertToBlob API call are
also gathered into this histogram, because the logic flow is exactly the
same as canvas.toBlob. It's worth to note that the values can come from idle
tasks on either main or worker thread.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
junov@chromium.org
Time spent on 2D canvas toDataURL API call.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated on 2018-05-04.
khushalsagar@chromium.org
The number of images which could have been checkered (async decoded) for a
performance gain, split by the DOM element type on which they were used.
This is recorded each time an image for an element created by the page is
loaded, either from the network or the local cache. The browser heuristics
define an image to be checkerable if it is expected to have a long decode
duration. Since these images may be on the rendering critical path, decoding
them asychronously from painting other content can provide better
performance be reducing overall content checkerboarding.
hubbe@chromium.org
Gamut properties of destination color space.
hubbe@chromium.org
Gamut properties of image color space.
msarett@chromium.org
Gamma properties of destination color space.
Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28.
ccameron@chromium.org
Whether or not the output color space ICC profile was able to produce raw
transfer function tables.
ccameron@chromium.org
The result of analyzing the destiation color space's ICC profile.
Linear fit found to be always inaccurate on 2017-02-28.
ccameron@chromium.org
The L-infinity error (in 8-bit values) of the numerical approximation of
table-based ICC profile transfer functions, when falling back to a linear
approximation.
Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28.
ccameron@chromium.org
Whether or not to-XYZD50 matrix was extracted from the output color space
ICC profile.
Nonlinear fit code moved to skcms on 2018-04-25.
ccameron@chromium.org
Whether or not the nonlinear least squares fit of the table-based ICC
profile transfer function for a single channel converged.
Nonlinear fit code moved to skcms on 2018-04-25.
ccameron@chromium.org
The L-infinity error (in 8-bit values) of the numerical approximation of
table-based ICC profile transfer functions for a single channel, when the
nonlinear approximation converged.
ccameron@chromium.org
The L-infinity error (in 8-bit values) of the numerical approximation of
table-based ICC profile transfer functions for all channels combined, when
the nonlinear approximation converged.
Merged into Blink.ColorSpace.Destination.ICCResult on 2017-02-28.
ccameron@chromium.org
Whether or not the output color space ICC profile has a numerical transfer
function.
TMax found to almost always be 1 on 2017-02-28.
ccameron@chromium.org
One minus the maximum value of table-based ICC profile transfer functions as
an 8-bit fixed-point value. This histogram is temporary, to see if we can
bake in the assumption that it will almost always be 255.
TMin found to almost always be 0 on 2017-02-28.
ccameron@chromium.org
The minimum value of table-based ICC profile transfer functions as an 8-bit
fixed-point value. This histogram is temporary, to see if we can bake in the
assumption that it will almost always be 0.
ccameron@chromium.org
Gamma properties of image color space.
paint-dev@chromium.org
Number of composited layers based on various reasons. Recorded when a page
finishes its layer updates.
paint-dev@chromium.org
Time spent updating compositing in the Blink document lifecycle.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
kinuko@chromium.org
dcheng@chromium.org
Microseconds per sync IPC call to set cookies.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
kinuko@chromium.org
dcheng@chromium.org
Microseconds per sync IPC call to fetch cookies.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated as of 11/29/2016.
ryansturm@chromium.org
bengr@google.com
The original canvas dimensions were sufficient to determine image size. This
is logged once per image header decode, which happens typically twice per
image on the page.
Deprecated as of 11/29/2016.
ryansturm@chromium.org
bengr@google.com
How many bytes of the file were read before an image width and height were
determined. This is logged once per image header decode, which happens
typically twice per image on the page.
rob.buis@samsung.org
Image orientation inferred during decode.
Deprecated as of 11/29/2016.
ryansturm@chromium.org
bengr@google.com
How much the canvas width needed to be expanded as a result of the first
frame's width and x-offset being larger than the initial canvas width. This
is logged once per image header decode, which happens typically twice per
image on the page.
Deprecated as of 11/29/2016.
ryansturm@chromium.org
bengr@google.com
How much the canvas height needed to be expanded as a result of the first
frame's height and y-offset being larger than the initial canvas height.
This is logged once per image header decode, which happens typically twice
per image on the page.
urvang@chromium.org
Image codec inferred during decode.
Deprecated 01/2018.
bokan@chromium.org
Time it takes to execute all the `resize` event listeners on a page when a
resize event is fired. Tracked only for the main frame.
csharrison@chromium.org
The total microseconds spent in ResourceFetcher::requestResource.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
drott@chromium.org
Counts success or failure of attempting to access font tables using the zero
copy instantiation method in the HarfBuzz integration layer. This value is
only recorded on non-Mac platforms. Reported each time a HarfBuzz face
object is created.
eae@chromium.org
Total number of entries in all Blink ShapeCache instances. The value is
reported each time the FontCache::purge() method is called.
drott@chromium.org
Tracks adoption ratio of variable fonts compared to conventional (in the
sense of non-variable) web fonts. Recorded at the time of instantiating a
Skia SkTypeface from the successfully decoded web font blob.
jyasskin@chromium.org
domenic@google.com
How many times two user gesture tokens were merged by UserGestureIndicator,
and whether each token had an active gesture. One of the new token's
gestures, if any, is moved to the old token.
paint-dev@chromium.org
Time spent computing IntersectionObserver observations in the Blink document
lifecycle.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
joedow@chromium.org
garykac@chromium.org
Records each call to the navigator.keyboard{Lock|Unlock} methods.
sclittle@chromium.org
Records the initial lazy loading action taken for a cross-origin iframe.
sclittle@chromium.org
Records the effective connection type whenever a lazily-loaded iframe that
wasn't initially hidden or near the viewport starts loading. The count for
an effective connection type in this histogram can be subtracted from the
'Deferred' bucket from the
Blink.LazyLoad.CrossOriginFrames.InitialDeferralAction.* histogram for the
corresponding effective connection type to determine the number of iframes
that LazyLoad is avoiding to load altogether.
sclittle@chromium.org
Records the effective connection type whenever a lazily-loaded iframe that
wasn't initially hidden or near the viewport becomes visible. The count for
an effective connection type in this histogram can be subtracted from the
corresponding count in
Blink.LazyLoad.CrossOriginFrames.LoadStartedAfterBeingDeferred to determine
how many iframes were loaded unnecessarily by LazyLoad.
Deprecated 08/2017 as it is integrated into media controller.
qinmin@chromium.org
Records how the download button on the MediaDocument is used.
Deprecated 11/2016 in Issue 666370 with the deprecation of Autoplay
experiment.
oysteine@chromium.org
Records user observation and interaction with Media HTML elements that
feature autoplay, either script-controlled or through the attribute.
hiroshige@chromium.org
RevalidationPolicy used for non-preloading requests for each resource type.
https://crbug.com/579496
hiroshige@chromium.org
RevalidationPolicy used for requests that hit Resource only referenced from
MemoryCache for each resource type. https://crbug.com/579496 Requests
counted by this are also counted by Blink.MemoryCache.RevalidationPolicy or
Blink.MemoryCache.RevalidationPolicy.Preload.
hiroshige@chromium.org
RevalidationPolicy used for preloading requests for each resource type.
https://crbug.com/579496
paint-dev@chromium.org
Time spent updating paint in the Blink document lifecycle.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
SlimmingPaintInvalidation is enabled by default, so this histogram is no
longer being logged.
paint-dev@chromium.org
Time spent updating paint invalidation in the Blink document lifecycle. Not
available when SlimmingPaintInvalidation or SlimmingPaintV2 is enabled.
paint-dev@chromium.org
Time spent updating paint properties and paint invalidation in the Blink
document lifecycle. Available when SlimmingPaintInvalidation or
SlimmingPaintV2 is enabled.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
dtapuska@chromium.org
kenjibaheux@google.com
Count of resources attempted Stale Revalidation.
dtapuska@chromium.org
kenjibaheux@google.com
Duration of completed stale revalidation attempts.
toyoshim@chromium.org
Count received data size in bytes for each resource.
toyoshim@chromium.org
altimin@chromium.org
Total decoded size of resources associated with frames of a particular type.
Recorded when a fetch has been completed.
Each bucket of the histogram cointains the total size of all requests
associated with frames with a particular frame status in kilobytes.
ksakamoto@chromium.org
The largest number of outstanding resource requests issued by a frame until
the network 2-quiet (no more than 2 active network requests for 1 seconds).
toyoshim@chromium.org
Count resource request circumstance, e.g. from the main frame vs sub-frames,
or in throttled state vs in not-throttled state, on each resource load
completion.
toyoshim@chromium.org
Count how many times the scheduler has changed throttling status from the
frame creation until network activity quiets.
toyoshim@chromium.org
Total received data size in bytes to load resources from the frame creation
until network activity quiets.
toyoshim@chromium.org
Total number of resource requests completed from the frame creation until
network activity quiets.
toyoshim@chromium.org
Total traffic data in bytes transferred over networks to load resources from
the frame creation until network activity quiets.
toyoshim@chromium.org
Count traffic data size in bytes transferred over networks to load each
resource.
toyoshim@chromium.org
altimin@chromium.org
Total encoded size of resources associated with frames of a particular type.
Recorded when a fetch has been completed.
Each bucket of the histogram cointains the total size of all requests
associated with frames with a particular frame status in kilobytes.
Deprecated 01/2016 and replaced by Blink.RestoredCachedStyleSheet2
kouhei@chromium.org
On each link stylesheet tag resolve, record whether a Blink MemoryCached
StyleSheetContents was reused.
Deprecated 04/2017.
kouhei@chromium.org
On each link stylesheet tag resolve, record which cache Blink hit.
haraken@chromium.org
Duration of time taken to scan pending activities of all V8 wrappers in a
worker thread.
kouhei@chromium.org
hiroshige@chromium.org
Number of script elements for each scheduling type, recorded for each
successful #prepare-a-script.
Used to justify distribution of serialized data in the wild, but unlikely to
be useful to track long-term.
platform-architecture-dev@chromium.org
Number of DOM wrappers serialized as part of an object passed to
postMessage, IndexedDB, or another API that serializes script values.
Used to justify distribution of serialized data in the wild, but unlikely to
be useful to track long-term.
platform-architecture-dev@chromium.org
Number of JavaScript objects (other than DOM wrappers) serialized as part of
an object passed to postMessage, IndexedDB, or another API that serializes
script values.
Used to justify distribution of serialized data in the wild, but unlikely to
be useful to track long-term.
platform-architecture-dev@chromium.org
Number of primitive values (numbers, strings, etc.) serialized as part of an
object passed to postMessage, IndexedDB, or another API that serializes
script values.
pdr@chromium.org
The time it took to update scrolling coordinator data (scroll gesture
regions, touch event rects, and main thread scrolling reasons). These values
are calculated during the main-thread blink lifecycle.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
hiroshige@chromium.org
Number of failed SharedBuffer::lock() calls for each resource type.
https://crbug.com/603791
hiroshige@chromium.org
Number of successful SharedBuffer::lock() calls for each resource type.
https://crbug.com/603791
hiroshige@chromium.org
Number of SharedBuffer::unlock() calls for each resource type.
https://crbug.com/603791
layout-dev@chromium.org
Time spent updating style and layout in the Blink document lifecycle.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
loonybear@chromium.org
Records usage of animated 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 via PageLoadMetricsObserver.
This histogram counts CSS properties only when they are animated by a CSS
Animation. Refer to Blink.UseCounter.CSSProperties for more details.
As of M69, Blink.UseCounter.AnimatedCSSProperties is moved from the blink
side to the browser side.
Renamed to Blink.UseCounter.AnimatedCSSProperties in 03/2018, M69. The old
blink UseCounter is flawed in OOPIF, so moved to the browser side instead.
loonybear@chromium.org
Records usage of animated CSS properties used across all frames in a page,
either statically or dynamically, from the time the page is initialised to
when it is closed or navigated away from. Each property is counted at most
once per page view except kTotalPagesMeasuredCSSSampleId which represents a
page load (enum value of 1) and is counted exactly once per page view.
loonybear@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
via PageLoadMetricsObserver.
The first time a CSS property is parsed on a page, the histogram is updated
to increment the counter. Each histogram bucket corresponds to a CSS
property (eg. width, border-radius). The exception is the 'Total pages
measured' bucket - this counts the number of pages that CSS properties were
counted on. When a page navigation occurs the page count bucket is
incremented and tracking of the set of which properties have been seen is
reset.
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.
Note that CSS properties used inside of SVG images are tracked separately in
the Blink.UseCounter.SVGImage.CSSProperties histogram.
As of M57 this histogram supercedes WebCore.FeatureObserver.CSSProperties.
As of M69, Blink.UseCounter.AnimatedCSSProperties is moved from the blink
side to the browser side.
Renamed to Blink.UseCounter.CSSProperties in 03/2018, M69. The old blink
UseCounter is flawed in OOPIF, so moved to the browser side instead.
loonybear@chromium.org
Records usage of CSS properties used across all frames in a page, either
statically or dynamically, from the time the page is initialised to when it
is closed or navigated away from. Each property is counted at most once per
page per view except kTotalPagesMeasuredCSSSampleId which represents a page
load (enum value of 1) and is counted exactly once per page view.
loonybear@chromium.org
Count of how many page loads use various features for pages with a
chrome-extension:// URL only. The PageVisits bucket is incremented for each
page load, and the other buckets incremented at most once per PageVisit via
the WebCore::UserCounter class.
Warning: This histogram represents pre-renderer metrics and so is flawed
under OOPIF.
loonybear@chromium.org
Count of how many page loads use various features across all frames in a
page. The PageVisits bucket is incremented for each page load, and the other
buckets incremented at most once per PageVisit via blink::UseCounter and
UseCounterPageLoadMetricsObserver.
Note that features used inside of SVG images are tracked separately in the
Blink.UseCounter.SVGImage.Features histogram. Features used inside of
extension pages are tracked separately in the
Blink.UseCounter.Extensions.Features histogram.
As of M67, Blink.UseCounter.Features is moved from the blink side to the
browser side, the semantics have changed a little. The blink side histogram
is renamed to "Blink.UseCounter.Features_Legacy".
loonybear@chromium.org
Count of how many page loads use various features. The PageVisits bucket is
incremented for each page load, and the other buckets incremented at most
once per PageVisit via the blink::UseCounter class.
As of M67 this has been replaced by browser-side UseCounter. This is the old
blink-side counters which are flawed in OOPIF scenarios because they are
pre-renderer-processes. This histogram will be removed.
Renamed to Blink.UseCounter.Features in 03/2018, M67. The old blink
UseCounter is flawed in OOPIF, so moved to the browser side (this) instead.
loonybear@chromium.org
Count of how many page loads use various features across all frames in a
page. The PageVisits bucket is incremented for each page load, and the other
buckets incremented at most once per PageVisit via the WebCore::UseCounter
class. This counter lives in browser process.
Removed in 06/2018, M69 since the histogram is not really useful. See
https://crbug.com/804645.
loonybear@chromium.org
Like Blink.UseCounter.AnimatedCSSProperties but specifically for the case of
CSS properties used inside of an SVG image.
Warning: This histogram represents pre-renderer metrics and so is flawed
under OOPIF.
This histogram counts usage of animated CSS properties only. Refer to
Blink.UseCounter.SVGImage.CSSProperties for details.
Removed in 06/2018, M69 since the histogram is not really useful. See
https://crbug.com/804645.
loonybear@chromium.org
Like Blink.UseCounter.CSSProperties but specifically for the case of CSS
properties used inside of an SVG image.
Warning: This histogram represents pre-renderer metrics and so is flawed
under OOPIF.
The 'Total pages measured' bucket is incremented each time a new SVG image
is created. Note that the same SVG image can be used across multiple tabs
in a single renderer but this counts as a single usage. See
http://crbug.com/236262.
loonybear@chromium.org
Like Blink.UseCounter.Features except specifically for the case of SVG
Images.
Warning: This histogram represents pre-renderer metrics and so is flawed
under OOPIF.
Count of how many SVG images use various features. The PageVisits bucket is
incremented each time a new SVG image is created. Note that the same SVG
image can be used across multiple tabs in a single renderer but this counts
as a single usage. See http://crbug.com/236262.
sclittle@chromium.org
Records the effective connection type whenever a lazyload-eligible (i.e.
cross-origin and non-hidden) iframe that was initially below the fold
becomes visible before it finishes loading.
sclittle@chromium.org
Milliseconds spent waiting for an above the fold iframe to load. Only fires
for iframes that would be eligible for lazy loading, i.e. cross-origin and
non-hidden.
sclittle@chromium.org
Milliseconds spent waiting for a below the fold iframe to load. Only fires
for iframes that would be eligible for lazy loading, i.e. cross-origin and
non-hidden.
Deprecated 06/2017 in Issues 455099 and 681769 (M61).
hiroshige@chromium.org
The count of XMLHttpRequest.setRequestHeader() calls where header values are
invalid/valid but affected by normalization/valid in RFC 7230.
https://crbug.com/455099.
oilpan-reviews@chromium.org
Duration of finishing marking the transitive closure of objects during the
final Blink garbage collection pause. Recorded at the end of each garbage
collection.
Deprecated 06/2018. The sample taken here was a mix of marking, sweeping and
compaction. Replaced by BlinkGC.AtomicPhaseMarking for the marking phase and
BlinkGC.TimeForTotalCollectGarbage for the overal time.
haraken@chromium.org
Duration of time taken to run Heap::collectGarbage(). Recorded at the end of
each garbage collection.
haraken@chromium.org
The percentage of objects that have been collected by a Blink GC. 0 is
passed if there were no objects when a Blink GC started.
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.
keishi@chromium.org
Amount of memory reduced with the GC triggered on page navigation while the
device is in a low memory state. Only implemented on low end Android devices
at the moment. Memory usage is approximated by summing the memory usage of
the following allocators: BlinkGC, PartitionAlloc, and V8 main thread
isolate heap.
haraken@chromium.org
The size of allocated objects just after Blink GC is triggered.
haraken@chromium.org
The size of allocated objects just before Blink GC is triggered.
haraken@chromium.org
The total size of objects freed by BlinkGC's heap compaction. This is
recorded once following each compaction.
Removed at 2014 Jan.
haraken@chromium.org
Duration of time taken to run ThreadState::performPendingSweep().
haraken@chromium.org
hpayer@chromium.org
Duration of memory coalesce operation in the Blink GC. Reported once per
coalesce operation.
haraken@chromium.org
Duration of time taken to run global weak processing of Blink GC.
haraken@chromium.org
Duration of wall time taken to run BlinkGC's heap compaction.
haraken@chromium.org
Duration of time taken to run ThreadState::invokePreFinalizers().
As of 02/2017, the code to stop Blink threads was removed.
haraken@chromium.org
Duration of time taken to stop all Blink threads before starting a GC.
haraken@chromium.org
Accumulated time taken to sweep all objects.
As of 02/2017, the code for thread-local weak processing was removed.
haraken@chromium.org
Duration of time taken to run thread-local weak processing.
haraken@chromium.org
hpayer@chromium.org
Duration of total Blink garbage collection time when the garbage collector
is invoked for finishing a garbage collection. This includes finishing up
any already running garbage collection operation as well as potentially
performing a follow-up collection synchronously. Recorded each time after
invoking the Blink garbage collector.
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.
ulan@chromium.org
Records how a bloated renderer was handled in the browser process.
ulan@chromium.org
Records how a bloated renderer was handled in the resource coordinator
service.
ulan@chromium.org
Records how a bloated V8 heap was handled in the renderer process. It is
emitted the first time V8 heap reaches the heap limit and invokes the
NearHeapLimitCallback. Subsequent invocations of the callback are ignored.
Thus it is emitted once per renderer process run.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Disconnected GATT connection status codes. Used to better understand errors
seen in Android.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Failed GATT connection error codes. Used to better understand errors seen in
Android.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Successful GATT connection result codes. Used to better understand Android
results.
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.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of calls to BluetoothAdapter::StartDiscoverySession.
Used to prioritize efforts to fix failures of this function.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of calls to BluetoothDiscoverySession::Stop. Used to
prioritize efforts to fix failures of this function.
As of 08/2015 this has been replaced by
Bluetooth.Web.Characteristic.ReadValue and
Bluetooth.Web.Characteristic.WriteValue.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how many times each GATT Error has occured. The results will be used
to determine how common this errors are and if we need to provide better
error messages to the users.
scheib@chromium.org
device-dev@chromium.org
Records how many times each macOS GATT error has occured. The results will
be used to determine how commun this errors are and if we need to provide
better error messages to the users.
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.
Deprecated 08/2015 and replaced by Bluetooth.Web.RequestDevice.Outcome.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of a navigator.bluetooth.requestDevice() call. Used to
understand what errors developers are getting so we can target efforts
toward the most common ones. Multiple outcomes may result for a given
RequestDevice, such as rescan multiple times and then select a device.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
'status' values returned by Android GATT event.
Deprecated as of 11/2016, replaced by
Bluetooth.Web.Blocklist.ParsedNonEmptyString.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of BluetoothBlacklist::Add parsing a non-empty string.
These strings will be updated dynamically by a server, and this histogram
provides feedback that parsing is functioning correctly on clients.
False values are BAD, a blacklist is failing to be applied correctly.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of BluetoothBlocklist::Add parsing a non-empty string.
These strings will be updated dynamically by a server, and this histogram
provides feedback that parsing is functioning correctly on clients.
False values are BAD, a blocklist is failing to be applied correctly.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to characteristic.readValue(). Used to know
what types of errors users are seeing. The results will be used to determine
how common these errors are and if we need to provide better error messages
to the users.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to characteristic.startNofications(). Used to
know what types of errors users are seeing. The results will be used to
determine how common these errors are and if we need to provide better error
messages to the users.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to characteristic.writeValue(). Used to know
what types of errors users are seeing. The results will be used to determine
how common these errors are and if we need to provide better error messages
to the users.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Counts how many times users interact with a regular chooser vs. an invalid
chooser. (A chooser is invalid when it's event handler becomes null.)
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of a device.gatt.connect() call. Used to understand what
errors developers are getting so we can target efforts toward the most
common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how long it takes for a connection attempt to fail. Use to let
developers know how to better wait for and handle connection errors.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how long it takes for a device to successfully connect. Use to let
developers know how long it should take to connect to a BLE device.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to descriptor.readValue(). Used to know what
types of errors users are seeing. The results will be used to determine how
common these errors are and if we need to provide better error messages to
the users.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to descriptor.writeValue(). Used to know what
types of errors users are seeing. The results will be used to determine how
common these errors are and if we need to provide better error messages to
the users.
Deprecated as of 3/2017. Replaced by using blink IDL annotation MeasureAs
which appear in Blink.UseCounter.Features.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Counts the number of times each call to a WebBluetooth function is done.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the UUIDs used when getting a characteristic. The recorded value is
a 31-bit hash of the UUID. Used to know what types of characteristics to
target when building libraries that use the Web Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to getCharacteristic(). Used to understand
what errors developers are getting so we can target efforts toward the most
common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the UUIDs used when getting characteristics. The recorded value is a
31-bit hash of the UUID. Used to know what types of characteristics to
target when building libraries that use the Web Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to getCharacteristics(). Used to understand
what errors developers are getting so we can target efforts toward the most
common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the UUIDs used when getting a descriptor. The recorded value is a
31-bit hash of the UUID. Used to know what types of descriptors to target
when building libraries that use the Web Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to getDescriptor(). Used to understand what
errors developers are getting so we can target efforts toward the most
common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the UUIDs used when getting descriptors. The recorded value is a
31-bit hash of the UUID. Used to know what types of descriptors to target
when building libraries that use the Web Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the outcome of a call to getDescriptors(). Used to understand what
errors developers are getting so we can target efforts toward the most
common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of a GATTServer.getPrimaryService() call. Used to
understand what errors developers are getting so we can target efforts
toward the most common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records what GATT Services are used when connected. The record value is a
31-bit hash of the Service UUID. This will help us know if we should build
an API for specific services rather than a general Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of a GATTServer.getPrimaryServices() call. Used to
understand what errors developers are getting so we can target efforts
toward the most common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records what GATT Services are used when connected. The record value is a
31-bit hash of the Service UUID. This will help us know if we should build
an API for specific services rather than a general Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how many filters are used when scanning. These results will help us
better understand the uses of the API and make changes according to
developers' behavior.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records a 31-bit hash of the GATT Service UUIDs used when scanning. This
will help us know if we should build an API for specific services rather
than a general Bluetooth API.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how many services are used in a filter. These results will help us
better understand the uses of the API and make changes according to
developers' behavior.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
juncai@chromium.org
In the case of not accepting all devices, records the number of devices that
are in the chooser when a device is paired.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how many optional services are used when scanning. These results
will help us better understand the uses of the API and make changes
according to developers' behavior.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records what optional services are used. The recorded value is a 31-bit hash
of the Service UUID. These results will help us better understand the uses
of the API and make changes according to developers' behavior.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the value of 'acceptAllDevices' in RequestDeviceOptions. These
results will help us better understand the uses of the API and make changes
according to developers' behavior.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records the result of a navigator.bluetooth.requestDevice() call. Used to
understand what errors developers are getting so we can target efforts
toward the most common ones.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
juncai@chromium.org
Raw RSSI values provided to chooser, before processing them for display in
the Web Bluetooth chooser.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
juncai@chromium.org
Displayed RSSI levels, after processing and as displayed to users in the Web
Bluetooth chooser.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
juncai@chromium.org
Records the duration scanning for devices is run, terminated by events such
as the chooser being closed with a selected device, cancelled, or the scan
duration timing out.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records how many services are used when scanning. This results will help us
better understand the uses of the API and make changes according to
developers' behavior.
jyasskin@chromium.org
ortuno@chromium.org
scheib@chromium.org
Records what services are used from either required or optional sets. The
recorded value is a 31-bit hash of the Service UUID. These results will help
us better understand the uses of the API and make changes according to
developers' behavior.
mcchou@chromium.org
This is specific to Chrome OS. Records a duration of a Bluetooth adapter
being lost. This helps us better understand the Bluetooth controller drop
issue in the field.
Replaced 08/2018 by BlueZ.ChipLost2 for more suspend/resume filtering even
when the Bluetooth adapter is turned off.
sonnysasaka@chromium.org
This is specific to Chrome OS. Records a duration of a Bluetooth adapter
being lost caused by hardware disconnection. This helps us better understand
the Bluetooth controller drop issue in the field.
sonnysasaka@chromium.org
This is specific to Chrome OS. Records a duration of a Bluetooth adapter
being lost caused by hardware disconnection. This helps us better understand
the Bluetooth controller drop issue in the field.
mcchou@chromium.org
This is specific to Chrome OS. Records the number of existing advertisements
when registering for a new advertisement. This helps us better understand
the common amount of advertisments used and the registration failures due to
the limited number of advertisement slots.
mcchou@chromium.org
This is specific to Chrome OS. Records the reason of Bluetooth disconnection
between the local device and the remote Bluetooth device. This helps us
better understand the initiator of disconnection request.
mcchou@chromium.org
This is specific to Chrome OS. Records the outcomes of advertisement
registration. This helps us better understand the persentage of successful
advertisements against failures and the causes of failures.
mcchou@chromium.org
This is specific to Chrome OS. Records the outcomes of connection requests
to remote devices. This helps us better understand the persentage of
successful connections against failures and the causes of failures.
mcchou@chromium.org
This is specific to Chrome OS. Records the outcomes of pairing with remote
devices. This helps us better understand the persentage of successful
pairing against failures and the causes of failures.
mcchou@chromium.org
This is specific to Chrome OS. Records the duration when the local device is
performing Bluetooth advertisment and discoverable as a Bluetooth Low Energy
device by other devices. This helps us better understand the amount of
successful advertisment sessions and the duration.
mcchou@chromium.org
This is specific to Chrome OS. Records the duration when the local device is
discoverable by other devices as a Bluetooth classic device. This helps us
better understand the amount of requests to expose the local device as a
Bluetooth classic device and the duration.
mcchou@chromium.org
This is specific to Chrome OS. Records the duration for the local device to
perform device discovery. This helps us better understand the amount of
device discovery request and the duration for users to find the target
device.
mcchou@chromium.org
This is specific to Chrome OS. Records the duration taken to finish a
successful pairing between the local device and a remote Bluetooth device.
This helps us better understand the latency of completing Bluetooth pairing.
mcchou@chromium.org
This is specific to Chrome OS. Records the duration taken to finish a
successful connection between the local device and a remote Bluetooth
device. This helps us better understand the latency of connecting to a
Bluetooth device.
mcchou@chromium.org
This is specific to Chrome OS. Records the types of device discovery
performed by the local device. This helps us better understand the most
common type of device discovery performed.
mcchou@chromium.org
This is specific to Chrome OS. Records the types of discovered devices in
terms of Bluetooth classic, Bluetooth low energy and Dual-mode supports.
This helps us better understand the persentage of Bluetooth devices in terms
of type.
calamity@chromium.org
Logs when a user action triggers a command in the bookmark manager. Commands
can be triggered by keyboard shortcuts, menu items or other buttons in the
UI.
calamity@chromium.org
Logs when a keyboard shortcut triggers a command in the bookmark manager.
calamity@chromium.org
Logs where the menu was opened from when a user action opens the command
menu in the bookmark manager.
calamity@chromium.org
Logs the number of bookmarks that were dragged simultaneously by a user.
calamity@chromium.org
Records the time taken to load the bookmarks Web UI and render. This is
roughly equivalent to 'time to first meaningful paint' for the bookmark
manager.
calamity@chromium.org
Logs the number of bookmark items inside a folder every time a folder is
opened inside the bookmark manager.
ianwen@chromium.org
How users add a new bookmark.
mamir@chromium.org
The size of the file used to persist bookmarks. It's recorded every time the
file is loaded in memory.
yfriedman@chromium.org
Logs the depth of the bookmark in the bookmark tree hierarchy every time a
bookmark is launched. Depth indicates how many levels below a permanent
bookmark folder the bookmark was found in (e.g. a bookmark immediately in
the bookmark bar has depth 1).
ianwen@chromium.org
Logs a UI location from which a bookmark is launched.
pkotwicz@chromium.org
Logs how frequently BookmarkModel::OnFaviconsChanged() is called with a
non-empty |icon_url| to determine whether BookmarkNodes should be cached
based on their favicon URLs (e.g. http://www.google.com/favicon.ico) in
addition to their page URLs (e.g. http://www.google.com). OnFaviconChanged()
is expected to be called less than 10 times per user per day with a
non-empty |icon_url|.
Deprecated as of 1/2016.
kkimlabs@chromium.org
Logs how user is opening a bookmark on Android. For example, user can long
press and select "Open in a new tab" or "Open in incognito
tab".
wychen@chromium.org
Logs whether the bookmark entry is a user bookmark or a partner bookmark
when it is opened.
Replaced 08/2016 by BootTime.Total2 with larger range and more buckets.
bccheng@chromium.org
semenzato@chromium.org
Time from power on to login panel ready (Chrome OS).
bccheng@chromium.org
semenzato@chromium.org
Time from power on to login panel ready (Chrome OS).
eustas@chromium.org
Compressed/Decompressed size ratio.
eustas@chromium.org
More detailed failure reason.
eustas@chromium.org
Indicates whether the gzip-like header was detected.
eustas@chromium.org
The final state of BrotliFilter.
eustas@chromium.org
Maximal amount of memory allocated by decoder.
sadrul@chromium.org
sky@chromium.org
The time it takes for the browser to request a tab to be visible. Note that
this only measures the time from the browser deciding to make the tab
visible (after a click, or keyboard-shortcut to switch tabs), until the tab
is requested to become visible. The time it takes to actually make the tab
visible and show on screen is measured in a separate metric, in
RWH_TabSwitchPaintDuration.
ltian@chromium.org
The number of tabs currently opened when users tap "Open in new Chrome
tab" from Browser Actions context menu. This includes the new tab
created from the tap.
ltian@chromium.org
The option that the user selected from a Browser Actions context menu.
ramyasharma@chromium.org
Whether or not the user checked the option in the external protocol dialog
to remember their choice of opening or not opening the specified app.
Recorded each time the user interacts with the External Protocol Dialog,
when making a decision.
Deprecated 09/2017. This histogram has been replaced with
ExternalProtocol.HandleState.
dominickn@chromium.org
Whether or not the user checked the option in the external protocol dialog
to remember their choice of opening or not opening the specified app.
Recorded each time the user interacts with the External Protocol Dialog
(either accepting or cancelling/dismissing).
wfh@chromium.org
Count of renderer process crashes grouped by type.
wfh@chromium.org
Count of renderer process kills grouped by type.
oshima@chromium.org
Out of BrowserRenderProcessHost.ChildKills, numer of kills due to SIGKILL,
which is a strong signal of out of memory on Chrome OS, grouped by renderer
type.
wfh@chromium.org
The launch error codes for failed renderer process launches.
wfh@chromium.org
Count of renderer process launch failures grouped by type.
wfh@chromium.org
Count of renderer process crashes that we miscounted because we took the
exit code too early. Grouped by type.
horo@chromium.org
How long a render process is kept alive by additional customers such as
shared workers and service workers.
panicker@chromium.org
How long fetch is alive which in turn keeps the render process alive.
TODO(panicker): Remove after investigation of crbug/823482, likely in M68.
panicker@chromium.org
How long service worker is alive which in turn keeps the render process
alive. TODO(panicker): Remove after investigation of crbug/823482, likely in
M68.
panicker@chromium.org
How long shared worker is alive which in turn keeps the render process
alive. TODO(panicker): Remove after investigation of crbug/823482, likely in
M68.
alexmos@chromium.org
panicker@chromium.org
How long the renderer process is kept alive by a subframe unload handler.
TODO(panicker): Remove after investigation of crbug/823482.
wfh@chromium.org
Number of times BrowserRenderProcessHost::OnChannelError was called.
alexmos@chromium.org
lukasza@chromium.org
Records what happens when an attempt is made to use a spare
RenderProcessHost - logs that either the attempt succeeded or why it failed.
peconn@chromium.org
Triggered when a TrustedWebActivity is paused, recording the time since it
had been resumed.
peconn@chromium.org
The result of Digital Asset Link verification performed when starting a
Trusted Web Activity.
sadrul@chromium.org
mustash-team@google.com
Duration of an interactive resize from start to end. Measured only on
Windows.
sadrul@chromium.org
Size changed between two consecutive steps during browser-window resize.
Measured only on Windows.
sadrul@chromium.org
Number of intermediate resize-steps taken to complete the resize from start
to end. Measured only on Windows.
sadrul@chromium.org
Time-interval between two consecutive steps during browser-window resize. An
interactive resize can have many number of small steps. This measures the
interval between two steps. 'Duration' measures the interval between the
first and last steps. Measured only on Windows.
hcarmona@chromium.org
An open bubble was closed because the user accepted it.
hcarmona@chromium.org
An open bubble was closed because the user didn't accept it.
hcarmona@chromium.org
An open bubble was closed because of a focus change.
hcarmona@chromium.org
An open bubble was forced to close.
hcarmona@chromium.org
An open bubble was dismissed because a frame was destroyed.
hcarmona@chromium.org
An open bubble was dismissed because fullscreen was toggled.
hcarmona@chromium.org
An open bubble was dismissed because the page was navigated.
hcarmona@chromium.org
An open bubble was closed because a tab was detached.
hcarmona@chromium.org
An open bubble was closed because a tab was switched.
hcarmona@chromium.org
An open bubble was dismissed by the user without making a decission.
hcarmona@chromium.org
Log the amount of time any bubble was visible. Only bubbles that are shown
will have a visible time.
hcarmona@chromium.org
A bubble was given to the bubble manager but not shown.
junov@chromium.org
kbr@chromium.org
Records the context type names used to create canvas rendering contexts.
junov@chromium.org
zakerinasab@chromium.org
The source from which an ImageBitmap is created by a createImageBitmap call.
Deprecated 11/2017 with removal of Display List Canvas 2D mode.
junov@chromium.org
The reasons why a canvas initially set to display list mode had to fall back
to direct rasterization mode.
junov@chromium.org
The reasons why a GPU accelerated canvas stopped deferring its rendering
operations.
junov@chromium.org
Records the occurrence of events related to 2D canvas GPU resource
hibernation.
xidachen@chromium.org
junov@chromium.org
The type of code path that OffscreenCanvas's commit API goes through.
xlai@chromium.org
Records the occurence of image file formats passed into toDataURL and toBlob
functions in canvas.
Deprecated 08/2016 with removal of Chrome Crash Service component.
scottmg@chromium.org
Tracks the component updater steps for the Chrome Crash Service.
warx@chromium.org
Within one minute of the default network reporting a portal network, if we
see an offline detection result, it is likely the client got blacklisted.
Record the boolean rate that Chrome observes offline vs non-offline
detection results. See go/bad-portal for client blacklisting problem.
meacer@chromium.org
Records the result of a captive portal probe.
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.
michaeldo@chromium.org
The result of captive portal detection attempts performed in user session.
Detection result is recorded when portal detection is completed for a failed
secure connection.
michaeldo@chromium.org
The result of captive portal detection attempts performed in user session.
Detection result is recorded when portal detection is completed for a
request which timed out or hadn't yet replied within eight seconds.
ryanchung@google.com
Records the result of the Cast certificate verification on the Cast sender.
ryanchung@google.com
Records whether the correct nonce challenge was in the Cast receiver's
response.
ryanchung@google.com
Records whether the signature returned by the Cast receiver is verifiable
with the challenge and device certificate.
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.
aberent@chromium.org
avayvod@chromium.org
Record each interaction with the fullscreen remote playback controls in
cases when the corresponding media element on the page was present.
aberent@chromium.org
avayvod@chromium.org
Record each interaction with the fullscreen remote playback controls in
cases when the corresponding media element on the page was not present.
aberent@chromium.org
avayvod@chromium.org
Indicates whether the corresponding media element on the page was present
when the fullscreen remote playback controls were shown.
Deprecated July 2017 in favor of Media.Controls.CTR.CastOverlayButton.
avayvod@chromium.org
mlamouri@chromium.org
media-dev@chromium.org
Records events and user interactions related to the Cast overlay shown on
video elements.
aberent@chromium.org
avayvod@chromium.org
Records the ratio of the time the media element was detached from the remote
playback session to the total duration of the session (as from when the
element has been attached till when the session stopped or disconnected), in
percents.
aberent@google.com
Records the result of resolving the video URL for cast, including checking
its CORS header.
posciak@chromium.org
Indicates whether initialization of a video encode accelerator for Cast
sender was successful.
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]".
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of cellular device activation failures (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of cellular device activation tries (Chrome OS).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of cellular reconnect failures during activation (Chrome OS).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of cellular device reconnect tries during activation (Chrome OS).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of successful cellular plan established (Chrome OS).
Please list the metric's owners. Add more owner tags as needed.
The count of initiated cellular device setup starts (Chrome OS).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of failed cellular plan setup tries (Chrome OS).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of failed cellular plan purchases (Chrome OS).
Deprecated 04/2016 as doesn't have data nor owner.
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.
rsleevi@chromium.org
Information about the certificate algorithms and sizes in use on the web, to
examine compliance with the CA/Browser Forum requirements and security best
practice. This histogram considers the notBefore as the issuance date, for
purposes of what requirements apply.
sinhak@chromium.org
escordeiro@chromium.org
Number of forced logouts for child accounts on an account reconciliation
error. Check |ChromeOSChildAccountReconcilorDelegate|.
jam@chromium.org
Count of child processes killed because they sent an IPC that couldn't be
deserialized.
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.
wfh@chromium.org
Count of child utility process crashes, bucketed by the hash of their
process name. The process name is typically the service name of the mojo
service.
wfh@chromium.org
Count of child process crashes grouped by process type.
Deprecated as of 10/2015.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes that we miscounted because we took the exit
code too early. Grouped by process type.
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.
Deprecated as of 10/2015.
Please list the metric's owners. Add more owner tags as needed.
Count of child process crashes for which we were not able to understand the
exit code, grouped by process type.
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.
wfh@chromium.org
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.
wfh@chromium.org
Count of child process abnormal channel disconnects that are not classified
and reported because we took the exit code too early. Grouped by process
type.
Deprecated 3/2017.
clamy@chromium.org
What the browser was waiting for from the renderer when it was reported as
hung.
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.
wfh@chromium.org
Count of child process kills grouped by process type.
oshima@chromium.org
Out of ChildProcess.Killled, number of kills due to SIGKILL, which is a
strong signal of out of memory on Chrome OS, grouped by process type.
nasko@chromium.org
Count of child processes killed by the extension API (processes.terminate).
Deprecated as of 10/2015.
Please list the metric's owners. Add more owner tags as needed.
Count of child process kills that we miscounted because we took the exit
code too early. Grouped by process type.
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.
wfh@chromium.org
Count of child utility process launches, bucketed by the hash of their
process name. The process name is typically the service name of the mojo
service.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Indicates how many times each particular type of Activity was in the
foreground when a UMA session was terminated abnormally. UMA sessions last
as long as Chrome remains in the foreground.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Indicates how many times each particular type of Activity was brought to the
foreground when a UMA session was active (i.e. launched at some point). UMA
sessions last as long as Chrome remains in the foreground.
manzagop@chromium.org
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.
gab@chromium.org
Track set of Windows errors inside the meessage loop/pump system, where
system calls fail, and we try to gracefully recover. These errors should
really never happen, so we should be sure to look closer if they do.
gab@chromium.org
The result of every rendez-vous reported once per browser process launch.
Deprecated as of 12/2017.
aseren@yandex-team.ru
gab@chromium.org
The error code of remote process termination on Windows in case when remote
process hung. This histogram has been replaced by
Chrome.ProcessSingleton.TerminateProcessErrorCode.Windows histogram.
aseren@yandex-team.ru
gab@chromium.org
The reason of remote hang processes termination.
aseren@yandex-team.ru
gab@chromium.org
Used to send the result of interaction with remote process as histograms in
case when remote process influences on start.
aseren@yandex-team.ru
gab@chromium.org
The error code of remote process termination on Posix in case when remote
process hung.
aseren@yandex-team.ru
gab@chromium.org
The error code of remote process termination on Windows in case when remote
process hung.
aseren@yandex-team.ru
gab@chromium.org
Time it takes from TerminateProcess call to the moment when we stop waiting
for remote process switches to signal state.
aseren@yandex-team.ru
gab@chromium.org
The error code of wating for remote process termination on Windows.
gab@chromium.org
Time it takes to grab the process singleton. Reported once per successful
attempt at obtaining the singleton.
gab@chromium.org
Time it takes to return an error from the process singleton algorithm (nor
succeeding in obtaining it, nor in generating a rendez-vous). This does not
include time spent in the fast notification path (chrome_exe_main_win.cc).
gab@chromium.org
Time it takes to find the process singleton owner and notify it. Reported
once per successful rendez-vous. This does not include time spent in the
fast notification path (chrome_exe_main_win.cc).
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.
Deprecated 6/2017. No longer tracked.
asvitkine@chromium.org
Records when a page load happens, based on the same logic as the PageLoad
user action.
Deprecated 10/2016 in favor of .IntentToFirstCommitNavigationTime2.*.
lizeb@chromium.org
Time between the intent arrival in a Chrome generated custom tab and the
first navigation commit, if the navigation is successful. Similar in
principle to Startup.FirstCommitNavigationTime.
Deprecated 2017-08 in favor of
ChromeGeneratedCustomTab.IntentToFirstNavigationStartTime.
lizeb@chromium.org
In "Herb" mode shows the time between the intent arrival in a
Chrome generated custom tab and the first navigation start (note: not the
navigation commit, as the name suggests). Recorded when the page has
finished loading.
lizeb@chromium.org
For Custom Tabs generated by Chrome itself instead of external apps, this
shows the time between the intent arrival in the CCT and the first
navigation start. Recorded when the page has finished loading.
lizeb@chromium.org
For Custom Tabs generated by Chrome itself instead of external apps, this
shows time between the intent arrival in the CCT and the first "page
loaded" event, if the navigation is successful.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The actions to enable or disable services sending synced notifications.
Synced Notification Sending services can be individually disabled by the
user in the Chrome Notification center settings dialog.
elijahtaylor@google.com
dominickn@chromium.org
shihuis@google.com
Records the response when the intent picker is shown to the user on Chrome
OS to allow them to open a URL in an app.
elijahtaylor@google.com
dominickn@chromium.org
shihuis@google.com
Records the app platform chosen (or Chrome if the user did not choose an
app) when the intent picker is shown to the user on Chrome OS. The
destination may be specified due to the user explicit selection or a
previously stored preference.
Deprecated 10/2017 and replaced by Platform.DetachableBase.PairResult.
kitching@google.com
Result of a Chrome OS detachable base pair operation.
Deprecated 10/2017 and replaced by Platform.DetachableBase.ROUpdateMetric.
kitching@google.com
Result of a Chrome OS detachable base RO firmware update.
Deprecated 10/2017 and replaced by Platform.DetachableBase.RWUpdateMetric.
kitching@google.com
Result of a Chrome OS detachable base RW firmware update.
Deprecated 8/2017.
xiaowenx@chromium.org
mukai@chromium.org
The name of the current color calibration of the display on Chrome OS. This
value is sent when the color calibration is changed by the user.
wjmaclean@chromium.org
Whether the GAIA Authenticator unexpectedly encountered a null contentWindow
value while handling WebView's onContentLoad event. This metric is only
enabled for AuthMode = DEFAULT, which indicates ChromeOS online login. This
is the only mode where the issue has been observed. Other modes not captured
here are OFFLINE (offline ChromeOS login) and DESKTOP (for online GAIA login
on desktop Chrome).
achuith@chromium.org
Whether a user signed in using the new WebView-based GAIA flow. This value
is sent after the GAIA screen has completed user authentication.
zeuthen@chromium.org
The number of seconds of uptime since the last time the Chrome OS machine-id
was regenerated. This is reported every time the machine-id is regenerated
except for the first time since reboot.
zeuthen@chromium.org
The reason why the Chrome OS machine-id was regenerated. This is reported
when the machine-id is re-generated.
xdai@chromium.org
The memory pressure level in Chrome OS, which is recorded periodically (once
per second). This is used to show the relative frequency of the system being
in a critical vs relaxed memory pressure state.
yoshiki@chromium.org
omrilio@chromium.org
The cause of the scroll event by the user on the message center. Only the
first event after the message center opens is recorded. For example, the
user opens the message center and scrolls by mouse then by key, only the
mouse event is recorded. If the user closes and reopens the message center
before the second event, both events are recorded.
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 certificate expiry check during a platform verification
attempt 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.
tetsui@chromium.org
An enum value how system tray bubble is interacted e.g. by tap (touch
screen), or click (mouse, trackpad, etc.) Reported every time the region
inside system tray bubble is tapped or clicked.
tetsui@chromium.org
The amount of time a user took from clicking on the button in status area,
to clicking on an item in the system tray bubble.
tetsui@chromium.org
An enum value how system tray bubble is expanded or collapsed. It can be
toggled by the button and touch gesture.
rsesek@chromium.org
The amount of time it took to load the native libraries in the browser
process.
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.
agrieve@chromium.org
ranj@chromium.org
yfriedman@chromium.org
The total number of times Chrome uses relinker fallback to extract and load
native libraries.
rsesek@chromium.org
The amount of time it took to load the native libraries in the renderer
process.
simonb@chromium.org
Whether relro sharing was attempted for a renderer process, and if
attempted, whether it succeeded.
anandc@chromium.org
sergeyu@chromium.org
Recorded every time a Chromoting connection enters a new state.
anandc@chromium.org
sergeyu@chromium.org
The duration of sessions that were closed, normally by a user-initiated
action.
anandc@chromium.org
sergeyu@chromium.org
The duration of sessions that failed to connect.
anandc@chromium.org
sergeyu@chromium.org
The time taken to authenticate as part of a Chromoting connection request.
anandc@chromium.org
sergeyu@chromium.org
The time taken to connect to a remote-host, after a request has been
authenticated.
anandc@chromium.org
sergeyu@chromium.org
Input event delivery latency from the browser to the plugin.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
anandc@chromium.org
sergeyu@chromium.org
The bandwidth of non-empty packets in Chromoting remote sessions, updated
every time a video packet is processed and logged every 1s.
anandc@chromium.org
sergeyu@chromium.org
The time to capture a video frame on the host, returned as part of a video
packet.
anandc@chromium.org
sergeyu@chromium.org
Amount of time wasted on IPC and threading overhead when capturing a video
frame.
anandc@chromium.org
sergeyu@chromium.org
The time from when an input event is received to when the next frame is
captured.
anandc@chromium.org
sergeyu@chromium.org
The time to decode a video packet on the client.
anandc@chromium.org
sergeyu@chromium.org
The time to encode a video packet on the host, returned as part of a video
packet.
anandc@chromium.org
sergeyu@chromium.org
Delay before a newly captured frame is passed to the encoder.
anandc@chromium.org
sergeyu@chromium.org
The frame-rate of non-empty packets in Chromoting remote sessions, updated
every time a video packet is processed and logged every 1s.
anandc@chromium.org
sergeyu@chromium.org
Estimated network roundtrip latency calculated by subtracting total
processing time on host and client from the total roundtrip time.
anandc@chromium.org
sergeyu@chromium.org
The packets/sec, including empty packets, in Chromoting remote sessions,
updated every time a video packet is processed and logged every 1s.
anandc@chromium.org
sergeyu@chromium.org
The time to paint a decoded video packet on the client.
anandc@chromium.org
sergeyu@chromium.org
The time from an input being sent from the client to a response being
received by the client after it is processed by the host.
anandc@chromium.org
sergeyu@chromium.org
Delay before an encoded video packet is written to the send buffer.
Please list the metric's owners. Add more owner tags as needed.
The length of time between a dangerous download appearing on the 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. Deprecated since
M54.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time between "Report and Discard" button being shown and it being
clicked.
Please list the metric's owners. Add more owner tags as needed.
The length of time between a dangerous download appearing on the download
shelf, and the "Keep" button being clicked.
tbansal@chromium.org
Count of client hints that were received by the render process. Recorded
approximately at the time of the renderer startup.
tbansal@chromium.org
Duration for which the origin requested the client hints to be persisted.
Collected on the renderer side.
tbansal@chromium.org
Count of events when the client hints needs to be persisted to the disk by
the browser.
tbansal@chromium.org
Count of client hints that need to be persisted to the disk. Recorded by the
renderer.
Launched briefly in M-59 dev, then refactoring made obsolete.
mpearson@chromium.org
Whether Android's Clipboard.java successfully constructed a hasher to hash
clipboard entries. Recorded on construction of the class, which happens
only on startup.
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.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time between capabilities updates.
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.
Removed 12/2015. http://crbug.com/466644
vitalybuka@chromium.org
Temporarily histogram with size of IPC sockets in default location.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time used to fail to collect printer capabilities.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time used to collect printer capabilities.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time the utility process runs before disconnect.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time used to fail to generate metafile.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time used to generate metafile.
vitalybuka@chromium.org
Event counts in ServiceUtilityProcessHost.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time used to fail to collect printer capabilities.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
The amount of time used to collect printer capabilities.
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.
Removed 02/2017. http://crbug.com/643570
vitalybuka@chromium.org
Xmpp timeout option value provided by server.
sorin@chromium.org
The number of times the component updater called UpdateClient::Install or
UpdateClient::Update. These correspond to the number of manual component
update checks performed as a result of a user action, and the number of
automated component update checks.
xiaochu@chromium.org
Chrome OS only. Installation error code in CrosComponentManager.
xiaochu@chromium.org
Chrome OS only. Time it takes to mount a component image.
sorin@chromium.org
The result of an install or an update check.
sorin@chromium.org
The result of an install or an update check.
sorin@chromium.org
Time to complete an Install or an Update component update call.
weili@chromium.org
Tracks the status of PDF document composition and generation conducted in
PDF compositor service.
weili@chromium.org
Tracks the status of PDF page composition and generation conducted in PDF
compositor service.
vmpstr@chromium.org
The maximum number of images that were cached in the browser over the
lifetime of the image decode cache. This is recorded at the image cache
destruction. It is further split up by Software and Gpu rasterization.
ccameron@chromium.org
The total number of quads in all render passes in a CompositorFrame. This is
logged as the CompositorFrame is submitted to its surface.
Deprecated 05/2016. See Blink.Paint.UpdateTime as a related alternate
metric.
paint-dev@chromium.org
Area of invalidated content, in pixels, divided by update (i.e. record), in
milliseconds. Recorded when display list recording source is updated (in a
browser process).
Deprecated 05/2016. See Blink.Paint.UpdateTime as a related alternate
metric.
paint-dev@chromium.org
Time spent updating (i.e. recording) a display list, in microseconds.
Recorded when display list is updated (in a browser process).
kylechar@chromium.org
How often the layer compositor successfully submitted content to the display
compositor, or what caused an abort. This is reported fairly late in the
pipeline, during the final stages of submitting content.
yigu@chromium.org
The GPU memory allocated for tilings (in a browser process), summed over all
picture layers. Emitted once per drawing. Nothing is recorded if there are
no picture layers.
Tilings are used for decomposition of the layer's entire contents at a
picture screenspace resolution to do threaded rasterization.
Team: animations-dev@chromium.org.
yigu@chromium.org
Time spent finding the closest matching layer to a given point whenever we
do hit testing on LayerTreeImpl (in a browser process).
Team: animations-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
animations-dev@chromium.org
Time spent updating layers, in microseconds. Recorded when layers are
updated (in a browser process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
paint-dev@chromium.org
Time spent updating layer draw properties, in microseconds. Recorded when a
LayerTreeImpl's draw properties are updated (in a browser process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
paint-dev@chromium.org
The number of layers in the active tree for each compositor frame. This is
logged once per frame, before the frame is drawn (in a browser process).
paint-dev@chromium.org
The number of PictureLayers in the active tree for each compositor frame.
This is logged once per frame, before the frame is drawn (in a browser
process).
paint-dev@chromium.org
The number of render surfaces in the render surface layer list. Recorded
each time the render surface layer list is constructed (in a browser
process).
paint-dev@chromium.org
Total estimated memory used by SkPictures in the layer tree, in kilobytes.
Recorded once per frame, before the frame is drawn (in a browser process).
paint-dev@chromium.org
Area of invalidated content, in pixels, divided by update (i.e. record), in
milliseconds. Recorded when picture pile is updated (in a browser process).
paint-dev@chromium.org
Time spent updating (i.e. recording) a picture pile, in microseconds.
Recorded when picture pile is updated (in a browser process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 11/2016. Increased the max tracking range to accomendate GPU
raster, and will require new baskets.
paint-dev@chromium.org
Rasterized area, in pixels, divided by rasterization time, in milliseconds,
of a compositor rasterization task. Recorded after the task finishes (in a
browser process).
paint-dev@chromium.org
Rasterized area, in pixels, divided by rasterization time, in milliseconds,
of a compositor rasterization task. Recorded after the task finishes (in a
browser process).
paint-dev@chromium.org
Time spent completing a compositor rasterization task, in microseconds.
Recorded after the task finishes (in a browser process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 02/2016. We'd learned as much as we could from this metric and it
made no sense to keep it around.
vollick@chromium.org
Tracks the number of missing tiles that had some image content in the
browser process.
Deprecated 02/2016. We'd learned as much as we could from this metric and it
made no sense to keep it around.
vollick@chromium.org
Tracks the number of missing tiles that did not have any image content in
the browser process.
fsamuel@chromium.org
The result of submitting a CompositorFrame to a CompositorFrameSink.
ACCEPTED means the frame was accepted by the CompositorFrameSink.
COPY_OUTPUT_REQUESTS_NOT_ALLOWED means an unprivileged client attempted to
readback a texture. SURFACE_INVARIANTS_VIOLATION means size or device scale
factor changed but a new viz::LocalSurfaceId was not allocated.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time taken for the sync readback of pixels is measured here.
weiliangc@chromium.org
Time spent drawing of composited layers by GLRenderer, in microseconds. This
is logged once per frame, when a frame should be drawn.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
weiliangc@chromium.org
Time spent drawing of composited layers by SoftwareRenderer, in
microseconds. This is logged once per frame, when a frame should be drawn.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
yiyix@chromium.org
Time spent to remove invisible quads from the quad_list in CompositorFrame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 02/2018, replaced by similar metric
Compositing.Display.Draw.Occlusion.Drawing.Area.Saved2.
yiyix@chromium.org
It records the total drawing area skipped to show on screen as a result of
applying draw occlusion. This is logged once per frame, when the frame is
drawn.
yiyix@chromium.org
It records the total drawing area skipped to show on screen as a result of
applying draw occlusion. This is logged once per frame, when the frame is
drawn.
yiyix@chromium.org
It records the percentage of total area drawing skipped by draw occlusion of
the total area of damage rects in a compositor frame. This is logged once
per frame, when the frame is drawn.
ccameron@chromium.org
This is logged once per frame, when the frame is drawn. The total number of
quads in all render passes in the CompositorFrame that is produced by
surface aggregation.
Deprecated 03/2018. We'd learned enough from this metric and it made no
sense to keep it around.
yiyix@chromium.org
This is logged once per frame, when the frame is drawn. Captures area of all
draw quads that need to go through no scale and no translation transforms.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Area of invalidated content, in pixels, divided by update (i.e. record), in
milliseconds. Recorded when display list recording source is updated.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Time spent updating (i.e. recording) a display list, in microseconds.
Recorded when display list is updated.
Deprecated 05/2017 in Issue 710306. Histogram was used temporarily for
tracking a potential performance regression.
paint-dev@chromium.org
Time spent finding the closest matching layer to a given point, in
microseconds. Recorded each time we do hit testing on LayerTreeImpl.
fsamuel@chromium.org
The amount of time it took for a main frame with unresolved dependencies to
activate. Note that some activations may be triggered due to a deadline
hitting.
Deprecated 04/2016, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
dneto@chromium.org
The number of layers in the active tree for each compositor frame. This is
logged once per frame, before the frame is drawn.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Total estimated memory used by SkPictures in the layer tree, in kilobytes.
Recorded once per frame, before the frame is drawn.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Area of invalidated content, in pixels, divided by update (i.e. record), in
milliseconds. Recorded when picture pile is updated.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Time spent updating (i.e. recording) a picture pile, in microseconds.
Recorded when picture pile is updated.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Rasterized area, in pixels, divided by rasterization time, in milliseconds,
of a compositor rasterization task. Recorded after the task finishes.
Deprecated 09/2015, replaced by similar metrics under Compositing.Renderer
and Compositing.Browser, depending on which process it occurs in.
paint-dev@chromium.org
Time spent completing a compositor rasterization task, in microseconds.
Recorded after the task finishes.
vmpstr@chromium.org
The maximum number of images that were cached in the renderer over the
lifetime of the image decode cache. This is recorded at the image cache
destruction. It is further split up by Software and Gpu rasterization.
ccameron@chromium.org
The outcome of attempting to replace all renderer tiles with CALayers.
Either success, or the first reason why a DrawQuad couldn't be replaced by a
CALayer.
khushalsagar@chromium.org
The outcome for whether an image could be sucessfully deferred for
asynchronous decode in the renderer compositor. If not, the reason for using
a synchronous decode. An image which is decoded asynchronously will be
checkerboarded on the rasterized tiles until the decode is finished, as
opposed to synchronous decodes where the tile rasterization is blocked on
the image decode completing.
ccameron@chromium.org
The total number of quads in all render passes in a CompositorFrame. This is
logged as the CompositorFrame is submitted to its surface.
Deprecated 05/2016. See Blink.Paint.UpdateTime as a related alternate
metric.
paint-dev@chromium.org
Area of invalidated content, in pixels, divided by update (i.e. record), in
milliseconds. Recorded when display list recording source is updated (in a
renderer process).
Deprecated 05/2016. See Blink.Paint.UpdateTime as a related alternate
metric.
paint-dev@chromium.org
Time spent updating (i.e. recording) a display list, in microseconds.
Recorded when display list is updated (in a renderer process).
kylechar@chromium.org
How often the layer compositor successfully submitted content to the display
compositor, or what caused an abort. This is reported fairly late in the
pipeline, during the final stages of submitting content.
yigu@chromium.org
The GPU memory allocated for tilings (in a renderer process), summed over
all picture layers. Emitted once per drawing. Nothing is recorded if there
are no picture layers.
Tilings are used for decomposition of the layer's entire contents at a
picture screenspace resolution to do threaded rasterization.
Team: animations-dev@chromium.org.
yigu@chromium.org
Time spent finding the closest matching layer to a given point whenever we
do hit testing on LayerTreeImpl (in a renderer process).
Team: animations-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
animations-dev@chromium.org
Time spent updating layers, in microseconds. Recorded when layers are
updated (in a renderer process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
paint-dev@chromium.org
Time spent updating layer draw properties, in microseconds. Recorded when a
LayerTreeImpl's draw properties are updated (in a renderer process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
paint-dev@chromium.org
The number of layers in the active tree for each compositor frame. This is
logged once per frame, before the frame is drawn (in a renderer process).
paint-dev@chromium.org
The number of PictureLayers in the active tree for each compositor frame.
This is logged once per frame, before the frame is drawn (in a renderer
process).
paint-dev@chromium.org
The number of render surfaces in the render surface layer list. Recorded
each time the render surface layer list is constructed (in a renderer
process).
paint-dev@chromium.org
Total estimated memory used by SkPictures in the layer tree, in kilobytes.
Recorded once per frame, before the frame is drawn (in a renderer process).
paint-dev@chromium.org
Area of invalidated content, in pixels, divided by update (i.e. record), in
milliseconds. Recorded when picture pile is updated (in a renderer process).
paint-dev@chromium.org
Time spent updating (i.e. recording) a picture pile, in microseconds.
Recorded when picture pile is updated (in a renderer process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 11/2016. Increased the max tracking range to accomendate GPU
raster, and will require new baskets.
paint-dev@chromium.org
Rasterized area, in pixels, divided by rasterization time, in milliseconds,
of a compositor rasterization task. Recorded after the task finishes (in a
renderer process).
paint-dev@chromium.org
Rasterized area, in pixels, divided by rasterization time, in milliseconds,
of a compositor rasterization task. Recorded after the task finishes (in a
renderer process).
paint-dev@chromium.org
Time spent completing a compositor rasterization task, in microseconds.
Recorded after the task finishes (in a renderer process).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 02/2016. We'd learned as much as we could from this metric and it
made no sense to keep it around.
vollick@chromium.org
Tracks the number of missing tiles that had some image content in the
renderer process.
Deprecated 02/2016. We'd learned as much as we could from this metric and it
made no sense to keep it around.
vollick@chromium.org
Tracks the number of missing tiles that did not have any image content in
the renderer process.
weiliangc@chromium.org
Checkerboarded area, in number of pixels, that has recording but does not
have time to finish rastering yet. A sample is recorded everytime a frame is
drawn while a scroll is in progress. Tracking bug 535732.
weiliangc@chromium.org
Checkerboarded area, in number of pixels, that has no recording to raster
from. A sample is recorded everytime a frame is drawn while a scroll is in
progress. Tracking bug 535732.
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.
weiliangc@chromium.org
Time spent aggregating compositor frames from different surfaces in
microseconds. This is logged once per frame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
kylechar@chromium.org
The number of SurfaceDrawQuads where the surface doesn't exist. This is
logged for each call to Aggregate().
kylechar@chromium.org
The number of SurfaceDrawQuads where the surface exists but doesn't have an
active CompositorFrame. This is logged for each call to Aggregate().
fsamuel@chromium.org
The number of SurfaceDrawQuads where the primary SurfaceId does not have a
corresponding active CompositorFrame and so the fallback surface is used
instead. This is logged for each call to Aggregate().
kylechar@chromium.org
The number of SurfaceDrawQuads where the surface exists and has an active
CompositorFrame. This is logged for each call to Aggregate().
fsamuel@chromium.org
Tracks whether an activation of a surface was due to due to a deadline or
the resolution of dependencies.
fsamuel@chromium.org
The amount of time it took for a Surface with unresolved dependencies to
activate. Note that some activations may be triggered due to a deadline
hitting. That is tracked in the DeadlineHit histogram.
fsamuel@chromium.org
The number of times a renderer in this browser session has violated a
surface synchronization invariant. This manifests as a skipped frame.
Ideally this metric should always report 0, but realistically there are
races in the system and this tracks the frequency that we hit these races.
Deprecated 2018/01/24.
kylechar@chromium.org
The number of temporary references that have existed for at least 10 seconds
and are most likely orphaned. This is logged every 10 seconds.
kylechar@chromium.org
Tracks the reason for removing a temporary reference.
chrisha@chromium.org
The number of confirmed bad modules found during module enumeration.
chrisha@chromium.org
The length of time it takes to enumerate the loaded modules in the browser
process.
chrisha@chromium.org
The length of time it takes to enumerate the shell extensions.
chrisha@chromium.org
The length of time it takes to enumerate the Winsock LSP modules.
chrisha@chromium.org
The cumulative length of time it takes to inspect all modules on disk,
extracting their certificates and version information. This work is actually
spread out over a much longer period of time so as not to impact the user.
chrisha@chromium.org
The cumulative length of time it takes to enumerate and inspect all modules.
This work is actually spread out over a much longer period of time so as not
to impact the user.
chrisha@chromium.org
The number of suspected bad modules found during module enumeration.
ebeach@google.com
Connectivity Diagnostics App: WiFi signal strength recorded during
NIC_SIGNAL_STRENGTH test.
The "Strength" property of a WiFi signal is a partially-reversible
function that linearly maps the RSSI range -120dBm to -20dBm to Strength
values from 0 to 100.
ebeach@google.com
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.
mlamouri@chromium.org
The default autoplay setting at profile open.
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.
Support for keygen was removed.
svaldez@chromium.org
The default setting for using key generation in forms at profile open.
toyoshim@chromium.org
The default location setting at profile open.
msramek@chromium.org
The default camera setting at profile open.
msramek@chromium.org
The default microphone setting at profile open.
This setting was deprecated in r322364 and replaced with separate settings
for camera and microphone. See
ContentSettings.DefaultMediaStreamCameraSetting and
ContentSettings.DefaultMediaStreamMicSetting.
toyoshim@chromium.org
msramek@chromium.org
The default MediaStream setting at profile open.
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.
mlamouri@chromium.org
steimel@chromium.org
The default sound setting at profile open.
csharrison@chromium.org
The default subresource filter setting at profile open
reillyg@chromium.org
The default permission setting for WebUSB at profile open.
jyasskin@chromium.org
The default permission setting for Web Bluetooth at profile open.
rhalavati@chromium.org
Records the number of times Flash permission is granted for a host.
lshang@chromium.org
The number of user defined content setting exceptions at browser start.
Suffixed with the name of content setting types.
lshang@chromium.org
Records the schemes of content setting exceptions at browser start. Each
exception provides one sample.
alexmos@chromium.org
Records how often a content settings exception for the file: scheme has a
non-empty path. Recorded once per exception at browser start.
alexmos@chromium.org
Count of how often a specific content type has a content settings exception
defined for a file: scheme with no path (i.e., wildcard path). Recorded once
per exception at browser start.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
alexmos@chromium.org
Count of how often a specific content type has a content settings exception
defined for a file: scheme with a valid, non-empty path. Recorded once per
exception at browser start.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
calamity@chromium.org
Counts which content setting buttons are pressed by the user.
Deprecated 2015-10-05 in Issue 433475. Histogram was used temorarily for
diagnosing crash causes.
scheib@chromium.org
Numer of results of parsing WebsiteSettingsHandler::last_setting_ success or
failure in WebsiteSettingsHandler methods.
estark@chromium.org
Tracks whether the mixed content shield was shown, and how the user
interacted with it.
battre@chromium.org
The number of user defined cookies setting exceptions for allowing cookies
at browser start.
battre@chromium.org
The number of user defined cookies setting exceptions for blocking cookies
at browser start.
battre@chromium.org
The number of user defined hostname patterns for content settings at browser
start.
battre@chromium.org
The number of user defined cookies setting exceptions for 'clearing cookies
on browser exit' at browser start.
Removed 11/2015 in favor of Permissions.Action.*
miguelg@chromium.org
Tracks whether a permission was granted, rejected, etc. The suffix of the
histogram indicates which particular permission.
Removed 11/2015 in favor of Permissions.Action.InsecureOrigin.*
miguelg@chromium.org
Tracks whether a permission was granted, rejected, etc on an insecure
origin. The suffix of the histogram indicates which particular permission.
Removed 11/2015 in favor of Permissions.Action.SecureOrigin.*
miguelg@chromium.org
Tracks whether a permission was granted, rejected, etc on a secure origin.
The suffix of the histogram indicates which particular permission.
kcarattini@chromium.org
dominickn@chromium.org
miguelg@chromium.org
Number of times a given permission was requested by a website and the user
has the permission set to prompt (i.e. not blocked or allowed).
Note this is probably not the metric you want - it does not correspond to
the total number of times websites request a permission. Also, because
specific permissions have code that can automatically block or grant
permissions based on things like incognito, installed extensions etc., this
does also not correspond to the number of times users are prompted to allow
permissions.
For a better metric to track how often users are prompted, either use
ContentSettings.PermissionsActions*, or Permissions.Prompt.*.
See https://crbug.com/638076 for more details.
kcarattini@chromium.org
dominickn@chromium.org
miguelg@chromium.org
Number of times a given permission was requested by an insecure origin and
the user has the permission set to prompt (i.e. not blocked or allowed).
Note this is probably not the metric you want - it does not correspond to
the total number of times websites request a permission. Also, because
specific permissions have code that can automatically block or grant
permissions based on things like incognito, installed extensions etc., this
does also not correspond to the number of times users are prompted to allow
permissions.
For a better metric to track how often users are prompted, use
ContentSettings.PermissionsActions*.
See https://crbug.com/638076 for more details.
kcarattini@chromium.org
dominickn@chromium.org
miguelg@chromium.org
Number of times a given permission was requested by a secure origin and the
user has the permission set to prompt (i.e. not blocked or allowed).
Note this is probably not the metric you want - it does not correspond to
the total number of times websites request a permission. Also, because
specific permissions have code that can automatically block or grant
permissions based on things like incognito, installed extensions etc., this
does also not correspond to the number of times users are prompted to allow
permissions.
For a better metric to track how often users are prompted, use
ContentSettings.PermissionsActions*.
See https://crbug.com/638076 for more details.
tommycli@chromium.org
Tracks whether the plugin content blocked puzzle piece was shown in the
Omnibox, and how the user interacted with it.
charleszhao@chromium.org
Tracks whether the popup content blocked puzzle piece was shown in the
Omnibox, and how the user interacted with it.
csharrison@chromium.org
Counts of various events related to the popup blocker. Including blocked
popups and overridden (clicked through) popups. This is similar to the
ContentSettings.Popups but is at the per-popup layer rather than at the UI
layer.
csharrison@chromium.org
The blocked popup list contains a list of links that Chrome has blocked via
the popup blocker. If a user clicks on the link, the popup is opened. This
metric records the position of the popup in the list that a user clicks
through. Currently it should only be recorded on desktop platforms, because
the mobile UI for popup blocking does not currently allow for specific
exceptions.
csharrison@chromium.org
Measures the total duration a popup WebContents is visible / foregrounded,
until it is closed.
csharrison@chromium.org
Measures the total duration a popup WebContents is visible / foregrounded,
until it is closed via some user gesture (like Ctrl-W).
Deprecated in favor of ContentSettings.Popups.FirstDocumentEngagementTime2.
csharrison@chromium.org
Measures the total duration a popup WebContents is visible / foregrounded
for the duration of its first document load. This time is measured from the
first navigation commit to the time either the WebContents is destroyed or
when a new navigation commits.
csharrison@chromium.org
Measures the total duration a popup WebContents is visible / foregrounded
for the duration of its first document load. This time is measured from the
first navigation commit to the time either the WebContents is destroyed or
when a new navigation commits.
csharrison@chromium.org
The total number of popups blocked by the strong blocker for a given page
load. Logged when the page is navigated away from, or the tab is closed.
Only logged for pages which are triggered for strong popup blocking, aka
abusive experience enforcement.
csharrison@chromium.org
Counts of various events related to the strong popup blocker (aka abusive
experience enforcement), that is triggered via safe browsing.
csharrison@chromium.org
ericrobinson@chromium.org
For pages that trigger Safe Browsing triggered popup blocker (in warn or
enforce modes), records the position in the redirect chain for the page the
activation was triggered by. If SubresourceFilterConsiderRedirects is
disabled, then always returns "Only navigation".
pnoland@chromium.org
Android: The integer status code of network requests made by the feed
library's networking host. This code includes both protocol(1xx-5xx) and
non-protocol(-xxx) errors. Recorded when a request completes.
pnoland@chromium.org
Android: the size in kb of gzip-compressed requests sent by the Feed's
networking host. Recorded when a request is sent.
pnoland@chromium.org
Android: the uncompressed size in KB of responses received by the Feed's
networking host. Recorded when a successful response is received.
pnoland@chromium.org
Android: failure reason when attempting to fetch an OAuth token for the
feed. Recorded when a token fetch completes.
Deprecated in favor of
ContentSuggestions.FetchPendingSpinner.VisibleDuration.
dgn@chromium.org
ntp-dev+metrics@chromium.org
Android: How long the content suggestion placeholder is shown. This is
tracked based on when the placeholder is enabled in the UI, not how long it
is actually visible on screen. Depending on the screen size, the used value
could be bigger.
dgn@chromium.org
ntp-dev+metrics@chromium.org
Android: How long the content suggestion loading spinner is shown. This is
tracked based on when the spinner is enabled in the UI, not how long it is
actually visible on screen. Depending on the screen size, the used value
could be bigger.
michaeldo@chromium.org
Logs true when the system touches are cancelled in order to show the Context
Menu instead of performing a default system action. Only logged on iOS.
michaeldo@chromium.org
Logged when DOM element details are not yet available when the user
completes a long press. Also logs if the context menu was shown once the
element details became available or if the display was cancelled. This
ensures that all context menu gestures are eventually processed. Only logged
on iOS.
michaeldo@chromium.org
How long it takes to fetch the details of the DOM element the user is
selecting for the context menu. On iOS, JavaScript must be run in order to
get the details of the DOM element. If the element is not inside the main
frame, latency could be added due to the communication between frames. Only
logged on iOS.
michaeldo@chromium.org
Logged when the Context Menu will be displayed. Also logs if the element for
the last touch was found in the main frame or a iframe. Only logged on iOS.
qinmin@chromium.org
Type of the url when user saves the content through the save link context
menu.
newt@chromium.org
The option that the user selected from a context menu.
mpearson@chromium.org
Recorded when a context menu is shown, sliced by whether a web contents was
present. (It generally should be; indeed, this code path should not be
followed when it is absent. For instance, invoking a context menu from the
new tab page or from the sad tab page will not cause an emission to this
histogram.) Note that this refers to link context menus, not the
cut-copy-paste context menus that can appear during long presses on text on
a web page or long presses in the omnibox. The value of this histogram for
"present" could be usefully compared with the total count of
ContextMenu.SelectedOption to determine the clickthrough rate for context
menus.
michaeldo@chromium.org
Logged when an unexpected FindElementResultHandler message was received by
the application. An unexpected message may be sent by a malicious frame.
Only logged on iOS.
michaeldo@chromium.org
Logs true when the context menu gesture recognizer fully recognizes a long
press, but is still waiting on the DOM element details before the context
menu can be shown. Only logged on iOS.
huayinz@chromium.org
twellington@chromium.org
Android: Whether contextual suggestions are enabled. Recorded when the
enabled state changes. Note that this may be recorded multiple times per
session.
donnd@chromium.org
fgorski@chromium.org
twellington@chromium.org
Records each event handled by the Contextual Suggestions backend. Recorded
when the event is sent to the backend, typically when a UI or network action
is registered. Implemented for Android.
pnoland@chromium.org
Android: The net::Error status code of contextual suggestion fetches.
Recorded when a fetch completes.
pnoland@chromium.org
fgorski@chromium.org
Android: the amount of time taken elapsed between a contextual suggestion
fetch starting and ending. Recorded when a fetch is completed.
pnoland@chromium.org
Android: The size of the serialized and base64-encoded proto sent to the
server when fetching contextual suggestions. Recorded when a fetch is
initiated.
pnoland@chromium.org
Android: The http status code of contextual suggestion fetches. Recorded
when a fetch completes.
pnoland@chromium.org
Android: The number of bytes in the response received when a contextual
suggestions fetch completes. Recorded when the response is received.
Removed 2018-06-01 in favor of a histogram that measures bytes received over
the network directly instead of the uncompressed KB.
pnoland@chromium.org
Android: The size of the response body received when a contextual
suggestions fetch completes. Recorded when the response is received.
fgorski@chromium.org
Android: The length of a visit on a page. Reported for HTTP and HTTPS pages
provided there was something visible printed to the screen. Selecting a tab
or loading a new URL in current tab starts timing a visit. Switching to a
different tab, closing the tab or loading a new URL finishes timing and
reports the time if the page did a visually non-empty paint or finished
loading.
huayinz@chromium.org
twellington@chromium.org
Android: Whether the user preference for contextual suggestions is enabled.
Recorded on cold start and when the user has changed the preference state.
Note that this may be recorded multiple times per session.
mkwst@chromium.org
tnagel@chromium.org
Records the age (in days) of the oldest cookie delivered along with a
request. Recorded when setting the `Cookie` header for a given request.
mkwst@chromium.org
tnagel@chromium.org
Records the age (in days) of all cookies delivered along with a request.
Recorded when setting the `Cookie` header for a given request.
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.
Deprecated 2015-08-17 as part of cookie histogram cleanup
(https://crbug.com/521135).
Please list the metric's owners. Add more owner tags as needed.
Intervals between access time updates for each cookie.
morlovich@chromium.org
Recorded when a problem occurs trying to commit changes to the cookie store
back to disk, in the SQLite store.
mkwst@chromium.org
Record when at attempt is made to delete an equivalent cookie on a set
cookie operation and when such a cookie is found and deleted. Also measure
when strict secure cookie rules affect this outcome and prevent a cookie
from being deleted.
Removed 2017-07-14 as it demonstrated that making cookie parsing rules
stricter was not feasible. See https://crbug.com/638117.
ricea@chromium.org
Indicates whether a cookie initialised from a Set-Cookie header value was
valid or not. This is only logged after cookies containing control
characters have already been rejected, so "Invalid" here means
that the cookie contains quotes, commas, backslashes or top-bit-set
characters.
estark@chromium.org
Number of times a cookie was set with a name prefixed by
"__Secure-" or "__Host-" (prefixes reserved by
https://tools.ietf.org/html/draft-west-cookie-prefixes).
estark@chromium.org
Number of times a cookie was set with a name prefixed by
"__Secure-" or "__Host-" that violate cookie prefix
rules. That is, a __Secure- cookie must be set over a secure connection with
the Secure attribute, and a __Host- cookie must be set over a secure
connection, with the Secure attribute, with no Domain attribute, and with a
Path attribute of "/". (As defined in
https://tools.ietf.org/html/draft-west-cookie-prefixes.)
estark@chromium.org
For each cookie added to the store, record whether its source URL has a
cryptographic scheme, broken down by Secure and not Secure.
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.
nharper@chromium.org
For each cookie removed from the store, the reason it was removed.
Deprecated 2015-08-17 as part of cookie histogram cleanup
(https://crbug.com/521135).
Please list the metric's owners. Add more owner tags as needed.
For each domain, number of cookies in that domain (recorded every 10 minutes
of active browsing time).
Deprecated 2015-08-17 as part of cookie histogram cleanup
(https://crbug.com/521135).
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of subdomains in that top level domain
(recorded every 10 minutes of active browsing time).
Deprecated 2015-08-17 as part of cookie histogram cleanup
(https://crbug.com/521135).
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of cookies in that domain (recorded every
10 minutes of active browsing time).
nharper@chromium.org
For each evicted (not expired) cookie, the amount of time since it was last
used
battre@chromium.org
Number of minutes until cookie expires when set.
rockot@chromium.org
The length of time between when the network stack receives a request for a
cookie list and when it actually responds to the request or abandons it (for
e.g. a closed renderer).
mkwst@chromium.org
The size of each outgoing request's 'Cookie' header field's value, in bytes.
Please list the metric's owners. Add more owner tags as needed.
Whether killing the database because it was corrupted beyond repair
succeeded.
morlovich@chromium.org
Recorded when a problem is recorded when loading the persistent cookie
store.
tnagel@chromium.org
Degree of protection against cookie theft. Recorded for each cookie when
setting the `Cookie` header for a request.
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.
pwnall@chromium.org
This histogram records the total duration of time during which at least one
web request was blocked waiting for the cookie store to load. If no requests
were affected, the value is 0. If two requests are simultaneously blocked
for 1 second, the value is 1 second. If two requests are consecutively
blocked for 1 second each, the value is two seconds.
pwnall@chromium.org
The number of distinct Effective Top-Level Domains Plus One (ETLD+1, i.e.,
google.com, bbc.co.uk) for which a priority cookie load occurred.
Deprecated as of 8/2015.
huangs@chromium.org
The duration in seconds between a cookie getting evicted (due to the number
of cookies exceeding a domain limit), and subsequently reinstated.
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.
Deprecated as of 9/2015. The associated experiment was flawed.
erikchen@chromium.org
The number of session cookies deleted on shutdown. This metric is emitted
even if no cookies are deleted.
Deprecated as of 9/2015. The associated experiment was flawed.
erikchen@chromium.org
The amount of time required to delete session cookies on shutdown. This
metric is emitted even if no cookies are deleted.
erikchen@chromium.org
The number of session cookies deleted on startup. This metric is emitted
even if no cookies are deleted. This metric is not emitted if session
cookies are restored, rather than deleted on startup.
erikchen@chromium.org
The amount of time required to delete session cookies on startup. This
metric is emitted even if no cookies are deleted. This metric is not emitted
if session cookies are restored, rather than deleted on startup.
nharper@chromium.org
The amount of time (ms) between the cookie store load starting and
completing.
pwnall@chromium.org
The amount of time (ms) to migrate a v9 cookie database to v10.
Deprecated as of 04/2015. The migration has finished for most users.
The amount of time (ms) to migrate a v4 database to v5.
Deprecated as of 04/2015. The migration has finished for most users.
The amount of time (ms) to migrate a v5 database to v6.
Deprecated as of 04/2015. The migration has finished for most users.
The amount of time (ms) to migrate a v6 database to v7.
Deprecated as of 04/2015. The migration has finished for most users.
The amount of time (ms) to migrate a v7 database to v8.
erikchen@chromium.org
The amount of time (ms) to migrate a v8 database to v9.
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.
pwnall@chromium.org
This histogram records the wall-clock delay between a priority load task
being posted to the DB-thread and its execution.
erikchen@chromium.org
This histogram records the the total amount of time spent fetching the
cookies associated with an eTLD+1 from disk, including time spent waiting in
task queues.
pwnall@chromium.org
This histogram records the sum of the durations of all initial tasks loading
cookies from the database.
erikchen@chromium.org
This histogram records the wall-clock delay between the Load task being
posted to the DB-thread and its execution.
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).
wychen@chromium.org
The cache hit status of metadata extraction for AppIndexing.
wychen@chromium.org
The time spent on scanning the document in the main frame to extract the
metadata. The metadata would be used to feed Icing for CopylessPaste feature
on Android. This only counts pages with failed or empty JSON extraction.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
wychen@chromium.org
The error status of metadata extraction for AppIndexing.
wychen@chromium.org
The time spent on scanning the document in the main frame to extract the
metadata. The metadata would be used to feed Icing for CopylessPaste feature
on Android. This only counts pages with successful JSON extraction.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
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. Note: Due to
https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier.
See also Stability.CrashedProcessAge.Extension that is usually logged at the
same time.
wfh@chromium.org
The exit codes for crashed renderer processes. Note: Due to
https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier.
See also Stability.CrashedProcessAge.Renderer that is usually logged at the
same time.
crashpad-dev@chromium.org
The reason that a crash report entered the upload pending state.
crashpad-dev@chromium.org
The size of a crash report minidump on disk when captured.
crashpad-dev@chromium.org
Logs whether a crash uploaded succeeded or failed.
crashpad-dev@chromium.org
The reason that a crash report upload was skipped.
crashpad-dev@chromium.org
The outcome of execution of the Crashpad exception handler.
crashpad-dev@chromium.org
The exception code encountered in a crash on Mac OS X.
crashpad-dev@chromium.org
The exception code encountered in a crash on Windows.
crashpad-dev@chromium.org
A count of the number of exceptions handled by Crashpad with two buckets for
starting and finishing.
crashpad-dev@chromium.org
The exception code encountered for a crash of the crash handler process on
Mac OS X.
crashpad-dev@chromium.org
The exception code encountered for a crash of the crash handler process on
Windows.
crashpad-dev@chromium.org
Handler start/crash/exit events.
Deprecated as of 04/2016 as CrashPad does not implement this.
siggi@chromium.org
Reports the result of an attempt to report a crash dump via Breakpad.
Success indicates only that the out-of-process crash reporter succesfully
generated a dump. The success or failure of the eventual upload is not
measured. This stability metric is logged from the first Chrome launch
post-dump.
Deprecated as of 04/2016 as CrashPad does not implement this.
siggi@chromium.org
Reports the result of an attempt to report a dump via Breakpad without
crashing. Success indicates only that the out-of-process crash reporter
succesfully generated a dump. The success or failure of the eventual upload
is not measured. This stability metric is logged from the first Chrome
launch post-dump.
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.
Deprecated 01/2017 in Issue 680162 with the removal of Kasko.
siggi@chromium.org
Counts crash reports that the Kasko crash reporter fails to upload and hands
off to Chrome. Kasko stores the failed reports in a location specified by
Chrome. Chrome records this metric when it detects new minidump files in
that location. Currently the reports are discarded, but they could
eventually be uploaded via the Chrome network stack.
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.
alemate@chromium.org
Records the number of times when first-run dialog was shown.
alemate@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.
alemate@chromium.org
The total time that user spent on first-run tutorial.
alemate@chromium.org
The time that user spent on some step of tutorial.
alemate@chromium.org
Tracks the way how user left tutorial.
alemate@chromium.org
Records the number of times when first-run tutorial has been launched.
benwells@chromium.org
tbuckley@chromium.org
Recorded each time a Crostini app is launched, recording whether the app is
the built in terminal, a registered app, or an unknown app.
jopra@chromium.org
tbuckley@chromium.org
Records the number of Crostini apps that surface in the launcher at login
time (not including the Terminal). This only logs if Crostini is enabled for
the current user.
benwells@chromium.org
tbuckley@chromium.org
Recorded each time the user completes the Crostini setup UI, recording the
result of the setup.
benwells@chromium.org
tbuckley@chromium.org
Recorded each time the user initiates the Crostini setup UI, recording the
UI surface that invoked the setup.
benwells@chromium.org
tbuckley@chromium.org
The time from a user setting up their device, to the user enabling Crostini.
benwells@chromium.org
tbuckley@chromium.org
Recorded each time the user completes the Crostini uninstall UI, recording
the result of the uninstall.
benwells@chromium.org
tbuckley@chromium.org
Recorded each time the user initiates the Crostini uninstall UI, recording
the UI surface that initiated the uninstall.
hansberry@chromium.org
Indicates that there was no issue retrieving supported and enabled software
features, or that there were enabled features which were not in the
supported feature set.
jhawkins@chromium.org
The top-level result of the CryptAuth device enrollment process.
dkrahn@chromium.org
Checksum status of critical persistent data used by Cryptohome. This status
is recorded every time the cryptohomed daemon reads a file.
loyso@chromium.org
In low disk space scenarios, Cryptohome erases whole user profiles. This is
a number of user profiles deleted during cleanup. Only reported when
non-zero.
dspaid@chromium.org
The status of the user home directory migration from ecryptfs to
ext4-crypto. This is logged once at the end of each migration.
kinaba@chromium.org
The error code of file operation by which the user home directory migration
from ecryptfs to ext4-crypto has failed. This is logged once the migration
encounters a file I/O error.
kinaba@chromium.org
The type of file operation at which the user home directory migration from
ecryptfs to ext4-crypto has failed. This is logged once the migration
encounters a file I/O error.
kinaba@chromium.org
The category of the path where the user home directory migration from
ecryptfs to ext4-crypto has failed. This is logged once the migration
encounters a file I/O error.
dspaid@chromium.org
The total amount of free disk space on the system when the user started the
migration from ecryptfs to ext4-crypto. This is only logged when the user
encounters an insufficient space error.
dspaid@chromium.org
The total amount of free disk space on the system when the user received an
insufficient space error during the migration from ecryptfs to ext4-crypto.
This is only logged when the user encounters an insufficient space error.
dspaid@chromium.org
The total number of bytes of xattr data that we are trying to store on a
file when we receive an insufficient space error. This includes both xattr
data already present on the file as well as the new xattr we are trying to
set. This is only logged during ecryptfs to ext4-crypto migration if we
receive an insufficient space error when setting a new extended attribute.
dspaid@chromium.org
The status of the user home directory migration from ecryptfs to
ext4-crypto. This is logged once at the start of each migration.
hashimoto@chromium.org
The total byte count (MB) of the data in a user's home directory which is
being migrated from ecryptfs to ext4-crypto. This is logged once when a new
migration starts.
hashimoto@chromium.org
The total file count in a user's home directory which is being migrated from
ecryptfs to ext4-crypto. This is logged once when a new migration starts.
dspaid@chromium.org
pmarko@chromium.org
The status of the user home directory minimal migration from ecryptfs to
ext4-crypto. This is logged once at the end of each minimal migration.
dspaid@chromium.org
pmarko@chromium.org
The status of the user home directory minimal migration from ecryptfs to
ext4-crypto. This is logged once at the start of each minimal migration.
loyso@chromium.org
In low disk space scenarios, Cryptohome erases caches while target amount of
free disk space is not reached. It starts from low priority categories. This
histogram reports which topmost priority was reached to fulfill a cleanup
request.
dkrahn@chromium.org
Cryptohome errors.
Deprecated 05/2018 in favor of Cryptohome.GCache.FreedDiskSpaceInMb. Reports
zero in 99% of hits.
oka@chromium.org
The amount of drive cache (MB) which was evicted by cryptohome due to
shortage of remaining disk space.
loyso@chromium.org
In low disk space scenarios, Cryptohome performs a lot of disk space
operations to erase data. This is a number of milliseconds taken to perform
a cleanup. Reported only if longer than 5 ms.
loyso@chromium.org
This is an amount of Google Drive cache (MB) which was evicted by cryptohome
due to shortage of remaining disk space. Reported only if something was
deleted (greater than zero).
dspaid@chromium.org
The encryption type used for a user's cryptohome directory. This is logged
each time the cryptohome is mounted.
alemate@chromium.org
This is the status of cryptohome migration to GaiaId. Every time user logs
in current migration status is recorded.
fukino@chromium.org
The amount of consumed battery level during cryptohome encryption migration.
This is logged when the battery level decreases during migration, and the
data is used to check if the minimum battery level required to start
migration is appropriate.
fukino@chromium.org
The first screen in the encryption migration UI, which is shown when a user
attempts to log in to the system and old encryption (eCryptfs) is detected.
fukino@chromium.org
The result of encryption migration from eCryptfs to Ext4 dircrypto. The
recorded result is what the migration UI in Chrome side is notified from
cryptohomed.
fukino@chromium.org
The result of the removal of user's cryptohome. When the migration UI is
notified that the migration failed, the UI tries to remove the user's
cryptohome to make sure that the user can create clean crytohome directory
in the next sign-in.
fukino@chromium.org
User's choice when the system is ready to migrate encryption. The user can
start migration or skip it. It is used to know how many users have skipped
migration.
fukino@chromium.org
How many times each screen in migration UI is shown to the user. A screen is
recorded as a visible screen when the screen is kept displayed at least for
a second.
dspaid@chromium.org
The amount of time (ms) for the user's home directory to be migrated from
ecryptfs to ext4-crypto. If the migration is interrupted and subsequently
resumed (such as due to power loss) then no value is recorded for either
attempt.
dspaid@chromium.org
The amount of time (ms) for the user's home directory to be migrated from
ecryptfs to ext4-crypto if the minimal migration method was used. If the
minimal migration is interrupted and subsequently resumed (such as due to
power loss) then no value is recorded for either attempt.
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.
afakhry@chromium.org
The errors resulting from interacting with the Trusted Platform Module (TPM)
device.
ranj@chromium.org
yfriedman@chromium.org
Records the time duration in CustomTab Activity from onStart/onResume to
onStop/onPause, if that activity is opened by Webapp/WebApk/Trusted Web
Activity.
yusufo@chromium.org
Android: AppId declared by the launching application in EXTRA_APPLICATION_ID
in a custom tab. This histogram is used as a means to count the total
instances of custom tabs created meanwhile binning them across launching
apps that have identified themselves.
nyquist@chromium.org
ssid@chromium.org
Android: Recorded whenever user closes the custom tab by hitting the close
button or back to return to the caller app. Keeps track of the connection
status and whether the app was using a KeepAlive connection. Recorded only
for AGSA.
nyquist@chromium.org
ssid@chromium.org
Android: Recorded whenever user closes the custom tab by hitting the close
button or back to return to the caller app. Keeps track of the connection
status and whether the app was using a KeepAlive connection. Recorded for
all apps other than AGSA.
lizeb@chromium.org
Time between the start of a detached resource request and its completion
(failure or success). Android only.
lizeb@chromium.org
Reports the final status of the detached request, including success.
Recorded once per detached resource request. Android only.
lizeb@chromium.org
Number of redirects followed by a detached resource request until success or
failure. Android only.
mvanouwerkerk@chromium.org
Time to create an activity delegate for a custom tabs dynamic module.
Android only.
mvanouwerkerk@chromium.org
Time to create the package context for a custom tabs dynamic module. Android
only.
mvanouwerkerk@chromium.org
Time to load the entry point class for a custom tabs dynamic module. Android
only.
mvanouwerkerk@chromium.org
Time to instantiate the entry point class for a custom tabs dynamic module.
Android only.
mvanouwerkerk@chromium.org
Possible results when loading a custom tabs dynamic module. Android only.
Deprecated 10/2016 in favor of .IntentToFirstCommitNavigationTime2.*.
lizeb@chromium.org
Time between the intent arrival in Chrome and the first navigation commit,
if the navigation is successful. Similar in principle to
Startup.FirstCommitNavigationTime.
Deprecated 2017-08 in favor of CustomTabs.IntentToFirstNavigationStartTime.
lizeb@chromium.org
Time between the intent arrival to a Custom Tab and the navigation start
(note: not the navigation commit, as the name suggests). Recorded when the
page has finished loading. Non-"Herb" mode.
lizeb@chromium.org
Time between the intent arrival to a Custom Tab and the first navigation
commit. Recorded for every custom tabs intent when the page has finished
loading.
lizeb@chromium.org
Time between the intent arrival to a Custom Tab and the navigation start.
Recorded when the page has finished loading. Non-"Herb" mode.
lizeb@chromium.org
Time between the intent arrival in Chrome and the first "page
loaded" event, if the navigation is successful. Non-"Herb"
mode.
lizeb@chromium.org
Android only. Which flavors of mayLaunchUrl() were used before a tab launch.
Can be low and/or high confidence. Recorded at the same time as
CustomTabs.WarmupStateOnLaunch for the buckets "Session, No Warmup,
Warmup called from another UID", "Session, No Warmup" and
"Session, Warmup".
Deprecated 4/2018 when prerender was removed from Custom Tabs.
lizeb@chromium.org
Android: When there is a prerender for a session with non-default
parameters, whether the prerender was matched when navigating.
lizeb@chromium.org
Recorded only on Android. Whether a parallel request was requested by the
calling application, and if so its initial status. Recorded once per handled
intent, when the request is initiated.
lizeb@chromium.org
For Custom Tabs, records whether mayLaunchUrl() has been called, and if so,
whether the call was later matched by a URL launch.
lizeb@chromium.org
When a URL prediction succeeds, time in ms between the prediction and the
actual launch.
Deprecated 4/2018 when prerender was removed from Custom Tabs.
lizeb@chromium.org
Android: When prerendering a URL for Custom Tabs, whether the client session
uses the default parameters.
lizeb@chromium.org
Android: When a spare WebContents is created from Custom Tabs, record
creation, and whether it was used, killed or destroyed. Creation is recorded
to get the "abandoned" case, that is when Chrome is killed before
the renderer.
lizeb@chromium.org
Android: When a spare WebContents is created from Custom Tabs, record how
long is took before the render process was killed.
mattcary@chromium.org
Recorded only for Android. How a speculation was started or why it was
disallowed. This is recorded when a speculation of any kind is requested,
with either a "Speculation allowed" value, or a reason why it was
not allowed. If the speculation is allowed and is attempted to be started,
the status on start will be counted in addition: one of
"Prefetch", "Prerender", "Background Tab" or
"Prerender not started". The last case is when a prerender is
abandoned during start.
mattcary@chromium.org
Recorded only for Android. Recorded when a speculation is requesting to swap
into a visible tab.
yusufo@chromium.org
Recorded only for Android. Records on every metrics upload whether the
currently visible tab is a custom tab. The custom tab is launched by a
client app with customized UI. Some metrics like page load time will behave
differently for these tabs since it will be possible to warm up the browser
process and prepare resources for specific urls ahead of time via a service
connection. This histogram can be used to cluster these metric differently.
lizeb@chromium.org
Recorded only on Android. Reports whether warmup() has been called when a
Custom Tabs Intent is received from an application, and if so, whether the
call could be matched with a session.
lizeb@chromium.org
Android: When a CustomTabActivity creates its Tab, whether we use a
prerendered WebContents, a spare renderer or create a new WebContents.
Replaced by DataReductionProxy.LoFi.Accuracy.
bengr@chromium.org
tbansal@chromium.org
Counts the accuracy of estimated network quality when using Lo-Fi. Counters
are incremented when a main frame URL request is handled by Data Reduction
Proxy and session was in Auto Lo-Fi enabled field trial.
Deprecated as of 8/2017, per server-directed preview decision.
tbansal@chromium.org
Counts the changes in the state of Lo-Fi request header (q=low) being added
to the Chrome proxy request header. Counters are incremented when a main
frame URL request is handled by Data Reduction Proxy and session was in Auto
Lo-Fi enabled field trial.
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.
Deprecated 2018/04.
tbansal@chromium.org
bengr@chromium.org
Records if the platform detected that a captive portal is present on the
current network. Recorded at the time of Chrome startup and on IP change
event. Recorded only for users that have data saver enabled.
Removed in Feb. 2016
bengr@chromium.org
Size of the response body. This is the actual number of bytes received,
which usually agrees with but is not necessarily the same as the size
specified by the Content-Length header. Only recorded if the request is sent
while a simulated Data Reduction Proxy configuration fetch is taking place.
Removed in Feb. 2016
bengr@chromium.org
The difference between the size specified in the X-Original-Content-Length
header and the size of the response body. Only recorded if the request is
sent while a simulated Data Reduction Proxy configuration fetch is taking
place. Only positive values are logged, so if X-Original-Content-Length is
not specified or if it equals or exceeds the content length, it is not
logged.
Removed in Feb. 2016
bengr@chromium.org
Size specified in the X-Original-Content-Length header. If this header is
not present in the response, the size of the response body is used. Only
recorded if the request is sent while a simulated Data Reduction Proxy
configuration fetch is taking place.
bengr@chromium.org
Total number of authentication required responses received from the Data
Reduction Proxy.
An "Unexpired" value is recorded every time a new client config is
fetched and parsed successfully. An "Expired" value is recorded
every time Chrome receives an authentication failure from the data saver
proxy.
bengr@chromium.org
tbansal@chromium.org
On receiving an authentication failure from the data reduction proxy,
records whether the session key used in the request matches the current
session key.
Recorded every time Chrome receives an authentication failure from the data
saver proxy.
bengr@chromium.org
tbansal@chromium.org
Time from when the request starts to the time when the auth failure is
received from the data saver proxy.
Recorded every time an auth failure is received from the data saver proxy.
bengr@chromium.org
The number of failed attempts when retrieving the configuration from the
Data Reduction Proxy API before a successful attempt took place.
Recorded every time a new client config is fetched and parsed successfully.
If the device has a valid connection type but no Internet connectivity, this
count will keep increasing.
bengr@chromium.org
Time from when the Data Reduction Proxy configuration request starts until
it completes.
Recorded every time a new client config is fetched and parsed successfully.
bengr@chromium.org
Count per HttpResponseCode when attempting to retrieve the Data Reduction
Proxy configuration from the Data Reduction Proxy API.
bengr@chromium.org
tbansal@chromium.org
Upper bound on the count of HTTP requests that did or did not go through the
data saver proxy.
An HTTP request may not go through data saver proxy if the config was
unavailable, due to local bypass rules, or due to server side bypasses. If
data saver is turned on, this metric is recorded every time proxy is
resolved for an HTTP request.
bengr@chromium.org
robertogden@chromium.org
Upper bound on the count of main frame requests that did or did not go
through the data saver proxy.
A main frame request may not go through data saver proxy if the config was
unavailable, due to local bypass rules, or due to server side bypasses. If
data saver is turned on, this metric is recorded every time proxy is
resolved for an HTTP request.
Deprecated 2018/04.
tbansal@chromium.org
bengr@chromium.org
Records whether the persisted client config for data saver proxies read from
the disk at the time of Chrome startup was expired or not. Recorded once at
the time of Chrome startup.
robertogden@chromium.org
Records whether the client config client sent variation headers in the
config request.
tbansal@chromium.org
bengr@chromium.org
Records the number of days since data reduction proxy was last enabled by
the user. Recorded only if the data reduction proxy was last enabled since
this metric was added to Chromium (M-56). Recorded at Chrome startup if data
reduction proxy is already enabled, and when the user enables the data
reduction proxy.
tbansal@chromium.org
bengr@chromium.org
Records the number of days since the data reduction savings were cleared
because the system clock moved back by more than 1 day. Recorded at Chrome
startup if data reduction proxy is enabled, and if the data reduction proxy
savings were cleared in some previous Chrome session.
robertogden@chromium.org
bengr@chromium.org
When the data savings are cleared because the user deletes their browsing
history, record how many buckets were deleted. See also
DataReductionProxy.SavingsCleared.Reason/User action - cleared browsing
history.
bengr@chromium.org
rajendrant@chromium.org
Samples of user interactions with the Data Saver settings menu across all
platforms (android, IOS, desktop extension). Data is collected whenever user
toggles the ON/OFF switch in the settings menu for reducing data usage.
For desktop, Off-to-On/On-to-Off histogram count will increment when the
data saver extension is installed/uninstalled respectively as well.
Removed in June 2017
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTP responses that have been checked
for tampering. This assumes the data reduction proxy injected fingerprints
have not been tampered with. Only the data reduction proxy responses with
200 OK response code are checked.
Removed in June 2017
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTPS responses that have been checked
for tampering. This assumes the data reduction proxy injected fingerprints
have not been tampered with. Only the data reduction proxy responses with
200 OK response code are checked.
Removed in June 2017
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTP responses that passed the tamper
detection. This assumes the data reduction proxy injected fingerprints have
not been tampered with. Only the data reduction proxy responses with 200 OK
response code are checked.
Removed in June 2017
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
For each carrier, the total number of HTTPs responses that passed the tamper
detection. This assumes the data reduction proxy injected fingerprints have
not been tampered with. Only the data reduction proxy responses with 200 OK
response code are checked.
Removed in June 2017
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
The total number of HTTP responses that some part (specified by suffix name)
have been tampered with. This assumes the data reduction proxy injected
fingerprints have not been tampered with. Only the data reduction proxy
responses with 200 OK response code are checked.
Removed in June 2017
xingx@chromium.org
bolian@chromium.org
bengr@chromium.org
The total number of HTTPS responses that some part (specified by suffix
name) have been tampered with. This assumes the data reduction proxy
injected fingerprints have not been tampered with. Only the data reduction
proxy responses with 200 OK response code are checked.
kundaji@chromium.org
Time taken to load historical data usage from Level DB into memory. This UMA
is reported each time the method to load historical data usage is called,
which happens when user views data usage history.
tbansal@chromium.org
Net error codes observed when invalid response headers were received from
data reduction proxy.
rajendrant@chromium.org
bengr@chromium.org
Records the aggregate data use of services for the last week. Different
conditions are added as suffixes to this histogram. Recorded when Chrome is
started, so this does not include the current session. The aggregation
happens when requests complete. The current week calculation is based on
week starting from the Epoch day(Thursday, January 1, 1970), and every 7
days is treated as a week.
rajendrant@chromium.org
bengr@chromium.org
Records the aggregate data use for the last week. This is the downstream
data use of all user-initiated traffic. Recorded when Chrome is started, so
this does not include the current session. The aggregation happens when
requests complete. The current week calculation is based on week starting
from the Epoch day(Thursday, January 1, 1970), and every 7 days is treated
as a week.
kundaji@chromium.org
Status of calling Open() on Data Reduction Proxy LevelDB.
kundaji@chromium.org
Size of Data Reduction Proxy LevelDB measured at startup.
Deprecated as of 8/2017, per server-directed preview decision.
bengr@chromium.org
tbansal@chromium.org
Records the accuracy of estimated network quality when using Lo-Fi. Network
quality predicted at the time of navigation start is compared with the
network quality observed during the specified time interval following the
start of the navigation. This metric is recorded only when the session is in
Lo-Fi enabled field trial.
Obsolete as of October 2017.
bengr@chromium.org
megjablon@chromium.org
Counts of Lo-Fi implicit opt out actions. If the user chooses to "Load
image" for k pages in a session, LoFi is disabled for the remainder of
that session. If Lo-Fi is disabled for j consecutive sessions, Lo-Fi is
disabled for that user until the next implicit opt out epoch, which may be
in a later session, or never. k and j default to 3 and are assigned via the
DataReductionProxyLoFi field trial.
Deprecated as of October 2017 per transition to blacklist.
bengr@chromium.org
megjablon@chromium.org
Tracks Lo-Fi usage at the granularity of browser sessions. Counts for each
session if Lo-Fi was used or not. In the case where Lo-Fi was not used,
records if it was because the network quality was always good or because the
user had implicitly opted out. The session where a user permanently opts out
is counted in the Lo-Fi used bucket.
bengr@chromium.org
megjablon@chromium.org
Counts of pageloads that received or requested, but did not receive, various
Lo-Fi lite page transformations. Recorded when a lite page is requested or
received through Data compression proxy.
Deprecated as of 9/2016, replaced by Previews.ContextMenuAction.LoFi.
bengr@chromium.org
megjablon@chromium.org
User interactions with the Lo-Fi snackbar and context menu option. These
include:
Displays and clicks on the "Load images" snackbar. Displays and
clicks on the "Load image" and "Load images"context menu
options. Count of pages where the user has clicked "Load image" at
least once.
Removed 2018/04.
bengr@chromium.org
sclittle@chromium.org
Counts the response bytes of responses that Chrome expected to come through
a data reduction proxy and have the data reduction proxy via header, but
where the data reduction proxy via header was missing. Note that this does
not include responses that were bypassed.
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.
tbansal@chromium.org
Records if the network properties of a network were found in the cache or
not. Recorded every time there is a change in the connection type.
ryansturm@chromium.org
Counts the number of times that pageload metrics were queued to be attempted
or not queued based on the reporting fraction. Recorded once per pageload.
ryansturm@chromium.org
Counts various actions related to crash detection in the pingback client.
This is recorded only when a renderer crash occurs on a Data Reduction Proxy
page load.
ryansturm@chromium.org
Counts the number of times that a batched pingback request succeeded or
failed at being sent to the server. Recorded everytime a pingback request is
attempted.
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.
dougarnett@chromium.org
Records the sending of accepted transform headers to the data reduction
proxy and also receiving transforms and policies from the data reduction
proxy. Recorded on a per page request basis and also on a per image resource
request basis for empty-image transforms. Headers for both types of requests
(pages and resources) are recorded here for convenience in viewing in a
single histogram. In general, the separate groups of request/receive buckets
for either page or resource types can be compared.
dougarnett@chromium.org
Records the reason that a page request is not accepting proxy server
transforms. Recorded on a per page request basis.
sclittle@chromium.org
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.
tbansal@chromium.org
bengr@chromium.org
Records the scheme of the data reduction proxy server. Recorded for every
request that is fetched successfully through a data reduction proxy server.
Deprecated in 5/2017, since the experiment to use default QUIC alternative
proxy was deprecated.
tbansal@chromium.org
bengr@chromium.org
Status of the availability of valid alternative data reduction proxy
servers. This metric is recorded only when data reduction proxy delegate is
queried for the value of the supported alternative proxy server.
As of M66 this has been superceded by Net.AlternativeProxyFailed.
tbansal@chromium.org
Number of times an alternative QUIC proxy was marked as broken.
tbansal@chromium.org
Records the result of the attempt to use a data reduction proxy that
supports QUIC. The metric is logged for every request for which the resolved
proxy is a data reduction HTTPS proxy.
Deprecated in 2/2016, since it didn't get recorded for many kinds of error
codes when it should have been recorded, and
Net.HttpRequestCompletionErrorCodes is a good enough replacement when
filtering for clients with the Data Reduction Proxy enabled.
sclittle@chromium.org
bengr@chromium.org
Reports the different network errors that requests that try to use the data
reduction proxy are completing with, including OK and ABORTED.
Deprecated in 2/2016, since it didn't get recorded for many kinds of error
codes when it should have been recorded, and
Net.HttpRequestCompletionErrorCodes is a good enough replacement when
filtering for clients with the Data Reduction Proxy enabled.
sclittle@chromium.org
bengr@chromium.org
Reports the different network errors that main frame resource requests that
try to use the data reduction proxy are completing with, including OK and
ABORTED.
Deprecated 2018/04.
tbansal@chromium.org
bengr@chromium.org
Content type of the resource determined by data reduction proxy. Used for
determining the data reduction proxy that should be used for fetching the
resource. Logged once per resource for only the resources that are eligible
for fetching by data reduction proxies.
sclittle@chromium.org
bengr@chromium.org
Reports the state of the proxy server field in the response seen by the Data
Reduction Proxy bypass logic.
Replaced by DataReductionProxy.SavingsCleared.Reason in M68.
tbansal@chromium.org
bengr@chromium.org
Records if the data reduction savings were cleared because the system clock
moved back by more than 1 day. Recorded at Chrome startup if the data
reduction proxy is enabled.
robertogden@chromium.org
bengr@chromium.org
Records why the data reduction savings were cleared. See also
DataReductionProxy.DeleteBrowsingHistory.NumBuckets.
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 they toggle the ON/OFF switch.
bengr@chromium.org
megjablon@chromium.org
Logs the data savings in MB of the data reduction proxy snackbar promo that
was shown. The snackbar promo shows the user the amount of data Chrome has
saved them using Data Saver.
rajendrant@chromium.org
bengr@chromium.org
Records the negative data savings percentage at Chrome startup for data
saver enabled users who have browsed a reasonable amount (at least 10MB
since data saver was enabled).
rajendrant@chromium.org
bengr@chromium.org
Records the data savings percentage at Chrome startup for data saver enabled
users who have browsed a reasonable amount (at least 10MB since data saver
was enabled). Negative savings are not recorded.
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).
tbansal@chromium.org
bengr@chromium.org
Count of the number of requests that were successfully fetched via data
reduction proxy. The bucket represents the index of the data reduction proxy
in the data reduction proxy list.
tbansal@chromium.org
bengr@chromium.org
Count of the number of main frame requests that were successfully fetched
via data reduction proxy. The bucket represents the index of the data
reduction proxy in the data reduction proxy list.
rajendrant@chromium.org
bengr@chromium.org
Records the aggregate data use of services for the current week. Different
conditions are added as suffixes to this histogram. Recorded when Chrome is
started, so this does not include the current session. The aggregation
happens when requests complete. The current week calculation is based on
week starting from the Epoch day(Thursday, January 1, 1970), and every 7
days is treated as a week.
rajendrant@chromium.org
bengr@chromium.org
Records the aggregate data use for the current week. This is the downstream
data use of all user-initiated traffic. Recorded when Chrome is started, so
this does not include the current session. The aggregation happens when
requests complete. The current week calculation is based on week starting
from the Epoch day(Thursday, January 1, 1970), and every 7 days is treated
as a week.
Deprecated 2018/04.
tbansal@chromium.org
bengr@chromium.org
Records the time duration between the data saver initialization and the
first HTTP request that is resolved through the data saver proxy. On IP
address changes, time duration between the IP address change event and the
next subsequent HTTP request that resolves through the data saver proxy is
recorded.
bengr@chromium.org
megjablon@chromium.org
Samples of user interactions with the Data Reduction Proxy promos, First Run
Experience, main menu footer, and settings menu. All samples are mutually
exclusive. These samples include:
The user interactions with the First Run Experience. On Android when the
user sees the FRE card, the Data Reduction Proxy defaults to ON. The user
can disable the proxy via a switch on the card. The state of the proxy is
sampled when the First Run Experience is completed and only reported if the
Data Reduction Proxy card was shown.
The user interactions with the second run promo. On Android, there are two
actions that dismiss this promo (enable or dismiss). This is sampled when
the promo leaves view.
The user interactions with the Infobar promo. On Android, there are two
actions that dismiss the promo (enable, dismiss). This is sampled when the
promo leaves view.
The user interactions with the Snackbar promo. The user can either ignore
the promo or click the action to the settings menu. From the settings menu,
the user may enable or disable the proxy.
The user interactions with the main menu footer. The user can click the
footer to enter the settings menu. From the settings menu, the user may
enable or disable the proxy.
Any other user interaction with the ON/OFF switch in the settings menu for
reducing data usage. Only the setting changes between entering the reducing
data usage setting menu and leaving the menu will be sampled regardless of
how many times they toggle the ON/OFF switch. Other samples that report
ON/OFF settings menu changes are not also reported here.
The views of and user interactions with the site breakdown in the settings
menu. The site breakdown can be sorted by data saved descending or data used
descending, and expanded to view more sites. The Data Reduction statistics
can also be reset.
tbansal@chromium.org
The total original content size displayed to the user. Computed over the
last 30 days. Recorded when the user views the data savings in the UI.
robertogden@chromium.org
bengr@chromium.org
The difference between the total data savings as displayed to the user and
the sum of the data savings for all hosts in the data use breakdown.
Calculated as a percentage of `abs(summedSavingsTotal -
displayedSavingsTotal) / (summedSavingsTotal + displayedSavingsTotal)`.
Recorded when the user views the data savings in the UI.
tbansal@chromium.org
The percentage of data savings displayed to users. Computed over the last 30
days. Recorded when the user views the data savings in the UI.
Deprecated March 2018. Percent no longer displayed.
tbansal@chromium.org
The total data saved displayed to the user. Computed over the last 30 days.
Recorded when the user views the data savings in the UI.
robertogden@chromium.org
bengr@chromium.org
The difference between the total data usage as displayed to the user and the
sum of the data usage for all hosts in the data use breakdown. Calculated as
a percentage of `abs(summedUsageTotal - displayedUsageTotal) /
(summedUsageTotal + displayedUsageTotal)`. Recorded when the user views the
data savings in the UI.
tbansal@chromium.org
Records the result of an attempt to fetch the warmup URL.
tbansal@chromium.org
Records the total number of warmup URL (i.e., the probe URL) fetch attempts
that were made before the warmup URL was successfully fetched.
tbansal@chromium.org
Number of times the data reduction proxy warm up URL was fetched.
tbansal@chromium.org
Whether the warm up URL was fetched succesfully.
tbansal@chromium.org
Whether the response headers of the warm up URL had Chrome Proxy via header.
Recorded only when non-null response headers were available when the fetch
of warm up URL concludes.
tbansal@chromium.org
HTTP response code of the warm up URL. Set to 1 when HTTP response headers
were unavailable.
tbansal@chromium.org
Net error codes observed when the fetch of the warm up URL concludes.
tbansal@chromium.org
Proxy scheme of the proxy server via which the warm up URL was fetched.
Recorded only when non-null response headers were available when the fetch
of warm up URL concludes.
tbansal@chromium.org
Whether the warmup (or probe) URL was successfully fetched over a data saver
proxy.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The number of invalid matching rules fetched from the platform external data
use observer. A sample is recorded everytime fetch done callback is called.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The number of valid matching rules fetched from the platform external data
use observer. A sample is recorded everytime fetch done callback is called.
Deprecated 2018/07.
rajendrant@chromium.org
bengr@chromium.org
Records the sequence number of the page load within a data usage tracking
session. Logged for each navigation in the tracking session.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The time taken in milliseconds to fetch the matching rules for the first
time from the platform external data use observer. This measures the
duration from the start time of Chromium to the time the rules are returned
asynchronously. A sample is recorded when the first fetch done callback is
called.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The time taken in milliseconds to submit the data use reports to the
platform external data use observer. This measures the duration from the
time of report submission to the time report submission done asynchronous
callback is received. A sample is recorded everytime report submission done
callback is received.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The time taken in milliseconds for a regular expression to parse an URL. A
sample is recorded evertime regular expression parsing is done for an URL.
Deprecated 2018/07.
bengr@chromium.org
tbansal@chromium.org
Count of bytes in the data use reports that were intended to be submitted to
the platform external data use observer.
Deprecated 2018/07.
bengr@chromium.org
tbansal@chromium.org
Result of data usage report submission.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The duration from the start time of a tab entry's latest data usage tracking
session, till when the entry is expired and removed from the tab model. This
is for tab entries that are still actively tracking data usage for a
Chromium tab.
Tab model maintains the tab entries, each pertaining to tracking sessions of
a single Chromium tab. These entries are considered expired after some
duration and can be removed from the tab model after that. The sample is
taken when an expired tab entry still tracking data usage is removed from
the tab model.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The duration from the end time of a tab entry's latest data usage tracking
session, till when the entry is expired and removed from the tab model. This
is for tab entries that are not actively tracking data usage for a Chromium
tab.
Tab model maintains the tab entries, each pertaining to tracking sessions of
a single Chromium tab. These entries are considered expired after some
duration and can be removed from the tab model after that. The sample is
taken when an expired inactive tab entry is removed from the tab model.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The duration from the end time of a data usage tracking session, till when
the tracking session is removed from the tab model. This is for old tracking
sessions that are not actively tracking data usage.
Tab model maintains a limited number of tracking sessions per Chromium tab.
When this limit is reached oldest inactive tracking sessions are removed.
The sample is taken when an old inactive tracking session of a tab is
removed from the tab model.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The lifetime of a data usage tracking session of a Chromium tab, maintained
by the tab model. This is the duration between the time tracking started due
to an entry event and ended with an exit event. The sample is taken when the
data usage tracking session ends.
Deprecated 2018/07.
bengr@chromium.org
rajendrant@chromium.org
The duration from the end time (start time, if still active) of a tab
entry's latest data usage tracking session, till when the entry is removed
from the tab model. This is for tab entries that are not expired yet, and
removed from the tab model.
Tab model maintains a limited number of entries, each pertaining to tracking
sessions of a single Chromium tab. When this limit is reached even after
removing expired tab entries, then oldest unexpired tab entries are removed.
The sample is taken when an unexpired tab entry is removed from the tab
model.
Deprecated 2018/07.
rajendrant@chromium.org
bengr@chromium.org
The reason for ending the data usage tracking session. Logged when the
tracking session ends.
Deprecated 2018/07.
rajendrant@chromium.org
bengr@chromium.org
The reason for starting the data usage tracking session. Logged when the
tracking session was started.
Deprecated 2018/07.
bengr@chromium.org
megjablon@chromium.org
Samples of user interactions with the Data Use snackbar and dialog. These
samples include:
Displays of the snackbar that indicates the start of data use tracking and
clicks on its "More" button. Displays of snackbar that indicates
the end of data use tracking and clicks on its "More" button.
Displays of the dialog that indicates the end of data use tracking and the
user interactions with it, which include: clicking "Continue",
clicking "Cancel", clicking "Learn more", and opting out
of seeing the dialog. If the user opts out of seeing the dialog, they will
see the snackbar that indicates the end of data use tracking from then on.
Replaced by KB version in October, 2017.
rajendrant@chromium.org
bengr@chromium.org
The total background data use of Chrome's services broken down by service
name. It is logged only in Android when the URLRequest of a service
completes.
Replaced by DataUse.AllServicesKB.* version in June, 2018.
rajendrant@chromium.org
bengr@chromium.org
The total background data use of Chrome's services broken down by service
name. It is logged only in Android when the URLRequest of a service
completes.
bengr@chromium.org
rajendrant@chromium.org
The request and response size of the messages exchanged by all the services.
Whenever a URLRequest of a service is completed, the number of exchanged
bytes is logged in this histogram. The buckets in this histogram are
services recorded by the corresponding network traffic annotation tag
hashes, so it makes it possible to compare the use of different services in
different conditions. Different conditions are added as suffixes to this
histogram. If the OS is not Android all the requests are considered
foreground.
rajendrant@chromium.org
bengr@chromium.org
Records the data use of Chrome user traffic by the foregound vs. background
state of the app and tab.
rajendrant@chromium.org
bengr@chromium.org
The time since Chrome is in background when background data use happens.
Recorded for each byte of background data use. The source of traffic whether
from user browsing or chrome services is added as suffix to this histogram.
rajendrant@chromium.org
bengr@chromium.org
The time since Chrome is in background when first background data use
happens. Recorded when first background downstream data use after Chrome is
in background. The source of traffic whether from user browsing or chrome
services is added as suffix to this histogram.
tbansal@chromium.org
Count of total bytes received by the Chrome on the network.
tbansal@chromium.org
Count of total bytes sent by the Chrome on the network.
Deprecated 2018/05. Bytes are logged to DataUse.ContentType.ServicesKB.
rajendrant@chromium.org
bengr@chromium.org
Data use of Chrome services traffic by different content types. Recorded
when network bytes are received by Chrome.
rajendrant@chromium.org
bengr@chromium.org
Data use of Chrome services traffic by different content types. Recorded in
KB when network bytes are received by Chrome.
Deprecated 2017/04. Bytes are logged to DataUse.ContentType.UserTrafficKB.
rajendrant@chromium.org
bengr@chromium.org
Data use of user traffic by different content types. Recorded when network
bytes are received by Chrome.
rajendrant@chromium.org
bengr@chromium.org
Data use of user traffic by different content types. Recorded in KB when
network bytes are received by Chrome.
rajendrant@chromium.org
bengr@chromium.org
Records the downstream network data use of favicon requests. Logged when the
request is completed or redirected. Zero bytes are recorded when the request
is served from cache.
rajendrant@chromium.org
bengr@chromium.org
Records the downstream network data use of favicon requests with non 200
response code. Logged when the request is completed or redirected.
Deprecated 10/2017.
bengr@chromium.org
The request and response size of the messages exchanged by a service. It is
logged when the URLRequest of a service is completed. The service name is
added as a suffix to this histogram name.
Replaced by DataUse.AllServicesKB.* version in June, 2018.
bengr@chromium.org
The request and response size of the messages exchanged by all the services.
Whenever a URLRequest of a service is completed, the number of exchanged
bytes is logged in this histogram. The buckets in this histogram are
services, so it makes it possible to compare the use of different services
in different conditions. Different conditions are added as suffixes to this
histogram. If the OS is not Android all the requests are considered
foreground.
Deprecated 2018/05. Bytes are logged to
DataUse.PageTransition.UserTrafficKB.
rajendrant@chromium.org
bengr@chromium.org
Data use of user traffic by different core page transition types. Recorded
when the URL request finishes.
rajendrant@chromium.org
bengr@chromium.org
Data use of user traffic by different core page transition types. Recorded
in KB when the URL request finishes.
Deprecated 10/2017.
bengr@chromium.org
Number of downloaded bytes of different data types in Sync service for
received updates. It is updated when an update message is received from sync
server.
Deprecated 10/2017.
bengr@chromium.org
Number of downloaded entities of different data types in Sync service for
received updates. It is updated when an update message is received from sync
server.
Deprecated 10/2017.
bengr@chromium.org
Number of downloaded bytes of ProgressMarker of different data types in Sync
service for received updates. It is updated when an update message is
received from sync server.
Deprecated 10/2017.
bengr@chromium.org
Number of uploaded bytes of different data types in Sync service for sent
commits. Updated when a commit message is sent to sync server.
Deprecated 10/2017.
bengr@chromium.org
Number of uploaded entities of different data types in Sync service for sent
commits. Updated when a commit message is sent to sync server.
bengr@chromium.org
The total data use of Chrome's services. There is no ResourceRequestInfo
attached to these requests. If the OS is not Android all the requests are
considered foreground.
bengr@chromium.org
The total amount of data use of Chrome for user traffic. This traffic has
content::ResourceRequestInfo attached to its request. If the OS is not
Android all the requests are considered foreground.
satorux@chromium.org
Whether an asynchronous D-Bus method call is successful.
satorux@chromium.org
The time spent for an asynchronous D-Bus method call.
satorux@chromium.org
Whether a call to a D-Bus exported method is handled successfully.
satorux@chromium.org
The time spent for handling a call to a D-Bus exported method.
satorux@chromium.org
The time spent for handling a D-Bus signal.
satorux@chromium.org
The time spent for sending a D-Bus signal.
satorux@chromium.org
Whether a synchronous D-Bus method call is successful.
satorux@chromium.org
The time spent for a synchronous D-Bus method call.
pmonette@chromium.org
grt@chromium.org
The HRESULT from ActivateApplication when opening the Win10+ settings page
fails.
Deprecated 2015/11. Renamed to DefaultBrowser.SetDefaultAsyncDuration.
pmonette@chromium.org
How long it took to set Chrome as the default browser asynchronously in
Windows 10+. The duration is recorded only on Success, Failure, Abandoned
and Retry result codes.
Deprecated 2015/11. Renamed to DefaultBrowser.SetDefaultResult.
pmonette@chromium.org
The count of how many times users were successfully able to set Chrome as
the default browser asynchronously in Windows 10+.
pmonette@chromium.org
Possible user interactions with the default browser info bar.
gab@chromium.org
Results of interaction with set-as-default dialog in Win8+ first run flow.
Deprecated 2016/03. The async set-as-default experiments are finished.
pmonette@chromium.org
How long it took to set Chrome as the default browser asynchronously in
Windows 10+. The duration is recorded only on Success, Failure, Abandoned,
Retry and NoErrorsNotDefault result codes.
Deprecated 2016/03.
pmonette@chromium.org
The outcome of an attempt to set Chrome as the user's default browser.
pmonette@chromium.org
The outcome of an attempt to set Chrome as the user's default browser.
pmonette@chromium.org
The reason why the default browser settings interaction concluded on Windows
10.
pmonette@chromium.org
The registry keys for the default browser protocols (http/https) are
monitored to know when the user finished interacting with the system
settings. This is how long it took for the last registry watcher to get
signaled.
gab@chromium.org
Whether Chrome was the default browser when it started up.
pmonette@chromium.org
When changing the default browser on Windows 10, records whether the browser
chooser is successfully invoked when opening the settings page. This
histogram is only recorded when the Win10AcceleratedDefaultBrowserFlow
experiment is enabled.
Deprecated 2015/11. The same information is available as the value Failure
in DefaultBrowser.SetDefaultResult.
gab@chromium.org
In the make-default infobar, the user explicitly declined to set Chrome as
default. Or, on OSes requiring the SetAsDefaultUI, the user explicitly chose
another browser as default from the interactive UI. TODO(gab): Split the
interactive signal into a separate histogram.
Deprecated 2015/11. Renamed to DefaultBrowser.InfoBar.UserInteraction.
gab@chromium.org
The user ignored the make-default infobar (it was eventually dismissed along
with its associated web content without the user interacting with it).
Deprecated 2015/11. Renamed to DefaultBrowser.Infobar.UserInteraction. There
is no longer a distinction between interactive or not.
gab@chromium.org
In the make-default infobar, the user clicked a button making Chrome the
default.
Deprecated 2015/11. Renamed to DefaultBrowser.Infobar.UserInteraction. There
is no longer a distinction between interactive or not.
gab@chromium.org
Same as SetAsDefault, but in Win8+ (resulting in interactive UI instead of
automatic takeover). Successes == these reports minus reports for
DefaultBrowserWarning.SetAsDefaultUIFailed and some
DefaultBrowserWarning.DontSetAsDefault. TODO(gab): Improve reporting here.
Deprecated 2015/11. The same information is available as the value Failure
in DefaultBrowser.SetDefaultResult.
gab@chromium.org
The user dismissed the interactive SetAsDefaultUI without making an explicit
choice (or the UI failed to come up for another reason).
Deprecated 2016/03.
pmonette@chromium.org
The outcome of an attempt to set Chrome as the user's default client for a
protocol.
pmonette@chromium.org
The outcome of an attempt to set Chrome as the user's default client for a
protocol.
Deprecated March 2018
bmcquade@chromium.org
The actual delay added to main frame navigations by DelayNavigationThrottle.
Deprecated March 2018
bmcquade@chromium.org
The absolute delta between the specified and actual delays added to main
frame navigations by DelayNavigationThrottle.
Deprecated March 2018
bmcquade@chromium.org
The specified delay added to main frame navigations by
DelayNavigationThrottle.
mrefaat@chromium.org
The dimissal reason of the desktop to iOS promotion entry point.
DismissalReason will be prefixed by the entry point promotion name that the
user interacted with.
mrefaat@chromium.org
The type of the desktop to iOS promotion that was shown to the user. This
will be logged every time the user sees the desktop to iOS promotion.
mrefaat@chromium.org
[IOS] For users who sign-in on Chrome for iOS, log the type of the desktop
iOS promotions that was shown to the user. Only recorded if the user has
seen at least one desktop iOS promotion in the last 7 days and is signing
into chrome on iOS. The last promotion entry point that sent an SMS (if any)
is logged as DesktopIOSPromotion.SMSSent.IOSSigninReason; all other
promotions that the user has seen are logged as
DesktopIOSPromotion.NoSMS.IOSSigninReason.
justincohen@chromium.org
Whether getting the OAuth token was successful for a desktop to iOS
promotion query.
justincohen@chromium.org
HTTP Response code returned by the server when trying to fetch the OAuth
token for a desktop ios promotion query.
mrefaat@chromium.org
Whether the SMS service api called from the desktop to iOS promotion
returned a phone number or failed. This phone number is presented to the
user so they know that Chrome will send the SMS to this number.
mrefaat@chromium.org
Whether the SMS service api initiated SMS sending successfully from the
desktop to iOS promotion.
mrefaat@chromium.org
[IOS] The difference between the client time of triggering the SMS action on
a specific entry point promotion on desktop and client time of signing in
Chrome iOS app. This will only be logged if at least one promotion was shown
to the user on the last 7 days and if at least one SMS was sent. If multiple
SMSs were sent (at any time), it uses the time from the most recently sent
one. If the is negative due to bad clock on one of the clients it will be
logged as 0. SMSToSigninTime will be prefixed by the entry point promotion
name that was responsible for the SMS sending.
mrefaat@chromium.org
[IOS] For users who sign-in on Chrome for iOS, log which variation of the
desktop iOS promotions was shown to the user. The variation number is a
unique identifier that is set for each group on the DesktopIOSPromotion
study, and will be only recorded if the user has seen at least one desktop
iOS promotion in the last 7 days and is signing into Chrome on iOS. The last
variation that sent an SMS (if any) is logged as
DesktopIOSPromotion.SMSSent.VariationSigninReason. If no SMS was sent, then
the last variation the user has seen is logged as
DesktopIOSPromotion.NoSMS.VariationSigninReason.
alph@chromium.org
pfeldman@chromium.org
Specified DevTools action has been taken.
alph@chromium.org
pfeldman@chromium.org
Time to load Developer Tools when user clicks Inspect Element in the context
menu.
alph@chromium.org
pfeldman@chromium.org
Specified DevTools panel was shown.
alph@chromium.org
pfeldman@chromium.org
Specified DevTools setting was changed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the DiskSpace recovery step that runs
on recovery startups. The recovery step attempts to guarantee the DiskSpace
test, which checks that the disk space in the volume where the user data
directory normally lives is not dangerously low, would pass on the next
startup.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the JSONBookmarks recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
JSONBookmarks test, which makes sure that the JSON-encoded Bookmarks file is
properly formed, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the JSONLocalState recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
JSONLocalState test, which makes sure that the JSON-encoded Local State file
is properly formed, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the JSONPreferences recovery step
that runs on recovery startups. The recovery step attempts to guarantee the
JSONPreferences test, which makes sure that the JSON-encoded Preferences
file is properly formed, would pass on the next startup.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathDictionaries recovery step
that runs on recovery startups. The recovery step attempts to guarantee the
PathDictionaries test, which makes sure that the path to the Dictionaries
directory exists and has the right permissions, would pass on the next
startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathLocalState recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
PathLocalState test, which makes sure that the path to the Local State file
exists and has the right permissions, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathResources recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
PathResources test, which makes sure that the path to the Resources
directory exists and has the right permissions, would pass on the next
startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the PathUserData recovery step that
runs on recovery startups. The recovery step attempts to guarantee the
PathUserData test, which makes sure that the path to the User Data directory
exists and has the right permissions, would pass on the next startup.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityAppCache recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityAppCache test, which checks the integrity of
the App Cache database, would pass on the next startup.
Removed as of Jun 2014: we no longer have an archived database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityArchivedHistory
recovery step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityArchivedHistory test, which checks the
integrity of the Archived History database, would pass on the next startup.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityCookie recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityCookie test, which checks the integrity of the
Cookie database, would pass on the next startup.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker
recovery step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityDatabaseTracker test, which checks the
integrity of the Database Tracker database, would pass on the next startup.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityFavicons recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityFavicons test, which checks the integrity of
the Favicons database, would pass on the next startup.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityHistory recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityHistory test, which checks the integrity of the
History database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSCert recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityNSSCert test, which checks the integrity of the
NSS Certificate database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSKey recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityNSSKey test, which checks the integrity of the
NSS Key database, would pass on the next startup.
Deprecated 05/2016 in Issue 617226; has not been valid for many years.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityThumbnails
recovery step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityThumbnails test, which checks the integrity of
the Thumbnails database, would pass on the next startup.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityTopSites recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityTopSites test, which checks the integrity of
the TopSites database, would pass on the next startup.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityWebData recovery
step that runs on recovery startups. The recovery step attempts to
guarantee the SQLiteIntegrityWebData test, which checks the integrity of the
Web Data database, would pass on the next startup.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Count of the number of times diagnostics recovery is invoked or not, and how
it was invoked. A sample is added to this histogram once for each startup
of Chrome.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the DiskSpace test
that runs on recovery startups. The DiskSpace test checks that the disk
space in the volume where the user data directory normally lives is not
dangerously low.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the JSONBookmarks
test that runs on recovery startups. The JSONBookmarks test checks to make
sure that the JSON encoded bookmarks file is properly formed.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the JSONLocalState
test that runs on recovery startups. The JSONLocalState test checks to make
sure that the JSON encoded Local State file is properly formed.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the JSONPreferences
test that runs on recovery startups. The JSONPreferences test checks to
make sure that the Preferences file is properly formed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathDictionaries
test that runs on recovery startups. The PathDictionaries test checks makes
sure that the path to the Dictionaries folder exists and has the right
permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathLocalState
test that runs on recovery startups. The PathLocalState test checks makes
sure that the path to the Local State folder exists and has the right
permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathResources
test that runs on recovery startups. The PathResources test checks makes
sure that the path to the Resources folder exists and has the right
permissions.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of diagnostics for the PathUserData test
that runs on recovery startups. The PathUserData test checks makes sure that
the path to the User Data folder exists and has the right permissions.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityAppCache test that
runs on recovery startups. The test checks the integrity of the App Cache
database.
Removed as of Jun 2014: we no longer have an archived database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityArchivedHistory
test that runs on recovery startups. The test checks the integrity of the
Archived History database.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityCookie test that
runs on recovery startups. The test checks the integrity of the Cookie
database.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityDatabaseTracker
test that runs on recovery startups. The test checks the integrity of the
Database Tracker database.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityFavicons test that
runs on recovery startups. The test checks the integrity of the Favicons
database.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityHistory test that
runs on recovery startups. The test checks the integrity of the History
database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSCert test that
runs on recovery startups. The test checks the integrity of the NSS
Certificate database.
Please list the metric's owners. Add more owner tags as needed.
Shows the success and failure rates of the SQLiteIntegrityNSSKey test that
runs on recovery startups. The test checks the integrity of the NSS Key
database.
Deprecated 05/2016 in Issue 617226; has not been valid for many years.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityThumbnails test
that runs on recovery startups. The test checks the integrity of the
Thumbnails database.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityTopSites test that
runs on recovery startups. The test checks the integrity of the TopSites
database.
shess@chromium.org
Shows the success and failure rates of the SQLiteIntegrityWebData test that
runs on recovery startups. The test checks the integrity of the Web Data
database.
Please list the metric's owners. Add more owner tags as needed.
TBD - Not run automatically yet, so this is just a placeholder for future
metrics collection. Any samples collected here represent users running
diagnostics manually.
shess@chromium.org
Histogram comparing the various types of diagnostic test failures when
diagnostic tests are run. Note that some types of test failures cause the
rest of the tests to be skipped.
pdyson@chromium.org
Counts the number times dialog boxes are created using a particular parent
class.
pdyson@chromium.org
Counts the number times various types of dialog boxes are created.
Deprecated, use Dialog.DialogDelegate.Create.
pdyson@chromium.org
Counts the number times dialog boxes are created using DialogDelegate.
pdyson@chromium.org
How long dialog boxes are open, for dialog boxes created using the parent
class DialogDelegate. This will include bubbles that use
BubbleDialogDelegateView as a parent class, and dialogs that use
DialogDelegateView as a parent class. This is logged on delegate
destruction.
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)
kulshin@chromium.org
Records the error returned from CreateFontFace.
kulshin@chromium.org
Records how many font families are in the fallback cache.
kulshin@chromium.org
Measures the effectiveness of the font fallback proxy. This tracks if we
were able to find a suitable font to render the character, and whether an
IPC was necessary.
kulshin@chromium.org
The number of font families as seen by the font proxy in the renderer.
kulshin@chromium.org
The errors encountered by the DirectWrite font proxy while loading fonts.
kulshin@chromium.org
Records the error returned from GetSystemFontCollection.
kulshin@chromium.org
The number of last resort fallback fonts found on the system as seen by the
browser.
kulshin@chromium.org
The number of font files found for a last resort fallback font.
kulshin@chromium.org
The codepath that was used to load a font family. This is logged in the
browser every time a renderer attempts to load a font family, once per font
file.
kulshin@chromium.org
The outcome of attempting to load a font family in the renderer (success vs
failure and number of families). This is logged in the renderer once per
family that is loaded.
kulshin@chromium.org
The time taken to load a font family, excluding glyph data. This is logged
in the renderer once per family that is loaded.
kulshin@chromium.org
Errors, if any, encountered by the DirectWrite font proxy message filter.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Whether an extension has been wiped out.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
How many external extensions get wiped out as a result of the Sideload
Wipeout one-time initiative.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Whether any extension got wiped out as a result of the Sideload Wipeout
one-time initiative.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The user selection in the Sideload Wipeout bubble, grouped by the
UmaWipeoutHistogramOptions enum.
fdoray@chromium.org
Whether the machine was online when a discarded tab was reloaded.
fdoray@chromium.org
Number of tabs that are not pending load or discarded when an urgent discard
request is received.
fdoray@chromium.org
Time between two consecutive urgent discard requests. Urgent discards are
undesirable; it is better to reduce memory usage before the system is in a
bad state.
fdoray@chromium.org
Time between Chrome startup and the first urgent discard request. Urgent
discards are undesirable; it is better to reduce memory usage before the
system is in a bad state.
Deprecated as of 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
brandonsalmon@chromium.org
Records information about DiskBasedCertCache operations with respect to
certificate chain positions. Zero indicates that a certificate is root, one
indicates that it is the first intermediate certificate, etc.
Deprecated as of 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
brandonsalmon@chromium.org
Records the outcome of requests to retrieve certificates from the disk
cache.
Deprecated as of 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
brandonsalmon@chromium.org
Whether or not the leaf certificate of a certificate chain was successfuly
read from the disk cache.
Deprecated as of 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
brandonsalmon@chromium.org
Whether or not the leaf certificate of a certificate chain was successfully
written to the disk cache.
Deprecated as of 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
brandonsalmon@chromium.org
Measures the wall clock time spent reading a certificate chain. The starting
time is when the read command is issued, and the ending time is when all of
the certificates in the chain have been read into memory.
Deprecated as of 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
brandonsalmon@chromium.org
Measures the wall clock time spent writing a certificate chain to disk. The
starting time is when the write command is issued, and the ending time is
when all the certificates in the chain have been written to disk.
rvargas@chromium.org
The 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.
malaykeshav@chromium.org
The zoom percentage that the user has set on the internal display and is
actively using. This is emitted when the zoom factor has been updated in
display manager and has not been changed for a while.
weidongg@chromium.org
The number of displays connected to the device that are in software or
hardware mirror mode. This is emitted once when the normal or mixed mirror
mode is enabled through API call, or the display configuration changes (e.g.
adding or removing a display) when mirror mode is on.
weidongg@chromium.org
The types of mirror mode in which the displays connected to the device are
in. This is emitted once when the normal or mixed mirror mode is enabled
through API call, or the display configuration changes ( e.g. adding or
removing a display) when mirror mode is on.
afakhry@chromium.org
The mode in which the connected displays to the device are in. This is
emitted once when displays are added or removed, or when the user changes
the mode by e.g. enabling mirror or unified modes.
afakhry@chromium.org
The number of displays connected to the device when Unified Desktop mode is
on. This is emitted when Unified Desktop mode is turned on, or the displays
are added or removed while in Unified Mode.
Deprecated as of 6/2018.
mgersh@chromium.org
The attempt which completed after the job was already cancelled.
mgersh@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.
mgersh@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.
mgersh@chromium.org
The attempt that has not resolved the host successfully.
mgersh@chromium.org
The attempt that resolved the host first and the resolution was not
successful.
mgersh@chromium.org
The attempt that resolved the host first and the resolution was successful.
mgersh@chromium.org
The attempt that has resolved the host successfully.
mgersh@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.
Deprecated as of 6/2018.
mgersh@chromium.org
This histogram shows the time saved by having spawned an extra attempt, when
the first attempt didn't finish before retry attempt.
Deprecated as of 9/2017.
mgersh@chromium.org
The time left to expiration of an entry when it is removed while compacting
the HostCache.
Deprecated as of 9/2017.
mgersh@chromium.org
The time since expiration of an entry when it is removed while compacting
the HostCache.
Deprecated as of 9/2017.
mgersh@chromium.org
The time since expiration of an entry when it is removed on lookup.
Deprecated as of 9/2017.
mgersh@chromium.org
Error status when an empty address list was found in OnLookupComplete().
mgersh@chromium.org
The reason for erasing a DNS entry from the host cache.
mgersh@chromium.org
When erasing a stale (expired or old-network) DNS entry from the host cache,
how long past the expiration time it is.
mgersh@chromium.org
When erasing a stale (expired or old-network) DNS entry from the host cache
how many network changes happened between setting and erasing it.
mgersh@chromium.org
When erasing a stale (expired or old-network) DNS entry from the host cache
how many hits it received while stale.
mgersh@chromium.org
When erasing a valid DNS entry from the host cache, for how much longer it
would have remained valid.
mgersh@chromium.org
The outcome of looking up a DNS entry in the host cache.
mgersh@chromium.org
When looking up a stale DNS entry in the host cache, how long past the
expiration time it is.
mgersh@chromium.org
When looking up a stale DNS entry in the host cache, how many network
changes happened between setting it and looking it up.
mgersh@chromium.org
Number of HostCache entries persisted to disk, measured at restore time.
mgersh@chromium.org
Whether the persisted HostCache entries were restored successfully.
mgersh@chromium.org
The outcome of setting a DNS entry in the host cache.
mgersh@chromium.org
When updating a stale (expired or old-network) DNS entry in the host cache,
and both results are successful, how the address list differs between the
old and new entries.
mgersh@chromium.org
When updating a stale (expired or old-network) DNS entry in the host cache,
how long past the expiration time the old entry was.
mgersh@chromium.org
When updating a stale (expired or old-nework) DNS entry in the host cache,
how many network changes happened between setting the old entry and setting
the new entry.
mgersh@chromium.org
The number of hits received to an updated stale DNS entry in the host cache
while it was stale.
Deprecated as of 9/2017.
mgersh@chromium.org
When either a pre-resolution was not done recently enough to provide
benefit, or the corresponding pre-resolution is still pending, this
histogram shows the duration of time used to resolve a hostname as not
existing during a failed attempt to navigate to (GET) a URL. In newer
versions, if the hostname has never been found as a link during a page scan,
and it has a referring URL, then it is added to referrer list data structure
(hoping we'll do better next time).
Deprecated as of 9/2017.
mgersh@chromium.org
When either a pre-resolution was not done recently enough to provide
benefit, or the corresponding pre-resolution is still pending, this
histogram shows the duration of the duration of time used to resolve a
hostname to navigate to (GET) a URL. In newer versions, if the hostname has
never been found as a link during a page scan, and it has a referring URL,
then it is added to referrer list data structure (hoping we'll do better
next time).
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool).
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority HIGHEST when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority IDLE when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority LOW when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority LOWEST when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTime.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started (a getaddrinfo call was dispatched to the thread
pool). Includes only Jobs which had priority MEDIUM when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool).
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority HIGHEST when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority IDLE when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority LOW when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority LOWEST when started.
Deprecated as of 9/2017. Replaced by Net.DNS.JobQueueTimeAfterChange.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started (a getaddrinfo call was dispatched to the thread pool). Includes
only Jobs which had priority MEDIUM when started.
Deprecated as of 9/2017.
mgersh@chromium.org
The duration of time used (most recently) to pre-resolve a hostname, when
the prefetched resolution was apparently evicted from the cache. The
included samples only list pre-resolution times when the later
navigations/fetches took in excess of 15ms.
Deprecated as of 9/2017.
mgersh@chromium.org
The duration of time used (most recently) to pre-resolve a hostname, when
the prefetched resolution was apparently evicted from the cache. The
included samples only list pre-resolution times when the later
navigations/fetches took in excess of 15ms.
Deprecated as of 9/2017.
mgersh@chromium.org
Replaced by DNS.PrefetchFoundNameL.
Deprecated 2/2010, and replaced by DNS.PrefetchResolution
mgersh@chromium.org
The duration of time used by the DNS pre-resolving threads to resolve a host
name via the network. Any resolutions that are faster than 15ms are
considered to be local cache hits, not requiring network access, and are not
included in this histogram. This histogram is most useful for estimating the
typical cost of a name resolution, but it also estimates the total number of
network-based resolutions induced by this feature. Not all these
resolutions prove helpful (i.e., the user does not always actually visit the
resolved hostnames).
Deprecated as of 9/2017.
mgersh@chromium.org
Replaced by DNS.PrefetchNegativeHitL.
Deprecated as of 9/2017.
mgersh@chromium.org
The duration of time saved due to DNS pre-resolving in the "name not
found" case. Time "savings" shown in the histogram are
defined to be the difference between the DNS pre-resolution duration, and
the DNS resolution duration seen during a navigation. These cache hits only
list events where the DNS pre-resolve duration for a host was in excess of
15ms (i.e., the network was consulted), and the actual DNS resolution (when
a user attempted to navigate to a link with the same host name) took less
than 15ms (i.e., the network was not consulted), which means the gain was a
result of a "cache hit" in the OS cache. For some users with
LANs, all negative results (even when the DNS cache might otherwise help)
take about 2.5 seconds (due to timeouts for netbios broadcasts), and hence
no savings are possible (or shown) for such users in this category.
Deprecated as of 9/2017.
mgersh@chromium.org
Replaced by DNS.PrefetchPositiveHitL.
Deprecated as of 9/2017.
mgersh@chromium.org
The duration of time saved due to DNS pre-resolving in the "name was
found" case, and induced by either a page scan for a link or an omnibox
entry by the user. Time "savings" shown in the histogram are
defined to be the difference between the DNS pre-resolution duration, and
the DNS resolution duration seen during a navigation. These cache hits only
list events where the DNS pre-resolve duration for a host was in excess of
15ms (i.e., the network was consulted), and the actual DNS resolution (when
a user attempted to navigate to a link with the same host name) took less
than 15ms (i.e., the network was not consulted), which means the gain was a
result of a "cache hit" in the OS cache.
Deprecated as of 9/2017.
mgersh@chromium.org
The duration of time spent by a proposed resolution waiting in the queue to
be resolved. This number is in addition to any DNS resolution time that may
come later.
Deprecated as of 9/2017.
mgersh@chromium.org
The duration of time saved due to DNS pre-resolving in the "name was
found" case, and induced by predicting (using referrer lists) that a
resolution was needed. Time "savings" shown in the histogram are
defined to be the difference between the DNS pre-resolution duration, and
the DNS resolution duration seen during a navigation. These cache hits only
list events where the DNS pre-resolve duration for a host was in excess of
15ms (i.e., the network was consulted), and the actual DNS resolution (when
a user attempted to navigate to a link with the same host name) took less
than 15ms (i.e., the network was not consulted), which means the gain was a
result of a "cache hit" in the OS cache.
mgersh@chromium.org
The duration of time used by the DNS pre-resolving threads to resolve a host
name via the network. Any resolutions that are faster than 15ms are
considered to be local cache hits, not requiring network access, and are not
included in this histogram. This histogram is most useful for estimating the
typical cost of a name resolution, but it also estimates the total number of
network-based resolutions induced by this feature. Not all these
resolutions prove helpful (i.e., the user does not always actually visit the
resolved hostnames).
Deprecated as of 9/2017.
mgersh@chromium.org
When, due to congestion avoidance, a queued pre-resolution is abandoned
(recycled) without actually being resolved, this histograms records the age
in the queue of that entry. Only times over 2 seconds are recorded in this
histogram.
Deprecated as of 9/2017.
mgersh@chromium.org
When, due to congestion avoidance, a queued pre-resolution is abandoned
(recycled) without actually being resolved, this histograms records the age
in the queue of that entry. Only times less than or equal to 2 seconds are
recorded in this histogram.
Deprecated as of 9/2017. Replaced by Net.DNS.ResolveCategory.
mgersh@chromium.org
Counts of successes and failures of OS resolutions in various categories.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskFail.
mgersh@chromium.org
Duration of time taken in OS resolutions for actual navigations. Note that
cached OS resolutions may provide low (0ms?) resolution times.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskFail.
mgersh@chromium.org
Same as DNS.ResolveFail, but limited to pure IPv4 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskFail.
mgersh@chromium.org
Same as DNS.ResolveFail, but limited to pure IPv6 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskFail.
mgersh@chromium.org
Same as DNS.ResolveFail, but limited to IPv4/IPv6 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskFail.
mgersh@chromium.org
Duration of time taken in speculative OS resolutions. Note that cached OS
resolutions may provide low (0ms?) resolution times.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess.
mgersh@chromium.org
Duration of time taken in speculative OS resolution that succeeded. Note
that cached resolutions may provide low (0ms?) resolution times.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess.
mgersh@chromium.org
Duration of time taken in OS resolutions that succeeded and were requested
for actual navigations. Note that cached resolutions may provide low (0ms?)
resolution times.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess.
mgersh@chromium.org
Same as DNS.ResolveSuccess, but limited to pure IPv4 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess.
mgersh@chromium.org
Same as DNS.ResolveSuccess, but limited to pure IPv6 lookups.
Deprecated as of 9/2017. Replaced by Net.DNS.ProcTaskSuccess.
mgersh@chromium.org
Same as DNS.ResolveSuccess, but limited to IPv4/IPv6 lookups.
Deprecated as of 5/2013.
mgersh@chromium.org
Counts of hits and misses in the DNS cache and DNS jobs pool of wasted
HostResolverImpl::Jobs that could be avoided by always resolving using
AF_UNSPEC.
mgersh@chromium.org
When a DNS request made through StaleHostResolver returns, a stale cached
result was available, and the network responded before or exactly at the
stale delay, how much earlier it responded.
mgersh@chromium.org
When a DNS request made through StaleHostResolver returns, a stale cached
result was available, and the network responded after the stale delay, how
much later it responded.
mgersh@chromium.org
When a DNS request made through StaleHostResolver returns or is canceled,
the outcome of the request.
mgersh@chromium.org
When a DNS request made through StaleHostResolver has no stale cached result
available, the number of host cache entries that were restored from prefs.
mgersh@chromium.org
When a DNS request made through StaleHostResolver has no stale cached result
available, the number of entries in the host cache.
mgersh@chromium.org
When a DNS request made through StaleHostResolver had a stale cached result
and both the stale and network results were successful, the difference
between the old and new address lists.
Deprecated as of 9/2017. Replaced by Net.DNS.TotalTime.
mgersh@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Excludes speculative requests.
Deprecated as of 9/2017. Replaced by Net.DNS.TotalTime_speculative.
mgersh@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Speculative requests only.
Deprecated as of 9/2017.
mgersh@chromium.org
In some cases, such as when content arrives with embedded references to
other servers, the prefetch system can't (or doesn't) attempt to pre-resolve
the hostnames. As an example, a visit to www.cnn.com will fetch content
with references to about 12 additional hostnames, none of which are
currently anticipated. Such resolutions are termed "Unexpected
Resolutions," and the durations associated with those DNS resolutions
are shown below. Future features may attempt to learn (from prior
experience locally, or from server provided hints), what secondary hostname
resolutions should be done when a primary resolution (or navigation) takes
place. This histogram shows what the potential savings are that
"remain on the table" until we employ some of these more advanced
features.
Deprecated as of 9/2017.
mgersh@chromium.org
In some cases, such as when content arrives with embedded references to
other servers, or when a page (such as one in SSL) preclude scanning and
prefetching, the prefetch system can't (or doesn't) attempt to pre-resolve
the hostnames. As an example, a visit to www.cnn.com will fetch content
with references to about 12 additional hostnames, none of which might be
anticipated. Similarly, clicking on a link in an SSL page won't be
anticipated (since scanning in not allowed by default). Such resolutions are
termed "Unexpected Resolutions," and the durations associated with
those navigation induced DNS resolutions are shown below. If a referring
URL is available for the navigation, the relationship to the referring URL
was recorded, and future navigations to the referring hostname would have
induced a pre-resolution of hostname that caused an entry below. Such any
entry may facilitate future listing in the ReferredPositiveHit histogram.
mgersh@chromium.org
Status of DNS probe updates sent to a DNS error page.
Renamed 7/2013 to DnsProbe.ProbeDuration.
mgersh@chromium.org
Time between starting and finishing DNS probe.
Removed 7/2013.
mgersh@chromium.org
Time between starting and finishing DNS probe when NCN says we're offline.
Removed 7/2013.
mgersh@chromium.org
Result of DNS probes sent by the probe service when NCN says we're offline.
Removed 7/2013.
mgersh@chromium.org
Time between starting and finishing DNS probe when NCN says we're online.
Removed 7/2013.
mgersh@chromium.org
Result of DNS probes sent by the probe service when NCN says we're online.
Renamed 7/2013 to DnsProbe.ProbeResult. (Also switched to the full
DnsProbe.ProbeStatus enum.)
mgersh@chromium.org
Result of DNS probes sent by the probe service.
Removed 7/2013.
mgersh@chromium.org
Elapsed time of DNS probes that return PROBE_BAD_CONFIG.
Removed 7/2013.
mgersh@chromium.org
Whether the only nameserver in the system DNS config was 127.0.0.1 when the
probe result was BAD_CONFIG.
Removed 7/2013.
mgersh@chromium.org
The result of the system probe job when the overall probe result was
BAD_CONFIG.
Removed 7/2013.
mgersh@chromium.org
The number of nameservers in the system DNS config when the probe result was
BAD_CONFIG.
Removed 7/2013.
mgersh@chromium.org
Elapsed time of DNS probes that return PROBE_NO_INTERNET.
Removed 7/2013.
mgersh@chromium.org
Elapsed time of DNS probes that return PROBE_NXDOMAIN.
Removed 7/2013.
mgersh@chromium.org
Elapsed time of DNS probes that return PROBE_UNKNOWN.
mgersh@chromium.org
Time between starting and finishing DNS probe.
mgersh@chromium.org
Result of DNS probes sent by the probe service.
panicker@chromium.org
Records result of invoking beforeunload handler, that determines whether to
show the dialog.
hajimehoshi@chromium.org
keishi@chromium.org
Records the GC count between the time when the document is shut down and and
the time when the document is actually destroyed. This only counts documents
that are destroyed before the process dies.
hajimehoshi@chromium.org
keishi@chromium.org
Records documents that survives some GCs after the document is shut down.
Removed 9/2016.
mariakhomenko@chromium.org
Recorded only for Android. Records on every metrics upload whether document
mode is enabled.
panicker@chromium.org
Microseconds spent in beforeunload.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
panicker@chromium.org
fmeawad@chromium.org
Microseconds spent in onfreeze.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
panicker@chromium.org
Microseconds spent in pagehide.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
panicker@chromium.org
Microseconds spent in vibilitychange (hidden).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
panicker@chromium.org
fmeawad@chromium.org
Microseconds spent in onresume.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
panicker@chromium.org
Microseconds spent in unload.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
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.
Removed January 2018.
mattm@chromium.org
Number of certs loaded from domain bound cert database.
nharper@chromium.org
The status of loading the Channel ID database from disk. This histogram
records why the database failed to load, or that it loaded successfully.
Removed January 2018.
mattm@chromium.org
Time spent loading domain bound cert database.
Removed 4/2017.
mattm@chromium.org
The size, on disk, of the domain bound cert database as it is being loaded.
nharper@chromium.org
The version number of the Channel ID database (before any migrations are
run).
Removed 4/2017.
mattm@chromium.org
Time spent generating a domain bound cert.
Removed 4/2017.
mattm@chromium.org
Combined time for GetDomainBoundCert retrieval (both synchronous and
asynchronous).
Removed 4/2017.
mattm@chromium.org
Time for asynchronous retrieval (from the GetDomainBoundCert call until
completion callback is called).
Removed 4/2017.
mattm@chromium.org
Time for synchronous GetDomainBoundCert cert retrieval.
Removed January 2018.
mattm@chromium.org
Result of GetDomainBoundCert function.
mattm@chromium.org
Whether the domain-bound certs sqlite database was killed succesfully when
an unrecoverable error was detected.
Removed January 2018.
mattm@chromium.org
Counts of SSL client sockets broken down by support for Domain Bound
Certificates TLS extension. Counts only connections with full handshakes,
resumed sessions are not counted.
Removed 4/2017.
mattm@chromium.org
Longest time spent by requests waiting for load of domain bound cert
database.
Removed 4/2017.
mattm@chromium.org
Number of requests that waited for load of domain bound cert database.
qfiard@google.com
The distribution over daily active users of Google Search of the ratio of
Google searches in the past day that were issued by the user on a Google
domain that is not the primary one used by the user over the same time
period.
qfiard@google.com
The distribution over daily active users of Google Search of the ratio of
Google searches in the past 30 days that were issued by the user on a Google
domain that is not the primary one used by the user over the same time
period.
qfiard@google.com
The distribution over daily active users of Google Search of the ratio of
Google searches in the past week that were issued by the user on a Google
domain that is not the primary one used by the user over the same time
period.
qfiard@google.com
The distribution over daily active users of Google Search of the ratio of
Google searches in the past two weeks that were issued by the user on a
Google domain that is not the primary one used by the user over the same
time period.
Removed November 2017.
juliatuttle@chromium.org
The time between successive Domain Reliability beacons being queued in the
same context. (Can be arbitrarily long if no beacons are queued in a while.)
Removed November 2017.
juliatuttle@chromium.org
The time between successive Domain Reliability beacons being queued across
all contexts. (Can be arbitrarily long if no beacons are queued in a while.)
Removed November 2017.
juliatuttle@chromium.org
Whether a beacon added to a Domain Reliability context was saved to be
uploaded to the collector.
Removed November 2017.
juliatuttle@chromium.org
Whether adding a beacon to a Domain Reliability context caused it to evict
an older beacon to stay within memory limits.
Removed November 2017.
juliatuttle@chromium.org
The Chrome error code included in a beacon saved to be uploaded to the
collector.
Removed November 2017.
juliatuttle@chromium.org
The Chrome error code included in a beacon with a non-empty server_ip field
saved to be uploaded to the collector.
Removed November 2017.
juliatuttle@chromium.org
The upload depth included in a beacon saved to be uploaded to the collector.
(Zero means the beacon was not about a report upload; n+1 means the beacon
was about a report with upload depth n.)
Removed November 2017.
juliatuttle@chromium.org
When Domain Reliability receives a valid NEL configuration header for an
origin with Domain Reliability active, whether or not it needed to recreate
the origin's context to apply a changed config.
Removed November 2017.
juliatuttle@chromium.org
The index of the collector that a Domain Reliability upload was sent to.
(Later collectors are only used when earlier collectors have failed.)
Removed November 2017.
juliatuttle@chromium.org
After an upload to a collector finishes (successfully or not), the delay
before the scheduler can send another upload to that collector. (If recent
uploads were successful, this will be 0; if not, it will be based on the
BackoffEntry and any Retry-After header received.)
juliatuttle@chromium.org
The elapsed time between starting and finishing a Domain Reliability upload.
Deprecated 11/2014; see UploadCollectorIndex
juliatuttle@chromium.org
Whether a Domain Reliability upload was sent to a collector other than the
first one listed in the config. (This only happens when an upload to the
first collector fails.)
Removed November 2017.
juliatuttle@chromium.org
The time between successive Domain Reliability uploads being started in the
same context. (Can be arbitrarily long if no beacons are reported in a
while.)
Removed November 2017.
juliatuttle@chromium.org
The time between successive Domain Reliability uploads being started across
all contexts. (Can be arbitrarily long if no beacons are reported in a
while.)
juliatuttle@chromium.org
The time from the first beacon in a Domain Reliability upload being recorded
and that upload completing successfully. (Note that if some beacons are
never uploaded successfully, they will not feature in this histogram at
all.)
juliatuttle@chromium.org
The network error code (or OK if none) returned by the URLFetcher when a
Domain Reliability report is uploaded.
juliatuttle@chromium.org
The HTTP response code returned by the Domain Reliability collector when a
report is uploaded.
juliatuttle@chromium.org
Whether a Domain Reliability upload succeeded.
UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017.
mdjones@chromium.org
Records if the close button was used before or after opening and viewing
Reader Mode content.
wychen@chromium.org
The reason to reject distillability at PageDistillableAfterParsing time.
wychen@chromium.org
Score of distillability from AdaBoost model, non-mobile-friendly only. The
score shown here is multiplied by 100.
wychen@chromium.org
Score of distillability from AdaBoost model, non-mobile-friendly only. The
score shown here is multiplied by 100.
nyquist@chromium.org
Whether the perceived quality of the distillation of a web page was good.
mdjones@chromium.org
"Used" is recorded when the user clicks the infobar to enter
Reader Mode. "Not Used" is recorded when the user clicks the close
button. If there's no user action, nothing is recorded.
wychen@chromium.org
Score of long article from AdaBoost model, distillable and
non-mobile-friendly only. The score shown here is multiplied by 100.
wychen@chromium.org
Score of long article from AdaBoost model, distillable and
non-mobile-friendly only. The score shown here is multiplied by 100.
PageDistillableAfterLoading and PageDistillableAfterParsing provide more
details since 02/2016.
cjhopman@chromium.org
Records the "Distillable Type" (not distillable, mobile-friendly
distillable, non-mobile-friendly distillable, etc) for each analyzed page.
wychen@chromium.org
Records the "Distillable Type" (mobile-friendly not distillable,
mobile-friendly distillable, non-mobile-friendly not distillable,
non-mobile-friendly distillable) for each analyzed page after loading.
wychen@chromium.org
Records the "Distillable Type" (mobile-friendly not distillable,
mobile-friendly distillable, non-mobile-friendly not distillable,
non-mobile-friendly distillable) for each analyzed page after parsing.
Not collected anymore.
cjhopman@chromium.org
Records the "Distillable Type" (not distillable, mobile-friendly
distillable, non-mobile-friendly distillable, etc) for each distilled page.
kuan@chromium.org
Records whether a page has distilled data.
mdjones@chromium.org
Records if the panel became visible at any point after a page was navigated.
mdjones@chromium.org
Records the number of words in a distilled page. This only records the first
page of a multi-page article.
nyquist@chromium.org
Records the number of words in a distilled page. For articles with multiple
pages, each page is counted separately.
yfriedman@chromium.org
Time spent in DomDistiller's identification of text content.
yfriedman@chromium.org
Complete time spent in DomDistiller's processing of a page.
wychen@chromium.org
Time spent in DistillPageImpl(), mostly ExecuteJavaScript(), including
compilation and execution.
yfriedman@chromium.org
Time spent in creating DomDistiller's internal representation of the HTML
document.
yfriedman@chromium.org
Time spent in DomDistiller's final processing of article content/formatting.
yfriedman@chromium.org
Time spent in DomDistiller's processing of article metadata.
wychen@chromium.org
Time spent in ExecuteJavaScript() in DomDistiller. It includes JavaScript
code transmission through IPC, parsing, compilation, execution, and
returning the JSON back through IPC.
UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017.
wychen@chromium.org
Records the time from a swipe-up gesture on ReaderModePanel to the first
paint of the empty template.
wychen@chromium.org
Records the time from the Reader Mode panel opening to the viewer loaded.
mdjones@chromium.org
Records the amount of time a user spent on a Reader Mode Page.
UI rewrite to be an InfoBar makes this metric irrelevant as of 05/2017.
mdjones@chromium.org
Records the amount of time between the Reader Mode panel opening and it
closing or returning to the peeking state.
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().
Removed from code 2017-08.
treib@chromium.org
Outcome of downloading the Doodle config.
Removed from code 2017-08.
treib@chromium.org
The time it took to download the Doodle config. Recorded only if the
download succeeded and the received data was parsed without errors.
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.
Deprecated January 2017.
asanka@chromium.org
The actual bandwidth (per read) of a download.
asanka@chromium.org
Downloads extension API function calls.
asanka@chromium.org
Time taken to invoke IAttachmentExecute::Save() excluding the time taken to
instantiate CLSID_AttachmentServices.
asanka@chromium.org
Result of invoking (or attempting to invoke) Windows Attachment Services API
via IAttachmentExecute::Save().
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).
Deprecated January 2017.
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.
Deprecated April 2017.
qinmin@chromium.org
For parallel downloading, average disk bandwidth seen when only 1 stream is
actively downloading the content. Other streams may have already finished,
or have not been created yet. If a download was ever paused, this is not
recorded.
Deprecated April 2017.
qinmin@chromium.org
For parallel downloading, average disk bandwidth seen when parallel streams
are downloading the content. If a download was ever paused, this is not
recorded.
Deprecated 1/2017.
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).
qinmin@chromium.org
File size calculated from the content-length header of successfully
completed Parallelizable downloads.
Deprecated 03/2017, and replaced by Download.Start.ContentType.
asanka@chromium.org
Content types that are downloaded.
jming@chromium.org
xingliu@chromium.org
Types of audio files that are downloaded.
asanka@chromium.org
Types of images that are downloaded.
jming@chromium.org
xingliu@chromium.org
Types of text files that are downloaded.
jming@chromium.org
xingliu@chromium.org
Types of video files that are downloaded.
xingliu@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.
jialiul@chromium.org
nparker@chromium.org
Indicates why a download is marked as DANGEROUS_FILE. Grouped by reason,
such as Safe Browsing (SB) service is not available, and SB returns UNKOWN
or SAFE verdict. The sum of all reasons should roughly equal to the
DANGEROUS_FILE bucket count in Download.DownloadWarningShown.
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
Time taken to create a single download in the history DB.
xingliu@chromium.org
Records whether the download database is available when database startup
completes, before starting any pending downloads. If the database is
available, it will provide the next download id. Or no download history will
be persisted.
asanka@chromium.org
Time taken to query all downloads from history DB.
asanka@chromium.org
Time taken to update a single download in the history DB.
qinmin@chromium.org
Whether a download can be found for a download slice in the DB. This
histogram is recorded for each download slice row every time the database is
loaded.
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.
Deprecated 2/2017
asanka@chromium.org
How long it took to delete a batch of downloads from history.
Deprecated 2/2017
asanka@chromium.org
How long it took to delete some downloads from history, per download.
xingliu@chromium.org
How long users keep downloaded audio files on disk. Recorded when the
downloaded file is deleted.
xingliu@chromium.org
How long users keep downloaded video files on disk. Recorded when the
downloaded file is deleted.
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.
Deprecated 1/2017.
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
jialiul@chromium.org
Records when user is shown the download danger prompt while attempting to
recover a blocked download from chrome://downloads, grouped by the type of
file.
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.
qinmin@chromium.org
Estimated time saved on a download when parallel downloading is enabled. To
estimate this, the time spent on a download is classified into two
categories. The fist category has only one stream active, while other
streams are either finished, not started, or failed. And the second category
has multiple streams active. By calculating the average bandwidth during the
first category, a rough estimation on the time it will save is obtained by
assuming all the bytes downloaded during the second category are downloaded
by only one stream. If a download is ever paused, this is not recorded.
qinmin@chromium.org
Similar to Download.EstimatedTimeSavedWithParallelDownload, but this
estimates the time wasted on a download when parallel downloading is
enabled.
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.
xingliu@chromium.org
The count of HTTP Response codes for download requests.
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 total number of bytes minus the received number of bytes at the time
that a download is interrupted. This is only triggered when the total
content size is known before any bytes are transferred, such as when a
Content-Length header is supplied.
xingliu@chromium.org
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 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
True if the size of an interrupted download is unknown, false if it is
known.
bdibello@chromium.org
The action that a user takes on a file after it has been successfully
downloaded on iOS.
mrefaat@chromium.org
Positive net error codes that happens in the case of download content fetch
failure.
stkhapugin@chromium.org
eugenebut@chromium.org
stuartmorgan@chromium.org
HTTP status code returned when file download completes on iOS.
eugenebut@chromium.org
Logged when the download is completed (successfully or not) or in-progress
download was cancelled because of the app termination. This histogram
includes information whether the download was successful and whether or not
the download task was running while the app was active.
bdibello@chromium.org
Result when a user attempts to download a file on iOS.
eugenebut@chromium.org
Logged when the download was successfully completed. Bool value indicates
whether or not Install Google Drive promo was shown to the user.
eugenebut@chromium.org
MIME type of a download response. Logged when the download UI was offered by
the browser to the user.
gchatz@chromium.org
Result when a user attempts to download a PassKit file on iOS.
eugenebut@chromium.org
The user discarded in-progress download and replaced with the new one. Only
recorded after the user interacts with a dialog offering the choice between
replacing an in-progress download versus downloading separately to a new
filename.
eugenebut@chromium.org
Result of an attempt to present Add Passes dialog on iOS.
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 core page transition type for navigation initiated downloads. Not
recorded for programmatic downloads. This metric is recorded when the
response headers were received and processed for a download. The number of
samples here should correspond to Download.Counts[8] (Started) -
(programmatic downloads that don't have a page transition type).
xingliu@chromium.org
Records the ratio of parallel streams bandwidth to single stream bandwidth
in parallel download.
xingliu@chromium.org
When parallel downloading feature is enabled, a download may be created as
parallel download or fall back to normal download based on various factors.
Records the total number of parallel and non-parallel downloads created when
parallel downloading feature is enabled. Also records the reason why a
parallel download falls back to normal download. The reasons are not
mutually exclusive.
qinmin@chromium.org
Records the remaining download time when building parallel requests.
xingliu@chromium.org
Records the ratio of the actual total time of the download to the total time
without parallel streams. The total time without parallel streams is
calculated as the size of the file divided by the single stream bandwidth.
xingliu@chromium.org
Records if the byte stream reader of a subsequent request is successfully
added to the download sink.
xingliu@chromium.org
The total number of requests sent for a parallel download, including the
initial request.
xingliu@chromium.org
The download time for a parallelizable download.
xingliu@chromium.org
The download size of a parallelizable download.
qinmin@chromium.org
For parallelizable download, average disk bandwidth seen for different
settings. If a download was ever paused, this is not recorded.
xingliu@chromium.org
The download path generation behavior which happens before download path
validation in download target determination process.
xingliu@chromium.org
The download path validation result before the final download target is
determined.
Deprecated January 2017.
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.
dbeam@chromium.org
Records the time taken to load the downloads Web UI and render (at least) a
screen full of items. This is roughly equivalent to 'time to first
meaningful paint' for the downloads page.
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.
xingliu@chromium.org
Records a failed database operation.
xingliu@chromium.org
Records a successful database operation.
xingliu@chromium.org
The total number of database records used by download service, and the
number of records in each entry state.
xingliu@chromium.org
The interrupt reason for failed downloads in download service.
dtrainor@chromium.org
An action the download service took on an active download.
dtrainor@chromium.org
Records how many resumptions have taken place at the time of resumption for
a download in the Download Service. This differs from
Download.Service.Entry.RetryCount, which records restarts.
dtrainor@chromium.org
Records how many attempts have taken place at the time of a retry for a
download in the Download Service. This differs from
Download.Service.Entry.ResumptionCount, which records resumptions not
complete restarts.
shaktisahu@chromium.org
The number of times download service tried to delete the download file
before successfully deleting it.
xingliu@chromium.org
The number of files that have been deleted by external application or the
user, when performing clean up tasks in download service.
xingliu@chromium.org
The number of failed file deletion attempts, when performing clean up tasks
in download service.
xingliu@chromium.org
The number of files successfully deleted, when performing clean up tasks in
download service.
xingliu@chromium.org
The error code when failed to create the download directory.
xingliu@chromium.org
The percentage of disk space used by download service files. Recorded during
initialization of the file monitor.
xingliu@chromium.org
The percentage of free disk space to total disk space. Recorded during
initialization of the file monitor.
xingliu@chromium.org
The lifestime of a download file, which begins from the download completion
to the file being deleted by the clean up task.
xingliu@chromium.org
Records if the final file path has been renamed by low level download
library after the download is successfully completed.
xingliu@chromium.org
The file size of completed download, including failed downloads.
xingliu@chromium.org
The time to complete the download in download service.
xingliu@chromium.org
The completion type for downloads in download service.
shaktisahu@chromium.org
The reason for suspending a download right after the upload data is received
from the client. Every pause will result in two entries in the histogram:
ANY and a more specific reason.
shaktisahu@chromium.org
The reason for pausing an in-progress download. Every pause will result in
two entries in the histogram: ANY and a more specific reason.
xingliu@chromium.org
The state that the entry transitions to when recovery operation happens.
xingliu@chromium.org
The battery requirement of the download request.
xingliu@chromium.org
Records the API calls on download service.
xingliu@chromium.org
The network requirement of the download request.
xingliu@chromium.org
The priority of the download request.
xingliu@chromium.org
The start response of download attempts.
xingliu@chromium.org
The start result of download attempts.
xingliu@chromium.org
The start up result of the download service.
xingliu@chromium.org
The platform background tasks used by download service will invoke native
functions after being scheduled. The tasks may be aborted or canceled. This
metric records the status of background tasks when native functions are
invoked.
shaktisahu@chromium.org
Records if the entry has been deleted for some reason while we are waiting
for the client to respond with the upload data.
shaktisahu@chromium.org
The download service uses a single code path for both downloading and
uploading data. This metric records whether a given request includes upload
data. It is recorded upon starting a download or upload, immediately after
the client indicates whether the request includes upload data.
sdy@chromium.org
Events related to dragging a completed download from the shelf, which
represents dragging a reference to the downloaded file.
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.
Deprecated 1/2018, integrated into Download.Counts.DOWNLOAD_TRIGGERED_COUNT
xingliu@chromium.org
The initiation source (if initiated within the content layer of chrome) for
a download.
xingliu@chromium.org
The initiation source (if initiated within the above-content layer of
chrome) for a download.
shaktisahu@chromium.org
Content types of the downloads.
cthomp@chromium.org
estark@chromium.org
The content type of a download, for downloads where the final resolved URL
or any redirect before the final URL are insecure. To normalize these
numbers, divide the counts by the counts of Download.Start.ContentType (to
measure the proportion for each content type downloaded insecurely) or by
the sum of Download.Start.ContentType (to measure the proportion of a
particular insecure download content type over all downloads).
shaktisahu@chromium.org
Content types of the downloads that are started in non-incognito profile.
cthomp@chromium.org
estark@chromium.org
The content type of a download, for downloads where the final resolved URL
and all redirects before the final URL are secure. To normalize these
numbers, divide the counts by the counts of Download.Start.ContentType (to
measure the proportion for each content type downloaded securely) or by the
sum of Download.Start.ContentType (to measure the proportion of a particular
secure download content type over all downloads).
jialiul@chromium.org
The connection security state of a download, indicating whether its final
resolved url and the redirects before final url are secure.
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.
Deprecated 1/2017
asanka@chromium.org
The number of iterations for the write loop in BaseFile::AppendDataTofile().
Deprecated 1/2017
asanka@chromium.org
The write size for calls to BaseFile::AppendDataTofile().
Deprecated 2/2018
digit@chromium.org
The time to succesfully download and install the DownloadableStrings
component on Android.
Deprecated 2/2018
digit@chromium.org
The mobile country code (MCC) of the device's SIM card, if available (in the
[200..999] range), or 0 for "undetermined". This is collected on
Chrome startup. For devices with several SIM cards, this only reports the
code of the SIM card in use during startup.
Deprecated 2/2018
digit@chromium.org
The status code returned after trying to install and update the
DownloadableStrings component.
Deprecated 2/2018
digit@chromium.org
The timeout reported by the component updater when trying to install the
DownloadableStrings component fails with a specific error.
hirono@chromium.org
Respose code of batch upload request.
Deprecated 8/2013.
joshwoodward@google.com
Status of drive cache metadata database open.
weifangsun@chromium.org
sashab@chromium.org
Time spent to load the delta change list information from the server.
weifangsun@chromium.org
sashab@chromium.org
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.
mtomasz@chromium.org
Error codes returned by the Drive API for files list requests executed via
the FilesListRequestRunner class.
mtomasz@chromium.org
Maximum number of results for each files list request using the Drive API.
weifangsun@chromium.org
sashab@chromium.org
Time spent to load the entire file system information from the server
Deperecated 12/2013 since it did not record meaningful information.
Drive.DirectoryFeedLoadTime should be checked for measuring the time until
the user sees the first response of file lists.
joshwoodward@google.com
Time spent to load the initial part of the file system information from the
server
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.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
hirono@chromium.org
Total file count contained in a drive batch upload request.
hirono@chromium.org
Total file size contained in a drive batch upload request.
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.
hirono@chromium.org
Upload protocol for each file. e.g. Batch upload including 5 files triggers
the metric 5 times.
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.
andrescj@chromium.org
mcasas@chromium.org
Whether an EDID blob was detected. This UMA is recorded whenever we attempt
to parse the EDID from a display.
andrescj@chromium.org
mcasas@chromium.org
When attempting to get the color space from an EDID blob, whether the sanity
checks passed (and if not, which check failed). This UMA is recorded
whenever the color space is extracted from an EDID blob.
Deprecated as of 03/2018.
joshwoodward@google.com
isherman@chromium.org
When Easy Unlock attempts to authenticate the secure connection between a
Chromebook (or other Chrome device) and an Android phone, whether the
authentication succeeded.
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 their 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 their 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.
Deprecated as of 02/2017.
bcwhite@chromium.org
Reports the type of Bluetooth adapter present in the device.
Statistics about what Bluetooth capabilities are available will determine
how the EasyUnlock feature gets developed and deployed across platforms.
This value is logged only once during the lifetime of the Chrome process,
shortly after it starts up. If a Bluetooth USB adapter is inserted after
that point, the change will not be registered until Chrome restarts.
joshwoodward@google.com
tbarzic@chromium.org
Button clicked in EasyUnlock app during setup process.
Deprecated 02/2015. Replaced by EasyUnlock.Setup.PromoNotificationEvent.
joshwoodward@google.com
tbarzic@chromium.org
Tracks events related to notifications used by EasyUnlock feature. For
example a specific EasyUnlock notification being shown or clicked.
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 they
try to complete the setup flow with a device in airplane mode, and then try
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 they
try to complete the setup flow with a device in airplane mode, and then try
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.
jhawkins@chromium.org
Records events at each step of the Setup process, when the Setup flow is
initiated without the promotion notification.
jhawkins@chromium.org
Records events at each step of the Setup process, when the Setup flow is
initiated via the promotion notification.
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.
Deprecated as of 03/2018.
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.
Deprecated 03/2016; replaced by
EmbeddedWorkerInstance.Start.SendStartWorker_ExistingProcess and
EmbeddedWorkerInstance.Start.TimeToURLJob_ExistingProcess.
ksakamoto@chromium.org
The time taken to allocate a process to start the EmbeddedWorkerInstance.
Recorded when an existing process was used.
Deprecated 03/2016; replaced by
EmbeddedWorkerInstance.Start.SendStartWorker_NewProcess and
EmbeddedWorkerInstance.Start.TimeToURLJob_NewProcess.
ksakamoto@chromium.org
The time taken to allocate a process to start the EmbeddedWorkerInstance.
Recorded when a new process was created.
Deprecated as of 05/2015. Replaced by
EmbeddedWorkerInstance.NewProcessAllocation and
EmbeddedWorkerInstance.ExistingProcessAllocation.
horo@chromium.org
The time taken to allocate a process to start the EmbeddedWorkerInstance.
ksakamoto@chromium.org
Whether a new renderer process was created for the EmbeddedWorkerInstance or
existing one was used. Only recorded for installed workers.
Deprecated as of 03/2016. Replaced by
EmbeddedWorkerInstance.Start.TimeToEvaluateScript.
horo@chromium.org
The time taken to evaluate the script to start the EmbeddedWorkerInstance.
Deprecated as of 03/2016. Replaced by
EmbeddedWorkerInstance.Start.TimeToLoad_Network.
horo@chromium.org
The time taken to load the script file for the EmbeddedWorkerInstance with
network access.
Deprecated as of 03/2016. Replaced by
EmbeddedWorkerInstance.Start.TimeToLoad_HttpCache and
EmbeddedWorkerInstance.Start.TimeToLoad_InstalledScript.
horo@chromium.org
The time taken to load the script file for the EmbeddedWorkerInstance
without network access.
Removed June 2018 (M69). Replaced with
ServiceWorker.StartTiming.SentStartWorkerToReceivedStartWorker.
falken@chromium.org
The time between the browser sending a "start a service worker"
message to the renderer, and the renderer receiving it. This may include
renderer startup time. Only recorded if the high-resolution system clock was
used and deemed consistent across proceses, and the time was non-negative
(see EmbeddedWorkerInstance.Start.StartMessageLatency.Type). Only recorded
for installed workers. Recorded upon successful startup.
Removed June 2018 (M69). Replaced with
ServiceWorker.StartTiming.ClockConsistency.
falken@chromium.org
See EmbeddedWorkerInstance.Start.StartMessageLatency. Describes the outcome
of taking the measurement and whether StartMessageLatency was recorded.
Removed July 2018 (M69). Replaced with
ServiceWorker.StartTiming.ScriptEvaluationStartToScriptEvaluationEnd.
falken@chromium.org
The time taken for initial evaluation of the service worker script.
Specifically, the time between ACK from the renderer that the thread started
and ACK that the script evaluation finished. Only recorded for installed
workers.
Removed June 2018 (M69). This depended on the URLRequestJob code path, which
won't be taken with S13nServiceWorker/NetworkService. If we want this again,
it can be logged from ServiceWorkerScriptLoader or in Blink directly using
Resource Timing.
falken@chromium.org
The time taken to load a new (not installed) service worker, when it came
from the HTTP cache.
Removed June 2018 (M69). This path is no longer taken since service worker
installed script manager is used for installed scripts.
falken@chromium.org
The time taken to load an installed service worker.
Removed June 2018 (M69), see note in
EmbeddedWorkerInstance.Start.TimeToLoad.HttpCache.
falken@chromium.org
The time taken to load a new (not installed) service worker, when it came
from the network.
Removed July 2018 (M69). Replaced with
ServiceWorker.StartTiming.StartToSentStartWorker.
falken@chromium.org
The time taken between deciding to start a worker and sending the start
worker IPC. Only recorded for installed workers.
Removed July 2018 (M69). Replaced with
ServiceWorker.StartTiming.ReceivedStartWorkerToScriptEvaluationStart.
falken@chromium.org
The time taken to start the service worker thread. Specifically, the time
between ACK from the renderer that load finished and ACK that the thread
started. Does not include script evaluation time. Only recorded for
installed workers.
Removed June 2018 (M69). This path is no longer taken since service worker
installed script manager is used for installed scripts.
falken@chromium.org
The round-trip time between asking the renderer process to start a worker
and receiving the corresponding resource request. Only recorded for
installed workers.
Removed June 2018 (M69).
falken@chromium.org
Indicates if Blink was not initialized by the time the browser sent a
"start a service worker" message to the renderer. If this is true,
receiving the message had to wait until after Blink initialization finished.
Blink initialization is considered the time RenderThreadImpl::Init sets up
the Mojo interface for receiving the "start a service worker"
message. Only recorded for installed workers. Recorded upon successful
startup.
Removed June 2018 (M69).
falken@chromium.org
Recorded when EmbeddedWorkerInstance.Start.WaitedForRendererSetup is true.
The time between when the "start a service worker" was sent by the
browser, and Blink initialization finishing. The start time is recorded by
the browser process, and the end time by the renderer process, so process
clock skew could possibly affect the result.
Removed 4/2016 after we no longer show "all bookamrks" in bookmark
manager.
ianwen@chromium.org
Number of bookmarks the user has. Android only.
Removed 3/2015 along with the enhanced bookmarks sync experiment.
noyau@chromium.org
yefim@chromium.org
Captures the state the enhanced bookmark experiment is in. Recorded on
startup. To be removed once the enhanced bookmark experiment is finished.
see crbug/323423.
Removed 9/2015 after list view became the only view mode.
ianwen@chromium.org
Record which Enhanced Bookmark UI mode users are in. This will be recorded
everytime the user opens the bookmark manager UI.
rsorokin@chromium.org
The way device is joined to the Active Directory domain. This will be
recorded during successful enterprise enrollment and domain join.
aberent@chromium.org
Android Only - Time to load the App Restrictions from the O.S..
aberent@chromium.org
Android Only - Whether Chrome was able to read and decode the
AppRestrictions policy cache on startup.
tnagel@chromium.org
Consistency between TPM lock state and absence/presence of install
attributes at boot.
pmarko@chromium.org
igorcov@chromium.org
Duration of the bucket download part of the auto-enrollment protocol.
pmarko@chromium.org
igorcov@chromium.org
Time since the user logged in until the auto-enrollment protocol completed.
0 is sampled when the protocol is done by the time the user logs in.
pmarko@chromium.org
igorcov@chromium.org
Total duration time of the auto-enrollment protocol.
pmarko@chromium.org
igorcov@chromium.org
Network error code (if applicable) for auto-enrollment requests.
pmarko@chromium.org
igorcov@chromium.org
URL fetcher status for auto-enrollment requests.
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.
hunyadym@chromium.org
Number of retries the client did to execute a DeviceManagementServer
request. It's recorded after the request has been completed, either
successfully after 0 or more retries, with a failure (too many retries or
non-retriable error) or with a server error.
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.
emaxx@chromium.org
poromov@chromium.org
Chrome OS only. Whether the successful locking of install attributes reused
the previously existing locked attributes, or a fresh lock has being held.
pmarko@chromium.org
igorcov@chromium.org
Chrome OS only. Encodes if initial enrollment should be done, and if not,
why. This histogram is recorded when the Auto Enrollment Check screen is
reached in the Chrome OS Out Of The Box Experience (OOBE) sequence and the
device has not been enrolled or in consumer mode before, i.e. when the
'check_enrollment' and 'ActivateDate' VPD keys are not present.
igorcov@chromium.org
Chrome OS only. Number of policy files that turned out to be invalid when
reading the device policy data. In success scenario the latest policy file
read is successful and has valid data submitting zero for this statistic.
mnissler@chromium.org
Number of policies loaded at startup on iOS, and when a change is detected
at runtime.
zmin@chromium.org
Records whether the Chrome install is system level or user level when trying
to enroll into the machine level user cloud policy on Windows. This is
intended to count the number of enrollments for each install type.
rogerta@chromium.org
Time since the enrollment request was made until an error is returned from
the server.
rogerta@chromium.org
Time since the enrollment request was made until a successful enrollment
response is returned from the server.
zmin@chromium.org
The result of machine level user cloud policy enrollment.
rogerta@chromium.org
Records whether the machine level user cloud policy enrollment dialog is
shown to the user and the action they took.
rogerta@chromium.org
The length of time the machine level user cloud policy enrollment dialog was
visible to the user.
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.
atwilson@chromium.org
Tracking the results of policy key verification.
mnissler@chromium.org
Load status from the policy loaders which pull policy settings from the
underlying platform, such as Windows Group Policy.
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.
antrim@chromium.org
Time since last device policy fetch.
zmin@chromium.org
Time since last machine level user policy fetch.
antrim@chromium.org
Time since last user policy fetch.
poromov@chromium.org
Tracking the results of policy user verification.
isandrk@chromium.org
sduraisamy@chromium.org
Extensions (and apps) are quite restricted in public sessions for security
and privacy concerns - some permissions are blocked which means the
extension itself is blocked (prevented from loading). This histogram counts
requested permissions on extension installation in public sessions (both
installed and blocked extensions).
xiyuan@chromium.org
sduraisamy@chromium.org
A public session starts when a user signs in using the policy configured
public account. It stops when the user signs out. Session length is the
duration between the start and stop events. It is recorded during signing
out and reported on the next chrome run. This metric tracks the recorded
session length rounded down to the nearest 10-minute bucket and capped at 24
hours.
xiyuan@chromium.org
sduraisamy@chromium.org
A regular user session starts when a user signs in using his/her user
account. It stops when the user signs out. Session length is the duration
between the start and stop events. It is recorded during signing out and
reported on the next chrome run. This metric tracks the recorded session
length on an enrolled device rouned down to the nearest 10-minute bucket and
capped at 24 hours.
emaxx@chromium.org
igorcov@chromium.org
On Chrome OS, the response obtained to retrieve policy request.
Deprecated and removed from code as of 01/2016.
pbond@chromium.org
Events for counting sensitive data occurrences in system logs to upload.
(Email addresses, IP addresses, SSIDs, URLs). The lines with this data will
be removed before upload.
hunyadym@chromium.org
Number of retries the client did to execute an UploadJob. It's recorded
after the request has been completed, either successfully after 0 or more
retries, with a failure because of too many retries or if the UploadJob is
interrupted (destroyed before it could succeed or fail).
atwilson@chromium.org
Result of the attempted policy load during profile initialization.
atwilson@chromium.org
Result of validating the policy that has just been loaded from disk.
atwilson@chromium.org
Result of validating the policy sent down from the server, before writing to
disk.
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.
emaxx@chromium.org
Session abort due to a fatal error of Chrome OS user policy initialization.
mnissler@chromium.org
Source of policy validation errors on Chrome OS.
mnissler@chromium.org
Validation result when loading user policy from the policy store.
mnissler@chromium.org
Validation result when writing user policy to the policy store.
xiyuan@chromium.org
sduraisamy@chromium.org
Tracks the sign-in events on an enrolled device.
atwilson@chromium.org
Choice the user made when presented with enterprise signin dialog.
igorcov@chromium.org
tnagel@chromium.org
The status code (exit code or signal) from sanity check of RW_VPD read and
matching the contents with data from dump_vpd_log (Chrome OS).
igorcov@chromium.org
tnagel@chromium.org
The status code (exit code or signal) from VPD update operation (Chrome OS).
mnissler@chromium.org
Delay incurred by the token fetching step of the wildcard login check.
mnissler@chromium.org
Total delay incurred by the wildcard login check.
mnissler@chromium.org
Delay incurred by the user info fetching step of the wildcard login check.
Deprecated 07/2016 in Issue 621270.
mnissler@chromium.org
pastarmovj@chromium.org
Whether we were able to contact the AD Domain Controller. This check is
performed once at start-up on Windows.
Deprecated 07/2016 in Issue 621270.
mnissler@chromium.org
pastarmovj@chromium.org
Enum of possible things that can fail while checking for enterprise env.
This check is performed once at start-up on Windows.
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.
olsen@chromium.org
A set of policy rules that failed validation due to unparsable JSON, or JSON
that did not match the schema. This validation happens on start-up and when
the policy has changed.
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.
mad@chromium.org
Whether the machine is joined to an AD domain. This check is performed once
at start-up on Windows.
rogerta@chromium.org
Whether the machine is considered an enterprise user. An enterprise user is
either in a domain or is managed via MDM. This check is performed once at
start-up on Windows.
mad@chromium.org
Whether the full machine name is the same as the short one, identifying a
local machine. This check is performed once at start-up on Windows.
mad@chromium.org
Whether the currently logged in user is a local user or not, based on its
SAM compatible user name and machine name. This check is performed once at
start-up on Windows.
rogerta@chromium.org
Whether the machine is managed via MDM. This check is performed once at
start-up on Windows.
rogerta@chromium.org
Whether we could obtain the address of the NetGetJoinInformation function.
This check is performed once at start-up on Windows.
mnissler@chromium.org
pastarmovj@chromium.org
The rough Windows suite we are running on. This check is performed once at
start-up on Windows.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
On non-mobile sites, gesture taps are delayed to prevent double taps from
sending a click event. This stat tracks the user's first action within 5
seconds after a double tap gesture when the gesture tap delay is disabled.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
On non-mobile sites, gesture taps are delayed to prevent double taps from
sending a click event. This stat tracks the user's first action within 5
seconds after a double tap gesture when gesture tap events are delayed.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between initiation of any input event and the renderer receiving and
starting to process it.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
mustaq@chromium.org
Tracks the number of Android MotionEvents with ACTION_DOWN or
ACTION_POINTER_DOWN or ACTION_BUTTON_PRESS for each ToolType (unknown,
finger, mouse or stylus).
Team: input-dev@chromium.org.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how many clients were queried (asynchronously) to determine the
target for an input event.
riajiang@chromium.org
Tracks how long it takes for a client to respond to an asynchronous request
to find a target for an input event.
Team: event-targeting@chromium.org.
riajiang@chromium.org
Tracks how long an event has to wait in the queue while a previous event is
being targeted asynchronously.
Team: event-targeting@chromium.org.
nzolghadr@chromium.org
Whether click target was affected by DOM manipulation or not.
Team: input-dev@chromium.org.
tdresser@chromium.org
Team: input-dev@chromium.org.
Number of Mouse events coalesced.
tdresser@chromium.org
Team: input-dev@chromium.org.
Number of Touch events coalesced.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between the first and last events in a coalesced mouse events group.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between the first and last events in a coalesced touch events group.
Team: input-dev@chromium.org.
chongz@chromium.org
Number of continuous gesture events (GestureScrollUpdate,
GesturePinchUpdate) coalesced inside the compositor thread event queue per
event. This field is recorded just before the event is processed on the
compositor thread.
Team: input-dev@chromium.org.
chongz@chromium.org
Time between the first event in a coalesced continuous gesture events group
(GestureScrollUpdate, GesturePinchUpdate) and when it was processed on the
compositor thread.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
chongz@chromium.org
Time between the last event in a coalesced continuous gesture events group
(GestureScrollUpdate, GesturePinchUpdate) and when it was processed on the
compositor thread.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
chongz@chromium.org
Time between when a non-continuous gesture event (GestureScrollStart/End,
GesturePinchStart/End) was placed into the queue and when it was processed
on the compositor thread.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 01/2018 in favor of
Event.DownEventCount.PerInputFormFactorDestinationCombination.
xiaoyinh@chromium.org
tbuckley@chromium.org
The number of down events received per destination. Every down event that is
targeted to each destination will be counted, including those that don't
have an effect. For example: Tapping on a disabled button inside the browser
frame will be treated as down events on browser window.
Deprecated 01/2018 in favor of
Event.DownEventCount.PerInputFormFactorDestinationCombination.
xiaoyinh@chromium.org
tbuckley@chromium.org
Counts the number of down events generated by clamshell/touchview.
Deprecated 01/2018 in favor of
Event.DownEventCount.PerInputFormFactorDestinationCombination.
xiaoyinh@chromium.org
tbuckley@chromium.org
Counts the number of down events generated by Mouse/Touch/Stylus.
xiaoyinh@chromium.org
tbuckley@chromium.org
The number of down events received per input, form factor, and destination
combination.
Input is down events generated by mouse/touch/stylus. Form factor is down
events generated by clamshell/touchviewLandscape/touchviewPortrait.
Destination: Every down event that is targeted to each destination will be
counted,including those that don't have an effect. For example: Tapping on a
disabled button inside the browser frame will be treated as down events on
browser window.
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.
tdresser@chromium.org
progressive-web-metrics@chromium.org
For each 10 second window, reports the fraction of the time there was no
user input. We consider there to be no user input if we haven't received any
events for > 50ms.
wjmaclean@chromium.org
Record whether we unexpectedly encounter an empty gesture queue while
routing gesture events to frames' renderers: true => empty queue, false
=> non-empty queue.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Emitted after a renderer process main-thread fling curve animation
terminates, for any reason, reporting the average animation frequency
(animations/second) of the fling instance over its lifetime. This is
computed as the number of fling animation ticks divided by the fling
animation duration.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Emitted after a renderer process impl-thread fling curve animation
terminates, for any reason, reporting the average animation frequency
(animations/second) of the fling instance over its lifetime. This is
computed as the number of fling animation ticks divided by the fling
animation duration.
Team: input-dev@chromium.org.
kuscher@google.com
The gesture-events recognized and dispatched by the browser gesture
recognizer. This replaces Ash.GestureCreated, which did not record events on
Android and Windows.
Team: input-dev@chromium.org.
dtapuska@chromium.org
For each hit test, records whether it was a hit or miss, and why.
Team: input-dev@chromium.org.
dtapuska@chromium.org
For hit tests that are validated, records whether it was correct or not, and
why.
Team: input-dev@chromium.org.
dtapuska@chromium.org
For hit tests that are invalid, records the score (a series of bits
indicating what was matched and what wasn't).
Team: input-dev@chromium.org.
tdresser@chromium.org
input-dev@chromium.org
Time between the renderer main thread receiving a keyboard event and acking
it, for events which were not preventDefaulted. Only recorded for key
presses.
tdresser@chromium.org
input-dev@chromium.org
Time between the renderer main thread receiving a keyboard event and acking
it, for events which were preventDefaulted. Only recorded for key presses.
tdresser@chromium.org
Time between the renderer main thread receiving a touchend event and acking
it, for events which were not preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the renderer main thread receiving a touchend event and acking
it, for events which were preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the renderer main thread receiving a touchmove event and acking
it, for events which were not preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the renderer main thread receiving a touchmove event and acking
it, for events which were preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the renderer main thread receiving a touchstart event and
acking it, for events which were not preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the renderer main thread receiving a touchstart event and
acking it, for events which were preventDefaulted.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of all input events and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of input event and browser processing.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between key events sent from RWH to renderer and acked by renderer.
Only monitors key presses.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between key events received by Chrome and sent from RWH to renderer.
Only monitors key presses.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between touch events sent from RWH to renderer and acked by renderer.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between touch events received by Chrome and sent from RWH to renderer.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
ccameron@chromium.org
Time between wheel events sent from RWH to renderer and acked by renderer.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
ccameron@chromium.org
Time between wheel events received by Chrome and sent from RWH to renderer.
Team: input-dev@chromium.org.
tdresser@chromium.org
input-dev@chromium.org
Time between the OS receiving a keyboard event and the resulting GPU frame
swap. If no swap was induced by the event, no recording is made. Only
recorded for key presses.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
input-dev@chromium.org
Time between the OS receiving a mouse event and the resulting GPU frame
swap. If no swap was induced by the event, no recording is made.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
dtapuska@chromium.org
Duration of a non-resurive hitTest operation. The hit test is non-recursive
when the AllowChildFrameContent flag is clear. See also
Event.Latency.HitTestRecusrive.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
dtapuska@chromium.org
Duration of a recursive hitTest operation. The hit test is recursive when
the AllowChildFrameContent flag is set. See also Event.Latency.HitTest.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Team: input-dev@chromium.org.
Time between input event received by OS and sent to Chrome.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
input-dev@chromium.org
Time between sending a keyboard event to the renderer main thread and when
the renderer begins to process that event, for events which were not
preventDefaulted. Only recorded for key presses.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a keyboard event to the renderer main thread and when
the renderer begins to process that event, for events which were
preventDefaulted. Only recorded for key presses.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a touchend event to the renderer main thread and when
the renderer begins to process that event, for events which were not
preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a touchend event to the renderer main thread and when
the renderer begins to process that event, for events which were
preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a touchmove event to the renderer main thread and when
the renderer begins to process that event, for events which were not
preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a touchmove event to the renderer main thread and when
the renderer begins to process that event, for events which were
preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a touchstart event to the renderer main thread and when
the renderer begins to process that event, for events which were not
preventDefaulted.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between sending a touchstart event to the renderer main thread and when
the renderer begins to process that event, for events which were
preventDefaulted.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between initiation of all input events and renderer processing. This is
soon to be replaced by Event.Latency.Renderer2.*
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between input event creation and the renderer receiving and starting to
process the event. For touch events on Windows, we measure from when the
event reaches Chrome, whereas on other platforms we use the timestamp from
the kernel. On Windows, this metric is only reported when |IsHighResolution|
is true, which will introduce some sampling bias.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between input event creation and the renderer impl thread receiving and
starting to process the event. For touch events on Windows, we measure from
when the event reaches Chrome, whereas on other platforms we use the
timestamp from the kernel. On Windows, this metric is only reported when
|IsHighResolution| is true, which will introduce some sampling bias.
Team: input-dev@chromium.org.
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.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between touch event creation and when the resulting GestureScroll
reaches the Impl thread. Maximum is 1000ms. On Windows, we measure from when
the touch event reaches Chrome, whereas on other platforms we use the
timestamp from the kernel. On Windows, this metric is only reported when
|IsHighResolution| is true, which will introduce some sampling bias. This
supersedes the Event.Latency.RendererImpl.GestureScroll metric.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between initial creation of a wheel event and the generated
ScrollUpdate gesture event is handled on main/impl thread (specified by
suffix). If no swap was induced by the ScrollUpdate gesture event, no
recording is made. Unlike Event.Latency.ScrollUpdate.Wheel.TimeToHandled2
this metric includes the first GSU of every scrolling sequence as well.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a wheel event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. Unlike
Event.Latency.ScrollUpdate.Wheel.TimeToScrollUpdateSwapBegin2 this metric
includes the first GSU of every scrolling sequence as well.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by *.TimeToScrollUpdateSwapBegin2 https://crbug.com/849735 in M68.
nzolghadr@chromium.org
Time between initial creation of a wheel/touch event and start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made. If no
swap was induced by the event, no recording is made.
Team: input-dev@chromium.org.
nzolghadr@chromium.org
Time between initial creation of a wheel/touch event and start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made. If no
swap was induced by the event, no recording is made.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the browser receives the notification of the first ScrollUpdate
gesture event in a given scroll gesture event sequence with touch source
induced renderer swap and GPU starts to swap.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between gpu starts to swap the first ScrollUpdate gesture event in a
given scroll gesture event sequence with touch source induced frame and the
swap finishes.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the first ScrollUpdate gesture event in a given scroll gesture
event sequence with touch source, is handled on main/impl thread (specified
by suffix) and before renderer starts to swap.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the renderer starts to swap a frame induced by the first
ScrollUpdate gesture event in a given scroll gesture event sequence with
touch source, and browser receives the swap notification.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between initial creation of a touch event and the first generated
ScrollUpdate gesture event in a given scroll gesture event sequence is
handled on main/impl thread (specified by suffix). If no swap was induced by
the ScrollUpdate gesture event, no recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made. This is
going to be replaced by *.TimeToScrollUpdateSwapBegin3 version since a
rebucketing change made this metric lose its usefulness in Chirp
infrastructure.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68.
tdresser@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the browser receives the notification of the first ScrollUpdate
gesture event in a given scroll gesture event sequence with wheel source
induced renderer swap and GPU starts to swap.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between gpu starts to swap the first ScrollUpdate gesture event in a
given scroll gesture event sequence with wheel source induced frame and the
swap finishes.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the first ScrollUpdate gesture event in a given scroll gesture
event sequence with wheel source, is handled on main/impl thread (specified
by suffix) and before renderer starts to swap.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the renderer starts to swap a frame induced by the first
ScrollUpdate gesture event in a given scroll gesture event sequence with
wheel source, and browser receives the swap notification.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between initial creation of a wheel event and the first generated
ScrollUpdate gesture event in a given scroll gesture event sequence is
handled on main/impl thread (specified by suffix). If no swap was induced by
the ScrollBegin gesture event, no recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a wheel event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made. This is
going to be replaced by *.TimeToScrollUpdateSwapBegin3 version since a
rebucketing change made this metric lose its usefulness in Chirp
infrastructure.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68.
tdresser@chromium.org
Time between initial creation of a wheel event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a wheel event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
sahel@chromium.org
Time between the browser receives the notification of a ScrollUpdate gesture
generated from a touchscreen fling induced renderer swap and GPU starts to
swap.
Team: input-dev@chromium.org.
sahel@chromium.org
Time between gpu starts to swap a ScrollUpdate gesture event generated from
a touchscreen fling induced frame and the swap finishes.
Team: input-dev@chromium.org.
sahel@chromium.org
Time between a ScrollUpdate gesture event generated from a touchscreen
fling, is handled on main/impl thread (specified by suffix) and before
renderer starts to swap.
Team: input-dev@chromium.org.
sahel@chromium.org
Time between the renderer starts to swap a frame induced by a ScrollUpdate
gesture event generated from a touchscreen fling, and browser receives the
swap notification.
Team: input-dev@chromium.org.
sahel@chromium.org
Time between initial creation of a ScrollUpdate gesture event generated from
a touchscreen fling is handled on main/impl thread (specified by suffix). If
no swap was induced by the ScrollUpdate gesture event, no recording is made.
Team: input-dev@chromium.org.
sahel@chromium.org
Time between initial creation of a ScrollUpdate gesture event generated from
a touchscreen fling and the start of the frame swap on the GPU service
caused by the generated ScrollUpdate gesture event. If no swap was induced
by the event, no recording is made. This is going to be replaced by
*.TimeToScrollUpdateSwapBegin3 version since a rebucketing change made this
metric lose its usefulness in Chirp infrastructure.
Team: input-dev@chromium.org.
Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68.
sahel@chromium.org
Time between initial creation of a ScrollUpdate gesture event generated from
a touchscreen fling and the start of the frame swap on the GPU service
caused by the generated ScrollUpdate gesture event. If no swap was induced
by the event, no recording is made.
Team: input-dev@chromium.org.
sahel@chromium.org
Time between initial creation of a ScrollUpdate gesture event generated from
a touchscreen fling and the start of the frame swap on the GPU service
caused by the generated ScrollUpdate gesture event. If no swap was induced
by the event, no recording is made.
Team: input-dev@chromium.org.
To be replaced by
Event.Latency.ScrollUpdate.Touch.BrowserNotifiedToBeforeGpuSwap2,
Event.Latency.ScrollUpdate.Wheel.BrowserNotifiedToBeforeGpuSwap2 in M56.
https://crbug.com/649754
rbyers@chromium.org
Time between the browser receives the notification of a ScrollUpdate gesture
event induced renderer swap and GPU starts to swap.
To be replaced by Event.Latency.ScrollUpdate.Touch.GpuSwap2,
Event.Latency.ScrollUpdate.wheel.GpuSwap2 in M56. https://crbug.com/649754
rbyers@chromium.org
Time between gpu starts to swap a ScrollUpdate gesture event induced frame
and the swap finishes.
To be replaced by Event.Latency.ScrollUpdate.Touch.HandledToRendererSwap2,
Event.Latency.ScrollUpdate.Wheel.HandledToRendererSwap2 in M56.
https://crbug.com/649754
rbyers@chromium.org
Time between the ScrollUpdate gesture event is handled on main/impl thread
(specified by suffix) and before renderer starts to swap.
To be replaced by
Event.Latency.ScrollUpdate.Touch.RendererSwapToBrowserNotified2,
Event.Latency.ScrollUpdate.Wheel.RendererSwapToBrowserNotified2 in M56.
https://crbug.com/649754
rbyers@chromium.org
Time between the renderer starts to swap a frame induced by ScrollUpdate
gesture event and browser receives the swap notification.
Replaced by *.TimeToScrollUpdateSwapBegin2 https://crbug.com/849735 in M68.
nzolghadr@chromium.org
Time between initial creation of a wheel/touch event and start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event.
If no swap was induced by the event, no recording is made. The first GSU of
every scrolling sequence is excluded from this metric.
Team: input-dev@chromium.org.
nzolghadr@chromium.org
Time between initial creation of a wheel/touch event and start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event.
If no swap was induced by the event, no recording is made. The first GSU of
every scrolling sequence is excluded from this metric.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between the browser receives the notification of a ScrollUpdate gesture
event with touch source induced renderer swap and GPU starts to swap.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between gpu starts to swap a ScrollUpdate gesture event with touch
source induced frame and the swap finishes.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the ScrollUpdate gesture event with touch source, is handled on
main/impl thread (specified by suffix) and before renderer starts to swap.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the renderer starts to swap a frame induced by ScrollUpdate
gesture event with touch source, and browser receives the swap notification.
Team: input-dev@chromium.org.
Replaced by Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
To be replaced by
Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2 in M57.
https://crbug.com/669618
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between initial creation of a touch event and the generated
ScrollUpdate gesture event is handled on main/impl thread (specified by
suffix). If no swap was induced by the ScrollUpdate gesture event, no
recording is made.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a touch event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. The first GSU of every
scrolling sequence is excluded from this metric. This is going to be
replaced by *.TimeToScrollUpdateSwapBegin3 version since a rebucketing
change made this metric lose its usefulness in Chirp infrastructure.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68.
tdresser@chromium.org
Time between initial creation of a touch event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. The first GSU of every
scrolling sequence is excluded from this metric.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a touch event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. The first GSU of every
scrolling sequence is excluded from this metric.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
To be replaced by Event.Latency.ScrollUpdate.Touch.TimeToHandled2 in M56.
https://crbug.com/649754
rbyers@chromium.org
Time between initial creation of a touch event and the generated
ScrollUpdate gesture event is handled on main/impl thread (specified by
suffix). If no swap was induced by the ScrollUpdate gesture event, no
recording is made.
tdresser@chromium.org
Time between the browser receives the notification of a ScrollUpdate gesture
event with wheel source induced renderer swap and GPU starts to swap.
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between gpu starts to swap a ScrollUpdate gesture event with wheel
source induced frame and the swap finishes.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the ScrollUpdate gesture event with wheel source, is handled on
main/impl thread (specified by suffix) and before renderer starts to swap.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between the renderer starts to swap a frame induced by ScrollUpdate
gesture event with wheel source, and browser receives the swap notification.
Team: input-dev@chromium.org.
Replaced by Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a wheel event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
To be replaced by
Event.Latency.ScrollBegin.Wheel.TimeToScrollUpdateSwapBegin2 in M57.
https://crbug.com/669618
Team: input-dev@chromium.org.
tdresser@chromium.org
Time between initial creation of a wheel event and the generated
ScrollUpdate gesture event is handled on main/impl thread (specified by
suffix). If no swap was induced by the ScrollUpdate gesture event, no
recording is made. The first GSU of every scrolling sequence is excluded
from this metric.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a wheel event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. The first GSU of every
scrolling sequence is excluded from this metric. This is going to be
replaced by *.TimeToScrollUpdateSwapBegin3 version since a rebucketing
change made this metric lose its usefulness in Chirp infrastructure.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by *.TimeToScrollUpdateSwapBegin4 https://crbug.com/849735 in M68.
tdresser@chromium.org
Time between initial creation of a wheel event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. The first GSU of every
scrolling sequence is excluded from this metric.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
Time between initial creation of a wheel event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made. The first GSU of every
scrolling sequence is excluded from this metric.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by
Event.Latency.ScrollUpdate.Touch.TimeToFirstScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
Replaced by Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a touch event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made.
Replaced by Event.Latency.TouchToFirstScrollUpdateSwapBegin.
crbug.com/478845
rbyers@chromium.org
Time between initial creation of a touch event and the frame swap caused by
by the generated ScrollUpdate gesture event if that ScrollUpdate is the
first such in a given scroll gesture event sequence. If no swap was induced
by the event, no recording is made.
Replaced by Event.Latency.ScrollBegin.Touch.TimeToScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a touch event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
To be replaced by
Event.Latency.ScrollUpdate.Touch.TimeToFirstScrollUpdateSwapBegin2 in M56.
https://crbug.com/649754
Team: input-dev@chromium.org.
Replaced by Event.Latency.TouchToScrollUpdateSwapBegin. crbug.com/478845
tdresser@chromium.org
Time between initial creation of a touch event and the frame swap caused by
by the generated ScrollUpdate gesture event. If no swap was induced by the
event, no recording is made.
Replaced by Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a touch event and start of the frame swap
on the GPU service caused by the generated ScrollUpdate gesture event. If no
swap was induced by the event, no recording is made.
To be replaced by
Event.Latency.ScrollUpdate.Touch.TimeToScrollUpdateSwapBegin2 in M56.
https://crbug.com/649754
Team: input-dev@chromium.org.
Replaced by
Event.Latency.ScrollUpdate.Wheel.TimeToFirstScrollUpdateSwapBegin2.
tdresser@chromium.org
Time between initial creation of a wheel event and the start of the frame
swap on the GPU service caused by the generated ScrollUpdate gesture event
if that ScrollUpdate is the first such event in a given scroll gesture event
sequence. If no swap was induced by the event, no recording is made.
Deprecated 08/2016, and replaced by Linux.X11.ServerRTT.
thomasanderson@chromium.org
Time to request a timestamp from the X server.
Deprecated 03/2018 due to lack of usage.
dtapuska@chromium.org
Number of continuous events (touchmove, mousemove, mousewheel) coalesced
inside the main thread event queue per event. This field is recorded just
before the event is processed on the main thread.
Team: input-dev@chromium.org.
Deprecated 01/2018 due to lack of usage.
dtapuska@chromium.org
Time between when a continuous event (touchmove, mousemove, mousewheel) was
placed into the queue (or coalesced with another event) and when it was
processed on the main thread.
Team: input-dev@chromium.org.
Deprecated 01/2018 due to lack of usage.
dtapuska@chromium.org
Time between when a continuous event (touchmove, mousemove, mousewheel) was
placed into the queue and when it was processed on the main thread.
Team: input-dev@chromium.org.
dtapuska@chromium.org
Whether the Begin Main Frame was not received and the queue generated a
flush queue after a given timeout.
Team: input-dev@chromium.org.
Deprecated 01/2018 due to lack of usage.
dtapuska@chromium.org
Time between when a non-continuous event (not touchmove, mousemove,
mousewheel) was placed into the queue and when it was processed on the main
thread.
Team: input-dev@chromium.org.
dtapuska@chromium.org
Counts the number of event listener invocations that were forced to be
passive due to interventions and whether the invocation of the listener
called prevent default or not.
Team: input-dev@chromium.org.
dtapuska@chromium.org
The result of handling of MouseWheel, TouchStart, TouchMove, TouchEnd events
in the renderer.
Team: input-dev@chromium.org.
Deprecated 08/2016 in Issue 595327, and replaced by
Event.PassiveListeners.ForcedNonBlockingLatencyDueToFling.
dtapuska@chromium.org
Time between when a forced non-blocking event was generated and the event
processed. This histogram tracks the benefit of forcing non-blocking events
listeners.
dtapuska@chromium.org
Time between when a touchstart or first touchmove event per scroll was
generated and the event processed, for events which were forced non-blocking
since they occurred during fling. This histogram tracks the benefit of
forcing events non-blocking during fling.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 04/2018 due to cancellation of experiment.
tdresser@chromium.org
Time between when a touchstart or first touchmove event per scroll was
generated and the event processed, for events which were forced non-blocking
since they occurred while the main thread was unresponsive. This histogram
tracks the benefit of forcing events non-blocking when the main thread is
unresponsive.
Team: input-dev@chromium.org.
dtapuska@chromium.org
Time between when a cancelable event was generated and the event processed
yet no action was executed for the event. This histogram tracks the
potential benefit of using passive events listeners.
Team: input-dev@chromium.org.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated 06/2017 due to lack of usage.
dtapuska@chromium.org
Whether the input IPC messages were discarded before being fully processed
in RenderView's IPC message handler.
Team: input-dev@chromium.org.
Deprecated 10/2017 due to the completion of the experiment.
yigu@chromium.org
Record the area of a scroller upon page load. This is intended to help us
measure the distribution of scrollers with different sizes. Combined with
the other two metrics which measure the size of scrollers on scroll, we may
have a better idea of not compositing small scrollers.
Team: input-dev@chromium.org, animations-dev@chromium.org.
Deprecated 10/2017 due to the completion of the experiment.
yigu@chromium.org
Record the area of a scroller upon ScrollBegin. This is intended to help us
measure the frequencies of different sizes of scrollers getting scrolled.
For those small scrollers that users may rarely scroll, there is no need to
composite them even if we are able to do so.
Team: input-dev@chromium.org, animations-dev@chromium.org.
tdresser@chromium.org
On non-mobile sites, gesture taps are delayed to prevent double taps from
sending a click event. This stat counts the number of taps that are delayed
by the double-tap delay versus those that are sent immediately on mobile
sites.
Team: input-dev@chromium.org.
Deprecated as of 1/2018 in issue 650338 (http://crbug.com/650338). Using a
DCHECK instead.
majidvp@chromium.org
caseq@chromium.org
Whether the timestamps on input events produced by the windowing system
appear to be sharing the same time base as TimeTicks, modulo possible
roll-over.
Team: input-dev@chromium.org.
kuscher@google.com
rbyers@chromium.org
The gesture-events recognized and dispatched for UI components owned by the
browser. This histogram was created as part of separating gesture events
between the browser and Ash (crbug.com/826476). The enums are extracted from
Ash.GestureTarget.
Deprecated 05/2016, and replaced by Event.Touch.TargetAndDispatchResult2.
dtapuska@chromium.org
An enumeration identifying 3 properties: 1) a classification of the event
target whether it is a root scroll listener (window, document, body) or not;
2) the result of the dispatch; 3) whether the document was scrollable or
not.
dtapuska@chromium.org
An enumeration identifying 4 properties: 1) a classification of the current
target whether it is a root scroll listener (window, document, body) or not;
2) the result of the dispatch or whether it was previously canceled 3)
whether the document was scrollable or not 4) what phase the listener was
encountered at. This metric is logged during the dispatch of the touch
events. It will only be reported for main frame events that block scrolling,
have only one touch point and current targets that fired an event listener
at that phase.
Team: input-dev@chromium.org.
tdresser@chromium.org
On non-mobile-optimized (desktop) sites, whether the ack response from the
renderer for any event in a contiguous touch sequence exceeds the
desktop-specific timeout threshold.
Team: input-dev@chromium.org.
tdresser@chromium.org
On mobile-optimized sites, whether the ack response from the renderer for
any event in a contiguous touch sequence exceeds the mobile-specific timeout
threshold.
Team: input-dev@chromium.org.
eirage@chromium.org
Records the euclidean distance in dips from a gesture event's original tap
center to its adjusted touch point. 0 if not adjusted. This only records
GestureTap events and GestureLongPress events.
Team: input-dev@chromium.org.
Deprecated 03/2018 due to no longer needed.
eirage@chromium.org
Records if doing touch adjustment on touchstart have same hit test node as
doing touch adjustment on GestureTap. If not, record if one is descendant of
the other. Others means neither of the nodes are descendant of the other.
This only records GestureTap events.
Team: input-dev@chromium.org.
Deprecated 02/2018 and replaced by Event.Touch.TouchAdjustment.AdjustedNode.
eirage@chromium.org
Records if doing touch adjustment on touchstart have same hit test node as
doing touch adjustment on GestureTap. True for same node, false for
different node. This only records GestureTap events.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Records the disposition (handled or not handled) of touchstart events and
the first touchmove events per scroll. Only recorded after the page is fully
loaded.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Records the disposition (handled or not handled) of touchstart events and
the first touchmove events per scroll. Only recorded before the page is
fully loaded.
Team: input-dev@chromium.org.
Deprecated 08/2016 in Issue 595327, and replaced by
Event.Touch.TouchDispositionsDuringFling2.
tdresser@chromium.org
Records the disposition (handled or not handled) of touchstart events. Only
recorded while there is an active fling animation.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Records the disposition (handled or not handled) of touchstart and first
touchmove events per scroll. Only recorded while there is an active fling
animation.
Team: input-dev@chromium.org.
Deprecated 08/2016 in Issue 595327, and replaced by
Event.Touch.TouchDispositionsOutsideFling2.
tdresser@chromium.org
Records the disposition (handled or not handled) of touchstart events. Only
recorded while there is no active fling animation.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Records the disposition (handled or not handled) of touchstart and first
touchmove events per scroll events. Only recorded while there is no active
fling animation.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between when a touch event was generated and the event was processed.
Recorded only for touchstart events and the first touchmove events per
scroll that occur after the page is fully loaded.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between when a touch event was generated and the event was processed.
Recorded only for touchstart events and the first touchmove events per
scroll that occur before the page is fully loaded. This histogram tracks the
benefit of forcing passive event listeners before the page is fully loaded.
Team: input-dev@chromium.org.
Deprecated 06/2017 due to lack of usage.
tdresser@chromium.org
Time between when a touch event was generated and the event was processed.
Recorded only for touchstart events and the first touchmove events per
scroll when there was no active fling animation.
Team: input-dev@chromium.org.
Deprecated 08/2016 in Issue 595327, and replaced by
Event.PassiveListeners.ForcedNonBlockingLatencyDueToFling.
tdresser@chromium.org
Time between when a touchstart event was generated and the event was
processed. Recorded only when there was an active fling animation. This
histogram tracks the benefit of forcing passive event listeners during
fling.
Deprecated 08/2016 in Issue 595327, and replaced by
Event.Touch.TouchLatencyOutsideFling.
tdresser@chromium.org
Time between when a touchstart event was generated and the event was
processed. Recorded only when there was no active fling animation.
kuscher@google.com
tdresser@chromium.org
The duration of a touch-sequence. Only measured for single finger gestures.
This replaces Ash.TouchDuration2, which did not record events on Android and
Windows.
Team: input-dev@chromium.org.
kuscher@google.com
tdresser@chromium.org
The maximum euclidean distance in dips (device independent pixel) which a
touch point has travelled away from its starting point. Only measured for
single finger gestures. This replaces Ash.TouchMaxDistance, which did not
record events on Android and Windows.
Team: input-dev@chromium.org.
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.
amaralp@chromium.org
Percentage of touch handle height that would be clipped by the viewport in
the best case of flipping or not flipping.
amaralp@chromium.org
Percentage of touch handle height that would be clipped by the viewport if
the handle was not vertically flipped.
amaralp@chromium.org
The difference between the metrics |BottomHandleClippingPercentage| and
|BestVerticalClippingPercentage|. Measures how useful vertical flipping is.
amaralp@chromium.org
Percentage of left touch handle width that would be clipped by the viewport
without flipping.
amaralp@chromium.org
Percentage of right touch handle width that would be clipped by the viewport
without flipping.
amaralp@chromium.org
Whether flipping the handle vertically would result in less clipping.
Deprecated as of 07/2018. Replaced with Event.VizHitTest.AggregateTimeUs.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how long it takes for HitTestAggregator to aggregate hit-test data
received from all clients.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how long it takes for HitTestAggregator to aggregate hit-test data
received from all clients, in microseconds.
riajiang@chromium.org
event-targeting@chromium.org
Total number of hit-test regions Viz received from all clients.
Deprecated as of 07/2018. Replaced with Event.VizHitTest.TargetTimeUs.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how long it takes for HitTestQuery to find a target on a given
location.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how long it takes for HitTestQuery to find a target on a given
location, in microseconds.
Deprecated as of 07/2018. Replaced with Event.VizHitTest.TransformTimeUs.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how long it takes for HitTestQuery to transform a location to a given
target's coordinate space.
riajiang@chromium.org
event-targeting@chromium.org
Tracks how long it takes for HitTestQuery to transform a location to a given
target's coordinate space, in microseconds.
mgiuca@chromium.org
The number of times the fullscreen bubble was re-shown due to inactivity
during a session of fullscreen mode (not including mouse or keyboard lock).
If the mouse or keyboard is also locked while a re-show occurs, both this
and BubbleReshowsPerSession.MouseLock and/or
BubbleReshowsPerSession.KeyboardLock are incremented. Includes all types of
fullscreen (user-triggered, extension-triggered and page-triggered).
Recorded at the end of the session if the simplified-fullscreen-ui flag is
enabled.
joedow@chromium.org
The number of times the keyboard lock exit bubble was re-shown during a
session of keyboard lock mode. This occurs when the ExclusiveAccessMode
inactivity timer fires (roughly every 15 minutes). If also in fullscreen
while a re-show occurs both this and BubbleReshowsPerSession.Fullscreen are
incremented in that scenario. Recorded at the end of the session if the
simplified-fullscreen-ui flag is enabled.
joedow@chromium.org
The number of times the keyboard lock exit bubble was re-shown during a
session of keyboard lock mode due to the user pressing the escape key
repeatedly. This metric does not count reshows due to inactivity. Recorded
at the end of the session if the simplified-fullscreen-ui flag is enabled.
mgiuca@chromium.org
The number of times the mouse lock bubble was re-shown due to inactivity
during a session of mouse lock mode. If also in fullscreen while a re-show
occurs, both this and BubbleReshowsPerSession.Fullscreen are incremented.
Recorded at the end of the session if the simplified-fullscreen-ui flag is
enabled.
Deprecated with M46.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that inject at least one new ad.
Deprecated with M46.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that performed an action that
heuristically looks like injecting an ad, but could not be confirmed.
Deprecated with M46.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that performed an action that
heuristically looks like replacing an ad, but could not be confirmed.
Deprecated with M46.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that remove at least one ad.
Deprecated with M46.
felt@chromium.org
rdevlin.cronin@chromium.org
For each pageload, the number of extensions that replace at least one ad.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that inject a content script.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create divs to add to the
page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create 'embed' elements to
add to the page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create iframes to add to
the page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create inputs to add to the
page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create links to add to the
page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create 'object' elements to
add to the page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that create script tags to add
to the page.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that use document.write.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that inject a
content script.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create divs
to add to the page.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
'embed' elements to add to the page.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
iframes to add to the page.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
inputs to add to the page.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create links
to add to the page.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
'object' elements to add to the page.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that create
script tags to add to the page.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that use
document.write.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that set
innerHTML.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that invoke DOM
methods.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that set the
value of DOM properties via assignments.
Deprecated with M46.
felt@chromium.org
For each www.google.com pageload, the number of extensions that read from
the DOM.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that set innerHTML.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that invoke DOM methods.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that set the value of DOM
properties via assignments.
Deprecated with M46.
felt@chromium.org
For each pageload, the number of extensions that read from the DOM.
nparker@chromium.org
The number of extensions that were blacklisted when already installed,
grouped by Extension::Location. Logged when ExtensionService blackists and
unloads an installed extension.
nparker@chromium.org
The number of extensions that have been blocked from installing grouped by
Extension::Location. Logged when ExtensionService refuses to install a
blacklisted extension.
nparker@chromium.org
The number of extensions that have been silently installed in a blacklisted
state, grouped by Extension::Location. Logged when ExtensionService installs
a blacklisted extension without blocking it (ExtensionBlacklist.BlockCRX
would be logged otherwise). Typically this will be when a user has a
blacklisted extension synced.
nparker@chromium.org
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.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced with ExtensionInstalledLoader.ForceDisabled2.
Please list the metric's owners. Add more owner tags as needed.
Counts whether we force-disabled an installed extension at startup because a
policy provider indicated it must remain disabled.
rdevlin.cronin@chromium.org
Counts whether we force-disabled an installed extension at startup because
it failed ManagementPolicy::MustRemainDisabled check. This checks both
UserMayLoad and MustRemainDisabled methods on a policy provider.
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.
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.
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.
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.
Deprecated 2/2014.
rdevlin.cronin@chromium.org
The number of extensions which would display an Active Script Running
indiciation to the user. Recorded at page close.
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.
rdevlin.cronin@chromium.org
The amount of time it takes to generate the JavaScript API bindings for a
particular extension API. This includes the time from when a JavaScript
context tries to access the API, triggering the lazy initializion, to the
time when the API object is returned. This is only recorded if the binding
is successfully generated. See also Extensions.DidCreateScriptContext_*.
rdevlin.cronin@chromium.org
The amount of time it takes to create the JavaScript binding object using
the binding.js module. This is a strict subset of
Extensions.ApiBindingGenerationTime, which includes this work and more.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
dbertoni@chromium.org
Reports whether a tab was updated to a javascript:-scheme URL from the
extensions tabs.update API. Reported once per call to tabs.update().
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Captures the results of URL resolution when relative urls are used in the
tabs/windows api.
benwells@chromium.org
tapted@chromium.org
The number of times v1 apps are launched grouped by
extension_misc::AppLaunchBuckets. See also Apps.AppLaunch for v2 apps.
Deprecated as of 12/2014, replaced by Apps.HostedAppLaunchContainer.
benwells@chromium.org
tapted@chromium.org
The number of times apps are launched grouped by
extensions::LaunchContainer.
benwells@chromium.org
cylee@chromium.org
The number of times apps are launched grouped by
extensions::AppLaunchSource.
lazyboy@chromium.org
A platform app ended up in a regular tab either by the app page or its
background page. Note that this happens unexpectedly right now and we wish
to track its usage before removing the supporting code.
benwells@chromium.org
tapted@chromium.org
The number of apps loaded at startup time grouped by Extension::Location.
benwells@chromium.org
tapted@chromium.org
The actions taken in the NTP apps promo grouped by
extension_misc::AppsPromoBuckets.
benwells@chromium.org
tapted@chromium.org
The number of apps launched grouped by extensions::LaunchType.
rdevlin.cronin@chromium.org
The extension install location of an extension that Chrome attempted to add,
but failed because it would downgrade the version. Tracking for
https://crbug.com/810799.
rdevlin.cronin@chromium.org
The extension item type of an extension that Chrome attempted to add, but
failed because it would downgrade the version. Tracking for
https://crbug.com/810799.
rdevlin.cronin@chromium.org
Time taken to load BackgroundContents for apps at startup when the extension
system notifies that it is ready.
Replaced by Extensions.BackgroundPageLoadTime2.
rdevlin.cronin@chromium.org
The time for an extension's background page to load.
rdevlin.cronin@chromium.org
The time taken for an extension's persistent background page to load its
initial URL.
rdevlin.cronin@chromium.org
The type (if any) of background page the extension has. Recorded for
installed extensions on startup.
rdevlin.cronin@chromium.org
The number of times each Extension function call sends a bad message,
killing the renderer. This may indicate a bug in that API's implementation
on the renderer. Note a similar, aggregate metric is BadMessageTerminate_EFD
which counts the number of bad messages that are sent overall.
rdevlin.cronin@chromium.org
The reason a valid ExtensionSyncData could not be parsed from a SyncData
received from sync.
rdevlin.cronin@chromium.org
The elapsed time to create a new full instance of an extension API's
bindings using native bindings.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
rdevlin.cronin@chromium.org
The elapsed time to update the bindings for a new or existing v8::Context.
The suffix indicates which type of context the bindings are for.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
mgiuca@chromium.org
ortuno@chromium.org
Time it takes to retrieve the app for the current URL during a navigation.
mgiuca@chromium.org
ortuno@chromium.org
Time it takes to retrieve the app associated with the window during a
navigation.
mgiuca@chromium.org
ortuno@chromium.org
Time it takes to retrieve the app for the target url during a navigation.
alancutter@chromium.org
mgiuca@chromium.org
The HTTP status code class returned for each icon loaded during a
BookmarkApp's creation.
alancutter@chromium.org
mgiuca@chromium.org
The HTTP status code class returned for each icon loaded when syncing a
BookmarkApp.
mgiuca@chromium.org
ortuno@chromium.org
Number of times navigations into and out of Bookmark Apps are processed,
grouped by their result.
mgiuca@chromium.org
ortuno@chromium.org
The time between the last navigation in the context and us opening a new app
window in response to a new navigation. If it is very small, the context
probably redirected immediately, which is a bad user experience.
benwells@chromium.org
Records the container used for a bookmark app launch.
benwells@chromium.org
mgiuca@chromium.org
ortuno@chromium.org
The number of times Bookmark Apps are launched, grouped by
extensions::AppLaunchSource. The equivalent histogram on Android is called
Launch.HomeScreenSource.
lukasza@chromium.org
When an extension violates browsing instance boundaries, this metric records
the extension type.
This is a temporary metric - probably okay to remove it in M66, after we've
gathered sufficient UMA data in M65. See also http://crbug.com/718489.
lukasza@chromium.org
When an extension violates browsing instance boundaries, this metric records
whether either the source or the target frame was of the extension view type
of VIEW_TYPE_BACKGROUND_CONTENTS.
This is a temporary metric - probably okay to remove it in M66, after we've
gathered sufficient UMA data in M65. See also http://crbug.com/718489.
lukasza@chromium.org
When an extension violates browsing instance boundaries, this metric records
the extension view type of the source frame.
This is a temporary metric - probably okay to remove it in M66, after we've
gathered sufficient UMA data in M65. See also http://crbug.com/718489.
lukasza@chromium.org
When an extension violates browsing instance boundaries, this metric records
the extension view type of the found frame.
This metric should help confirm or deny the theory that violating browsing
instance boundaries is only needed for looking up background contents /
pages (of VIEW_TYPE_BACKGROUND_CONTENTS type).
This is a temporary metric - probably okay to remove it in M66, after we've
gathered sufficient UMA data in M65. See also http://crbug.com/718489.
rkaplow@chromium.org
The amount of time that elapsed during
ExtensionService::CheckForExternalUpdates.
lazyboy@chromium.org
rdevlin.cronin@chromium.org
How long a successful initialization of computed_hashes.json file takes.
Recorded when content verification needs to retrieve block hashes.
lazyboy@chromium.org
rdevlin.cronin@chromium.org
Whether or not computed_hashes.json file read and parse succeeded. Recorded
when content verification needs to retrieve block hashes.
lazyboy@chromium.org
rdevlin.cronin@chromium.org
Whether or not fetching verified_contents.json succeeded. Recorded when the
file wasn't available locally and we needed to fetch it from network.
lazyboy@chromium.org
rdevlin.cronin@chromium.org
Time spent by ContentVerifier for a request to create a ContentHash
instance. Recorded during an extension load completion or during an on
demand content verification that was triggered by ContentVerifyJob.
lazyboy@chromium.org
rdevlin.cronin@chromium.org
Whether or not initializing verified_contents.json succeeded. Recorded
during an extension load completion or during an on demand content
verification that was triggered by ContentVerifyJob.
lazyboy@chromium.org
rdevlin.cronin@chromium.org
How long a successful initialization of verified_contents.json file takes.
Recorded if Extensions.ContentVerification.VerifiedContentsInitResult = true
was recorded.
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
Fires when we detect corruption in an enterprise policy forced install
extension and begin the process of reinstalling it. Compare to
CorruptPolicyExtensionResolved to judge success rate.
asargent@chromium.org
Fires when we've successfully resinstalled a corrupt enterprise policy
force-installed extension, with a value indicating how long it took
end-to-end to complete the reinstall (including download time).
Deprecated 9/2016 by fix for Issue 447040.
asargent@chromium.org
Fires when we detect corruption in an enterprise policy forced install
extension. See http://crbug.com/447040 for more background on why we don't
yet disable these. A useful comparison can be made between this value and
the number of policy forced extensions loaded at startup, which is logged in
the EXTERNAL_POLICY_DOWNLOAD bucket of the Extensions.ExtensionLocation
histogram.
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.
cmumford@chromium.org
The result of an attempt to recover from an attempt to open a database that
failed as a result of corruption.
cmumford@chromium.org
The result of an open attempt to an Extensions database.
Shipped only in M48. Superceded by Extensions.Database.Database.Restore and
Extensions.Database.Value.Restore.
cmumford@chromium.org
The result of an attempt to recover from an attempt to open a database that
failed as a result of corruption.
cmumford@chromium.org
The result of an attempt to delete a corrupted value from a database.
karandeepb@chromium.org
Number of calls to the declarative API extension functions. This includes
the declarativeContent and declarativeWebRequest APIs. Emitted when the
extension function is called.
karandeepb@chromium.org
Measures the time taken to load the indexed ruleset in the browser process
for an extension. This includes memory mapping the ruleset file and
verifying it. Emitted when an extension using the Declarative Net Request
API is loaded.
karandeepb@chromium.org
Time taken to evaluate whether a network request should be blocked or
redirected as per the Declarative Net Request API. This includes the time
taken to evaluate all the extension rulesets. Emitted for non-sensitive
network requests seen by the Extension System.
karandeepb@chromium.org
Time taken to index and persist to disk, the deserialized json rules
provided by an extension manifest for the Declarative Net Request API. This
includes the time recorded in
Extensions.DeclarativeNetRequest.IndexRulesTime together with the time taken
to persist the ruleset to disk. This is emitted whenever an extension's json
ruleset is successfully indexed and persisted. This may happen when a packed
extension is installed, an unpacked extension is loaded, an extension's
ruleset is re-indexed due to corruption, etc.
karandeepb@chromium.org
Time taken to index the deserialized json rules provided by an extension
manifest for the Declarative Net Request API. This is emitted whenever an
extension's json ruleset is successfully indexed. This may happen when a
packed extension is installed, an unpacked extension is loaded, an
extension's ruleset is re-indexed due to corruption, etc.
karandeepb@chromium.org
Records the result of loading an extension ruleset for the Declarative Net
Request API. Emitted whenever an extension with a ruleset is loaded.
karandeepb@chromium.org
The number of indexed declarative rules provided by an extension manifest
for the Declarative Net Request API. This is emitted whenever an extension's
json ruleset is indexed. This may happen when a packed extension is
installed, an unpacked extension is loaded, an extension's ruleset is re-
indexed, due to corruption, etc.
karandeepb@chromium.org
lazyboy@chromium.org
Describes the different cases pertaining to initiator checks used by the
Declarative Net Request Page Whitelisting API. Emitted whenever an extension
ruleset is evaluated for a main frame sub-resource request.
karandeepb@chromium.org
lazyboy@chromium.org
Indicates whether reindexing of the Declarative Net Request ruleset was
successful. Called whenever the JSON ruleset for an extension is reindexed,
e.g. on ruleset corruption.
Deprecated May 2018. Replaced with
Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions
karandeepb@chromium.org
Time taken to evaluate whether a network request should be blocked as per
the Declarative Net Request API. This includes the time taken to evaluate
all the extension rulesets. Emitted whenever a non-sensitive network request
is seen by the Extension System.
karandeepb@chromium.org
Time taken to evaluate whether a network request should be blocked for a
single extension ruleset. Emitted for each network request that is visible
to the extension.
karandeepb@chromium.org
Time taken to evaluate whether a network request should be redirected for a
single extension ruleset. Emitted for network requests visible to the
extension.
Deprecated May 2018. Replaced with
Extensions.DeclarativeNetRequest.EvaluateRequestTime.AllExtensions
karandeepb@chromium.org
Time taken to evaluate whether a network request should be redirected as per
the Declarative Net Request API. This includes the time taken to evaluate
all the extension rulesets. Emitted for non-sensitive network requests seen
by the Extension System.
Please list the metric's owners. Add more owner tags as needed.
Time spent until rules storage delegate gets ready.
karandeepb@chromium.org
Whether a network request from a guest webview has any declarative web
request rules that need to be evaluated. Emitted whenever a network request
from a guest webview is received at the network layer.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Number of extensions referenced in the depricated external extensions source
at path chrome::DIR_DEPRICATED_EXTERNAL_EXTENSIONS.
There is no such thing as an extension dialog.
Please list the metric's owners. Add more owner tags as needed.
The time for a dialog-hosted extension to load.
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per blessed
extension context (chrome-extension://... origins within Extension
processes, like background pages, options pages, popups).
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per blessed web page
context (hosted apps).
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per content script
context.
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per content script
context. This histogram measures the time to install Extension Javascript
bindings in a context for a platform app enabled on the Chrome OS lock
screen.
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per unblessed
extension context (chrome-extension://... origins hosted in iframes).
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings in an unknown type
of context (this should never happen other than in bizarre circumstances).
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per web page context
(just the chrome.app, chrome.webstore, and possibly chrome.runtime APIs).
rdevlin.cronin@chromium.org
Part of the suite of Extensions.DidCreateScriptContext_* metrics. Records
the time taken to install Extension JavaScript bindings per WebUI context
(chrome://extensions and so forth).
rdevlin.cronin@chromium.org
Records the time taken to install Extension JavaScript bindings per service
worker context.
rdevlin.cronin@chromium.org
Records the Chrome channel when JavaScript exceptions are not gracefully
dealt with, and suppressed by C++ instead. These are exceptions generated
(or simply not caught and gracefully recovered) in our own internal
JavaScript, not from JavaScript code written by developers (that which is
typically hosted in CRX files). This should be 0 for unstable channels like
canary and dev, because we try *not* to suppress errors and instead kill the
renderer and generate a crash report. However, at times we need to suppress
even those. Note that this histogram is intended to be tracked over time,
per channel, to observe crash rates. Comparisons between
stable/beta/dev/canary are unlikely to be meaningful.
rdevlin.cronin@chromium.org
The number of extensions that are disabled at browser startup.
rdevlin.cronin@chromium.org
The number of extensions that are disabled at browser startup due to
permissions increases.
Deprecated 03/2017 because miscounting IGNORE histogram entry. This error is
fixed with DisabledUIUserResponse2.
rdevlin.cronin@chromium.org
User response to the dialog shown when an extension is disabled due to an
update requiring more permissions.
catmullings@chromium.org
User response to the dialog shown when an extension is disabled due to an
update requiring more permissions. A count is recorded when the user takes
an action on the dialog (re-enable or remove the extension) or ignores the
dialog.
Deprecated 03/2017 because miscounting IGNORE histogram entry. This error is
fixed with DisabledUIUserResponseRemoteInstall2.
mek@chromium.org
User response to the dialog shown when an extension is disabled due to it
having been installed remotely.
catmullings@chromium.org
User response to the dialog shown when an extension is disabled due to it
having been installed remotely. A count is recorded when the user takes an
action on the dialog (re-enable or remove the extension) or ignores the
dialog.
asargent@chromium.org
The count of disabled extensions at startup grouped by disble reason from
disable_reason::DisableReason. When an extension is disabled, it can be for
one or more reasons (although typically just one), so the sum of these may
be greater than 'Extensions.Disabled' which is a count of the number of
unique extensions that are disabled.
rdevlin.cronin@chromium.org
The state of the toolbar icon for the docs offline extension (visible in the
toolbar, overflowed in the menu, or the extension is disabled). Recorded
once per startup per (non-incognito) profile.
Obsolete since the enhanced bookmarks manager is no longer using an event
page.
wittman@chromium.org
The number of event listeners the Enhanced Bookmarks Manager has, measured
at profile startup. A value of 0 implies that Chrome has a general bug with
event page management, since the bookmarks manager should always have at
least one event listener - but a bug with event page management that affects
the bookmarks manager is particularly dire.
asargent@chromium.org
If opening the CRX file for unpacking fails, this integer is the error code
given by the OS.
rdevlin.cronin@chromium.org
The number of extensions with event pages that have no registered event
listeners at profile startup. (This may indicate something has gone wrong;
such event pages will never get started.)
Replaced by Extensions.EventPageActiveTime2.
rdevlin.cronin@chromium.org
The time an extension's event page has spent loaded.
rdevlin.cronin@chromium.org
The time between an extension's event page loading its first URL and the
event page later shutting down.
rdevlin.cronin@chromium.org
The time an extension's event page has spent unloaded.
Replaced by Extensions.EventPageLoadTime2.
rdevlin.cronin@chromium.org
The time for an extension's event page to load.
rdevlin.cronin@chromium.org
The time taken for an extension's event page to load its initial URL.
rdevlin.cronin@chromium.org
Recorded every time an event is dispatched to an extension.
rdevlin.cronin@chromium.org
Recorded every time an event is dispatched to a *component* extension.
Otherwise identical to Extensions.Events.Dispatched.
mfoltz@chromium.org
Recorded every time an event is dispatched to a *component* extension with a
suspended event page. Otherwise identical to
Extensions.Events.DispatchWithSuspendedEventPage.
rdevlin.cronin@chromium.org
Recorded every time an event is dispatched to an extension with a persistent
background page. The event may or may not have been dispatched to the
background page itself, for example it may have been dispatched to its
popup. When this metric is recorded, Extensions.Events.Dispatch will also be
recorded.
rdevlin.cronin@chromium.org
Recorded every time an event is dispatched to an extension with an event
page that was already running (i.e. at some point had been woken from its
suspended state, see Extensions.Events.DispatchWithSuspendedEventPage). The
event may or may not have been dispatched to the event page itself, for
example it may have been dispatched to its popup. When this metric is
recorded, Extensions.Events.Dispatch will also be recorded.
rdevlin.cronin@chromium.org
Recorded every time an event is dispatched to an extension with an event
page that was suspended. This implies that firing this event woke up the
event page. The event may or may not have been dispatched to the event page
itself, for example it may have been dispatched to its popup, but regardless
it will wake the event page. When this metric is recorded,
Extensions.Events.Dispatch will also be recorded.
achuith@chromium.org
Number of cached extensions on disk. Reported on Chrome OS during user
session start.
achuith@chromium.org
Total size of .crx files in cache on disk. Reported on Chrome OS during user
session start.
rdevlin.cronin@chromium.org
The amount of time taken to create a single extension object. This includes
parsing all the different extension manifest keys and initializating the
associated manifest data.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
rdevlin.cronin@chromium.org
True if the cache of the extension frame map was hit during access on the IO
thread.
rdevlin.cronin@chromium.org
True if the lookup for a frame in the extension frame map succeeded after a
cache miss.
rdevlin.cronin@chromium.org
The maximum number of ExtensionHosts (primarily background/event pages) that
were actively loading at any one time, within the first minute of Chrome
startup. Emitted exactly one minute after startup.
rdevlin.cronin@chromium.org
The maximum number of ExtensionHosts (primarily background/event pages) in
the queue awaiting being loaded (via an ExtensionHostQueue), within the
first minute of Chrome startup. Emitted exactly one minute after startup.
rdevlin.cronin@chromium.org
The total number of ExtensionHosts that completed loading in the first
minute of Chrome startup. Emitted exactly one minute after startup.
rdevlin.cronin@chromium.org
The total number of ExtensionHosts (primarily background/event pages) that
were added to a queue to start loading, within the first minute of Chrome
startup. These may or may not end up starting, let alone finishing,
depending on the queue behavior. Emitted exactly one minute after startup.
rdevlin.cronin@chromium.org
An extension has been installed.
rdevlin.cronin@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.
Deprecated 4/2016. ExtensionRendererState was replaced with
ExtensionFrameMap.
rdevlin.cronin@chromium.org
True if the cache for the ExtensionRendererState was hit during a lookup.
Please list the metric's owners. Add more owner tags as needed.
Length of the Extensions dir path inside the profile directory.
rdevlin.cronin@chromium.org
Time taken for the ExtensionService to initialize, including the time it
takes to load the extensions for the service's profile and parse their
manifests. This happens during startup and also any time a new profile is
loaded.
rdevlin.cronin@chromium.org
Time taken for the ExtensionService to notify all ready listeners that the
extension system is now ready. This happens as part of the total
initialization time of ExtensionService, measured in
Extensions.ExtensionServiceInitTime.
rdevlin.cronin@chromium.org
An extension has been uninstalled.
mxnguyen@chromium.org
The number of extensions that are checked for update. This number is emitted
right before the extensions are split between the current extension updater
and the unified extension updater (if used).
mxnguyen@chromium.org
The number of extensions that are passed over to the extension updater for
update check. Triggered when the extension updater starts doing update
check.
mxnguyen@chromium.org
The number of extensions that have updates in an update check session.
Triggered when the extension updater found an update for an extension.
mxnguyen@chromium.org
Records the update results of extensions in an extension updater session,
grouped by ExtensionUpdaterUpdateResult.
Please list the metric's owners. Add more owner tags as needed.
Records what happens to extensions that are sideloaded, grouped by the
ExternalExtensionEvent enum.
Please list the metric's owners. Add more owner tags as needed.
The number of sideloaded apps/extensions loaded on startup grouped by
enabled/disabled state.
Please list the metric's owners. Add more owner tags as needed.
Number of extensions referenced in the external extensions source at path
chrome::DIR_EXTERNAL_EXTENSIONS.
rdevlin.cronin@chromium.org
Whether or not the uninstallation of an external extension succeeded.
Triggered when the external install warning is shown to the user and the
user selects to remove the extension.
rkaplow@chromium.org
The amount of time that elapsed during extensions::FeatureProvider::Static.
Only measured while in the browser process.
rdevlin.cronin@chromium.org
The number of extensions (and friends) that could have been given access to
the file:// scheme, and were, for users that have at least one extension
that could have been given access. This excludes anything that doesn't show
up in chrome://extensions (platform apps, hosted apps, component
extensions), policy-installed extensions, and unpacked extensions. See also
Extensions.FileAccessNotAllowed.
rdevlin.cronin@chromium.org
The number of extensions (and friends) that could have been given access to
the file:// scheme, but weren't, for users that have at least one extension
that could have been given access. This excludes anything that doesn't show
up in chrome://extensions (platform apps, hosted apps, component
extensions), policy-installed extensions, and unpacked extensions. See also
Extensions.FileAccessAllowed.
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.
poromov@chromium.org
The amount of time elapsed during installation of enterprise policy forced
extensions.
poromov@chromium.org
Number of enterprise policy forced extensions that are not installed after 5
minutes if at least one of policy forced extensions is not yet enabled.
poromov@chromium.org
Number of enterprise policy forced extensions that are not enabled after 5
minutes timeout, while might be already installed.
Please list the metric's owners. Add more owner tags as needed.
Number of apps/extensions loaded on startup with an inconsistent "from
webstore" state. This means an item that is flagged as from_webstore,
but with either a non-webstore update_url or an external install location.
rdevlin.cronin@chromium.org
Number of calls to extension functions.
rdevlin.cronin@chromium.org
Recorded when an extension function call fails and finishes execution. The
suffix indicates the exact bucket the function is in. See also
Extensions.Functions.FailedTotalExecutionTime.
rdevlin.cronin@chromium.org
The total amount of time it took to execute an extension function that
failed from the time the extension function is called to the time the
function responds. Note that since some extension functions are inherently
slow (anything that requires user interaction, for instance), this is not a
definitive source for function performance.
rdevlin.cronin@chromium.org
The amount of time it takes to handle a response for an extension API
request. Recorded on the renderer side once we receive the response IPC from
the browser and have deserialized the arguments and passed them to the JS
context. Only recorded if the response is successfully handled.
rdevlin.cronin@chromium.org
The amount of time it takes to start an extension API request. Recorded on
the renderer side after we perform JS pre-processing, but includes all
serialization and dispatching. Only recorded if the request is successfully
dispatched.
rdevlin.cronin@chromium.org
Recorded when an extension function call succeeds and finishes execution.
The suffix indicates the exact bucket the function is in. See also
Extensions.Functions.SucceededTotalExecutionTime.
rdevlin.cronin@chromium.org
The total amount of time it took to execute an extension function that
succeeded from the time the extension function is called to the time the
function responds. Note that since some extension functions are inherently
slow (anything that requires user interaction, for instance), this is not a
definitive source for function performance.
rdevlin.cronin@chromium.org
The synchronous amount of time an extension function takes. Note that many
extension functions run asynchronously; see also
Extensions.Functions.[Succeeded|Failed]TotalExecutionTime.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
What happens when the extensions system tries to get a temp dir to unpack
in?
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@chromium.org
The number of extensions (and friends) that could have been allowed in
incognito, and were, for users that have at least one extension that could
have been allowed. This excludes anything that doesn't show up in
chrome://extensions (platform apps, hosted apps, component extensions),
policy-installed extensions, and unpacked extensions. See also
Extensions.IncognitoNotAllowed.
rdevlin.cronin@chromium.org
The number of extensions (and friends) that could have been allowed in
incognito, but weren't, for users that have at least one extension that
could have been allowed. This excludes anything that doesn't show up in
chrome://extensions (platform apps, hosted apps, component extensions),
policy-installed extensions, and unpacked extensions. See also
Extensions.IncognitoAllowed.
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.
rdevlin.cronin@chromium.org
The amount of time for a CSS file to be injected into a page.
ksakamoto@chromium.org
Time taken to execute all scripts for one location within an extension.
Recorded every time content scripts injected by extensions are executed.
Unlike Extensions.InjectScriptTime, this includes execution time of
asynchronously injected scripts.
rdevlin.cronin@chromium.org
Number of blocking scripts injected at document end by extensions.
rdevlin.cronin@chromium.org
Number of scripts injected at document end by extensions.
rdevlin.cronin@chromium.org
Time taken to inject all scripts at document end by extensions. Not reported
if scripts are executed asynchronously.
rdevlin.cronin@chromium.org
Number of blocking scripts injected at document idle by extensions.
rdevlin.cronin@chromium.org
Number of scripts injected at document idle by extensions.
rdevlin.cronin@chromium.org
Time taken to inject all scripts at document idle by extensions. Not
reported if scripts are executed asynchronously.
Deprecated 03/2017 in favor of Extensions.InjectedScriptExecutionTime.
rdevlin.cronin@chromium.org
Time taken to inject all scripts by extensions.
rdevlin.cronin@chromium.org
Number of blocking scripts injected at document start by extensions.
rdevlin.cronin@chromium.org
Number of css files injected by extensions.
rdevlin.cronin@chromium.org
Number of scripts injected at document start by extensions.
rdevlin.cronin@chromium.org
Time taken to inject css/scripts at document start by extensions. Not
reported if scripts are executed asynchronously.
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.
rdevlin.cronin@chromium.org
Installs grouped by the location property in prefs.
rdevlin.cronin@chromium.org
Installs grouped by Extension::HistogramType.
rdevlin.cronin@chromium.org
The number of extensions and themes loaded at profile open.
rdevlin.cronin@chromium.org
Time taken to load all component extensions at profile open. This happens as
part of the total initialization time of ExtensionService, measured in
Extensions.ExtensionServiceInitTime.
rdevlin.cronin@chromium.org
Time taken to load all non-component extensions at profile open. This
happens as part of the total initialization time of ExtensionService,
measured in Extensions.ExtensionServiceInitTime.
rdevlin.cronin@chromium.org
Time taken to load all non-component extensions at profile open and record
metrics. This happens as part of the total initialization time of
ExtensionService, measured in Extensions.ExtensionServiceInitTime.
rdevlin.cronin@chromium.org
The number of apps loaded by each user at profile open.
rdevlin.cronin@chromium.org
The number of externally managed apps loaded by each user at profile open.
rdevlin.cronin@chromium.org
The number of user-installed apps loaded by each user at profile open.
rdevlin.cronin@chromium.org
The number of browser action extensions loaded at profile open.
Deprecated as of 4/2015. Replaced by ManagedUsers.Whitelist.Count.
asargent@chromium.org
The number of content-pack extensions loaded at profile open.
calamity@chromium.org
The creation flags of all extensions loaded at profile open grouped by
Extension::InitFromValueFlags.
rdevlin.cronin@chromium.org
The number of extensions loaded at profile open.
rdevlin.cronin@chromium.org
The number of externally managed extensions loaded at profile open.
rdevlin.cronin@chromium.org
The number of user-installed extensions loaded at profile open.
rdevlin.cronin@chromium.org
The number of externally managed extensions and apps loaded at profile open.
rdevlin.cronin@chromium.org
The number of hosted apps loaded by each user at profile open.
rdevlin.cronin@chromium.org
The number of extensions that had neither a page nor browser action
specified in their manifest. Recorded at profile open.
rdevlin.cronin@chromium.org
The number of enabled extensions or apps the user has installed that do not
update from the Chrome Web Store. Recorded during profile initialization.
rdevlin.cronin@chromium.org
The number of legacy packaged apps loaded by each user at profile open.
rdevlin.cronin@chromium.org
The number of platform apps loaded at profile open.
rdevlin.cronin@chromium.org
The number of themes loaded at profile open.
rdevlin.cronin@chromium.org
The number of extensions loaded at profile open grouped by
Extension::HistogramType.
rdevlin.cronin@chromium.org
The number of converted user scripts loaded at profile open.
isandrk@chromium.org
jhastings@chromium.org
Records requests to enter or exit locked fullscreen mode through extension
APIs. Used only on Chrome OS.
ksakamoto@chromium.org
The amount of time taken to inject content scripts. If multiple scripts are
injected within a single task, this records the time taken to execute all
the scripts.
This metric only logs tasks longer than 50 milliseconds. This threshold
aligns with the definition of "long task" in Long Tasks API
(https://w3c.github.io/longtasks/).
Note that this histogram itself doesn't tell you what percentage of content
scripts are greater than 50 ms. See Extensions.Inject{Start,End,Idle}_Time
and Extensions.InjectedScriptExecutionTime.* for the overall distribution.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a google.com domain, before eventually giving up.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a non google.com domain, before eventually giving up.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a google.com domain, before eventually succeeding.
Please list the metric's owners. Add more owner tags as needed.
Number of times chrome retried to download an extension update manifest with
a url on a non google.com domain, before eventually succeeding.
Please list the metric's owners. Add more owner tags as needed.
Number of extension loads on startup where it is necessary to reload the
mainfest because the locale has changed.
Please list the metric's owners. Add more owner tags as needed.
Number of extension loads on startup where it is not necessary to reload the
extension's manifest.
Please list the metric's owners. Add more owner tags as needed.
Number of extension loads on startup where it is necessary to reload the
manifest because the extension is unpacked.
rdevlin.cronin@chromium.org
The manifest version of each loaded extension.
rdevlin.cronin@chromium.org
The number of ports created in a given script context at a specific time.
Recorded once at the destruction of the script context (when no more ports
could be created) if and only if at least one port was created in the
context. Only includes ports to extension contexts (i.e., not ports created
to tabs or native apps).
rdevlin.cronin@chromium.org
The total amount of time between when an extension opens a new channel and
when it receives the global port id from the browser and can begin sending
messages.
rdevlin.cronin@chromium.org
The amount of synchronous time taken for the renderer to request an
extension message port id from the browser when a new channel is first
opened by an extension.
rdevlin.cronin@chromium.org
nharper@hromium.org
The behavior for including the TLS channel ID in the information sent with
extension messaging. Recorded once per opened channel.
redevlin.cronin@chromium.org
The size, in bytes, of a message sent from an extension using one of the
messaging APIs (e.g. chrome.runtime.sendMessage). All message sizes are
logged, but messages over 64 MB in size aren't sent.
rdevlin.cronin@chromium.org
The amount of time for the renderer to inform the browser process of a new
port being created with a certain id. This replaces the flow for
Extensions.Messaging.GetPortId[A]SyncTime.
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.
Never used. Added to source 06/2012. Removed from source and added here
09/2016.
Delay of network requests due to waiting for extension declarativeWebRequest
rules to be loaded from disk at startup.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it is automatically disabled
due to a permission increase (e.g., after an extension upgrade).
Deprecated as of 6/2015, replaced by Extensions.Permissions_AutoDisable3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it is automatically disabled
due to a permission increase (e.g., after an extension upgrade).
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed.
Deprecated as of 6/2015, replaced by Extensions.Permissions_Install3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was aborted, not
including installation errors and user cancels.
Deprecated as of 6/2015, replaced by Extensions.Permissions_InstallAbort3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was aborted, not
including installation errors and user cancels.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was canceled.
Deprecated as of 6/2015, replaced by Extensions.Permissions_InstallCancel3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation was canceled.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was loaded.
Deprecated as of 6/2015, replaced by Extensions.Permissions_Load3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was loaded.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was re-enabled from a
confirmation prompt.
Deprecated as of 6/2015, replaced by Extensions.Permissions_ReEnable3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was re-enabled from a
confirmation prompt.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@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.
Deprecated as of 6/2015, replaced by Extensions.Permissions_ReEnableAbort3.
rdevlin.cronin@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.
rdevlin.cronin@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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable was canceled from
the confirmation prompt.
Deprecated as of 6/2015, replaced by Extensions.Permissions_ReEnableCancel3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when the re-enable was canceled from
the confirmation prompt.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was uninstalled.
Deprecated as of 6/2015, replaced by Extensions.Permissions_Uninstall3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was uninstalled.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed through the
web store.
Deprecated as of 6/2015, replaced by
Extensions.Permissions_WebStoreInstall3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when it was installed through the
web store.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was aborted, not including installation errors and user cancels.
Deprecated as of 6/2015, replaced by
Extensions.Permissions_WebStoreInstallAbort3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was aborted, not including installation errors and user cancels.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was canceled.
Deprecated as of 6/2015, replaced by
Extensions.Permissions_WebStoreInstallCancel3.
rdevlin.cronin@chromium.org
rpaquay@chromium.org
The permissions present in an extension when installation from the web store
was canceled.
rdevlin.cronin@chromium.org
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.
rdevlin.cronin@chromium.org
The time taken between a user clicking on a button to open a popup, and the
popup finishing loading its initial URL. This is a good way to measure the
UI responsiveness of extension popups. It will be strictly larger than
Extensions.PopupLoadTime2, which only measures the time it takes to load -
there may be a delay between clicking and starting to load, for example, if
the popup's host got caught in a queue.
Replaced by Extensions.PopupLoadTime2.
rdevlin.cronin@chromium.org
The time for an Extension's popup to load.
rdevlin.cronin@chromium.org
The time taken for an extension popup to load its initial URL. This may not
include the time taken for an extension process to start, if the extension
already has a background page running. It does not necessarily correlate
with the amount of time since the popup was *clicked* either, since there
may be a delay between the user clicking and the loading started.
Extensions.PopupCreateTime measures this instead.
rdevlin.cronin@chromium.org
The time taken to start up persistent background pages for extensions in
ExtensionProcessManager when the extension system notifies that it is ready.
rdevlin.cronin@chromium.org
treib@chromium.org
Whether the DISABLE_PERMISSIONS_INCREASE disable reason was removed from an
extension while checking for a permissions increase. Recorded during startup
and on reload and update, for each extension that has the
DISABLE_PERMISSIONS_INCREASE reason.
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.
achuith@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.
Removed in September, 2016
Emitted when QuotaExceededError was called due to an extension using too
many bytes for a given setting. The number has no natural numerator
(normalizing factor) and thus is not particularly useful.
Removed in September, 2016
Emitted when QuotaExceededError was called due to an extension using too
many keys. The number has no natural numerator (normalizing factor) and
thus is not particularly useful.
Removed in September, 2016
Emitted when QuotaExceededError was called due to an extension using too
many bytes. The number has no natural numerator (normalizing factor) and
thus is not particularly useful.
alexmos@chromium.org
When the web-accessible resource check in
ChromeContentBrowserClientExtensionsPart::ShouldAllowOpenURL fails, this
records the reason for the failure. This check is performed on navigations
that utilize the OpenURL path as well as on transfers.
alexmos@chromium.org
When the web-accessible resource check in
ChromeContentBrowserClientExtensionsPart::ShouldAllowOpenURL fails, this
records the scheme of the SiteInstance that initiated the blocked load. This
check is performed on navigations that utilize the OpenURL path as well as
on transfers.
This has not been recorded since at least mid-2013.
asargent@chromium.org
The time one extension delays network requests at startup.
This has not been recorded since at least mid-2013.
rdevlin.cronin@chromium.org
The total time extensions delay network requests at startup.
rkaplow@chromium.org
The amount of time that elapsed during StorageFrontend::Init.
rdevlin.cronin@chromium.org
The amount of synchronous time spent retrieving an extension's message
bundle (the collection of its i18n resources) from the browser.
rdevlin.cronin@chromium.org
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
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).
ksakamoto@chromium.org
Time elapsed between two asynchronously-injected content script runs.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time taken to load a toolstrip.
mxnguyen@chromium.org
Records the error codes of the unified extension updater download errors.
These events are triggered when the extension updater fails to download the
extension update package of an extension, which can happen only after the
updater has successfuly determined that there is an update for the
extension.
mxnguyen@chromium.org
The number of extensions that are passed over to the unified extension
updater for update check. Triggered when the new extension updater starts
doing update check.
mxnguyen@chromium.org
Records the error codes of the unified extension updater update check
errors. These events are triggered only when the new extension updater gets
an error in the update check phase.
mxnguyen@chromium.org
Records the update results of extensions in an unified extension updater
session, grouped by ExtensionUpdaterUpdateResult.
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.
rdevlin.cronin@chromium.org
The source for the extension uninstall. This is only recorded if an
uninstall dialog is shown to the user (i.e., it is not recorded for internal
"cleanups").
rdevlin.cronin@chromium.org
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.
Deprecated 3/2018 in https://crbug.com/357781 with the removal of the
extensions-update-frequency command line flag.
catmullings@chromium.org
Logs whether or not the extensions-update-frequency command line flag is
used. Recorded at profile creation if extensions autoupdate is enabled.
mxnguyen@chromium.org
Counts the number of entries with the same extension ID found in the update
manifest of an update check request. When the update manifest does not
contain any update entry for an extension ID in the update check request,
the count will be 0.
mxnguyen@chromium.org
The number of prodversionmin attributes appearing in an update manifest of
an update check request.
Please list the metric's owners. Add more owner tags as needed.
The number of extensions that were updated at browser startup.
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.
karandeepb@chromium.org
rdevlin.cronin@chromium.org
Describes the different cases pertaining to host permissions check for the
initiator URL of a network request. This is emitted whenever an extension is
found to have access to a request url, when checked by the WebRequest API.
rockot@chromium.org
Tracks whether any interesting response header modifications were made for
each request seen by the Web Request API. Logged for every network request
as long as one or more enabled extensions is using a declarative or blocking
filter to process onHeadersReceived events.
This histogram is temporary, for investigating https://crbug.com/827582. It
can probably be removed by M69.
rockot@chromium.org
For every network request visible to the Web Request API, this indicates
whether any registered declarative rules or event listeners observed the
onBeforeSendHeaders event.
This histogram is temporary, for investigating https://crbug.com/827582. It
can probably be removed by M69.
rockot@chromium.org
For every network request visible to the Web Request API, this indicates
whether any registered declarative rules or event listeners observed the
onHeadersReceived event.
This histogram is temporary, for investigating https://crbug.com/827582. It
can probably be removed by M69.
rockot@chromiumorg
Whether either or both of the special Accept-Language or User-Agent request
headers were removed by an extension using the Web Request API. Logged for
every network request as long as one or more enabled extensions is using a
declarative or blocking filter to process onBeforeSendHeaders events.
This histogram is temporary, for investigating https://crbug.com/827582. It
can probably be removed by M69.
yhirano@chromium.org
Whether cookies on a websocket connection are modified in
OnBeforeSendHeaders.
This histogram is temporary, for investigating https://crbug.com/827582.
yhirano@chromium.org
Whether cookies on a websocket connection are modified in OnHeadersReceived.
This histogram is temporary, for investigating https://crbug.com/827582.
yhirano@chromium.org
ricea@chromium.org
Whether certain headers are modified in OnBeforeSendHeaders.
yhirano@chromiumorg
Tracks request headers modifications on a websocket connection in
OnBeforeSendHeaders.
This histogram is temporary, for investigating https://crbug.com/827582.
yhirano@chromiumorg
Whether response headers on a websocket connection are modified in
OnHeadersReceived.
This histogram is temporary, for investigating https://crbug.com/827582.
karandeepb@chromium.org
Counts the number of times an action is requested by extensions as part of
the Web Request API. For a given web request stage, multiple actions may be
logged.
karandeepb@chromium.org
Number of enabled extensions which have requested the
"webRequestBlocking" permission. Includes all kinds of extensions,
including component and unpacked extensions. Recorded during profile
initialization.
Deprecated as of 11/2017. No longer relevant after refactoring.
rdevlin.cronin@chromium.org
Whether or not the render frame lookup for a given webRequest event
succeeded.
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.
rdevlin.cronin@chromium.org
The amount of time between starting the provisional load and fully loading
the document in the main frame of the chrome://extensions page. This
corresponds to the WebContentsObserver::DocumentLoadedInFrame method.
rdevlin.cronin@chromium.org
The amount of time between starting the provisional load and having
completed the onload handler in the main frame of the chrome://extensions
page. This corresponds to the
WebContentsObserver::DocumentOnLoadCompletedInMainFrame method.
Please list the metric's owners. Add more owner tags as needed.
Records whether adding a new/updated extension to the install verifier
succeeded.
Please list the metric's owners. Add more owner tags as needed.
The outcome of a call to ExtensionService::VerifyAllExtensions, whether it
was called for bootstrapping or another reason (extension
installed/uninstalled, etc.).
yamaguchi@google.com
Records the reason why the ZIP unpacker extension was disabled when the
service attempted to re-enable the extension upon startup. Each entry
indicates that the extension was disabled unintentionally and a fix was
attempted.
Please list the metric's owners. Add more owner tags as needed.
When loading the chrome://extensions page, this records whether we decided
to do a verification check against the server (because the user had one or
more extensions disabled due to verification failure).
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).
pmarko@chromium.org
rogerta@chromium.org
Record the validity of |rlz_embargo_end_date| in RW_VPD. This is recorded
when the VPD value is accessed, which may be multiple times in the same
chrome invocation. This is not recorded when the VPD value is missing.
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.
Deprecated as of 12/2017.
fhorschig@chromium.org
Records the number of favicon link tags on a page once the page has finished
loading. The count includes the automatically added favicon.ico entry.
Deprecated as of 12/2017.
fhorschig@chromium.org
Records the number of favicon link tags with a non empty sizes attribute
once the page has finished loading.
Deprecated as of 12/2017.
fhorschig@chromium.org
Records the number of apple-touch-icon and apple-touch-icon-precomposed link
tags once the page has finished loading.
Deprecated as of 12/2017.
fhorschig@chromium.org
Records the number of icons requested until the best-fitting candidate was
found or there were no candidates left to check. More than 15 attempts are
unlikely and will be stored in overflow bucket 16. Less than 1 attempt means
an error happened; these cases are in bucket 0.
Deprecated as of 12/2017.
fhorschig@chromium.org
Records whether a download succeeded, failed or was skipped because it has
failed previously.
mastiz@chromium.org
Records the number of large icons that were fetched from the local cache
(e.g. during NTP impression), where the URL (of the page or the icon)
matches a hardcoded blacklist. Suspicious mismatches are reported as errors.
jkrcal@chromium.org
Records the size (concretely the width) in pixel of the favicon downloaded
from Google favicon server (size 0 denotes that download has failed).
jkrcal@chromium.org
Records the size (concretely the width) in pixel of the favicon that is used
to generate a fallback style in the case when large enough favicon is not
available (size 0 denotes that no favicon is available at all).
skym@chromium.org
The scheduler watches for various triggers, which cause it to decide if a
refresh is currently warranted or not. This histogram is emitted when a
trigger causes a refresh.
skym@chromium.org
When NTP is opened, the scheduler host tells the Feed library how to act, if
the existing content should be shown, immediately or with timeout, and if a
refresh request should be started.
afakhry@chromium.org
Records the source that requested showing the feedback app.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: Counts the number of directory-changed events,
bucketed by the RootType of the directory newly displayed.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser - Specific actions taken by user such initiating
cloud import, canceling import, selecting a directory, or opting-in to
Drive>Photos sync.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser opening mode.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: time to scan a directory. Measured on every File
Browser directory change.
sashab@chromium.org
slangley@chromium.org
Tracks whether download destination is set to a Google Drive folder when the
download destination is changed by the user in the settings page.
sashab@chromium.org
slangley@chromium.org
Tracks whether download destination is set to a Google Drive folder on
startup.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: number of files and directories in the Downloads
directory (not including the contents of nested directories). Computed every
time the File Browser current directory changes to Downloads.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: this is recorded when the user adds a folder
shortcut.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: number of saved folder shorcuts. This is recorded
when the Files app is launched.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: this is recorded when the user clicks or selects a
folder shortcut and is navigated to the target folder.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: this is recorded when the user removes a folder
shortcut.
The bug which the UMA was investigating got fixed.
sashab@chromium.org
slangley@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.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: time from the DiskRemoved event to the Suspend
event. The UMA is added temporarily for crbug.com/433734.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser is an built-in extension without a background page.
Its main.html file is loaded every time the user opens a File Browser tab or
a file chooser dialog. The file is fairly large and the initialization is
pretty expensive.
sashab@chromium.org
slangley@chromium.org
Chrome OS Files App: The locations (root types) of non-top-level entries
when they are expanded or collapsed (expand icon clicked) in the directory
tree.
sashab@chromium.org
slangley@chromium.org
Chrome OS Files App: The locations (root types) of top-level entries (root
entries) when they are expanded or collapsed (expand icon clicked) in the
directory tree.
sashab@chromium.org
slangley@chromium.org
Chrome OS Files App: The locations (root types) of non-top-level entries
when they are clicked in the directory tree.
sashab@chromium.org
slangley@chromium.org
Chrome OS Files App: The locations (root types) of top-level entries (root
entries) when they are clicked in the directory tree.
sashab@chromium.org
slangley@chromium.org
Chrome OS Files App: The commands selected in the menu by the files app.
joelhockey@google.com
sashab@google.com
Chrome OS File Browser: time to start and mount the crostini container in
order to show Linux Files.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: The locations (root types) of files which are opened
by the file picker.
Deprecated 4/2013, and replaced by FileBrowser.ViewingFileType.
sashab@chromium.org
slangley@chromium.org
File types that were tried to be opened through browser.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: time to display an image. Measured from the moment
the user selected the image till the moment it is displayed (not counting
the low resolution preview).
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: the type of the file opened.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: the way the image has been loaded.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: time to load an image from a file.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: the result of a file save operation.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: time to save an image to a file.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: size of an image file in megabytes. Measured on
every image load.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: size of an image in megapixels. Measured on every
image load.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Editor: the button which the user clicked.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Import flow: action chosen in the Action Choice dialog for
the external device.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Import flow: the number of photos imported. Measured on
every successfull import operation.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Import flow: the percent of photos imported among all the
photos on the device. Measured on every successfull import operation.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Import flow: time to load the action dialog. Measured
between the moment window appears and the moment user see all available
actions for the device.
sashab@chromium.org
slangley@chromium.org
Chrome OS Photo Import flow: time to scan the external device.
sashab@chromium.org
slangley@chromium.org
File dialog type (e.g. Full page, Save as file) when quick view is launched.
sashab@chromium.org
slangley@chromium.org
File types that were tried to be opened with quick view.
sashab@chromium.org
slangley@chromium.org
File types that were selected when quick view is launched.
sashab@chromium.org
slangley@chromium.org
The volume type where quick view is opened.
sashab@chromium.org
slangley@chromium.org
How quick view was opened.
sashab@chromium.org
slangley@chromium.org
Time to load a recently modified file list from Media Views. It is triggered
when the user opens or reloads Recent view in the Files app.
sashab@chromium.org
slangley@chromium.org
Time to load a recently modified file list from Downloads. It is triggered
when the user opens or reloads Recent view in the Files app.
sashab@chromium.org
slangley@chromium.org
Time to load a recently modified file list from Drive. It is triggered when
the user opens or reloads Recent view in the Files app.
sashab@chromium.org
slangley@chromium.org
Time to load a recently modified file list from all sources. It is triggered
when the user opens or reloads Recent view in the Files app.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: the reason why the suggest apps dialog was closed.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: whether the Webstore item user selected was
successfully installed or not.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: whether the initialization of the dialog succeeded
or not.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: time to load the suggest apps dialog. Measured
between the moment window appears and the moment all the contents in the
dialog including the Chrome Webstore widget are ready.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: number of Team Drives a user has available in the
Files app. Computed every time the File Browser is opened (including file
picker dialogs). NOTE: This data is biased towards users that use the Files
App more often.
sashab@chromium.org
slangley@chromium.org
Chrome OS Files App: Recorded when the Grid View/List View toggle menu icon
is selected.
sashab@chromium.org
slangley@chromium.org
File types that were tried to be viewed through browser. This is recorded
when the user tries to view a file from the Files app.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: The locations (root types) of files which are opened
in stand-alone mode. This does not include files opened in file picker mode.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: The type of the handler to be used to open files.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: counts the number of times volumes are mounted for
each volume type.
sashab@chromium.org
slangley@chromium.org
Chrome OS File Browser: counts the number of times ZIP file was opened or
created, categorized by component extensions and its operation types.
mek@chromium.org
For each FileReaderSync instance records the type of the web worker that
created the instance.
tzik@chromium.org
The result of FileSystemDirectoryDatabase initialization.
tzik@chromium.org
The result of FileSystemDirectoryDatabase repair.
tzik@chromium.org
The success or the cause of failure for each call to OpenFileSystem().
tzik@chromium.org
The result of opening a filesystem.
tzik@chromium.org
The result of opening a non-throttled filesystem.
tzik@chromium.org
The result of FileSystemOriginDatabase initialization.
nick@chromium.org
Logged when we fail the permission validation of the filesystem URL origin,
from ChildProcessSecurityPolicy::HasPermissionsForFileSystemFile. This is
not expected to happen in normal operation.
tzik@chromium.org
Number of origins that have persistent filesystem. Measured when the Quota
system queries the filesystem subsystem about its entire usage, which
usually happens when one of the storage subsystem methods is called for the
first time.
tzik@chromium.org
Number of origins that have temporary filesystem. Measured when the Quota
system queries the filesystem subsystem about its entire usage, which
usually happens when one of the storage subsystem methods is called for the
first time.
olivierrobin@chromium.org
Counts the number of times First Run experience was triggered by another
application launching Chrome. This metric measures the effectiveness of
Smart App Banner promotions on installation of Chrome.
hcarmona@chromium.org
This histogram records when a user interacted with the Google Apps new user
experience. We record both accept and reject but are not recording when a
user ignored the prompt completely. Users can ignore this prompt by closing
the tab or navigating away, we record when the prompt is shown.
hcarmona@chromium.org
This histogram records what Google apps were selected as part of the Google
Apps New User Experience. Histogram is only recorded when a user accepts the
prompt to add Google Apps.
jlebel@chromium.org
Result of sentinel file has been written.
jlebel@chromium.org
File error when the sentinel file was not written.
msarda@chromium.org
Result of the sign in flow during Mobile first run.
pkl@chromium.org
WARNING: The list of actions used to identify new tasks hasn't been
attentively updated for several years (as of 2017). Some actions that
should likely be considered new tasks are probably missing. Take this
histogram with a grain of salt.
The amount of time (in seconds) that the app was in the background before
the user started it
tedchoc@chromium.org
The amount of time (in minutes) that the app was in the background before
the user started it (via an ACTION_MAIN intent) and performed a user action
that describes the intent of resuming the app. Only recorded if the action
took place within the first 10 seconds of starting Chrome. The actions are
further described in the FirstUserActionTypes suffix.
pkl@chromium.org
WARNING: The list of actions used to identify new tasks hasn't been
attentively updated for several years (as of 2017). Some actions that
should likely be considered new tasks are probably missing. Take this
histogram with a grain of salt.
On handsets, the type of the first user action performed after the app was
started or unbackgrounded.
pkl@chromium.org
WARNING: The list of actions used to identify new tasks hasn't been
attentively updated for several years (as of 2017). Some actions that
should likely be considered new tasks are probably missing. Take this
histogram with a grain of salt.
On tablets, the type of the first user action performed after the app was
started or unbackgrounded.
Deprecated as of 01/2016. The error has been fixed by GCM. (crbug/580367)
khushalsagar@chromium.org
Result of a message received by the GcmReceiver on Android.
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.
Deprecated as of 03/2018 (M67).
zea@chromium.org
Whether the GCM connection was made via a proxy or not.
zea@chromium.org
URL response and error codes from GCM disconnect events.
zea@chromium.org
Number of connections made to each specific MCS endpoint.
zea@chromium.org
URL response and error codes from GCM connection attempts.
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.
peter@chromium.org
Success rate of writing new keying material to the GCM key store.
peter@chromium.org
Result of decryption on a received GCM message, which includes unencrypted
messages, successfully decrypted messages and decryption failures.
nator@chromium.org
Result of upgrading GCM Key Store Database from deprecated format to current
format. We upgrade the GCM Key store when it first initialized, if it
contains any EncryptionData object with a KeyPair in it, and then record
whether the upgrade was successful in this metric.
peter@chromium.org
Success rate of reading keying material from the GCM key store.
peter@chromium.org
Success rate of initializing the LevelDB back-end of the GCM key store.
peter@chromium.org
Success rate of loading existing keying material in the GCM key store.
peter@chromium.org
Success rate of removing keying material from the GCM key store.
cmumford@chromium.org
The result of a database open attempt by the GCM store.
juyik@chromium.org
Interval between two successive received data message bursts.
peter@chromium.org
Number of DATA_MESSAGE messages received from Google Cloud Messaging for
which a matching registration exists. Recorded when processing the received
message. Prior to M56 this also counted received DELETED_MESSAGES messages
(whether or not a registration existed).
peter@chromium.org
Records whether a non-empty collapse_key token is set for each received
DATA_MESSAGE message from Google Cloud Messaging for which a matching
registration exists. Recorded while processing the received message.
No longer used starting with Chrome 61 as the check was removed.
peter@chromium.org
Records whether a matching registration was found for each received
DATA_MESSAGE message from Google Cloud Messaging. Recorded while processing
the received message. Prior to M56 this also counted received
DELETED_MESSAGES messages.
peter@chromium.org
For every DELETED_MESSAGES message received from Google Cloud Messaging
(whether or not a matching registration exists), this records the provided
count of how many messages were simultaneously deleted, or zero if the count
is unknown.
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).
peter@chromium.org
Number of SEND_ERROR messages received from Google Cloud Messaging. Recorded
when processing the received message.
jianli@chromium.org
Status code of loading from the persistent GCM store.
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.
peter@chromium.org
Number of connection events which have not been sent to GCM. This is
recorded only at the time of shutdown to capture the events which are being
lost due to shutdown. Because this is recorded at shutdown, this is not
guaranteed to be complete and should be treated as a best effort record.
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.
nator@chromium.org
Reports the status of cached GCM registration. This is recorded when a new
registration request is considered on the GCM client.
jianli@chromium.org
Length of time taken to complete a GCM registration request successfully. If
the registration is retried multiple times, the length of time is counted
for the last successful retry.
peter@chromium.org
Number of registration requests sent to Google Cloud Messaging. Recorded
immediately after the request has started.
juyik@chromium.org
Status code of the outcome of a GCM registration request. The Unknown error
case was split up in M56 (merged mid-beta to M55) to separate out the
Response parsing failed, Internal server error, Quota exceeded, and Device
has too many registrations cases.
jianli@chromium.org
Number of retries before a GCM registration succeeds.
jianli@chromium.org
Number of sender IDs specified in a registration request.
Deprecated in M56 in favor of GCM.ResetStoreError
jianli@chromium.org
Reports the problem encountered when resetting the GCM store.
zea@chromium.org
Reports the problem encountered when resetting the GCM store.
zea@chromium.org
Number of unacknowledged incoming messages restored from the persistent
store at startup.
zea@chromium.org
Number of pending outgoing messages restored from the persistent store at
startup.
jianli@chromium.org
Number of registrations restored from the persistent store at startup.
peter@chromium.org
Result of sending an upstream message through Google Cloud Messaging.
Recorded when the message has either been queued, sent, or has been dropped
because it expired or an error happened.
zea@chromium.org
Success indicates successfully destroying the GCM persistent store. Failure
indicates a failure destroying the persistence store. GCM store will be
destroyed when the profile has been signed out.
zea@chromium.org
Size of the GCM persistent store in kilobytes at startup.
zea@chromium.org
Success indicates successfully updating the GCM persistent store on message
update. Failure indicates a failure updating the persistence store.
zea@chromium.org
Time elapsed from machine suspend until resume.
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.
peter@chromium.org
Number of unregistration requests sent to Google Cloud Messaging. Recorded
immediately after the request has started.
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
Records the action performed by an existing user when prompted to authorize
the use of location by Chrome.
mvanouwerkerk@chromium.org
Records the action performed by a new user when prompted to authorize the
use of location by Chrome.
mvanouwerkerk@chromium.org
Whether high accuracy geolocation information was requested.
kcarattini@chromium.org
dominickn@chromium.org
For Geolocation requests from the omnibox on Android, the time since the
location was most recently acquired. If no location has been acquired, the
maximum bucket is incremented.
kcarattini@chromium.org
dominickn@chromium.org
Counts Geolocation requests for omnibox searches sliced by various
permission combinations. The location mode abbreviations indicate one of:
High Accuracy, Battery Saving, GPS On or Location Mode Off.
kcarattini@chromium.org
dominickn@chromium.org
For Geolocation requests from the omnibox on Android, the time since the
location was first acquired. If no location has been acquired, the minimum
bucket is incremented.
kiyun@chromium.org
mvanouwerkerk@chromium.org
newt@chromium.org
Reason why the X-Geo header was or was not included in a Google search from
the omnibox.
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.
benwells@chromium.org
Records the backoff level when the Location Settings Dialog is accepted by
the user.
benwells@chromium.org
Records the backoff level when the Location Settings Dialog is rejected by
the user.
benwells@chromium.org
Records the backoff level when the Location Settings Dialog is shown to the
user.
benwells@chromium.org
Records the backoff level when the Location Settings Dialog is suppressed
due to backoff.
mvanouwerkerk@chromium.org
Counts Geolocation request timeout values, bucketing by timeout duration.
This is recorded for all requests upon creation, see
Geolocation.TimeoutExpired for timeouts that actually expired.
mvanouwerkerk@chromium.org
Counts Geolocation request timeout expirations, bucketing by timeout
duration. This means no position was received within the allowed time from
the browser process due to e.g. a slow network or an unresponsive system
location provider.
benwells@chromium.org
Records the action the user took after the geolocation disclosure has been
displayed.
benwells@chromium.org
Records how long the search geolocation disclosure infobar was visible for.
Deprecated 2017/11. Use PostDisclosureDSESetting instead.
benwells@chromium.org
Records the geolocation content setting for the default search engine's
origin after the search geolocation disclosure has been shown and won't be
shown again. This metric is only recorded once per client.
benwells@chromium.org
Records the geolocation default search engine setting after the search
geolocation disclosure has been shown and won't be shown again. This metric
is only recorded once per client.
Deprecated 2017/01. Replaced by PostDisclosureContentSetting.
benwells@chromium.org
Records the geolocation permission for the default search engine's origin
after the search geolocation disclosure has been shown and won't be shown
again. This metric is only recorded once per client.
Deprecated 2017/11. Use PreDisclosureDSESetting instead.
benwells@chromium.org
Records the geolocation content setting for the default search engine's
origin immediately before the search geolocation disclosure has been shown.
This metric is only recorded once per client.
benwells@chromium.org
Records the geolocation default search engine setting immediately before the
search geolocation disclosure has been shown. This metric is only recorded
once per client.
Deprecated 2017/01. Replaced by PreDisclosureContentSetting.
benwells@chromium.org
Records the geolocation permission for the default search engine's origin
immediately before the search geolocation disclosure has been shown. This
metric is only recorded once per client.
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.
andrewhayden@chromium.org
dgn@chromium.org
ConnectionResult error codes resulting from attempts to check whether or not
Google Play Services is available. Most of these checks are done lazily,
when a user accesses a feature that uses Google Play Services. Added for
http://crbug.com/490710.
andrewhayden@chromium.org
Types of action taken in response to Google Play Services user-recoverable
errors. Added for http://crbug.com/490710.
Deprecated 2015/08.
kmadhusu@chromium.org
Counts number of Google searches from various access points in the browser.
WARNING: Do not use this histogram as it currently fails to classify a large
percentage of Omnibox searches correctly - http://crbug.com/421631.
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.
Deprecated 12/2015 in Issue 566085.
yfriedman@chromium.org
dfalcantara@chromium.org
(Android-only) Records what action the user took (if any) on the InfoBar
indicating that a new version of Chrome is available.
shaktisahu@chromium.org
(Android-only) The amount of internal memory storage that is free on the
file system and available to the applications when the InfoBar or update
menu item is shown.
yfriedman@chromium.org
dfalcantara@chromium.org
khushalsagar@chromium.org
(Android-only) The amount of internal memory storage available on the user's
device when the InfoBar or update menu item is shown. Deprecating soon in
M64.
Deprecated 12/2015 in Issue 566085.
yfriedman@chromium.org
dfalcantara@chromium.org
(Android-only) The amount of time which the InfoBar indicating a new version
is available is visible.
grt@chromium.org
The exit code from Chrome's installer following a failed on-demand update
check. All values reported for this histogram fall in the
GOOGLE_UPDATE_ERROR_UPDATING bucket of the GoogleUpdate.UpdateErrorCode
histogram and the GOOPDATEINSTALL_E_INSTALLER_FAILED bucket of the
GoogleUpdate.ErrorHresult histogram.
twellington@chromium.org
(Android-only) Records whether Chrome was updated after the update menu item
was clicked.
twellington@chromium.org
(Android-only) Records whether the update menu item was clicked when the app
menu was opened.
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.
vmiura@chromium.org
Refresh rate of the display in Hz. This is recorded every time we present a
frame.
cwallez@chromium.org
The sum of the size of the CPU-side memory allocations of Buffer11's copies
(vs. GPU memory allocations). These allocations are used when modifying the
buffer data on the CPU or when transfering to GPU memory via DMA.
jmadill@chromium.org
An extended Windows error code returned from D3D11CreateDevice on error. Can
be almost any valid HRESULT or DXGI error code, which are listed at
https://msdn.microsoft.com/en-us/library/windows/desktop/bb509553.aspx.
jmadill@chromium.org
The 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
The time ANGLE spends calling the D3D shader compiler. Tracks total time we
spend compiling shaders on startup and during Chrome's lifetime.
jmadill@chromium.org
Time ANGLE spends in eglInitialize, where it spins up a Renderer. This can
gives us insight into how much time we're spending initializing the GPU.
jmadill@chromium.org
The time to load a gpu program from the program cache.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
jmadill@chromium.org
The time to link a gpu program.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
jmadill@chromium.org
If a successfully linked program was found in the GPU program cache during a
program link call, and if the hit was originally loaded from disk.
jmadill@chromium.org
Records if the call to load a cached binary was successful. This can
legitimately fail if the driver wants chrome to re-link and re-cache the gpu
program.
jmadill@chromium.org
The size of program binaries loaded into the gpu program cache.
jmadill@chromium.org
Time ANGLE spends initializing various shaders and internal classes. This is
time that isn't purely loading system DLLs and calling OS methods. It might
be work we can optimize or defer until later.
jmadill@chromium.org
Time ANGLE spends loading system DLLs, such as the D3D compiler DLL, and the
D3D11 and DXGI DLLs. Probably unavoidable startup costs, though very useful
to keep track of.
jmadill@chromium.org
Windows computers running Windows 8+, or running Windows 7 with a platform
update, support the newer version of DXGI. This update also indicates the
computer is capable of running Direct3D 11.1 if the hardware supports it.
forshaw@chromium.org
On Windows 10 version RS1 and above the GPU can be sandboxed using an
AppContainer. This is recorded every time the GPU sandbox is initialized and
enabling the AppContainer is requested, such as through a command line
option. The recorded value can indicate that the AppContainer was disabled
due to an incompatible configuration or the GPU process had previously
crashed resulting in the AppContainer being forcefully disabled.
forshaw@chromium.org
On Windows 10 version RS1 and above the GPU can be sandboxed using an
AppContainer. This indicates the status when initializing the sandbox
profile during process creation.
vmiura@chromium.org
The amount of GPU memory that was currently allocated as of just before the
GPU process' exit.
vmiura@chromium.org
The maximum amount of GPU memory that had ever been allocated during the GPU
process' lifetime, as of just before the GPU process' exit.
vmiura@chromium.org
The GPU memory manager's limit on the amount of GPU memory that can be
allocated as of just before the GPU process' exit.
vmiura@chromium.org
The number of surfaces that the GPU process was rendering to right before
exiting. This should be equal to the number of tabs (both visible and
hidden) rendering via the compositor.
vmiura@chromium.org
The number of windows that the GPU memory manager believed to exist as of
just before the GPU process' exit.
vmiura@chromium.org
Counts number of browser invocations for which a GPU feature is
allowed/blacklisted/disabled.
Replaced by GPU.BlacklistFeatureTestResultsWindows2 in M67.
vmiura@chromium.org
Counts number of browser invocations for which a GPU feature is
allowed/blacklisted/disabled in various Windows sub-versions.
vmiura@chromium.org
Counts number of browser invocations for which a GPU feature is
allowed/blacklisted/disabled in various Windows sub-versions.
vmiura@chromium.org
Counts number of browser invocations for which a disabled blacklist entry is
matched.
vmiura@chromium.org
Counts number of browser invocations for which the GPU process is blocked
due to a blacklist entry match.
kbr@chromium.org
Indicates whether WebGL / Pepper3D were blocked, and if so, for all domains,
or only a single one. This statistic is gathered every time an attempt is
made to create a 3D context.
Deprecated 01/2017.
ericrk@chromium.org
The amount of time spent in GLES2DecoderImpl::CheckFramebufferValid.
vmiura@chromium.org
The time that the GPU process spends collecting driver information during
startup.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
sievers@chromium.org
The reason a GPU command buffer context of a given type was lost.
ericrk@chromium.org
The amount of memory used by a GL Context.
Deprecated 07/2018: not useful anymore.
vmiura@chromium.org
The time that the browser process takes to create the compositor from its
point of view. One of these is created for each top-level window (browser
frame, menus, etc.).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
vmiura@chromium.org
Whether D3D11 supports B8G8R8A8 format for render targets.
vmiura@chromium.org
Whether D3D11 supports B8G8R8A8 format for 2D textures.
vmiura@chromium.org
The highest D3D11 feature level available.
vmiura@chromium.org
magchen@chromium.org
The maximum D3D12 feature level supported in the gpu drivers. It is recorded
15 seconds after the browser launch.
jmadill@chromium.org
ANGLE's currently active D3D shader model version. Logged once every startup
of the GPU process, on Windows only. Note that Shader Models 2 and 3 map to
D3D9 with ANGLE, and 4+ map to D3D11 ANGLE.
Deprecated 11/2016.
ericrk@chromium.org
The amount of time spent destroying programs during ProgramManager::Destroy.
Deprecated 11/2016.
ericrk@chromium.org
The number of progams destroyed during ProgramManager::Destroy.
Deprecated 11/2016.
ericrk@chromium.org
The number of programs destroyed per millisecond during
ProgramManager::Destroy. Only logged if both the number of programs and the
elapsed time are greater than zero.
jbauman@chromium.org
How the Desktop Window Manager presented Chrome's DirectComposition layers
to the screen.
jbauman@chromium.org
Recorded for each quad (on overlay processing) the reason it was or wasn't
put in an overlay.
jbauman@chromium.org
How many frames since the last time the layer color format was changed.
jbauman@chromium.org
True if Chrome will try to use DirectComposition overlays.
Replaced by format specific histograms under OverlaySupportFlags2.
sunnyps@chromium.org
These are the flags explaining how well overlays are supported on the
current display. The is recorded for every connected display when creating a
DirectComposition view context.
sunnyps@chromium.org
Flags that indicate if overlays are supported, and if additional features
such as scaling are supported for some common pixel formats.
jbauman@chromium.org
Whether or not a frame displays an overlay.
sunnyps@chromium.org
Emitted on direct composition surface swap buffers failure.
Deprecated 05/2018. GetLastError returns error for last successful or failed
win32 call so this doesn't work as expected.
sunnyps@chromium.org
Last error when presentation using DirectComposition fails.
jbauman@chromium.org
What type of swapchain was actually created for an overlay.
Deprecated 05/2018. Moved to GPU.ProcessLifetimeEvents.DisplayCompositor.
mohsen@chromium.org
Counts of the number of gpu process crashes when it only has display
compositor (no hardware acceleration and software compositing).
Deprecated 2/2017. The values hadn't been updated since it was created, and
the code gathering the installation status has been removed in Chrome CL
2679773002.
vmiura@chromium.org
Whether a version of DisplayLink is installed that crashes the GPU process.
This information is collected at statup. It applies only to Windows. See
http://crbug.com/177611.
jmadill@chromium.org
The time we spend in GLES2DecoderImpl::DoLinkProgram. Related to how much
time we spend compiling shaders during startup.
jbauman@chromium.org
vmiura@chromium.org
kbr@chromium.org
zmo@chromium.org
For every entry in the gpu driver bug list that is hit on a machine, this
records the id. Entry 0 is the total number of times that data is recorded.
It should be recorded whenever new GPU information is received: on startup,
whenever a GPU process launches, and whenever the active GPU changes.
jbauman@chromium.org
The display type used to ask for an EGLDisplay.
junov@chromium.org
piman@chromium.org
The error states generated by OpenGL calls.
reveman@chromium.org
Whether GLFence support is available. Recorded each time a new context group
is initialized and extensions are detected.
wnwen@chromium.org
Breakdown of exit status for gpu processes. Only recorded on Android.
jbauman@chromium.org
Counts for the exit codes returned by the GPU process when it terminated.
vmiura@chromium.org
Whether the GPU process successfully initialized or failed and then exitted
normally.
Deprecated 08/2016.
piman@chromium.org
Counts enumerating the initial cause for the GPU Process to be launched.
piman@chromium.org
Startup time of the GPU process as measured by the GPU process host.
Deprecated 05/2018. Moved to GPU.ProcessLifetimeEvents.HardwareAccelerated.
vmiura@chromium.org
Counts of the number of process launches and crashes (when running on h/w).
vmiura@chromium.org
A boolean indicating whether the gpu process that was launched uses software
or hardware 3d rendering.
Deprecated April 2018. Replaced by GPU.GPUProcessTerminationStatus2.
vmiura@chromium.org
Counts for each time the GPU Process Host detects the process dies.
vmiura@chromium.org
Counts for each time the GPU Process Host detects the process dies.
Deprecated 10/2013.
vmiura@chromium.org
Records whether a client was selected for the force compositing mode field
trial or not.
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.
vmiura@chromium.org
The time that the GPU process spends in initializing the GL surface, and
collecting graphics information.
ccameron@chromium.org
The time that it took to update the CALayer tree and commit the transaction.
This is often affected by IOSurface paging.
ccameron@chromium.org
The time that it took for a call to IOSurfaceCreate to complete.
ccameron@chromium.org
The time that it took for a call to glFlush to complete. This is often
affected by IOSurface paging.
ccameron@chromium.org
The time that it took for a call to CGLTexImageIOSurface2D to complete.
senorblanco@chromium.org
The maximum number of multisampled anti-aliasing (MSAA) samples per pixel
that the user's GPU can render.
khushalsagar@chromium.org
During OutOfProcess(Oop) raster, the renderer generates and sends the
requisite glyph data for rasterizing a tile with the serialized paint
commands. If the data for any glyph is missing, the GPU process attempts to
use a fallback glyph from the cache. This records each time we encounter a
cache miss on the GPU and whether we could use a fallback.
hubbe@chromium.org
media-dev@chromium.org
Records the output color space of the monitor as reported by Windows.
Recorded once for each monitor when the gpu process starts. If monitor
enumeration fails, this metric will not be provided.
hubbe@chromium.org
media-dev@chromium.org
Records if any connected monitor is HDR capable. Recorded when the gpu
process starts. Only recorded on Windows as of M-61. If monitor enumeration
fails, this metric will not be provided.
hubbe@chromium.org
media-dev@chromium.org
Records the display maximum lumens as reported by Windows. Recorded once for
each monitor when the gpu process starts. If monitor enumeration fails, this
metric will not be provided.
vmiura@chromium.org
Recorded once for every GPU process launch and crash when GPU process is
started for the display compositor with software compositing. Crash buckets
are based on crash count for disabling features. No hardware acceleration
and no SwiftShader WebGL will be run.
vmiura@chromium.org
Recorded once for every GPU process launch and crash when GPU process is
started for hardware accelerated GPU compositing and/or WebGL. Crash buckets
are based on crash count for disabling features. With OOP-D enabled the
display compositor also runs in the GPU process.
vmiura@chromium.org
Recorded once for every GPU process launch and crash when GPU process is
started for SwiftShader WebGL. Crash buckets are based on crash count for
disabling features. With OOP-D enabled the display compositor with software
compositing will also run as part of the GPU process.
vmiura@chromium.org
The time to load a gpu program from the program cache.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
vmiura@chromium.org
The time to link a gpu program.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
jmadill@chromium.org
If a successfully linked program was found in the GPU program cache during a
program link call.
vmiura@chromium.org
The time to check the program cache that we've already compiled the shader.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
vmiura@chromium.org
The time to compile a shader.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ericrk@chromium.org
Whether we succeeded in compressing program data. Expected to always be
true.
ericrk@chromium.org
The time to compress a program's binary data during insertion into the
program cache.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ericrk@chromium.org
The percentage of raw size that a program binary takes after compression.
ericrk@chromium.org
Whether we succeeded in decompressing program data. Failure indicates disk
or memory corruption.
ericrk@chromium.org
The time to decompress a program's binary data during retrieval from the
program cache.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
vmiura@chromium.org
Records if the call to glProgramBinary was successful. This can
legitimately fail if the driver wants chrome to re-link and re-cache the gpu
program.
ssid@chromium.org
Amount of memory released from the program cache on memory pressure.
vmiura@chromium.org
Records the total in-memory cache size, before a program is cached. Can be
used with GPU.ProgramCache.MemorySizeBeforeKb to find the maximum cache size
distribution.
vmiura@chromium.org
Records the total in-memory cache size, after a program is cached. Can be
used with GPU.ProgramCache.MemorySizeAfterKb to find the maximum cache size
distribution.
vmiura@chromium.org
The size of program binaries loaded into the gpu program cache.
piman@chromium.org
Whether or not the GPU sandbox properly initialized. Failures are typically
platform- and driver-specific (e.g. driver creating threads on Linux).
vmiura@chromium.org
Counts activation and deactivation of accelerated compositing.
ericrk@chromium.org
Whether or not the shader prefix loaded from disk matched the expected
prefix for the data and system configuration. False indicates either disk
corruption or a system configuration change, and should be rare.
Never used.
vmiura@chromium.org
Counts of the number of gpu process crashes when the software rasterizer is
enabled.
vmiura@chromium.org
Records whether a client was selected for the Stage3D on XP field trial or
not.
vmiura@chromium.org
magchen@chromium.org
This metric shows whether the GPU supports D3D12. It is recorded 15 seconds
after the browser launch.
vmiura@chromium.org
magchen@chromium.org
This metric shows whether the GPU supports Vulkan. It is recorded 15 seconds
after the browser launch.
Deprecated 12/2012. Moved to GPU.AtExitSurfaceCount.
vmiura@chromium.org
The number of surfaces that the GPU process was rendering to right before
exiting. This should be equal to the number of tabs (both visible and
hidden) rendering via the compositor.
Deprecated 05/2018. Moved to GPU.ProcessLifetimeEvents.SwiftShader.
capn@chromium.org
Counts of the number of process launches and crashes (when running on s/w).
hubbe@chromium.org
rijubrata.bhaumik@intel.com
media-dev@chromium.org
Whether LUMINANCE_F16 and/or R16_EXT texture support is available. Recorded
each time a new context group is initialized and extensions are detected.
reveman@chromium.org
Whether RG texture support is available. Recorded each time a new context
group is initialized and extensions are detected.
Deprecated 04/2018. Infobar has been removed.
vmiura@chromium.org
Counts user actions when a 3D API info bar is raised.
vmiura@chromium.org
magchen@chromium.org
Whether the Vulkan extension VK_KHR_external_memory_win32 is supported in
the GPU drivers. It is recorded 15 seconds after the browser launch.
vmiura@chromium.org
magchen@chromium.org
Whether the Vulkan extension VK_KHR_external_semaphore_win32 is supported in
the GPU drivers. It is recorded 15 seconds after the browser launch.
vmiura@chromium.org
magchen@chromium.org
Whether the Vulkan extension VK_KHR_win32_keyed_mutex is supported in the
GPU drivers. It is recorded 15 seconds after the browser launch.
vmiura@chromium.org
magchen@chromium.org
The maximum Vulkan API version supported in the gpu drivers. It is recorded
15 seconds after the browser launch.
stanisc@chromium.org
Whether WaitForVBlank operation has been successful or failed with one of
the errors prompting a backup delay based v-sync mechanism. Recorded each
time a new GPU v-sync signal is generated.
vmiura@chromium.org
Counts of context initialization that succeed or fail based on combinations
of attributes requiring canRecoverFromContextLoss and devices that report
can_lose_context. Failing Init is desired when a device can not guarantee it
won't fail for a user that can not handle failures, e.g. DX9 on WinXP used
by Canvas2D'
vmiura@chromium.org
The WinSAT (Windows System Assessment Tool) gaming graphics score. It is in
the range 1.0-5.9 on Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0
represents a failure to get the score. This is collected each time Chrome is
launched.
vmiura@chromium.org
The WinSAT (Windows System Assessment Tool) gaming graphics score, scaled by
10x. It is in the range 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0
represents a failure to get the score. This is collected each time Chrome is
launched.
vmiura@chromium.org
The WinSAT (Windows System Assessment Tool) graphics score. It is in the
range 1.0-5.9 on Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 represents a
failure to get the score. This is collected each time Chrome is launched.
vmiura@chromium.org
The WinSAT (Windows System Assessment Tool) graphics score, scaled by 10x.
It is in the range 10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0
represents a failure to get the score. This is collected each time Chrome is
launched.
vmiura@chromium.org
A boolean representing whether or not we succeeded in getting the system's
WinSAT scores. This is collected each time Chrome is launched.
vmiura@chromium.org
The WinSAT (Windows System Assessment Tool) overall system score. This is
the minimum of all the individual subscores. It is in the range 1.0-5.9 on
Vista, 1.0-7.9 on Win7 and 1.0-9.9 on Win8. 0 represents a failure to get
the score. This is collected each time Chrome is launched.
vmiura@chromium.org
The WinSAT (Windows System Assessment Tool) overall system score, scaled by
10x. This is the minimum of all the individual subscores. It is in the range
10-59 on Vista, 10-79 on Win7 and 10-99 on Win8. 0 represents a failure to
get the score. This is collected each time Chrome is launched.
vmiura@chromium.org
The amount of time it takes to read the WinSAT results. This is collected
each time Chrome is launched.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
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.
Seek penalty detection is disabled on XP/Vista as of 9/24/2015 because it
crashes too much. http://crbug.com/514822
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.
charliea@chromium.org
On Windows and Mac, we're implementing new methods to enumerate serial
devices that provide us more information about the actual devices. This
metric measures the difference between the number of devices that the new
and old enumeration methods find. Once this metric gives us confidence that
the new and old methods are at parity, we can cut out the old method
altogether.
ryansturm@chromium.org
bengr@chromium.org
Records that the capping heavy pages InfoBar was allowed or the specific
reason that the feature was blacklisted from heavy page capping. Recorded
when the triggering threshold is met for users with capping heavy pages
enabled. Reasons are ordered in the same order they are checked.
ryansturm@chromium.org
bengr@chromium.org
Records the details of user interaction with the heavy page capping InfoBar.
ryansturm@chromium.org
Records the data savings due to heavy page capping. This is recorded when
the page is being terminated. This is not recorded when the tab is
backgrounded, so android fast shutdown may result in this metric not being
recorded. This is only recorded for page loads that were still paused when
the page was terminated.
merkulova@chromium.org
Which HID were detected when user pressed Continue on OOBE dialog. This
metric is specific to Chrome OS.
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 Chrome OS.
merkulova@chromium.org
Records number of times the dialog was shown by the time OOBE is completed.
This metric is specific to Chrome OS.
asvitkine@chromium.org
bcwhite@chromium.org
The hash codes of histograms that were found to have bad construction
arguments. These would be DCHECK exceptions in debug builds but have simply
been logged and corrected as best as possible rather than crash.
Deprecated 7/2017.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a browser for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency MAY appear time and
again as the same corrupt histogram is examined for each potenital UMA
upload.
Deprecated 7/2017.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a browser for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency will only appear at
most one time for each histogram in a single process (i.e., duplicate
corruption in a single histogram is not noted in this chart.)
Deprecated 7/2017.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a child process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency MAY appear time and
again as the same corrupt histogram is examined for each potenital UMA
upload.
Deprecated 7/2017.
asvitkine@chromium.org
The number of inconsistency events found when examining a single histogram's
data in a child process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA. Each type of inconsistency is a bit, and all bits
found in one histogram examination are added together to summarize the
inconsistent event. Note that the same inconsistency will only appear at
most one time for each histogram in a single process (i.e., duplicate
corruption in a single histogram is not noted in this chart.)
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.)
Deprecated 7/2017.
asvitkine@chromium.org
The number of extra samples counted in the redundant_count in a histogram
that were not found by summing the samples in the buckets.
Deprecated 7/2017.
asvitkine@chromium.org
The number of missing samples in the redundant_count in a histogram that
were found by summing the samples in the buckets.
asvitkine@chromium.org
The amount of discrepancy found when examining a single histogram's data in
the browser process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA.
asvitkine@chromium.org
The amount of discrepancy found when examining a single histogram's data in
a child process for transmission via UMA. Inconsistent data is NOT
transmitted via UMA.
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.
asvitkine@chromium.org
bcwhite@chromium.org
The hash codes of histograms that were found to have construction arguments
different from a previous instantiation of the same name. Entries here have
conflicting definitions and should be investigated. Data collected for the
secondary definitions will be silently dropped.
asvitkine@chromium.org
bcwhite@chromium.org
The hash codes of histograms of which the external name storage was altered
after the histogram was created.
brettw@chromium.org
Logged whenever history database initialization fails. The frequency of
logging will tell you the total failure rate. True indicate that we think
the database is non-recoverable and it will be deleted. It should be
re-created the next time Chrome is started. False indicates we think the
error is temporary (like out of disk space or file locked). Chrome will run
with no history database and nothing will be done to try to fix the error.
See History.InitializationFailureStep for which particular step of history
initialization failed.
msramek@chromium.org
Whether a notice about other forms of browsing history was shown in the
footer of the Clear Browsing Data dialog. This is recorded every time the
dialog is opened.
dmurph@chromium.org
Recorded when the user presses the 'clear' button when presented with the
list of important sites they might want to exclude from clearing browsing
data. We record the number of sites the user deselected, or protected, from
clearing. The default has all sites selected.
dmurph@chromium.org
Recorded when the user presses the 'clear' button when presented with the
list of important sites they might want to exclude from clearing browsing
data. We record the percent of sites the user deselected, or protected, from
clearing. The default has all sites selected, which is 0%. Note: To reduce
the number of empty buckets, the percent is divided by 5.
dmurph@chromium.org
Recorded when the user presses the 'clear' button in the clear browsing
dialog. We record 'true' if the important sites dialog is shown.
dmurph@chromium.org
Recorded when we successfuly fetched important sites in the clear browsing
data screen. This is the number of sites that we think are important to the
user.
msramek@chromium.org
Recorded when the user deletes their passwords in the ClearBrowsingData
dialog. Counts how many other data types were selected for deletion.
msramek@chromium.org
Whether a dialog with a notice about other forms of browsing history was
shown after the user deleted data from the Clear Browsing Data dialog.
dullweber@chromium.org
msramek@chromium.org
Track whether the SpannableString is applied correctly in
ClearBrowsingDataCheckbox.java. (crbug.com/783866)
dullweber@chromium.org
msramek@chromium.org
The number of tasks that are in the task queue when the BrowsingDataRemover
is destroyed.
dullweber@chromium.org
msramek@chromium.org
Time spent in Clear Browsing Data dialog. From opening the dialog until data
is cleared. This does not record users who exit the dialog without clearing.
msramek@chromium.org
Recorded when the user deletes their browsing data. Shows whether cookies
and/or cache were among the selected data types.
msramek@chromium.org
Recorded when the user deletes their browsing data manually from the
ClearBrowsingData dialog. Shows whether cookies and/or cache were among the
selected data types.
dullweber@chromium.org
msramek@chromium.org
Recorded when the user deletes their browsing data. Shows which tab was used
to perform the deletion.
shess@chromium.org
Time spent on advanced History DB metrics calculation (weekly and monthly
URL, host, and category counts). Advanced metrics are logged on
initialization of the History DB on 0.3% of starts.
shess@chromium.org
Time spent on basic History DB metrics calculation (file size and table
counts). Basic metrics are logged on initialization of the History DB on 1%
of starts.
shess@chromium.org
Size of History DB file. Duplicate of Profile.HistorySize and
Sqlite.SizeKB.History. Logged on initialization of the History DB on 1% of
starts.
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.
calamity@chromium.org
The percentage of time taken in ExpireHistoryBackend::ExpireVisits for
calculating the redirect parent.
calamity@chromium.org
The time taken to expire a list of visits. This is not scaled to the number
of visits deleted, but gives an idea of how long a single request to
ExpireHistoryBackend::ExpireVisits takes.
rogerm@chromium.org
The wall-clock time taken to gather favicon database metrics. Metrics are
logged on initialization of the Favicon DB on 1% of starts.
rogerm@chromium.org
Size of the Favicons database in MB. This is calculated as the number of
pages consumed by the database multiplied by the page size. Logged on
initialization of the Favicon DB on 1% of starts.
No longer tracked as of March 2017.
rpop@google.com
Size of the recovered Favicons database relative to the original corrupt
database. Recovery is VACUUM-like, so the resulting database should always
be smaller. Substantial 100% results would indicate empty databases being
recovered, substantial low% results would indicate very little data being
recovered.
No longer tracked as of March 2017.
rpop@google.com
Rows recovered from [favicon_bitmaps] table in Favicons recovery.
No longer tracked as of March 2017.
rpop@google.com
Rows recovered from [favicons] table in Favicons recovery.
No longer tracked as of March 2017.
rpop@google.com
Rows recovered from [icon_mapping] table in Favicons recovery.
No longer tracked as of March 2017.
rpop@google.com
Track results of SQLite database recovery code in thumbnail_database.cc.
yiyaoliu@chromium.org
The count of differences between cached top sites and up-to-date top sites
when function TopSitesImpl::SetTopSites is firstly called at startup.
yiyaoliu@chromium.org
The amount of time for function
history::TopSitesBackend::UpdateTopSitesOnDBThread to execute when this
function is called during startup. Excludes the case where local
TopSitesDatabase db_ is unavailable, i.e. where the update doesn't really
happen.
calamity@chromium.org
The page of the MD History page shown to the user. Logged each time the user
loads the MD History page or switches pages.
rkaplow@chromium.org
The amount of time that elapsed during HistoryService::Init.
brettw@chromium.org
The phase of history initialization that failed. This histogram is only
logged on database initialization failure.
History.AttemptedToFixProfileError will tell how often initialization fails
overall.
gab@chromium.org
The number of typed URLs in the history database that are read into the
"in memory" history database. This in memory copy of the typed
URLs is used for synchronous inline autocomplete on the UI thread, while the
larger slower service is run off of disk on a background thread. Recorded on
profile open.
gab@chromium.org
Number of items in in-memory keyword_search_terms table. Recorded on profile
open.
gab@chromium.org
Time to load in-memory keyword_search_terms table from disk. Recorded on
profile open.
gab@chromium.org
Number of items in in-memory urls table. Recorded on profile open.
gab@chromium.org
Time to load in-memory urls table from disk urls table. Recorded on profile
open.
gab@chromium.org
The time it takes to read the typed URLs from the main history database into
the "in memory" history database. This in memory copy of the typed
URLs is used for synchronous inline autocomplete on the UI thread, while the
larger slower service is run off of disk on a background thread. Recorded on
profile open.
gab@chromium.org
The sum of the visit_count fields for all URLs in the "in memory"
history database. This corresponds to the number of times the user has
visited the typed URLs in the last 30 days (excluding page reloads, since
the history database does not increment the visit_count in that case).
Recorded on profile open.
mpearson@chromium.org
Size of on-disk cache for in-memory url index. Recorded on profile open when
restoring from a cache file.
mpearson@chromium.org
Number of items in the in-memory url index char_word_map_. Recorded on
profile open when restoring from a cache file and again shortly after
profile open when rebuilding the in-memory url index from history.
mpearson@chromium.org
Number of history items in the in-memory url index. Recorded on profile open
when restoring from a cache file and again shortly after profile open when
rebuilding the in-memory url index from history.
mpearson@chromium.org
Time to rebuild in-memory url index from main history database. Recorded
once shortly after profile open.
mpearson@chromium.org
Time to restore the in-memory url index from disk cache. Recorded on profile
open.
mpearson@chromium.org
Time to write in-memory url index to disk cache. Recorded once shortly after
profile open (after rebuilding the in-memory url index from history) and
again upon (clean) shutdown.
mpearson@chromium.org
Number of items in in-memory url index word_map_. Recorded on profile open
when restoring from a cache file and again shortly after profile open when
rebuilding the in-memory url index from history.
brettw@chromium.org
History database version from which history migration failed. If there are
higher than normal migration failures, this histogram will indicate which
migration step failed.
shess@chromium.org
Unique hostnames in History database urls table with last-visit times in the
last 30 days. Metrics are logged on initialization of the History DB on 0.3%
of starts.
shess@chromium.org
Unique URLs in History database urls table with last-visit times in the last
30 days. Metrics are logged on initialization of the History DB on 0.3% of
starts.
shess@chromium.org
Number of rows in History visits table with visit times in the last 30 days.
Metrics are logged on initialization of the History DB on 1% of starts.
rogerm@chromium.org
The total number of favicon bitmaps (of all sizes) cached in a user's
Favicon database. A given favicon URL may be associated with multiple
bitmaps (of different sizes). Logged on initialization of the Favicon DB on
1% of starts.
rogerm@chromium.org
The number of page URL (e.g., http://www.google.com) to favicon URL (e.g.,
http://www.google.com/favicon.ico) mappings stored in a user's Favicon
database. Logged on initialization of the Favicon DB on 1% of starts.
rogerm@chromium.org
The total number of favicon URLs (e.g. http://www.google.com/favicon.ico)
tracked in a user's Favicon database. This metric tracks knowledge of a
favicon URL not whether there are cached bitmaps for that favicon URL. See
History.NumFaviconBitmapsInDB for that. Logged on initialization of the
Favicon DB on 1% of starts.
rogerm@chromium.org
The total number of large (>= 64 pixels wide) favicons being tracked in a
user's Favicon database. This is a subset of History.NumFaviconBitmapsInDB,
which includes all sizes in its count. Logged on initialization of the
Favicon DB on 1% of starts.
rogerm@chromium.org
The total number of touch icons being tracked in a user's Favicon database.
This is a subset of History.NumFaviconsInDB, which includes all icon types
in its count. Logged on initialization of the Favicon DB on 1% of starts.
chengx@chromium.org
The amount of time for function HistoryBackend::QueryMostVisitedURLs to
execute. Excludes the case where local HistoryDatabase db_ is unavailable,
i.e. where the query doesn't really happen.
tsergeant@chromium.org
Records the time taken to load the history Web UI and render (at least) a
screen full of items. This is roughly equivalent to 'time to first
meaningful paint' for the history page.
msramek@chromium.org
Whether the notice about other forms of browsing history was shown in the
header of the History page when the header was displayed. The header is
refreshed with every history query.
twifkak@chromium.org
bengr@chromium.org
Page visits to each of a user's top 50 hosts. The bucket is the 1-based rank
of the host. Visits to all other hosts go into the 51st bucket.
Android-only. Only counts the last URL in a redirect chain. The list of top
hosts is computed approximately nightly. This means that a given day will
likely include a recalculation of top hosts, and therefore a given bucket
may represent two different hosts at different times of day.
Please list the metric's owners. Add more owner tags as needed.
Size of the recovered TopSites database relative to the original corrupt
database. Recovery is VACUUM-like, so the resulting database should always
be smaller. Substantial 100% results would indicate empty databases being
recovered, substantial low% results would indicate very little data being
recovered.
Please list the metric's owners. Add more owner tags as needed.
Rows recovered from [thumbnails] table in TopSites recovery.
Please list the metric's owners. Add more owner tags as needed.
The TopSites recovery code is written conservatively, with successful
recovery committed and any failure leading to rollback. This tracks the
outcomes to determine which cases are high-frequency enough to warrant
adding additional code to handle them (versus simply deleting the data).
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.
shess@chromium.org
Number of rows in urls table in History DB. Metrics are logged on
initialization of the History DB on 1% of starts.
shess@chromium.org
Number of rows in visits table in History DB. Metrics are logged on
initialization of the History DB on 1% of starts.
shess@chromium.org
Unique hostnames in History database urls table with last-visit times in the
last 7 days. Metrics are logged on initialization of the History DB on 0.3%
of starts.
shess@chromium.org
Unique URLs in History database urls table with last-visit times in the last
7 days. Metrics are logged on initialization of the History DB on 0.3% of
starts.
shess@chromium.org
Number of rows in History visits table with visit times in the last 7 days.
Metrics are logged on initialization of the History DB on 1% of starts.
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'.
calamity@chromium.org
Counts which content setting buttons in the hosted app frame are pressed by
the user.
calamity@chromium.org
Number of times that each menu item is clicked from the hosted app window
menu button.
Deprecated as of 10/2017. Feature removed with crbug/761426.
rlp@chromium.org
The state of the hotword audio logging preference. This value is emitted
each time the hotword availability is requested by the extension if the user
is also opted in to hotword voice search. This check typically happens each
time a hotword search is initiated.
Deprecated as of 10/2017. Feature removed with crbug/761426.
rlp@chromium.org
The state of the hotword preference. This value is emitted during
HotwordService initialization which happens during Profile initialization.
Deprecated as of 10/2017. Feature removed with crbug/761426.
rlp@chromium.org
Whether the external component hotword extension exists (i.e., not pending
download, disabled, etc.). This value is emitted each time the hotword
availability is requested by the extension which typically happens each time
a hotword search is initiated.
Deprecated as of 10/2017. Feature removed with crbug/761426.
rlp@chromium.org
Errors reported by the hotword service when determining if hotwording is
available. Non-errors are also reported so that errors can be seen as a
percentage of total requests.
Deprecated as of 10/2017. Feature removed with crbug/761426.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Success or error when attempting to open a MediaStream for the microphone.
At most one success or error will be logged for an attempt to open a stream.
Deprecated as of 10/2017. Feature removed with crbug/761426.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Timeout occured while waiting for a message from the NaCl hotword detector
plugin. This value is the message that was expected to be received from the
plugin.
Deprecated as of 10/2017. Feature removed with crbug/761426.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Success or error when attempting to load the NaCl hotword detector plugin.
Deprecated as of 10/2017. Feature removed with crbug/761426.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Location of hotword trigger. Emitted every time the hotword is triggered by
the user saying 'Ok Google'.
Deprecated as of 10/2017. Feature removed with crbug/761426.
amistry@chromium.org
rlp@chromium.org
somast@chromium.org
Language, switched to by the user, that triggered a hotword shared module
reinstall.
morlovich@chromium.org
For every http cache transaction with a pattern (see HttpCache.Pattern), the
time from the first access to the disk cache until the transaction was done.
morlovich@chromium.org
For http cache transactions in which a network request was sent, the time
elapsed between sending it over the network until the transaction was done.
Deprecated as of 3/2015.
ricea@chromium.org
The time spent performing an asynchronous revalidation that was triggered by
a Cache-Control: stale-while-revalidate directive. This is recorded when the
asynchronous revalidation completes, either after the response was
completely read or an error occurred. One entry is recorded for each
asynchronous revalidation that is performed.
morlovich@chromium.org
For http cache transactions in which a network request was sent, the time
elapsed between beginning the request and sending it over the network; this
is the time spent accessing the disk cache.
jkarlin@chromium.org
For each request that results in an unconditionalizable network request, the
cause for the request.
morlovich@chromium.org
For each request with HttpCache.CantConditionalizeCause == Zero Freshness,
this is true iff the zero freshness status was determined by looking at
in-memory hints in disk cache index, rather than by opening the entry and
looking at headers.
jkarlin@chromium.org
morlovich@chromium.org
The time spent waiting for write lock on a disk cache entry.
stale-while-revalidate implementation removed for now, see
https://crbug.com/700568.
ricea@chromium.org
Count of the number of external (ie. from Blink) conditionalized requests,
and whether or not those requests could have been served from the browser
cache.
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.
shivanisha@chromium.org
Records whether a transaction either created a Writers object when one
didn't exist, or joined an existing Writers object, or why it failed to do
so (e.g., it's a range request, it's not a GET request, etc.).
morlovich@chromium.org
jkarlin@chromium.org
For each http cache transaction, the recorded pattern.
morlovich@chromium.org
For http cache transactions in which a network request was sent, the
percentage of total request time that elapsed before sending the request
over the network; this is the time spent accessing the disk cache.
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.
jkarlin@chromium.org
For each http cache transaction for which a cache entry exists but it cannot
be used because the entry's age is beyond its freshness: counts how many
freshness periods have elapsed since the entry was last used (x1000).
jkarlin@chromium.org
For each http cache transaction for which a validation attempt is made due
to a stale entry and is updated (e.g., 200), records the age of the entry in
seconds.
jkarlin@chromium.org
For each http cache transaction for which a validation attempt is made due
to a stale entry and is updated (e.g., 200), records the age of the entry as
percentage of freshness period.
jkarlin@chromium.org
For each http cache transaction for which a validation attempt is made due
to a stale entry and is validated (304), records the age of the entry in
seconds.
jkarlin@chromium.org
For each http cache transaction for which a validation attempt is made due
to a stale entry and is validated (304), records the age of the entry as
percentage of freshness period.
jkarlin@chromium.org
For each validation attempt, the cause for the validation.
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.
kojii@chromium.org
The time it takes to open a hyphenation dictionary.
kojii@chromium.org
The time it takes to open a hyphenation dictionary file.
gcomanici@chromium.org
The size of the history on Auto Import from IE. This measure is only logged
on a succesfull Auto Import.
gab@chromium.org
The importer used on first run Auto Import.
gab@chromium.org
The importer used on import from the bookmarks file API.
gab@chromium.org
The importer used on import from the chrome://settings/importData UI.
vabr@chromium.org
hurims@gmail.com
Whether or not the password checkbox is checked when importing a profile of
Firefox. Note that canceled imports could be counted also.
vabr@chromium.org
hurims@gmail.com
The number of passwords that are imported from Firefox. This is recorded
when importing a profile of Firefox with the password checkbox checked. Note
that the reported number of password could be slightly bigger than the
actual number of imported passwords because some incomplete or blacklisted
passwords that are dropped while importing might be included in the reported
value.
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.
xaerox@yandex-team.ru
File error happened upon temporary file creation at ImportantFileWriter.
xaerox@yandex-team.ru
File error happened upon temporary file deletion at ImportantFileWriter.
xaerox@yandex-team.ru
File error happened upon opening temporary file at ImportantFileWriter.
xaerox@yandex-team.ru
File error happened upon temporary file renaming at ImportantFileWriter.
xaerox@yandex-team.ru
File error happened upon writing data to temporary file at
ImportantFileWriter.
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).
mamir@chromium.org
Time used to atomically write string into a file using ImportantFileWriter.
robliao@chromium.org
The thread used to initialize the Windows parental controls.
robliao@chromium.org
The amount of time that elapsed during a run of
PlatformParentalControlsValue::IsParentalControlActivityLoggingOnImpl on
Windows 7 and above.
pmonette@chromium.org
Records whether the user was automatically shown the
chrome://settings/incompatibleApplications page following a Chrome crash.
pmonette@chromium.org
The number of incompatible applications detected by Chrome at the time the
chrome://settings/incompatibleApplications page was opened.
timvolodine@chromium.org
Whether the Sensor.TYPE_LINEAR_ACCELERATION was available at the start of
Device Motion.
timvolodine@chromium.org
Whether the Sensor.TYPE_ACCELEROMETER was available at the start of Device
Motion.
timvolodine@chromium.org
Whether the SENSOR_TYPE_ACCELEROMETER_3D was available at the start of
Device Motion on the Windows platform.
timvolodine@chromium.org
Provides a histogram of the base sensors (if any) that are used at the start
of the Device Orientation API. Currently Sensor.TYPE_GAME_ROTATION_VECTOR is
the default sensor for orientation, if it's not available fall-back options
are provided by using either Sensor.TYPE_ROTATION_VECTOR or a combination of
Sensor.TYPE_ACCELEROMETER and Sensor.TYPE_MAGNETIC_FIELD.
timvolodine@chromium.org
Whether the SENSOR_TYPE_GYROMETER_3D was available at the start of Device
Motion on the Windows platform.
timvolodine@chromium.org
Whether the Sensor.TYPE_GYROSCOPE was available at the start of Device
Motion.
timvolodine@chromium.org
Whether the SENSOR_TYPE_INCLINOMETER_3D was available at the start of Device
Orientation on the Windows platform.
timvolodine@chromium.org
This histogram counts the number of Device Motion API invocations in the
default implementation (Linux and CrOS). The default implementation does not
provide any sensors so the result is always false.
timvolodine@chromium.org
Whether the sudden motion sensor was available at the start of Device Motion
on the MacOS platform.
timvolodine@chromium.org
This histogram counts the number of Device Orientation API invocations in
the default implementation (Linux and CrOS). The default implementation does
not provide any sensors so the result is always false.
timvolodine@chromium.org
Whether the sudden motion sensor was available at the start of Device
Orientation on the MacOS platform.
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.
dfalcantara@chromium.org
rkaplow@chromium.org
Records how many times a particular infobar was shown to the user. On
Android, the infobar may be partially hidden due to stacking. On desktop, a
tab with a visible infobar will increment this histogram every time the user
switches away from the tab and back to it with the infobar still visible.
dfalcantara@chromium.org
dominickn@chromium.org
Records how many times a particular infobar was displayed in a hidden state
due to at least one other infobar existing. If there are no existing
infobars, but the user scrolls at the exact moment a new infobar is added,
the infobar may be hidden, but not recorded in this metric. Reliably
triggering and detecting this combination is tricky so it isn't done. Only
recorded on Android.
dfalcantara@chromium.org
dominickn@chromium.org
Records how many times a particular infobar was visible and hiding a new
infobar behind it. Only recorded on Android.
dfalcantara@chromium.org
dominickn@chromium.org
Records how many times a particular infobar was displayed in a visible state
due to no other infobars existing. If there are no existing infobars, but
the user scrolls at the exact moment a new infobar is added, the infobar may
be hidden, but recorded here as visible. Reliably triggering and detecting
this combination is tricky so it isn't done. Only recorded on Android.
nyquist@chromium.org
xingliu@chromium.org
Records if in-product help configuration is parsed correctly, and the
failure reasons for parsing failures.
nyquist@chromium.org
xingliu@chromium.org
Records if database initialization succeeds for in-product help.
nyquist@chromium.org
xingliu@chromium.org
Records if database successfully loads the data for in-product help.
nyquist@chromium.org
xingliu@chromium.org
Records the total number of event records in the database for in-product
help after the event model is loaded.
nyquist@chromium.org
xingliu@chromium.org
Records if each database update succeeds for in-product help.
nyquist@chromium.org
xingliu@chromium.org
Records if the model is ready when in-product help event happens.
nyquist@chromium.org
xingliu@chromium.org
Records if in-product help is shown to the user, and the failure reasons if
in-product help is not shown. Recorded on its own across all in-product help
features, in addition to being a base name for feature-specific histograms.
shuchen@chromium.org
The number of active input methods. Recorded when the user logs in to Chrome
OS or each cold start of Chrome on Android. The active input methods are
selected by user in the language settings page on Chrome OS and in system
language settings on Android.
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.
This is deprecated since M46, InputMethod.ID2 is used since then.
shuchen@chromium.org
The breakdown of input method usage by input method IDs. Recorded when the
user presses keys on physical or on-screen keyboard.
shuchen@chromium.org
The breakdown of input method usage by input method IDs. Recorded when the
user presses keys on physical or on-screen keyboard.
azurewei@chromium.org
shuchen@chromium.org
Whether the opt-in IME menu in the shelf has been activated.
azurewei@chromium.org
shuchen@chromium.org
The number of times users click emoji, handwriting or voice button in opt-in
IME menu.
shuchen@chromium.org
The trigger type of input method switches by user.
aurimas@chromium.org
Whether the currently selected keyboard language matches the system
language. Recorded once with every cold start of Chrome for Android.
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.
changwan@chromium.org
The result of registering proxy view to InputMethodManager.
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
Chrome OS histogram that counts the number of times the cursor was moved to
the previous word by swiping backwards on the selection track. The count is
initialized when the user starts swiping from any side of the virtual
keyboard, incremented based on how far they swipe backwards on the selection
track, and recorded when they release their finger.
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.
yhanada@chromium.org
Chrome OS histogram that counts the number of times each virtual keyboard
display mode is used. Recorded when the virtual keyboard is opened or a user
changes the keyboard mode from UI in the virtual keyboard.
shuchen@chromium.org
How long the virtual keyboard was visible.
girard@chromium.org
Text input events related to gesture typing.
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
Chrome OS histogram that counts the number of times the cursor was moved to
the next word by swiping forward on the selection track. The count is
initialized when the user starts swiping from any side of the virtual
keyboard, incremented based on how far they swipe forwards on the selection
track, and recorded when they release their finger.
girard@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
Chrome OS histogram that tracks the total number of words that were deleted
by swiping forward on the deletion track. The count is initialized when the
user starts swiping on the backspace key, incremented based on how far they
swipe forwards on the deletion track, and recorded when they release their
finger.
rsadam@chromium.org
The number of words typed per minute. Recorded when the virtual keyboard is
closed.
rsadam@chromium.org
Chrome OS histogram that tracks the total number of words that were restored
by swiping backwards on the deletion track. The count is initialized when
the user starts swiping on the backspace key, incremented based on how far
they swipe backwards on the deletion track, and recorded when they release
their finger.
zeuthen@chromium.org
The number of update attempts until the update has been applied. This is
reported every time the device has completed an update.
zeuthen@chromium.org
Errors from update_engine process when running in dev mode.
zeuthen@chromium.org
The overhead in downloading extra bytes due to errors/interruptions.
Expressed as a percentage of the bytes that are actually needed to be
downloaded for the update to be successful.
zeuthen@chromium.org
The combinations of protocol and source server that were used to complete a
successful update.
zeuthen@chromium.org
The number of update attempts with a full update payload until the update
has been applied. This is reported on every update attempt.
zeuthen@chromium.org
The source used to provision the install-date-days value sent to Omaha with
every request. This is reported when OOBE completes (M34 or later) or when
upgrading to a version with install-date-days support.
zeuthen@chromium.org
Errors from update_engine process when running in normal mode.
zeuthen@chromium.org
The age of the OS, defined as the age of the /etc/lsb-release file. This is
reported on every update check but at most once a day.
zeuthen@chromium.org
The number of update attempts until the update has been applied. This is
reported on every update attempt.
zeuthen@chromium.org
The type of update payload used to update the device. The difference between
"Full" and "Forced Full" is that in the latter, the
request sent to Omaha included a directive saying that a delta payload
wasn't accepted. A "Full" payload is one where a delta payload was
accepted but Omaha provided a full payload. This is reported every time the
device has completed an update.
zeuthen@chromium.org
The number of consecutive times a device has failed to boot an update that
successfully applied. This metric is reported every time the firmware fails
to boot the slot with the update and fell back to the slot it originally
updated from.
Superseded by Installer.Recovery.Reason in 8/2017.
ahassani@chromium.org
The number of times the device has been recovered.
This is reported on reboot after a successful recovery. Cleared only when
switching to dev mode or on factory reset.
This metric is specific to Chrome OS.
lannm@chromium.org
The reason for entering recovery mode immediately prior to a recovery.
This is reported on reboot after a successful recovery.
This metric is specific to Chrome OS.
zeuthen@chromium.org
Number of MBs downloaded from during an update that completed successfully.
zeuthen@chromium.org
Wall-clock duration between when an update has successfully completed (and
the user is presented with the "reboot arrow") and when the system
has booted into the new update. This is reported every time the device is
rebooted after an update has been applied.
zeuthen@chromium.org
Total number of MBs downloaded since the last successful update. This also
includes all the bytes downloaded during any prior failed attempts.
zeuthen@chromium.org
Absolute wall-clock time duration it took for the update to complete from
the time an update first began. It includes not just the time the device
was up, but also includes the time the device spent sleeping.
zeuthen@chromium.org
Uptime duration it took for the update to complete from the time an update
first began. It does not include the time the device spent sleeping, but it
does include the uptime spent in waiting for the hourly update checks to
happen.
zeuthen@chromium.org
Number of times the device was rebooted by the user since an update began
and until it completed successfully.
zeuthen@chromium.org
The number of update attempts that didn't complete because a newer update
was detected during the update operation. This is reported every time the
device has completed an update.
zeuthen@chromium.org
The number of consecutive different abandoned update payloads since the last
successful update. This is reported every time an update payload is
abandoned because a newer update payload is available.
zeuthen@chromium.org
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.
jianli@chromium.org
Length of time taken to complete the DeleteToken request successfully. If
the request is retried multiple times, the length of time is counted for the
last successful retry.
juyik@chromium.org
Status code of the outcome of DeleteToken request.
jianli@chromium.org
Number of retries before DeleteToken succeeds.
jianli@chromium.org
Whether the Instance ID API is enabled. Checked when a chrome.instanceID
function is called.
jianli@chromium.org
Length of time taken to complete the GetToken request successfully. If the
request is retried multiple times, the length of time is counted for the
last successful retry.
juyik@chromium.org
Status code of the outcome of GetToken request.
jianli@chromium.org
Number of retries before GetToken succeeds.
jianli@chromium.org
Number of Instance IDs restored from the persistent store at startup.
jianli@chromium.org
Number of InstanceID tokens restored from the persistent store at startup.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Records various events of interest in the InstantController. E.g. When URLs
are blacklisted.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
How often an Instant preview is committed onto a different tab than it was
created from.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time between the first Omnibox interaction and when the Instant preview
shows. If the instant preview was already showing when the user interacted
with the omnibox, this histogram is not recorded.
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.
Removed in August 2016 with the removal of query in the omnibox code.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a search query to another search query.
Removed in August 2016 with the removal of query in the omnibox code.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a search query to a url. Example: Accidental search for
google.con, then navigation to google.com.
Removed in September 2016 because (i) this measurement was somewhat wrong,
(ii) it's difficult to understand the data, and (iii) there are better ways
to answer the same question. The measurement is somewhat wrong because
reloads, link drops, and pasting URLs and pressing enter are all incorrectly
logged to the URLtoQuery histogram, not the URLtoURL histogram. Futhermore,
this histogram is difficult to analyze because it's not broken up by input
length. Short URLs can by random chance have a sizable percentage match
with a query. Finally, there are better source for data like this; ask
mpearson for details.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a url to a search query.
Removed in September 2016 because (i) this measurement was somewhat wrong,
and (ii) there are better ways to answer the same question. The measurement
is somewhat wrong because reloads, link drops, and pasting URLs and pressing
enter are all incorrectly logged to the URLtoQuery histogram, not the
URLtoURL histogram. Furthermore, there are better source for data like
this; ask mpearson for details.
mpearson@chromium.org
Records the number of matching characters at the start of the user's text as
a percentage of average length between the old and new text when the user
navigates from a url to another url.
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.
Deprecated as of 7/2015.
ksimbili@chromium.org
Records the scroll state on the preview page when instant search clicks
feature is triggered.
Deprecated as of 7/2015.
ksimbili@chromium.org
Records the reason that triggered the page swap when instant search clicks
feature is triggered.
Deprecated as of 7/2015.
ksimbili@chromium.org
The time spent by the user in preview page before swapping to original or
navigating out of preview page.
Deprecated as of 7/2015.
ksimbili@chromium.org
The time it took for swap to trigger for all swaps. The is the time between
preview page load start to preview page swap with the original page.
hansberry@chromium.org
Provides a breakdown of how many times each possible Bluetooth advertisement
registration result occurs.
The bucket "Unknown result" indicates that the Bluetooth platform
returned an unknown error code; if it has any counts, the client code should
be changed to account for the new error code.
hansberry@chromium.org
Provides a breakdown of how many times each possible Bluetooth advertisement
unregistration result occurs.
The bucket "Unknown result" indicates that the Bluetooth platform
returned an unknown error code; if it has any counts, the client code should
be changed to account for the new error code.
hansberry@chromium.org
Provides the success rate of starting a Bluetooth discovery session.
hansberry@chromium.org
Provides the success rate of stopping a Bluetooth discovery session.
hansberry@chromium.org
Provides a top-level breakdown of the times a connection to a host has
failed.
An "unknown error" is caused by the host returning an
"unknown error" response code. Tethering timing out and client
connection error are both broken down further in
InstantTethering.ConnectionToHostResult.Failure.TetheringTimeout and
InstantTethering.ConnectionToHostResult.Failure.ClientConnection,
respectively.
hansberry@chromium.org
Breaks down the reasons why the client failed to connect to the hotspot, and
the number of times they occurred.
Note that a client connection can be canceled by a user either via pressing
the Disconnect button or beginning a connection attempt to another host. The
"internal error" case is a general bucket that captures client
errors we don't expect to be significant failure causes.
This histogram breaks down the "client connection error" count of
InstantTethering.ConnectionToHostResult.Failure.
hansberry@chromium.org
Captures the number of times of whether or not first-time setup was required
when tethering timed out.
Starting tethering on the host works like so: if first-time setup is
required on the host, a first-time setup UI is shown on the host; once the
user interacts with it, the provisioning app is called. If first-time setup
is not required, then the provisioning app is directly called. To be clear:
the provisioning app is always run.
There are two possible ways for tethering to time out: either the
provisioning app flaked (crashed or hung, and never called back to Instant
Tethering), or the user never interacted with the first-time setup UI flow
(assuming first-time setup was required).
Because it's very unlikely for the provisioning app to flake, we can read
the "was first-time setup" count as almost always indicative of
the user not interacting with the first-time setup UI. We expect the
"was not first-time setup" count to be low (because, as mentioned,
it's very unlikely for the provisioning app to flake).
This histogram breaks down the "tethering timed out" count of
InstantTethering.ConnectionToHostResult.Failure.
hansberry@chromium.org
Provides a breakdown of the times a connection to a host was either
unsuccessful due to provisioning failure (the carrier disallows tethering)
or "other" (this is captured under
InstantTethering.ConnectionToHostResult.SuccessRate).
This metric captures the rough percentage of connections which are
unsuccessful due to provisioning failure. It is separate from
InstantTethering.ConnectionToHostResult.SuccessRate and the metrics related
to it because provisioning failure is neither truly a success nor an error.
hansberry@chromium.org
Captures the count of successful and failed connection attempts.
This metric counts the top-level user action from beginning to connect, all
the way through success or failure of the connection (excluding any
programmatic retries within the connection attempt).
This metric provides an immediate understanding of the Instant Tethering
connection success rate. The counts of failure are broken down in
InstantTethering.ConnectionToHostResult.Failure.
hansberry@chromium.org
Captures the count of successful and failed connection attempts.
This metric counts the top-level user action from beginning to connect, all
the way through success or failure of the connection (excluding any
programmatic retries within the connection attempt).
This histogram is the background advertisement analog of
InstantTethering.Performance.ConnectionToHostResult.SuccessRate.
hansberry@chromium.org
Breaks down the state of Instant Tethering during user sessions. All states,
except for 'Enabled', indicate that the feature was not active. This
histogram is emitted to each time a condition affecting Instant Tethering's
state, e.g. the user enabling or disabling the feature, or Bluetooth
becoming enabled or disabled.
Note: The "Screen locked" bucket is obsolete, and should not have
any reports.
hansberry@chromium.org
Captures the effective count of successful and failed GATT connection
attempts, including retries. This means that if a GATT connection attempt
fails but then succeeds on a future retry, this is counted as a single
success. In the context of this metric, a failure represents a GATT failure
in all retry attempts.
An individual attempt is considered successful if a GATT connection was
created and authenticated successfully (i.e., the connection was ready for
Instant Tethering to exchange protocol messages).
hansberry@chromium.org
Captures the effective count of successful and failed GATT connection
attempts, including retries. This means that if a GATT connection attempt
fails but then succeeds on a future retry, this is counted as a single
success. In the context of this metric, a failure represents a GATT failure
in all retry attempts.
An individual attempt is considered successful if a GATT connection was
created and authenticated successfully (i.e., the connection was ready for
Instant Tethering to exchange protocol messages).
This metric is the background advertisement analog of
InstantTethering.GattConnectionAttempt.EffectiveSuccessRateWithRetries.
hansberry@chromium.org
Captures the count of successful and failed GATT connection attempts.
An attempt is considered successful if a GATT connection was created and
authenticated successfully (i.e., the connection was ready for Instant
Tethering to exchange protocol messages).
hansberry@chromium.org
Captures the count of successful and failed GATT connection attempts.
An attempt is considered successful if a GATT connection was created and
authenticated successfully (i.e., the connection was ready for Instant
Tethering to exchange protocol messages).
This metric is the background advertisement analog of
InstantTethering.GattConnectionAttempt.SuccessRate.
hansberry@chromium.org
The duration of a batch of host scans. A batch is defined as a series of one
or host scans separated by no more than one minute.
For example, if a scan occurs then stops and does not start back up again,
the metric logged would be the amount of time taken for that scan. However,
if a scan finishes and a new scan starts up again less than a minute after
the previous scan finished, the metric logged would be the time difference
between the start of the first scan and the finish of the second scan.
hansberry@chromium.org
Provides a breakdown of the results of each host scan. This metric is
recorded after each host scan.
Comparing the number of times no hosts were found against the other buckets
can help determine how often a host scan is useful.
The sum of the buckets capturing that a notification was shown can be used
as a baseline of comparison against
InstantTethering.ConnectionToHostResult.ProvisioningFailureRate to roughly
measure engagement with the notification.
hansberry@chromium.org
The duration of time between the start and end of a Tether connection.
Timing starts when the device connects to the Wi-Fi hotspot and ends when
the device becomes disconnected from the Wi-Fi hotspot.
hansberry@chromium.org
Counts the number of interactions a user has with each of the Instant
Tethering notifications.
hansberry@chromium.org
The duration of time between when a client begins to scan and advertise, and
connects to a host (before authentication).
This histogram only considers the time from when the client *sends* an
advertisement, and not when the client *receives* an advertisement. See
InstantTethering.Performance.StartScanToReceiveAdvertisementDuration and
InstantTethering.Performance.ReceiveAdvertisementToConnectionDuration for
histograms that consider when the client receives an advertisement.
This histogram is the foreground advertisement analog of
InstantTethering.Performance.StartScanToConnectionDuration.Background.
hansberry@chromium.org
The duration of time between when a client connects to a host, and
authenticates with that host.
hansberry@chromium.org
The duration of time between when a client connects to a host, and
authenticates with that host.
This histogram is the background advertisement analog of
InstantTethering.Performance.ConnectionToAuthenticationDuration.
hansberry@chromium.org
The duration of time between when a client authenticates with a host, and
receives a ConnectTetheringResponse.
hansberry@chromium.org
The duration of time it takes for the client to connect to the host, from
the moment the user taps 'Connect', until the client connects to the host's
hotspot. This does not include timeouts.
hansberry@chromium.org
The duration of time it takes for the client to connect to the host, from
the moment the user taps 'Connect', until the client connects to the host's
hotspot. This does not include timeouts.
This histogram is the background advertisement analog of
InstantTethering.Performance.ConnectToHostDuration.Background.
hansberry@chromium.org
The duration of time it takes for the client to connect to the provided
hotspot after receiving a ConnectTetheringResponse. This does not include
timeouts.
hansberry@chromium.org
The duration of time it takes for the client to send off a
DisconnectTetheringRequest.
hansberry@chromium.org
The duration of time between when a client authenticates with a host, and
receives a KeepAliveTickleResponse.
hansberry@chromium.org
The duration of time between when a client received a foreground
advertisement from a host, and connected to that host (before
authentication).
hansberry@chromium.org
The duration of time between when a client received a background
advertisement from a host, and connected to that host (before
authentication).
This histogram is the background advertisement analog of
InstantTethering.Performance.ReceiveAdvertisementToConnectionDuration.
hansberry@chromium.org
The duration of time between when a client begins to scan, and connects to a
host (before authentication).
This histogram is the background advertisement analog of
InstantTethering.Performance.AdvertisementToConnectionDuration.
hansberry@chromium.org
The duration of time between when a client begins to scan and advertise, and
receives a foreground advertisement from a host.
hansberry@chromium.org
The duration of time between when a client begins to scan, and receives a
background advertisement from a host.
This histogram is the background advertisement analog of
InstantTethering.Performance.AdvertisementToConnectionDuration.
hansberry@chromium.org
The duration of time between when a client authenticates with a host, and
receives a TetherAvailabilityResponse.
hansberry@chromium.org
Provides a breakdown of how each Tether session ended. A session begins when
a device is first connected to a host's hotspot, and ends when the device is
no longer connected to the hotspot. This metric is recorded at the end of
each session.
hansberry@chromium.org
Provides the count of the number of users who have the Instant Tethering
toggle enabled vs. disabled on startup. This metric is logged each time a
user logs into a Chromebook.
hansberry@chromium.org
Provides the count of the number of times users have enabled or disabled the
user preference for Mobile data. This metric is logged each time the value
is toggled.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, which
may be either accept or deny. This is only recorded for overridable SSL
warnings with a CERT_AUTHORITY_INVALID warning. Timing begins when user
first focuses on the page.
meacer@chromium.org
User action when the user is shown a captive portal error page.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, which
may be either accept or deny. This is only recorded for overridable SSL
warnings with a CERT_COMMON_NAME_INVALID warning. Timing begins when user
first focuses on the page.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, which
may be either accept or deny. This is only recorded for overridable SSL
warnings with a CERT_DATE_INVALID warning. Timing begins when user first
focuses on the page.
felt@chromium.org
User decision when presented with a security interstitial. As of M44,
subresource interstitials were split into their own entries. As of M52,
social_engineering_ads* and social_engineering_landing* interstitial reasons
are split into their own entries from phishing*.
felt@chromium.org
User decision when presented with a security interstitial, on a site that
the user had previously visited. As of M44, subresource interstitials were
split into their own entries. As of M52, social_engineering_ads* and
social_engineering_landing* interstitial reasons are split into their own
entries from phishing*.
felt@chromium.org
User interactions with a security interstitial. As of M44, subresource
interstitials were split into their own entries. As of M52,
social_engineering_ads* and social_engineering_landing* interstitial reasons
are split into their own entries from phishing*.
Replaced by interstitial.ssl_overridable.* and
interstitial.ssl_nonoverridable.* in Jan 2015 (M42).
felt@chromium.org
User action when the user is shown a SSL interstitial. SHOW_ALL and MORE
refer to the total number of SSL errors; all of the other numbers pertain to
the number of actions related to SSL errors that are overridable. The counts
do not sum to 100%; SHOW_ALL is a superset of SHOW_OVERRIDABLE, which in
turn will be a supserset of the PROCEED/DONT_PROCEED variables.
SHOW_UNDERSTAND is only being used by an experimental field trial. The
interstitials due to captive portals are now recorded in the
"SSLCaptivePortal".
meacer@chromium.org
Record possible states of captive portals. This histogram is emitted
(possibly multiple times to different buckets) whenever a ssl interstitial
page is displayed and captive portal detection is enabled. The captive
portal technique forces a client on a network to see a special web page
(usually for authentication purposes) before using the internet normally.
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.
mab@chromium.org
State of the system clock, as inferred from the build timestamp, when an SSL
CERT_INVALID_DATE error is seen.
Deprecated August 2016. Replaced with interstitial.ssl.clockstate.network2,
which records reasons why network time might be unavailable.
mab@chromium.org
State of the system clock, relative to network time, when an SSL
CERT_INVALID_DATE error is seen.
Deprecated October 2016. Due to a bug, data in this histogram is mislabelled
and should be disregarded. Replaced with
interstitial.ssl.clockstate.network3.
estark@chromium.org
mab@chromium.org
State of the system clock, relative to network time, when an SSL
CERT_INVALID_DATE error is seen.
estark@chromium.org
mab@chromium.org
State of the system clock, relative to network time, when an SSL
CERT_INVALID_DATE error is seen.
felt@chromium.org
The histogram shows the connection types associated with SSL warnings. E.g.,
do more warnings occur on WiFi?
Deprecated September 13 2017.
jww@chromium.org
Specifies when a user enters the page info menu whether or not the user
pressed the SSL decisions revoke button. This can only by done if the user
is in the "Remember Certificate Error Decisions" experiment. This
is logged when the page info UI is closed. Replaced by
.did_user_revoke_decisions2 to keep data separate after changing
functionality to only log when button was visible.
carlosil@chromium.org
Specifies when a user enters the page info menu whether or not the user
pressed the SSL decisions revoke button. This is logged when the page info
UI is closed, only if the button was visible in the page info.
Deprecated Dec 2017 (M65).
jww@chromium.org
Records when a user has made a decision to proceed on a nonoverridable SSL
interstitial. Also records whether a prior decision had been made but the
decision expired.
Deprecated Dec 2017 (M65).
jww@chromium.org
Records when a user has made a decision to proceed on an overridable SSL
interstitial. Also records whether a prior decision had been made but the
decision expired.
Deprecated Nov 2017 (M64).
jww@chromium.org
Emitted when a good certificate is seen, specifying whether the user already
gave an exception for a bad certificate for the same host.
Deprecated December 2017 (M65).
jam@chromium.org
Whether the resource type for a request that succeeded with a good cert and
revoked a certificate exception is for a frame (as opposed to subresource).
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.
carlosil@chromium.org
Records when a user visits a site after clicking through a certificate
warning.
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, when
the user accepts the SSL warning. This is only recorded for overridable SSL
warnings. Timing begins when user first focuses on the page.
meacer@chromium.org
The type of action that the SSL error handler takes.
estark@chromium.org
When handling a certificate date error, Chrome (under certain Variations
Service experiments) will delay displaying the warning interstitial for up
to 3 seconds while querying a network time service. This histogram records
the amount of time for which the interstitial was delayed on this check. The
histogram is recorded even when a time query is not sent (for example,
because Chrome already had an up-to-date network timestamp that it could
use, or because the client is not in the experimental group that enables
network time queries).
estark@chromium.org
When encountering a certificate error, Chrome looks for the well-known
Superfish certificate in the certificate chain and records this histogram as
true if the Superfish certificate is present and false otherwise. The
Superfish certificate is an indication that the user is vulnerable to
man-in-the-middle attacks because of software installed on their computer.
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.
estark@chromium.org
Recorded when a non-overridable SSL interstitial is shown. The value is true
if the user has seen the same error multiple times (in which case a special
message is added to the interstitial).
estark@chromium.org
Recorded when a non-overridable SSL interstitial is shown for a Certificate
Transparency error. The value is true if the user has seen the same error
multiple times (in which case a special message is added to the
interstitial).
estark@chromium.org
Recorded when an overridable SSL interstitial is shown. The value is true if
the user has seen the same error multiple times (in which case a special
message is added to the interstitial).
estark@chromium.org
Recorded when an overridable SSL interstitial is shown for a Certificate
Transparency error. The value is true if the user has seen the same error
multiple times (in which case a special message is added to the
interstitial).
estark@chromium.org
Recorded whenever the user sees or proceeds through an SSL interstitial for
an error that the user has seen multiple times (in which case a special
message is added to the interstitial).
estark@chromium.org
Recorded whenever the user sees or proceeds through an SSL interstitial for
a Certificate Transparency error that the user has seen multiple times (in
which case a special message is added to the interstitial).
Removed on 8/1/13.
felt@chromium.org
The time between the SSL interstitial display and the user decision, when
the user rejects the SSL warning. This is only recorded for overridable SSL
warnings. Timing begins when user first focuses on the page.
nyquist@chromium.org
khushalsagar@chromium.org
Status of sending outgoing invalidation message through GCM upsteam.
pavely@chromium.org
Network channel used for invalidations.
Deprecated 2018-01. As of M65 use Mobile.CanonicalURLResult.
gchatz@chromium.org
The result of the operation to retrieve the page's canonical URL.
danyao@chromium.org
When a navigation is committed, the web view URL is expected to match that
of the current back-forward item. WKWebView seems to break this assumption
at times. This histogram counts the frequency of this invariant violation at
the time when a new navigation is committed. True means the URL matches the
current back-forward item.
olivierrobin@chromium.org
The number of times the Content Extension was displayed since last Chrome
foregrounding. Reported when Chrome is put in foregrounded.
olivierrobin@chromium.org
The index of the URL selected by the user in the Content Extension.
jif@chromium.org
The type of content that the user is dragging into Chrome. Because a drag
can contain multiple types of objects, multiple DragContent values may be
recorded for a single drag event.
danyao@chromium.org
When a navigation is finished, the web view URL is expected to match that of
the current back-forward item. WKWebView seems to break this assumption at
times. This histogram counts the frequency of this invariant violation at
the time when a new navigation is finished. True means the URL matches the
current back-forward item.
erikchen@chromium.org
This event is recorded each time a Handoff is received by Chrome on iOS. The
enumeration indicates the source of the Handoff.
gchatz@chromium.org
Tracks the reason for why the In Product Help bubble was dismissed.
pkl@chromium.org
Counts the times when a mailto: URL is tapped by user and whether the URL
has been rewritten for an available native Mail client app or not.
gambard@chromium.org
The type of NTP impressions on iOS, split by type of suggestions shown
(local vs remote vs remote_collapsed).
danyao@chromium.org
The number of navigation started events by navigation type.
danyao@chromium.org
The "true" value of this boolean histogram counts the number of
page loading started events. The "false" value will never be seen.
Deprecated 2017-11.
danyao@chromium.org
Counts different types of navigation and loading events that are relevant to
counting page loads.
danyao@chromium.org
Measures the time from the end of user input in the omnibox to when the page
is fully loaded. Only measures page loads initiated by user typing a URL or
selecting a suggested entry from the URL bar.
mrefaat@chromium.org
The user reaction to the prompt that appears when a website tries to open an
external application repeatedly.
olivierrobin@chromium.org
The action selected by the user in the Search Extension.
olivierrobin@chromium.org
The number of times the Search Extension was displayed since last Chrome
foregrounding. Reported when Chrome is put in foreground.
olivierrobin@chromium.org
The number of items received simultaneously in Chrome from the IOS share
extension.
olivierrobin@chromium.org
Type of the item received from the iOS share extension.
olivierrobin@chromium.org
The delay in milliseconds between the item creation in the extension and its
processing in Chrome.
olivierrobin@chromium.org
The source application that sent the external command to Chrome.
gchatz@chromium.org
The latency in milliseconds between the start of the Share Page operation
and when the UI is ready to be presented.
edchin@chromium.org
Tracks the result of snapshotting when the user enters the tab switcher.
Recorded whenever the user enters the tab switcher.
olivierrobin@chromium.org
The Spotlight Action pressed by the user.
olivierrobin@chromium.org
Tracks the availability of the Spotlight indexation on the device. It is
logged once at each cold start. Note: Spotlight may be available on the
device but disabled by the user.
olivierrobin@chromium.org
Time spent in Spotlight initial indexation of bookmarks.
olivierrobin@chromium.org
Number of bookmarks indexed during initial indexation.
olivierrobin@chromium.org
This event is recorded each time a Chrome Spotlight entry is selected by the
user. The enumeration indicates the nature of the Spotlight entry.
mrefaat@chromium.org
eugenebut@chromium.org
The result of StoreKit handling for a specific iTunes URL. Not Handled will
be logged when the LinksHandler didn't handle a specific URL on purpose (not
supported), and Failure will be logged when a URL that should have been
handled wasn't handled.
mrefaat@chromium.org
Whether the StoreKit loaded the required iTunes product successfully or not.
danyao@chromium.org
WKWebView should notify navigation commit before navigation finish, but
exceptions have been observed. This histogram counts the frequency of this
invariant violation at the time when a new navigation is finished. True
means navigation finish callback happened before navigation commit.
erikchen@chromium.org
Errors that the privileged attachment broker encounters while trying to
broker attachments.
erikchen@chromium.org
Errors that an unprivileged attachment broker encounters while trying to
broker attachments.
avi@chromium.org
The count of the number of characters in JavaScript dialog messages.
Deprecated 2018-06.
avi@chromium.org
The count of the number of characters in JavaScript dialog messages that
were suppressed by the user. Compare with
JSDialogs.CountOfJSDialogMessageCharacters.
Deprecated 2018-06.
avi@chromium.org
The count of the number of characters in JavaScript dialog messages.
Deprecated 2018-06.
avi@chromium.org
The count of the number of newlines in JavaScript dialog messages. (This
does not count breaks inserted by the UI toolkit in wrapping the messages.)
Deprecated 2016-02.
avi@chromium.org
The count of the number of characters in onbeforeunload messages.
Deprecated 2016-02.
avi@chromium.org
The count of the number of newlines in onbeforeunload messages. (This does
not count breaks inserted by the UI toolkit in wrapping the messages.)
avi@chromium.org
The cause of dismissal of JavaScript dialogs.
joenotcharles@chromium.org
Fine-grained (in msec) time between closing a Javascript dialog and opening
another, to track very frequent dialogs.
joenotcharles@chromium.org
Fine-grained (in msec) time between opening a Javascript dialog and opening
another, to track very frequent dialogs.
joenotcharles@chromium.org
Fine-grained (in msec) time between opening a Javascript dialog and closing
it, to track very short-lived dialogs.
avi@chromium.org
For dialogs, whether or not they were spawned by a tab that was foremost.
avi@chromium.org
For onbeforeunload dialogs, the user's choice between staying on the page
and leaving it.
avi@chromium.org
For dialogs, the relationship of the origins of the main frame vs the
alerting frame.
avi@chromium.org
The scheme of the URL showing a JavaScript dialog.
Deprecated 2017-10.
avi@chromium.org
The site engagement values of sites showing onbeforeunload dialogs. Logged
once per dialog, whether shown or suppressed.
Deprecated 2016-10. Site engagement needed to be measured in small buckets
anyway so it was never high-resolution enough for use.
avi@chromium.org
The site engagement values of sites showing dialogs. Logged once per dialog,
whether shown or suppressed.
Deprecated 07/2016 in crbug.com/631204 with KeyboardUmaEventFilter removal.
girard@chromium.org
The time between keystrokes in Aura text fields. The only keystrokes that
are measured are ones that produce a printable character and are not over 5
seconds apart.
xiaohuic@chromium.org
zalcorn@chromium.org
The time between a user pressing the Chrome OS "Search" key and
the second key being pressed down to active a shortcut. e.g. Search + L
would record the time between Search key down and L key down. If the user
pressed multiple keys after Search, we only record the first key down.
jamescook@chromium.org
msw@chromium.org
wutao@chromium.org
Time delay between the user gesture that triggered the keyboard shortcut
viewer dialog (e.g. pressing Ctrl-Alt-/) and the dialog widget being shown,
including layout time for the views::Views.
fhorschig@chromium.org
Android only. Records whenever users faces an action in the accessory bar or
one of its sheets.
fhorschig@chromium.org
Android only. Records whenever users select an action in the accessory bar
or one of its sheets.
fhorschig@chromium.org
Android only. Records how often users encounter the keyboard accessory bar.
Its buckets show the contents when it came up. Every bucket may be logged up
to one time per impression.
fhorschig@chromium.org
Android only. Records how many suggestions a user faced when opening a
sheet. The base histogram counts impressions across all sheets.
fhorschig@chromium.org
Android only. Records which type of suggestion was selected from an open
sheet.
fhorschig@chromium.org
Android only. Records how often the bottom sheet was opened or closed by a
user and the overall count of closures. Closing buckets may be logged up to
one time per trigger. There are suffixes for each specific sheet type.
xiyuan@chromium.org
Tracks cryptohome failure during kiosk launch.
xiyuan@chromium.org
Tracks kiosk launch errors.
xiyuan@chromium.org
blumberg@chromium.org
Records kiosk launches, whether it is an enterprise or consumer kiosk and
whether it is an auto launch or manual launch.
googleo@chromium.org
The actions taken on languages settings, recorded every time they happen.
This histogram will record every single event that happens separately.
googleo@chromium.org
The type of panes which language settings loads.
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.
asvitkine@chromium.org
Logs which Chrome flags from about:flags were active on start up.
dfalcantara@chromium.org
Records how Chrome handled a launch from an Android Home screen shortcut.
dominickn@chromium.org
Records the source of an Android homescreen launch intent used to launch
Chrome.
The Menu item bucket is deprecated as of M57, and will only contain records
for shortcuts added to the homescreen until M56.
For M57+, the Menu item (standalone) bucket contains all launch intents
originating from the add to homescreen menu item that launch to standalone
mode and *are not* WebAPKs. These are sites which do not meet the PWA
eligibility criteria, but have an app manifest that specifies either
standalone or fullscreen display. This bucket also contains PWA *and*
non-PWA intents that were added to the homescreen *prior* to M57, as we
cannot distinguish between them after they are added.
For M57+, the Menu item (shortcut) bucket contains all launch intents
originating from the add to homescreen menu item that launch to a browser
tab, regardless of when the intent was added.
dfalcantara@chromium.org
Records flags (and combinations of flags) that were attached to the Intent
that started ChromeLauncherActivity.
Deprecated 2016-06 -- hit rate is neglible.
dfalcantara@chromium.org
Records whether or not an invalid Android Intent was fired to launch Chrome.
(http://crbug.com/445136)
jamescook@chromium.org
Records when a mojo ash UI service is started, for example the mojo app
version of the keyboard shortcut viewer.
calamity@chromium.org
The different ways Chrome is launched.
piotrs@chromium.org
Records the display mode (as defined in the Web App Manifest spec) at the
launch of the Added to Home screen or installed Web App (including WebAPKs).
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
complex text fragments, the average number of microseconds spent laying out
each node.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
floats, the average number of microseconds spent laying out each node.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, the average number of
microseconds spent laying out each node.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
fixed or absolute positioned, the average number of microseconds spent
laying out each node.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
simple text fragments, the average number of microseconds spent laying out
each node.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
benjhayden@chromium.org
For layouts that considered at least 100 nodes, at least half of which were
table cells, the average number of microseconds spent laying out each node.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
skobes@chromium.org
Records the number of times ScrollAnchor adjusts the scroll offset.
pnoland@chromium.org
Records the status of attempts to restore a serialized scroll anchor.
pnoland@chromium.org
The number of characters in the selector computed for a serialized scroll
anchor. Recorded when a scroll anchor is serialized.
ymalik@chromium.org
Records the number of times scroll anchoring is suppressed because of the
SANACLAP bit being set on an ancestor (see bit.ly/sanaclap).
pnoland@chromium.org
The time it took to compute the selector of a serialized anchor element.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ymalik@chromium.org
The time it took to find a suitable anchor element.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
pnoland@chromium.org
The time it took to restore the scroll anchor using the serialized anchor
element.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
chaopeng@chromium.org
input-dev@chromium.org
We are considering allowing JS scrolling to prevent browser scroll position
restoration. This histogram measures the impact of that change, in terms of
how often restoration would be prevented by JS Scroll. Recorded after each
successful scroll restoration attempt.
cmumford@chromium.org
The result of an open attempt of a leveldb.
Deprecated 2017-10. Superceded by LevelDB.SharedCache.KBUsed.
cmumford@chromium.org
The estimated size (in bytes) of the leveldb shared cache. Recorded once per
UMA ping.
cmumford@chromium.org
The number of databases currently using the shared block cache. Recorded
once per UMA ping.
cmumford@chromium.org
The estimated size (in kilobytes) of the leveldb shared cache. Recorded once
per UMA ping.
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.
cmumford@chromium.org
Tracks the success rate of deleting an unused leveldb table backup file.
dgrogan@chromium.org
Methods where leveldb's Chromium environment has IO errors.
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.
dgrogan@chromium.org
PlatformFileErrors encountered by a single leveldb method.
cmumford@chromium.org
Errors (base::File::Error) encountered by a single leveldb method.
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewLogger.
dgrogan@chromium.org
Errno of errors encountered in NewLogger.
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.NewSequentialFile.
dgrogan@chromium.org
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.
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileAppend.
dgrogan@chromium.org
Errno of errors encountered in WritableFileAppend.
Deprecated 2015-05. As of M43 use LevelDBEnv.IOError.BFE.WritableFileFlush.
dgrogan@chromium.org
Errno of errors encountered in WritableFileFlush.
dgrogan@chromium.org
Number of directories missing when Non-IDB LevelDBEnv tries to create a Lock
file.
Deprecated as of September 20, 2017.
cmumford@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.
As of M54 no longer creating or using table backup files.
dgrogan@chromium.org
Success indicates a successful backup or restore operation for .ldb table
files when used by LevelDB clients other than IndexedDB.
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, as LevelDBEnv only sleeps when retries are
needed.
mek@chromium.org
Delay between the browser process receiving changes and those changes being
written to the DB.
chengx@chromium.org
This metric records the LoadLibraryExW and LoadLibraryW Windows API call
results, which are used in native_library_win.cc.
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
Percentage of the native library code pages resident in memory. Recorded
immediately before the library prefetching kicks in, only on Android.
lizeb@chromium.org
Detailed status of the library prefetch final status. This is an expanded
version of LibraryLoader.PrefetchStatus. Android only, recorded at most once
per browser startup.
lizeb@chromium.org
Indicates whether the forking of a child process to prefetch the native
library succeeded. Android only, recorded at most once per browser startup.
timbrown@chromium.org
thomasanderson@chromium.org
The Linux distro used. Logged on each start up.
thestig@chromium.org
The version of glibc used. (Linux only) Logged on each start up.
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.
thomasanderson@chromium.org
RTT between Chrome and the X11 server. Tracked in X11EventSource by
measuring the latency to receive a property event after changing a property.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
alexilin@chromium.org
The number of origins that were preconnected for a page load. It includes
preconnect attempts that don't result in new opened connection. Logged after
the preconnect manager completes all jobs attached to the page load.
alexilin@chromium.org
The percentage of origins that were preconnected and requested by a page
load to the total number of origins that were preconnected for a page load.
Logged after the preconnect manager completes all jobs attached to the page
load.
alexilin@chromium.org
When the loading predictor has origins in the local database for a given
navigation to preconnect and preresolve, the count of predicted origins.
alexilin@chromium.org
When the loading predictor has origins in the local database for a given
navigation to preconnect and preresolve, the precision of the predictions in
percentage. This is computed as 100 \times \frac{correct
predictions}{predictions}.
alexilin@chromium.org
When the loading predictor has origins in the local database for a given
navigation to preconnect and preresolve, the recall of the predictions, in
percentage. This is computed as 100 \times \frac{correct predictions}{all
prefetchable subresources}.
alexilin@chromium.org
When the prefetch predictor has origins in the local database for a given
navigation to preconnect and preresolve, records stats about whether
redirect was predicted correctly or incorrectly.
alexilin@chromium.org
The number of hosts that were preresolved for a page load. It includes only
successful DNS lookups. Logged after the preconnect manager completes all
jobs attached to the page load.
alexilin@chromium.org
The percentage of hosts that were preresolved and requested by a page load
to the total number of hosts that were preresolved for a page load. Logged
after the preconnect manager completes all jobs attached to the page load.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
Records the time measured before starting DNS lookup until after the
connection is complete for main frame subresources observed by the
LoadingPredictor. Only resources that required network connection and
happened before the first contentful paint are recorded.
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.
uthakore@chromium.org
invernizzi@chromium.org
Number of requests made by a private page to resources besides itself.
uthakore@chromium.org
invernizzi@chromium.org
Number of requests made by a public page to resources with reserved IP
addresses.
ssid@chromium.org
Total size of the HTML5 LocalStorage browser-side cache purged in KB when
memory pressure signal was triggered or cache size hit the limits.
ssid@chromium.org
Total size of the HTML5 LocalStorage databases in KB in the browser-side
cache recorded each time a new database is opened in memory.
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.
jam@chromium.org
Size of the HTML5 LocalStorage DB in KB in the renderer-side cache using
Mojo implementation.
jam@chromium.org
Time (in ms) to load HTML5 LocalStorage into the renderer-side cache using
Mojo implementation.
jam@chromium.org
Time (in ms) to load HTML5 LocalStorage into the renderer-side cache using
Mojo implementation, split by size.
ssid@chromium.org
The renderer side cache hit rate metrics for new HTML5 LocalStorage DB
opened.
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.
mek@chromium.org
Total size of the HTML5 LocalStorage browser-side cache purged in KB when
memory pressure signal was triggered or cache size hit the limits.
mek@chromium.org
Total size of the HTML5 LocalStorage databases in KB in the browser-side
cache. Recorded each time a new database is opened in memory.
mek@chromium.org
The result of an attempt to commit localstorage data to the database.
mek@chromium.org
The result of a failed attempt to open a LevelDB database for LocalStorage.
mek@chromium.org
The result of a failed attempt to open a LevelDB database for LocalStorage
on disk.
mek@chromium.org
The result of a failed attempt to open a LevelDB database for LocalStorage
in memory.
mek@chromium.org
The result of attempting to delete the LocalStorage database.
mek@chromium.org
The reason opening a directory for the LevelDB database that backs
LocalStorage failed.
mek@chromium.org
The reason loading an initial snapshot of the localstorage data for an
origin failed.
mek@chromium.org
Whether or not any fixes needed to be made to localstorage data, as a result
of bugs in the migration code in M61/M62. Recorded every time the browser
loads an initial snapshot of the localstorage data for an origin.
mek@chromium.org
The reason opening the LevelDB database that backs LocalStorage failed.
mek@chromium.org
The result of opening the LevelDB database that backs LocalStorage.
mek@chromium.org
The reason reading the schema version of the LocalStorage database failed.
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.
achuith@chromium.org
Chrome OS login failure reason.
achuith@chromium.org
omrilio@chromium.org
Chrome OS histogram that keeps track of the days since the least frequently
used account signed in. Reported on every boot and once a day after that.
alemate@chromeos.org
Records whether a new user's priority prefs sync timed out.
alemate@chromeos.org
Time spent waiting for priority preferences to sync after new user sign in.
The operation will time out after 10s.
glevin@chromium.org
On offline login failure, records whether it is for an existing user.
glevin@chromium.org
On offline login success, records number of attempts, including success.
xiyuan@chromium.org
omrilio@chromium.org
Records the UI flow after a possible password change is detected.
cmasone@chromium.org
The state of Chrome OS owner key and device policy files.
achuith@chromium.org
Time from first display of the login prompt until the user completes signing
in.
elijahtaylor@google.com
yusukes@chromium.org
Time from first display of the login prompt until the existing user
completes signing in.
achuith@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.
achuith@chromium.org
Chrome OS login success reason.
glevin@chromium.org
Time between sending a request to, and receiving a reply from, GAIA token
endpoint to validate TokenInfo.
glevin@chromium.org
Time between sending a request to, and receiving a reply from, GAIA token
endpoint to obtain TokenInfo.
alemate@chromium.org
achuith@chromium.org
Chrome OS histogram that keeps track of number of users who have logged in
in the last 7 days. Reported on every boot and once a day after that.
alemate@chromium.org
achuith@chromium.org
Chrome OS histogram that keeps track of percentage of local users who have
logged in in the last 7 days. Reported on every boot and once a day after
that.
cmasone@chromium.org
Chrome OS histogram that keeps track of the way a user logs in and whether
Chrome OS is running normal or developer mode.
tbansal@chromium.org
Original Blink priority of the request that belongs to an iframe. Recorded
for every request fetched via Blink, but only when the experiment to lower
the priority of iframes is enabled.
tbansal@chromium.org
Original Blink priority of the request that belongs to the main frame.
Recorded for every request fetched via Blink, but only when the experiment
to lower the priority of iframes is enabled.
achuith@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.
vikassoni@chromium.org
Error codes to handle AImage and AImageReader api calls.
avayvod@chromium.org
mlamouri@chromium.org
zhiqiang@chromium.org
Android-specific metric. The time between the moment the backgrounded video
playback is started (meaning the user just resumed the backgrounded video
allowing playback) and the moment it stops being background playback by the
current playing video either going foreground or being paused by the user.
Note: on Android, videos are suspended when backgrounded.
Deprecated as of 08/2017
qinmin@chromium.org
Android: Records whether a regular media URL is HLS (HTTP Live Streaming)
media or not.
Deprecated as of 08/2017
sandersd@chromium.org
Android: Records which HLS prediction based on the original URL was best.
timav@chromium.org
Android: Whether MediaPlayer exited without errors.
Deprecated as of 04/2017
qinmin@chromium.org
Android: Number of consecutive media server crashes monitored before it is
reset to 0. Reset happens if there are no crashes in a minute, or if user
hits the "try again" button on the media throttle info bar.
Deprecated as of 04/2017
qinmin@chromium.org
Android: The distribution of responses to the media throttle infobar prompt.
Deprecated as of June 12, 2017. Replaced by
Media.ChromeArcVideoDecodeAccelerator.InitializeResult.
johnylin@chromium.org
Counts of status values returned from calls to
ArcGpuVideoDecodeAccelerator::Initialize().
mlamouri@chromium.org
Records how long more than one tab is audible at the same time. The
concurrent tabs might change during this period. The time recorded starts
when the browser goes from one to two audbile tabs and stops when it is back
below two.
mlamouri@chromium.org
Records how many tabs were audible when a new tab started to be audible.
mlamouri@chromium.org
Records how many tabs are audible at the same time during the session. It is
recording the maximum audible tab count everytime it increases. In other
words, a session with N concurrent audible tabs will record entries from 1
through N exactly once.
henrika@chromium.org
Size (in audio frames) of native I/O buffers that is set by the audio
manager when calling AUAudioInputStream::Open(). I.e., it is the actual
buffer size and it can differ from the one that the client requested. Only
sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Stored in combination with Media.Audio.RenderFailsWhenBufferSizeChangesMac.
It is set to true if calls to AudioUnitRender has ever worked, i.e., we did
not start to see kAudioUnitErr_CannotDoInCurrentContext error messages
directly from start but there has been at least on successful call to
AudioUnitRender.
henrika@chromium.org
Indicates if the Automatic Gain Control (AGC) is enabled or not. Only
sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'.
mlamouri@chromium.org
avayvod@chromium.org
zqzhang@chromium.org
Records the autoplay source of audios.
hubbe@chromium.org
media-dev@chromium.org
Records time from load starts until audio starts based on autoplay
attribute.
hubbe@chromium.org
media-dev@chromium.org
Records time from load starts until audio starts based on play method.
Deprecated as of 02/2017.
tommi@chromium.org
A boolean that reflects whether or not an error was reported during audio
capture.
grunell@chromium.org
Whether missing callbacks where detected during audio capture. Logged when
AudioInputDevice is stopped.
grunell@chromium.org
The audio input device latency. The time from when a frame was captured
until it reaches Chrome's platform audio implementation. Sampled for every
buffer received from the device, and reports the latency for the first frame
in the buffer.
grunell@chromium.org
The number of captured audio frames that is provided by the operating system
in each callback. Typically, Chrome will want to use a 10 ms buffer (e.g.
480 frames for a sample rate of 48 kHz), but the OS may decide to capture
e.g. 256 frames of audio at a time. If the desired frame size is used, the
emitted value is special-cased to be 0. This histogram then shows how
frequent it is that the desired number of frames is used and if not, the
number of frames used in practice. The number of frames per callback is
normally constant or very rarely changed throughout the lifetime of the
audio stream. The first value that differs from the desired value is stored
and logged when an audio input stream is closed. Any further differences
during the lifetime will be ignored.
grunell@chromium.org
The number of glitches that were detected at the OS level while an audio
stream was active. A glitch is detected if the OS has to skip providing a
set of frames. This value is logged when an audio input stream is closed.
maxmorin@chromium.org
A boolean that reflects whether or not an error was reported during audio
capture for a high latency stream.
maxmorin@chromium.org
This histogram measures the duration of every input stream, as seen from the
renderer. It counts from when it has been successfully started, until it is
stopped. Streams that fail to start are not logged.
grunell@chromium.org
The length in milliseconds of the largest audio glitch that was detected at
the OS level. This value is logged when an audio input stream that has
suffered glitches is closed.
grunell@chromium.org
The combined length in milliseconds of audio glitches that was detected at
the OS level. This is useful to know in particular for audio processing such
as echo cancellation. This value is logged when an audio input stream that
has suffered glitches is closed.
maxmorin@chromium.org
A boolean that reflects whether or not an error was reported during audio
capture for a low latency stream.
jonasolsson@chromium.org
maxmorin@chromium.org
olka@chromium.org
Error codes from AudioInputStreamBroker::ObserverBindingLost. They describe
why an audio input stream ended.
Replaced by Media.Audio.Capture.StreamCallbackError2
maxmorin@chromium.org
When AudioInputDevice is stopped, this stat is recorded with whether an
error callback was ever received over IPC.
maxmorin@chromium.org
When AudioInputDevice is stopped, this stat is recorded with whether an
error callback was ever received over IPC, and in that case whether the
error occurred during or after stream creation.
maxmorin@chromium.org
A boolean that reflects whether or not an error was reported during audio
capture for a virtual stream.
grunell@chromium.org
The number of times a glitch was detected by detecting skipped frames (as
with Media.Audio.Capture.Glitches) and disconituity was flagged by the OS at
the same time (as with Media.Audio.Capture.Win.Discontinuities). Sometimes
these indications are not consistent with each other so this metric helps
understanding how often they aren't. This value is logged when an audio
input stream is closed.
grunell@chromium.org
The audio engine's period between processing passes. See
IAudioClient::GetDevicePeriod. This value is logged when an audio input
stream is opened.
grunell@chromium.org
The number of times the device position was less than expected during the
lifetime of an audio stream. This value is logged when an audio input stream
is closed.
grunell@chromium.org
The number of glitches that were detected at the OS level on Windows while
an audio stream was active, as reported by the OS via the discontinuity flag
(see IAudioCaptureClient::GetBuffer). This value is logged when an audio
input stream is closed.
grunell@chromium.org
The endpoint buffer size for input audio. This value is logged when an audio
input stream is opened.
tommi@chromium.org
Error codes from IAudioClient::Initialize() in
WASAPIAudioInputStream::InitializeAudioEngine on Windows.
grunell@chromium.org
Errors from IAudioClient::Initialize() in
WASAPIAudioInputStream::InitializeAudioEngine on Windows that are related to
the audio format. Each error is split by whether format conversion was used
or not.
tommi@chromium.org
Success/error cases for opening an audio input stream on Windows.
grunell@chromium.org
The maximum stream latency as reported by the OS. See
IAudioClient::GetStreamLatency. This value is logged when an audio input
stream is opened.
ossu@chromium.org
Tracks support and initialization success/failure of the CoreAudio dispatch
override hotfix. Logged during initialization of AudioManagerMac. The fix is
not supported on macOS earlier than version 10.10.
ossu@chromium.org
Logged whenever the CoreAudio dispatch override hotfix needs to look up the
calling function using dladdr(). Once ResumeIO and PauseIO have been
identified, no more lookups should be performed during the session.
henrika@chromium.org
Indicates if the size of the audio unit's IO buffer was changed when
starting an input audio stream. Sampled each time an AUAudioInputStream
instance is closed, i.e., we know that input audio has started as it should
when this value is stored. Can be compared with
Media.Audio.InputBufferSizeWasChangedMac which is only added when input
audio fails to start.
henrika@chromium.org
Indicates if the size of the audio unit's IO buffer was changed when
starting an input audio stream. Only sampled when
Media.Audio.InputStartupSuccessMac reports 'Failure'.
Deprecated Feb 2018. Was put in place to debug missing callback issues that
have since been resolved.
henrika@chromium.org
Lists device properties that have been changed during an audio input stream
session. We update a map of different property changes during a session and
all these values are recorded when an AUAudioInputStream object is closed,
hence multiple enum values can be emitted when the histogram is stored.
Deprecated Feb 2018. Was put in place to debug missing callback issues that
have since been resolved.
henrika@chromium.org
Lists device properties that have been changed during an audio input stream
session. Only sampled when Media.Audio.InputStartupSuccessMac reports
'Failure' and multiple enum values can be emitted each time that happens.
Deprecated May 2017. Restart mechanism is removed.
henrika@chromium.org
Counts the total number of times an attempt to restart input audio has been
done. The value is stored once when a stream is closed and updated when it
has been detected that input audio callbacks are not generated as expected.
henrika@chromium.org
Indicates if audio capturing did start after stream startup was requested.
Sampled once, a few seconds after a stream has been asked to start.
henrika@chromium.org
Indicates if audio capturing started with a small delay or not. Sampled each
time an AUAudioInputStream instance is closed, i.e., we know that input
audio has started as it should when this value is stored. Can be compared
with Media.Audio.InputStartWasDeferredMac which is only added when input
audio fails to start.
henrika@chromium.org
Indicates if audio capturing started with a small delay or not. Only sampled
when Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Indicates if the Mac OSX device is on battery power or not. Only sampled
when Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
The number of logical processors/cores available on the Mac OSX device. Only
sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Number of created default input audio streams. Only sampled when
Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Number of created low-latency input audio streams. Only sampled when
Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Number of created output audio streams. Only sampled when
Media.Audio.InputStartupSuccessMac reports 'Failure'.
olka@chromium.org
Time delta between the moment output device authorization request is
received by the browser and the moment its processessing is finished (and
reply is to be sent back to the renderer if IPC is not closed yet).
maxmorin@chromium.org
When a mojo audio stream factory is destructed, the streams it created are
also destructed. This is a potential source of stat differences between the
new mojo code and the old Chrome IPC code, where streams could potentially
stick around until the destruction of the owning RenderProcessHost. This
histogram measures how many output streams are destructed each time a mojo
output stream factory is destructed.
henrika@chromium.org
The number of physical processors/cores available on the Mac OSX device.
Only sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'.
olka@chromium.org
Number of simultaneous inputs coming to the AudioRendererMixer which renders
audio with user specified latency. The value is logged each time it reaches
a new maximum for the mixer. It is useful for evaluating how mixing audio in
renderer reduces the number of output audio streams going from the renderer
to the browser.
olka@chromium.org
Number of simultaneous inputs coming to the AudioRendererMixer which renders
audio with interactive latency. The value is logged each time it reaches a
new maximum for the mixer. It is useful for evaluating how mixing audio in
renderer reduces the number of output audio streams going from the renderer
to the browser.
olka@chromium.org
Number of simultaneous inputs coming to the AudioRendererMixer which renders
audio with playback latency. The value is logged each time it reaches a new
maximum for the mixer. It is useful for evaluating how mixing audio in
renderer reduces the number of output audio streams going from the renderer
to the browser.
olka@chromium.org
Number of simultaneous inputs coming to the AudioRendererMixer which renders
audio with real time latency. The value is logged each time it reaches a new
maximum for the mixer. It is useful for evaluating how mixing audio in
renderer reduces the number of output audio streams going from the renderer
to the browser.
olka@chromium.org
Subset of audio output latencies encountered by the renderer so far. Logged
each time an audio output with a new latency starts playing. The values are
bitsets where each bit represents corresponding latency according to
AudioLatency::LatencyType. Useful for understanding usecases for audio
output mixing in renderer.
olka@chromium.org
Reflects how regularly browser issues audio requests to renderer. Depends on
how well the system buffer size the browser side renders audio at and the
buffer size it requests from renderer are aligned. When zero, it means
renderer buffer size is a multiple of system buffer size, and render calls
from browser to renderer are issued evenly. When -1, it means the renderer
buffer size is larger than system buffer size, but is not an exact multiple
of it; in this case browser periodically skips a call to renderer. When
positive, floor(value/2) reflects the number of extra consecutive render
requests issued by browser to renderer each time to fulfill the system audio
render request; if (value/2) is not integer, then plus one more extra call
is issued periodically. The metric is recorded on the edge between browser
and renderer. On Mac the system buffer size may vary dynamically, the metric
does not capture that: only the buffer size mismatch introduced by audio
output device configuration is captured.
tommi@chromium.org
The number of frames audio is actually rendered at if the number is
different from the desired number of frames. If the desired frame size is
used, this value will be 0. Typically, Chrome will want to use a 10ms buffer
(e.g. 480 frames for a sample rate of 48kHz), but we might have to render
audio 256 frames at a time. This histogram gives us an indication as to how
frequent that is and what buffer sizes are used in practice. This value is
logged when an audio output stream is stopped.
grunell@chromium.org
The time spent to get audio data from the source. For WebRTC, it's the time
spent in WebRtcAudioRenderer::SourceCallback. Logged every function call,
which is every 10 ms.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
grunell@chromium.org
The maximum time spent to get audio data from the source during a session.
For WebRTC, it's the time spent in WebRtcAudioRenderer::SourceCallback. A
session is between Start() and Stop() of WebRtcAudioRenderer.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tommi@chromium.org
The number of glitches that were detected at the OS level while an audio
stream was active. A glitch is detected if the OS has to skip rendering a
set of frames. This value is logged when an audio output stream is stopped.
jonasolsson@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time delta from an AudioInputDevice sending a RecordStream message to it
getting its first data callback.
jonasolsson@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time delta between the moment a MojoAudioInputIPC instance on the
renderer process requests a new stream from the browser to the moment it
receives a response.
tommi@chromium.org
The length in milliseconds of the largest glitch that was detected at the OS
level. This value is logged when an audio output stream that has suffered
glitches is stopped.
tommi@chromium.org
The combined length in milliseconds of audio glitches. This is useful to
know in particular for audio processing such as echo cancellation. This
value is logged when an audio output stream that has suffered glitches is
stopped.
maxmorin@chromium.org
Similar to Media.Audio.OutputDeviceAuthorizationTime, this histogram
measures the time required for device authorization, but it is measured on
the renderer side when AudioOutputDevice calls RequestDeviceAuthorization on
the IO thread until it receives OnDeviceAuthorized, also on the IO thread.
Note that an authorization timeout will cause OnDeviceAuthorized to be
called, so for platforms that use a timeout, very few times will be above
the timeout value.
olka@chromium.org
Whether audio output device timed out waiting for authorization reply from
the browser side.
jonasolsson@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time delta from an AudioOutputDevice sending its first PlayStream
message to it getting its first data callback.
olka@chromium.org
dalecurtis@chromium.org
Device status received in response to device authorization request.
jonasolsson@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time delta between the moment a MojoAudioOutputIPC instance on the
renderer process requests a new stream from the browser to the moment it
receives a response.
maxmorin@chromium.org
This histogram measures the duration of every output stream, as seen from
the renderer. It counts from when it has been successfully started, until it
is stopped. Streams that fail to start are not logged.
olka@chromium.org
Whether a cached sink was used to get audio output device information, or a
new sink was created for that.
olka@chromium.org
When a new sink is created to get output device information, it is cached.
This metric shows if such a sink is later reused for audio output (can
happen no more than once) or deleted unused after timeout expires. Logged
when one of the abovementioned events takes place.
olka@chromium.org
Whether a sink was created through the sink cache or directly.
jonasolsson@chromium.org
maxmorin@chromium.org
olka@chromium.org
Error codes from AudioOutputStreamBroker::ObserverBindingLost. They describe
why an audio output stream ended.
Replaced by Media.Audio.Render.StreamCallbackError2
maxmorin@chromium.org
When AudioOutputDevice is stopped, this stat is recorded with whether an
error callback was ever received over IPC.
maxmorin@chromium.org
When AudioOutputDevice is stopped, this stat is recorded with whether an
error callback was ever received over IPC, and in that case whether the
error occurred during or after stream creation.
henrika@chromium.org
True if a call to AudioUnitRender failed with an error code of
kAudioUnitErr_CannotDoInCurrentContext (-10863) and the call was preceded
with a change in the native I/O buffer size. This value is logged while
input audio is active but it should be a very rare event.
henrika@chromium.org
Size (in audio frames) the client has asked for when creating an
AUAudioInputStream object. It might not be able to fulfill this request. The
actual size is given by Media.Audio.ActualInputBufferFrameSizeMac. Only
sampled when Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Counts the number of times the system has resumed from power suspension.
Counting is reset each time Chrome restarts. Only sampled when
Media.Audio.InputStartupSuccessMac reports 'Failure'.
henrika@chromium.org
Reports the system uptime in hours for Mac OS X devices. Only sampled when
Media.Audio.InputStartupSuccessMac reports 'Failure'.
dalecurtis@chromium.org
Bits per channel of HTML5 audio sample data.
grunell@chromium.org
Whether there is input audio glitches due to dropped input audio data or
not. Sampled when a low-latency input audio stream is destructed.
grunell@chromium.org
The percentage of input audio data that was dropped at the browser/renderer
boundary due to for example buffer overflow in the writer side buffer or in
the socket. Reported at the destruction of low-latency audio input stream.
grunell@chromium.org
The percentage of input audio data blocks that had to be buffered because
there was not room in the shared memory ring buffer on the browser/renderer
boundary. This happens if the reading side hasn't read data in time.
Reported at the destruction of low-latency audio input stream.
Deprecated as of Jan 2018.
minyue@chromium.org
Captures bit-exact audio repetitions with pre-defined look back time. As
soon as a repetition is detected, its look back time is reported. Ideally,
no reports should be generated.
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::
Deprecated as of 02/2017.
dalecurtis@chromium.org
Whether capture started successfully after an input stream startup was
requested.
grunell@chromium.org
Every 15 seconds during the lifetime of an audio input stream, the sound
level is measured, see AudioInputController::CheckAudioPower(). If the level
is below a certain threshold, it's considered "silence". Otherwise
it's considered "audio". This metric shows whether there was only
silence, only audio, or both, during the lifetime of a stream. If logged
before the first measurement, i.e. if the lifetime is less than 15 seconds,
"no measurement" is reported. If there is no audio data provided
by the OS during the lifetime of the stream, for example because of a bug,
measurements will not be performed and "no measurement" is
reported.
dalecurtis@chromium.org
Measures the time taken for AudioInputDeviceManager::
dalecurtis@chromium.org
Measures the time taken for AudioOutputController::
maxmorin@chromium.org
A boolean that reflects whether or not an error was reported during audio
rendering, reported after a stream has stopped, if it was started.
maxmorin@chromium.org
Whether an AudioOutputController succeeded in creating and opening an output
stream proxy. Only logged for the initial creation, subsequent re-creations
due to device change events are logged in the
Media.AudioOutputController.ProxyStreamCreationResultForDeviceChange
histogram.
maxmorin@chromium.org
Whether an AudioOutputController succeeded in creating and opening an output
stream proxy after receiving a default device change event.
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.
olka@chromium.org
Whether a low latency stream to be rendered through the resampler was opened
successfully or which type of fallback stream was used instead. In case a
fake fallback stream is used it means audio rendered through the resampler
will be muted. In case fallback fails entirely, renderer callback error will
be signalled.
marinaciocea@chromium.org
This histogram is the 3nd potential failure step in
CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram
is input for
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetMixFormatResult
histogram.
marinaciocea@chromium.org
This histogram is the 1st potential failure step in
CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram
is input for
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceResult
histogram.
marinaciocea@chromium.org
This histogram is the 2nd potential failure step in
CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram
is input for
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateClientResult
histogram.
marinaciocea@chromium.org
This histogram is the last potential failure step in
CoreAudioUtil::GetPreferredAudioParameters.
marinaciocea@chromium.org
This histogram is the 4nd potential failure step in
CoreAudioUtil::GetPreferredAudioParameters. The success% of this histogram
is input for
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetDevicePeriodResult
histogram.
olka@chromium.org
Records format used by AudioManager to create audio output stream proxy. If
a fake stream is created it results in muted audio playback.
On Windows, the failure reasons that can lead to fake stream creation are
tracked with the following histograms:
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceEnumeratorResult
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateDeviceResult
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.CreateClientResult
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetMixFormatResult
Media.AudioOutputStreamProxy.GetPreferredOutputStreamParametersWin.GetDevicePeriodResult
henrika@chromium.org
Captures if render-side audio glitches are detected or not. Sampled when a
low-latency output audio stream is destructed.
Deprecated Mar 2016 in favor of a new PipelineStatus code.
scherkus@chromium.org
Captures statistics for various AudioRendererImpl events.
Deprecated 02/2017. No longer needed.
grunell@chromium.org
The maximum number of simultaneous audio render streams over IPC created in
AudioRendererHost for a render process. Logged at render process shutdown.
Deprecated 02/2017. No longer needed.
grunell@chromium.org
The maximum number of simultaneous audio render streams over IPC created in
AudioRendererHost for all render processes. Logged at render process
shutdown.
dalecurtis@chromium.org
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).
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
How long it take for the audio manager instance to be created by the audio
service, in case the audio service owns the audio manager.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time interval when the audio service has connections, computed from the
moment the first bind request is received to the moment when the last
connection is closed.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time interval when the audio service has no connections, computed from
the moment the last connection is closed until quit closure is called or a
new bind request is received.
Deprecated 06/2018. Split into Media.AudioService.ObservedInitialDowntime
and Media.AudioService.ObservedDowntime2.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The audio service downtime, observed from the browser process. The downtime
interval is measured either from when the audio service listener is
initialized to the first audio service start, or from the audio service
shutdown to the next startup.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The audio service downtime, observed from the browser process. The downtime
interval is measured from the audio service shutdown to the next startup.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The audio service downtime, observed from the browser process. The downtime
interval is measured from when the audio service listener is initialized to
the first audio service start.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The termination status of the audio service process, observed from the
browser process.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The start result of the audio service, observed from the browser process.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The startup time of the audio service, observed from the browser process.
The startup time interval is measured from when a connect request results in
the audio service being created to the moment when the audio service is
started.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The uptime of the audio service, observed from the browser process. The
uptime interval is measured from when the audio service starts to when it is
shut down (either normally or through kill/crash). This metric includes
Media.AudioService.Uptime measurements, logged by the audio service on
normal shutdown. A difference between Media.AudioService.ObservedUptime and
Media.AudioService.Uptime indicates buggy audio service behavior.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The time interval between the moment when a client issues a system
information request to the audio service, and the moment it receives the
responce. Logged individually for each request type.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
The uptime of the audio service, observed from the audio service. The uptime
interval is measured from the audio service start to the audio service stop.
dalecurtis@chromium.org
State of the audio thread. A value of "started" is emitted once
the hang monitor has been initialized. If the thread is detected as hung
later, a value of "hung" is emitted. If the hung thread later
recovers a value of "recovered" is emitted.
grunell@chromium.org
State of the media stream audio track processing, sampled once during the
life time of a MediaStreamAudioProcessor.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
The result of autoplaying video elements in cross-origin iframes.
liberato@chromium.org
Record a count for each frame sent to the client by AVDA, separated by what
type of frame it is: Non Overlay, secure overlay, etc.
liberato@chromium.org
Record a count for each frame sent to the client by AVDA. True counts
indicate that the frame was an overlay (SurfaceView). False counts are for
Non Overlay frames. This will be deprecated in favor of
Media.AVDA.FrameInformation in M63.
Deprecated 03/2016. No longer needed.
watk@chromium.org
The time that a bitstream buffer spends in AVDA's pending bitstream buffer
queue before it is fed to MediaCodec.
Deprecated 10/2016. No longer needed.
liberato@chromium.org
Number of times that AVDA stopped decoding because MediaCodec failed to
provide a FORMAT_CHANGED message before sending decoded frames back. True
counts indicate instances where FORMAT_CHANGE was missed, while false
instances indicate any MediaCodec initialization by AVDA.
Deprecated 10/2016. No longer needed.
watk@chromium.org
The number of concurrently running AndroidVideoDecodeAccelerators. Logged
during each AVDA initialization.
Deprecated 10/2016. No longer needed.
liberato@chromium.org
Number of times that AVDA's deferred rendering encountered a virtual GL
context. True counts indicate virtual, false counts indicate not.
Deprecated 06/2018. This has been renamed to
Media.CodecImage.SurfaceTextureGLOwner.WaitTimeForFrame and
Media.CodecImage.ImageReaderGLOwner.WaitTimeForFrame.
liberato@chromium.org
Time spent waiting for a frame to become available in a Non Overlay after
requesting that MediaCodec renders it.
hubbe@chromium.org
media-dev@chromium.org
Kb read by media demuxer from MultiBuffer cache.
hubbe@chromium.org
media-dev@chromium.org
Kb read by from network into MultiBuffer cache.
scherkus@chromium.org
Whether a media response might be used to satisfy a future request.
Deprecated as of Dec 18, 2017. Replaced by
Media.GpuArcVideoDecodeAccelerator.InitializeResult.
johnylin@chromium.org
Counts of status values returned from calls to
ChromeArcVideoDecodeAccelerator::Initialize().
mfoltz@chromium.org
The average number of delayed and dropped frames for the ChromeCast
application. Reported every 5 seconds.
Deprecated 07/2015 in issue 508534.
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.
vikassoni@chromium.org
Time spent waiting for a frame to become available in a Non Overlay
(AImageReader mode) so that MediaCodec can render it. This time is recorded
before the frame is rendered.
liberato@chromium.org
Time spent waiting for a frame to become available in a Non Overlay
(SurfaceTexture mode) so that MediaCodec can render it. This time is
recorded before the frame is rendered.
mlamouri@chromium.org
media-dev@chromium.org
Records events related to click through rate (CTR) calculation.
The CTR can be calculated by computing "Interacted" /
"Displayed". "Interacted", for buttons, means that they
were clicked. For sliders, it will reflect any change in the internal state
and includes other events in addition to clicks. "Displayed" means
that the control element was meant to be displayed in the controls. It does
not mean that the user have seen the element so is not to be confused with
visibility. Furthermore, because the controls UI changes while loading,
"Displayed" is only computed when metadata are available unless
preloading was disabled on the element or the browser.
Deprecated July 2017 in favor of Media.Controls.CTR.DownloadButton.
mlamouri@chromium.org
nyquist@chromium.org
media-dev@chromium.org
Records events and user interactions related to the download button shown on
media elements.
beccahughes@chromium.org
media-dev@chromium.org
Records the amount of time the overflow menu is displayed until the user
clicked on a menu item. The overflow menu is shown by clicking the three
dots on the media controls and is used to show more controls when there is
not enough space. This histogram will record up to 100 seconds with accuracy
to the second.
beccahughes@chromium.org
media-dev@chromium.org
Records the amount of time the overflow menu is displayed until the user
dismissed the menu without clicking on a menu item. The overflow menu is
shown by clicking the three dots on the media controls and is used to show
more controls when there is not enough space. This histogram will record up
to 100 seconds with accuracy to the second.
Deprecated May 19 2016 in favor of Media.Controls.Show.{Audio,Video}
mlamouri@chromium.org
Record whether the default media controls were shown and why every time they
could be shown.
mlamouri@chromium.org
Record whether the default media controls of an audio element were shown and
why every time they could be shown. Note that audio elements that were not
insterted to the DOM and do not have a controls attribute are not taken into
account.
mlamouri@chromium.org
Record whether the default media controls of a video element were shown and
why every time they could be shown.
ajm@chromium.org
The state of the user selected virtual beamforming audio device on CrOS.
It's logged whenever the format of the audio input stream is queried, which
at least happens on stream startup, but could happen at other times as well.
liberato@chromium.org
sandersd@chromium.org
tmathmeyer@chromium.org
This enum measures whether or not d3d11 is supported and if not, what the
reason is.
Deprecated Sep 15 2015 in favor of Media.DetectedAudioCodecHash
jrummell@chromium.org
Audio codec used in HTML5 media.
jrummell@chromium.org
Audio codec used in HTML5 media. Reporting corrected in M51 to include all
detected audio codecs, not just those up to and including the first one
supported.
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.
wolenetz@chromium.org
Number of detected audio tracks in HTML5 media. Not all may be usable by the
player.
wolenetz@chromium.org
Number of detected text tracks in HTML5 media. Not all may be usable by the
player.
wolenetz@chromium.org
Number of detected video tracks in HTML5 media. Not all may be usable by the
player.
Deprecated Sep 15 2015 in favor of Media.DetectedVideoCodecHash
jrummell@chromium.org
Video codec used in HTML5 media.
jrummell@chromium.org
Video codec used in HTML5 media. Reporting corrected in M51 to include all
detected video codecs, not just those up to and including the first one
supported.
Removed 10/2015 in favor of Permissions.Action.
Please list the metric's owners. Add more owner tags as needed.
Measures the actions taken in the media infobar, which prompts the users for
device permission.
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.
Removed 03/2017 in favor of Media.Duration2 with larger max bucket.
scherkus@chromium.org
Duration in milliseconds of HTML5 media (when known).
dalecurtis@chromium.org
Duration in milliseconds of HTML5 media (when known).
jbauman@chromium.org
sandersd@chromium.org
Whenever an error is logged from the DXVAVDA, this records the line in
dxva_video_decode_accelerator.cc where the failure occurred.
jbauman@chromium.org
sandersd@chromium.org
Whenever an error is logged from the DXVAVDA picture buffer code, this
records the line in dxva_picture_buffer_win.cc where the failure occurred.
This histogram can only meaningfully be compared between different versions
of Chromium if no line numbers in that file changed between those versions.
liberato@chromium.org
sandersd@chromium.org
This enum measures how often each of the various DXVAVDA PictureBuffer
display mechanisms are used. Each count represents the mechanism selected
at the end of DXVA::Initialize; i.e., there is one count per decoder.
sandersd@chromium.org
Result of EME promises that were handled by Chromium code.
Deprecated 02/2016 with removal of prefixed EME.
xhwang@chromium.org
addKey result
Deprecated 02/2016 with removal of prefixed EME.
xhwang@chromium.org
cancelKeyRequest result.
xhwang@chromium.org
Size in KB of the last file successfully read by the CDM through CDM FileIO
before a specific error happens. This is reported only when the error
happens, which should be rare.
xhwang@chromium.org
Size in KB of the first file successfully read by the CDM through CDM
FileIO. This is recorded once per CDM instance.
media-dev@chromium.org
The actual time spent by the CDM reading a file.
media-dev@chromium.org
The actual time spent by the CDM writing a file.
media-dev@chromium.org
The status of CDM host verification. This is reported per CDM load.
xhwang@chromium.org
Chromium could support multiple versions of CDM interface. This metric
records the CDM interface version that the CDM created by Chromium uses.
This is recorded once per CDM instance.
media-dev@chromium.org
The error code of a library CDM load failure. Only reported on Windows.
media-dev@chromium.org
The result from an attempt to load a library CDM.
media-dev@chromium.org
The time spent to load a library CDM.
xhwang@chromium.org
Whether the CDM instance is created successfully. Reported each time a CDM
instance creation is attempted, usually as a result of Javascript call of
createMediaKeys().
xhwang@chromium.org
The time it takes to create the CDM instance.
xhwang@chromium.org
Whether EME encrypted event has been fired. Every time a WebMediaPlayerImpl
object is created a "false" value is reported to provide a
baseline. Every time an encrypted event is fired, a "true" value
will be reported. Note that it is possible to have multiple encrypted events
during the lifetime of a WebMediaPlayerImpl object.
xhwang@chromium.org
Whether encrypted media is enabled when requestMediaKeySystemAccess() is
called. User can enable and disable encrypted media in content settings.
Recorded when requestMediaKeySystemAccess() is called but will be reported
at most once per renderer process.
jrummell@chromium.org
media-dev@chromium.org
The encryption scheme used by the audio stream in an HTML5 video. Reported
when metadata is available if the initial config is encrypted.
jrummell@chromium.org
media-dev@chromium.org
The encryption scheme used by the video stream in an HTML5 video. Reported
when metadata is available if the initial config is encrypted.
Deprecated 02/2016 with removal of prefixed EME.
xhwang@chromium.org
generateKeyRequest result.
xhwang@chromium.org
Whether a given WebMediaPlayer instance, with a CDM attached, is played in
an incognito window or in Chrome OS guest mode. Players that never started
playback are excluded. Recorded once at time of player destruction.
Deprecated 02/2016 with removal of prefixed EME.
xhwang@chromium.org
KeyAdded event count.
Deprecated 02/2016 with removal of prefixed EME.
xhwang@chromium.org
KeyError event count.
media-dev@chromium.org
System code count associated with key status.
Deprecated 02/2016 with removal of prefixed EME.
xhwang@chromium.org
Key system support query status and result. Each enum value will be reported
at most once per renderer process.
media-dev@chromium.org
Whether the CDM is available for the key system or not. In normal cases,
this is reported once per render process if the EME API is used. In rare
cases it could be reported more than once if the CDM is not available and
then is component updated.
media-dev@chromium.org
Whether MediaCrypto is available on a MediaDrm-based CDM. Reported once per
MediaDrmBridge creation. In normal cases it should always be available.
media-dev@chromium.org
Whether MediaDrmBridge supports the key system. Reported once per
MediaDrmBridge creation. In normal cases it should always be supported.
media-dev@chromium.org
Whether connection error has happened for MojoCdm. Every time a MojoCdm
object is created a "false" value is reported to provide a
baseline. Every time a mojo connection error happened, a "true"
value will be reported, which typically means a remote CDM process crash.
Renamed to Media.EME.EncryptedEvent in 10/2017.
xhwang@chromium.org
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.
xhwang@chromium.org
System code count in promise rejection.
xhwang@chromium.org
The time it takes to resolve a EME promise.
xhwang@chromium.org
Whether the robustness level of any video capability in the supported
configuration passed into requestMediaKeySystemAccess() is empty. This is
specific to the Widevine key system.
mlamouri@chromium.org
media-dev@chromium.org
Records the reason why the Media Engagement data was cleared. Partial
changes and full wipeout will both be recorded as one event.
beccahughes@chromium.org
media-dev@chromium.org
Recorded when the Media Engagement Preloaded List is checked whether a
string is present on that list. If the check was successful then the result
of the check is recorded in this histogram. If the check was not successful
then the reason for the check failing is recorded.
beccahughes@chromium.org
media-dev@chromium.org
Recorded when data is loaded into the Media Engagement Preloaded List. If
the load is successful then "loaded" is recorded to this
histogram. If the load was not successful then the reason why is recorded to
this histogram.
mlamouri@chromium.org
media-dev@chromium.org
Time taken to load the Media Engagement Preloaded List. It should be
recorded once per load of the list which will be once per start up with
additional loads when the list is updated while running.
mlamouri@chromium.org
media-dev@chromium.org
Time taken to lookup an entry in the Media Engagement Preloaded List. This
is recorded for every lookup, regardless of its success.
beccahughes@chromium.org
media-dev@chromium.org
The media engagement score recorded at the time of playback. It is converted
to a percentage so should be divided by 100 to get the actual score. It is
only recorded for playback that is either lacking an audio track or not
muted.
beccahughes@chromium.org
media-dev@chromium.org
Media engagement scores for each origin, recorded at Chrome startup. It is
converted to a percentage so should be divided by 100 to get the actual
score.
mlamouri@chromium.org
media-dev@chromium.org
Records creation and playback status of a Media Engagement Session. This is
recorded at the same time as the data is commited into the content settings
database.
mlamouri@chromium.org
media-dev@chromium.org
Records creation and playback status of a restored Media Engagement Session.
This is recorded at the same time as the data is commited into the content
settings database. Restored information are recorded in addition of regular
ones (Media.Engagement.Session).
beccahughes@chromium.org
media-dev@chromium.org
Recorded when the Media Engagement service doesn't determine a player to be
significant. If a player is not significant the reasons why will be
individually recorded to this histogram each time except for the first time
which is recorded to a different histogram.
The significant state of a player is reevaluated any time the state of the
player changes (e.g. muted, playing/paused). If the player was not
considered signficiant and still is not then we will record the reasons why
in this histogram.
beccahughes@chromium.org
media-dev@chromium.org
Recorded when the Media Engagement service doesn't determine a player to be
significant. If a player is not significant the reasons why will be
individually recorded to this histogram the first time only.
The significant state of a player is reevaluated any time the state of the
player changes (e.g. muted, playing/paused). If the player was not
considered signficiant and still is not then we will record the reasons why
in this histogram.
beccahughes@chromium.org
media-dev@chromium.org
Recorded when the Media Engagement service no longer determines a player to
be significant. If a player is no longer significant, the reasons why will
be individually recorded to this histogram.
The significant state of a player is re-evaluted any time the state of the
player changes (e.g. muted, playing/paused). If the player was previously
considered significant and is no longer considered that we will record the
reasons why in this histogram.
beccahughes@chromium.org
media-dev@chromium.org
Recorded when the history is cleared and the media engagement data are
similarly cleared. It records the reduction in score for each affected
origin. The algorithm is made to reduce the score by 0.0 as much as possible
and if it fails, the score will actually become 0.0 so every reduction also
represent the value of the previous score.
Deprecated May 2018; has been 32-bit for years now.
dalecurtis@chromium.org
Bits per channel of the hardware audio device which failed to open in low
latency mode and required high latency fallback.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the Fling application.
Reported every 5 seconds.
Deprecated 07/2015 in issue 508534.
halliwell@chromium.org
The average number of displayed frames for the Fling application. Reported
every 5 seconds.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time needed to pre-buffer A/V data before the actual playback for the Fling
application.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an abort for the Fling application.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an underrun for the Fling application.
dcastagna@chromium.org
Records when a context provider is acquired in media, and when it's released
because a context loss has been detected.
hiroh@chromium.org
Counts of status values returned from calls to
GpuArcVideoDecodeAccelerator::Initialize().
dcastagna@chromium.org
mcasas@chromium.org
GpuMemoryBufferVideoFramePool is called with an unsupported VideoFrame pixel
format. Emitted on VideoFrame arrival.
sandersd@chromium.org
Counts of video decode errors reported to GpuVideoDecoder.
posciak@chromium.org
Results of attempts to GpuVideoDecoder::Initialize().
Deprecated May 2018; has been 32-bit for years now.
dalecurtis@chromium.org
Bits per channel of the hardware audio device.
dalecurtis@chromium.org
Channel count of the hardware audio device.
dalecurtis@chromium.org
Channel layout of the hardware audio device.
dalecurtis@chromium.org
Samples per second of the hardware audio device.
dalecurtis@chromium.org
Samples per second of the hardware audio device (atypical values, in Hz).
dalecurtis@chromium.org
Whether a given WebMediaPlayer instance, after preload, started playback;
recorded once at time of player destruction.
maxmorin@chromium.org
Whether capture started successfully after a high-latency input stream
startup was requested.
Deprecated June 2017. Found that the MediaInfoLoader class (the only user of
this histogram) is no longer used by anyone.
qinmin@chromium.org
The time it takes to perform redirect tracking and a CORS access check while
preparing to play a media file.
Deprecated 05/2015 in Issue 1141703002. FFmpeg is now statically linked.
scherkus@chromium.org
Errors returned by LoadLibraryEx on Windows while attempting to load
ffmpegsumo.dll.
tommi@chromium.org
Error codes that we encounter while setting up an AUAudioInputStream on Mac.
Deprecated and removed from code as of 02/2016.
henrika@chromium.org
Invalid input sample rate when calling AUAudioInputStream::Open on Mac.
henrika@chromium.org
Duration in milliseconds of low-latency audio input streams. Sampled when
the stream is closed by the AudioInputController.
maxmorin@chromium.org
Duration in milliseconds of low-latency audio input streams which never got
any callbacks.
sandersd@chromium.org
Whether the WMPI data source is streaming (does not support range requests).
dalecurtis@chromium.org
Audio IO layer used by the Linux OS, sampled once at startup of the browser.
xhwang@chromium.org
Load type of HTML5 media, such as URL, MediaSource and MediaStream.
Please list the metric's owners. Add more owner tags as needed.
State of the WebRtc local renderer, sampled once during the lifetime of a
local renderer.
maxmorin@chromium.org
Whether capture started successfully after a low-latency input stream
startup was requested.
dalecurtis@chromium.org
The total watch time (see Media.WatchTime) of a given playback divided by
the number of rebuffering events that occured during that playback.
jrummell@chromium.org
Whether the content type provided to HTMLMediaElement would parse with
ParsedContentType or not.
ossu@chromium.org
grunell@chromium.org
Whether or not the MediaElement is at a playback position of infinity when
checking if playback has ended.
mlamouri@chromium.org
media-dev@chromium.org
Recorded when an HTMLMediaElement play() promise is rejected (handled or
not) with the type of rejection.
shenghao@chromium.org
mcasas@chromium.org
The errors HW video encode encounters in MediaRecorder.
shenghao@chromium.org
mcasas@chromium.org
Whether HW video encode is used in MediaRecorder.
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.
toyoshim@chromium.org
Connected input port numbers on the initialization.
toyoshim@chromium.org
Connected output port numbers on the initialization.
toyoshim@chromium.org
The final status of MidiManager on destruction. This can monitor unexpected
failures on initializing platform dependent MIDI stuff.
toyoshim@chromium.org
Reports whether any data was sent or received by a MidiManager. Recorded
once per MidiManager instantiation, upon destruction. MidiManager is
instantiated when the first Web MIDI client starts a session, and destroyed
when the last client ends the session.
toyoshim@chromium.org
Reports sysex message size.
toyoshim@chromium.org
The MidiManager instance use count, but this is not intended to understand
the real API usage because this can be counted by feature scanning scripts
that are often used for footprinting. You may want to track SendReceiveUsage
to monitor only instances that actually send or receive MIDI messages.
sandersd@chromium.org
Records the number of active MojoVideoDecoderService instances that are
alive each time an instance becomes active. An instance is active if
Decode() has been called at least once. This provides an estimate of the
concurrent hardware resource requirements.
acolwell@chromium.org
Audio codec used in Media Source Extensions playback. Set when AddId() is
called during playback.
Deprecated 05/2018. Splicing no longer performed on buffers with estimated
duration. See https://crbug.com/396634.
chcunningham@chromium.org
Categorizes MSE audio splicing by the type of duration used in the
overlapped buffer.
wolenetz@chromium.org
Amount of time taken to destroy one ChunkDemuxer object, not including
initial background task scheduling delay.
wolenetz@chromium.org
Number of detected audio tracks in Media Source Extensions playback. Not all
may be usable by the player.
wolenetz@chromium.org
Number of detected text tracks in Media Source Extensions playback. Not all
may be usable by the player. This count includes only explicitly signalled
tracks in MSE initialization segments parsed from WebM or ISO BMFF
bytestreams.
wolenetz@chromium.org
Number of detected video tracks in Media Source Extensions playback. Not all
may be usable by the player.
Deleted along with browser side MSE implementation.
qinmin@chromium.org
timav@chromium.org
Relative number of late audio frames wrt total number of audio frames in MSE
playback, multiplied by one million. The audio frame is considered late if
it might cause an underrun, i.e. comes from decoder when audio buffer is
already depleted.
Deleted along with browser side MSE implementation.
qinmin@chromium.org
timav@chromium.org
Relative number of late video frames wrt total number of video frames in MSE
playback, multiplied by one million. The video frame is late if it missed
its presentation time as determined by PTS when it comes from decoder. The
rendering policy (i.e. render or skip) does not affect it.
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.
Renamed to Media.LoadType.
acolwell@chromium.org
Whether Media Source Extensions is specified for playback of Media elements.
Sampled when media pipeline starts.
Deleted along with browser side MSE implementation.
qinmin@chromium.org
timav@chromium.org
Duration of an uninterrupted MSE playback. This is the time interval between
the playback starts or resumes and the moment when user stops the playback
by pressing pause, initiating a seek etc. Measured in media time in
milliseconds.
Deleted along with browser side MSE implementation.
qinmin@chromium.org
timav@chromium.org
Relative number of starvations wrt total number of frames in MSE playback,
multiplied by one million. Starvation happens when the player interrupts the
regular playback and asks for more data, conditions are player-specific.
acolwell@chromium.org
Video codec used in Media Source Extensions playback. Set when AddId() is
called during playback.
media-dev@chromium.org
Video codec used in Media Source Extensions playback if the media container
is MP4. Set when AddId() is called during playback.
media-dev@chromium.org
Video codec used in Media Source Extensions playback if the media container
is WebM. Set when AddId() is called during playback.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The audio bit rate as reported by the Netflix application. May be reported
multiple times as network conditions change during playback.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of audio channels as reported by the Netflix application. May be
reported multiple times as network conditions change during playback.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the Netflix
application. Reported every 5 seconds.
Deprecated 07/2015 in issue 508534.
halliwell@chromium.org
The average number of displayed frames for the Netflix application. Reported
every 5 seconds.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Video bit rate as reported by the Netflix application. May be reported
multiple times as network conditions change during playback.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Video height as reported by the Netflix application. May be reported
multiple times as network conditions change during playback.
mlamouri@chromium.org
avayvod@chromium.org
zqzhang@chromium.org
The type of media notification the user clicked to go back to Chrome.
maxmorin@chromium.org
Duration of an audio output stream. Measured in AudioOutputController from
when a stream is started until it is stopped. A stream is stopped when it is
paused, closed (i.e. destructed), or when a device change event causes it to
be restarted.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Whether Pepper players have played sound through its lifetime.
ihf@chromium.org
posciak@chromium.org
Counts of video decode errors reported to plugin.
ihf@chromium.org
posciak@chromium.org
Number of PictureBuffers/textures requested per hardware decoder creation.
This value varies by platform and video. A user visible video may trigger
multiple decoder creations (sometimes every 5 seconds) but would normally
not hold more than 2 sets of buffers at any given time in memory.
ihf@chromium.org
posciak@chromium.org
Vertical video resolution rounded to the nearest bucket. (Corresponds
roughly to the number in 720p.)
prabhur@chromium.org
dalecurtis@chromium.org
Status of the media pipeline at the end of its lifecycle suffixed by stream
and video decoder type.
xhwang@chromium.org
Status of the media pipeline starting process (including demuxer and
renderer initialization). If the media pipeline is destroyed during the
starting process nothing will be reported, but this should relatively rare.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the PlayMovies
application. Reported every 5 seconds.
Deprecated 07/2015 in issue 508534.
halliwell@chromium.org
The average number of displayed frames for the PlayMovies application.
Reported every 5 seconds.
media-dev@chromium.org
Indicates if a suspend initiated for preload=metadata was ideal. I.e. we did
not immediately resume after completing the suspend when signaling
ReadyState::HAVE_FUTURE_DATA.
dalecurtis@chromium.org
Indicates the number of rebuffers a given watch time session had.
miu@chromium.org
Tracks whether a web page allows content to be remoted.
miu@chromium.org
Measured audio content transfer bitrate while remoting content.
miu@chromium.org
Audio channel layout used while remoting content.
miu@chromium.org
Audio codec used while remoting content.
miu@chromium.org
Audio sampling rate while remoting audio content.
miu@chromium.org
Audio sampling rate while remoting audio content (atypical values, in Hz).
Deprecated 11/2017 in issue 788940.
miu@chromium.org
The difference between the estimated transmission capacity and the media
bitrate when capacity is higher.
Deprecated 11/2017 in issue 788940.
miu@chromium.org
The difference between the media bitrate and the estimated transmission
capacity when media bitrate is higher.
Deprecated as no more poster image is being downloaded while remoting
content.
miu@chromium.org
Measures the amount of time it took to ultimately fail to download a poster
image for an HTML5 video while remoting content.
Deprecated as no more poster image is being downloaded while remoting
content.
miu@chromium.org
Measures the amount of time it took to successfully download a poster image
for an HTML5 video while remoting content.
miu@chromium.org
Measures the duration of each remoting session.
miu@chromium.org
Tracks the trigger for starting a remoting session.
miu@chromium.org
Tracks the trigger for stopping a remoting session.
miu@chromium.org
Measures the duration of each remoting session shorter than 15 seconds.
Deprecated 11/2017 in issue 788940.
miu@chromium.org
The estimated content bitrate (including both audio and video) when starting
a remoting session.
miu@chromium.org
Measures how long, from the start of a remoting session, until content began
playing out on the remote device.
miu@chromium.org
Measures how long, from the start of a remoting session, until a message was
received from the remote device indicating initialization succeeded.
miu@chromium.org
Tracks whether audio or video or both are remoted.
Deprecated 11/2017 in issue 788940.
miu@chromium.org
The estimated transmission capacity when starting a remoting session.
miu@chromium.org
Aspect ratio of video while remoting content.
miu@chromium.org
Measured video content transfer bitrate while remoting content.
miu@chromium.org
Video codec used while remoting content.
miu@chromium.org
Video codec profile used while remoting content.
miu@chromium.org
Video width while remoting content.
posciak@chromium.org
Counts of video decode errors reported to RTCVideoDecoder.
Renamed to Media.RTCVideoDecoderInitDecodeSuccess.
posciak@chromium.org
Results of attempts to RTCVideoDecoder::InitDecode().
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.
emircan@chromium.org
Indicates whether we were successful in preserving timestamps in hardware
video encoder session. It is tracked during the session and logged after it
ends.
avayvod@chromium.org
mlamouri@chromium.org
Time during which a media session has been active, in other words, the time
between an activation and deactivation, without counting time while it was
suspended. If a session is activated after being deactivated, there will be
two entries. For example, if a user plays a song but is interrupted by a
phone call, it will only account for the song playing time.
avayvod@chromium.org
mlamouri@chromium.org
The number of times the user paused playback of a media session using other
means than the pause button on the page.
avayvod@chromium.org
mlamouri@chromium.org
The number of times the user started playback of a media session using other
means than the play button on the page.
avayvod@chromium.org
mlamouri@chromium.org
Indicate whether the native requestAudioFocus() call was successful.
avayvod@chromium.org
mlamouri@chromium.org
The number of times the user stopped a media session using other means than
the pause button on the page.
avayvod@chromium.org
mlamouri@chromium.org
The number of times a media session is suspended and why it has been
suspended.
media-dev@chromium.org
zqzhang@chromium.org
The number of times user interacts with MediaSession sorted by action type.
media-dev@chromium.org
Whether a SRC= playback had a poster set at load() when the effective
preload type is "auto". Note that this includes audio playbacks,
since we do not have track metadata at load(); audio elements never have
posters.
media-dev@chromium.org
Whether a SRC= playback had a poster set at load() when the effective
preload type is "metadata". Note that this includes audio
playbacks, since we do not have track metadata at load(); audio elements
never have posters.
media-dev@chromium.org
Video codec used in plain src= (not MSE) HTML5 media if the media container
is MP4.
media-dev@chromium.org
Video codec used in plain src= (not MSE) HTML5 media if the media container
is WebM.
johnme@chromium.org
media-dev@chromium.org
The duration of the user gesture (how long their finger is down), recorded
at the end of each drag gesture. This histogram is split according to the
width of the slider track in CSS px - see histogram name suffix.
johnme@chromium.org
media-dev@chromium.org
The net distance the media scrubber moved, recorded at the end of each drag
gesture, as a percentage of the width of the slider track. This histogram is
split according to the width of the slider track in CSS px - see histogram
name suffix.
johnme@chromium.org
media-dev@chromium.org
The sum of absolute distances the media scrubber incrementally moved,
recorded at the end of each drag gesture, each measured as the change in
media current time. If the scrubber was dragged back and forth before being
released, this will be larger than the value recorded for
Media.Timeline.DragTimeDelta (and may even be larger than the media
duration), otherwise it will be the same as DragTimeDelta. This histogram is
split according to the width of the slider track in CSS px - see histogram
name suffix.
johnme@chromium.org
media-dev@chromium.org
The net distance the media scrubber moved, recorded at the end of each drag
gesture, measured as the change in media current time. This histogram is
split according to the width of the slider track in CSS px - see histogram
name suffix.
johnme@chromium.org
media-dev@chromium.org
The type of user gesture, recorded at the end of each input sequence. For
example holding down the right arrow key with the scrubber focused will only
be logged as a single event. This histogram is split according to the width
of the slider track in CSS px - see histogram name suffix.
johnme@chromium.org
media-dev@chromium.org
The width of the media timeline track in CSS pixels, recorded the first time
a media element with controls starts playing (strictly speaking, it's the
width in CSS pixels ignoring CSS transforms, multiplied by pageZoomFactor,
but deliberately ignoring pinch zoom's pageScaleFactor).
dalecurtis@chromium.org
media-dev@chromium.org
Time in milliseconds from when WebMediaPlayerImpl starts loading until the
first video frame has been shown.
dalecurtis@chromium.org
media-dev@chromium.org
Time in milliseconds from when WebMediaPlayerImpl starts loading until
metadata is known.
Removed from code 2014/6/18.
scherkus@chromium.org
Time in milliseconds from HTML5 media pipeline creation to playing event.
dalecurtis@chromium.org
media-dev@chromium.org
Time in milliseconds from when WebMediaPlayer starts loading until it has
buffered enough to start playback.
hajimehoshi@chromium.org
kouhei@chromium.org
scherkus@chromium.org
Size of HTML5 media (when known), in MB.
scherkus@chromium.org
Reasons a media response won't be used to satisfy a future request.
Removed Feb 2017. Media.UnderflowDuration provides more useful counts.
dalecurtis@chromium.org
The number of times a src= playback has underflowed; i.e. ran out of data.
Removed Aug 2017. Media.UnderflowDuration2.SRC removes zero-weighting so
that we only report actual underflows.
dalecurtis@chromium.org
The amount of time taken to leave the underflow state (i.e. resume playback)
for src= playbacks.
Removed Aug 2017. Media.UnderflowDuration2.EME removes zero-weighting so
that we only report actual underflows.
media-dev@chromium.org
The amount of time taken to leave the underflow state (i.e. resume playback)
for Encrypted Media Extensions (EME) based playbacks.
Removed Aug 2017. Media.UnderflowDuration2.MSE removes zero-weighting so
that we only report actual underflows.
dalecurtis@chromium.org
The amount of time taken to leave the underflow state (i.e. resume playback)
for Media Source Extensions (MSE) based playbacks.
dalecurtis@chromium.org
The amount of time taken to leave the underflow state (i.e. resume playback)
for playbacks. This doesn't report initial zero samples, which was
previously used to compensate for playbacks that don't rebuffer.
scherkus@chromium.org
URL scheme used with HTML5 media. (each URL provides one sample)
acourbot@chromium.org
mcasas@chromium.org
Whether the call to VaapiWrapper's VADisplayState::Initialize() succeeded or
not.
kcwu@chromium.org
Error codes reported by jpeg decode using VA-API hardware jpeg decoder.
shenghao@chromium.org
Result codes reported by jpeg encode using VA-API hardware jpeg encoder.
posciak@chromium.org
Error codes reported by video decode using VA-API hardware video decoder.
acourbot@chromium.org
mcasas@chromium.org
Whether the creation of VaapiWrapper succeeded or not inside VaVDA.
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.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Records the autoplay source of videos. This includes
Media.Video.Autoplay.Muted.
hubbe@chromium.org
media-dev@chromium.org
Records time from load starts until video starts based on autoplay
attribute.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Records the autoplay source of muted videos.
Deprecated as autoplay muted video by attributed is paused when going
offscreen since https://crbug.com/683141.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Records the offscreen playing duration of a muted video autoplaying from
autoplay attribute.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Records the reason why autoplay of muted videos was blocked.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Records muted video started playing with play() become visible at some
point. The UMA for false is not complete since it is recorded in a
destructor which is garbage-collected. Please subtract
Media.Video.Autoplay.Muted "play() method" count with the true
count of this histogram to obtain the real false count.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Records the offscreen playing duration of a muted video autoplaying from
play() method.
avayvod@chromium.org
mlamouri@chromium.org
zqzhang@chromium.org
Status of the unmute action on a video that autoplayed because it was muted.
hubbe@chromium.org
media-dev@chromium.org
Records time from load starts until video starts based on play method.
johnme@chromium.org
media-dev@chromium.org
Whether auto rotation of screen orientation is enabled by the user (if so
the user has not locked the screen orientation at the OS level, though the
orientation may still be locked by apps). Recorded each time
MediaControlsOrientationLockDelegate locks the screen orientation in
response to a video going fullscreen (or loading metadata whilst
fullscreen).
mlamouri@chromium.org
Result of the orientation lock attempt when a video enters fullscreen.
mlamouri@chromium.org
Status of the metadata when attempting to lock the screen orientation for a
fullscreen video.
avayvod@chromium.org
dalecurtis@chromium.org
Records the time distance between consequent keyframes in a video. The new
value is recorded for each video key frame decoded.
Deprecated as of 01/18/2017 in issue 670150. Replaced by
Media.Video.TimeFromForegroundToFirstFrame.DisableTrack and
Media.Video.TimeFromForegroundToFirstFrame.Paused.
avayvod@chromium.org
dalecurtis@chromium.org
Records the time between the moment when the video element is brought to the
foreground and when the video frame compositor outputs the next frame.
avayvod@chromium.org
dalecurtis@chromium.org
Records the time between the moment when the video element that had video
track disabled in the background is brought to the foreground and when the
video frame compositor outputs the next frame. Recorded even if disabling
video track in the background is turned off to collect data for the control
group.
avayvod@chromium.org
dalecurtis@chromium.org
Records the time between the moment when the video element that was paused
in the background is brought to the foreground and when the video frame
compositor outputs the next frame. Recorded even if disabling pausing video
in the background is turned off to collect data for the control group.
mcasas@chromium.org
Video Capture Device captured aspect ratio, as a rounded integer multiplied
by 100. The collection is made in the VideoCaptureController upon reception
of the first frame.
mcasas@chromium.org
Counts appearances of Blacklisted Video Capture devices during enumeration.
This collection happens during first enumeration in the appropriate
platforms' VideoCaptureDeviceFactory.
chfremer@chromium.org
Time it takes from the moment that a VideoCaptureController is requested to
start to the moment the first video frame arrives at
VideoCaptureController::OnFrameReadyInBuffer().
mcasas@chromium.org
Video Capture Device frame rate requested by VideoCaptureManager on
AllocateAndStart(). The collection is made in the VideoCaptureController
upon reception of the first frame.
Deprecated as of 10/2014 in issue 422822. Replaced by
Media.VideoCaptureManager.Event and the two new values 3 and 4 in the enum
VideoCaptureEvent.
grunell@chromium.org
mcasas@chromium.org
Whether any frames were received during a video capture session. This metric
is recorded when a video source is stopped.
mcasas@chromium.org
Video Capture Device captured frame height in pixels. The collection is made
in the VideoCaptureController upon reception of the first frame.
perkj@chromium.org
MacBook hardware version used when Chrome cannot enumerate a video device.
This is used for tracking http://crbug.com/582931.
perkj@chromium.org
Number of video capture devices detected by Chrome during device
enumeration. Zero devices indicate a problem since all MacBooks should have
a built-in camera. This is used for tracking http://crbug.com/582931.
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.
chfremer@chromium.org
Indicates which video capture backend is used on Windows. A count is
recorded each time a new VideoCaptureDeviceFactoryWin instance is created.
chfremer@chromium.org
Counts number of times taking a still image on Windows fails/succeeds.
chfremer@chromium.org
Counts how many retries are needed for calls to MediaFoundation function
GetAvailableDeviceMediaType before getting a result different from
MF_E_INVALIDREQUEST or giving up.
chfremer@chromium.org
Counts how many retries are needed for calls to MediaFoundation function
GetDeviceStreamCategory before getting a result different from
MF_E_INVALIDREQUEST or giving up.
chfremer@chromium.org
Counts how many retries are needed for calls to MediaFoundation function
GetDeviceStreamCount before getting a result different from
MF_E_INVALIDREQUEST or giving up.
mcasas@chromium.org
Video Capture and device enumeration/monitoring API used for Mac OS Lion or
later. Collection is made only once when the flags are parsed and the
appropriate library selected and/or loaded, successfully or not.
henryhsu@chromium.org
Indicates whether we were successful in initializing hardware jpeg decoder
for attempts to VideoCaptureGpuJpegDecoder::Initialize().
mcasas@chromium.org
Measures the time taken for VideoCaptureManager::
grunell@chromium.org
mcasas@chromium.org
Counts video capture event, such as start and stop capture. Note that the
ideal case is 50% start events and 50% normal stop events.
Deprecated 07/2017 in favor of the more differentiated durations.
chfremer@chromium.org
Measures the duration from the time the Browser connected to the video
capture service to the time it closed the connection.
chfremer@chromium.org
Measures the duration from the time the Browser connected to the video
capture service to the time it closed the connection. Entries are only
logged if the service was used for creating an actual capture session as
opposed to enumerating devices only.
chfremer@chromium.org
Measures the duration from the time the Browser connected to the video
capture service to the time it closed the connection. Entries are only
logged if the service was used for enumerating devices only, but not for
creating an actual capture session.
chfremer@chromium.org
Measures the duration from the time the Browser connected to the video
capture service to the time the connection was lost.
Deprecated 07/2017 in favor of the more differentiated durations.
chfremer@chromium.org
Measures the duration from the time the Browser last closed or lost
connection to the video capture service to the time it reconnects.
chfremer@chromium.org
Measures the duration from the time the Browser last closed or lost
connection to the video capture service to the time it reconnects. This
duration only gets logged for reconnects after usage of the service for
capture (as opposed to enumeration-only usage).
chfremer@chromium.org
Measures the duration from the time the Browser last closed or lost
connection to the video capture service to the time it reconnects. This
duration only gets logged for reconnects after enumeration-only usage of the
service.
chfremer@chromium.org
Counts video capture service events, such as startup, shutdown, and
connection lost.
scherkus@chromium.org
Video codec used in HTML5 media.
scherkus@chromium.org
Video codec profile used in HTML5 media.
Deprecated 11/2016 in issue 2506533002.
scherkus@chromium.org
Coded aspect ratio of HTML5 video.
Deprecated 11/2016 in issue 2506533002.
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.
chcunningham@chromium.org
Indicates whether we were successful performing some database operation. See
suffix VideoDecodeStatsDBOperations.
Replaced by Media.VideoFramePixelFormat 05/2015.
mcasas@chromium.org
Pixel format used in HTML5 video. Emitted on video load.
hubbe@chromium.org
media-dev@chromium.org
Video frame color space. Emitted for each video frame.
mcasas@chromium.org
watk@chromium.org
Color space or range used in HTML5 video. Emitted on video load.
Replaced by Media.VideoPixelFormatUnion 08/2015.
mcasas@chromium.org
watk@chromium.org
Pixel format used in HTML5 video. Emitted on video load.
media-dev@chromium.org
The height of the first video frame in an HTML5 video. Reported when the
first video frame is available.
mlamouri@chromium.org
peconn@chromium.org
zqzhang@chromium.org
Every time a video persistence session could be triggered, it records the
result of the attempt.
mlamouri@chromium.org
zqzhang@chromium.org
Record the type of controls a persisted video is using. This is recorded
every time a video enters persistence mode
mlamouri@chromium.org
peconn@chromium.org
zqzhang@chromium.org
Records the length during which a video was in a persistent state. It is
recorded once per video persistence session.
mlamouri@chromium.org
peconn@chromium.org
zqzhang@chromium.org
Records the reason why a video persistence session has ended.
Replaced by Media.VideoFormat 05/2015.
scherkus@chromium.org
Pixel format used in HTML5 video. Emitted on video load.
mcasas@chromium.org
emircan@chromium.org
Pixel format used in capture and 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).
xhwang@chromium.org
Indicates whether video is rendering in low delay mode. It's recorded when a
video starts playing.
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.
maxmorin@chromium.org
Whether capture started successfully after a high-latency input stream
startup was requested.
Deprecated 05/2016.
dcastagna@chromium.org
Number of frame buffers used by Vpx decoder.
Deprecated 05/2016.
dcastagna@chromium.org
Number of frame buffers currently in use by both Vpx decoder and a
VideoFrame.
dalecurtis@chromium.org
Amount of time taken to decode one VP9 frame.
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.
dalecurtis@chromium.org
Watch time is defined as the amount of elapsed media time for audio+video
media aggregated per player instance. A minimum of 7 seconds of unmuted,
foreground media must be watched to start watch time monitoring. Watch time
is checked on a regular basis and reported to UMA upon one of the stop
events mentioned below or at player destruction if none occur prior.
Any one of paused, hidden, or muted is sufficient to stop watch time metric
reports. Each of these has a hysteresis where if the state change is undone
within some time, the watch time will be counted as uninterrupted.
Power events (on/off battery power) have a similar hysteresis, but unlike
the aforementioned properties, will not stop metric collection.
Each seek event will result in a new watch time metric being started and the
old metric finalized as accurately as possible.
olka@chromium.org
dalecurtis@chromium.org
Status of audio sink provided to WebMediaPlayer. If not OK, null sink will
be used for audio output instead.
servolk@chromium.org
Amount of memory used by the WebMediaPlayerImpl and its components.
dalecurtis@chromium.org
Media container extensions seen by WebView that are not supported by the
standard HTML5 playback path. This value is recorded every time a
WebMediaPlayer is created with one of the unsupported containers.
Deprecated 01/2017 as Windows Core Audio is now the only audio input
implementation on Windows.
henrika@chromium.org
Whether Chrome is using Windows Core Audio for audio input or not. Updated
on Windows only when a low-latency audio input stream is created.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average number of delayed and dropped frames for the YouTube
application. Reported every 5 seconds.
Deprecated 07/2015 in issue 508534.
halliwell@chromium.org
The average number of displayed frames for the YouTube application. Reported
every 5 seconds.
Please list the metric's owners. Add more owner tags as needed.
Time needed to pre-buffer A/V data before the actual playback for the
YouTube application.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an abort for the YouTube application.
Please list the metric's owners. Add more owner tags as needed.
Time needed to buffer A/V data after an underrun for the YouTube
application.
vandebo@chromium.org
If a media scan was cancelled, the duration (in ms) it ran.
vandebo@chromium.org
The number of directories with media files found during a scan.
vandebo@chromium.org
Duration in milliseconds taken to do a media scan that ran to completion.
vandebo@chromium.org
The percentage of galleries accepted (not deselected) from the scan result
dialog.
vandebo@chromium.org
The number of galleries added or updated in preferences after a scan.
vandebo@chromium.org
Various usage counts for media galleries.
steimel@chromium.org
media-dev@chromium.org
The type of media that a user is opening via the MediaLauncherActivity.
imcheng@chromium.org
Round trip time for a Cast app availability request. Can be suffixed with
Success or Failure.
mfoltz@chromium.org
Whether opening Cast channel succeeds or not. Recorded when all opening
channel attempts (including retry attempts) finish.
mfoltz@chromium.org
Errors encountered on a Cast channel. Recorded when a Cast channel fails to
open, or when an opened channel fails to respond to keepalive ping request
and times out.
btolsch@chromium.org
The number of Cast devices available from the device cache at the time of a
new network connection.
mfoltz@chromium.org
The number of connected Cast devices. Recorded when browser finishes
discovering Cast devices. Recording happens roughly once per hour.
mfoltz@chromium.org
The number of known Cast devices. Recorded when browser finishes discovering
Cast devices. Recording happens roughly once per hour.
btolsch@chromium.org
The source of discovery for a newly-created Cast sink.
mfoltz@chromium.org
Duration in milliseconds taken to fail to open a cast channel. Recorded when
one opening channel attempt fails.
mfoltz@chromium.org
Duration in milliseconds taken to successfully open a cast channel. Recorded
when one opening channel attempt succeeds.
mfoltz@chromium.org
The number of available DIAL devices. Recorded when browser finishes
discovering DIAL devices. Recording happens roughly once per hour.
mfoltz@chromium.org
The number of known DIAL devices. Recorded when browser finishes discovering
DIAL devices. Recording happens roughly once per hour.
mfoltz@chromium.org
Error encountered while parsing DIAL device description XML text. Recorded
when utility process returns an invalid DIAL device description object to
browser.
takumif@chromium.org
Location the user clicked to open the Media Router dialog.
btolsch@chromium.org
Network connection type reported by DiscoveryNetworkMonitor whenever it
detects a change in the set of networks connected to the host device which
may affect local discovery.
btolsch@chromium.org
Time between network change events reported by DiscoveryNetworkMonitor.
imcheng@chromium.org
The type of Presentation URL used in a PresentationRequest by a web page.
imcheng@chromium.org
Result of a request to the extension (or an unknown) MediaRouteProvider to
create a route.
takumif@chromium.org
Result of a request to the wired display MediaRouteProvider to create a
route.
imcheng@chromium.org
Result of a request to the extension (or an unknown) MediaRouteProvider to
join a route.
takumif@chromium.org
Result of a request to the wired display MediaRouteProvider to join a route.
takumif@chromium.org
Records whether the Media Route Provider succeeded or failed to create a
controller for a media route.
mfoltz@chromium.org
Result of a request to the extension (or an unknown) MediaRouteProvider to
terminate a route.
takumif@chromium.org
Result of a request to the wired display MediaRouteProvider to terminate a
route.
mfoltz@chromium.org
Records how the major version of the Media Router component extension
compares to the major version of the browser.
mfoltz@chromium.org
Reason that the Media Router woke the Media Route Provider event page.
mfoltz@chromium.org
Records the outcome of waking the Media Router component's event page.
takumif@chromium.org
The number of times a Media Router create route response succeeds or fails.
This breaks down the different failure types in to separate buckets.
takumif@chromium.org
The outcome of querying Media Route Providers for a sink by ID.
"Success" indicates that a sink was found. This is recorded when
the user attempts to cast to a sink with a manually entered ID.
takumif@chromium.org
The type of the Media Sink that media is being Cast to. Recorded each time
the user selects a Media Sink to start Casting.
takumif@chromium.org
The source of a Media Router session. This is recorded to keep track of what
kind of media is being streamed.
takumif@chromium.org
The file format of a local media Media Router session. This is recorded when
a casting session begins to keep track of what kind of media is being
streamed.
takumif@chromium.org
The file size of a local media Media Router session. This is recorded when a
casting session begins to keep track of what kind of media is being
streamed, specifically, whether it is a clip or a song, or a full length
film or podcast.
takumif@chromium.org
Duration in milliseconds taken from the user opening the Media Router dialog
to the user closing the dialog. This is only recorded if closing the dialog
is the first action the user takes.
takumif@chromium.org
Duration in milliseconds taken from the Media Router dialog showing the sink
list and being populated with at least one device to the user selecting a
device immediately after to create a new route.
takumif@chromium.org
The index of the sink that was selected in the sink list.
takumif@chromium.org
The number of times a session was successfully started versus failed.
takumif@chromium.org
The number of times a user stops different types of routes.
takumif@chromium.org
Counts the number of devices known and populated to the Media Router dialog
three seconds after the dialog loads. Always expected to be non-negative.
takumif@chromium.org
Duration in milliseconds it takes the WebUI route controls in the route
details view to be populated after the view is opened.
takumif@chromium.org
Duration in milliseconds taken from the user click to open the Media Router
dialog to initializing the dialog with data.
takumif@chromium.org
Duration in milliseconds taken from a user click to open the Media Router
dialog to the initial paint.
takumif@chromium.org
The first action taken by the user after opening the Media Router dialog.
takumif@chromium.org
The view that was shown when the Media Router dialog is initially opened.
takumif@chromium.org
The number of times the user selects a specific cast source type.
takumif@chromium.org
The number of Media Sinks available for Casting a Presentation API URL to
local screens. Recorded at most once an hour, when the Wired Display Media
Route Provider reports an update on the sink count.
jkarlin@chromium.org
The outcome of Entry::WriteData in the memory cache.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
A rough estimate of the private memory footprint of the audio service
process. Recorded once per UMA ping.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
An amount of private memory of the audio service process placed in swap
(VmSwap). Available only on Android and Linux.
marinaciocea@chromium.org
maxmorin@chromium.org
olka@chromium.org
A rough estimate of the shared memory footprint of the audio service
process. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
TBD.
Deprecated 06/2016 Replaced with Memory.Browser.Large2.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by the browser process. Recorded once per UMA
ping. Note the existence of Memory.Browser.Large, which doesn't have
overflow issues. TODO(rkaplow): This should be replaced with
Memory.Browser.Large2 in M54.
Deprecated 03/2018. No direct replacement.
bashi@chromium.org
kouhei@chromium.org
The total committed memory used by the browser process. Recorded once per
UMA ping.
Deprecated 07/2016 as it reports wrong numbers. crbug.com/629354. Replaced
with Memory.Browser.Large2
erikchen@chromium.org
The private working set used by the browser process. Recorded once per UMA
ping.
Deprecated 11/2017 Replaced with Memory.Browser.PrivateMemoryFootprint.
bashi@chromium.org
kouhei@chromium.org
The private working set used by the browser process. Recorded once per UMA
ping.
erikchen@chromium.org
A rough estimate of the private memory footprint of the browser process.
Recorded once per UMA ping.
erikchen@chromium.org
ssid@chromium.org
An amount of private memory of the browser process placed in swap (VmSwap).
Available only on Android and Linux.
erikchen@chromium.org
A rough estimate of the shared memory footprint of the browser process.
Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
TBD.
Deprecated 11/2017. No direct replacement, but
Memory.Renderer.PrivateMemoryFootprint is similar.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each chrome:// renderer process. Each
process provides one sample. Recorded once per process per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active chrome:// renderer processes. Recorded once per UMA
ping.
Deprecated as of Aug 2016. CompressibleString has been reverted once at
https://crrev.com/2227933002.
hajimehoshi@chromium.org
This records the frequency with which JavaScript source strings are
compressed and decompressed in foreground and background tabs. Compressing
runs 10 seconds after the tab goes background and decompressing runs when
JavaScript source string is required (e.g. V8 starts to compile). This
measurement is a preparation to introduce CompressibleString class for
JavaScript source strings to reduce Blink memory usage.
bashi@chromium.org
Available free memory until the system will be in a critical state. Critical
is as defined by the OS (swapping will occur, or physical memory will run
out, etc).
Obsolete as of 2/2017
bashi@chromium.org
Time elapsed between the global state changes.
Obsolete as of 2/2017
bashi@chromium.org
The global state of memory coordinator when a critical pressure notification
is received.
Obsolete as of 2/2017
bashi@chromium.org
The global state of memory coordinator when a moderate pressure notification
is received.
Obsolete as of 2/2017
bashi@chromium.org
The total private working set memory used by the browser and renderer
processes when the memory coordinator changes the global memory state.
Obsolete as of 2/2017
bashi@chromium.org
Android: Records trim memory level when the global state is NORMAL.
Obsolete as of 2/2017
bashi@chromium.org
Android: Records trim memory level when the global state is SUSPENDED.
Obsolete as of 2/2017
bashi@chromium.org
Android: Records trim memory level when the global state is THROTTLED.
reveman@chromium.org
The discardable memory allocation size in KB. Recorded each time a new
discardable memory instance is created.
ericrk@chromium.org
The size of the EGL_ANDROID_blob_cache cache file on disk. Recorded once per
Chrome launch, after the first page has loaded.
Deprecated 12/2017. Replaced by Memory.Browser.PrivateMemoryFootprint.
erikchen@chromium.org
A rough estimate of the private memory footprint of the browser process.
Deprecated 03/2018.
bashi@chromium.org
Amount of reclaimed memory (in terms of the private working set size) after
a purge request on the browser process. Recorded 2 seconds after the purge
request.
erikchen@chromium.org
ssid@chromium.org
The browser process's memory usage reported by the memory instrumentation
service in MB.
erikchen@chromium.org
ssid@chromium.org
The browser process's memory usage reported by the memory instrumentation
service in KB.
bashi@chromium.org
The number of pages compressed per second. Recorded every 60 seconds. Only
recorded on macOS.
hjd@chromium.org
primiano@chromium.org
erikchen@chromium.org
Records how many failed process dumps there were for a given global dump
completed by the memory instrumentation service
(resource_coordinator/memory_instrumentation/coordinator_impl.h). This is
recorded once each time a global dump request is completed.
hjd@chromium.org
primiano@chromium.org
erikchen@chromium.org
Records how long it took the memory instrumentation service
(resource_coordinator/memory_instrumentation/coordinator_impl.h) from
starting working on a global memory dump request until complating that
request. This does not include queuing time (requests are handled serially).
This is recorded once each time a request is completed.
hjd@chromium.org
primiano@chromium.org
erikchen@chromium.org
Number of global memory dump requests queued in by the memory
instrumentation service
(resource_coordinator/memory_instrumentation/coordinator_impl.h). This
includes the request currently being worked on if any. This is recorded once
each time a new request is queued. This happens at least once per UMA ping
to in order to compute Memory.Experimental.Renderer2,
Memory.Experimental.Browser2 etc.
bashi@chromium.org
The number of pages decompressed per second. Recorded every 60 seconds. Only
recorded on macOS.
Deprecated 12/2017. Replaced by Memory.Extension.PrivateMemoryFootprint.
erikchen@chromium.org
A rough estimate of the private memory footprint of an extension process.
erikchen@chromium.org
ssid@chromium.org
The extension process's memory usage reported by the memory instrumentation
service in MB.
erikchen@chromium.org
ssid@chromium.org
The extension process's memory usage reported by the memory instrumentation
service in KB.
erikchen@chromium.org
The physical footprint of the GPU process on macOS. Other measurements fail
to correctly account for OpenGL memory usage. This metric also has flaws
and is not intended for permanent use. It's an emergency measure added to
help debug https://crbug.com/713854. Recorded once per UMA ping.
Deprecated 12/2017. Replaced by Memory.Gpu.PrivateMemoryFootprint.
erikchen@chromium.org
A rough estimate of the private memory footprint of the GPU process.
erikchen@chromium.org
ssid@chromium.org
The gpu process's memory usage reported by the memory instrumentation
service in MB.
erikchen@chromium.org
ssid@chromium.org
The gpu process's memory usage reported by the memory instrumentation
service in KB.
ssid@chromium.org
Records the status of OOM intervention if the feature is turned on, with
various reasons for failure, in the browser process. Recorded once at
browser startup.
bashi@chromium.org
Records state of the intervention (accepted or declined) when the foreground
renderer is crashed after near-OOM intervention is triggered.
bashi@chromium.org
Records the time elapsed between a near-OOM detection and when a navigation
is started.
bashi@chromium.org
Records the reason for stopping near-OOM detection. This isn't recorded when
a near-OOM situation was detected.
bashi@chromium.org
Records the time elapsed between a near-OOM detection and when an OOM
protected renderer was crashed.
ssid@chromium.org
The renderer process' Blink memory usage, as sum of V8, PartitionAlloc and
BlinkGC allocations, when a foreground OOM occurs. This was last recorded
metric by renderer a few seconds before getting killed.
ssid@chromium.org
Records the status of OOM intervention in renderer process if the feature is
turned on, with various reasons for failure. Recorded at each navigation or
reload.
bashi@chromium.org
Records the time elapsed between a near-OOM detection and when a foreground
renderer process was gone. This histogram does not contain OOM protected
crashes.
ssid@chromium.org
bashi@chromium.org
The renderer process' private memory footprint when a foreground OOM occurs.
This was last recorded metric by renderer a few seconds before getting
killed.
ssid@chromium.org
bashi@chromium.org
The renderer process' swap size when a foreground OOM occurs. This was last
recorded metric by renderer a few seconds before getting killed.
ssid@chromium.org,haraken@chromium.org
Records the time since last main frame navigation start on the renderer
process when it OOMs in foreground visible state. Record 0 if no navigation
was started.
Replaced by Memory.Experimental.OomIntervention.RendererVmSizeAtOOMLarge.
ssid@chromium.org
The renderer process' virtual memory usage, when a foreground OOM occurs.
This was last recorded metric by renderer a few seconds before getting
killed.
ssid@chromium.org
bashi@chromium.org
The renderer process' virtual memory usage, when a foreground OOM occurs.
This was last recorded metric by renderer a few seconds before getting
killed.
bashi@chromium.org
Records user decisions on near-OOM intervention.
keishi@chromium.org
The renderer process's memory usage at the specific timing, i.e. after a
page load and 5/10/15minutes after backgrounded.
keishi@chromium.org
The number of loads in a main frame during the lifetime of a render process
(excludes extensions). Emitted when the processes quits.
Deprecated 12/2017. Replaced by Memory.Renderer.PrivateMemoryFootprint.
erikchen@chromium.org
A rough estimate of the private memory footprint of a renderer process.
bashi@chromium.org
Amount of reclaimed memory (in terms of
Memory.Experimental.Renderer.TotalAllocated) after a purge request on a
renderer process. Recorded 2 seconds after the purge request.
keishi@chromium.org
The uptime of a render process in time ticks (excludes extensions). Emitted
when the processes quits.
erikchen@chromium.org
ssid@chromium.org
The renderer process's memory usage reported by the memory instrumentation
service in MB.
erikchen@chromium.org
ssid@chromium.org
The renderer process's memory usage reported by the memory instrumentation
service in KB.
bashi@chromium.org
The number of swap-ins per second. Recorded every 60 seconds.
bashi@chromium.org
The number of swap-outs per second. Recorded every 60 seconds.
sebmarchand@chromium.org
The swap thrashing level, which is recorded periodically. This shows the
cumulative number of seconds that systems spend in each of the swap
thrashing states. Only available on Windows.
sebmarchand@chromium.org
The number of swap-thrashing level state changes for each possible pairwise
state change. Only available on Windows.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the private memory footprint of all processes.
Deprecated 11/2017. Replaced by Memory.Extension.PrivateMemoryFootprint.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each extension process. Each process
provides one sample. Recorded once per process per UMA ping.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the private memory footprint of the extension process.
Recorded once per process per UMA ping.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the shared memory footprint of the extension process.
Recorded once per process per UMA ping.
creis@chromium.org
nasko@chromium.org
The count of active extension processes. Recorded once per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The number of glyph pages present in the renderer when it commits a load.
Since this is per-sub-process, you can get the average number of glyph pages
in the system by multiplying this number with the average number of
renderers. Note that this typically won't count the glyph pages added as a
result of the load that just committed, since layout will happen after the
commit. There are 512 bytes per glyph page, but this number also very
closely approximates the number of glyph width map pages in the same
renderer. The only difference is that if you have font fallback, it will
make a new glyph page and no width page, but in most common cases there is
no fallback). Width pages are 1K each (256 floats), so you could think of
this value as being the number of "1.5K units related to glyphs per
renderer per page load".
Deprecated 11/2017. Replaced by Memory.Gpu.PrivateMemoryFootprint.
hajimehoshi@chromium.org
jamescook@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by the GPU process. Recorded once per UMA
ping.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the private memory footprint of the gpu process.
Recorded once per UMA ping.
erikchen@chromium.org
ssid@chormium.org
An amount of private memory of the GPU process placed in swap (VmSwap).
Available only on Android and Linux.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the shared memory footprint of 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.
Obsolete as of 11/2015
dskiba@chromium.org
Size of messages received by IPC::ChannelReader.
lizeb@chromium.org
Recorded each time a Movable String is (un)parked, with the context:
foreground/background.
lizeb@chromium.org
This records the number of movable Javascript source string resources in a
given renderer, at the time page is backgrounded. Recorded alongside
Memory.MovableStringsTotalSizeKb.
lizeb@chromium.org
This records the total size of movable Javascript source string resources in
a given renderer, at the time page is backgrounded. Recorded alongside
Memory.MovableStringsCount.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Native Client loader process. Each
process provides one sample. Recorded once per process per UMA ping.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Native Client broker process. Each
process provides one sample. Recorded once per process per UMA ping.
oshima@chromium.org
System-wide memory allocation right after a renderer was killed by
oom-killer, roughly equivalent to the sum of memory allocated with malloc()
in userspace plus graphics driver memory.
oshima@chromium.org
System-wide file-backed memory plus free memory right after a renderer was
killed by oom-killer, which should be smaller than or close to what the
kernel uses to trigger low-memory notifications for tab discards. If this is
higher than the kernel's threshold for tab discards, renderers may be killed
due to reasons other than out-of-memory.
oshima@chromium.org
Graphics driver (GEM object) memory right after a renderer was killed by
oom-killer.
oshima@chromium.org
System-wide shared memory right after a renderer was killed by oom-killer.
Used primarily for shared buffers in the graphics system. Tracked because
it's a historical source of leaks on Chrome OS.
oshima@chromium.org
System-wide memory allocation right after a renderer was killed by
oom-killer, roughly equivalent to the sum of memory allocated with malloc()
in userspace plus graphics driver memory.
oshima@chromium.org
System-wide file-backed memory plus free memory right after a renderer was
killed by oom-killer, which should be smaller than or close to what the
kernel uses to trigger low-memory notifications for tab discards. If this is
higher than the kernel's threshold for tab discards, renderers may be killed
due to reasons other than out-of-memory.
oshima@chromium.org
Graphics driver (GEM object) memory right after a renderer was killed by
oom-killer.
oshima@chromium.org
System-wide shared memory right after a renderer was killed by oom-killer.
Used primarily for shared buffers in the graphics system. Tracked because
it's a historical source of leaks on Chrome OS.
dcastagna@chromium.org
primiano@chromium.org
The total number of open file descriptors opened per process. Recorded once
per UMA ping.
dcastagna@chromium.org
primiano@chromium.org
The limit of open file descriptors that can be opened per process. Recorded
once per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of other various utility processes (nacl, gpu, sandbox, zygote,
utility). Recorded once per UMA ping.
Deprecated 11/2017. No direct replacement.
thestig@chromium.org
The private working set used by each Pepper Flash plugin process. Each
plugin process provides one sample. Recorded once per process per UMA ping.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Pepper plugin process. Each plugin
process provides one sample. Recorded once per process per UMA ping.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each Pepper plugin broker process. Each
process provides one sample. Recorded once per process per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of Pepper plugin broker processes, recorded once per metrics
services (UMA) update. See MetricsReportingScheduler for details.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active Pepper plugin processes. Recorded once per UMA ping.
Deprecated due to NPAPI removal.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each plugin process. Each plugin process
provides one sample. Recorded once per process per UMA ping.
Deprecated due to NPAPI removal.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active plugin processes. Recorded once per UMA ping.
chrisha@chromium.org
The memory pressure level, which is recorded periodically. This shows the
cumulative number of seconds that systems spend in each of the memory
pressure states.
chrisha@chromium.org
The number of pressure level state changes for each possible pairwise state
change.
creis@chromium.org
nasko@chromium.org
The count of all active processes. Recorded once per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The current process limit. Recorded once per UMA ping.
Deprecated 06/2016 Replaced with Memory.Renderer.Large2.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each renderer process. Each renderer
process provides one sample. Recorded once per UMA ping. TODO(rkaplow):
This should be replaced with Memory.Renderer.Large2 in M54.
Deprecated 03/2018. No direct replacement.
bashi@chromium.org
kouhei@chromium.org
The total committed memory used by each renderer process. Each renderer
process provides one sample. Recorded once per process per UMA ping.
hajimehoshi@chromium.org
The esitimated memory size which would be reduced when reusing disk cache is
implemented. If it is 100% sure that the encoded data is in disk cache, the
same data in memory can be dropped to reduce memory usage. This is
rencorded when an ImageResource is pruned. See crbug/664437.
Deprecated 11/2017. Replaced by Memory.Renderer.PrivateMemoryFootprint.
bashi@chromium.org
kouhei@chromium.org
The private working set used by each renderer process. Each renderer
process provides one sample. Recorded once per process per UMA ping.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the private memory footprint of the renderer process.
Recorded once per process per UMA ping.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the shared memory footprint of the renderer process.
Recorded once per process per UMA ping.
Deprecated 11/2017. No direct replacement, although
Memory.Total.PrivateMemoryFootprint is similar.
bashi@chromium.org
hajimehoshi@chromium.org
tasak@chromium.org
The private working set used by each renderer process, including all
renderer types, i.e. this includes Chrome renderer, extensions renderer, as
well as regular renderer processes. Each renderer process provides one
sample. Recorded once per process per UMA ping.
Deprecated 01/2018. No direct replacement, although
Memory.Total.PrivateMemoryFootprint is similar.
bashi@chromium.org
hajimehoshi@chromium.org
tasak@chromium.org
The total committed memory used by each renderer process, including all
renderer types, i.e. this includes Chrome renderer, extensions renderer, as
well as regular renderer processes. Each renderer process provides one
sample. Recorded once per process per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Growth speed of the private working set used by each renderer process per 30
minutes. The usage and growth speed is recorded at most every 30 minutes,
not every exact 30 minutes. If the interval is longer than 30 minutes, it
is normalized to a speed KB per 30 minutes. Each renderer process provides
one sample. Recorded once per UMA log unless this is the first time the UMA
log is recorded after startup of the renderer, 30 minutes have not passed
from the last recording of the renderer or the usage goes down. If the usage
goes down, the amount of the shrink will be recorded in the
Memory.RendererShrinkIn30Min histogram.
creis@chromium.org
nasko@chromium.org
The count of active renderer processes. Recorded once per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Shrink speed of the private working set used by each renderer process per 30
minutes. The usage and shrink speed is recorded at most every 30 minutes,
not every exact 30 minutes. If the interval is longer than 30 minutes, it
is normalized to a speed KB per 30 minutes. Each renderer process provides
one sample. Recorded once per UMA log unless this is the first time the UMA
log is recorded after startup of the renderer, 30 minutes have not passed
from the last recording of the renderer or the usage goes up. If the usage
goes up, the amount of the growth will be recorded in the
Memory.RendererGrowthIn30Min histogram.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each sandbox helper process. Each sandbox
helper process provides one sample. Recorded once per process per UMA ping.
reveman@chromium.org
The amount of free space in temporary directory for shared memory files.
Recorded each time a new discardable memory manager instance is created.
Deprecated in 595320 and replaced with Memory.Stats.Win.AvailPageFile2.
georgesak@chromium.org
Windows-only metric that represents the maximum amount of memory the current
process can commit. This value is equal to or smaller than the system-wide
available commit value.
georgesak@chromium.org
Windows-only metric that represents the maximum amount of memory the current
process can commit. This value is equal to or smaller than the system-wide
available commit value.
Deprecated in 595320 and replaced with Memory.Stats.Win.AvailPhys2.
georgesak@chromium.org
Windows-only metric that represents the amount of physical memory currently
available. This is the amount of physical memory that can be immediately
reused without having to write its contents to disk first. It is the sum of
the size of the standby, free, and zero lists.
georgesak@chromium.org
Windows-only metric that represents the amount of physical memory currently
available. This is the amount of physical memory that can be immediately
reused without having to write its contents to disk first. It is the sum of
the size of the standby, free, and zero lists.
Deprecated in 595320 and replaced with Memory.Stats.Win.AvailVirtual2.
georgesak@chromium.org
Windows-only metric that represents the amount of unreserved and uncommitted
memory currently in the user-mode portion of the virtual address space of
the calling process.
georgesak@chromium.org
Windows-only metric that represents the amount of unreserved and uncommitted
memory currently in the user-mode portion of the virtual address space of
the calling process.
georgesak@chromium.org
Windows-only metric that represents the approximate percentage of physical
memory that was in use (0 indicates no memory use and 100 indicates full
memory use).
Deprecated in 595320 and replaced with Memory.Stats.Win.TotalPageFile2.
georgesak@chromium.org
Windows-only metric that represents the current committed memory limit for
the system or the current process, whichever is smaller.
georgesak@chromium.org
Windows-only metric that represents the current committed memory limit for
the system or the current process, whichever is smaller.
Deprecated in 595320 and replaced with Memory.Stats.Win.TotalPhys2.
georgesak@chromium.org
Windows-only metric that represents the amount of actual physical memory.
georgesak@chromium.org
Windows-only metric that represents the amount of actual physical memory.
Deprecated in 595320 and replaced with Memory.Stats.Win.TotalVirtual2.
georgesak@chromium.org
Windows-only metric that represents the size of the user-mode portion of the
virtual address space of the calling process. This value depends on the type
of process, the type of processor, and the configuration of the operating
system. For example, this value is approximately 2 GB for most 32-bit
processes on an x86 processor and approximately 3 GB for 32-bit processes
that are large address aware running on a system with 4-gigabyte tuning
enabled.
georgesak@chromium.org
Windows-only metric that represents the size of the user-mode portion of the
virtual address space of the calling process. This value depends on the type
of process, the type of processor, and the configuration of the operating
system. For example, this value is approximately 2 GB for most 32-bit
processes on an x86 processor and approximately 3 GB for 32-bit processes
that are large address aware running on a system with 4-gigabyte tuning
enabled.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by the browser process. Recorded once per UMA ping if the
system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each chrome:// renderer process. Each process provides one
sample. Recorded once per process per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The amount of memory that swap was compressed into. Recorded once per UMA
ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The ratio of swapped data original size to compressed size. Recorded once
per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each extension process. Each process provides one sample.
Recorded once per process per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by the GPU process. Recorded once per UMA ping if the system
has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Indicates that the system has swapped memory out at least once since boot.
Recorded once per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The amount of memory that is used by swap, including bookkeeping. Recorded
once per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Native Client loader process. Each process provides
one sample. Recorded once per process per UMA ping if the system has
swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Native Client broker process. Each process provides
one sample. Recorded once per process per UMA ping if the system has
swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The number of reads from swap. Recorded once per UMA ping if the system has
swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The number of writes to swap. Recorded once per UMA ping if the system has
swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The amount of memory that was swapped out. Recorded once per UMA ping if
the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Pepper plugin process. Each plugin process provides
one sample. Recorded once per process per UMA ping if the system has
swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each Pepper plugin broker process. Each process provides
one sample. Recorded once per process per UMA ping if the system has
swapped.
Deprecated due to NPAPI removal.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each plugin process. Each plugin process provides one
sample. Recorded once per process per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each renderer process. Each renderer process provides one
sample. Recorded once per process per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each sandbox helper process. Each sandbox helper process
provides one sample. Recorded once per process per UMA ping if the system
has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The sum of all processes' swap. Recorded once per UMA ping if the system has
swapped. See Memory.Swap.Total2 for the same metric with higher precision
bucketing.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
rkaplow@chromium.org
The sum of all processes' swap. Recorded once per UMA ping if the system has
swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each utility process. Each utility process provides one
sample. Recorded once per process per UMA ping if the system has swapped.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by each worker process. Each worker process provides one
sample. Recorded once per process per UMA ping if the system has swapped.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The swap used by the zygote process. Recorded once per UMA ping if the
system has swapped.
Deprecated 09/2016. Replaced by Memory.Total2.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The sum of all processes. This is not aware of shared memory so it is just a
rough estimate. Recorded once per UMA ping. See Memory.Total2 for the same
metric with higher precision bucketing.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the private memory footprint of all processes. Recorded
once per UMA ping.
erikchen@chromium.org
ssid@chromium.org
A rough estimate of the shared memory footprint of all processes. Recorded
once per UMA ping.
Deprecated 11/2017. Replaced by Memory.Total.PrivateMemoryFootprint.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
rkaplow@chromium.org
The sum of all processes. This is not aware of shared memory so it is just a
rough estimate. Recorded once per UMA ping.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each utility process. Each utility process
provides one sample. Recorded once per process per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by each worker process. Each worker process
provides one sample. Recorded once per process per UMA ping.
Deprecated 03/2018. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The count of active worker processes. Recorded once per UMA ping.
Deprecated 11/2017. No direct replacement.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
The private working set used by the zygote process. Each zygote process
provides one sample. Recorded once per process per UMA ping.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Value of getMemoryClass() recorded once upon startup. This is an integer,
device-specific constant correlated with the amount of memory available on
Android device.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Reasons behind evictions of individual tabs, recorded upon each tab
eviction.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Number of loaded (memory-resident) tabs when LowMemory notification is
delivered.
Deprecated 04/2018.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Time between two consecutive LowMemory notification in one foreground
session.
ssid@chromium.org
Whether Chrome is running in low ram mode. This histogram is reported on
every upload by Android devices. A device is considered low-RAM if it has
512MiB of RAM or lower (see SysUtils.detectLowEndDevice()).
Note: The low-RAM determination has changed in M-49, it used to be given
directly by the Android OS.
Deprecated 04/2018 in favor of Android.MemoryPressureNotification.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Memory notifications delivered through system callbacks to Chrome while in
the background.
Deprecated 04/2018 in favor of Android.MemoryPressureNotification.
hajimehoshi@chromium.org
kenjibaheux@google.com
kouhei@chromium.org
Memory notifications delivered through system callbacks to Chrome while in
the foreground - we count LowMemory notification vs particular levels of
TrimMemory foreground notification.
bashi@chromium.org
The amount of reclaimed memory after a tab became inactive.
Deprecated as of 10/2016.
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.
justincohen@chromium.org
The number of memory warnings during a given foreground session.
Deprecated as of 10/2016.
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.
Deprecated as of 07/2018.
gab@chromium.org
The size of the delayed task queue when the loop becomes idle. Diagnosis
metric for https://crbug.com/850450#c4.
Deprecated as of 07/2018.
gab@chromium.org
Reports the delay of a delayed task posted to a MessageLoop. Reported once
per delayed task. Diagnosis metric for https://crbug.com/850450#c4.
gab@chromium.org
The size of the delayed task queue when the loop becomes idle on a UI
thread. Diagnosis metric for https://crbug.com/850450#c4. Note: this metric
is a bit broken on Mac OSX as CFRunLoop doesn't deterministically invoke
MessageLoop::DoIdleWork().
Deprecated as of 07/2018.
gab@chromium.org
Reports the delay for which the MessageLoop successfully slept until an
upcoming delayed task. Reported each time a MessageLoop successfully sleeps
until the next delayed task.
Deprecated as of 07/2018.
gab@chromium.org
Reports the delay for which the MessageLoop had planned to sleep (next
delayed task) before it was woken up early. Reported each time a MessageLoop
is woken up early.
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.
gchatz@chromium.org
tedchoc@chromium.org
The result of the operation to retrieve the page's canonical URL.
dtrainor@chromium.org
Android: The number of browsers installed on the device.
dtrainor@chromium.org
Android: Whether or not the device has a default browser and whether or not
it is a system installed browser.
dtrainor@chromium.org
Android: The number of system installed browsers.
dtrainor@chromium.org
Android: Represents the number of system notifications that were blocked and
could not be shown by type.
dtrainor@chromium.org
Android: Represents the type of notification that was last shown before the
user disabled notification permissions on Chrome. This is only logged the
first time we attempt to show a notification and fail.
awdf@chromium.org
Android: Represents the number of system notifications by type that we
attempted to show but were blocked, due to their notification channel being
blocked. Only applies to devices on Android O and above.
dtrainor@chromium.org
Android: Represents the number of system notifications that will be
successfully shown to the user by type.
qinmin@chromium.org
Android: Records the total data downloaded by completion status.
qinmin@chromium.org
Android: Records the total data wasted during download due to resumptions.
qinmin@chromium.org
Android: Records the reason that a download is canceled.
qinmin@chromium.org
Android: Records various counts related to the save image context menu
option.
qinmin@chromium.org
Android: Records user interaction on the download resumption button.
qinmin@chromium.org
Android: Records the total time for a download by completion status.
qinmin@chromium.org
Android: Records various counts related to the duplicate download infobar.
Deprecated 09/2016 in Issue 647755 with all downloads going through Chrome.
qinmin@chromium.org
Android: Records the reason that Chrome fails to intercept a download and
pass it to the Android DownloadManager.
qinmin@chromium.org
Android: Records the total interruptions for a download by completion
status.
xingliu@chromium.org
Records whether the user accepted or dismissed the dialog to select a
download location.
xingliu@chromium.org
Records the download location dialog type when the dialog is shown to the
user.
xingliu@chromium.org
Records the directory type when the user selects the download directory
through download location dialog or selects the download directory in
download preference. May be recorded even when the user didn't download
anything.
Deprecated 10/2017 in Issue 722320 with the removal of
DownloadNotificationService.hideDanglingSummaryNotification.
dtrainor@chromium.org
Android: Records the situation where we try to fix a standalone downloads
summary notification, which shouldn't be visible to the user. True if the
notification was a foreground notification, in which case we can't dismiss
it and need to attempt a more drastic workaround. False if it was a normal
notification and we can dismiss it easily (this is okay and expected
behavior in some scenarios).
qinmin@chromium.org
Android: Records the number of resumptions for a download by resumption
type. For all resumption types, this is recorded when a download is
finished, completed or cancelled. For automatic resumptions, it is also
recorded when user manually resumes the download to clear the auto retry
count.
qinmin@chromium.org
Android: Records various counts when requesting the storage permission.
justincohen@chromium.org
iOS: Records the status of the privacy page after user taps on the privacy
link on the first run welcome view. This metric is only recorded if and
after the TOS are accepted. This metric is specific to iOS.
gogerald@chromium.org
Android: Records which states of the "first run experience" have
been reached. Each bucket represents a state and recorded everytime the
state changed. Pages can be double counted if the user goes backwards in
the flow.
aruslan@chromium.org
Android: How the user left the sign-in part of the "first run
experience" activity (M-38+).
qinmin@chromium.org
Android: Records the duration that a fullscreen video is played after device
rotates from portrait to landscape mode for the first time, and before it
exits fullscreen. If there is no device rotation or if the video starts with
landscape mode, it is not recorded. If there are mutiple rotations between
portrait and landscape mode, only one record is emitted and it is equal to
the time period from the first rotation to the moment when the video exits
fullscreen.
qinmin@chromium.org
Android: Records the duration that a fullscreen video is played in landscape
mode. If a video starts playing in landscape mode, and then it is switched
back and forth between landscape and portrait mode, only the time period
before the first switch is accounted. If a video starts playing in portrait
mode, it is not recorded.
qinmin@chromium.org
Android: Records whether a fullscreen video is switched from landscape to
portrait mode at any point during playback.
qinmin@chromium.org
Android: Records the device orientation when a video enters fullscreen. The
value is true if device orientation is portrait, or false otherwise. The
video doesn't necessarily needs to be in a playing state.
qinmin@chromium.org
Android: Records the duration that a fullscreen video is played in portrait
mode. If a video starts playing in portrait mode, and then it is switched
back and forth between landscape and portrait mode, only the time period
before the first switch is accounted. If a video starts playing in landscape
mode, it is not recorded.
qinmin@chromium.org
Android: Records whether a fullscreen video is switched from portrait to
landscape mode at any point during playback.
qinmin@chromium.org
Android: Records whether a video has a larger height than width when it
enters the fullscreen mode.
tedchoc@chromium.org
Android: Count of page loads started by intents from external apps.
jif@chromium.org
mpearson@chromium.org
When a user presses an omnibox suggestion based on the content of the
clipboard, this histograms records how long ago Chrome detected a change in
the clipboard.
Intended to be compared to Omnibox.ClipboardSuggestionShownAge.
If Chrome never detected a change to the clipboard, no clipboard suggestion
is shown, meaning this histogram will never be emitted to.
jlebel@chromium.org
Counts how many times the signin promo is implicitly dismissed (by closing
the bookmark manager) per impression.
jlebel@chromium.org
Counts how many times one of the "sign in" buttons (any of the
signed-out "Sign in to Chrome" button, the "Continue as
|name|" button, or the "Not |email|?" button) is clicked per
impression.
jlebel@chromium.org
Counts how many times the explicit "X"-to-close button is clicked
per impression.
jlebel@chromium.org
Counts how many times the signin promo is implicitly dismissed (by closing
the settings view) per impression.
jlebel@chromium.org
Counts how many times one of the "sign in" buttons (any of the
signed-out "Sign in to Chrome" button, the "Continue as
|name|" button, or the "Not |email|?" button) is clicked per
impression.
jlebel@chromium.org
Counts how many times the explicit "X"-to-close button is clicked
per impression.
tedchoc@chromium.org
For cold starts of Chrome (native not initialized at the time of intent),
record in ChromeTabbedActivity whether the intent had the effect of opening
a new page or was a restore of last session.
charliema@chromium.org
The count of launching Chrome mobile app within a day.
twellington@chromium.org
Android: The time it takes from creating an intent for ChromeActivity to
activity creation. This includes activity creation time spent in the
framework.
charliema@chromium.org
The type of launching Chrome mobile app, e.g launch by hitting icon.
tedchoc@chromium.org
danielpark@chromium.org
twellington@chromium.org
Android: Tracks whether a homepage was loaded on startup of
ChromeTabbedActivity. Launching a homepage is conditional on a homepage
being configured on the device and the absence of any existing tabs, so it
will only happen on a subsets of cold starts. The metric splits out whether
the homepage was the NTP or some other URL.
Deprecated and removed from the code 05/2018
mariakhomenko@chromium.org
Android: Records the first action the user does within 10s of starting
Chrome. Recorded in DocumentActivity and ChromeTabbedActivity only when the
starting intent is of type MAIN.
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.
Deprecated and removed from the code 05/2018
mariakhomenko@chromium.org
Android: Records the first action the user does within 10s of starting
Chrome. Recorded in DocumentActivity and ChromeTabbedActivity only when the
starting intent is not of type MAIN, e.g. VIEW, etc.
Deprecated and removed from the code 05/2018
knn@chromium.org
Android: The time since last use until Chrome is launched from the home
screen. This is measured from the time the last tab is closed until a Main
intent is received. Has a minute level precision for first 10 minutes
increasing exponentially till 30 days.
Note: this metric is broken in M63 and below and only reliable in M64+.
Deprecated and renamed to MobileStartup.ToolbarFirstDrawTime2 due to double
reporting bug (see https://crbug.com/857508).
yusufo@chromium.org
Android: The time it takes from launch to the completion of first draw for
Toolbar. This excludes activity creation time spent in framework.
yusufo@chromium.org
Android: The time it takes from launch to the completion of first draw for
Toolbar. This excludes activity creation time spent in framework.
mheikal@chromium.org
Android: The state of chrome startup at the first time the user focuses the
omnibox, if the user does so within the first 30s of the launch (excluding
activity creation time spent in the framework).
Deprecated and renamed to MobileStartup.ToolbarFirstFocusTime2 due to double
reporting bug (see https://crbug.com/857508).
pasko@chromium.org
Android: The time it takes from launch to the first time the user focuses
the omnibox if the user does so within first 30s of the launch. This
excludes activity creation time spent in framework.
pasko@chromium.org
Android: The time it takes from launch to the first time the user focuses
the omnibox if the user does so within first 30s of the launch. This
excludes activity creation time spent in framework.
pasko@chromium.org
Android: The time spent performing toolbar layout inflation.
pmonette@chromium.org
Records the result of writing the path of the module blacklist cache to the
registry so that chrome_elf.dll can use it. A value is emitted every time
the cache is updated because another instance of Chrome with a different
User Data directory could have overwritten the path to point to their own
version of the cache.
pmonette@chromium.org
The status of a blacklisted module in the process. Recorded when the cache
is updated.
pmonette@chromium.org
The result of deleting the module blacklist cache when third-party module
blocking is disabled. Attempting to delete an empty file is considered a
success.
pmonette@chromium.org
Records whether the MD5 digest of the module blacklist cache matched the one
recorded in the Local State file.
pmonette@chromium.org
Records the number of modules in the module blacklist cache at the time it
was written to disk.
pmonette@chromium.org
The result of reading the current module blacklist cache while updating it.
pmonette@chromium.org
The result of writing the updated module blacklist cache.
anthonyvd@chromium.org
Represents the amount of bytes in a module that are different on disk and in
memory. Logged when the ModuleIntegrityVerifier determines that a module is
different on disk and in memory after being triggered by an incident.
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.
amistry@chromium.org
erikchen@chromium.org
Errors that the broker process encounters while trying to send or receive
Mach ports from a child process.
amistry@chromium.org
erikchen@chromium.org
Errors that a child process encounters while trying to receive Mach ports
from the broker process.
Deprecated 2/2018. Has not actually been collected for some time.
rockot@chromium.org
Measures the time it takes for a new child process to receive an
initialization request from the Mojo shell. This is precisely the duration
of the MojoShellConnectionImpl::BindToMessagePipe() call in ChildThreadImpl.
Deprecated 2/2018. Data no longer useful.
rockot@chromium.org
Measures the time it takes for a child to receive its parent platform handle
synchronously from the broker on startup. This only applies to the subset of
platforms on which the sync broker is used.
Deprecated as of 6/2017.
rockot@chromium.org
Number of internal Mojo system messages processed synchronously during a
single execution of NodeController::AcceptIncomingMessages(). This is called
any time an event requires internal Mojo system messages to be pumped.
Values below 4 are no longer logged.
Deprecated 2/2018. Data no longer useful.
rockot@chromium.org
Number of connected peer nodes tracked by a node. This is emitted any time a
peer is added to or dropped from a node.
Deprecated 2/2018. Data no longer useful.
rockot@chromium.org
Number of connected pending child node connections tracked by a node. This
is emitted any time a parent-child node connection is initiated or dropped.
mek@chromium.org
Methods where leveldb's Mojo environment has IO errors.
mek@chromium.org
Errors (base::File::Error) encountered by a single leveldb method in
leveldb's Mojo environment.
mek@chromium.org
When Mojo LevelDBEnv successfully retries an operation that had failed,
record the error from the most recent failed attempt.
mek@chromium.org
Time Mojo LevelDBEnv slept before successfully completing this operation. 0
means success on the first try, as LevelDBEnv only sleeps when retries are
needed.
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.
lannm@chromium.org
Tracks mouse reverse scroll setting changes by the user.
lannm@chromium.org
Tracks mouse reverse scroll setting on startup.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user mousedown-ed a link and when
the user clicked a link.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
For each click handled by an HTML anchor tag link, whether Blink saw a
mousedown event preceding it. This is only measured for clicks handled by
the anchor tag's default click event handler.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of mousedown events detected at HTML anchor-tag links' default
event handler.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user mouseover-ed a link and when
the user clicked a link.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user mouseover-ed a link and when
the user mouseout-ed a link without click.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of mouseover events detected at HTML anchor-tag links' default
event handler.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The tap gesture events detected before click at HTML anchor-tag links'
default event handler.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Measures the time elapsed between when the user tapdown-ed a link and when
the user clicked a link.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of gesturetapdown events detected at HTML anchor-tag links'
default event handler.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of gesturetapunconfirmed events detected at HTML anchor-tag
links' default event handler.
ppi@chromium.org
The time it takes to spawn the first child subprocess (including sandbox
init).
ppi@chromium.org
The time it takes to spawn child sub processes not counting the first one.
lizeb@chromium.org
Time to call fork() or clone(), in ms. Recorded at each fork excluding from
the zygote, only on posix platforms.
Deprecated 08/2016 due to lack of use (Histogram Eraser).
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.
Deprecated 12/2017 due to lack of usage.
amaralp@chromium.org
The length of time the renderer is unresponsive according to the hang
monitor. Recorded when the renderer regains responsiveness.
renamed MPArch.IIR_InputEventDelta.
Please list the metric's owners. Add more owner tags as needed.
The time spent waiting for the renderer to acknowledge an input event.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time spent inside RenderWidgetHost::OnMsgPaintRect.
fsamuel@chromium.org
piman@chromium.org
The time delta for processing a paint message. On platforms that don't
support asynchronous painting, this is equivalent to
MPArch.RWH_TotalPaintTime.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time spent inside RenderWidgetHost::OnMsgScrollRect.
Deprecated 10/2017. Replaced with MPArch.RWH_OnMsgResizeOrRepaintACK.
Please list the metric's owners. Add more owner tags as needed.
TBD
Please list the metric's owners. Add more owner tags as needed.
TBD
jbauman@chromium.org
Time from tab switch requested to tab appearing on screen (Aura and Mac
only).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time that the user sees a blank white page after switching to a
different tab, while the RenderWidgetHost receives data to paint from the
renderer process.
jordynass@chromium.org
Counts the number of each MultiDevice setup notification clicked by a user.
jordynass@chromium.org
Counts the number of each MultiDevice setup notification shown to a user.
Deprecated 11/2017. Analysis confirms that the number of discards increases
with the number of logged in users. No action will be taken based on this
information.
skuhne@chromium.org
The relation of discarded tabs vs. the amount of simultaneous users. The
counts are the number of discards and the buckets are the number of users.
Since the count values are absolute numbers, they need to be normalized
before use - so divide the counts by the percentage of users per session
found under 'MultiProfile.UsersPerSessionIncremental'.
Deprecated 09/2017 when side-by-side multi-profile mode was removed. There
is now only one multi-profile mode (separate desktop). See the metric
'MultiProfile.UsersPerSessionIncremental' for overall usage of the
multi-profile feature on Chrome OS.
skuhne@chromium.org
The session counter for different multi profile modes which gets stored once
per session at the beginning of the session.
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.
Deprecated 04/2018. Was not being maintained - some cases leading to
teleport were not captured. See counts of 'MultiProfile.TeleportWindowType'
to assess the usage of the teleport window feature.
skuhne@chromium.org
Counts the number of window teleportations when using separated desktop
mode.
skuhne@chromium.org
Counts the number of teleported windows by types in separated desktop mode.
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.
sehr@chromium.org
bradnelson@chromium.org
When the browser started, what happened with the NaCl helper process?
sehr@chromium.org
bradnelson@chromium.org
When a NaCl application process was created, what had happened with the NaCl
helper process when the browser was started?
sehr@chromium.org
bradnelson@chromium.org
The OS/Architecture of a nexe that was loaded.
sehr@chromium.org
bradnelson@chromium.org
The status code returned when trying to load a manifest inside an installed
app.
sehr@chromium.org
bradnelson@chromium.org
The status code returned when trying to load a manifest from a source other
than an installed app.
sehr@chromium.org
bradnelson@chromium.org
The status code returned when trying to load a NaCl executable inside an
installed app.
sehr@chromium.org
bradnelson@chromium.org
The status code returned when trying to load a NaCl executable from a source
other than an installed app.
sehr@chromium.org
bradnelson@chromium.org
The error code returned by NaCl's Chrome plugin.
sehr@chromium.org
bradnelson@chromium.org
The error code returned by NaCl's Chrome plugin, but only for installed
apps.
sehr@chromium.org
bradnelson@chromium.org
The error code returned by NaCl's Chrome plugin, but excluding installed
apps.
sehr@chromium.org
bradnelson@chromium.org
The error code returned by NaCl's sel_ldr.
sehr@chromium.org
bradnelson@chromium.org
The error code returned by NaCl's sel_ldr, but only for installed apps.
sehr@chromium.org
bradnelson@chromium.org
The error code returned by NaCl's sel_ldr, but excluding installed apps.
sehr@chromium.org
bradnelson@chromium.org
Was the manifest specified as a data URI rather than a .nmf file?
Deprecated 6/2011, renamed.
sehr@chromium.org
bradnelson@chromium.org
The time it took to download the manifset file for a Native Client module.
sehr@chromium.org
bradnelson@chromium.org
The time a NaCl module ran before it crashed.
sehr@chromium.org
bradnelson@chromium.org
The time a NaCl module ran without crashing, at shutdown.
Deprecated 6/2011, renamed.
sehr@chromium.org
bradnelson@chromium.org
The time it took to download the main .nexe for a Native Client module.
Deprecated 6/2011, renamed.
sehr@chromium.org
bradnelson@chromium.org
The size of the main .nexe file downloaded for a Native Client module.
Deprecated 6/2011, renamed.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@chromium.org
The optimization level set for the initial Portable Native Client
translation from bitcode to native code.
Deprecated 6/2011, renamed.
sehr@chromium.org
bradnelson@chromium.org
The OS/Architecture of a nexe that was loaded.
sehr@chromium.org
bradnelson@chromium.org
Did the Portable Native Client translation cache find an executable
translated from bitcode?
sehr@chromium.org
bradnelson@chromium.org
The rate for compiling a Portable Native Client bitcode file to an object
file in Kilobytes per second.
sehr@chromium.org
bradnelson@chromium.org
The time it took to compile a Portable Native Client bitcode file to an
object file.
sehr@chromium.org
bradnelson@chromium.org
The time it took to link a Portable Native Client generated object file into
a Native Client executable.
sehr@chromium.org
bradnelson@chromium.org
The time it took to load and validate the Portable Native Client compiler.
sehr@chromium.org
bradnelson@chromium.org
The time it took to load and validate the Portable Native Client linker.
sehr@chromium.org
bradnelson@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).
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@chromium.org
The time it took the NaCl module to shut down.
sehr@chromium.org
bradnelson@chromium.org
The size of the manifest file.
sehr@chromium.org
bradnelson@chromium.org
The size of the main .nexe file downloaded for a Native Client module.
sehr@chromium.org
bradnelson@chromium.org
The size of the main .pexe bitcode file downloaded for a Portable Native
Client module.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@chromium.org
The time it took to load the NaCl module into sel_ldr.
sehr@chromium.org
bradnelson@chromium.org
The time it took to load the NaCl module into sel_ldr. Normalized by the
size of the .nexe, in megabytes.
sehr@chromium.org
bradnelson@chromium.org
The time it took to download the manifset file for a Native Client module.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@chromium.org
The time it took to download the main .nexe for a Native Client module.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@chromium.org
The time it took between the Native Client plugin initialization and when
the NaCl module is ready to be used.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@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.
sehr@chromium.org
bradnelson@chromium.org
Did a validation cache query find a previously known validation result?
sehr@chromium.org
bradnelson@chromium.org
Was the validation cache updated with a new validation result?
jif@chromium.org
The number of times that Chrome detected that a request to download and
install another Google iOS app completed successfully.
zentaro@chromium.org
The number of active mounts that a user has. This is recorded after a share
has been successfully mounted.
zentaro@chromium.org
The result of the mount operation for Native SMB File Share. This is
recorded after the D-Bus call to Mount returns.
zentaro@chromium.org
The number of entries read when calling ReadDirectory. This is recorded
after the D-Bus call to ReadDirectory returns.
zentaro@chromium.org
The duration of ReadDirectory call to SmbProvider in milliseconds. This is
recorded after the D-Bus call returns.
zentaro@chromium.org
The result of the Remount operation during startup. This is recorded after
the D-Bus call to Remount returns.
clamy@chromium.org
The cache flags set on back-forward navigations.
Deprecated 2018-02, replaced by Navigation.IsSameProcess.BackForward.
clamy@chromium.org
Whether the back-forward navigation lead to a change of process or not.
Deprecated 2018-02, replaced by
Navigation.ReadyToCommitUntilCommit.BackForward.
clamy@chromium.org
The time needed to commit a back forward-navigation once it is ready to
commit. This is the time between ReadyToCommit and DidFinishNavigation (for
a navigation that commits).
Deprecated 2018-02, replaced by Navigation.TimeToReadyToCommit.BackForward.
clamy@chromium.org
The time delta between the start of a back-forward navigation and the time
it was ready to commit.
clamy@chromium.org
Whether the back-forward navigation was served from cache.
msramek@chromium.org
Recorded when a navigation is deferred while clearing site data. Indicates
how much time the clearing took.
msramek@chromium.org
The parameters of the Clear-Site-Data header. Recorded when the header is
successfully parsed.
Deprecated 10/2016 in favor of Navigation.DeferredDocumentLoading.StatesV2.
dgrogan@chromium.org
Why and if cross-origin documents would be loaded in a world where we defer
loading until they are visible.
Deprecated 10/2016 in favor of Navigation.DeferredDocumentLoading.StatesV3.
dgrogan@chromium.org
Why and if cross-origin documents would be loaded if we were to defer
loading as long as possible.
Deprecated 3/2017 in favor of Navigation.DeferredDocumentLoading.StatesV4.
dgrogan@chromium.org
Why and if cross-origin documents would be loaded if we were to defer
loading as long as possible. Difference from V2: frames positioned both
above and to the left of the page have their own bucket and are no longer
counted in the "above" bucket.
dgrogan@chromium.org
Why and if cross-origin documents would be loaded if we were to defer
loading as long as possible. Changes from V3: replace detailed reasons with
summaries for four strategies. E.g. any document that would load under a
strategy of loading when a frame is two screens away is logged to the
WouldLoad2Screens AND WouldLoad3Screens bucket. We only record documents
below the current viewport, not to the right of it.
csharrison@chromium.org
yaoxia@chromium.org
When a navigation results in a download, logs the download policy applied to
that navigation.
felt@chromium.org
The amount of time that an HTTP page was in the foreground. Recorded on
every page close/transition.
felt@chromium.org
The amount of time that an HTTPS page was in the foreground. Recorded on
every page close/transition.
felt@chromium.org
The percentage of time that HTTPS pages were in the foreground, as compared
to total foreground time. Recorded whenever user metrics are uploaded.
Deprecated 03/2017 in Issue 703460.
palmer@chromium.org
cbentzel@chromium.org
Whether the navigation was to a URL that had embedded credentials.
csharrison@chromium.org
Records whether the InterceptNavigationThrottle ignored the navigation. This
is recorded at the end of every navigation the throttle observes.
csharrison@chromium.org
The microseconds it takes for the InterceptNavigationThrottle to determine
if the navigation should be ignored, at WillStartRequest time.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
eugenebut@chromium.org
Counts slow/fast back/forward WKWebView navigations on iOS. Fast navigation
is a back/forward navigation done with WKBackForwardList.
Removed from code March 2018.
cjhopman@chromium.org
nyquist@chromium.org
Signifies whether a succesfully finished page load for the main frame
content width fits within the device width and/or has a fixed page scale.
clamy@chromium.org
nasko@chromium.org
Whether the navigation led to a change of process or not.
Deprecated 03/2017 in Issue 703460.
palmer@chromium.org
cbentzel@chromium.org
Whether the main-frame navigation was to a URL that had embedded
credentials.
elawrence@chromium.org
estark@chromium.org
The scheme of the URL for each main-frame navigation.
Removed from code October 2017.
meacer@chromium.org
The mime type of the data: URL for each main-frame navigation. This only
contains mime types that can run scripts.
elawrence@chromium.org
estark@chromium.org
The scheme of the URL for each main-frame navigation that replaces a
document object. This is not reported for reference fragment navigations,
pushState/replaceState or same page history navigation.
elawrence@chromium.org
estark@chromium.org
The scheme of the URL for each main-frame navigation that replaces a
document object while in incognito. This is not reported for reference
fragment navigations, pushState/replaceState or same page history
navigation.
elawrence@chromium.org
estark@chromium.org
The scheme of the URL for each main-frame navigation while in incognito.
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.
clamy@chromium.org
nasko@chromium.org
The time needed to commit a navigation once it is ready to commit. This is
the time between ReadyToCommit and DidFinishNavigation (for a navigation
that commits).
haitaol@chromium.org
donnd@chromium.org
Total length of the redirect URL strings in navigation entry. Logged when
entry is committed.
toyoshim@chromium.org
Reported when a user triggers reload without any other navigations after the
previous reload in the same page, and the previous reload variant was
RELOAD_MAIN_RESOURCE. Duration time between two reloads is reported.
toyoshim@chromium.org
Reported when a user triggers reload without any other navigations after the
previous reload in the same page. Duration time between two reloads is
reported.
arthursonzogni@chromium.org
clamy@chromium.org
nasko@chromium.org
The time needed in the renderer process between receiving the message to
commit the navigation until the navigation has committed.
Obsolete as of 06/2018.
arthursonzogni@chromium.org
clamy@chromium.org
nasko@chromium.org
The time delta between when the ResourceHandler is allowed to read the
response's body and when it has completed its first read.
Obsolete as of 06/2018.
arthursonzogni@chromium.org
clamy@chromium.org
nasko@chromium.org
The time delta between when the ResourceHandler started receiving the
response and when it is allowed to read the response's body.
csharrison@chromium.org
window.location and other scheduled navigation changes can cause the current
provisional load to be aborted. Many times these are initiated without user
gesture. This histogram logs counts of the various aborters.
csharrison@chromium.org
window.location and other scheduled navigation changes can cause the current
provisional load to be aborted. Many times these are initiated without user
gesture. This histogram logs the time between the aborted navigation start
and the scheduled navigation start, if the aborted navigation has a non-zero
navigationStart value.
Deprecated 4/2017 in Issue 712843.
palmer@chromium.org
felt@chromium.org
The scheme of the URL for the first main-frame navigation per origin per
non-OffTheRecord session.
Deprecated 4/2017 in Issue 712843.
palmer@chromium.org
felt@chromium.org
The scheme of the URL for the first main-frame navigation per origin per
OffTheRecord session.
jam@chromium.org
True counts the events when a https URL commits with a SSL certificate.
False is when the certificate is missing. This should be at 100%, anything
less is probably a bug.
Data collected and posted on issue 675833.
csharrison@chromium.org
The difference between Now() in the renderer and browser_navigation_start
for browser-initiated navigations if the difference is negative. This value
should ideally only reflect the IPC time between the browser process and
renderer process, but in practice could be skewed by inter-process timing
errors. If the clocks used for TimeTicks are monotonic across processes, all
samples should fall into the Positive bucket.
Data collected and posted on issue 675833.
csharrison@chromium.org
The difference between Now() in the renderer and browser_navigation_start
for browser-initiated navigations if the difference is positive. This value
should ideally only reflect the IPC time between the browser process and
renderer process, but in practice could be skewed by inter-process timing
errors. If the clocks used for TimeTicks are monotonic across processes, all
samples should fall into the Positive bucket.
csharrison@chromium.org
nasko@chromium.org
The time delta between the start of a navigation and the time it is
committed.
Deprecated March 2018 in favor of Navigation.StartToCommit variants.
carlosk@chromium.org
Time between the start of a browser-started navigation request in and its
commit.
clamy@chromium.org
nasko@chromium.org
The time delta between the start of a navigation and the time it is ready to
commit.
carlosk@chromium.org
Time between the start of a browser-started navigation request and the
reception of a corresponding ResourceRequest in the network stack.
Deprecated 06/2018 in favor of PageLoad metrics.
clamy@chromium.org
Obsolete. Time between receiving an Android Intent and the navigation
commit.
Deprecated 06/2018 in favor of PageLoad metrics.
clamy@chromium.org
Obsolete. Time between clicking on a link and the navigation commit.
Deprecated 06/2018 in favor of PageLoad metrics.
clamy@chromium.org
Obsolete. Time between receiving an Android intent and the document load
complete event for a navigation in the main frame.
Deprecated 06/2018 in favor of PageLoad metrics.
clamy@chromium.org
Obsolete. Time between clicking on a link and the document load complete
event for a navigation in the main frame.
estark@chromium.org
When the navigation URL loader receives an OnComplete message from the
network service that contains certificate chains, this histogram records the
size in KB of those pickled certificate chains. This histogram is recorded
by the navigation URLLoader for navigations that fetch from network, for
every request which contains an SSLInfo in its OnComplete notification.
estark@chromium.org
Whether the network service's OnComplete message to the navigation URL
loader contains an SSLInfo, which should only be present for main-frame
requests with certificate errors. This histogram is recorded for every
request completion by the navigation URL loader that fetches from network.
bmcquade@chromium.org
The connection subtype of the network the client is connected to, when the
client is on a cellular connection. This histogram is logged once per UMA
record, if the user is on a cellular connection, at the time the record is
finalized.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a 2G connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a 3G connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a 4G connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a Bluetooth
connection, before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on an Ethernet
connection, before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen while the
NetworkChangeNotifier thought there was no network connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on an unknown connection
type, before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of the fastest round-trip-time seen on a Wifi connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to a 2G connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to a 3G connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to a 4G connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to a Bluetooth connection and receiving the first
network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to an Ethernet connection and receiving the first
network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between disconnecting and receiving the first network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to an unknown connection type and receiving the first
network data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time between switching to a Wifi connection and receiving the first network
data.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via a 2G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via a 3G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via a 4G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via a Bluetooth connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via an Ethernet connection,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while the NetworkChangeNotifier thought there
was no network connection, before the NetworkChangeNotifier detected a
connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via an unknown connection type,
before the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How much data was transfered while connected via a Wifi connection, before
the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a 2G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a 3G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a 4G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a Bluetooth connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on an Ethernet connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen while the NetworkChangeNotifier
thought there was no network connection, before the NetworkChangeNotifier
detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on an unknown connection type, before
the NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Rough estimate of peak throughput seen on a Wifi connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via a 2G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via a 3G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via a 4G connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via a Bluetooth connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via an Ethernet connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent disconnected, before the NetworkChangeNotifier detected a
connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via an unknown connection type, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
How long was spent connected via a Wifi connection, before the
NetworkChangeNotifier detected a connectivity change.
This metric is recorded when the NetworkChangeNotifier detects a
connectivity change. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
Deprecated 6/2018.
pauljensen@chromium.org
Time from ConnectionTypeChanged message until IPAddressChanged message.
Deprecated 6/2018.
pauljensen@chromium.org
Time between DNS configuration change messages.
Deprecated 05/2017 in Issue 677365.
pauljensen@chromium.org
tbansal@chromium.org
Records the result of querying the network info of the current active
network. Useful for investigating how frequently the current network was
unblocked, and why it was not unblocked. See http://crbug.com/677365.
pauljensen@chromium.org
How long does each call to NetworkChangeNotifier::GetConnectionType() take.
Deprecated 5/2017 for Issue 592131.
pauljensen@chromium.org
True if the first call to ConnectivityManager.getNetworkInfo(Network) did
not throw NullPointerException, false if it did. Useful for investigating
and avoiding unexpected exceptions, see http://crbug.com/592131.
Deprecated 5/2017 for Issue 592131.
pauljensen@chromium.org
Recorded after the first call to ConnectivityManager.getNetworkInfo(Network)
threw a NullPointerException. True if the second call to
ConnectivityManager.getNetworkInfo(Network) did not throw
NullPointerException, false if it did. Useful for investigating and avoiding
unexpected exceptions, see http://crbug.com/592131.
Deprecated 5/2017 for Issue 592131.
pauljensen@chromium.org
True if the first call to WifiManager.getConnectionInfo() did not throw
NullPointerException, false if it did. Useful for investigating and avoiding
unexpected exceptions, see http://crbug.com/592131.
Deprecated 5/2017 for Issue 592131.
pauljensen@chromium.org
Recorded after the first call to WifiManager.getConnectionInfo() threw a
NullPointerException. True if the second call to
ConnectivityManager.getNetworkInfo(Network) did not throw
NullPointerException, false if it did. Useful for investigating and avoiding
unexpected exceptions, see http://crbug.com/592131.
Deprecated 6/2018.
pauljensen@chromium.org
Time between IP address change messages.
Deprecated 6/2018.
pauljensen@chromium.org
Time from IPAddressChanged message until ConnectionTypeChanged message.
Deprecated 6/2018.
pauljensen@chromium.org
Time between going online until we go offline change messages, using new
filtered signal.
Deprecated 6/2018.
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.
Deprecated 6/2018.
pauljensen@chromium.org
Time between going online until we go offline change messages.
Deprecated 6/2018.
pauljensen@chromium.org
Time between when we thought we went offline and when we received some
network data (a URLRequest read completed).
Deprecated 6/2018.
pauljensen@chromium.org
Count of how many times we received network data (a URLRequest read
completed) while offline when some data was received at most five seconds
before going online.
Deprecated 6/2018.
pauljensen@chromium.org
Time between when we received the last network data (a URLRequest read
completed) while offline and when we thought we went online.
Deprecated 6/2018.
pauljensen@chromium.org
Count of how many times we polled the online/offline status before detecting
an offline to online transition.
Deprecated 6/2018.
pauljensen@chromium.org
Time between going offline until we go online change messages.
Deprecated 6/2018.
pauljensen@chromium.org
Time between when we thought we went offline and when we received some
network data (a URLRequest read completed), while polling
NetworkChangeNotifier::GetConnectionType() still told us we were offline.
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.
tbansal@chromium.org
rch@chromium.org
Positive net error codes that failed alternative protocol requests end with.
Recorded only when an alternative job fails, and the main job succeeds.
tbansal@chromium.org
Positive net error codes that failed alternative proxy requests end with.
Recorded when an alternative job fails, whether or not the main job
succeeds.
As of M66 this superceded DataReductionProxy.Quic.OnAlternativeProxyBroken.
rch@chromium.org
The difference between the size of alternative service mappings in cache and
preferences. This tracks zero or negative values (when the difference
between preferences size is less than or equal to memory cache size).
Positive values are tracked by
Net.AlternativeServiceServers.MorePrefsEntries.
rch@chromium.org
The difference between the size of alternative service mappings in
preferences and cache. This tracks positive values (when the difference
between preferences size is greater than memory cache size). Non positive
values are tracked by Net.AlternativeServiceServers.MoreOrEqualCacheEntries.
bnc@chromium.org
Information about the AlternativeService used for each request.
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.
ricea@chromium.org
Counts of error codes received while reading the body of an async
revalidation before getting a response. Only async revalidations that had a
read error are counted.
ricea@chromium.org
Counts of error codes received while performing an async revalidation before
getting a response. Only async revalidations that had in a response error
are counted.
ricea@chromium.org
The result of an async revalidation resulting from application of the
Cache-Control: stale-while-revalidate directive. All async revalidations are
counted.
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.
mmenke@chromium.org
Number of times auto-reload has been attempted before auto-reload stopped
without succeeding, either because the stop button was pressed or because
the renderer was destroyed.
mmenke@chromium.org
Number of times auto-reload had to attempt to reload a page before
succeeding.
mmenke@chromium.org
Original error code that started an auto-reload which then succeeded on the
first attempt.
mmenke@chromium.org
Error code, if any, when auto-reload stopped without succeeding, either
because the stop button was pressed or because the renderer was destroyed.
mmenke@chromium.org
Original error code that started an auto-reload which then eventually
succeeded.
xunjieli@chromium.org
Number of bytes received over this stream.
xunjieli@chromium.org
Number of bytes sent over this stream.
xunjieli@chromium.org
How long it takes from starting the request to reading the end of the
response.
xunjieli@chromium.org
How long it takes from starting the request to reading the start of the
response.
xunjieli@chromium.org
How long it takes from starting the request to when the last byte is sent.
xunjieli@chromium.org
How long it takes from starting the request to when we can start sending
data.
Part of a concluded experiment, 2016-08-02.
ellyjones@chromium.org
Counts of response bytes by cache state.
Part of a concluded experiment, 2016-08-02.
ellyjones@chromium.org
State of the cache for a request, delta-encoding eligible or otherwise.
Part of a concluded experiment, 2016-08-02.
ellyjones@chromium.org
Counts of response bytes by cache state for delta-encoding eligible
requests.
Part of a concluded experiment, 2016-08-02.
ellyjones@chromium.org
State of the cache for a delta-encoding eligible request.
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.
estark@chromium.org
The net error code returned after attempting an AIA fetch on Android.
Recorded once per intermediate that Chrome attempts to fetch via AIA on
Android.
martinkr@google.com
Whether certificate validation was disabled for a set of public keys because
the --ignore-certificate-errors-spki-list switch was set on startup.
martinkr@google.com
Whether certificate validation was disabled because the
--ignore-certificate-errors switch was set on startup.
Deprecated 06/2017 as SHA-1 was successfully disabled in 01/2017.
rsleevi@chromium.org
Whether or not SHA-1 was present in a resource fetched for the main frame,
and if so, what its maximum validity period was.
Deprecated 06/2017 as SHA-1 was successfully disabled in 01/2017.
rsleevi@chromium.org
Whether or not SHA-1 was present in a subresource fetch, and if so, what its
maximum validity period was.
estark@chromium.org
This histogram is recorded every time Chrome successfully verifies a
certificate that chains to a private root. A value of true indicates that
the certificate contains the TLS Feature Extension, and false indicates that
it doesn't.
estark@chromium.org
This histogram is recorded every time Chrome successfully verifies a
certificate that chains to a private root and the certificate contains the
TLS Feature Extension. A value of true indicates that the connection had an
OCSP response stapled, and a value of false indicates that it did not.
rsleevi@chromium.org
The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust
anchor encountered in a successfully-verified certificate chain, during an
HTTP URL request. The associated root certificate can be looked up using
https://crt.sh/?spkisha256= .
rsleevi@chromium.org
The SHA-256 hash of the subjectPublicKeyInfo of the most-specific trust
anchor encountered in a successfully-verified certificate chain, during
verification time. The associated root certificate can be looked up using
https://crt.sh/?spkisha256= .
rsleevi@chromium.org
This histogram is recorded every time Chrome successfully validates a
certificate, but cannot determine a public trust anchor from the verified
chain. A value of true indicates that the trust anchor list is out of date,
as the OS believes a public trust anchor is being used, but the built-in
list does not know about this trust anchor, while a value of false indicates
that a public trust anchor was not used, thus there is no evidence that the
list is out of date. This histogram is temporary until the transition to a
unified root store (in source), at which point, the OS store will no longer
be consulted for known roots.
estark@chromium.org
Whether or not certificate verification was successful after attempting AIA
fetching on Android. Recorded once per certificate verification on Android
that resulted in an untrusted-root error without AIA fetching.
Renamed to Net.PublicKeyPinSuccess 28 Oct 2011.
Please list the metric's owners. Add more owner tags as needed.
A validated certificate chain may be subject to additional
"pinning" requirements on a per-domain basis. This records the
fraction of successful matches between a certificate chain and a pin list.
eranm@chromium.org
Whether an observed Signed Certificate Timestamp (SCT) can be checked for
inclusion. An SCT can be checked for inclusion if the client has a valid
Signed Tree Head (STH) and the STH currently known to the client was issued
24 hours after the timestamp in the SCT (24 hours being the typical Maximum
Merge Delay).
Deprecated Nov 2017, replaced with
Net.CertificateTransparency.ConnectionComplianceStatus2
estark@chromium.org
The compliance of each QUIC connection with the Certificate Transparency
policy, recorded once on connection setup unless CT evaluation has been
disabled for that connection or the certificate is invalid. Connections can
be compliant, or they can be non-compliant for one of several reasons (not
enough Signed Certificate Timestamps [SCTs], not diverse enough SCTs, or the
build was old so CT compliance wasn't checked).
Deprecated Nov 2017, replaced with
Net.CertificateTransparency.ConnectionComplianceStatus2
estark@chromium.org
The compliance of each SSL connection with the Certificate Transparency
policy, recorded once on connection setup unless CT evaluation has been
disabled for that connection or the certificate is invalid. Connections can
be compliant, or they can be non-compliant for one of several reasons (not
enough Signed Certificate Timestamps [SCTs], not diverse enough SCTs, or the
build was old so CT compliance wasn't checked).
estark@chromium.org
The compliance of each connection with the Certificate Transparency policy,
recorded once on connection setup unless CT evaluation has been disabled for
that connection or the certificate is invalid. Connections can be compliant,
or they can be non-compliant for one of several reasons (not enough Signed
Certificate Timestamps [SCTs], not diverse enough SCTs, or the build was old
so CT compliance wasn't checked). Not recorded for certificates that chain
to locally-installed roots.
Deprecated Nov 2017, replaced with
Net.CertificateTransparency.CTRequiredConnectionComplianceStatus2
estark@chromium.org
The compliance of each QUIC connection with the Certificate Transparency
policy, for connections for which CT compliance is required for the
connection to succeed. (For example, CT compliance is required for certain
Certificate Authorities, or a site can opt in to having CT be required.)
Recorded once on connection setup for applicable connections unless CT
evaluation has been disabled for that connection or the certificate is
otherwise invalid.
Deprecated Nov 2017, replaced with
Net.CertificateTransparency.CTRequiredConnectionComplianceStatus2
estark@chromium.org
The compliance of each SSL connection with the Certificate Transparency
policy, for connections for which CT compliance is required for the
connection to succeed. (For example, CT compliance is required for certain
Certificate Authorities, or a site can opt in to having CT be required.)
Recorded once on connection setup for applicable connections unless CT
evaluation has been disabled for that connection or the certificate is
otherwise invalid. Not recorded for certificates that chain to
locally-installed roots.
estark@chromium.org
The compliance of each connection with the Certificate Transparency policy,
for connections for which CT compliance is required for the connection to
succeed. (For example, CT compliance is required for certain Certificate
Authorities, or a site can opt in to having CT be required.) Recorded once
on connection setup for applicable connections unless CT evaluation has been
disabled for that connection or the certificate is otherwise invalid. Not
recorded for certificates that chain to locally-installed roots.
estark@chromium.org
The compliance of each HTTP request with the Certificate Transparency
policy, for requests on connections for which CT compliance is required for
the connection to succeed. (For example, CT compliance is required for
certain Certificate Authorities, or a site can opt in to having CT be
required.) Recorded once on request completion for requests on applicable
connections, unless CT evaluation has been disabled for that connection or
the certificate is otherwise invalid. Not recorded when the request's
certificate chains to a locally-installed root.
robpercival@chromium.org
Counts of specific error codes returned by LogDnsClient at the end of an
attempt to obtain an inclusion proof for a certificate from a Certificate
Transparency log.
robpercival@chromium.org
The time taken attempting to obtain an inclusion proof from a Certificate
Transparency log over DNS. This includes the time taken to obtain the leaf
index first. Emitted at the end of an attempt. Includes attempts that fail.
robpercival@chromium.org
The time taken to successfully obtain an inclusion proof from a Certificate
Transparency log over DNS. This includes the time taken to obtain the leaf
index first. Emitted at the end of an attempt.
robpercival@chromium.org
Counts of specific error codes returned by LogDnsClient at the end of an
attempt to obtain a leaf index for a certificate from a Certificate
Transparency log.
Replaced by Net.CertificateTransparency.DnsQueryError, which provides the
full range of net::Error codes rather than summarising them into the limited
set used by this histogram.
robpercival@chromium.org
The status of each attempt to obtain an inclusion proof from a Certificate
Transparency log over DNS. This can consist of more than one DNS request.
Emitted at the end of an attempt.
Deprecated Nov 2017, replaced with
Net.CertificateTransparency.EVCompliance2.QUIC
estark@chromium.org
The state of compliance with Certificate Transparency presence requirements
for each EV certificate. Recorded once on QUIC connection setup when the
connection uses an EV certificate unless CT evaluation has been disabled for
that connection or the certificate is invalid.
Deprecated Nov 2017, replaced with
Net.CertificateTransparency.EVCompliance2.SSL
estark@chromium.org
The state of compliance with Certificate Transparency presence requirements
for each EV certificate. Recorded once on SSL connection setup when the
connection uses an EV certificate unless CT evaluation has been disabled for
that connection or the certificate is invalid.
estark@chromium.org
The state of compliance with Certificate Transparency presence requirements
for each EV certificate. Recorded once on QUIC connection setup when the
connection uses an EV certificate unless CT evaluation has been disabled for
that connection or the certificate is invalid. Not recorded for certificates
that chain to locally-installed roots.
eranm@chromium.org
The result of an inclusion check for a Certificate Transparency log entry
(composed of a TLS certificate observed together with Signed Certificate
Timestamps). Emitted once per (TLS certificate, Signed Certificate
Timestamp) pair observed and checked for inclusion (check results are
cached).
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
Age of Pilot's Signed Tree Head, as observed by the client, in minutes.
Measuring the age of a particular log's Signed Tree Head will allow more
informed update frequency of the Component Updater component that provides
them. Emitted once for every STH update received by the component updater.
estark@chromium.org
The compliance of each HTTP request with the Certificate Transparency
policy, recorded once on request completion unless CT evaluation has been
disabled for that request's connection or the certificate is otherwise
invalid. A request's connection can be compliant, or it can be non-compliant
for one of several reasons (not enough Signed Certificate Timestamps [SCTs],
not diverse enough SCTs, or the build was old so CT compliance wasn't
checked). Not recorded when the request's certificate chains to a
locally-installed root.
estark@chromium.org
rsleevi@chromium.org
Time to verify a single SCT (Signed Certificate Timestamps) when setting up
a TLS connection. Recorded each time a single SCT is verified. Includes not
just the signature verification but also other operations that are involved
in verifying an SCT, such as notifying observers and looking up the log that
issued the SCT.
estark@chromium.org
rsleevi@chromium.org
Time to verify the SCTs (Signed Certificate Timestamps) when setting up a
TLS connection. Recorded on each connection setup where at least one SCT is
verified.
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.
mattm@chromium.org
If the CertDualVerificationTrial is enabled, each certificate verification
associated with a (non-incognito) profile which is opted-in to SBER2(Scout)
will record the outcome of comparing the primary verifier and secondary
verifier results.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of times we sent N packets, but could have sent N-1 packets.
This experiment has concluded.
Please list the metric's owners. Add more owner tags as needed.
The amount of time taken before we failed to resolve the Comodo test DNS
record. This is an experiment, run in conjuction with Comodo, to test the
viability of a DNS based certificate revocation mechanism.
This experiment has concluded.
Please list the metric's owners. Add more owner tags as needed.
The amount of time taken to successfully resolve the Comodo test DNS record.
This is an experiment, run in conjuction with Comodo, to test the viability
of a DNS based certificate revocation mechanism.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was compressed.
Only includes requests which did not go through an explicit proxy and did
not go over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The compressed number of bytes received per request that was compressed.
Only includes requests which did not go through an explicit proxy and did
not go over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was not
compressed but appears to have been compressible. Only includes requests
which did not go through an explicit proxy and did not go over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was compressed.
Only includes requests sent through a proxy without SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The compressed number of bytes received per request that was compressed.
Only includes requests sent through a proxy without SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was not
compressed but appears to have been compressible. Only includes requests
sent through a proxy without SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was compressed.
Only includes requests sent over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The compressed number of bytes received per request that was compressed.
Only includes requests sent over SSL.
Removed as of 02/2015
Please list the metric's owners. Add more owner tags as needed.
The uncompressed number of bytes received per request that was not
compressed but appears to have been compressible. Only includes requests
sent over SSL.
The count was inaccurate (it counted transactions rather than connections)
Please list the metric's owners. Add more owner tags as needed.
Each bucket is the number of connections of a particular type that the user
has had during the session.
Renamed to match HadConnectionType.
Please list the metric's owners. Add more owner tags as needed.
Each bucket is the number of successful connections of a particular type
that the user has had during the session.
Removed May 2016.
davidben@chromium.org
Each bucket is the number of successful connections of a particular type
that the user has had during the session.
No longer collected.
Please list the metric's owners. Add more owner tags as needed.
Each bucket is the number of failed connections of a particular type that
the user has had during the session.
Replaced with Net.ConnectionUsedSSLDeprecatedCipherFallback2 in Chrome 44.
davidben@chromium.org
True if an HTTPS connection was made using the deprecated cipher suite
fallback.
Removed May 2017.
davidben@chromium.org
For each successful HTTPS request, whether it used the deprecated cipher
suite fallback.
Replaced by Net.ConnectionUsedSSLVersionFallback in Chrome 21.
Please list the metric's owners. Add more owner tags as needed.
True if the HTTP request was to a server which requires SSLv3 fallback
Replaced with Net.ConnectionUsedSSLVersionFallback2 in Chrome 44.
agl@chromium.org
Nonzero if the HTTP request was to a server which requires SSL version
fallback. The value indicates the SSL version the request fell back on.
Removed June 2016.
davidben@chromium.org
For each successful HTTPS request, whether it used the SSL version fallback.
The value indicates the SSL version the request fell back on
Obsoleted in favor of Net.ContentDecodingFailed2.FilterType below.
For each CONTENT_DECODING_FAILED, record the filter that failed.
xunjieli@chromium.org
For each CONTENT_DECODING_FAILED, record the filter that failed.
Obsoleted in favor of Net.ContentDecodingFailed2 above.
xunjieli@chromium.org
For each CONTENT_DECODING_FAILED, record the filter that failed.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Whether or not updates to the backing store succeeded or failed, recorded
every update.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Intervals between access time updates for each cookie.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Number of cookies in the store (recorded every 10 minutes of active browsing
time)
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For each cookie removed from the store, the reason it was removed.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For each domain, number of cookies in that domain (recorded every 10 minutes
of active browsing time).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of subdomains in that top level domain
(recorded every 10 minutes of active browsing time).
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For every top level domain, number of cookies in that domain (recorded every
10 minutes of active browsing time).
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
For each evicted (not expired) cookie, the amount of time since it was last
used
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
Number of minutes until cookie expires when set.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
The amount of time (ms) to get cookies for each URL request.
Initial typo; only here to get results from builds before r59117. See
"Cookie." group.
Please list the metric's owners. Add more owner tags as needed.
The amount of time (ms) to load the persistent cookie store at browser
start.
bnc@chromium.org
rch@chromium.org
The total number of servers (HostPortPairs) to which alternative protocol
was used. This counts the number of servers persisted to prefs file.
bnc@chromium.org
rch@chromium.org
The total number of servers (HostPortPairs in memory) to which alternative
protocol was used.
wangyix@chromium.org
The number of broken alternative services loaded from the prefs file on
startup. Alternative services allow an origin server to specify additional
means of interacting with it on the network. A broken alternative service is
one whose most recent connection attempt failed and whose retry timeout
period has not yet expired. Recorded when broken alternative services are
loaded from the prefs file on startup.
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 servers (HostPortPairs) that support HTTP pipelining.
This counts the number of servers persisted to prefs file.
zhongyi@chromium.org
This counts the number of server configs persisted in prefs file.
wangyix@chromium.org
The number of recently broken alternative services loaded from the prefs
file on startup. Alternative services allow an origin server to specify
additional means of interacting with it on the network. A recently broken
alternative service is one whose most recent connection attempt failed.
Recorded when broken alternative services are loaded from the prefs file on
startup.
bnc@chromium.org
rch@chromium.org
The total number of SPDY server names persisted to prefs file.
Removed on 2016-10-11.
bnc@chromium.org
rch@chromium.org
The total number of SPDY Settings properties persisted to prefs file.
Deprecated 2017-04-21 as it was Linux/CrOS only.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to block to fetch one or
more revocation lists. This measures the amount of time that failures to get
CRL information take.
Deprecated 2017-04-21 as it was Linux/CrOS only.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to block to fetch one or
more revocation lists. This records the fraction of successful requests.
Deprecated 2017-04-21 as it was Linux/CrOS only.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to block to fetch one or
more revocation lists. This measures the amount of time that each fetch
takes.
rch@chromium.org
Measures time spent to deserialize and populate the
net::CachingCertVerifier's cache.
rch@chromium.org
Measures time spent to serialize the net::CachingCertVerifier's cache.
mgersh@chromium.org
Measures time spent creating the Cronet PrefService, including loading the
prefs from disk synchronously.
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.
Deprecated. Moved to
Net.DailyContentLength_DataReductionProxyEnabled_UnknownBypass in M46.
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 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 while the data
reduction proxy was enabled. A negative saving will be shown as zero. This
only counts responses while the data reduction proxy is enabled. The metric
is reported when the first response in the current day is received. If no
video bytes were received while the data reduction proxy was enabled, the
metric will not be reported.
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.
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. If no video bytes were
received via the data reduction proxy, the metric will not be reported.
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 57.
kundaji@chromium.org
bengr@chromium.org
The percentage of data savings in past
|DataReductionProxy::kNumDaysInHistorySummary| days. This number is
displayed to users as their data savings.
Removed in Chrome 57.
kundaji@chromium.org
bengr@chromium.org
The total data saved in KB in past
|DataReductionProxy::kNumDaysInHistorySummary| days. This number is used to
compute the data savings displayed to the user.
Removed in Chrome 64.
yhirano@chromium.org
Duration of time that a request associated with DetachableResourceHandler
takes.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Measures time from initiating a fetch of a PAC file from DHCP WPAD to
cancellation of the fetch. For a given fetch, only one of the cancellation
or completion histograms will be added to.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Measures time from initiating a fetch of a PAC file from DHCP WPAD to
completion of the fetch. For a given fetch, only one of the cancellation or
completion histograms will be added to.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Tracks the net error codes received when the DHCP WPAD fetch fails to
retrieve a PAC file (including PAC_NOT_IN_DHCP, which is not really an error
but an indication that a PAC URL was not configured in DHCP).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Tracks the frequency of each of the different known error codes of calling
the GetAdaptersAddresses Win32 API.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Measures the time taken to call the GetAdaptersAddresses Win32 API, to
validate our understanding that it should complete quickly enough to call
synchronously from the network thread.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Total number of adapters enabled for DHCP as seen when the wait timer in the
DHCP WPAD code hits. This timer fires after a timeout from when we get some
information from the first adapter to finish.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Number of adapters enabled for DHCP that we have not completed retrieving
information for, as seen when the wait timer in the DHCP WPAD code hits.
This timer fires after a timeout from when we get some information from the
first adapter to finish.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
Counts the number of errors from the DhcpRequestParams API that we do not
have specific handling for, so that we can see if there is an abnormally
high rate.
Removed in Chrome 65.
erikchen@chromium.org
The sum of the size of all files in the HTTP cache directory.
This is recorded on startup, and then every 24 hours afterwards. However, it
is only recorded for 0.1% of profiles, to reduce overhead for most users.
This is meant to be a temporary metric to help debug a potential HTTP cache
leak. We do not yet know which milestone we expect it to be removed in.
mgersh@chromium.org
Counts of specific error codes returned by DnsTask. Only counts failures
that took less than 10ms, which are probably local failures.
mgersh@chromium.org
Counts of specific error codes returned by DnsTask. Only counts failures
that took at least 10ms, which are probably remote failures or connectivity
problems.
mgersh@chromium.org
Counts of specific error codes returned by DnsTask if a subsequent ProcTask
succeeded.
mgersh@chromium.org
Duration of time taken by DnsTask in resolutions that failed. Excludes time
spent in the subsequent fallback.
mgersh@chromium.org
Duration of time taken by DnsTask in resolutions that succeeded.
mgersh@chromium.org
Time elapsed between the time the HostResolverImpl::Job was created and the
time the Job was started.
mgersh@chromium.org
Time elapsed between the last time the priority of a HostResolverImpl::Job
changed (when a Request was attached or detached) and the time the Job was
started.
mgersh@chromium.org
Duration of time taken by ProcTask in resolutions that failed.
mgersh@chromium.org
Duration of time taken by ProcTask in resolutions that succeeded.
mgersh@chromium.org
Whether a DNS resolution (single HostResolverImpl::Job) succeeded or failed,
and whether it was speculative.
mgersh@chromium.org
For DNS resolutions that failed after less than 10 ms, which are probably
local failures, what error code the jobs failed with.
mgersh@chromium.org
For DNS resolutions that failed after at least 10 ms, which are probably
remote failures or connectivity problems, what error code the jobs failed
with.
mgersh@chromium.org
Duration of time taken by HostResolverImpl::Job in resolutions that failed.
This is the time to resolve a hostname from start to finish. The main
histogram and by-priority versions exclude speculative requests.
mgersh@chromium.org
Duration of time taken by HostResolverImpl::Job in resolutions that
succeeded. This is the time to resolve a hostname from start to finish. The
main histogram and by-priority versions exclude speculative requests.
mgersh@chromium.org
When DnsUDPAttempt gets a malformed response, it returns an error but
continues running. This histogram records all attempt outcomes that are
returned to the transaction once a malformed response has been received,
including the original malformed response.
mgersh@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests. Includes
cache hits (recorded as 0). Excludes speculative requests.
mgersh@chromium.org
Duration of time since a HostResolverImpl::Resolve request to the time a
result is posted. Excludes canceled, evicted, and aborted requests and
requests that returned synchronously (such as cache hits). Excludes
speculative requests.
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.
mmenke@chromium.org
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.
Deprecated 07/2017, not necessary to determine deprecation for invalid DNS
names.
palmer@chromium.org
True if |net::IsCanonicalizedHostCompliant| returns true. Used to see if
IsCanonicalizedHostCompliant() runs afoul of real websites. This histogram
is recorded when converting dotted DNS names into DNS query form, in
preparation for issuing a DNS request. This histogram is only recorded if
Net.ValidDNSName is true.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The number of HTTP request responses with MS Office Docs MIME types. The
responses are classified based on their method type and cacheability (POST,
cacheable GET and non-cacheable GET). The histogram is used in Double GET
Experiment, where successful non-cacheable GET requests are intercepted
after initial response and repeated in order to determine how much reissuing
non-cacheable GET requests influences their error rate. The histogram tracks
only initial requests (not the repeated ones).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The response codes encountered for GET request repeated in Double GET
Experiment. In the experiment successful non-cacheable GET requests are
intercepted after initial response and repeated. The goal of the experiment
is to measure how much reissuing non-cacheable GET requests influences their
error rate.
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.
Deprecated in favor of Net.ErrAborted.CountPerUpload2 which has a higher
upper bound
csharrison@chromium.org
The count of the ABORTED bucket in Net.ErrorCodesForMainFrame3 at the time
histograms are being uploaded.
csharrison@chromium.org
The count of the ABORTED bucket in Net.ErrorCodesForMainFrame3 at the time
histograms are being uploaded.
csharrison@chromium.org
The bucket proportion of the ABORTED bucket in Net.ErrorCodesForMainFrame3
at the time histograms are being uploaded.
Removed from Chromium as of 2018/7/2.
csharrison@chromium.org
The TotalReceivedBytes() at the time the request finishes with ERR_ABORTED.
Removed from Chromium as of 2018/7/2.
csharrison@chromium.org
The TotalSentBytes() at the time the request finishes with ERR_ABORTED.
Deprecated as of 2012/5/16, replaced by
Net.ErrorCodesForHTTPSGoogleMainFrame2, which measures the same data but
includes ERR_ABORT and OK.
Please list the metric's owners. Add more owner tags as needed.
Errors resulting from loading pages from https://www.google.com. Note that
this only counts the errors in "main frames", so it is a measure
of the error pages that users actually see (it does not for example count
the error codes for subresoures on a page). This is a temporary histogram,
added in order to debug query loss from the SSL Search launch.
Deprecated as of 7/2018, replaced by Net.ErrorCodesForHTTPSGoogleMainFrame3.
mmenke@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" for
https://www.google.com. Subresources or main frame navigations to other
origins are not included.
mmenke@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" for
https://www.google.com (it does not for example count the error codes for
subresoures on a page). It excludes main frame navigations that are
converted to downloads (unless they fail / are aborted before it's known
that they would be a download), and requests handled externally (like mailto
links).
Deprecated as of 7/2018, replaced by Net.ErrorCodesForImages2, which is
recorded in a net-service friendly way.
skonig@chromium.org
hbengali@chromium.org
Net error codes that requests for images end with, including net::OK and
net:ERR_ABORTED.
skonig@chromium.org
hbengali@chromium.org
Net error codes that requests for images end with, including net::OK and
net:ERR_ABORTED.
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).
Deprecated as of 7/2018, replaced by Net.ErrorCodesForMainFrame4, which is
recorded in a net-service friendly way.
mmenke@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" (it
does not for example count the error codes for subresoures on a page).
mmenke@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" (it
does not for example count the error codes for subresoures on a page). It
excludes main frame navigations that are converted to downloads (unless they
fail / are aborted before it's known that they would be a download), and
requests handled externally (like mailto links).
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".
Deprecated as of 7/2018, replaced by Net.ErrorCodesForSubresources3, which
is recorded in a net-service friendly way.
mmenke@chromium.org
Net error codes that requests for "subresources" end with,
including net::OK and net::ERR_ABORTED.
mmenke@chromium.org
Net error codes that requests for "subresources" end with,
including net::OK and net::ERR_ABORTED.
Deprecated as of 7/2018, replaced by
Net.ErrorCodesForTLS13ExperimentMainFrame2, which is recorded in a
net-service friendly way.
svaldez@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" for
endpoints used in the initial TLS 1.3 deployment. Subresources or main frame
navigations to other origins are not included.
svaldez@chromium.org
Positive net error codes that requests for pages end with, including net::OK
and net::ERR_ABORTED. This only counts loads in "main frames" for
endpoints used in the initial TLS 1.3 deployment. Subresources or main frame
navigations to other origins are not included.
Deprecated as of 2015/8/21
mmenke@chromium.org
Temporary histogram to investigate http://crbug.com/500556. Records which
button on the network error page was pushed when either the URL Blink
reports for the page is not the internal error page URL or the
NetErrorHelper core has no error information for the current page (or both).
Deprecated as of 2015/8/21
mmenke@chromium.org
Temporary histogram to investigate http://crbug.com/500556. Records
whether, when the handler for a button press on the network error page runs,
which of the following are or are not true: The URL Blink reports for the
page is not the internal error page URL or the NetErrorHelper core has no
error information for the current page.
mmenke@chromium.org
Counts of various events that can occur on the network error page. Note that
this histogram enum buckets are not mutually exclusive and so a single error
page load might report samples into multiple ones. Each bucket has
descriptions that further explain the context of their samples.
edwardjung@chromium.org
Counts of the type of navigation correction suggestions shown on the network
error page. Multiple suggestions can be shown at the same time.
edwardjung@chromium.org
Usage of navigation correction suggestions shown on the network error page.
Deprecated 10/2016.
mmenke@chromium.org
The number of main frame 4xx/5xx responses that have content, to determine
if it's worth hooking up an error page for those that don't. Intended to be
removed from the binary soon.
Deprecated 10/2016.
mmenke@chromium.org
The number of non-main frame 4xx/5xx responses that have content, to
determine if it's worth hooking up an error page for those that don't.
Intended to be removed from the binary soon.
estark@chromium.org
Sites can send an Expect-CT header to Chrome to indicate that they intend
their sites to comply with Chrome's Certificate Transparency policy. This
histogram is recorded whenever an Expect-CT header is processed on a
connection. True indicates that the header parsed successfully, and false
indicates that there was a parse failure.
estark@chromium.org
Sites can send an Expect-CT header to Chrome to indicate that they intend
their sites to comply with Chrome's Certificate Transparency policy. This
histogram is recorded on connection setup, whenever Chrome connects to an
Expect-CT site using a publicly trusted root. The histogram records the CT
policy compliance status of the connection.
estark@chromium.org
Sites can send an Expect-CT header to Chrome to indicate that they intend
their sites to comply with Chrome's Certificate Transparency policy. This
histogram is recorded whenever an Expect-CT header is successfully parsed on
a connection that chains to a publicly trusted root. The histogram records
the CT policy compliance status of the connection on which the header was
received.
Deprecated 04/2017.
estark@chromium.org
Sites can send an Expect-CT header to Chrome to indicate that they want a
report to be sent when the connection does not comply with Certificate
Transparency policy. This histogram is recorded whenever Chrome receives an
Expect-CT header, and it records the result of processing the header, such
as whether it was ignored due to a bad value.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Flush failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file GetSize failed with. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Open failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Read failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Seek failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file SetEof failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code that a file Write failed with. The code is OS dependent,
so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Flush failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Flush. The code is
OS dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file GetSize failed with. Any value other
than 0 indicates that we have received errors in a range outside of the one
in which we recorded the specific errors in Net.FileError_GetSize. The code
is OS dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Open failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Open. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Read failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Read. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Seek failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Seek. The code is OS
dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file SetEof failed with. Any value other
than 0 indicates that we have received errors in a range outside of the one
in which we recorded the specific errors in Net.FileError_SetEof. The code
is OS dependent, so when looking at the histogram don't mix OSes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
System error code range that a file Write failed with. Any value other than
0 indicates that we have received errors in a range outside of the one in
which we recorded the specific errors in Net.FileError_Write. The code is
OS dependent, so when looking at the histogram don't mix OSes.
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.
Removed June 2016.
davidben@chromium.org
Records a sample for each HTTPS request to a Google server that either
succeeded or received an inappropriate_fallback alert. This is used to
estimate how frequently the fallback is used to recover from a spurious
network failure.
Replaced with Net.GoogleConnectionUsedSSLVersionFallback2 in Chrome 44.
agl@chromium.org
Nonzero if the HTTP request was to a Google server which required SSL
version fallback. The value indicates the SSL version the request fell back
on. Since Google servers support TLS 1.2, any fallback is an indication of
network middleware problems.
Removed June 2016.
davidben@chromium.org
For each successful HTTPS request to a Google server, whether it used the
SSL version fallback. The value indicates the SSL version the request fell
back on. Since Google servers support TLS 1.2 and FALLBACK_SCSV, any
fallback is an indication of a broken local SSL MITM proxy.
Removed around 2015/03/18. The code which implemented Gzip encoding fixup
was removed.
asanka@chromium.org
Resources are sometimes transferred with an incorrect encoding type of gzip.
net::Filter::FixupEncodingTypes() attempts to correct for these situations
by applying a set of heuristics. This histogram counts the frequency of
usage of these heuristics in the wild.
The count was inaccurate (it counted transactions rather than connections).
Please list the metric's owners. Add more owner tags as needed.
Each bucket is a boolean (0 or 1) indicating whether the user has had a
connection of that type during the session.
This statistic measures successful and failed connections, the new one only
measures successful ones.
Please list the metric's owners. Add more owner tags as needed.
Each bucket is a boolean (0 or 1) indicating whether the user has had a
connection of that type during the session.
Removed May 2016.
davidben@chromium.org
Each bucket is a boolean (0 or 1) indicating whether the user has had a
successful connection of that type during the session.
Replaced by Net.HadFtpServerType2 on 2012-11-13.
phajdan.jr@chromium.org
Each bucket is the number of sessions that encountered a given FTP server
type. Each session reports a given server type at most once.
phajdan.jr@chromium.org
Each bucket is the number of sessions that encountered a given FTP server
type. Each session reports a given server type at most once.
davidben@chromium.org
Records, on startup, for ARM devices running Android, whether the CPU is
known to have a broken NEON unit. See https://crbug.com/341598.
Removed in 2017 March.
bnc@chromium.org
Format of :status header value in HTTP/2 response.
Removed 2017-02.
davidben@chromium.org
The SSL/TLS cipher suite that was negotiated, recorded for each successful
HTTP/2 connection.
asanka@chromium.org
Whether adding an entry to the HTTP auth cache evicted another entry.
asanka@chromium.org
When an HTTP auth cache entry is evicted, the time since it was created.
asanka@chromium.org
When an HTTP auth cache entry is evicted, the time since it was last used.
asanka@chromium.org
Whether adding a path to an entry in the HTTP auth cache evicted another
path.
asanka@chromium.org
When looking up an HTTP auth cache entry by path, the position (1-indexed)
of the entry on a hit, or 0 on a miss.
asanka@chromium.org
When looking up an HTTP auth cache entry by realm, the position (1-indexed)
of the entry on a hit, or 0 on a miss.
asanka@chromium.org
cbentzel@chromium.org
Per-authentication-scheme counts of authentication attempts and rejections.
meacer@chromium.org
Type of the HTTP auth prompt displayed.
Removed in https://crrev.com/209100
Please list the metric's owners. Add more owner tags as needed.
Count of authentication requests for top level pages vs. sub-resources, such
as images or iframes.
asanka@chromium.org
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.
Replaced by Net.HttpContentLengthV2
bengr@chromium.org
Size of the response body. This is the actual number of bytes received,
which usually agrees with but is not necessarily the same as the size
specified by the Content-Length header.
Deprecated 04/2018.
bengr@chromium.org
Size of the response body if it is cacheable. This is the actual number of
bytes received, which usually agrees with but is not necessarily the same as
the size specified by the Content-Length header.
Deprecated 04/2018.
bengr@chromium.org
Size of the response body if it is cacheable for at least 24 hours. This is
the actual number of bytes received, which usually agrees with but is not
necessarily the same as the size specified by the Content-Length header.
Deprecated 04/2018.
bengr@chromium.org
Size of the response body if it is cacheable for at least 4 hours. This is
the actual number of bytes received, which usually agrees with but is not
necessarily the same as the size specified by the Content-Length header.
Deprecated 06/2018.
bengr@chromium.org
The difference between the size specified in the X-Original-Content-Length
header and the size of the response body. This is zero if the
X-Original-Content-Length header is not present in the response.
bengr@chromium.org
The difference between the size specified in the X-Original-Content-Length
header and the size of the response body. Only includes resources that have
the X-Original-Content-Length header.
bengr@chromium.org
Size of the response body. This is the actual number of bytes received,
which usually agrees with but is not necessarily the same as the size
specified by the Content-Length header. Replaces Net.HttpContentLength,
recording non-DRP Http traffic as "Http.Direct" instead of
"Http.Other".
Deprecated 04/2018.
bengr@chromium.org
Size of the response body. Only includes resources that have the
X-Original-Content-Length header.
Deprecated as of 12/2016.
mmenke@chromium.org
Records the frequency with which a number of hacky HTTP header parsing rules
are invoked. This histogram should be removed after we have enough data to
know if we can remove the hacks.
tsepez@chromium.org
Count of requests which contained a basic auth username and password
embedded in the URL itself.
jkarlin@chromium.org
Total prefilter (e.g., before decompression) bytes read for an HttpJob
request.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading, for jobs served from the cache.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until
the job is killed. Note that we didn't detect the end of the data for this
job.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading, for jobs not served from the cache.
mmenke@chromium.org
Time it takes to complete an HttpJob, from starting the transaction until we
are done reading, for jobs when we read until no more data is available.
Replaced by Net.HttpOriginalContentLengthV2.
bengr@chromium.org
Size specified in the X-Original-Content-Length header. If this header is
not present in the response, the size of the response body is used.
bengr@chromium.org
Net.HttpOriginalContentLength with non-data reduction proxy traffic properly
labeled with the "Direct" suffix.
Size specified in the X-Original-Content-Length header. If this header is
not present in the response, the size of the response body is used. Replaces
Net.HttpOriginalContentLength, breaking down traffic by Direct, ViaDRP,
Bypassed, and Other.
bengr@chromium.org
Size specified in the X-Original-Content-Length header. Only includes
resources that have the X-Original-Content-Length header.
tbansal@chromium.org
Time taken to establish the connection to the HTTP proxy.
Deprecated as of 10/2016.
mmenke@chromium.org
Time it takes to request a new (unused) HTTP proxy socket.
Deprecated 06/2016 because this is not continuously tracked.
hiroshige@chromium.org
Whether a request contains invalid request header values in RFC 7230. This
is counted once for every redirect leg. https://crbug.com/455099.
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.
Deprecated 06/2016 because this is not continuously tracked.
hiroshige@chromium.org
Whether a response contains invalid response header values in RFC 7230. This
is counted once for every redirect leg. https://crbug.com/455099.
mmenke@chromium.org
The count of HTTP Response codes encountered.
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.
Deprecated as of 06/2016.
bnc@chromium.org
Application protocol used in HTTP response. Recorded every time a
URLRequest completes.
Deprecated as of July 2018.
mmenke@chromium.org
Application protocol used in HTTP responses to requests for main frames.
Only includes requests that went over the network.
Deprecated as of July 2018.
mmenke@chromium.org
Application protocol used in HTTP responses to requests for resources other
than main frames. Does not include internal Chrome requests. Only includes
requests that went over the network.
rch@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].
Deprecated as of 12/2016.
ellyjones@chromium.org
Records how often violations of RFC 7230's header parsing rules are
observed.
Deprecated as of 1/2018.
xunjieli@chromium.org
Reports the next state that the Alternative Job is in.
Deprecated as of 1/2018.
xunjieli@chromium.org
Reports the state that the Alternative Job is in.
Deprecated as of 1/2018.
xunjieli@chromium.org
Reports the next state that the Main Job is in.
Deprecated as of 1/2018.
xunjieli@chromium.org
Reports the state that the Main Job is in.
Deprecated 08/2017. No longer tracked.
zhongyi@chromium.org
Time it takes for OnStreamReadyCallback to be called.
mmenke@chromium.org
Time from when an HTTP request is issued to when the first byte is
processed.
mmenke@chromium.org
Time from when an HTTP request is issued to when the first byte is
processed, for requests with an upload that is > 1 MiB. Excludes chunked
uploads.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The count of handleable socket errors (connection abort/close/reset) per
socket reuse type.
Late bindings are on by default now.
Please list the metric's owners. Add more owner tags as needed.
The count of handleable socket errors (connection abort/close/reset) per
socket reuse type. Socket late binding is disabled.
Late bindings are on by default now.
Please list the metric's owners. Add more owner tags as needed.
The count of handleable socket errors (connection abort/close/reset) per
socket reuse type. Socket late binding is enabled.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The probe results when a test for IPv6 support is done.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The probe results when a test for IPv6 support is done, after a network
change event.
Deprecated 01/2018.
zhongyi@chromium.org
This counts number of all the job controllers that are still alive if the
count is a multiple of 100: 100, 200, 300, etc.
Deprecated 01/2018.
zhongyi@chromium.org
This counts number of JobControllers that are still alive, not created for
preconnect, and still have a HttpStreamFactoryImpl::Request pending.
Deprecated 01/2018.
zhongyi@chromium.org
This counts number of job controllers that are still alive, not created for
preconnect but HttpStreamFactoryImpl::Request has completed.
Deprecated 01/2018.
zhongyi@chromium.org
This counts number of job controllers which are used for preconnect and are
still alive.
Deprecated 01/2018.
zhongyi@chromium.org
This counts number of all the job controllers that are still alive.
Deprecated 08/2017.
zhongyi@chromium.org
This counts number of alternative jobs which are still alive.
Deprecated 08/2017.
zhongyi@chromium.org
This counts number of main jobs which are still alive.
Deprecated 04/2017, replaced by
Net.JobController.CountOfJobController.NonPreconnect.PendingRequest.
zhongyi@chromium.org
This counts number of HttpStreamFactoryImpl::Request which are still alive.
Deprecated 04/2017, replaced by
Net.JobController.CountOfJobController.Preconnect.
zhongyi@chromium.org
This counts number of job controllers which are used for preconnect and are
still alive.
Deprecated 02/2018, replaced by
Net.KeepaliveStatisticsRecorder.PeakInflightRequests2
yhirano@chromium.org
The peak number of concurrent outstanding requests with keepalive specified.
yhirano@chromium.org
The peak number of concurrent outstanding requests with keepalive specified.
This histogram is reported whenever the peak number is updated. For example,
if the inflight number of requests were 0 => 1 => 2 => 1 => 2
=> 3 => 2, then 0, 1, 2, and 3 would be reported.
yhirano@chromium.org
The peak number of concurrent outstanding requests with keepalive specified
per render process.
yhirano@chromium.org
The peak number of concurrent outstanding requests with keepalive specified
per render process. This histogram is reported whenever the peak number is
updated. For example, if the inflight number of requests were 0 => 1
=> 2 => 1 => 2 => 3 => 2, then 0, 1, 2, and 3 would be
reported.
Deprecated July 2018
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
The completion status of prefetches that have finished loading.
Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled
before that point are not registered.
This applies to requests with net::LOAD_PREFETCH, used by various
prefetching features such as no-state prefetch and RESOURCE_TYPE_PREFETCH.
Note that "success from cache" means that the
UrlRequest::was_cached() was true and unused_since_prefetch was false.
"success from network" means that was_cached() was false.
"success already prefetched" means that both was_cached() and
unused_since_prefetch were true. Validated results are considered cached,
even though a conditional network request is made.
jkarlin@chromium.org
The distribution of storable vs "cache-control: no-store"
main-frame resources.
Counted after response headers have completed and before the content has
completed. Redirects are counted. All HTTP cache transactions are counted,
not just those that require the network.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The time that a (non-cancelled) proxy resolution request was stalled waiting
for an execution thread, for MultiThreadedProxyResolver.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that it took for a (non-cancelled) proxy resolution request
to complete, for MultiThreadedProxyResolver.
davidben@chromium.org
Records, on startup, for ARM devices running Android, whether the kernel is
missing AT_HWCAP2 from the ELF auxv and /proc/cpuinfo reports support for
ARMv8 features. Those features should also be reported in AT_HWCAP2. This is
to measure the workaround in https://crbug.com/boringssl/46.
Removed in Chrome 44.
eroman@chromium.org
Counts the number of browser launches where chrome://net-internals and
chrome://net-internals/#tests are used.
xunjieli@chromium.org
This is logged when SCDynamicStoreCreate fails in
network_config_watcher_mac.cc.
xunjieli@chromium.org
This is logged when SCDynamicStoreCreateRunLoopSource fails in
network_config_watcher_mac.cc.
xunjieli@chromium.org
This is logged when retrying SCDynamicStore has stopped after either
receiving a success or hitting the maximum number of retries in
network_config_watcher_mac.cc. The 0 bucket is where no retry is performed,
and the maximal bucket is where all retries have failed.
juliatuttle@chromium.org
When Network Error Logging receives a "NEL:" header, what happens
to it.
juliatuttle@chromium.org
When Network Error Logging observes a completed request that might generate
a report, what happens to it. NEL observes all requests, since it can send
reports for a fraction of successful requests as well so error rates can be
calculated.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download the main frame of a page in
response to specific HTTP network errors succeeds.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download a subresource in response to
specific HTTP network errors succeeds.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download the main frame of a page in
response to specific HTTP network errors returns another network error.
Histogram includes only the error code that triggered the retry.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
How often automatically retrying to download a subresource in response to
specific HTTP network errors returns another network error. Histogram
includes only the error code that triggered the retry.
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
Deprecated 2015-08-17 as part of cookie histogram cleanup
(https://crbug.com/521135).
Please list the metric's owners. Add more owner tags as needed.
The number of duplicate cookies that were present in the cookie store during
startup.
rch@chromium.org
The number of QUIC sessions when the QuicStreamFactory is destroyed.
Deprecated 2017-04-21 as it was Linux/CrOS only.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to make one or more HTTP
fetches to OCSP responders in order to get revocation information. This
measures the amount of time that failures to get OCSP information take.
Deprecated 2017-04-21 as it was Linux/CrOS only.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to make one or more HTTP
fetches to OCSP responders in order to get revocation information. This
records the fraction of successful requests.
Deprecated 2017-04-21 as it was Linux/CrOS only.
rsleevi@chromium.org
When validating an HTTPS certificate we may have to make one or more HTTP
fetches to OCSP responders in order to get revocation information. This
measures the amount of time that each of those requests takes.
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.
mgersh@chromium.org
Positive error code that was returned by the system library
"getaddrinfo()". This error code is platform specific, so when
there is a Windows/Linux conflict, both decodings are shown.
mgersh@chromium.org
Positive error code that was returned by the system library
"getaddrinfo()".
mgersh@chromium.org
Positive error code that was returned by the system library
"getaddrinfo()".
mgersh@chromium.org
Positive error code that was returned by the system library
"getaddrinfo()".
Deprecated 4/27/2016. No longer tracked.
eroman@chromium.org
Proxy Auto Config (PAC) allows specifying an arbitrary javascript program to
pick network proxies on a per-request basis (based on the URL). This works
by calling the script's FindProxyForURL() function with the target URL as
its first argument.
Traditionally, the URL parameter passed into the script contains the exact
URL being loaded, except maybe for having stripped the fragment and embedded
identity portions of the URL.
This histogram records what happens when the URL passed into
FindProxyForURL() additionally has had its path component stripped. Does it
return the same proxy list as when calling FindProxyForURL() with the
original (unmodified) URL?
This comparison is done only when the URL scheme implies a secure channel
(i.e. https:// and wss://), in order to gather data for crbug.com/593759.
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.
No longer tracked.
csharrison@chromium.org
Indicate whether a link navigation was preceded by a recent pre-connect
trigger (within 10 seconds). There is a high chance that loading the page
used a preconnected TCP session.
No longer tracked.
csharrison@chromium.org
Indicate whether a URLRequest was preceded by a recent pre-connect trigger
(within 10 seconds). There is a high chance that loading the resource used a
preconnected TCP session.
Deprecated May 2018
csharrison@chromium.org
When a preconnection is made, indicate what the motivation was.
Currently, the most common (only?) motivations are SELF_REFERAL,
LEARNED_REFERAL and OMNIBOX. The SELF_REFERAL indicates that we made sure a
second connection was available for a resource that either was never before
seen, or has historically had no subresources. The LEARNED_REFERAL
indicates that we "learned" that a subresource was commonly
needed, and that motivated the TCP/IP preconnect. The OMNIBOX motivation
happens when a search is being suggested, and we preconnect to the search
provider. (WARNING: Prior to version 7.517.*, enums 7, 8, and 9 may be
confused, as EARLY_LOAD_MOTIVATED was inserted new 6 value.)
No longer tracked.
csharrison@chromium.org
Indicate whether there was a proxy to preclude preconnection.
tbansal@chromium.org
Indicates number of times a preconnect to proxy server was skipped due to an
existing pending preconnection request.
Deprecated May 2018
csharrison@chromium.org
What did we decide to do about a predicted resource, based on the historical
expected number of connection that this subresource will require.
This is basically the current thresholding of the SubresourceExpectation,
relative to current static thresholds, and taking into account whether
preconnection is enabled (i.e., if preconnection is disabled, we'll never
decide to preconnect).
Deprecated May 2018
csharrison@chromium.org
The expected number of connections, times 100, that we'll make to a given
subresource, based on learned history.
By comparing this to thresholds, we decide if we will preconnect,
preresolve, or do nothing. This histogram can be used to select those static
thresholds.
No longer tracked.
csharrison@chromium.org
Indicate whether if a preconnect trigger is followed by a resource request
(from link navigations) to the host or not. This is to measure precision of
link-based preconnect triggers.
Sourced data corrected, and replaced by NetPreconnectUtilization2
Please list the metric's owners. Add more owner tags as needed.
Indicate final utilization for each attempted socket connection.
We also include stats for non-speculative sockets. Some socket connections
may never connect, and others may never be used (as the user may abort
before then).
Deprecated in M68 (May 2018)
csharrison@chromium.org
Indicate final utilization for each attempted socket connection.
We also include stats for non-speculative sockets. Some socket connections
may never connect, and others may never be used (as the user may abort
before then).
Dev data was collected which was good enough to make a decision on the size
of the predictor database.
csharrison@chromium.org
The index into the predictor's MRU on navigation. This is the size the MRU
had to be in order to effectively predict subresources for this navigation.
Deprecated May 2018
csharrison@chromium.org
The approximate size in bytes of the predictor's database on startup.
jkarlin@chromium.org
Bytes read for requests that were served from a cache entry whose
unused_since_prefetch bit is true.
Deprecated July 2018
jkarlin@chromium.org
The completion status of prefetches that have finished loading.
Measurement occurs at ResourceLoader::ResponseCompleted so requests canceled
before that point are not registered.
This applies to requests with RESOURCE_TYPE_PREFETCH.
Note that "success from cache" means that the
UrlRequest::was_cached() was true and unused_since_prefetch was false.
"success from network" means that was_cached() was false.
"success already prefetched" means that both was_cached() and
unused_since_prefetch were true. Validated results are considered cached,
even though a conditional network request is made.
jkarlin@chromium.org
Number of bytes read from the network on behalf of prefetch requests. This
is prefilter, so before any decompression.
This applies to requests with RESOURCE_TYPE_PREFETCH.
Deprecated July 2018
jkarlin@chromium.org
Time spent on prefetch requests before the request was canceled.
This applies to requests with RESOURCE_TYPE_PREFETCH.
Deprecated July 2018
jkarlin@chromium.org
Time spent on requests that were served from a cache entry whose
unused_since_prefetch bit is true.
Deprecated July 2018
jkarlin@chromium.org
Time spent on prefetch requests when fetched from cache.
This applies to requests with RESOURCE_TYPE_PREFETCH.
Deprecated July 2018
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.
eroman@chromium.org
The breakdown of URL schemes seen for explicitly configured ProxyAutoConfig
(PAC). This metric is emitted once each time the proxy settings change
(including initial value). Note that this does not count implicitly inferred
PAC URLs (from WPAD).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent executing the proxy script during
"tracing" runs (executions of the script which discovered a new
DNS dependency and were subsequently abandoned).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent executing the proxy script during
"tracing" runs (executions of the script which discovered a new
DNS dependency and were subsequently abandoned).
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent in the non-blocking DNS bindings
while executing PAC scripts. This includes the times for abandoned
executions.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The amount of time inside of V8 that the proxy script spent executing for
the final pass. This includes the time spent in the javascript bindings.
This does not include the time spent in abandoned execution passes.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that alert() was called in the final execution of the
script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of errors that were seen in the final execution of the script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that the PAC script execution was restarted.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that the proxy resolution took. This includes all the time
spent waiting for DNS, PAC script execution, and restarts.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that proxy resolution spent waiting for DNS. This also
includes any queuing delays on the origin thread waiting for the DNS result
to be processed.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of unique DNS hostnames that the PAC script tried to resolve. The
*Ex() versions of the bindings count separately.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total amount of time that was spent in the non-blocking DNS bindings
while executing PAC scripts. This includes the times for abandoned
executions.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The amount of time inside of V8 that the proxy script spent executing for
the final pass. This includes the time spent in the javascript bindings
(which is probably dominated by Net.ProxyResolver.DnsWaitTotalTime). This
does not include the time spent in abandoned execution passes.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that alert() was called in the final execution of the
script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of errors that were seen in the final execution of the script.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of times that the PAC script execution was restarted.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The amount of time it took upon completion to run the final task posted back
to the IO thread.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that the proxy resolution took. This includes all the time
spent waiting for DNS, PAC script execution, and restarts.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that proxy resolution spent waiting for DNS. This also
includes any queuing delays on the origin thread waiting for the DNS result
to be processed.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The total time that the proxy resolution took, not including the post back
to the origin thread. This includes all the time spent waiting for DNS, PAC
script execution, and restarts.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The number of unique DNS hostnames that the PAC script tried to resolve. The
*Ex() versions of the bindings count separately.
Removed in Chrome 39.
Please list the metric's owners. Add more owner tags as needed.
The length of the URL that was passed into the PAC script.
cbentzel@chromium.org
The time taken from requesting a PAC script to receiving the first byte of
the response body on successful fetches. This does not include time spent
doing proxy auto-discovery, or failed attempts at retrieving PAC scripts.
If the response body was empty, this measures the total time to fetch the
(empty) response body.
cbentzel@chromium.org
The time taken to successfully fetch a PAC script. This does not include
time spent doing proxy auto-discovery, or failed attempts at retrieving PAC
scripts.
Deprecated as of Chrome 61.
eroman@chromium.org
The network error code of resolving a URL by forwarding the request to the
proxy resolver and executing the PAC script.
Deprecated as of Chrome 61.
eroman@chromium.org
The time taken to resolve a URL by forwarding the request to the proxy
resolver and executing the PAC script. This includes PAC script execution,
DNS queries, and internal retries. This does not include retries initiated
by the user, such as by calling ProxyService::ReconsiderProxyAfterError().
Deprecated as of Chrome 61.
eroman@chromium.org
Whether proxy resolution occured by forwarding the request to the proxy
resolver and executing the PAC script. This histogram records all URLs,
regardless of whether a proxy configuration is set. Note that in some cases,
the system proxy resolver is used. If so, this histogram indicates whether
the request was forwarded to the system resolver. However, on desktop
platforms, the number of users using the system resolver should be small
since the default is to use V8. Hence, the count of emissions to the 'True'
bucket on desktop caused by users of the system resolver should be small.
Deprecated as of Chrome 61.
eroman@chromium.org
The total time taken to resolve a URL. This includes PAC script execution,
DNS queries, and internal retries. This does not include retries initiated
by the user, such as by calling ProxyService::ReconsiderProxyAfterError().
Deprecated as of Chrome 61.
eroman@chromium.org
Whether a proxy resolution resulted in the PAC script terminating
unexpectedly. This does not include terminations that occured during
initialization of a new proxy resolver. This only happens when the resolver
process crashes when using out-of-process PAC.
Deprecated as of Chrome 61.
eroman@chromium.org
Whether the creation of a new proxy resolver resulted in the PAC script
terminating unexpectedly. This only happens when the resolver process
crashes when using out-of-process PAC.
Deprecated as of November 2016 because of disuse. Historical data is likely
inaccurate due to changes in the data structure that calculated domain IDs
for this histogram.
agl@chromium.org
Second-level domains for which we have observed public key pinning failures.
Deprecated as of 07/2016. Replaced with
Net.PublicKeyPinReportSendingFailure2.
estark@chromium.org
A validated certificate chain may be subject to additional pinning
requirements on a per-domain basis. When pinning requirements are violated,
Chrome attempts to send a report about the incident. This records the net
error code when sending a pinning violation report fails.
estark@chromium.org
A validated certificate chain may be subject to additional pinning
requirements on a per-domain basis. When pinning requirements are violated,
Chrome attempts to send a report about the incident. This records the net
error code when sending a pinning violation report fails.
agl@chromium.org
A validated certificate chain may be subject to additional
"pinning" requirements on a per-domain basis. This records the
fraction of successful matches between a certificate chain and a pin list.
Deprecated 11/2017.
bnc@chromium.org
Records whether HTTP/2 response headers have already arrived on a pushed
stream at the time the stream is matched up with a request. See
https://crbug.com/554220.
bnc@chromium.org
Information about the value of the Vary response header in HTTP/2 pushed
streams.
rch@chromium.org
The number of active QUIC sessions before we activate a new QUIC session.
tbansal@chromium.org
Breakdown of how requests which could potentially make use of an alternative
QUIC proxy server use or don't use the QUIC server.
wangyix@chromium.org
Tracks the number of QUIC alt-svc advertisements parsed by Chrome in Google
format vs in IETF format.
rch@chromium.org
The reject reasons for QUIC's CHLO (client hello) message from server
Deprecated 08/2014, and replaced by
Net.QuicClientHelloServerConfig.InvalidDuration.
rch@chromium.org
How expired server config is for sending inchoate ClientHello to the server.
rch@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.
rch@chromium.org
The reason (the state of the server config) for sending inchoate ClientHello
to the server.
Deprecated 02/2018. No data for this histogram for more than 30 days.
rch@chromium.org
The number of times Connection's visitor is a nullptr when CloseConnection
is called.
wub@chromium.org
The write result returned by the packet writer when the connection attempts
to write a packet.
rch@chromium.org
The number of times CryptoClientConfig's CachedState is populated from
canonical config whenever we create a new CryptoClientConfig::CachedState.
Deprecated as of 4/15/2017.
rch@chromium.org
Tracks number of times data read/parse/write API calls of QuicServerInfo to
and from disk cache is called.
Deprecated as of 10/2014.
rch@chromium.org
Tracks the opening and closing of disk cache entries. Recorded each time a
disk cache entry is either opened or closed.
rch@chromium.org
Tracks failure reasons to read/load/write of QuicServerInfo to and from disk
cache.
Deprecated as of 04/2016.
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.
ckrasic@chromium.org
The compression percentage, logged for each sent HPACK compressed header
frame.
ckrasic@chromium.org
For each indexed representation decoded, records the time since the
corresponding entry was added to the dynamic table. This data is being
collected to help analyze a proposed solution to HPACK induced head of line
blocking.
ckrasic@chromium.org
The decompression percentage, logged for each received HPACK compressed
header frame.
ckrasic@chromium.org
For each indexed representation encoded, records the time since the
corresponding entry was added to the dynamic table. This data is being
collected to help analyze a proposed solution to HPACK induced head of line
blocking.
Deprecated 2016. No longer tracked.
rch@chromium.org
The number of times QuicHttpStream's session_ is a nullptr before
StartRequest() is called.
rch@chromium.org
The reason (the state of the server config) for sending inchoate ClientHello
to the server.
zhongyi@chromium.org
The time from QUIC detecting network performance degradation to network
disconnection.
zhongyi@chromium.org
The time from QUIC detecting network performance degradation to an
alternative network becoming default.
zhongyi@chromium.org
The time from network disconnection to an alternative network becoming
default.
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.
rch@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.
Removed as of 05/2017.
rch@chromium.org
The number of times QuicHttpStream's stream_ is a nullptr before
IsDoneReading() is called.
Deprecated as of 4/15/2017.
rch@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.
rch@chromium.org
The state of the QUIC server information when it's loaded from the disk
cache.
Deprecated as of 4/19/2017.
rch@chromium.org
Time spent waiting to load QUIC server information from disk cache.
Deprecated as of 4/15/2017.
rch@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.
Deprecated as of 8/3/2017.
rch@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.
Deprecated as of 4/15/2017.
rch@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.
Deprecated 08/2016.
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.
Deprecated 08/2016.
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).
ckrasic@chromium.org
The number of pending stream requests aborted when the session is closed.
Pending streams are those which could not be created immediately because
there were too many active streams.
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.
rch@chromium.org
The number of BLOCKED frames recevied by a QuicSession when the session is
closed.
rch@chromium.org
The number of BLOCKED frames sent by a QuicSession when the session is
closed.
rch@chromium.org
The network error code returned to a QUIC session from the CertVerifier when
a certification verification is attempted.
rch@chromium.org
Time spent verifying a certificate when racing cert veriifcation with host
resolution.
rch@chromium.org
The final maximum packet size of the connection used by the client before
the session is closed.
rch@chromium.org
The network error code which resulted in all sessions being 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
True if a QUIC connection connected successfully after having been broken.
Only emitted after a QUIC connection attempt to a server that was previous
marked as broken.
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.
rch@chromium.org
Whether QUIC session's connection is flow control blocked when a PING
message is sent to server.
zhongyi@chromium.org
The result of a QUIC connection migration attempt. The suffix specifies the
cause of connection migration.
fayang@chromium.org
The result of connectivity probing according to different migration causes.
Recorded for every connectivity probing when attempting connection
migrations.
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.
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.
zhongyi@chromium.org
This measures the time gap between the most recent write error and the
network disconnection.
zhongyi@chromium.org
Whether QuicGoAwayFrame is received from server for connection migration due
to client's port change. Logged when a QuicGoAwayFrame with error code
QUIC_ERROR_MIGRATING_PORT is received.
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.
zhongyi@chromium.org
The handshake status when when the session attempts to migrate the
connection according to different migration causes.
The experiments with head of line blocking have been completed, and the code
tracking head of line blocking was removed.
ckrasic@chromium.org
The elapsed time that headers are head of line blocked on others, presumably
due to lost headers stream packets.
Deprecated 08/2016.
rch@chromium.org
The frames received on the headers stream which arrived early.
rch@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.
Deprecated 08/2016. No longer tracked.
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
The source for the initial RTT estimate recorded when a QUIC session is
created.
rch@chromium.org
The location where a QUIC internal error was generated, recorded any time an
internal error is generated, which should be once per connection.
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 minimum RTT observed during the life of a QUIC connection.
rch@chromium.org
The number of MTU probes sent by the client during the session. Logged when
the connection is destroyed.
rch@chromium.org
The number of QUIC streams opened when a new QUIC stream is created.
ckrasic@chromium.org
The number of pending stream requests when a new stream request is added to
the pending list. Pending streams are those which could not be created
immediately because there were too many active streams.
zhongyi@chromium.org
The number of queued packets when a connection is closed due to writing an
out of order packet.
zhongyi@chromium.org
The number of queued packets when a connection starts to write queued
packets.
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.
zhongyi@chromium.org
The number of missing packets between the last received packet before a PING
frame sent and the first packet received after PING sent.
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
Deprecated 08/2016.
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).
ckrasic@chromium.org
The number of packets retransmitted per 1000. Only sessions with
packets_sent >= 100 are included. Recorded in session destructor.
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.
ckrasic@chromium.org
The wait time of the pending stream when it is finally serviced. Pending
streams are those which could not be created immediately because there were
too many active streams.
zhongyi@chromium.org
The platform notification received by QUIC when network change happens.
rch@chromium.org
True if the QUIC session prefers to use AES GCM because of hardware support.
zhongyi@chromium.org
Number of retries to send connectivity probing packet on new path until
success.
zhongyi@chromium.org
The wait time to receive a matched probing response to mark connectivity
probing as successful.
Deprecated 02/2018. Use Net.QuicSession.PublicResetAddressMismatch2.
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.
ckrasic@chromium.org
The number of push streams received when the session is closed.
ckrasic@chromium.org
The number of pushed and used streams when the session is closed.
zhongyi@chromium.org
The number of bytes that is pushed but not used when the session is closed.
zhongyi@chromium.org
The number of bytes that is pushed when the session is closed.
rch@chromium.org
Version of the QUIC protocol used for this connection.
rch@chromium.org
The network error code returned when attempting to read from a QUIC
connection. The suffix specifies the condition/source of the read error.
zhongyi@chromium.org
The network error code returned when attempting to read on the current
network from a QUIC connection after handshake has been confirmed.
rch@chromium.org
True if the QUIC REJ message received from the server contains a proof.
rch@chromium.org
The length in bytes of a QUIC REJ message received from the server.
Deprecated 11/2017. Use Net.QuicSession.RetryAfterWriteErrorCount2.
rch@chromium.org
The number of consecutive times a packet was retried after a write error.
rch@chromium.org
The number of consecutive times a packet was retried after a write error,
using exponential backoff.
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.
Deprecated 03/2018 as crbug.com/817496 is resolved.
zhongyi@chromium.org
The number of times the connection sends connectivity probe to the peer.
rch@chromium.org
The largest packet which the client received from the server during the
session.
rch@chromium.org
The final smoothed RTT observed during the life of a QUIC connection.
rch@chromium.org
The QUIC error code which resulted in the stream (and connection) being
closed by the client after the handshake was confirmed.
rch@chromium.org
The QUIC error code which resulted in the stream (and connection) being
closed by the client after the handshake was confirmed.
rch@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
If a QUIC connection timed out locally with open streams, this contains the
local port number for the connection.
Deprecated 04/2015. Tracked as Net.QuicSession.TooManyOpenStreams.
rch@chromium.org
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.
Deprecated 08/2016.
rch@chromium.org
The number of truncated ACK frames received.
Deprecated 08/2016.
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
Time spent verifying the signature and certificate chain. This is logged
whenever QUIC verifies the certificate chain and signature during crypto
handshake.
rch@chromium.org
The network error code returned when attempting to write to a QUIC
connection.
rch@chromium.org
The network error code returned when attempting to write to a QUIC
connection after the handshake has been confirmed.
zhongyi@chromium.org
The most recent network error code when attempting to write to a QUIC
connection when the network gets disconnected.
Deprecated 06/2018 after https://crbug.com/818040 is fixed.
wub@chromium.org
Temporary histogram being used to investigate https://crbug.com/818040.
Records whether a connection is closed when an out of order queued packet is
about to be written.
ckrasic@chromium.org
The reason QUIC packet writer needed to allocate a new buffer, rather than
the expected case of reusing its existing one.
rch@chromium.org
A count of how often a user hits 1, 2, 3, 4 and 5 bad packet loss events for
port 443. Recorded whenever QUIC has bad packet loss (high packet loss on
multiple consecutive connections).
zhongyi@chromium.org
Records, for initial socket created for each new QUIC connection, whether
the bound network matched the default network tracked by QuicStreamFactory.
ckrasic@chromium.org
Rrecords reasons QUIC is disabled (for all ports), if sufficent recent
connections experience: public reset post crypto handshake, or timeouts with
streams open. QUIC is disabled until the next reboot of Chrome. Logged
during session close.
ckrasic@chromium.org
Captures the maximum number of public resets post handshake that occurred
within a window of recent connections (default 20). Will help inform the
choice of threshold to disable QUIC for clients that experience pathalogical
errors. Logged during session close.
rch@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.
ckrasic@chromium.org
Captures the maximum number of connection timeouts with streams open that
occurred within a window of recent connections (default 20). Will help
inform the choice of threshold to disable QUIC for clients that experience
pathalogical errors. Logged during session close.
Deprecated 06/2016. No longer tracked.
rch@chromium.org
Whether TSVIPCli DLL is loaded or not on windows when the socket is
configured.
Deprecated 08/2016. No longer tracked.
zhongyi@chromium.org
Time duration from last packet sent to a new packet sent in QUIC connection.
rch@chromium.org
Logged whenever proof verification fails and if the failure occurred before
or after the crypto handshake is confirmed.
csharrison@chromium.org
rsleevi@chromium.org
The total number of redirects encountered during processing a URLRequest.
This includes redirects generated by servers (for example, 302 Found) and
redirects generated internally (for example, HSTS redirects or error pages).
eustas@chromium.org
True for redirect responses with unadvertised "Content-Encoding".
False for valid redirect responses. See http://crbug.com/714514
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.
juliatuttle@chromium.org
The outcome of Reporting trying to process a single endpoint group in a
Report-To header once the header itself has been parsed.
juliatuttle@chromium.org
The outcome of Reporting trying to process a single endpoint in a Report-To
header once the header itself has been parsed.
juliatuttle@chromium.org
The outcome of Reporting trying to process a Report-To header. Once it is
parsed, Reporting.HeaderEndpointOutcome records the outcome of the endpoints
within it.
juliatuttle@chromium.org
When Reporting successfully delivers a report, the number of unsuccessful
delivery attempts that preceded the successful one.
juliatuttle@chromium.org
The delivery latency of reports successfully delivered by Reporting. Starts
when the report is queued and finishes when the delivery attempt returns
successfully.
juliatuttle@chromium.org
The outcome of Reporting trying to deliver a report, recorded when the
report is finally erased from memory.
juliatuttle@chromium.org
The error (net or HTTP) encountered by Reporting trying to upload one or
more reports to a single endpoint in a single request, recorded when the
upload attempt completes, if and only if the attempt failed with a net error
or an HTTP error other than 410 (which is specified to mean "remove
endpoint").
juliatuttle@chromium.org
The outcome of Reporting trying to upload one or more reports to a single
endpoint in a single request, recorded when the upload attempt completes.
Replaced by Net.RequestTime2 due to bug in original implementation.
The amount of time between request initiation and request completion for
success and various different errors.
Unused, so removed from Chromium as of 2017/8/31.
The amount of time between request initiation and request completion for
success and various different errors.
Unused, so removed from Chromium as of 2017/8/31.
csharrison@chromium.org
The amount of time between request initiation and request completion for
ERR_ABORTED when the request's scheme is http/s.
Unused, so removed from Chromium as of 2017/8/31.
csharrison@chromium.org
The amount of time between request initiation and request completion for
ERR_ABORTED when the requests TotalReceivedBytes() > 0.
Unused, so removed from Chromium as of 2017/8/31.
csharrison@chromium.org
The amount of time between request initiation and request completion for
ERR_ABORTED when the requests TotalReceivedBytes() = 0 and
received_response_content_length() = 0.
Unused, so removed from Chromium as of 2017/8/31.
csharrison@chromium.org
The amount of time between request initiation and request completion for
ERR_ABORTED when the requests TotalReceivedBytes() = 0 and
received_response_content_length() > 0.
Unused, so removed from Chromium as of 2017/8/31.
csharrison@chromium.org
The amount of time between request initiation and request completion for
ERR_ABORTED when the request's scheme is not http/s.
Removed from Chromium as of 2018/7/2.
csharrison@chromium.org
The amount of time between request initiation and request completion for
success for main frame resources.
Removed from Chromium as of 2018/7/2.
csharrison@chromium.org
The amount of time between request initiation and request completion for
success for non-main frame resources.
Removed from Chromium as of 2018/7.
xunjieli@chromium.org
The largest number of outstanding requests that are handled by the resource
dispatcher host for a single process.
Removed from Chromium as of 2018/7.
xunjieli@chromium.org
The largest number of outstanding requests that are handled by the resource
dispatcher host across all processes.
Removed from code as of 03/2018.
ksakamoto@chromium.org
The largest number of outstanding requests handled by the resource
dispatcher host, during the last sample interval (60 seconds). Not logged if
there are no outstanding requests in the interval. This metric is temporary
for the Loading Dispatcher v0 (crbug.com/723233), and will be removed soon.
yhirano@chromium.org
toyoshim@chromium.org
Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode)
for HTTP "GET" requests.
yhirano@chromium.org
toyoshim@chromium.org
Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode)
for HTTP "POST" requests.
yhirano@chromium.org
toyoshim@chromium.org
Records request mode (https://fetch.spec.whatwg.org/#concept-request-mode)
for HTTP "POST" requests whose url contains a port.
Removed 10/2017.
maksim.sisov@intel.com
mmenke@chromium.org
Records how many times expected content size equals/less/more than size of
read body/buffer or content size is unkown. Recorded for each resource load.
This experiment was turned down, see https://crbug.com/703188.
tzik@chromium.org
Counts whether the chunk inlining is applicable or not to a resource
loading. Counts the reason if inapplicable.
clamy@chromium.org
When starting a cross-site navigation, the time between reading the headers
and body of the response.
tzik@chromium.org
Time from the start to the end of receiving a response body. Recorded for
each resource load.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Removed from Chromium as of 2018/7/2.
csharrison@chromium.org
The time elapsed from URLRequest creation to when a ResourceLoader actually
calls Start on it.
The code to record this histogram was removed November 2017.
juliatuttle@chromium.org
Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by
the browser process.
The code to record this histogram was removed November 2017.
juliatuttle@chromium.org
Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by
a renderer process.
The code to record this histogram was removed November 2017.
juliatuttle@chromium.org
Count of (post-SSL/proxy, pre-filter) kilobytes received per request made by
a process not covered by one of the other ResponseSizeByProcess histograms.
Deprecated as of 9/2017.
xunjieli@chromium.org
Whether an idle socket is reused, timed out, or closed to make room for new
sockets.
Deprecated as of 7/2017.
mmenke@chromium.org
Seconds a socket was idle before it was reused. Emitted upon reuse. Does not
record the times sockets were idle before first use.
Deprecated as of 11/2016.
xunjieli@chromium.org
Number of milliseconds an idle socket saved in connection establishment
because it is reused.
mmenke@chromium.org
Number of idle sockets when one of them was reused.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time a previously used socket sat idle before encountering a recoverable
socket IO error (connection abort/reset/close).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time an unused socket sat idle before encountering a recoverable socket
IO error (connection abort/reset/close).
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.
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
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
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
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
The time a socket stream was open.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@chromium.org
Each bucket is the number of protocol type on socket stream.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@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
Number of reads on a socket stream.
Deprecated 2014-10-28. No longer generated. No direct replacement.
yhirano@chromium.org
ricea@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
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.
rch@chromium.org
The size of a socket's receive buffer when the attempt to change it via
setsockopt failed.
rch@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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Time it takes to request a new (unused) SOCKS proxy socket.
see SocketType_SOCK
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of sockets returned by the SOCKS pool.
Replaced by Net.SpdyConnectionLatency_2 on 2014-10-21.
rch@chromium.org
Time from when the Connect() starts until it completes.
Removed 2018-02.
bnc@chromium.org
Time from when the Connect() starts until it completes.
bnc@chromium.org
The counts of the flow control state of each frame (with stream and session
flow control on).
The last protocol which would trigger this was deprecated in 2014 November.
This histogram is deprecated in 2016 January.
rch@chromium.org
The counts of the flow control state of each frame (with stream flow control
on).
bnc@chromium.org
The percent compression achieved when compressing HEADERS frames.
ckrasic@chromium.org
The compression percentage in received HPACK compressed header frames.
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.
bnc@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.
bnc@chromium.org
The RTT for SPDY's PING.
Removed 2016-05-26.
rch@chromium.org
The count of streams at each priority over Spdy sessions.
bnc@chromium.org
This histogram is recorded exactly once for every PUSH_PROMISE frame
received on an HTTP/2 connection, and tracks the fate of the pushed stream.
bnc@chromium.org
The number of bytes recevied per stream.
bnc@chromium.org
HTTP status codes received in HTTP/2 HEADERS frames. If a stream contains
one or more informational (1xx) response preceeding the main response, each
status code is logged separately.
bnc@chromium.org
The number of bytes sent per stream.
Removed on 2016-10-10.
rch@chromium.org
Total number of bytes recevied per session before closing session due to
EOF.
Removed on 2016-10-10.
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.
bnc@chromium.org
Socket connected status in SpdySession::CreateStream.
zhongyi@chromium.org
The number of bytes that is pushed but not used when the session is closed.
zhongyi@chromium.org
The number of bytes that is pushed when the session is closed.
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.
bnc@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.
bnc@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.
bnc@chromium.org
The type of SPDY Session used when looking up a session.
bnc@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.
Removed on 2016-10-10.
rch@chromium.org
SpdySession::GetLocalAddress returned ERR_SOCKET_NOT_CONNECTED.
Removed on 2016-10-10.
rch@chromium.org
SpdySession::GetPeerAddress returned ERR_SOCKET_NOT_CONNECTED.
Removed on 2016-10-10.
rch@chromium.org
The count of SPDY Sessions with or without stalls.
Removed on 2016-10-10.
rch@chromium.org
The congestion window (in pkts) received at the end of a SpdySession.
Deprecated 2016 July with removal of SPDY/3.1.
rch@chromium.org
The congestion window (in pkts) sent at the beginning of a SpdySession.
Removed on 2016-10-10.
rch@chromium.org
Percentage of sessions which received settings from the server.
Removed on 2016-10-10.
rch@chromium.org
The Download Retransmission Rate (%) received at the end of a SpdySession.
Removed on 2016-10-10.
rch@chromium.org
The RTT received at the end of a SpdySession.
Removed on 2016-10-10.
rch@chromium.org
Percentage of sessions which sent settings to the server.
bnc@chromium.org
The time between receiving the first chunk and the last chunk of data on a
Spdy stream.
bnc@chromium.org
The number of pushed, but abandoned streams over a single session.
bnc@chromium.org
The number of streams issued over a single session.
bnc@chromium.org
The number of pushed, and used streams over a single session.
bnc@chromium.org
The number of push streams received over a single session.
Removed on 2016-10-10.
rch@chromium.org
The number of stream stalls per session.
bnc@chromium.org
The time of a Spdy stream. Measured from sending the first chunk to
receiving the last chunk of data.
bnc@chromium.org
The time between sending the request and receiving the first chunk of data
on a Spdy stream.
Deprecated on 2016-11-28, because SPDY/3 and, accordingly, SYN_STREAM frames
are no longer used. Compression values are now calculated slightly
differently. Replaced by Net.SpdyHeadersCompressionPercentage.
bnc@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 across
different builds. Replaced by Net.SpdyVersion2.
rch@chromium.org
The SPDY protocol version that is used to talk to SPDY servers.
Deprecated on 2016-02-01, because the incorrect bucket count caused data
corruption. Replaced by Net.SpdyVersion3.
bnc@chromium.org
The SPDY protocol version that is used to talk to SPDY servers. Logged
every time a SPDY session is initialized.
Deprecated 2016 July with removal of SPDY/3.1.
bnc@chromium.org
The SPDY protocol version that is used to talk to SPDY servers. Logged
every time a SPDY session is initialized.
Deprecated 2018-01 with the transition to a unified root list with OS
fallback.
rsleevi@chromium.org
The results of comparing the built-in list of known Windows roots against
the CERT_AUTH_ROOT_SHA256_HASH_PROP_ID certificate property. Recorded for
each certificate verification on Windows.
agl@chromium.org
rsleevi@chromium.org
The SSL/TLS cipher suite that was negotiated. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds.
agl@chromium.org
Counts of specific error codes returned when opening an SSL connection.
Removed 7/21/2015. No longer tracked.
bengr@chromium.org
Counts of specific error codes returned when opening an SSL connection for
an endpoint which is eligible for fastradio padding.
Removed 2018-03-07. No longer tracked.
svaldez@chromium.org
Counts of specific error codes returned when opening an SSL connection for
google.com and any subdomain of it.
svaldez@chromium.org
Counts of specific error codes returned when opening an SSL connection for
an endpoint we are using in the initial TLS 1.3 deployment.
Replaced by Net.SSL_Connection_Latency_2 on 2014-10-21.
agl@chromium.org
Time from when the Connect() starts until it completes.
agl@chromium.org
Time from when the Connect() starts until it completes.
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.
agl@chromium.org
Time from when the Connect() starts until it completes for full handshakes.
Replaced by Net.SSL_Connection_Latency_Google2 on 2014-10-21.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it.
Removed 2018-03-07. No longer tracked.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it.
Removed 2018-03-07. No longer tracked.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it for full handshakes.
Removed in 2011.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it. This only includes users in a 50% field trial that
disables revocation checking for certificate pinned sites.
Removed 2018-03-07. No longer tracked.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it for resumption handshakes.
Removed in 2011.
agl@chromium.org
Time from when the Connect() starts until it completes for google.com and
any subdomain of it. This only includes users not in a 50% field trail that
disables revocation for certificate pinned sites.
Deprecated as of 2016-12-01.
mab@chromium.org
Time from when the Connect() starts until it completes (full handshakes
only), for a set of domains that we expect to always offer the experimental
post-quantum (CECPQ1) ciphersuites.
agl@chromium.org
Time from when the Connect() starts until it completes for any server that
echos a dummy post-quantum padding extension.
agl@chromium.org
Time from when the Connect() starts until it completes for resumption
handshakes.
svaldez@chromium.org
Time from when the Connect() starts until it completes for a set of domains
that we are using in the initial TLS 1.3 deployment.
Deprecated as of 2016-12-01.
mab@chromium.org
For only browsers in the post-quantum (CECPQ1) ciphersuite experiment,
counts the full TLS handshakes where CECPQ1 was, or was not, negotiated on
hosts where we expect it to be negotiated.
Deprecated as of 01/2016.
eranm@chromium.org
rsleevi@chromium.org
The state of compliance with Certificate Transparency presence requirements
for each EV certificate. An EV certificate could be non-compliant (in which
case it loses the EV status), comply through inclusion in the EV whitelist
or have the required number of Signed Certificate Timestamps. This metric
will gauge adoption rate of Certificate Transparency and will help identify
when the EV whitelist is no longer needed. Emitted during every SSL
connection establishment, but only if the client is checking compliance with
Certificate Transparency requirements (currently guarded by a Finch
experiment).
Removed 06/2017 with the deprecation of the EV certificate whitelist after
all certificates expired.
eranm@chromium.org
rsleevi@chromium.org
Whether an EV certificate is present in the Certificate Transparency
whitelist. Emitted once for every EV certificate encountered (during SSL
connection establishment), but only if the client has a valid whitelist.
Removed 06/2017 with the deprecation of distinct EV and !EV CT policies.
eranm@chromium.org
rsleevi@chromium.org
The state of compliance with Certificate Transparency presence requirements
for each EV certificate. An EV certificate could be non-compliant (in which
case it loses the EV status), comply through inclusion in the EV whitelist
or comply with the CT certificate policy. This metric will gauge adoption
rate of Certificate Transparency and will help identify when the EV
whitelist is no longer needed. Emitted during every SSL connection
establishment.
Removed 06/2017 with the deprecation of the EV certificate whitelist after
all certificates expired.
eranm@chromium.org
rsleevi@chromium.org
Whether the client holds a valid EV Certificates whitelist or not. Only
emitted when an EV cert that is not compliant with the Certificate
Transparency requirement is encountered. This histogram is intended to be
short-lived and help determine if EV certificates are considered
non-compliant because they are not whitelisted or if the client does not
hold a valid instance of the whitelist.
Removed September 2016.
sigbjorn@opera.com
agl@chromium.org
rsleevi@chromium.org
Bit strength of the key exchange for DHE. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds.
sigbjorn@opera.com
agl@chromium.org
rsleevi@chromium.org
The curve used for key exchange for ECDHE. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds.
Removed May 2016.
sigbjorn@opera.com
agl@chromium.org
rsleevi@chromium.org
Bit strength of the key exchange for RSA. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds. See |SSL_SESSION|'s
key_exchange_info for more information.
Removed on 01/2016. Only ever measured blacklisted Comodo serials, not any
of the other blacklisted certificates and keys.
agl@chromium.org
Counts the number of times that users have hit blacklisted certificates. The
indexes match up to the indexes in
net/base/x509_certificate.cc:IsBlacklisted. The details of the certificates
in question is confidential.
rsleevi@chromium.org
Time to complete a certificate verification (success case).
rsleevi@chromium.org
Time to complete a certificate verification (error case).
davidben@chromium.org
For each HTTPS connection to the TLS 1.3 experiment server set, whether the
TLS 1.3 anti-downgrade mechanism would have fired. This is to measure the
effects of non-compliant middleboxes on this otherwise safe security
feature. The numbers are only valid while the TLS 1.3 experiment set deploys
a TLS 1.3 draft version compatible with the corresponding Chrome version and
implement the our draft anti-downgrade signal. See
https://crbug.com/boringssl/226.
Removed June 2016.
davidben@chromium.org
For each successful HTTPS request which used the TLS version fallback, the
error code of the last failed attempt.
Removed June 2016.
davidben@chromium.org
For each successful HTTPS request which used the TLS version fallback, the
type of handshake failure of the last failed attempt.
Removed in 2011.
Please list the metric's owners. Add more owner tags as needed.
Time to complete a DNS lookup for a DNS CAA record.
Removed in 2011.
Please list the metric's owners. Add more owner tags as needed.
Time that we would have wasted had we waited for a CAA lookup in order to
validate a certificate.
Removed in 2012.
Please list the metric's owners. Add more owner tags as needed.
Time to complete a speculative certificate verification.
bnc@chromium.org
For each TLS handshake, whether ALPN was negotiated; and if so, the
negotiated protocol.
Removed in March 2016.
davidben@chromium.org
The cipher suite used when the corresponding operation on an SSLClientSocket
fails with ERR_SSL_PROTOCOL_ERROR. This histogram will be removed when
https://crbug.com/593963 is resolved.
Removed in March 2016.
davidben@chromium.org
The internal, version-specific BoringSSL error reason reported when the
corresponding operation on an SSLClientSocket fails with
ERR_SSL_PROTOCOL_ERROR. This histogram will be removed when
https://crbug.com/593963 is resolved.
Superseded by Net.SSLNegotiatedAlpnProtocol in 2016 August.
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.
Removed in January 2018.
davidben@chromium.org
svaldez@chromium.org
The number of bytes, excluding the record header, of each TLS record read.
davidben@chromium.org
For each TLS connection which uses a known root, an RSA key, and TLS 1.2 or
below, what the result of checking the RSA key usage would have been.
davidben@chromium.org
For each TLS connection which uses a unknown root, an RSA key, and TLS 1.2
or below, what the result of checking the RSA key usage would have been.
davidben@chromium.org
For each attempted SSL renegotiation (non-initial handshake), whether the
server supported the renegotiation_info extension (RFC 5746).
Replaced by Net.SSLSignatureAlgorithm.
davidben@chromium.org
For each SSL connection with a full handshake using a DHE- or ECDHE-based
key exchange, the hash function used in the ServerKeyExchange signature.
Removed on 2017-10-02.
nharper@chromium.org
For each SSL connection where we resume a session and negotiate HTTP/2, the
simulated minimum number of sessions retained per host it would have
required with TLS 1.3 single-use sessions. See https://crbug.com/631988.
Removed on 2015-11-10.
davidben@chromium.org
For each SSL connection that resumed a session, whether the session was
resumed at the same version it was established at. This is only recorded in
BoringSSL ports.
davidben@chromium.org
For each SSL connection with a full handshake using a DHE- or ECDHE-based
key exchange, the signature algorithm used to authenticate the peer. In TLS
1.2, this is the signature on the ServerKeyExchange message. (Note: Although
the ECDSA values specify a curve, the curve is only enforced in TLS 1.3.)
Removed on 2014-08-20.
Please list the metric's owners. Add more owner tags as needed.
The number of times that we have performed SSLv3 fallback and found a TLS
renegotiation patched server.
Removed in 2012.
Please list the metric's owners. Add more owner tags as needed.
Was a speculative certificate verification used?
Removed in 2012.
Please list the metric's owners. Add more owner tags as needed.
Time saved by a speculative certificate vertification.
davidben@chromium.org
The SSL/TLS version that was negotiated. Recorded for each SSL/TLS
connection in the socket pool where Connect() succeeds.
Removed April 2018.
davidben@chromium.org
svaldez@chromium.org
For each detected SSL version interference against a server in the initial
TLS 1.3 deployment, details on how the initial connection failed.
davidben@chromium.org
For each detected SSL version interference, what network error the original
failed connection reported.
davidben@chromium.org
For each SSL version interference probe, what network error triggered it.
Probes are only triggered for a small set of network errors.
Removed in 07/2017.
palmer@chromium.org
True if a DNS name contains only characters for which
|net::IsValidLabelCharacter| returns true. Used to see if we can deprecate
and remove support for arbitrary bytes in DNS names. This histogram is
recorded after DNS resolution has completed successfully.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Number of idle sockets when the Connect() succeeded.
mmenke@chromium.org
Time from when the Connect() starts until it completes. Only times under 10
minutes are logged.
mgersh@chromium.org
Time from when the Connect() starts until it completes when the network
address only contains IPv4 addresses. Only times under 10 minutes are
logged.
mgersh@chromium.org
Time from when the Connect() starts until it completes when the IPv4
fallback connection won the race against IPv6. Only times under 10 minutes
are logged.
mgersh@chromium.org
Time from when the Connect() starts until it completes when we race an IPv6
connection against an IPv4 connection with a 300ms delay. Only times under
10 minutes are logged.
mgersh@chromium.org
Time from when the Connect() starts until it completes when the network
address only contains IPv6 addresses. Only times under 10 minutes are
logged.
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.
bmcquade@chromium.org
The kernel's estimated TCP round trip time. Recorded for each TCP socket, at
the time it is disconnected.
Was only used for HTTP[S] connections, renamed to Net.HTTPSocketType.
Please list the metric's owners. Add more owner tags as needed.
The counts of the type of TCP socket returned.
Experiment complete, code removed.
davidben@chromium.org
The time it took to do an IO to UI round-trip in the
ThreadHopResourceThrottle. This is part of an experiment to determine the
feasibility to moving some high-level resource loading checks to the UI
thread.
nharper@chromium.org
Time spent creating a Token-Binding header.
nharper@chromium.org
Logs on each request that is sent on a connection where Channel ID was sent
whether the key that would be used for Token Binding matches the key used
for Channel ID.
nharper@chromium.org
For each request to accounts.google.com on a connection where Channel ID was
sent, this logs whether the Cookie store and the Channel ID store were
ephemeral or persistent.
nharper@chromium.org
The number of secure HTTP requests broken down by support for Token Binding,
indicating if Token Binding was negotiated and supported by both client and
server, or why it wasn't if not.
Discontinued as of 4/12/09
Please list the metric's owners. Add more owner tags as needed.
Effective bandwidth in KByte/Second of transactions logged to
Transaction_Latency histogram. Note that only samples durations greater
than zero ms, and less than 1 hour are tallied into this ratio.
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).
Deprecated as of 10/2017.
Please list the metric's owners. Add more owner tags as needed.
Posix error code from call to bind() UDP socket.
Deprecated as of 10/2017.
Please list the metric's owners. Add more owner tags as needed.
Windows error code from call to bind() UDP socket.
mgersh@chromium.org
Chromium error code from call to RandomBind() UDP socket.
rch@chromium.org
The time spent in closesocket call in UDPSocketWin::Close.
estark@chromium.org
Records the usage of the Referrer-Policy header on redirect responses. This
histogram is recorded on each HTTP redirect response, with the value true if
a Referrer-Policy header was present and false otherwise.
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.
Deprecated 1/1/2018. No longer tracked.
Indicates the number of URLRequests that are handed out by a
URLRequestContext and are not yet destroyed.
Deprecated 1/1/2018. No longer tracked.
Records the annotation type of the URLRequest that is handed out by a
URLRequestContext when Net.URLRequestContext.OutstandingRequests is
recorded.
Deprecated 07/2017, not necessary to determine deprecation for invalid DNS
names.
palmer@chromium.org
True if a DNS name contains only characters for which
|net::IsValidLabelCharacter| returns true. Used to see if we can deprecate
and remove support for arbitrary bytes in DNS names. This histogram is
recorded when converting dotted DNS names into DNS query form, in
preparation for issuing a DNS request.
rajendrant@chromium.org
bengr@chromium.org
Records the downstream data use of WebSockets. Logged on every read
operation in the WebSocket.
rajendrant@chromium.org
bengr@chromium.org
Records the upstream data use of WebSockets. Logged on every write operation
in the WebSocket.
yhirano@chromium.org
ricea@chromium.org
Count the number of WebSockets that accepted permessage-deflate extension
for each context take over mode. Used by the new Chromium-based WebSocket
implementation.
yhirano@chromium.org
ricea@chromium.org
The time from a WebSocket is successfully opened until it's closed. Used to
study how WebSockets are used.
yhirano@chromium.org
ricea@chromium.org
Positive net error codes that WebSockets end with, including OK and ABORTED.
Deprecated 03/2018, replaced by Net.WebSocket.HandshakeResult2.
yhirano@chromium.org
ricea@chromium.org
Results of WebSocket handshakes. Use this histogram as a baseline for
investigating feature usage counters.
yhirano@chromium.org
ricea@chromium.org
bnc@chromium.org
Results of WebSocket handshakes, including information whether the handshake
happened over HTTP/2. Use this histogram as a baseline for investigating
feature usage counters.
yhirano@chromium.org
ricea@chromium.org
All HTTP status codes seen during WebSocket handshakes.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Status for TCP protocol for echoing
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The RTT for TCP protocol for echoing
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Status for UDP protocol for echoing
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The RTT for UDP protocol for echoing
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
This histogram records how many packets (out of 6 attempted) were sent via
UDP as rapidly as possible, just after successfully sending an UMA upload.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome sends 6 UDP packets in a row to test to see if there is a
probabalistic dependency in packet loss for consecutive packets. We record
a bit vector of packets received, where the least significant bit is a 1 if
the first packet was received, etc. For example, if all packets other than
packet 2 and 4 are responded to, then we'd have a sample (in binary) of
110101B, or 53.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP as rapidly as
possible, just after successfully sending an UMA upload. Each packet was
numbered, as was its ACK sent back by Google. If no packets (of the 21) were
ever ACKed, then the port is assumed to be blocked, and no data is recorded
in this histogram. If the port is not blocked, then this histogram shows the
number of echo responses received from the first
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP as rapidly as
possible, just after successfully sending an UMA upload. Each packet was
numbered, as was its ACK sent back by Google. This histogram records, for
each packet number, how often we received an ACK for that packet.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP as rapidly as
possible, just after successfully sending an UMA upload. If no packets (of
the 21) were ever ACKed, then the port is assumed to be blocked. The
histogram shows if we ever got an ACK for a packet in our series of 21.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
This histogram records how many packets (out of 21 attempted) were sent via
UDP as rapidly as possible, just after successfully sending an UMA upload.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, 21 packets were sent to Google via UDP on port 443 or
6121.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, a few packets were sent from Google to clients via UDP
on port 443 or 80 to perform net connectivity test.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
In this experiment, a few packets were sent from Google to clients via UDP
on port 443 or 80 to perform net connectivity test.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Next NetConnectivity5 experiment weren't started because there is an
outstading pending write.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network metric sampling the time spent using Cellular to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a 3G/Cellular
network and configure Layer 3 state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that a
3G/Cellular network is online after configuring Layer 3 state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that a
3G/Cellular network is in a captive portal after configuring Layer 3 state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS cellular usage API request status codes.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network metric sampling the time spent using Ethernet to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a wired
Ethernet network and configure Layer 3 state (typically acquire a DHCP
lease).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is online after configuring Layer 3 state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is in a captive portal after configuring Layer 3 state.
Deprecated 8/2015.
cschuet@chromium.org
Chrome OS metric counting the number of network configurations that
contained a NSS nickname identifying a CA certificate, which triggered the
migration to PEM encoding. This metric doesn't consider whether the
migration was successful but once a migration was successful the nickname is
removed.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS connection manager service errors seen.
benchan@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.
benchan@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.
benchan@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.
benchan@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.
benchan@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
benchan@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.
benchan@chromium.org
Chrome OS cellular network metric that tracks the number of drops based on
the network technology.
Deprecated since Chrome OS build 10010.0.0 and superceded by
Network.Shill.Cellular.ExpiredLeaseLengthSeconds2 due to change in number of
buckets (crosreview.com/557297, crosreview.com/703679).
benchan@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
cellular network at the time it expired without the DHCP client being able
to renew it.
benchan@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
cellular network at the time it expired without the DHCP client being able
to renew it.
benchan@chromium.org
Chrome OS network metric that tracks the presence of complete IPv6
configuration at the time when cellular connection is established.
benchan@chromium.org
Chrome OS network metric that tracks the types of IP configuration used for
establishing cellular connections.
benchan@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.
benchan@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.
benchan@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.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the result of portal detections
for a cellular network.
benchan@chromium.org
Chrome OS network metric sampling the signal strength (0-100) of the
cellular modem before it dropped from the network.
benchan@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).
benchan@chromium.org
Chrome OS network performance metric sampling the time to join a cellular
network and configure Layer 3 state.
benchan@chromium.org
Chrome OS network performance metric sampling the time to connect a cellular
modem.
benchan@chromium.org
Chrome OS network performance metric sampling the time to disable a cellular
modem.
benchan@chromium.org
Chrome OS network performance metric sampling the time to enable a cellular
modem.
benchan@chromium.org
Chrome OS network performance metric sampling the time to initialize a
cellular modem.
benchan@chromium.org
Chrome OS network performance metric sampling the time to determine that a
cellular network is online after configuring Layer 3 state.
benchan@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.
benchan@chromium.org
Chrome OS network performance metric sampling the time to scan a cellular
network and register a modem.
benchan@chromium.org
Chrome OS network metric that tracks the connectivity issue diagnosed by the
ConnectionDiagnostics class in Shill. This metric is logged each time a
ConnectionDiagnostics object completes its diagnostics actions and reports
the results to its caller.
benchan@chromium.org
Chrome OS cellular network metric that tracks the number of corrupted
profiles encountered by Shill.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the number of dark resume
actions that successfully complete or fail when shill suspends.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes dark resume actions to complete when shill suspends.
Deprecated 01/2015. Migrated to Network.Shill.DarkResumeActionsTimeTaken.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes dark resume actions to complete when shill suspends.
benchan@chromium.org
Chrome OS network metric sampling the number of times a dark resume scan is
retried in a single dark resume.
benchan@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.
benchan@chromium.org
Chrome OS network performance metric that tracks the connection status of
the device. A sample is emitted once every 3 minutes.
benchan@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 MTU value proposed by the
DHCP server. A sample is emitted each time the DHCP client completes
negotiation with a server.
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.
benchan@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.
benchan@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.
benchan@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
benchan@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.
Deprecated since Chrome OS build 10010.0.0 and superceded by
Network.Shill.Ethernet.ExpiredLeaseLengthSeconds2 due to change in number of
buckets (crosreview.com/557297, crosreview.com/703679).
benchan@chromium.org
Chrome OS network performance metric that tracks the length of a lease for
an Ethernet network at the time it expired without the DHCP client being
able to renew it.
benchan@chromium.org
Chrome OS network performance metric that tracks the length of a lease for
an Ethernet network at the time it expired without the DHCP client being
able to renew it.
benchan@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.
benchan@chromium.org
Chrome OS metric that signals the type of failure the LinkMonitor
encountered which caused it to stop monitoring an Ethernet network.
benchan@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.
benchan@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.
benchan@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.
benchan@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.
benchan@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.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the result of portal detections
for an Ethernet network.
benchan@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).
benchan@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).
benchan@chromium.org
Chrome OS network performance metric sampling the time to initialize an
Ethernet device.
benchan@chromium.org
Chrome OS network performance metric sampling the time to determine that an
Ethernet network is online after configuring Layer 3 state.
benchan@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.
gdk@chromium.org
Chrome OS network diagnostic metric sampling the MTU value provided by the
upstream PPP peer. A sample is emitted each time the client successfully
negotiates an MTU value via PPP.
benchan@chromium.org
Chrome OS connection manager service errors seen.
benchan@chromium.org
Chrome OS network metric sampling the number of services that are connected
to the currently connected network.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the number of suspend actions
that successfully complete or fail when shill suspends.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes suspend actions to complete when shill suspends.
Deprecated 01/2015. Migrated to Network.Shill.SuspendActionsTimeTaken.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes suspend actions to complete when shill suspends.
benchan@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.
Deprecated 10/2014. Migrated to Network.Shill.SuspendActionResult.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the number of termination
actions that successfully complete or fail when shill suspends.
Deprecated 10/2014. Migrated to Network.Shill.TerminationActionResult.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the number of termination
actions that successfully complete or fail when shill terminates.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill terminates.
Deprecated 01/2015. Migrated to Network.Shill.TerminationActionsTimeTaken.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill terminates.
Deprecated 10/2014. Migrated to Network.Shill.SuspendActionTime.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill suspends.
Deprecated 10/2014. Migrated to Network.Shill.TerminationActionTime.
benchan@chromium.org
Chrome OS network diagnostic metric sampling the time in milliseconds it
takes termination actions to complete when shill terminates.
benchan@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).
benchan@chromium.org
Chrome OS network metric that tracks the number of user-initiated events.
cernekee@chromium.org
Chrome OS network usage metric sampled on each successful VPN connection
that tracks the VPN connection type.
cernekee@chromium.org
Chrome OS network usage metric sampled on each successful VPN connection
that tracks the remote authentication method.
cernekee@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.
cernekee@chromium.org
Chrome OS network performance metric sampling the time to configure Layer 3
state on a VPN network (typically acquire a DHCP lease).
cernekee@chromium.org
Chrome OS network performance metric sampling the time to determine that a
WiMax network is online after configuring Layer 3 state.
cernekee@chromium.org
Chrome OS network usage metric sampled on each successful VPN connection
that tracks the user authentication method.
matthewmwang@chromium.org
Chrome OS network metric sampling the number of Wireless Access Points that
support the 802.11k standard, sampled on successful connections to an AP.
matthewmwang@chromium.org
Chrome OS network metric sampling the number of Wireless Access Points that
support the 802.11r standard, sampled on successful connections to an AP.
matthewmwang@chromium.org
Chrome OS network metric sampling the number of Wireless Access Points that
support the 802.11v BSS Max Idle Period feature, sampled on successful
connections to an AP.
matthewmwang@chromium.org
Chrome OS network metric sampling the number of Wireless Access Points that
support the 802.11v BSS Transition feature, sampled on successful
connections to an AP.
matthewmwang@chromium.org
Chrome OS network metric sampling the number of Wireless Access Points that
support the 802.11v DMS feature, sampled on successful connections to an AP.
matthewmwang@chromium.org
Chrome OS network usage metric sampled when an AP switches channels. Shows
the old frequency band and the new frequency band.
kirtika@chromium.org
Chrome OS network usage metric. Reason code reported when the AP
disconnects a WiFi connection.
kirtika@chromium.org
Chrome OS network usage metric. Broad category of reason AP disconnected a
WiFi connection.
kirtika@chromium.org
Chrome OS network usage metric. The AP mode setting for each successful
WiFi connection.
kirtika@chromium.org
Chrome OS network metric sampling the number of wifi services available for
auto-connect when auto-connect is initiated for wifi device.
kirtika@chromium.org
Chrome OS network metric sampling the number of BSSes (endpoints) available
for the currently connecting wifi service.
kirtika@chromium.org
Chrome OS network usage metric. The channel used for each successful WiFi
connection.
kirtika@chromium.org
Chrome OS network usage metric. Reason code reported when the client
disconnects a WiFi connection.
kirtika@chromium.org
Chrome OS network usage metric. Broad category of reason client
disconnected a WiFi connection.
kirtika@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.
kirtika@chromium.org
Chrome OS network metric that tracks the wake reason for dark resume.
kirtika@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.
kirtika@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
kirtika@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.
kirtika@chromium.org
Chrome OS network usage metric sampled on each successful 802.1x wireless
connection that tracks the configured inner authentication method.
kirtika@chromium.org
Chrome OS network usage metric sampled on each successful 802.1x wireless
connection that tracks the configured outer authentication method.
Deprecated since Chrome OS build 10010.0.0 and superceded by
Network.Shill.Wifi.ExpiredLeaseLengthSeconds2 due to change in number of
buckets (crosreview.com/557297, crosreview.com/703679).
kirtika@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
WiFi network at the time it expired without the DHCP client being able to
renew it.
kirtika@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
WiFi network at the time it expired without the DHCP client being able to
renew it.
kirtika@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.
kirtika@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.
kirtika@chromium.org
Chrome OS network metric that tracks the presence of complete IPv6
configuration at the time when WiFi connection is established.
kirtika@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.
kirtika@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.
kirtika@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.
kirtika@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.
kirtika@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.
kirtika@chromium.org
Chrome OS network metric that tracks the types of IP configuration used for
establishing WiFi connections.
kirtika@chromium.org
Chrome OS network performance metric that tracks the network problems
encountered by TrafficMonitor after WiFi connection is established.
kirtika@chromium.org
Chrome OS network usage metric. The channel type used for each successful
WiFi connection.
kirtika@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.
kirtika@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.
kirtika@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.
kirtika@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.
kirtika@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.
matthewmwang@chromium.org
Chrome OS network metric recording roam successes or failures. This is
recorded every time a client succeeds or fails to roam from one wireless
access point to another.
matthewmwang@chromium.org
Chrome OS network metric recording roam time in milliseconds. This is
recorded every time a successful roam from one wireless access point to
another occurs.
kirtika@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.
kirtika@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.
kirtika@chromium.org
Chrome OS network usage metric. The security setting for each successful
WiFi connection.
matthewmwang@chromium.org
Chrome OS network metric recording session length in milliseconds. This is
recorded every time an uninterrupted session with a wireless access point is
terminated.
silberst@chromium.org
Chrome OS network metric indicating the negative of the dBm received signal
strength recorded at the time of a WiFi disconnect.
kirtika@chromium.org
Chrome OS network metric indicating the negative of the dBm received signal
strength recorded at the time a successful WiFi connection started.
kirtika@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.
kirtika@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.
semenzato@chromium.org
kirtika@chromium.org
Time spent in suspended state, on a resume, for the case when wake on wifi
is disabled (WoWOff), and after resume, the NIC is found to be already
connected.
semenzato@chromium.org
kirtika@chromium.org
Time spent in suspended state, on a resume, for the case when wake on wifi
is enabled (WoWOff), and after resume, the NIC is found to be disconnected.
semenzato@chromium.org
kirtika@chromium.org
Time spent in suspended state, on a resume, for the case when wake on wifi
is enabled (WoWOn), and after resume, the NIC is found to be already
connected.
semenzato@chromium.org
kirtika@chromium.org
Time spent in suspended state, on a resume, for the case when wake on wifi
is enabled (WoWOn), and after resume, the NIC is found to be disconnected.
kirtika@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).
kirtika@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.
kirtika@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).
kirtika@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).
kirtika@chromium.org
Chrome OS network performance metric sampling the time to initialize an
802.11 wireless device.
kirtika@chromium.org
Chrome OS network performance metric sampling the time to join (associate
plus authenticate) an 802.11 wireless network.
kirtika@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.
kirtika@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.
kirtika@chromium.org
Chrome OS network performance metric sampling the time to scan WiFi until a
connection is found.
kirtika@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.
kirtika@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.
kirtika@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).
kirtika@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.
kirtika@chromium.org
Chrome OS network performance metric that tracks the result of
user-initiated WiFi connection attempts.
kirtika@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.
kirtika@chromium.org
Chrome OS network usage metric that tracks the wake on WiFi features that
are enabled in shill. Recorded once every 10 minutes.
kirtika@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.
kirtika@chromium.org
Chrome OS network metric that tracks whether a wake reason was received
during dark resume before executing WakeOnWiFi::OnDarkResume.
kirtika@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.
benchan@chromium.org
Chrome OS network metric that tracks the presence of a WiMax device in the
system. A sample is emitted once every 3 minutes.
Deprecated 5/2014, and replaced by Network.Shill.DHCPOptionFailureDetected.
benchan@chromium.org
Chrome OS network metric that tracks the number of DHCP option failures
encountered by Shill. This indicates that Shill is using minimal DHCP
options due to suspected MTU issues on the return path from the DHCP server
back to the client.
Deprecated since Chrome OS build 10010.0.0 and superceded by
Network.Shill.Wimax.ExpiredLeaseLengthSeconds2 due to change in number of
buckets (crosreview.com/557297, crosreview.com/703679).
benchan@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
WiMax network at the time it expired without the DHCP client being able to
renew it.
benchan@chromium.org
Chrome OS network performance metric that tracks the length of a lease for a
WiMax network at the time it expired without the DHCP client being able to
renew it.
benchan@chromium.org
Chrome OS network performance metric sampling the time to configure Layer 3
state on a WiMax network (typically acquire a DHCP lease).
benchan@chromium.org
Chrome OS network performance metric sampling the time to initialize a WiMax
device.
benchan@chromium.org
Chrome OS network performance metric sampling the time to determine that a
WiMax network is online after configuring Layer 3 state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a 3G/Cellular
network and configure Layer 3 state. Note this metric is deprecated; see
Network.Cellular.TimeToConfig.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join a wired
Ethernet network and configure Layer 3 state (typically acquire a DHCP
lease). Note this metric is deprecated; see Network.Ethernet.TimeToConfig.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease). Note
this metric is deprecated; see Network.Wifi.TimeToConfig.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network stability metric sampling the time in seconds between the
networking going online to going offline. Offline events due to device
shutdown or suspend are ignored (along with the online time before that
offline event).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join (associate
plus authenticate) an 802.11 wireless network. Note this metric is
deprecated; see Network.Wifi.TimeToJoin.
yzshen@chromium.org
How much, in bytes, of the response body has been read from network by a
URLLoader before it pauses reading, when it receives a
PauseReadingBodyFromNet() call. If there are multiple calls to
PauseReadingBodyFromNet(), only a single value is recorded for the last
call. This histogram is recorded by URLLoader implementations that fetch
from network. When SafeBrowsing indicates that a resource may be unsafe and
therefore a more time-consuming check is required to classify it, reading
response body from network is paused in order to reduce the chance of
writing unsafe contents into cache. This histogram is useful to evaluate how
much data is cached during this window.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Network metric reporting the download speed test results run at setup time.
Recorded at least once per day.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network metric sampling the time spent using WiFi to transport
data. These data are mostly useful when summed and compared to TimeOnline
for other network technologies (e.g. WiFi vs Cellular).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time from the resume event
to the time when an 802.11 wireless network has configured its Layer 3
state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to configure Layer 3
state on an 802.11 wireless network (typically acquire a DHCP lease).
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to join (associate
plus authenticate) an 802.11 wireless network.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
802.11 wireless network is online after configuring Layer 3 state.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS network performance metric sampling the time to determine that an
802.11 wireless network is in a captive portal after configuring Layer 3
state.
stevenjb@chromium.org
Number of shared remembered (preferred) networks on Chrome OS. Updated any
time the network list changes.
stevenjb@chromium.org
Number of private remembered (preferred) networks on Chrome OS. Updated any
time the network list changes.
stevenjb@chromium.org
Number of visible (in-range) networks on Chrome OS. Updated any time the
network list changes.
jam@chromium.org
How long the browser waits for the network process to exit at shutdown.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker observes a tick clock and a wall clock to determine
whether a timestamp retrieved from the network in the past can be used to
compute a current timestamp. When the tick clock and wall clock diverge from
each other, the NetworkTimeTracker must discard the network timestamp
because it has no way to compute a reliable current timestamp. Whenever the
NetworkTimeTracker discards a network timestamp due to the tick and wall
clocks diverging, this histogram records the difference of the tick clock's
delta minus the wall clock's delta since the network timestamp was
retrieved. For cases where the the tick clock delta is bigger than the wall
clock delta, see NetworkTimeTracker.ClockDivergence.Positive.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker observes a tick clock and a wall clock to determine
whether a timestamp retrieved from the network in the past can be used to
compute a current timestamp. When the tick clock and wall clock diverge from
each other, the NetworkTimeTracker must discard the network timestamp
because it has no way to compute a reliable current timestamp. Whenever the
NetworkTimeTracker discards a network timestamp due to the tick and wall
clocks diverging, this histogram records the difference of the tick clock's
delta minus the wall clock's delta since the network timestamp was
retrieved. For cases where the the wall clock delta is bigger than the tick
clock delta, see NetworkTimeTracker.ClockDivergence.Negative.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker makes periodic queries to obtain a secure timestamp over
the network. This histogram records the delta between each secure timestamp
and the previous one, to measure how often time queries are made. The first
time query is not recorded, because there is no previous query from which to
compute a delta.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker makes periodic queries to obtain a secure timestamp over
the network. This histogram records the latency of each time query.
Deprecated 08/2016 because it does not provide additional information beyond
NetworkTimeTracker.UpdateTimeFetchFailed and
NetworkTimeTracker.UpdateTimeFetchValid.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker makes periodic queries to obtain a secure timestamp over
the network. This histogram increments whenever such a query is attempted.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker makes periodic queries to obtain a secure timestamp over
the network. This histogram records the request's net error code whenever a
secure timestamp fetch results in a network error or a non-200 HTTP status
code.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker makes periodic queries to obtain a secure timestamp over
the network. Whenever one of these requests results in a successful 200
status code, this histogram records true if the response parsed and
validated successfully, and false otherwise.
estark@chromium.org
mab@chromium.org
NetworkTimeTracker observes a tick clock and a wall clock to determine
whether a timestamp retrieved from the network in the past can be used to
compute a current timestamp. When the NetworkTimeTracker observes that the
wall clock ran backwards, the NetworkTimeTracker must discard the network
timestamp because it has no way to compute a reliable current timestamp.
Whenever the NetworkTimeTracker discards a network timestamp due to the wall
clock running backwards, this histogram records the magnitude of the
difference of the current wall clock time minus the wall clock time when the
network timestamp was retrieved.
Deprecated as of 01/2017. Replaced by NewTabPage.ActionAndroid2.
newt@chromium.org
Actions taken by users from the new tab page on Android. These actions may
navigate away from the NTP (e.g. searching in the omnibox or opening a
bookmark), but can also happen without navigating away from the NTP (e.g.
opening a bookmark in a new tab).
finkm@chromium.org
Actions taken from the new tab page on Android. These actions may navigate
away from the NTP (e.g. searching in the omnibox or opening a bookmark), but
can also happen without navigating away from the NTP (e.g. opening a content
suggestion in a new tab).
justincohen@chromium.org
Actions taken by users from the new tab page on iOS. These actions may
navigate away from the NTP (e.g. searching in the omnibox or opening a
bookmark), but can also happen without navigating away from the NTP (e.g.
opening a bookmark in a new tab).
treib@chromium.org
The amount of time it takes to download the animated logo. Android only.
Please list the metric's owners. Add more owner tags as needed.
Histogram for the source of app page drags. For any succesful drop onto an
apps pane of the NTP, this logs where the drag originated.
ramyan@chromium.org
yyushkina@chromium.org
The time it took until a request from the New Tab Page for Google Photos
albums was served.
ramyan@chromium.org
yyushkina@chromium.org
The time it took until a request from the New Tab Page for Backdrop
Collections was served.
ramyan@chromium.org
yyushkina@chromium.org
The time it took until a request from the New Tab Page for Backdrop Images
was served.
ramyan@chromium.org
yyushkina@chromium.org
The time it took until a request from the New Tab Page for Google Photos (in
a specific album) was served.
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.
jkrcal@chromium.org
Android: Result of fetching a favicon for an article suggestion on the New
Tab Page.
jkrcal@chromium.org
Android: Time it takes to fetch a favicon for an article suggestion on the
New Tab Page.
huayinz@chromium.org
twellington@chromium.org
Android: Whether article suggestions on New Tab Page are set visible by user
on startup and when the visibility is changed.
jkrcal@chromium.org
Android: The type of trigger that caused a background fetch of NTP content
suggestions from a suggestion server. Every background fetch is recorded.
Deprecated in October 2017 (M64) and replaced by
NewTabPage.ContentSuggestions.BreakingNews.ReceivedMessageAction, when
adding support for push-to-refresh messages.
vitaliii@chromium.org
Android: Number of received messages and whether they contain pushed news. A
message contains pushed news if the payload key exists in the message. The
payload content is not checked at all (e.g. it may be empty). Recorded when
a message is received.
mamir@chromium.org
Android: Action of a received message. An action can be either push-by-value
or push-to-refresh. A message with a missing or invalid action is recorded
as well. Recorded when a message is received.
vitaliii@chromium.org
Android: The result of a subscription request for breaking news at the
content suggestions server. Recorded when a request finishes. Analogous to
NewTabPage.ContentSuggestions.BreakingNews.UnsubscriptionRequestStatus.
vitaliii@chromium.org
Android: Time between a token validation and the last successful token
retrieval from InstanceID. Recorded when InstanceID answers our token
request for a validation either with a token or an error. If the token was
never received before the validation, the metric is not recorded.
vitaliii@chromium.org
Android: The result of our inquiry to InstanceID to receive the current
token. Recorded when InstanceID replies to our inquiry for a token
(including for a validation).
vitaliii@chromium.org
Android: The result of an unsubscription request for breaking news at the
content suggestions server. Recorded when a request finishes. Analogous to
NewTabPage.ContentSuggestions.BreakingNews.SubscriptionRequestStatus.
vitaliii@chromium.org
Android: Whether a token validation detected an invalid token. This is
recorded only for validations where no error occured and the token was
actually retrieved.
treib@chromium.org
Android: A category of content suggestions that was dismissed (by swiping
away its empty state card).
Deprecated in July 2017. This metric was replaced by
CountOnNtpOpenedIfVisible. Initially the metric was not recorded properly if
any category was not visible. This was fixed in
https://codereview.chromium.org/2874213002/, however, not visible categories
still were polluting the metric (they were recorded as showing 0
suggestions).
treib@chromium.org
Android: The number of suggestion cards that were available at the time an
NTP was opened.
vitaliii@chromium.org
Android: The number of suggestion cards that were available at the time an
NTP was opened. Only visible categories (i.e. which can be seen by the user
on this NTP) are recorded, including empty ones.
Deprecated in October 2017 (M63) and replaced by
CountOnNtpOpenedIfVisible.Articles.Prefetched.Offline2, because
underreported. UI checked whether a URL is prefetched asynchronously. As a
result, there was a race condition and this metric could be reported before
all URLs are checked.
vitaliii@chromium.org
Android: The number of prefetched suggestion cards that were available in
Articles category if it was visible at the time an NTP was opened and the
user was offline. Analogous to
NewTabPage.ContentSuggestions.CountOnNtpOpenedIfVisible.
vitaliii@chromium.org
Android: The number of prefetched suggestion cards that were available in
Articles category if it was visible at the time an NTP was opened and the
user was offline. Analogous to
NewTabPage.ContentSuggestions.CountOnNtpOpenedIfVisible, except that this
metric is reported after all URL prefetched asynchronous checks finish.
treib@chromium.org
Android: The position of a suggestion card on the NTP that is dismissed,
typically by swiping it away. The suggestion had a URL that was NOT visited
before. We track the position the card had in the list when it was first
seen by the user. This tracked position can be different from the position
observed by the user, e.g. when the user dismissed some suggestions from the
list or requested more that got inserted in the middle of the feed.
treib@chromium.org
Android: The position of a suggestion card on the NTP that is dismissed,
typically by swiping it away. The suggestion had a URL that was visited
before. We track the position the card had in the list when it was first
seen by the user. This tracked position can be different from the position
observed by the user, e.g. when the user dismissed some suggestions from the
list or requested more that got inserted in the middle of the feed.
treib@chromium.org
Android: The position of a suggestion card whose long-press menu was opened,
analogous to NewTabPage.ContentSuggestions.Opened.
treib@chromium.org
Android: The age of a suggestion card on the NTP whose long-press menu was
opened, analogous to NewTabPage.ContentSuggestions.OpenedAge.
Replaced by NewTabPage.ContentSuggestions.MenuOpenedScoreNormalized.
treib@chromium.org
Android: The relevance score of a suggestion card on the NTP whose
long-press menu was opened, analogous to
NewTabPage.ContentSuggestions.OpenedScore.
tschumann@chromium.org
Android: The relevance score of a suggestion card on the NTP whose
long-press menu was opened, analogous to
NewTabPage.ContentSuggestions.OpenedScoreNormalized. Scores (which are
typically floats within (0,1]) get reported as discrete integers within
[1,10]. For instance, the discrete value 1 represents score values from
(0.0, 0.1]. The discrete value 11 is the overflow bucket for unexpectedly
high scores.
treib@chromium.org
Android: The position of a "More" suggestion card that was clicked
on the NTP. A card is considered shown when at least 2/3 of its height is
visible on the screen. We track the position the card had in the list when
it was first seen by the user. This tracked position can be different from
the position observed by the user, e.g. when the user dismissed some
suggestions from the list or requested more that got inserted in the middle
of the feed.
treib@chromium.org
Android: The position of a "More" suggestion card that was shown
on the NTP. A card is considered shown when at least 2/3 of its height is
visible on the screen. For each card, at most one impression is recorded per
NTP instance. We track the position the card had in the list when it was
first seen by the user. This tracked position can be different from the
position observed by the user, e.g. when the user dismissed some suggestions
from the list or requested more that got inserted in the middle of the feed.
vitaliii@chromium.org
Android: The new index of a category on the NTP after it has been moved up
due to a click. The index of a category, which has been overtaken, is not
recorded here. This tracked index can be different from the position
observed by the user, e.g. empty categories are not shown. This metric
ignores all other order changes (e.g. dismissing a category or clearing
history).
sfiera@chromium.org
Android: The number of actions taken on displayed notifications, either
user-initiated (tapping to open or swiping to dismiss), or automatic (hiding
due to a change in circumstances).
sfiera@chromium.org
Android: The number of times a user opted out, keyed by method: IMPLICIT
(user ignored enough notifications consecutively that we think they're not
interested), or EXPLICIT (via explicit setting).
sfiera@chromium.org
Android: The number of notifications that were shown, keyed by category. One
bucket counts the server-provided ARTICLES category; the other counts
everything else.
treib@chromium.org
Android: How an article linked from a suggestion card on the NTP was opened
(e.g. plain click, open in new tab, open in incognito).
treib@chromium.org
Android: The position of the suggestion card on the NTP, that is clicked
through to the host website of the content. We track the position the card
had in the list when it was first seen by the user. This tracked position
can be different from the position observed by the user, e.g. when the user
dismissed some suggestions from the list or requested more that got inserted
in the middle of the feed.
vitaliii@chromium.org
Android: The position of the prefetched suggestion card on the NTP, that is
clicked through to the host website of the content, when the user is
offline. Analogous to NewTabPage.ContentSuggestions.Opened. That is we track
the position the card had in the list when it was first seen by the user.
This tracked position can be different from the position observed by the
user, e.g. when the user dismissed some suggestions from the list or
requested more that got inserted in the middle of the feed.
treib@chromium.org
Android: The age of a suggestion card on the NTP that is clicked through to
the host website of the content. The age is measured from the moment the
content has been published.
vitaliii@chromium.org
Android: The index of a category on the NTP, whose suggestion card is
clicked through to the host website of the content. This tracked index can
be different from the position observed by the user, e.g. for the user a
category may be at the top of the NTP, but with index 1, because they
dismissed the one that was previously at the top.
Replaced by NewTabPage.ContentSuggestions.OpenedScoreNormalized.
treib@chromium.org
Android: The score of a suggestion card on the NTP that is clicked through
to the host website of the content. The recorded score is from the moment
the suggestion was fetched, it could have changed since.
tschumann@chromium.org
Android: The score of a suggestion card on the NTP that is clicked through
to the host website of the content. The recorded score is from the moment
the suggestion was fetched, it could have changed since. Scores (which are
typically floats within (0,1]) get reported as discrete integers within
[1,10]. For instance, the discrete value 1 represents score values from
(0.0, 0.1]. The discrete value 11 is the overflow bucket for unexpectedly
high scores.
dgn@chromium.org
finkm@chromium.org
Whether content suggestions from the remote service are enabled. It is
recored at startup. Note: This histogram is not specific to the New Tab
Page.
vitaliii@chromium.org
Android: The number of suggestion sections that were shown at the time an
NTP was opened. All shown sections (including empty ones) are counted.
treib@chromium.org
Android: The position of a suggestion card that was shown on the NTP. A card
is considered shown when at least 2/3 of its height is visible on the
screen. For each card, at most one impression is recorded per NTP instance.
We track the position the card had in the list when it was first seen by the
user. This tracked position can be different from the position observed by
the user, e.g. when the user dismissed some suggestions from the list or
requested more that got inserted in the middle of the feed.
Deprecated in October 2017 (M63) and replaced by
Shown.Articles.Prefetched.Offline2, because underreported. UI checked
whether a URL is prefetched asynchronously. As a result, there was a race
condition and for suggestions immediately visible on the suggestions surface
this metric could be reported before their URLs are actually checked.
vitaliii@chromium.org
Android: The position of a prefetched suggestion card that was shown on the
NTP when offline. Analogous to NewTabPage.ContentSuggestions.Shown. That is
a card is considered shown when at least 2/3 of its height is visible on the
screen. For each card, at most one impression is recorded per NTP instance.
We track the position the card had in the list when it was first seen by the
user. This tracked position can be different from the position observed by
the user, e.g. when the user dismissed some suggestions from the list or
requested more that got inserted in the middle of the feed.
vitaliii@chromium.org
Android: The position of a prefetched suggestion card that was shown on the
NTP when offline. Analogous to NewTabPage.ContentSuggestions.Shown. That is
a card is considered shown when at least 2/3 of its height is visible on the
screen. For each card, at most one impression is recorded per NTP instance.
We track the position the card had in the list when it was first seen by the
user. This tracked position can be different from the position observed by
the user, e.g. when the user dismissed some suggestions from the list or
requested more that got inserted in the middle of the feed. This metric is
reported not immediately after the impression, but once the request to
Offline Page model to check the URL finishes.
treib@chromium.org
Android: The age of a suggestion card that was shown on the NTP. A card is
considered shown when at least 2/3 of its height is visible on the screen.
For each card, at most one impression is recorded per NTP instance.
Replaced by NewTabPage.ContentSuggestions.ShownScoreNormalized.
treib@chromium.org
Android: The score of a suggestion card that was shown on the NTP. A card is
considered shown when at least 2/3 of its height is visible on the screen.
For each card, at most one impression is recorded per NTP instance.
tschumann@chromium.org
Android: The score of a suggestion card that was shown on the NTP. A card is
considered shown when at least 2/3 of its height is visible on the screen.
For each card, at most one impression is recorded per NTP instance. Scores
(which are typically floats within (0,1]) get reported as discrete integers
within [1,10]. For instance, the discrete value 1 represents score values
from (0.0, 0.1]. The discrete value 11 is the overflow bucket for
unexpectedly high scores.
Replaced by NewTabPage.ContentSuggestions.TimeSinceSuggestionFetched.
markusheintz@chromium.org
Android: The time since the last successful background fetch of remote
content suggestions. Recorded when the user looks at content suggestions on
the NTP.
markusheintz@chromium.org
Android: The time since the displayed content suggestions was fetched.
Recorded when the user looks at content suggestions on the NTP. The metric
is only recorded for suggestions of the Articles for you section.
jkrcal@chromium.org
Android: The time since the last fetch, recorded upon the first on-shown
fetch trigger. The first on-shown trigger does not necessarily cause a fetch
(if it comes before the end of the respective scheduling interval). This
metric is recorded at most once after each fetch (and additionaly at most
once after each startup of Chrome before the next fetch). This is used to
understand how changing scheduling intervals will impact traffic of
background fetches.
Deprecated as of July 2017, in favor of
NewTabPage.ContentSuggestions.TimeUntilFirstShownTrigger and
NewTabPage.ContentSuggestions.TimeUntilFirstStartupTrigger.
jkrcal@chromium.org
Android: The time since the last fetch, recorded upon the first soft fetch
trigger. The first soft trigger does not necessarily cause a fetch (if it
comes before the end of the respective scheduling interval). This metric is
recorded at most once after each fetch (and additionaly at most once after
each startup of Chrome before the next fetch). This is used to understand
how changing scheduling intervals will impact traffic of background fetches.
jkrcal@chromium.org
Android: The time since the last fetch, recorded upon the first startup
fetch trigger. The first startup trigger does not necessarily cause a fetch
(if it comes before the end of the respective scheduling interval). This
metric is recorded at most once after each fetch (and additionaly at most
once after each startup of Chrome before the next fetch). This is used to
understand how changing scheduling intervals will impact traffic of
background fetches.
jkrcal@chromium.org
Android: The time since the last fetch, recorded upon a persistent fetch.
This is used to understand what are the real persistent fetching intervals
in the wild.
jkrcal@chromium.org
Android: The time since the last fetch, recorded upon a soft fetch. This is
used to understand what are the real soft fetching intervals in the wild.
jkrcal@chromium.org
Android: The time since the last fetch, recorded upon a startup fetch. This
is used to understand what are the real soft fetching intervals in the wild.
Replaced by NewTabPage.ContentSuggestions.UIUpdateResult2 in January 2017.
jkrcal@chromium.org
Android: The result of updating the list of content suggestions in the UI.
jkrcal@chromium.org
Android: The result of updating the list of content suggestions in one UI
section.
jkrcal@chromium.org
Android: The number of content suggestions that have been seen by the user
in the UI section before the section was successfully updated. The seen
suggestions were not removed in the update so that we do not change visible
parts of the UI. This histogram is only recorded when the UIUpdateResult2 is
"Success (some suggestions replaced)".
markusheintz@chromium.org
Android: The time of day (in the local timezone) when the user used content
suggestions. Recorded for example when the user scrolls to the articles
suggestions or opens an article suggestions.
treib@chromium.org
Android: Time spent reading the page linked by an opened suggestion card.
Exit conditions include the tab not being in the foreground or starting a
new navigation.
ramyan@chromium.org
yyushkina@chromium.org
The availability of New Tab Page background customization features on
Desktop, based on feature flags or other configuration settings; logged per
NTP load.
ramyan@chromium.org
yyushkina@chromium.org
The availability of New Tab Page shortcut customization features on Desktop,
based on feature flags or other configuration settings; logged per NTP load.
ramyan@chromium.org
yyushkina@chromium.org
Customization actions performed by the user on the New Tab Page; logged as
each interaction occurs. This may indicate popularity of a particular
customization type.
ramyan@chromium.org
yyushkina@chromium.org
Captures the actions performed when configuring a 'Chrome background' image
on the New Tab Page. Since most actions are sequential, this may indicate
steps in the configuration process where users drop off.
ramyan@chromium.org
yyushkina@chromium.org
The New Tab Page features that have been customized by the user; logged per
NTP load.
ramyan@chromium.org
yyushkina@chromium.org
Captures the actions performed when uploading a local image as the
background on the New Tab Page. Since most actions are sequential, this may
indicate steps in the configuration process where users drop off.
ramyan@chromium.org
yyushkina@chromium.org
Captures the actions performed when configuring shortcuts on the New Tab
Page.
Deprecated 2016-02.
Please list the metric's owners. Add more owner tags as needed.
The default pane when the NTP is first opened.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram of the time, in milliseconds, users have the cursor over a most
visited thumbnail before clicking.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram of the time, in milliseconds, users have the cursor over a most
visited thumbnail before moving it away from the thumbnail without clicking.
Deprecated 2017-04, replaced by NewTabPage.TileType and
NewTabPage.SuggestionsImpression.IconsColor.
newt@chromium.org
The number of most visited tiles on the new tab page that are displayed
using a fallback color (as opposed to having an icon, or simply being gray).
Android only.
Deprecated 2017-04, replaced by NewTabPage.TileType and
NewTabPage.SuggestionsImpression.IconsGray.
newt@chromium.org
The number of most visited tiles on the new tab page that are displayed as
gray (as opposed to having an icon, or a fallback color). Android only.
Deprecated 2017-04, replaced by NewTabPage.TileType and
NewTabPage.SuggestionsImpression.IconsReal.
newt@chromium.org
The number of most visited tiles on the new tab page that are displayed with
the site's icon (as opposed using a fallback color or just gray). Android
only.
Deprecated 2017-05 (and not recorded for some time before that).
knn@chromium.org
Android: Whether an attempt to download the image for an interest was
successful.
Deprecated 2017-05 (and not recorded for some time before that).
knn@chromium.org
Android: Whether an attempt to fetch the interests for a user was
successful.
Deprecated 2017-05 (and not recorded for some time before that).
knn@chromium.org
Android: The number of interests fetched for a user to display on the NTP.
jkrcal@chromium.org
Android: Percentage of how much in browsing is the UI language of Chrome
used compared to overall use of the two top languages that are reported to
Chrome content suggestion server.
Deprecated 2018-04 with full launch of NTP condensed layout.
peconn@chromium.org
Android: A histogram detailing how the NewTabPageLayout is laid out on the
device (eg, whether it fits fully above the fold or not). This is logged
once per NewTabPageLayout creation (so once per NTP).
treib@chromium.org
Histogram of the time, in milliseconds, it took for the NTP to load all of
its tiles since navigation start.
mvanouwerkerk@chromium.org
Android: the type of load for the NTP, such as cold or warm start. It's a
warm start if the native library is already loaded and initialized at the
time the activity is created. This might happen if for example a service was
already running.
treib@chromium.org
The number of clicks on the static/call-to-action/animated logo on the NTP.
treib@chromium.org
Outcome of downloading search provider's logos. It measures whether
download/parsing is successful, revalidation and parsing work properly, etc.
treib@chromium.org
The amount of time it took to download the static logo. This includes
requests where there was no logo, or where an existing logo was revalidated
(so no new image data was downloaded), but it does not include failed
requests.
treib@chromium.org
A logo image (static or CTA) was downloaded. Recorded only when the image
was downloaded and decoded without errors.
treib@chromium.org
The number of static logos and animated logos shown to users. Note that the
base version of this histogram is recorded both for logos from the cache and
for fresh logos, so it can be recorded twice per NTP impression.
Deprecated 2017-08 because it was only recorded for cached logos. Replaced
by LogoShownTime2.
treib@chromium.org
The amount of time between opening an NTP and the logo appearing. Only
recorded when there is a logo, and only recorded once per NTP. Android only.
treib@chromium.org
The amount of time between opening an NTP and the logo appearing. Only
recorded when there is a logo, and only recorded once per NTP.
fserb@chromium.org
zmin@chromium.org
Record the network status when a new tab page is opened. True if user is
online and false for offline.
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.
justincohen@chromium.org
mastiz@chromium.org
treib@chromium.org
Histogram for user clicks of the most visited tile. The value is equal to
the index of the tile.
Deprecated 2016-02 (and not recorded for some time before that).
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.
mastiz@chromium.org
The age of the data at click time, that is, the elapsed time since the
suggestion was generated by a ranking algorithm.
Deprecated 2016-05.
treib@chromium.org
The schemes of URLs of most visited thumbnails that the user clicked on.
Deprecated 2016-02 (and not recorded for some time before that).
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.
treib@chromium.org
The time from the New Tab page being shown until the user to clicked on a
most visited tile. Only recorded if the user clicked on a tile, as opposed
to e.g. searching via the omnibox. Only measured on Android.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
The number of screenshots that were cached for the non-visible but ranked
suggestions on the Suggested NTP pane.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Given that the user has typed a URL, and given that that specific URL was
ranked but not visible on the Suggested pane of the NTP, this is the rank
that the Suggested pane had for that URL.
Deprecated 2016-07.
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.
Deprecated 2016-07.
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.
Deprecated 2016-07.
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.
Deprecated 2016-07.
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.
Deprecated 2016-07.
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.
Deprecated 2016-07.
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.
Deprecated 2016-07.
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.
treib@chromium.org
The number of tiles that are on the NTP, no matter if they are thumbnails,
gray tiles, or external tiles. Recorded before reloading the suggestions,
navigating to a URL, switching tabs, changing the active window or closing
the tab/shutting down Chrome. The sum of this histogram does not have to
equal to the total count of tile impressions (such as the total count in
NewTabPage.TileType). The reason is that not all tiles have to be impressed
initially (e.g., the second row of tiles may be initially out of sight on
iOS).
dewittj@chromium.org
The amount of time spent waiting for the offline page model to return which
New Tab Page URLs are available offline.
treib@chromium.org
The time it took until a request from the New Tab page for the OneGoogleBar
script was served. Recorded only on the local NTP.
treib@chromium.org
Histogram of the time, in milliseconds since navigation start, it took until
the OneGoogleBar showed up on the NTP. Recorded only on the local NTP.
Deprecated 05/2015. Feature was removed.
Please list the metric's owners. Add more owner tags as needed.
Histogram for usage of the menu on the NTP that allows the user to access
tabs from other devices.
Deprecated 2016-02.
Please list the metric's owners. Add more owner tags as needed.
The pane that had been previously selected when the user switches panes in
the NTP.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram for NTP bubble promo activity.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram for NTP notification promo activity.
pkotwicz@chromium.org
Records the amount of time that the "Recent Tabs" page is visible
and Chrome is in the foreground on Android. The metric is recorded whenever
the "Recent Tabs" page moves out of the foreground. The metric is
recorded when the "Recent Tabs" page is closed, when the user
switches from the "Recent Tabs" page to a different tab and when
Chrome is backgrounded.
jkrcal@chromium.org
Records how many background requests of the given type the browser tried to
perform each day where the type is specified by the _suffix of the
histogram. The histogram is emitted only after midnight of the given day
passes - right before the first following request (which can be several days
later if the user does not use Chrome in the meantime). The histogram counts
requests with both QUOTA_GRANTED and QUOTA_EXCEEDED status, i.e. the count
can easily exceed the daily quota.
jkrcal@chromium.org
Records how many interactive requests of the given type the browser tried to
perform each day where the type is specified by the _suffix of the
histogram. The histogram is emitted only after midnight of the given day
passes - right before the first following request (which can be several days
later if the user does not use Chrome in the meantime). The histogram counts
requests with both QUOTA_GRANTED and QUOTA_EXCEEDED status, i.e. the count
can easily exceed the daily quota.
jkrcal@chromium.org
Records the status w.r.t. the quota for all requests of the given type. The
type of request is specified by the _suffix of the histogram.
Deprecated February 2017.
mvanouwerkerk@chromium.org
The time until the search box became available on the NTP in a cold start.
It's a cold start if the native library is not already loaded and
initialized at the time the activity is created. Only measured on Android.
Deprecated February 2017.
mvanouwerkerk@chromium.org
The time until the search box became available on the NTP in a warm start.
It's a warm start if the native library is already loaded and initialized at
the time the activity is created. This might happen if for example a service
was already running. Only measured on Android.
mvanouwerkerk@chromium.org
The time until the search box became available on the NTP in a cold start.
It's a cold start if the native library is not already loaded and
initialized at the time the activity is created. Only measured on Android.
mvanouwerkerk@chromium.org
The time until the search box became available on the NTP in a warm start.
It's a warm start if the native library is already loaded and initialized at
the time the activity is created. This might happen if for example a service
was already running. Only measured on Android.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
TBD.
Deprecated 2016-02.
Please list the metric's owners. Add more owner tags as needed.
The pane selected when the user switches panes in the NTP.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram for user clicks of the Recently Closed items. The value is the
recency of the entry being restored (0 is most recent).
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram to track how many times a user switched pages in a single NTP
session.
Replaced by NewTabPage.ContentSuggestions.Opened.
knn@chromium.org
Android: The position of the snippets card on the NTP, that is clicked
through to the host website of the content. We track the position the
snippet had in the list when NTP was loaded. This tracked position is thus
different from the position observed by the user whenever before scrolling
down to the given snippet, the user discards some snippets in the top of the
list.
Replaced by NewTabPage.ContentSuggestions.OpenedAge.
jkrcal@chromium.org
Android: The age of the snippets card on the NTP, that is clicked through to
the host website of the content. The age is measured from the moment the
content has been published. In each "_x_y" suffix of the
histogram, only snippets on positions \gt;=x and \lt;=y are tracked. We
track the position the snippet had in the list when NTP was loaded. This
tracked position is thus different from the position observed by the user
whenever before scrolling down to the given snippet, the user discards some
snippets in the top of the list.
Deprecated as of 6/2016
jkrcal@chromium.org
Android: The score of the snippets card on the NTP, that is clicked through
to the host website of the content. The recorded score is from the moment
the snippet was fetched, it could have changed since. In each "_x"
suffix of the histogram, only snippets on positions \lt;=x are tracked. We
track the position the snippet had in the list when NTP was loaded. This
tracked position is thus different from the position observed by the user
whenever before scrolling down to the given snippet, the user discards some
snippets in the top of the list.
Replaced by NewTabPage.ContentSuggestions.OpenedScore.
jkrcal@chromium.org
Android: The score of the snippets card on the NTP, that is clicked through
to the host website of the content. The recorded score is from the moment
the snippet was fetched, it could have changed since. In each "_x"
suffix of the histogram, only snippets on positions \lt;=x are tracked. We
track the position the snippet had in the list when NTP was loaded. This
tracked position is thus different from the position observed by the user
whenever before scrolling down to the given snippet, the user discards some
snippets in the top of the list. In contrast to CardClickedScore, this
histogram has a proper maximal value of 100 000.
Deprecated as of 4/2016
knn@chromium.org
Android: The position of the snippets card on the NTP, that is expanded to
reveal more content.
Deprecated as of 4/2016
knn@chromium.org
Android: The position of the snippets card on the NTP, for which the
expanded content was minimized/hidden.
Replaced by NewTabPage.ContentSuggestions.MenuOpened.
peconn@chromium.org
Android: The position of a snippet card when it is long pressed, analagous
to NewTabPage.Snippets.CardClicked.
Replaced by NewTabPage.ContentSuggestions.MenuOpenedAge.
peconn@chromium.org
Android: The time difference between when a snippet card is long pressed and
when its content was published. Analagous to
NewTabPage.Snippets.CardClickedAge.
Replaced by NewTabPage.ContentSuggestions.MenuOpenedScore.
peconn@chromium.org
Android: The relevance score of an interest card that is long pressed,
analagous to NewTabPage.Snippets.CardClickedScoreNew.
Replaced by NewTabPage.ContentSuggestions.Shown.
knn@chromium.org
Android: The position of the snippets card that is shown on the NTP. Each
snippet (its position) is recorded whenever at least 2/3 of its height
becomes visible by scrolling through the NTP. Each snippet is recorded at
most once for a given instance of NTP and a given data set of snippets that
is shown. We track the position the snippet had in the list when NTP was
loaded. This tracked position is thus different from the position observed
by the user whenever before scrolling down to the given snippet, the user
discards some snippets in the top of the list. Previously (in the code
before 2016/05/27), this histogram was recorded each time a snippet became
visible (e.g. by scrolling up and down) at least by 1px; the first snippet
was thus recorded even without scrolling down.
Replaced by NewTabPage.ContentSuggestions.ShownAge.
jkrcal@chromium.org
Android: The age of the snippets card that is shown on the NTP. Each snippet
(its age) is recorded whenever at least 2/3 of its height becomes visible by
scrolling through the NTP. Each snippet is recorded at most once for a given
instance of NTP and a given data set of snippets that is shown. The age is
measured from the moment the content has been published. In each
"_x_y" suffix of the histogram, only snippets on positions \gt;=x
and \lt;=y are tracked. By this, we mean the position the snippet had in the
list when NTP was loaded. This tracked position is thus different from the
position observed by the user whenever before scrolling down to the given
snippet, the user discards some snippets in the top of the list.
Deprecated as of 6/2016
jkrcal@chromium.org
Android: The score of the snippets card that is shown on the NTP. Each
snippet (its score) is recorded whenever at least 2/3 of its height becomes
visible by scrolling through the NTP. Each snippet is recorded at most once
for a given instance of NTP and a given data set of snippets that is shown.
The recorded score is from the moment the snippet was fetched, it could have
changed since. In each "_x" suffix of the histogram, only
snippets on positions \lt;=x are tracked. By this, we mean the position the
snippet had in the list when NTP was loaded. This tracked position is thus
different from the position observed by the user whenever before scrolling
down to the given snippet, the user discards some snippets in the top of the
list.
Replaced by NewTabPage.ContentSuggestions.ShownScore.
jkrcal@chromium.org
Android: The score of the snippets card that is shown on the NTP. Each
snippet (its score) is recorded whenever at least 2/3 of its height becomes
visible by scrolling through the NTP. Each snippet is recorded at most once
for a given instance of NTP and a given data set of snippets that is shown.
The recorded score is from the moment the snippet was fetched, it could have
changed since. In each "_x" suffix of the histogram, only
snippets on positions \lt;=x are tracked. By this, we mean the position the
snippet had in the list when NTP was loaded. This tracked position is thus
different from the position observed by the user whenever before scrolling
down to the given snippet, the user discards some snippets in the top of the
list. In contrast to CardShownScore, this histogram has a proper maximal
value of 100 000.
treib@chromium.org
Android: The time it took to load the database of persisted content
suggestions. Recorded only when the database is loaded successfully.
treib@chromium.org
Android: The state of the RemoteSuggestionsProvider. Recorded when the state
changes, typically once at startup and rarely afterwards, e.g. on database
errors.
mastiz@chromium.org
Response or error codes encountered when attempting to fetch snippets.
mastiz@chromium.org
Result of attempting a fetch, logged once per issued trigger.
mastiz@chromium.org
Time spent fetching snippets. Only recorded for fetch attempts that resulted
in an actual network request.
finkm@chromium.org
Records the time of the day in minutes when a snippets background fetch was
initiated. Counts minutes since midnight UTC.
finkm@chromium.org
Records the time of the day in minutes when a snippets background fetch was
initiated. Counts minutes since midnight local time.
maybelle@chromium.org
Whether we discarded any of the snippets after fetching them due to having
incomplete metadata.
Removed 2016-10.
knn@chromium.org
Android: A histogram giving an overall summary of important events like
impressions, scroll events, clicks etc.
treib@chromium.org
Android: The number of snippet articles available to show on the NTP, logged
once every time the list is updated.
mastiz@chromium.org
Android: The number of valid snippet articles fetched from the server,
logged every time a fetch finishes successfully.
Removed 2016-10.
mastiz@chromium.org
Android: The number of snippet articles available to the user in the UI,
logged when the user scrolls below the fold (at max once per NTP load).
mastiz@chromium.org
Android: The number of snippet articles discarded by the user, logged every
time the list is updated resulting in an empty list (all articles
discarded).
treib@chromium.org
The number of snippets that we discard per fetch due to having incomplete
data.
Replaced by NewTabPage.ContentSuggestions.OpenDisposition.
peconn@chromium.org
Android: A histogram detailing how the articles linked from snippets are
opened (eg, plain click, open in new tab, open in incognito).
Replaced by NewTabPage.ContentSuggestions.VisitDuration.
mastiz@chromium.org
Android: Time spent reading the page linked by an opened (clicked) snippet
card. Exit conditions include the tab not being in the foreground or
starting a new navigation.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Histogram for user clicks of the suggested site thumbnails. The value is
equal to the index of the thumbnail.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Action taken by the user on the Suggested Sites NTP pane.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Time to load the Suggested Sites NTP pane, in milliseconds.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Time spent on the Suggested Sites NTP pane, in seconds.
treib@chromium.org
Histogram for impressions on the various most visited tiles. The value is
equal to the index of the thumbnail.
mastiz@chromium.org
The age of the data at impression time, that is, the elapsed time since the
suggestion was generated by a ranking algorithm.
Deprecated 2016-07.
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.
jkrcal@chromium.org
Mobile only. The result of fetching a favicon for a tile on the New Tab
Page. This is recorded for each gray MostVisited tile on the New Tab Page
once per impression of the tile.
jkrcal@chromium.org
Mobile only. The result of fetching a favicon for a tile on the New Tab
Page. This is recorded for each gray PopularSites tile on the New Tab Page
once per updating the set of tiles (notably upon each NTP impression).
Deprecated 06/2017. Replaced by NewTabPage.TileFaviconFetchStatus.Server.
jkrcal@chromium.org
Mobile only. The result of fetching a favicon for a tile on the New Tab
Page. This is recorded for each gray MostVisited tile on the New Tab Page
once per lifetime of Chrome (there as an in-memory cache of failed
requests).
mastiz@chromium.org
The favicon type that was chosen to represent a most visited tile displayed
on the new tab page, logged at impression time. Note that these values don't
involve an actual icon being displayed because a scrabble time might have
been displayed instead (see NewTabPage.TileType).
mastiz@chromium.org
The favicon type that was chosen to represent a most visited tile displayed
on the new tab page, logged when a tile is clicked. Note that these values
don't involve an actual icon being displayed (see
NewTabPage.TileTypeClicked).
treib@chromium.org
The number of times a tile was available offline, per tile index - compare
to the NewTabPage.SuggestionsImpression.* histograms. This is recorded when
the NTP finishes loading. Only measured on Android.
treib@chromium.org
Histogram of the time, in milliseconds since navigation start, it took for
the NTP most visited iframe to receive the data for all of its tiles. This
does not include actually loading the DOM elements for the tiles, in
particular the thumbnail images; see NewTabPage.LoadTime for that.
fhorschig@chromium.org
Records the source of the title for each most visited tiled displayed when
an NTP is opened, e.g. a short_name from a manifest, or the page title.
fhorschig@chromium.org
Records the source for the name a most visited tile showed when the user
clicked it, e.g. a URL, or the page title.
mastiz@chromium.org
The visual type of each most visited tile displayed on the new tab page,
e.g. actual thumbnail or placeholder thumbnail. This is recorded for each
most visited item when the NTP is opened.
mastiz@chromium.org
The visual type of the most visited item that the user clicked on, e.g.
actual thumbnail or placeholder thumbnail.
bauerb@chromium.org
The time spent on the new tab page as measured from when it was loaded or
last brought to the foreground until it was navigated away from or hidden.
Only measured on Android.
treib@chromium.org
Records the status of the New Tab page URL when an NTP is opened.
jkrcal@chromium.org
Android: The estimated average number of hours between two successive times
when a new tab page is opened. Recorded after each opening of a NTP (and
after updating the model used for the estimate).
jkrcal@chromium.org
Android: The estimated average number of hours between two successive times
when the list of content suggestions on a new tab page is shown (i.e. when
the user scrolls below the fold). Recorded after each time the suggestions
are shown (and after updating the model used for the estimate).
jkrcal@chromium.org
Android: The estimated average number of hours between two successive times
when the user opens a content suggestion or clicks on the "More"
button. Recorded after each time a suggestion or a More button is clicked
(and after updating the model used for the estimate).
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
The number of screenshots that were cached for the visible suggestions on
the Suggested NTP pane.
Deprecated 2016-02 (and not recorded for some time before that).
Please list the metric's owners. Add more owner tags as needed.
Given that the user has typed a URL, and given that that specific URL was
visible on the Suggested pane of the NTP, this is the rank that the
Suggested pane had for that URL.
treib@chromium.org
Actions taken by users of Voice Search on the local New Tab Page on Desktop.
These actions may navigate away from the NTP (e.g. submitting a speech
query), but can also happen without navigating away from the NTP (e.g.
initiating or retrying Voice Search).
treib@chromium.org
Errors that occur during Voice Search use on the local New Tab Page on
Desktop. These may be user-induced (e.g. the user's utterance could not be
recognized - no match), or resulting from external circumstances (e.g.
offline, lack of microphone permission).
dewittj@chromium.org
The actions taken on notifications, recorded every time they happen. This
histogram will record every single event that happens separately.
awdf@chromium.org
Records the delay between scheduling a job with the JobScheduler (with a
desired latency of 0ms, in response to a notification click) and receiving
the onStartJob callback. Only measured on Android N and above.
peter@chromium.org
Records whether notifications are enabled for Chrome, as the Android app,
for each Web Notification that is being shown to the user.
peter@chromium.org
The size, in bytes, of the author-provided data associated with a Web
Notification. Recorded when a persistent Web Notification is being shown by
the developer.
Replaced by Notifications.AuthorDataSize in February 2016.
peter@chromium.org
The size, in kilobytes, of the author-provided data associated with a Web
Notification. Recorded when a persistent Web Notification is being shown by
the developer.
peter@chromium.org
Records the result status codes of deleting notification data from the Web
Notification database that share their tag (replacement identifier) with a
notification that's about to be shown.
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.
Deprecated July 2015. No longer tracked since M42.
peter@chromium.org
Records if the requesting and embedding origins are different when
requesting permission to display Web Notifications.
Deprecated October 2017 (fullscreen notifications feature enabled by
default).
bmalcolm@chromium.org
Counts the number of times a notification was shown for the various types of
sources. The suffix distinguishes between the window state of the app or
webpage that sent the notification. This will be used to determine whether a
legacy mode is required when we allow apps or webpages to display
notifications over fullscreen content in the future.
dewittj@chromium.org
peter@chromium.org
The number of action buttons the developer provided for a notification
created using the extensions notification API. Logged when creating the
notification.
peter@chromium.org
The length, in characters, of the id given to an extension notification.
These can be automatically generated, in which case they will be either 36
bytes (GUID) or 16 bytes (random data) in length, or provided by the
developer. Measured when the notification is being displayed through the
chrome.notifications.create() extension API.
dewittj@chromium.org
peter@chromium.org
The type of a notification created using the extensions notification API.
Logged when creating the notification.
thomasanderson@chromium.org
Whether the notification server supports the capability in question. (Linux
only) Logged when the proxy to /org/Freedesktop/Notifications is set up
successfully, which happens at most once on startup.
Deprecated Nov 2016 in favor of Notifications.LoadFileSize.*
peter@chromium.org
The number of bytes loaded for a Web Notification icon.
Deprecated Nov 2016 in favor of Notifications.LoadFailTime.*
peter@chromium.org
The number of milliseconds it took to fail loading an icon for a Web
Notification.
Deprecated Nov 2016 in favor of Notifications.LoadFinishTime.*
peter@chromium.org
The number of milliseconds it took to finish successfully loading an icon
for a Web Notification.
Deprecated Nov 2016 in favor of Notifications.LoadScaleDownTime.*
peter@chromium.org
The number of milliseconds it took to scale down an icon for a Web
Notification.
thomasanderson@chromium.org
The status code for initializing NotificationPlatformBridgeLinux. (Linux
only) Logged on each start up.
johnme@chromium.org
The number of milliseconds it took to fail loading an icon/image for a Web
Notification.
johnme@chromium.org
The number of bytes loaded for a Web Notification icon/image.
johnme@chromium.org
The number of milliseconds it took to finish successfully loading an
icon/image for a Web Notification.
johnme@chromium.org
The number of milliseconds it took to scale down an icon/image for a Web
Notification.
chengx@chromium.org
The execute status of a ComServerModule class instance. Logged whenever a
notification_helper process is launched by Windows.
chengx@chromium.org
finnur@chromium.org
The primary execute status of NotificationActivator::Activate. Logged
whenever a notification_helper process is launched by Windows.
chengx@chromium.org
finnur@chromium.org
The secondary execute status of NotificationActivator::Activate. Logged
whenever a notification_helper process is launched by Windows.
Deprecated 06/2018. Replaced by NotificationActivatorPrimaryStatus and
NotificationActivatorSecondaryStatus.
chengx@chromium.org
The execute status of NotificationActivator::Activate. Logged whenever a
notification_helper process is launched by Windows.
chengx@chromium.org
The runtime of the notification_helper server process. This process is
created when a notification is activated from the Windows Action Center.
Once created, this process does some COM class registration work, so that
Windows can call certain APIs to handle the notification activation. Upon
finishing the API calls, Windows signals this process to exit.
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.
johnme@chromium.org
The number of action buttons the developer provided for a persistent Web
Notification. Logged whenever showNotification is called.
Deprecated 01/2016, no longer used.
peter@chromium.org
deepak.m1@samsung.com
Recorded when the data associated with a persistent Web Notification gets
deleted. The value will be true if data deletion succeeded, and false if
there was an error.
peter@chromium.org
deepak.m1@samsumg.com
Recorded delivery status for persistent notification clicks to a Service
Worker when handling a click on a persistent WebNotification has finished.
peter@chromium.org
nsatragno@chromium.org
Records delivery status for persistent notification close events sent to a
Service Worker when the event has been handled.
thomasanderson@chromium.org
Indicates if Chrome is using system notifications or the Chrome notification
center. Logged on each start up.
finnur@chromium.org
peter@chromium.org
chengx@chromium.org
The status of Activation requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever an activation from a notification occurs.
finnur@chromium.org
peter@chromium.org
The status of Close requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever a notification is closed.
finnur@chromium.org
peter@chromium.org
The status of Display requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever a notification is displayed.
finnur@chromium.org
peter@chromium.org
The status of decoding launch ids while processing a GetDisplayed requests
in NotificationPlatformBridgeWin (Windows only). Logged whenever a request
to retrieve all displayed notifications comes in.
finnur@chromium.org
peter@chromium.org
The status of GetDisplayedStatus requests in NotificationPlatformBridgeWin
(Windows only). Logged whenever a request to retrieve all displayed
notifications comes in.
finnur@chromium.org
peter@chromium.org
The status of GetNotificationLaunchId requests in
NotificationPlatformBridgeWin (Windows only). Logged whenever a request to
decode the GetNotificationLaunchId comes in.
finnur@chromium.org
peter@chromium.org
The policy value provided by get_Setting in NotificationPlatformBridgeWin
(Windows only). Logged whenever a request to show a notification comes in.
finnur@chromium.org
peter@chromium.org
The return value of get_Setting calls in NotificationPlatformBridgeWin
(Windows only). Logged whenever a request to show a notification comes in.
finnur@chromium.org
peter@chromium.org
The status of HandleEvent requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever a notification event is being handled.
finnur@chromium.org
peter@chromium.org
The status of History requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever history is requested for notifications.
chengx@chromium.org
finnur@chromium.org
Used to indicate the status of decoding an input launch id string (Windows
only). Logged whenever a notification event is being handled.
chengx@chromium.org
peter@chromium.org
The status of OnDismissed requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever a dismiss event is handled.
chengx@chromium.org
peter@chromium.org
The status of OnFailed requests in NotificationPlatformBridgeWin (Windows
only). Logged whenever a failed event is handled.
Replaced with Notifications.Windows.SetReadyCallbackStatus2 which is not
skewed.
finnur@chromium.org
peter@chromium.org
The status of SetReadyCallback requests in NotificationPlatformBridgeWin
(Windows only). Logged once at startup.
chengx@chromium.org
finnur@chromium.org
peter@chromium.org
The status of SetReadyCallback requests in NotificationPlatformBridgeWin
(Windows only). Logged once at startup.
chengx@chromium.org
finnur@chromium.org
peter@chromium.org
Used to indicate the status of start menu shortcut (Windows only). Logged
whenever a notification display attempt is made.
Deprecated 06/2018. Replaced with
Notifications.Windows.StartMenuShortcutStatus where typo is fixed.
chengx@chromium.org
finnur@chromium.org
peter@chromium.org
Used to indicate the status of start menu shortcut (Windows only). Logged
whenever a notification display attempt is made.
Deprecated 05/2018 as this is no longer needed.
chengx@chromium.org
peter@chromium.org
Used to indicate the code path where the user profile manager shows up
during startup (Windows only). Logged whenever a notification event is being
handled.
miguelg@chromium.org
rsesek@chromium.org
Mac only. Records the different events of a Notification XPC connection.
These are recorded by monitoring the different error callbacks provided by
the XPC connection object.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the estimated downstream throughput (in
kilobits per second) and the observed downstream throughput (in kilobits per
second). Downstream throughput estimated by the network quality estimator at
the time of navigation start is compared with the downstream throughput
observed during the specified time interval following the start of the
navigation.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the estimated effective connection type and
the observed effective connection type. Effective connection type is
estimated by the network quality estimator at the time of navigation start
is compared with the effective connection type observed during the specified
time interval following the start of the navigation.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the estimated HTTP RTT and the observed HTTP
RTT. HTTP RTT estimated by the network quality estimator at the time of
navigation start is compared with the HTTP RTT observed during the specified
time interval following the start of the navigation.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the estimated transport RTT and the observed
transport RTT. Transport RTT estimated by the network quality estimator at
the time of navigation start is compared with the transport RTT observed
during the specified time interval following the start of the navigation.
devdeepray@chromium.org
tbansal@chromium.org
The value of the downstream throughput used to compute the bandwidth delay
product. The 80th percentile throughput observation is used to calculate the
bandwidth delay product. This gets recorded everytime the BDP is computed.
devdeepray@chromium.org
tbansal@chromium.org
The value of the TransportRTT used to compute the bandwidth delay product.
The 20th percentile TransportRTT observation is used to calculate the
bandwidth delay product. This gets recorded everytime the BDP is computed.
devdeepray@chromium.org
tbansal@chromium.org
An estimate of the bandwidth delay product which is computed on main-frame
requests. It is calculated using the 80th percentile throughput and 20th
percentile TransportRTT values whenever |ComputeEffectiveConnectionType| is
called and the throughput and TransportRTT estimates are available.
tbansal@chromium.org
bengr@chromium.org
Records if the cached network quality (from memory or from a persistent
source) was available. Recorded right after connection change event.
tbansal@chromium.org
bengr@chromium.org
Whether the signal strength for the cellular network was available or not.
Recorded right before a connection change event. Recorded only on cellular
connections on Android platform.
tbansal@chromium.org
bengr@chromium.org
Difference between the minimum and the maximum received signal strength
since the last connection change event. Recorded only on cellular
connections on Android platform when the cellular signal strength was
available. Recorded right before a connection change event.
Replaced by NQE.CellularSignalStrength.LevelAvailable in June 2017.
tbansal@chromium.org
bengr@chromium.org
Whether the signal strength for the cellular network was available or not.
Recorded right before a connection change event. Recorded only on cellular
connections on Android platform.
Replaced by NQE.CellularSignalStrength.LevelDifference in June 2017.
tbansal@chromium.org
bengr@chromium.org
Difference between the minimum and the maximum received signal strength
since the last connection change event. Recorded only on cellular
connections on Android platform when the cellular signal strength was
available. Recorded right before a connection change event.
tbansal@chromium.org
This metric is recorded when the network quality change notification is
received by content and before the network quality change is notified to the
renderers. Records true if the notified network quality change is
meaningfully different from the last network quality notified to the
renderers.
Obsoleted in December 2017.
tbansal@chromium.org
bengr@chromium.org
Records estimated network quality (estimated RTT, estimated downlink
bandwidth), resource load size, and the resource load time in a single UMA
sample. This metric is recorded randomly when a resource load finishes. Each
sample in this sparse histogram consists of multiple metrics (each occupying
few bits in the sample). The data in the histogram would be analyzed using
custom scripts. A sample is recorded only when the resource size is between
0 Kilobits (inclusive) and 128 Kilobits (exclusive).
Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics.
bengr@chromium.org
tbansal@chromium.org
Difference between the actual RTT observation and the estimated RTT. This
metric is recorded on every request when the actual observation is higher
than the estimated value.
Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics.
bengr@chromium.org
tbansal@chromium.org
Difference between the estimated RTT and the actual RTT observation. This
metric is recorded on every request when the estimated value is higher than
the actual observation.
tbansal@chromium.org
bengr@chromium.org
Effective connection type estimated by the network quality estimator.
Recorded every time the effective connection type is computed.
tbansal@chromium.org
Rough estimate of the computed end-to-end round trip time. Recorded by the
network quality estimator every time the effective connection type is
computed.
tbansal@chromium.org
bengr@chromium.org
This histogram records whether the estimate of the network quality metric
was available or not. Recorded at every main frame request.
Obsoleted in February 2018.
bengr@chromium.org
tbansal@chromium.org
Records the estimate of the downlink bandwidth (in Kbps) provided by the
external estimate provided. Recorded every time the external estimate
provider provides a valid downlink bandwidth estimate to the network quality
estimator.
Obsoleted in February 2018.
bengr@chromium.org
tbansal@chromium.org
Records the estimate of the RTT provided by the external estimate provided.
Recorded every time the external estimate provider provides a valid RTT
estimate to the network quality estimator.
Obsoleted in February 2018.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the HTTP RTT estimated by the external
estimate provider and the observed HTTP RTT. The HTTP RTT estimated by the
external estimate provider at the time of navigation start is compared with
the HTTP RTT observed during the specified time interval following the start
of the navigation.
Obsoleted in February 2018.
bengr@chromium.org
tbansal@chromium.org
Records the interaction (availability and query count) of Network Quality
Estimator with external estimates provider. Logged on network change events,
everytime external estimate provider is queried for an updated estimate, and
when it proactively notifies that an updated estimate is available.
Obsoleted in August 2017
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the fastest round-trip-time, before a connectivity change
is detected.
This metric is recorded when a connectivity change is detected. This will
miss data from users whose connection type never changes and will be biased
to users whose connection type changes frequently.
tbansal@chromium.org
bengr@chromium.org
Number of Kbps observations indexed by the source of the observation.
Recorded by the network quality estimator every time a new observation is
made or synthesized.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the downstream peak throughput (in kilobits per second).
Recorded by the network quality estimator every time the effective
connection type is computed.
tbansal@chromium.org
bengr@chromium.org
Downstream throughput observation received or synthesized by network quality
estimator. Observations from different sources are recorded in separate
histograms.
tbansal@chromium.org
bengr@chromium.org
Effective connection type estimated by network quality estimator. Suffixed
with the connection type reported by the operating system.
This metric is recorded on main-frame requests.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the downstream peak throughput at different percentiles.
This metric is recorded on main-frame requests.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the URLRequest layer at
different percentiles.
This metric is recorded on main-frame requests.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the transport layer at
different percentiles.
This metric is recorded on main-frame requests.
tbansal@chromium.org
bengr@chromium.org
Whether the NetworkID (SSID of the Wi-Fi network, or the MCC/MNC operator of
the cellular network) was available or not. Recorded only on Wi-Fi and
cellular networks. Recorded right after the connection type changes.
Obsoleted in August 2017
bengr@chromium.org
tbansal@chromium.org
Rough estimate of downstream peak throughput, before a connectivity change
is detected.
This metric is recorded when a connectivity change is detected. This will
miss data from users whose connection type never changes and will be biased
to users whose connection type changes frequently.
tbansal@chromium.org
bengr@chromium.org
Number of times the network quality prefs were read by the network quality
estimator.
tbansal@chromium.org
bengr@chromium.org
Count of the number of network IDs in the prefs read by the network quality
estimator.
tbansal@chromium.org
bengr@chromium.org
Number of times the network quality prefs were written by the network
quality estimator.
Replaced in June 2016 by NQE.Accuracy.HttpRTT.* metrics.
bengr@chromium.org
tbansal@chromium.org
Ratio of the estimated RTT to the actual RTT observation multiplied by 100.
tbansal@chromium.org
bengr@chromium.org
Count of the number of times renderers were notified of the changes in the
network quality estimator. This metric makes sense to compare in frequency
relative to other events like the number of page loads or the number of
renderers seen. It is expected that we will see at least 1 notification per
renderer (on average), and less than 100.
Deprecated 01/2018.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the URLRequest layer at
different percentiles.
This metric is recorded immediately after a connectivity change is detected.
The metric name is suffixed with the connection type before the connectivity
change was detected. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
tbansal@chromium.org
HTTP RTT observation received by the network quality estimator. Recorded
when the request is detected as hanging.
tbansal@chromium.org
HTTP RTT observation received by the network quality estimator. Recorded
when the request is detected as not hanging because it was comparable to the
HTTP RTT estimate.
tbansal@chromium.org
HTTP RTT observation received by the network quality estimator. Recorded
when the request is detected as not hanging because the RTT value was lower
than the minimum threshold RTT needed to be categorized as a hanging
request.
tbansal@chromium.org
HTTP RTT observation received by the network quality estimator. Recorded
when the request is detected as not hanging because it was comparable to the
transport RTT estimate.
tbansal@chromium.org
bengr@chromium.org
Number of RTT observations indexed by the source of the observation.
Recorded by the network quality estimator every time a new observation is
made or synthesized.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the round trip time at the URLRequest layer. Recorded by
the network quality estimator every time the effective connection type is
computed.
tbansal@chromium.org
bengr@chromium.org
RTT observation received or synthesized by network quality estimator.
Observations from different sources are recorded in separate histograms.
Replaced in May 2016 by NQE.MainFrame.RTT.* metrics.
bengr@chromium.org
tbansal@chromium.org
RTT observations at the URLRequest layer made by network quality estimator,
recorded on every request.
tbansal@chromium.org
Count of the requests that were marked as hanging by the heuristic algorithm
in the throughput analyzer in the network quality estimator. A sample is
recorded everytime the heuristic algorithm is run.
tbansal@chromium.org
Count of the requests that were not marked as hanging by the heuristic
algorithm in the throughput analyzer in the network quality estimator. A
sample is recorded everytime the heuristic algorithm is run.
tbansal@chromium.org
Throughput observation made by network quality estimator, and eventually
discarded because the window (over which the througput was computed) was
detected as hanging.
tbansal@chromium.org
Throughput observation made by network quality estimator, and used when the
window (over which the througput was computed) was detected as not hanging.
Deprecated 01/2018.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the transport layer at
different percentiles.
This metric is recorded immediately after a connectivity change is detected.
The metric name is suffixed with the connection type before the connectivity
change was detected. This will miss data from users whose connection type
never changes and will be biased to users whose connection type changes
frequently.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the transport layer.
Recorded by the network quality estimator every time the effective
connection type is computed.
Obsoleted in August 2017.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the estimated HTTP RTT and the observed HTTP
RTT. HTTP RTT estimated by the network quality estimator at the time of
navigation start is compared with the HTTP RTT observed during the specified
time interval following the start of the navigation. Both the estimated and
the observed RTT are computed using average algorithm that assigns equal
weight to all observations.
Obsoleted in August 2017.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the URLRequest layer
computed using average algorithm that assigns equal weight to all
observations.
This metric is recorded on main-frame requests.
Obsoleted in August 2017.
tbansal@chromium.org
bengr@chromium.org
Records the difference between the estimated HTTP RTT and the observed HTTP
RTT. HTTP RTT estimated by the network quality estimator at the time of
navigation start is compared with the HTTP RTT observed during the specified
time interval following the start of the navigation. Both the estimated and
the observed RTT are computed using weighted average algorithm.
Obsoleted in August 2017.
bengr@chromium.org
tbansal@chromium.org
Rough estimate of the computed round trip time at the URLRequest layer
computed using weighted average algorithm.
This metric is recorded on main-frame requests.
Deprecated 04/2016 as doesn't have data nor owner.
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.
knn@chromium.org
This histogram records whether the account ID is actually an email if we
detect an account that has an account ID but not email.
knn@chromium.org
This histogram records the account ID migration status from email to GAIA ID
if we detect an account that has an account ID but not email.
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.
Deprecated 2015-05-22. Replaced by Signin.ListAccountsFailure.
zelidrag@chromium.org
Failure reason of final ListAccounts call failure during Chrome OS login.
This data is now included in Signin.ListAccountsFailure.
Deprecated 2015-05-22. Replaced by Signin.ListAccountsRetry.
zelidrag@chromium.org
Retry reason of failed ListAccounts call during Chrome OS login. This data
is now included in Signin.ListAccountsRetry.
zelidrag@chromium.org
Failure reason of MergeSession call during Chrome OS login, Chrome Signin or
account addition. On all OSes as of M44 (previously CrOS only).
zelidrag@chromium.org
Retry reason of failed MergeSession call during Chrome OS login, Chrome
Signin or account addition. On all OSes as of M44 (previously CrOS only).
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.
Deprecated 2015-05-22
zelidrag@chromium.org
Failure reason of final OAuthLogin (with uber token) call during Chrome OS
login. This data is now (M44+) included in Signin.UberTokenFailure.
Deprecated 2015-05-22
zelidrag@chromium.org
Retry reason of failed OAuthLogin (with uber token) call during Chrome OS
login. This data is now (M44+) included in Signin.UberTokenRetry.
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.
knn@chromium.org
Only applicable on M47 on Android. Measure the frequency of a suppressed
error state when the account is not seeded.
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.
dimich@chromium.org
jianli@chromium.org
Records events related to click through rate (CTR) calculation for Offline
Indicator UI. The CTR can be calculated by computing Clicked/Displayed.
jianli@chromium.org
Number of accesses to the offline page since its creation. This is reported
when the offline page was deleted.
jianli@chromium.org
Logs the UI location from which an offline page was launched.
romax@chromium.org
Counts the number of times an offline page is accessed. Events are reported
per offline pages namespace.
Deprecated 2016-10, and replaced by OfflinePages.AggregatedRequestResult2.
dimich@chromium.org
jianli@chromium.org
Result of servicing requests that may contain offline page.
dimich@chromium.org
jianli@chromium.org
Result of servicing requests that may contain offline page.
Deprecated 2017-10, and replaced by
OfflinePages.ArchiveManager.ArchiveDirsCreationResult2 with suffixes for
temporary and persistent pages.
romax@chromium.org
This is recorded every time the archive directory is being created. It
doesn't include the case which the archive directory exists.
romax@chromium.org
This is recorded every time the archive directory is being created. It
doesn't include the case which the archive directory exists. It has suffixes
indicating results for temporary or persistent archives directories.
chili@chromium.org
The error codes that caused a page load failure.
petewil@chromium.org
Reason for the Chrome Custom Tabs API prerender call to be ignored.
There are several causes for the Chrome Custom Tabs API calls to be ignored,
this tracks the potential causes so we can see how often the prerenderer
doesn't prerender due to these being switched off. Since this is checked
elsewhere (CCTAPI), this only catches the user switching off the third party
cookies or navigation prediction after the CCT API has checked.
petewil@chromium.org
Effective connection type at the start of an offlining attempt for an
attempt that eventually failed.
This metric is recorded for RequestCoordinator::SavePageLater API calls.
dougarnett@chromium.org
Effective connection type when pausing one or more background loads is
requested.
This metric is recorded for RequestCoordinator::PauseRequests API calls.
dougarnett@chromium.org
Effective connection type when removing one or more background loads is
requested.
This metric is recorded for RequestCoordinator::RemoveRequests API calls.
dougarnett@chromium.org
Effective connection type when resuming one or more background loads is
requested.
This metric is recorded for RequestCoordinator::ResumeRequests API calls.
dougarnett@chromium.org
Effective connection type when a background load is requested.
This metric is recorded for RequestCoordinator::SavePageLater API calls.
chili@chromium.org
Status code of background offlining requests at the final step.
dougarnett@chromium.org
Number of queued background load requests available for processing when
processing starts immediately (vs. scheduled). This is for non-svelte
devices (where svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Number of queued background load requests available for processing when
processing starts immediately (vs. scheduled). This is for svelte devices
(where svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Number of queued background load requests unavailable for processing when
processing starts immediately (vs. scheduled). This is for non-svelte
devices (where svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Number of queued background load requests unavailable for processing when
processing starts immediately (vs. scheduled). This is for svelte devices
(where svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Status of attempt to immediately start offlining a page in the background
while application is still concurrently using the foreground. This may be
attempted when an web page download is initially requested or resumed.
chili@chromium.org
The combined http and net error codes that caused a page load failure.
dougarnett@chromium.org
Status code of background offlining (loading and saving) requests.
petewil@chromium.org
Whether any previews were selected for a page we were asked to make
available offline.
dougarnett@chromium.org
Number of started attempts by failed background load requests.
dougarnett@chromium.org
Number of started attempts by successful background load requests.
petewil@chromium.org
True if all requested CSS was loaded when a background page loaded.
petewil@chromium.org
True if all requested images were loaded when a background page loaded.
petewil@chromium.org
True if all requested XHRs were completed when a background page loaded.
chili@chromium.org
Whether the save page result came from chrome custom tabs.
dougarnett@chromium.org
Number of queued background load requests available for processing when
background scheduled processing starts. This is for non-svelte devices
(where svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Number of queued background load requests available for processing when
background scheduled processing starts. This is for svelte devices (where
svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Number of queued background load requests unavailable for processing when
background scheduled processing starts. This is for non-svelte devices
(where svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Number of queued background load requests unavailable for processing when
background scheduled processing starts. This is for svelte devices (where
svelte is determined by base::SysInfo::IsLowEnd()).
dougarnett@chromium.org
Time from background request until it was canceled.
dougarnett@chromium.org
Time from background request until it was successfully saved.
dougarnett@chromium.org
Time from background request until processing it was first started. This is
for non-svelte devices.
dougarnett@chromium.org
Time from background request until processing it was first started on svelte
device. Svelte is determined by base::SysInfo::IsLowEnd().
dougarnett@chromium.org
Connection type when prerenderer reports Unsupported Scheme error.
To give insight about Unsupported Scheme errors that may be due to lost
network connection (as data URL used for rendering an error page will
manifest as an Unsupported Scheme error by the prerenderer).
Deprecated 2/2018. No longer used.
jianli@chromium.org
Number of offline pages that are deleted in a batch.
jianli@chromium.org
Total size, in kilobytes, of all offline pages that are deleted in a batch.
carlosk@chromium.org
fgorski@chromium.org
Can a recent page be saved or not? Logged for all attempts to save
harringtond@chromium.org
Number of thumbnails removed by the thumbnail cleanup task.
Deprecated 3/2016, and replaced by OfflinePages.ClearAllStatus2.
jianli@chromium.org
Status code of wiping out the offline page data.
jianli@chromium.org
Status code of wiping out the offline page data.
Deprecated as of Jan 2018, replaced by
OfflinePages.ClearTemporaryPages.BatchSize.
romax@chromium.org
Number of pages deleted in a batch during one clear-storage request.
Deprecated in Oct 2017 and replaced by OfflinePages.ClearStoragePreRunUsage2
as it was reporting data in bytes instead of the expected MiB.
petewil@chromium.org
The total storage size used by all offline pages from a specific client
namespace.
carlosk@chromium.org
The total disk storage size used by all offline pages from a specific client
namespace.
Deprecated as of Jan 2018, replaced by
OfflinePages.ClearTemporaryPages.Result.
romax@chromium.org
Result of asking storage manager to clear storage.
romax@chromium.org
Number of pages deleted in a batch in one clear storage task.
romax@chromium.org
Result of clearing temporary pages to release storage space.
carlosk@chromium.org
When a temporary page is deleted due to storage pressure, reports the time
since its creation. This metric should be useful to track the occurrence of
"content thrashing", when automatically created temporary pages
are forcing the deletion of recently saved temporary pages.
Deprecated 12/2017, replaced by
OfflinePages.ConsistencyCheck.Temporary.Result and
OfflinePages.ConsistencyCheck.Persistent.Result.
romax@chromium.org
Whether an attempt to delete archive files without metadata was successful.
Deprecated 12/2017, replaced by
OfflinePages.ConsistencyCheck.Temporary.Result and
OfflinePages.ConsistencyCheck.Persistent.Result.
romax@chromium.org
Whether an attempt to delete pages without archives was successful.
Deprecated 11/2016, replaced by
OfflinePages.Consistency.DeletePagesMissingArchiveFileResult.
romax@chromium.org
Whether an attempt to expire pages without archives was successful.
Deprecated 12/2017, replaced by
OfflinePages.ConsistencyCheck.Temporary.PagesMissingDbEntryCount and
OfflinePages.ConsistencyCheck.Persistent.PagesMissingDbEntryCount.
romax@chromium.org
Number of archives without metadata entry when checking consistency.
Deprecated 12/2017, replaced by
OfflinePages.ConsistencyCheck.Temporary.PagesMissingArchiveFileCount and
OfflinePages.ConsistencyCheck.Persistent.PagesMissingArchiveFileCount.
romax@chromium.org
Number of offline pages without archive file when checking consistency.
romax@chromium.org
Number of files which are deleted during legacy dir clearing since they have
no associated DB entry and live in private directory.
romax@chromium.org
Number of DB entries (in persistent namespaces) that have been missing their
files for longer than 365 days, and deleted during maintenance task.
romax@chromium.org
Number of files that are found missing during maintenance task, which is
also the number of DB entries that are updated with valid file missing time.
Deprecated 04/2018, since saving public offline pages to external download
directory needs a different consistency check strategy.
romax@chromium.org
Number of persistent offline pages without archive file when checking
consistency. It will only be reported if the number is larger than 0.
Deprecated 04/2018, since saving public offline pages to external download
directory needs a different consistency check strategy.
romax@chromium.org
Number of archives without database entry when checking persistent page
consistency. It will only be reported if the number is larger than 0.
romax@chromium.org
Number of files that were marked as missing reappeared in the file system,
which is also the number of DB entries that removes file missing time.
romax@chromium.org
Result of persistent page consistency check.
romax@chromium.org
Number of temporary offline pages without archive file when checking
consistency. It will only be reported if the number is larger than 0.
romax@chromium.org
Number of archives without database entry when checking temporary page
consistency. It will only be reported if the number is larger than 0.
romax@chromium.org
Result of temporary page consistency check.
Deprecated as of 12/2017. Replaced by OfflinePages.AccessCount.
jianli@chromium.org
Number of accesses to the offline page since its creation. This is reported
when the offline page was deleted.
Deprecated 2/2018. No longer used, duplicate of
OfflinePages.SavePage.FreeSpaceMB.
jianli@chromium.org
The amount of free space available, in megabytes, on the user's device after
the page is deleted.
Note that before M52 this operation was started before delete operation.
Deprecated as of 5/2016. Marginal applicability.
jianli@chromium.org
The percentage of free space available on the user's device when the page is
being deleted.
Deprecated as of 01/2018. Replaced by OfflinePages.PageAccessInterval.
jianli@chromium.org
Length of time between when an offline page was created and was opened last
time. This is reported when the page was deleted.
Deprecated 2/2018. No longer used, duplicate of OfflinePages.PageSize.
jianli@chromium.org
Size of the offline page, in kilobytes, that was deleted.
Deprecated as of 01/2018. Replaced by OfflinePages.PageAccessInterval.
jianli@chromium.org
Length of time between when an offline page was last opened and was deleted.
Deprecated as of 03/2018. Replaced by similar metric
OfflinePages.StorageInfo.InternalUsagePercentage and
OfflinePages.StorageInfo.ExternalUsagePercentage.
fgorski@chromium.org
jianli@chromium.org
The percentage of space taken by offline pages from the free space that
could be available, if the feature was not present. I.e. considering
situation where the user has: Free Space, Offline content, other apps and
data. This is a percentage of: Offline content / (Offline content + Free
Space).
The value will be recorded after user deletes a single or multiple offline
pages. In case pages are removed in bulk, this value will be reported once.
This value is only reported with deleting, as we are trying to infer if lack
of free space might have caused the user to delete.
romax@chromium.org
Counts the number of times an offline page is deleted. Events are reported
per offline pages namespace.
jianli@chromium.org
Result of removing an offline copy for a page.
Deprecated 2/2018. No longer used.
dewittj@chromium.org
dimich@chromium.org
The number of downloaded pages with the same URL that exist at the time that
we delete a downloaded page.
dewittj@chromium.org
fgorski@chromium.org
If at request time there is another request with the same URL, this tracks
this amount of time between creation of the most recent request and the
current request.
dewittj@chromium.org
fgorski@chromium.org
If at request time there is another downloaded page with the same URL, this
tracks this amount of time between creation of the most recent existing page
and the current request.
Deprecated 2/2018. No longer used.
dewittj@chromium.org
dimich@chromium.org
The number of downloaded pages with the same URL that exist at the time that
we save a downloaded page.
Deprecated 2/2018. No longer used.
dewittj@chromium.org
dimich@chromium.org
If at save time there is another downloaded page with the same URL, this
tracks this amount of time between creation of the most recent existing page
and the current page.
harringtond@chromium.org
Whether or not a thumbnail was provided for a prefetched offline article.
Recorded when the item is shown in Downloads Home.
Deprecated 5/2016. Offline pages no longer depend on bookmarks UI.
dougarnett@chromium.org
Whether a user-edited bookmark URL had a saved offline page.
Deprecated 11/2016. Offline pages no longer use two-step expiration.
romax@chromium.org
Number of pages that are expired in a batch.
Deprecated 11/2016. Offline pages no longer use two-step expiration.
romax@chromium.org
Length of time between when an offline page was created and was expired.
Deprecated 11/2016. Offline pages no longer use two-step expiration.
romax@chromium.org
Result of updating expired page in store.
Deprecated 11/2016. Offline pages no longer use two-step expiration.
romax@chromium.org
Length of time between when an offline page was last opened and was expired.
Deprecated 5/2016. Offline pages no longer depend on bookmarks UI.
fgorski@chromium.org
jianli@chromium.org
Whether user is connected when entering the filter with offline only
content.
Deprecated 5/2016. Offline pages no longer depend on bookmarks UI.
fgorski@chromium.org
jianli@chromium.org
Whether user is connected when leaving the filter with offline only content.
Deprecated 2/2018. Merged to OfflinePages.PageAccessInterval.
jianli@chromium.org
The time elapsed between creation of the offline page and the first time it
was opened.
Deprecated 5/2016. Not longer needed.
jianli@chromium.org
Whether the page that was being saved offline was in incognito mode.
carlosk@chromium.org
Upon starting saving a new last_n offline page snapshot, report if that is
being done for a page that is new (a navigation happened) or for one that
has been previously saved in the same session (no navigation happened). This
metric will assist in determining if there is the need to better track
actual content changes in pages saved more than once by last_n.
Deprecated 5/2016. Offline pages no longer depend on bookmarks UI.
fgorski@chromium.org
jianli@chromium.org
Logs a UI location from which an offline page is launched.
jianli@chromium.org
Status code of loading from the offline pages metadata store.
Deprecated 10/2015, and replaced by OfflinePages.LoadStatus.
jianli@chromium.org
Whether an attempt to load the offline pages metadata store was successful.
Deprecated 2/2018. No longer used.
dewittj@chromium.org
jianli@chromium.org
The amount of time to create the offline pages archive directory.
dewittj@chromium.org
jianli@chromium.org
The amount of time to create the offline pages archive directory and load
the offline page model.
Deprecated 2/2018. No longer used.
dimich@chromium.org
Whether the metadata database was successfully loaded, after possibly
several retries.
Deprecated 2/2018. No longer used.
dimich@chromium.org
The count of attempts spent to open the metadata database. In the best case,
it's 1. There is a small upper limit. This is recorded only at success.
Failures are counted by OfflinePages.Model.FinalLoadSuccessful.
Deprecated 5/2016. This was the dup of OfflinePages.SavedPageCount.
fgorski@chromium.org
jianli@chromium.org
Number of offline pages the user has. Android only.
dimich@chromium.org
Enum-based buckets reflect the number of days the Chrome was used in each
specific way: - Not used at all during whole day. - Started, but failed to
successfully navigate. - Only navigated to offline pages locally saved on
the device. - Only navigated online. - Navigated to both online and offline
pages. This data is accumulated locally and reported when connection is
likely to succeed (usually after successful online navigation).
Deprecated 5/2016. Offline pages no longer depend on bookmarks UI.
jianli@chromium.org
Whether the user was online when a saved page with offline copy was opened.
Deprecated 2/2018. Merged to OfflinePages.PageAccessInterval.
jianli@chromium.org
Length of time between two consecutive opens.
romax@chromium.org
Length of time between accesses to an offline page. This is the same time
period used for expiring temporary pages. This metric is recorded when an
offline page is accessed.
jianli@chromium.org
Length of time between when an offline page was created and was removed.
jianli@chromium.org
Size of the saved copy of an offline page.
carlosk@chromium.org
Records the archive size of an offline page loaded during a navigation that
took place while the device was considered to be offline or with poor
connectivity.
carlosk@chromium.org
Records the archive size of an offline page loaded during a navigation that
took place while the device was considered to be online.
dimich@chromium.org
Whether the Offline Pages Prefetch was effectively enabled during the day.
Determined by a combination of flags and user preferences. Reported at the
same moment as OfflinePages.OfflineUsage.
dewittj@chromium.org
Number of attempts to perform a specific retriable pipeline action for each
finished prefetch item.
Deprecated 9/2017. Replaced by OfflinePages.Prefetching.ActionAttempts
carlosk@chromium.org
Number of attempts to perform a specific retriable pipeline action for each
finished prefetch item.
carlosk@chromium.org
Reports differences between the expected size of a prefetch archive -- as
reported by the service -- and the actual downloaded file size.
carlosk@chromium.org
Actual size of archive file successfully downloaded by offline page
prefetching.
carlosk@chromium.org
Expected size of archive file that started being downloaded by offline page
prefetching.
carlosk@chromium.org
Reports the possible outcomes of an archive download finishing and its
respective prefetch item being updated in the store. Downloads are expected
to succeed or fail but a respective item should always exist and be updated.
The "item not found" cases are exceptions.
Deprecated as of 5/2018. Replaced with
OfflinePages.Prefetching.FetchThumbnail.Complete2.
harringtond@chromium.org
Records the final status of attempts to fetch thumbnails for prefetched
offline pages.
harringtond@chromium.org
carlosk@chromium.org
Records the final status of attempts to fetch thumbnails for prefetched
offline pages. The 1st attempt takes place right after the prefetch item was
sent to the cloud service as part of a request for the creation of its
offline snapshot. The 2nd attempt occurs right after the offline snapshot
was successfully downloaded by the client.
harringtond@chromium.org
Reports each time a thumbnail fetch is attempted.
carlosk@chromium.org
Error code representing the reason why each offline prefetch item was
finalized.
carlosk@chromium.org
The lifetime of an offline prefetch item, from creation until
"zombie-fication" (after metrics collection).
dewittj@chromium.org
Actions taken with respect to the offline prefetch notification, includes
show attempts to calculate CTR.
carlosk@chromium.org
Final result of an attempt to import a prefetched article into the Offline
Pages system.
petewil@chromium.org
Status returned by a request to the Offline Page Service's GetOperation
method.
petewil@chromium.org
Status returned by a request to the Offline Page Service's GetPageBundle
method.
petewil@chromium.org
A prefetch item was seen in this state when starting the background task.
petewil@chromium.org
A prefetch item was found in this state after more than 7 days since its
creation, time enough for it to have been finalized by the pipeline.
dewittj@chromium.org
When receiving suggestions in the prefetch pipeline, emits the number of new
suggestions added to the database. If there is an error, nothing is emitted.
fgorski@chromium.org
Counts when the offline pages prefetch store is opened or closed.
fgorski@chromium.org
Tracks the time between store closing and reopening again within a session.
The store is meant to close itself after a period of inactivity. We are
trying to assess how much time the store is unloaded from memory vs. time it
is loaded and not used. This event will be reported when the store is opened
after being closed within the same lifetime of Chrome.
dimich@chromium.org
Enum-based buckets reflect the number of days the Offline Pages Prefetch was
able to fetch new pages, and/or user was opening those pages. This data is
accumulated locally when fetch operations complete or when prefetched pages
are opened (often happens in background or while offline respectively), and
reported when connection is likely to succeed (usually after successful
online navigation).
petewil@chromium.org
When publishing an archive, we create the download directory if it doesn't
already exist. If we get an error, we record it here.
petewil@chromium.org
When publishing an offline page, the move file step can fail. This returns
the reason for failure as a linux errno.
petewil@chromium.org
When a move file fails for publishing, what caused the failure.
petewil@chromium.org
When publishing an offline page, a page might not be found. This returns
the publishing path that was used (ex: by Guid or by OfflineId).
petewil@chromium.org
Failure attempting to move a file while publishing downloaded page.
Deprecated 8/2016. Use OfflinePages.RequestResult instead.
dimich@chromium.org
Result of automatic redirect to offline version of the page or back. Emitted
exactly once when offline-to-online or online-to-offline redirect is
determined to be needed and conveys the outcome of redirect.
Deprecated 6/2016. Refactored into OfflinePages.RedirectResult.
jianli@chromium.org
Number of times an offline copy was loaded instead when the user is trying
to load the online version of a saved page and there is no network
connection.
Deprecated 6/2016. Refactored into OfflinePages.RedirectResult.
jianli@chromium.org
Number of times an online version was loaded instead when the user is trying
to load the offline copy of a saved page and there is network connection.
connection.
jianli@chromium.org
Records whether the content read from intent URI (file:// or content://)
changed after the initial validation that was done to route the request when
the intent was received. This is recorded at the time that Offline Page
Request Handler tried to read the data, in preparation to show an offline
page to a user.
jianli@chromium.org
Positive net error code for opening the underlying file to serve the offline
page, including net::OK.
jianli@chromium.org
Track whether the range header is provided when an offline page is served.
jianli@chromium.org
Positive net error code for the failure to read the underlying file to serve
the offline page. net::OK is not included.
jianli@chromium.org
Positive net error code for the failure to seek the underlying file to serve
the offline page. net::OK is not included.
Deprecated as of 2/2018. Replaced by OfflinePages.SavedPageCountUponQuery.
jianli@chromium.org
Number of saved pages restored from the offline pages metadata store when it
is logged.
carlosk@chromium.org
Total number of saved offline pages recorded when they are all queried from
the store. This value is more meaningful when filtered by unique users as
that eliminates multiple reports from the same Chrome instance.
Deprecated as of 03/2018. Replaced by similar metric
OfflinePages.StorageInfo.InternalFreeSpaceMB.
jianli@chromium.org
The amount of free space available, in megabytes, on the user's device after
the page is saved.
Note that before M52 this operation was started before save operation.
Deprecated as of 5/2016. Marginal applicability.
jianli@chromium.org
The percentage of free space available on the user's device when the page is
being saved.
dfalcantara@chromium.org
twellington@chromium.org
ianwen@chromium.org
The percentage of the page load completed when the button to save an offline
page is pressed.
romax@chromium.org
Counts the number of times an offline page is saved. Events are reported per
offline pages namespace.
jianli@chromium.org
Result of saving an offline copy for a page.
jianli@chromium.org
The amount of time taken to save an offline copy for a page.
dewittj@chromium.org
Whether a shared page was an offline page or not.
romax@chromium.org
Result of publishing internal page while sharing. CANCELLED means the page
to publish isn't found. ALREADY_EXISTS means the page have already been
published before.
Deprecated 6/2016. Refactored into OfflinePages.RedirectResult.
jianli@chromium.org
Whether an offline page is shown, instead of error page, when the network is
disconnected or poor condition.
dimich@chromium.org
If the directory to store the SQLite database file does not exist, it is
created. This is recorded every time the database is opened, even if the
directory already exists, in which case it's reported as FILE_OK.
fgorski@chromium.org
Used as a counter to track different events related to offline page store
inner working.
fgorski@chromium.org
Tracks the time between store closing and reopening again. The store is
meant to close itself after a period of inactivity. We are trying to assess
how much time the store is unloaded from memory vs. time it is loaded and
not used. This event will be reported when the store is opened after being
closed within the same lifetime of Chrome.
romax@chromium.org
The storage space used by the archive files of offline pages, including all
files in public directory with mhtml/mht extensions. Collected after every
time an offline page is saved successfully.
romax@chromium.org
The amount of free space on the external drive (which contains the public
download directory). Collected after every time an offline page is saved
successfully.
romax@chromium.org
The percentage of storage space on the external volume (that contains public
download directory) used by offline pages archives.
romax@chromium.org
The storage space used by the archive files of offline pages, including the
files in temporary and private directory. Collected after every time an
offline page is saved successfully.
romax@chromium.org
The amount of free space on the internal drive (which contains the app
directory). Collected after every time an offline page is saved
successfully.
romax@chromium.org
The percentage of storage space on internal volume (that contains the app
directory) used by offline pages archives.
carlosk@chromium.org
Tracks the reload of contents of an existing tab that is being restored
either because that tab is being presented for the first time after Chrome
was restarted or because its contents were discarded. All buckets are
mutually exclusive (adding up all reported values amounts to the total
number of tracked tab restores). This metric is focused on last_n offline
pages and is exclusive to Chrome on Android.
Deprecated as of 03/2018. Replaced by similar metric
OfflinePages.StorageInfo.TotalArchiveSize.
fgorski@chromium.org
jianli@chromium.org
Total size of all the offline pages saved by the user.
This value is recorded whenever the number of pages change, meaning after a
page is added or removed. If pages are removed in bulk, this value will be
reported only once.
Deprecated as of 5/2016. Marginal applicability.
fgorski@chromium.org
jianli@chromium.org
Total size of all the offline pages saved by the user as a percentage of
total storage size.
This value is recorded whenever the number of pages change, meaning after a
page is added or removed.
jianli@chromium.org
The trust state of the offline page. This is recorded when an offline page
is being opened.
petewil@chromium.org
jianli@chromium.org
Percentage of battery remaining when the offline page background loading
task wakes up to check for work.
petewil@chromium.org
jianli@chromium.org
Whether the device is plugged in when the offline page background load task
wakes up to check or work.
petewil@chromium.org
jianli@chromium.org
Time delay from a dinosaur page to connection being available.
petewil@chromium.org
jianli@chromium.org
Which network is available (if any) when the offling page background loading
task wakes up to check for work.
fgorski@chromium.org
Indicates whether the browser was connected when Open online button was
clicked on Page Info popup, which causes a reload of an offline page to
online version.
fgorski@chromium.org
Indicates whether Open online was visible in Page Info popup, when it was
shown for an offline page. (The button is visible only when Chrome is
connected when the Page Info popup is opened for offline page.)
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
When a page is loaded in offline mode, the percentage of resources on that
page that were successfully loaded.
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.
jdonnelly@chromium.org
The number of times each omnibox suggestion answer type (e.g., weather,
sports score) was received and parsed successfully. Can be normalized with
the count of emits to Omnibox.SuggestRequest.Success.GoogleResponseTime,
which counts all successful suggest responses from Google, not just those
with answers attached. Note that GoogleResponseTime is technically off given
that it will still count cases where we fail to extract, deserialize, or
parse the response. But these cases are rare to non-existent.
asvitkine@chromium.org
mpearson@chromium.org
Records the time taken between a keystroke being typed in the omnibox and
the text being painted. If there are multiple keystrokes before a paint,
logs the time since the earliest one.
This duration is composed of three parts:
a) the time spent processing the initial input event
b) the time spent for the repaint task to be scheduled on the message loop
c) the time spent painting the Omnibox
d) (on views platforms) the time until the pixels are actually composited
There's a number of breakdown metrics to help diagnose a regression. First,
Omnibox.CharTypedToRepaintLatency.ToPaint measures the combined time of (a)
and (b). Omnibox.QueryTime2 is a good proxy for just (a). And there's also
Omnibox.PaintTime that corresponds to (c). We don't have a direct metric for
(d), but if neither Omnibox.CharTypedToRepaintLatency.ToPaint nor
Omnibox.PaintTime regressed, then the regression must be in (d).
It's also possible to get insight into (b) via the UMA Task Profiler
dashboard by looking at "average queue time" of the task
DisplayScheduler::ScheduleBeginFrameDeadline.
Note: The semantics of this metric on views platforms changed in M62, as
previously time (d) was not included in the metric.
This became the new implementation of Omnibox.CharTypedToRepaintLatency as
of 08/2017.
asvitkine@chromium.org
mpearson@chromium.org
A refinement of the Omnibox.CharTypedToRepaintLatency metric that attempts
to more accurately track the latency by measuring until the point when the
compositor has actually put pixels on the screen. In particular, this will
capture the time used to also paint the Omnibox result views as a result of
the character insertion, which is not covered by
Omnibox.CharTypedToRepaintLatency. If there are multiple keystrokes before a
paint, logs the time since the earliest one.
asvitkine@chromium.org
mpearson@chromium.org
Records the time taken between a keystroke being typed in the omnibox and
the time when we're ready to paint the omnibox. This is a breakdown
diagnostic metric for Omnibox.CharTypedToRepaintLatency, to help diagnose
regressions in that metric. See that metric's description for more info.
mpearson@chromium.org
Recorded every time the omnibox is focussed and a recent URL from the user's
clipboard is suggested. The value indicates the estimated age of the
clipboard. (If Chrome observed the clipboard modification, this age is
exact. If Chrome did not observe the modification, then it's a conservative
estimate: the last time Chrome observed a clipboard modification, which is
certainly older than the current clipboard. If Chrome never observed a
clipboard modification, no clipboard suggestion is shown, meaning this
histogram will never be emitted to.)
Intended to be compared with MobileOmnibox.PressedClipboardSuggestionAge.
mpearson@chromium.org
Recorded every time the omnibox is focussed and a recent URL from the user's
clipboard is suggested. The number emitted is the number of times the URL
has been suggested within the same session including the current time. Thus,
the third time it is shown, we'll emit a three to this histogram, and this
histogram will have previously seen emits of one and two. If the clipboard
content was the same during a previous run of Chrome and this URL was
suggested during that run, those impressions are not counted. Also, if the
clipboard content changes during a particular run of Chrome to another URL,
the omnibox is focused and that URL is suggested, then content changes back
and Chrome starts suggesting the older URL again, the counts start again
from scratch. Chrome only remembers the number of times the URL was shown
consecutively.
This value is useful to compare with the number of times a clipboard
suggestion has been shown when it is clicked. This value can be obtained
from OmniboxEvent records in which the selected suggestion is from Clipboard
provider. In those cases, look in the Clipboard provider's ProviderInfo
field for |times_returned_results_in_session|. Note that at the time of
this writing that OmniboxEvent logs aren't recorded in incognito whereas
histograms are. Thus, the total counts will not be comparable, though the
distributions should be.
mpearson@chromium.org
Recorded every time the omnibox is focussed and a recent URL from the user's
clipboard is suggested. The value indicates whether the current URL was
shown (which would appear above the clipboard URL suggestion) or was absent
(which ought to only happen when the omnibox is empty / the user is on the
NTP).
On Android, the total count for this histogram can be usefully compared with
the count of the user action FocusLocation in order to determine the rate at
which a clipboard URL suggestion is shown in the omnibox. To determine the
same rate on iOS, one needs to compare this histogram's count with the sum
of the user actions MobileFocusedOmniboxOnNtp, MobileFocusedFakeboxOnNtp,
and MobileFocusedOmniboxNotOnNtp.
Furthermore, on either platform, this histogram's count can be usefully
compared with the count in the clipboard bucket of the
Omnibox.SuggestionUsed.Provider histogram to determine the clickthrough rate
on these suggestions.
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).
skare@chromium.org
Counts the number of document suggest requests the omnibox sent, were
invalidated, and were completed successfully.
skare@chromium.org
Number of results returned in each document suggestion reply. Logged for
successful requests where the provider returned a parseable result set.
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.
Replaced with Omnibox.FocusToOpenTimeAnyPopupState in April 2014.
mpearson@chromium.org
The length of time between when a user focused on the omnibox and opened an
omnibox match (which could be what they typed or a suggestion).
Replaced with Omnibox.FocusToOpenTimeAnyPopupState2 in August, 2016.
mpearson@chromium.org
The length of time between when a user focused on the omnibox and opened an
omnibox match (which could be what they typed or a suggestion). This is
recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open.
Replaced with Omnibox.FocusToOpenTimeAnyPopupState3 in January, 2017, which
only differs in the bucketing and range.
mpearson@chromium.org
The length of time between when a user focused on the omnibox and opened an
omnibox match (which could be what they typed or a suggestion). This is
recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open.
It is not recorded if a match is opened without triggering a focus event,
e.g., when a user drags a URL to the omnibox to navigate.
To know how common this last condition is, compare the total count of this
histogram to the total number of omnibox events.
mpearson@chromium.org
The length of time between when a user focused on the omnibox and opened an
omnibox match (which could be what they typed or a suggestion). This is
recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open.
It is not recorded if a match is opened without triggering a focus event,
e.g., when a user drags a URL to the omnibox to navigate.
To know how common this last condition is, compare the total count of this
histogram to the total number of omnibox events.
lpromero@chromium.org
iOS: Records whether a hardware keyboard is used to input text. This is
recorded each time a UIKeyboardWillChangeFrameNotification is sent while
editing the omnibox text.
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
Times URLIndexPrivateData::HistoryIDSetFromWords(), which is called by the
omnibox's HistoryQuick provider.
URLIndexPrivateData::HistoryIDSetFromWords() can be called multiple times
per keystroke due to, for example, the cursor being in the middle of the
input string or SearchProvider's calls to Classify().
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.
asvitkine@chromium.org
mpearson@chromium.org
Records the time to paint the omnibox contents. This is a subcomponent of
Omnibox.CharTypedToRepaintLatency. Implemented on desktop platforms.
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.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Records a boolean value indicating whether the Physical Web provider was
invoked by focusing the omnibox during the current omnibox session. This is
unexpected; it's probably a bug somwhere. Recorded when the user selects an
omnibox suggestion. Does not record when the Physical Web omnibox provider
is disabled.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
The number of matches returned by PhysicalWebProvider. Emitted when the
omnibox is first focused, unless the user is in incognito mode. Capped at
10.
Obsolete 05/16/2017. Data is unused (crbug.com/719801).
kkimlabs@chromium.org
The number of progress bar break point updates from page load started to
page load finished.
Obsolete 05/16/2017. Data is unused (crbug.com/719801).
kkimlabs@chromium.org
The number of progress bar frame updates from page load started to page load
finished. If there is no animation, this matches
Omnibox.ProgressBarBreakPointUpdateCount. Note that there can be additional
updates after page load finished, animating to 100%, but this histogram
doesn't include them.
Deprecated 2015-06-12. Replaced by Omnibox.ProviderTime2.
mpearson@chromium.org
The length of time taken by the named provider"s synchronous pass.
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.
stkhapugin@chromium.org
The elapsed time to acquire the location sent in the X-Geo header for an
Omnibox query.
stkhapugin@chromium.org
The estimated horizontal accuracy of the location sent in the X-Geo header
for an Omnibox query.
kiyun@chromium.org
For iOS, whether the application is authorized to use location services when
the user enters a search query into the Omnibox.
Deprecated 2015-06-12. Replaced by Omnibox.QueryTime2.
mpearson@chromium.org
Time it takes for the omnibox to become responsive to user input after the
user has typed N characters. This measures the time it takes to start all
the asynchronous autocomplete providers (but not wait for them to finish).
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
autocomplete providers (but not wait for the asynchronous ones 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
Time it takes for the omnibox to search the previous query history database
for queries that start with the omnibox text.
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.
Deprecated in M58, replaced with
Omnibox.SuggestionUsed.NearbyURLCount.AtFocus and
Omnibox.SuggestionUsed.NearbyURLCount.AtMatchCreation.
The number of nearby Physical Web URLs when the user focused the omnibox.
Recorded when the user accepts an omnibox suggestion, regardless of whether
the suggestion came from PhysicalWebProvider. Capped at 50.
In M57, the values recorded by this histogram were determined to be bugged.
It's believed that it was recording uninitialized values due to a corner
case on Android that allows an omnibox suggestion to be selected without
first focusing the omnibox. In addition to the new histograms,
Omnibox.PhysicalWebProvider.SuggestionUsedWithoutOmniboxFocus was added to
detect this case. https://crbug.com/691059
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
The number of nearby Physical Web URLs when Physical Web Provider was last
focused (i.e., the start of the current session). Recorded when the user
accepts an omnibox suggestion, regardless of whether the suggestion came
from PhysicalWebProvider. Capped at 50.
Does not record if the omnibox was not focused during the current session.
Omnibox.PhysicalWebProvider.SuggestionUsedWithoutOmniboxFocus records true
when we hit this case.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
The number of nearby Physical Web URLs when Physical Web Provider last
constructed matches. Recorded when the user accepts an omnibox suggestion,
regardless of whether the suggestion came from PhysicalWebProvider. Capped
at 50.
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 of the suggestion the user selected when the user used the
omnibox to go somewhere, only for omnibox interactions that start in the
specified page context:
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 provider and result type of the suggestion the user selected when the
user used the omnibox to go somewhere, only for omnibox interactions that
start in the specified page context:
lpy@chromium.org
mpearson@chromium.org
Measures the time from the page first appearing in the foreground to its
first meaningful paint. Only recorded on navigations that use a prerender
that is to a search query suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from navigation start to first meaningful paint. Only
recorded for a search query suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from the page first appearing in the foreground to its
first contentful paint. Only recorded on navigations that use a prerender
that is to a search query suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from navigation start to first contentful paint. Only
recorded for a search query suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from a page being navigated to in prerender to it first
showing up in foreground. Only recorded on navigations that used a prerender
that was to a search query suggestion selected from the omnibox. This is
only recorded on pages that experience a first contentful paint.
mpearson@google.com
The rough type of the suggestion the user selected when the user used the
omnibox to go somewhere.
mpearson@google.com
The rough type of the suggestion the user selected when the user used the
omnibox to go somewhere, only for omnibox interactions that start in the
specified page context:
lpy@chromium.org
mpearson@chromium.org
Measures the time from the page first appearing in the foreground to its
first meaningful paint. Only recorded on navigations that use a prerender
that is to a URL suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from navigation start to first meaningful paint. Only
recorded for a URL suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from the page first appearing in the foreground to its
first contentful paint. Only recorded on navigations that use a prerender
that is to a URL suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from navigation start to first contentful paint. Only
recorded for a URL suggestion selected from the omnibox.
lpy@chromium.org
mpearson@chromium.org
Measures the time from a page being navigated to in prerender to it first
showing up in foreground. Only recorded on navigations that used a prerender
that was to a URL suggestion selected from the omnibox. This is only
recorded on pages that experience a first contentful paint.
mpearson@chromium.org
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 they used the
omnibox to go somewhere. Switched on March 27 2018 from an bucketing where
every typed length is emitted exactly (up to 500) to ordinary exponential
bucketing.
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.
mpearson@chromium.org
The scheme of the destination URL for the selected omnibox suggestion. This
could be a what-you-typed suggestion (if the user fully typed a URL), an
inline autocompletion, or something in the dropdown, anything as long as
it's a URL navigation, not a search query. Excludes omnibox URL navigations
that are effectively reloads as well as cut-and-pastes of URLs. Also does
not take into account any redirects that destination URL may do before
finally serving a page. In other words, it's the scheme of the first request
in a possible chain.
cthomp@chromium.org
The amount of time, in milliseconds, between the start of a typed URL
navigation in the omnibox (the user typing a URL to completion, or selecting
a URL from the inline autocomplete or dropdown) and the start of a redirect
upgrading the URL to HTTPS. This is only recorded when the upgraded URL is
the same except for the scheme and the addition/removal of a
"www." prefix.
To calculate the percentage of HTTP URL navigations that have been upgraded
in this way, divide the count of this histogram by the count for HTTP in
Omnibox.URLNavigationScheme.
kenjibaheux@chromium.org
mpearson@chromium.org
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()).
mpearson@chromium.org
Whether the user has settings configured so that the current page URL can be
sent to the suggest server to request contextual suggestions. For example,
this is only supported for users who have Google as their default search
engine (unmodified version of Google), have search suggest enabled, are
signed-in and syncing without a custom passphrase, and don't have an
incognito window open. There are other criteria too. Recorded on focus in
the omnibox if there is default search provider and we've constructed a
suggest URL.
Some additional guidelines: if an incognito window is open, all focus events
will go into the "generally ineligible" bucket. Likewise, if the
current page is a search results page, we don't allow contextual suggestions
either so focus events on those pages go in the "generally
ineligible" bucket. The difference between "eligible" and
"generally eligible but not this time" depends only the properties
of the current URL.
Recorded regardless of whether contextual or non-contextual zero suggest is
currently enabled on the user's platform. However, if zero suggest (in all
forms) is entirely disabled, the user will be perpetually ineligible.
mpearson@chromium.org
Whether the user has settings configured so that the current page URL could
be sent to the suggest server to request contextual suggestions. For
example, this is only supported for users who have Google as their default
search engine (unmodified version of Google), have search suggest enabled,
and are signed-in and syncing without a custom passphrase. There are other
criteria too. Recorded on profile open. Note that opening an incognito
window (if none are currently open under the given profile) counts as
opening a new profile.
Some additional guidelines: unlike Omnibox.ZeroSuggest.Eligible.OnFocus,
because this is recorded on profile open, users cannot be declared
ineligible because they have an incognito window open (it's impossible to
have an incognito window open for a given profile at the time of profile
open) and also cannot be declared ineligible because the user is viewing a
search results page. (We test this on-profile-open using an arbitrary URL.)
Recorded regardless of whether contextual or non-contextual zero suggest is
currently enabled on the user's platform. However, if zero suggest (in all
forms) is entirely disabled, the user will be perpetually ineligible.
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.
achuith@chromium.org
Time spent on error screens during enrollment or autoenrollment.
achuith@chromium.org
Time spent on error screens during signin.
achuith@chromium.org
Time spent on error screens during supervised user creation.
achuith@chromium.org
Time spent on error screens during update.
achuith@google.com
Number of times error screen has appeared during enrollment or
autoenrollment.
achuith@google.com
Number of times error screen has appeared during signin.
achuith@google.com
Number of times error screen has appeared during supervised user creation.
achuith@google.com
Number of times error screen has appeared during update.
merkulova@chromium.org
Time spent on specific OOBE screen.
dougarnett@chromium.org
sophiechang@chromium.org
Whether processing the hints succeeded or failed at a particular step.
Recorded when the OptimizationGuideService receives a notification to
process hints.
Deprecated with CL 731423002. OriginChip has been removed.
gbillock@chromium.org
The number of clicks on the origin chip.
Obsolete as of Chrome 54. Sort of replaced by OriginTrials.ValidationResult.
chasej@chromium.org
iclelland@chromium.org
Counts the results of origin trial checks to enable experimental features.
The result for each feature check is counted at most once per execution
context (e.g. page, worker).
Obsolete as of Chrome 54.
chasej@chromium.org
iclelland@chromium.org
Counts how often an error message is generated for each origin trial check
to enable an experimental feature.
chasej@chromium.org
iclelland@chromium.org
Counts the results of token validation checks to enable experimental
features. The result for each token validation check is counted once per
token per execution context (e.g. page, worker).
erikchen@chromium.org
The availability and capabilities of the Bluetooth driver on OSX devices.
This metric is logged on startup.
Obsolete as of Chrome 43. See OmahaProxy for more relevant statistics.
mark@chromium.org
The cat's flavor and how many bits there are in it.
mark@chromium.org
Events seen by the OSX NSException swizzle.
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.
spqchan@chromium.org
This event is recorded each time a user triggers fullscreen for a browser
window. It indicates if the fullscreen is triggered for the browser or the
tab content.
erikchen@chromium.org
This event is recorded each time a user triggers fullscreen for a browser
window. It indicates the mechanism (immersive vs. AppKit) and the type of
AppKit Fullscreen (Presentation Mode vs. Canonical Fullscreen).
erikchen@chromium.org
This event is recorded each time a user triggers fullscreen for a browser
window. It indicates the screen in which the window was fullscreened, and
the number of screens available.
spqchan@chromium.org
This event is recorded each time a user triggers fullscreen and when the
fullscreen toolbar is updated with a new style.
erikchen@chromium.org
This event is recorded each time a Handoff is received by Chrome on OSX. The
enumeration indicates the source of the Handoff.
kerrnel@chromium.org
mark@chromium.org
The number of previous times that the keychain reauthorization did not
complete, when run during the main browser launch.
kerrnel@chromium.org
mark@chromium.org
The number of previous times that the keychain reauthorization did not
complete, when run at update time.
kerrnel@chromium.org
mark@chromium.org
How many times the keychain reauthorization ran before finally succeeding,
when run at update time.
kerrnel@chromium.org
mark@chromium.org
How many times the keychain reauthorization ran before finally succeeding,
when run during the main browser launch.
lgrey@chromium.org
Whether the user successfully shared via a native sharing extensions after
selecting it from the share menu. False can indicate failure or
user-initiated cancellation.
Deprecated as of 11/2015.
erikchen@chromium.org
This event records the amount of time that the browser process main thread
blocks, waiting for a frame with the right dimensions to arrive from the gpu
process.
erikchen@chromium.org
The configuration of the setting "Screens Have Separate Spaces"
available in OSX 10.9+.
Deprecated as of Chrome 51 since Mach has become the default mechanism.
erikchen@chromium.org
A histogram entry is emitted each time a base::SharedMemory object is
constructed. The value of the entry indicates the mechanism used to back the
shared memory region.
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.
erikchen@chromium.org
One metric is emitted every 24-hours after Chrome is launched for every
process that is being profiled. The timer is reset if Chrome exits.
erikchen@chromium.org
One metric is emitted every 24-hours after Chrome is launched for every
Chrome instance that is using out of process heap profiling. The timer is
reset if Chrome exits.
erikchen@chromium.org
The metric is emitted each time Chrome attempts to record a memory-infra
trace to upload an out-of-process heap-profiling memory dump.
erikchen@chromium.org
The metric is emitted each time Chrome uploads a trace. It reflects the
uncompressed size of the trace.
erikchen@chromium.org
The metric is emitted each time Chrome uploads a trace. It reflects whether
the upload was successful.
Deprecated as of Chrome 59 in favour of Overscroll.Cancelled3.
rbyers@chromium.org
mfomitchev@chromium.org
Overscroll gestures that were aborted before they were completed.
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).
Deprecated as of Chrome 44 to switch to NavigationDirection enum.
rbyers@chromium.org
mfomitchev@chromium.org
Navigations that were triggered due to completed overscroll gesture. Note
that not all completed overscroll gestures trigger a navigation.
Deprecated as of Chrome 59 in favour of Overscroll.Navigated3.
rbyers@chromium.org
mfomitchev@chromium.org
Navigations that were triggered due to completed overscroll gesture. Note
that not all completed overscroll gestures trigger a navigation.
mfomitchev@chromium.org
Navigations that were triggered due to completed overscroll gesture. Note
that not all completed overscroll gestures trigger a navigation.
Deprecated as of Chrome 44 to switch to NavigationDirection enum.
rbyers@chromium.org
mfomitchev@chromium.org
Overscroll gestures initiated by the user. Note that not all overcroll
gestures started are completed (e.g. the overscroll gesture is aborted if
user clicks or presses a key during the gesture).
Deprecated as of Chrome 59 in favour of Overscroll.Started3.
rbyers@chromium.org
mfomitchev@chromium.org
Overscroll gestures initiated by the user. Note that not all overscroll
gestures started are completed (e.g. the overscroll gesture is aborted if
user clicks or presses a key during the gesture).
mfomitchev@chromium.org
Overscroll gestures initiated by the user. Note that not all overscroll
gestures started are completed (e.g. the overscroll gesture is aborted if
user clicks or presses a key during the gesture).
pkotwicz@google.com
The squared distance between taps which occur in quick succession. Only
reported when the taps are far apart and touch noise filtering is enabled.
pkotwicz@google.com
The horizontal distance from a "touch press" to the closest other
touch. Only reported if there are two or more fingers onscreen and touch
noise filtering is enabled.
pkotwicz@google.com
The amount of time between noisy touches. The amount of time since Chrome
startup is recorded for the first noisy touch after startup.
pkotwicz@google.com
The time between taps which occur in quick succession at the same screen
location. Only reported when touch noise filtering is enabled.
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.
kouhei@chromium.org
Number of pages that had any HTML form interaction before next page load.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
bmcquade@chromium.org
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted due to being backgrounded.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a client side redirect (Javascript navigation).
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by the user closing the tab or browser.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a forward or back navigation.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a new navigation.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted. The abort cause is unknown.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a reload.
Deprecated in favor of PageLoad.Experimental.AbortTiming equivalent.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by the user pressing stop.
We now have sufficient infrastructure to always characterize aborts that
resulted in new navigations.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a navigation with unknown transition type.
jkarlin@chromium.org
The size (in KB) of the resources loaded for all of the ad frames on the
page that loaded over the network.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The percentage of bytes loaded for all ad frames that were loaded over the
network.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The size (in KB) of the resources loaded for all of the ad frames on the
page.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The size (in KB) of the resources loaded for an ad frame from the network.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The percentage of bytes loaded for a single ad frame that were loaded over
the network.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The size (in KB) of the resources loaded for an ad frame.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The size (in KB) of all of the page's resources that loaded over the
network.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes.
jkarlin@chromium.org
The percentage of bytes loaded for the page (from the network) that came
from resource loads in ad frames (from the network).
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The size (in KB) of all of the page's resources.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes.
jkarlin@chromium.org
The percentage of bytes loaded for the page that came from resource loads in
ad frames.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
jkarlin@chromium.org
The size (in KB) of all of the page's resources except for those loaded in
ad frames.
Only recorded if the page has at least one identified ad frame. Bytes are
measured as over-the-wire (e.g., compressed) response body KBs and do not
include header bytes. An ad frame consists of the identified ad frame and
all of its children (which may also be ads, but are counted as part of the
ancestor ad frame).
Deprecated In July 2018, metric was buggy for subresource filter ads.
jkarlin@chromium.org
When a frame that is (or previously was) an ad frame renavigates, record
whether it renavigated to an ad frame or a non-ad frame.
An ad frame consists of the identified ad frame and all of its children. Its
children (which may also be ads) are not counted when they renavigate.
This metric is recorded as the event happens. Note that this is unlike most
other Clients.Ads metrics, which are recorded when the page load is
complete.
Deprecated In July 2018.
jkarlin@chromium.org
When a frame that has never been part of an ad frame renavigates, record
whether it renavigated to an ad frame or a non-ad frame.
This metric is recorded as the event happens. Note that this is unlike most
other Clients.Ads metrics, which are recorded when the page load is
complete.
jkarlin@chromium.org
Records whether or not a parent frame is found for a subframe that finishes
navigating.
jkarlin@chromium.org
Records the content::ResourceType when a resource finishes loading but the
ads metrics aren't aware of a committed frame for the resource.
Deprecated In May 2017.
jkarlin@chromium.org
The number of frames (with parent frame of main frame) that are on the page
identified as Google Ad Frames.
Only recorded if the page has at least one identified ad frame. Child frames
of an ad frame are not included in the count.
Deprecated In May 2017.
jkarlin@chromium.org
The percentage of frames (with parent frame of main frame) on the page that
are identified as Google Ad Frames.
Only recorded if the page has at least one identified ad frame. An ad frame
consists of the identified ad frame and all of its children (which may also
be ads, but are counted as part of the ancestor ad frame).
Deprecated In May 2017.
jkarlin@chromium.org
The number of frames (with parent frame of main frame) on the page.
Only recorded if the page has at least one identified ad frame.
Deprecated In July 2017. Use
PageLoad.Clients.Ads.All.Navigations.AdFrameRenavigatedToAd instead.
jkarlin@chromium.org
When a frame that is (or previously was) an ad frame renavigates, record
whether it renavigated to an ad frame or a non-ad frame.
An ad frame consists of the identified ad frame and all of its children. Its
children (which may also be ads) are not counted when they renavigate.
This metric is recorded as the event happens. Note that this is unlike most
other Clients.Ads metrics, which are recorded when the page load is
complete.
Deprecated In July 2017. Use
PageLoad.Clients.Ads.All.Navigations.NonAdFrameRenavigatedToAd instead.
jkarlin@chromium.org
When a frame that has never been part of an ad frame renavigates, record
whether it renavigated to an ad frame or a non-ad frame.
This metric is recorded as the event happens. Note that this is unlike most
other Clients.Ads metrics, which are recorded when the page load is
complete.
Deprecated In July 2017. Use
PageLoad.Clients.Ads.All.ParentExistsForSubFrame instead.
jkarlin@chromium.org
Records whether or not a parent frame is found for a subframe that finishes
navigating.
Deprecated In July 2017. Use
PageLoad.Clients.Ads.All.ResourceTypeWhenNoFrameFound instead.
jkarlin@chromium.org
Records the content::ResourceType when a resource finishes loading but the
ads metrics aren't aware of a committed frame for the resource.
bmcquade@chromium.org
Count of same document page views for AMP pages.
bengr@chromium.org
ryansturm@chromium.org
100 times the ratio of network bytes received to network bytes the user
would have seen without data reduction proxy (not including headers) in a
page load that had its main resource loaded through data reduction proxy.
Recorded as a percent if the data reduction proxy saved the user data.
Recorded per page load when the user navigates away, hides the tab, or
backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The number of network kilobytes (not including headers) that the data
reduction proxy inflated for the user in a page load that had its main
resource was loaded through data reduction proxy. Recorded per page load
when the user navigates away, hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The inflation in network kilobytes (not including headers) the user saw due
to using data reduction proxy in a page load that had its main resource was
loaded through data reduction proxy. Recorded as a percent when the user saw
inflated data. Recorded per page load when the user navigates away, hides
the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The number of network kilobytes that were not fetched through the data
reduction proxy (not including headers) in a page load that had its main
resource was loaded through data reduction proxy. Recorded per page load
when the user navigates away, hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The number of network kilobytes (not including headers) that the user would
have seen without using data reduction proxy in a page load that had its
main resource was loaded through data reduction proxy. Recorded per page
load when the user navigates away, hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The percent of network kilobytes (not including headers) in a page load that
went through data reduction proxy when the main resource was loaded through
data reduction proxy. Recorded per page load when the user navigates away,
hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The number of network kilobytes that were fetched through the data reduction
proxy (not including headers) in a page load that had its main resource was
loaded through data reduction proxy. Recorded per page load when the user
navigates away, hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The number of network kilobytes (not including headers) that the data
reduction proxy saved the user in a page load that had its main resource was
loaded through data reduction proxy. Recorded per page load when the user
navigates away, hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The percent of completed resources loaded from network in a page load that
use data reduction proxy when the main resource was loaded through data
reduction proxy. Recorded per page load when the user navigates away, hides
the tab, or backgrounds the app.
Deprecated March 2018
bmcquade@chromium.org
The actual delay added to page loads by DelayNavigationThrottle, for page
loads that started in the foreground and reached first paint in the
foreground.
Deprecated March 2018
bmcquade@chromium.org
The absolute delta between the specified and actual delays added to main
frame navigations by DelayNavigationThrottle, for page loads that started in
the foreground and reached first paint in the foreground.
Deprecated March 2018
bmcquade@chromium.org
The specified delay added to main frame navigations by
DelayNavigationThrottle, for page loads that started in the foreground and
reached first paint in the foreground.
bmcquade@chromium.org
Counts the number of pages where a script loaded via document.write could
have been blocked.
shivanisha@chromium.org
bmcquade@chromium.org
jkarlin@chromium.org
This metric measures the counts of pages for various loading behaviors of
document.written scripts.
shivanisha@chromium.org
bmcquade@chromium.org
This metric measures reloads in pages that have synchronous, cross-origin
document.written scripts that could be blocked if document.write script
blocking feature is enabled.
Deprecated May 2018
mdw@chromium.org
Events related to Google CAPTCHA pages being seen by users.
bengr@chromium.org
ryansturm@chromium.org
The number of network kilobytes (not including headers) that LoFi resources
used in a page load that had at least one LoFi resource. Recorded per page
load when the user navigates away, hides the tab, or backgrounds the app.
bengr@chromium.org
ryansturm@chromium.org
The number of network LoFi resources in a page load that had at least one
LoFi resource. Recorded per page load when the user navigates away, hides
the tab, or backgrounds the app.
ksakamoto@chromium.org
Records the number of tabs with inflight loading activities. Recorded when a
new page load starts.
Deprecated June 2018 (M69) in favor of
PageLoad.Clients.ServiceWorker2.PageTransition.
falken@chromium.org
The core transition type for main frame page loads controlled by a service
worker.
falken@chromium.org
The core transition type for main frame page loads controlled by a service
worker that has a fetch event handler.
Deprecated May 2018 (M68) in favor of
SubresourceFilter.PageLoad.ActivationDecision
bmcquade@chromium.org
Records the policy decision to activate subresource filtering for a page
load. 'Activated' indicates that subresource filtering was activated. All
other reasons indicate that subresource filtering was not activated. Page
loads where subresource filtering was activated ('Activated') and at least
one subresource matched the subresource filter are counted in
PageLoad.Clients.SubresourceFilter.Count.
Deprecated May 2018 (M68) in favor of
SubresourceFilter.PageLoad.NumSubresourceLoads.MatchedRules (e.g. by looking
at 0 and non-zero buckets).
bmcquade@chromium.org
Records 'true' for page loads where the subresource filter matched a
subresource loaded by the page. Includes dryrun matches. To compute the
percentage of total page loads affected by subresource filtering, divide by
the sum of counts for (PageLoad.ParseTiming.NavigationToParseStart +
PageLoad.ParseTiming.NavigationToParseStart.Background).
Deprecated in May 2018 (M69).
csharrison@chromium.org
The time spent parsing author style sheets before the first contentful
paint.
Deprecated in May 2018 (M69).
csharrison@chromium.org
The sum of CSSTiming.Update and CSSTiming.Parse variants for this page load.
Deprecated in May 2018 (M69).
csharrison@chromium.org
The time spent in Document::updateStyle before the first contentful paint.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
DOMContentLoaded event is fired, for main frame documents.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
first layout is performed, for main frame documents.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
load event is fired, for main frame documents.
deprecated in favor of PageLoad.Events.*
csharrison@chromium.org
bmcquade@chromium.org
Captures counts of various page load events. These are enumerated in the
enum page_load_metrics::PageLoadEvent, and include events like 'page load
aborted before first layout'
Deprecated in favor of PageLoad.Timing2.NavigationToCommit and
PageLoad.AbortTiming.
csharrison@chromium.org
bmcquade@chromium.org
Captures counts of load events post-commit, on relevant page loads (i.e.
http/https, not same-page, not an error page). These events include aborts
before first layout and successful first layouts. Note that the event
'Committed load started' when segmented by background/foreground specifies
whether the eventually committed load started in the background or
foreground, not whether we backgrounded before the actual commit event. This
is because we don't have all the data to filter relevant page loads on
provisional loads.
Deprecated in favor of PageLoad.Internal.ErrorCode.
csharrison@chromium.org
bmcquade@chromium.org
Counts of various internal error conditions in the page_load_metrics system.
Deprecated Feb 2016 in favor of PageLoad.AbortTiming and
PageLoad.Timing2.NavigationToFailedProvisionalLoad. Note that the
corresponding background enumerations are no longer being tracked in the
timing histograms.
csharrison@chromium.org
bmcquade@chromium.org
Captures counts of provisional load events. These include aborted, failed,
and successful (committed) provisional loads.
bmcquade@chromium.org
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted due to being backgrounded.
Deprecated in favor of PageLoad.Internal.ClientRedirect.*.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a client side redirect (Javascript navigation).
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by the user closing the tab or browser.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a forward or back navigation.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a new navigation.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted. The abort cause is unknown.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by a reload.
csharrison@chromium.org
This metric is still experimental and not yet ready to be relied upon.
Measures the time from navigation start to the time the page load was
aborted by the user pressing stop.
jkarlin@chromium.org
The number of prefiltered (e.g., compressed) KiloBytes loaded from the cache
via the browser process for a page load. Recorded when the page load is
terminated.
jkarlin@chromium.org
The number of prefiltered (e.g., compressed) KiloBytes loaded over the
network via the browser process for a page load. Recorded when the page load
is terminated.
jkarlin@chromium.org
The number of prefiltered (e.g., compressed) KiloBytes loaded via the
browser process for a page load. Recorded when the page load is terminated.
Removed Jan 2018
csharrison@chromium.org
The percent of resources loaded from cache for the given page load. Recorded
at the end of HTML parsing.
Removed Jan 2018
csharrison@chromium.org
The number of resources a given page finished loading from cache at parse
stop.
csharrison@chromium.org
jkarlin@chromium.org
The number of completed resources loaded from the cache via the browser
process for a page load. Recorded when the page load is terminated.
csharrison@chromium.org
jkarlin@chromium.org
The number of completed resources loaded from the network via the browser
process for a page load. Recorded when the page load is terminated.
csharrison@chromium.org
jkarlin@chromium.org
The total number of completed resources loaded via the browser process for a
page load. Recorded when the page load is terminated.
dproy@chromium.org
tdresser@chromium.org
Measures Time to Interactive, a metric based on main thread and network
heuristics to approximate the point in time when the page feels interactive
to the user. See https://goo.gl/TFw6xz for detailed explanation. This
histogram uses First Meaningful Paint as the lower bound for quiescent
windows.
Deprecated in favor of PageLoad.PageTiming.ForegroundDuration.AfterPaint.
bmcquade@chromium.org
Measures the total time the page load was active after first paint, up until
being backgrounded, prior to the page load terminating. Recorded only for
page loads that started in the foreground.
Deprecated in favor of PageLoad.PageTiming.ForegroundDuration.AfterPaint.
bmcquade@chromium.org
Measures the total time the page load was active after first paint, for page
loads that spend the entire time in the foreground.
Deprecated in favor of PageLoad.PageTiming.ForegroundDuration.
bmcquade@chromium.org
Measures the total time the page load was active, up until being
backgrounded, for page loads that started in the foreground.
Deprecated in favor of PageLoad.PageTiming.ForegroundDuration.
bmcquade@chromium.org
Measures the total time the page load was active, for page loads that spend
the entire time in the foreground.
Deprecated in favor of
PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2.
ksakamoto@chromium.org
Whether the user had any interaction on the page (except mouse move) after
first paint, and whether the user left the page before network stable or
not.
Deprecated as of 05/17/2017.
ksakamoto@chromium.org
Whether the user had any interaction on the page (except mouse move) after
first paint, and whether the user left the page before network stable or
not. Not logged if page load was aborted before first paint.
ksakamoto@chromium.org
Records whether the First Meaningful Paint metric was reported for the page
load, or why it wasn't if not. See http://bit.ly/ttfmp-doc for the
definition of First Meaningful Paint.
Deprecated as of 05/17/2017.
ksakamoto@chromium.org
Measures the time between when the first meaningful paint
(http://bit.ly/ttfmp-doc) was computed to have happened, and when we
actually logged the metric.
This metric is useful in helping us tweak when FirstMeaningfulPaintDetector
should stop observing layout operations.
ksakamoto@chromium.org
Measures the time from a background tab being switched to the foreground to
the time the first meaningful paint is performed, for main frame documents.
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the first
meaningful paint (http://bit.ly/ttfmp-doc), for main frame documents.
ksakamoto@chromium.org
Measures the time from when the HTML parser started, to the first meaningful
paint (http://bit.ly/ttfmp-doc), for main frame documents.
Removed Jan 2018
csharrison@chromium.org
The parse duration of the page load where 0-50% of all subresources (loaded
during parsing) were served from the HTTP cache (including 304s).
Removed Jan 2018
csharrison@chromium.org
The parse duration of the page load where 51-100% of all subresources
(loaded during parsing) were served from the HTTP cache (including 304s).
Renamed to
PageLoad.Internal.Renderer.FirstMeaningfulPaintDetector.FirstMeaningfulPaintOrdering
ksakamoto@chromium.org
Whether the two variants of First Meaningful Paint reported different
values, and if so, which one was reported first.
Renamed to
PageLoad.Internal.Renderer.FirstMeaningfulPaintDetector.HadNetworkQuiet
ksakamoto@chromium.org
Recorded when the page load reached network 0-quiet (no active network
connection for 0.5 seconds), or network 2-quiet (no more than 2 active
network connections for 2 seconds).
PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2
histogram gives the fraction of page loads that had network 2-quiet, so it
can be used as a baseline.
tdresser@chromium.org
dproy@chromium.org
Records whether the Time To Interactive metric was reported for the page
load, or why it wasn't if not. See https://goo.gl/TFw6xz for definition of
Time to Interactive.
Removed Jan 2018
csharrison@chromium.org
The number of resources a given page finished loading at parse stop.
Removed April 2018, replaced by OriginStatus.
ericrobinson@chromium.org
For each identified ad frame, whether the origin of the ad matches the
origin of the main frame.
An ad frame consists of the identified ad frame and all of its children
(which may also be ads, but are counted as part of the ancestor ad frame).
Frames of zero bytes (e.g., never had a document or their document was
doc.written and no sub-resources were loaded) are not counted.
ericrobinson@chromium.org
For each identified ad frame, whether the origin of the ad matches the
origin of the main frame, differs from the origin of the main frame, or is
indeterminable.
An ad frame consists of the identified ad frame and all of its children
(which may also be ads, but are counted as part of the ancestor ad frame).
Frames of zero bytes (e.g., never had a document or their document was
doc.written and no sub-resources were loaded) are not counted.
jkarlin@chromium.org
The number of frames on the page that have loaded more than 0 bytes of
content.
For pages with zero ad frames, the other PageLoad.Clients.Ads metrics are
not recorded unless otherwise specified.
Child frames of an ad frame are not included in the count.
tdresser@chromium.org
Measures the time to first non-scroll input after the first paint.
tdresser@chromium.org
Measures the time to first scroll input after the first paint.
tdresser@chromium.org
Measures First Input Delay, the duration between the hardware timestamp and
the start of event processing on the main thread for the first meaningful
input per navigation. See https://goo.gl/tr1oTZ for a detailed explanation.
In ms.
tdresser@chromium.org
The duration between navigation start and the hardware timestamp of the
first meaningful input per navigation. See https://goo.gl/tr1oTZ for a
detailed explanation. In ms.
tdresser@chromium.org
The duration between the hardware timestamp and the start of event
processing on the main thread for a meaningful input. In ms.
tdresser@chromium.org
The duration between navigation start and the hardware timestamp of a
meaningful input. In ms.
tdresser@chromium.org
Measures longest Input Delay, the longest duration between the hardware
timestamp and the start of event processing on the main thread for the
meaningful input per navigation. In ms.
tdresser@chromium.org
The duration between navigation start and the hardware timestamp of the
meaningful input with longest queuing delay per navigation. In ms.
bmcquade@chromium.org
The delay between first paint and a client-side redirect navigation, for
pages that reported a first paint. This metric is only intended to help in
choosing a heuristic delay to distinguish between client-side redirects and
other client initiated navigations, and will be deprecated in M54. Please
contact bmcquade@chromium.org before using this metric.
bmcquade@chromium.org
Counts how often a client-side redirect was initiated from a page that did
not report a first paint. This metric is only intended to help in choosing a
heuristic delay to distinguish between client-side redirects and other
client initiated navigations, and will be deprecated in M54. Please contact
bmcquade@chromium.org before using this metric.
Deprecated in favor of
PageLoad.Internal.ClientRedirect.FirstPaintToNavigation and
PageLoad.Internal.ClientRedirect.NavigationWithoutPaint.
bmcquade@chromium.org
The delay between first paint and a client-side redirection. This metric is
only intended to help in choosing a heuristic delay to distinguish between
client-side redirects and other client initiated navigations, and will be
deprecated in M54. Please contact bmcquade@chromium.org before using this
metric.
Deprecated on 10/14/2016. No longer needed.
bmcquade@chromium.org
The delay between commit and completion, for page loads that did not receive
any timing IPCs. This metric is only intended to help understand the cases
where committed page loads don't receive timing IPCs. Please contact
bmcquade@chromium.org before using this metric.
csharrison@chromium.org
bmcquade@chromium.org
Counts of various internal error conditions in the page_load_metrics system.
dproy@chromium.org
tdresser@chromium.org
Measures time delta between Time to Interactive and when we can detect TTI.
TTI cannot be detected in real time - we have to wait sufficiently long to
determine main thread and network quiescence. See https://goo.gl/TFw6xz for
detailed explanation of Time to Interactive. This histogram uses First
Meaningful Paint as the lower bound for quiescent windows.
bmcquade@chromium.org
Whether a navigation started in the foreground.
bmcquade@chromium.org
The difference in magnitude between existing and updated timing, for
inter-frame timings that are received out of order. Page load metrics
observes timing updates in all frames on a page. It's possible for timings
in different frames to arrive out of order. This metric tracks how often
this happens, along with the magnitude of the difference.
bmcquade@chromium.org
Whether a page load completed after the app entered the background. We log a
'Started' value for each PageLoadTracker that is active when the app enters
the background, and a 'Completed' value for each of those PageLoadTrackers
that successfully runs its destructor. This helps to understand how many
trackers are destroyed while the app is in the background before they are
able to run their destructor. This metric is only intended to help in
understanding how often app background leads to data loss, and will be
deprecated in a subsequent release. Please contact bmcquade@chromium.org
before using this metric.
bmcquade@chromium.org
The status of PageLoadTiming structs received from the render process over
IPC.
ksakamoto@chromium.org
Whether the user had any interaction on the page before
FirstMeaningfulPaint. Recorded when the page load reaches network idle.
bmcquade@chromium.org
Counts the number of prerender navigations. Only logs true values.
csharrison@chromium.org
This histogram counts the number of provisional loads aborted by other
navigations, until a final forward back navigation commits.
csharrison@chromium.org
This histogram counts the number of provisional loads aborted by new
navigations, until a final new navigation commits.
csharrison@chromium.org
This histogram counts the number of provisional loads aborted by new
navigations. In this case the chain never ends with a commit. This is logged
on the next abort signal comes in (e.g. tab close or new navigation).
csharrison@chromium.org
This histogram counts the number of provisional loads aborted by other
navigations, until a final reload navigation commits.
csharrison@chromium.org
This histogram counts the number of consecutive provisional loads aborted by
other navigations with the same url (before redirects). It's logged when a
provisional abort does not share a URL, or when a load finally commits. Note
that we don't log chains of length 0.
ksakamoto@chromium.org
Whether the two variants of First Meaningful Paint reported different
values, and if so, which one was reported first.
ksakamoto@chromium.org
Recorded when the page load reached network 0-quiet (no active network
connection for 0.5 seconds), or network 2-quiet (no more than 2 active
network connections for 2 seconds).
PageLoad.Experimental.PaintTiming.FirstMeaningfulPaintSignalStatus2
histogram gives the fraction of page loads that had network 2-quiet, so it
can be used as a baseline.
panicker@chromium.org
For first paint, first contentful paint, first meaningful paint, first text
paint, and first image paint, we use the swap timestamp of the corresponding
paint, which is the timestamp the CC SwapPromise was positively fulfilled
(i.e. DidSwap() was invoked). If the swap did not occur (DidNotSwap() was
invoked), we use the timestamp when the swap promise fails. However, in the
future we may stop reporting timestamps for certain failure reasons. This
metric records whether or not the swap occurred, and the reason for failure
if it failed. The distribution of this metric will help determine the effect
of not reporting timestamps in certain cases.
deprecated May 2018: The swap-timestamp comes from a different process, and
comparing that with the paint-time (which is from the local process) does
not produce a reliable metric.
panicker@chromium.org
Records the delta between the renderer timestamp and swap timestamp for
first paint, first contentful paint, first meaningful paint, first text
paint, and first image paint. The renderer timestamp is recorded on the
Paint path, while the swap timestamp is the result of a CC SwapPromise
(queued on the Paint path) either being successfully fulfilled, or broken in
cases where the swap did not occur. As we switch to using the swap
timestamps in place of their renderer counterparts, this metric allows us to
see the discrepancies between the two timestamps.
csharrison@chromium.org
The number of URLs in the redirect chain for this navigation. This excludes
the first URL.
bmcquade@chromium.org
For page loads that start in the foreground, measures the duration of time
until one of the following events occurs: the load of the main resource
fails, the page load is stopped, the tab hosting the page is closed, the
render process hosting the page goes away, a new navigation which later
commits is initiated in the same tab, or the tab hosting the page is
backgrounded. This metric has a very long tail, for pages that spend a long
period of time in the foreground. As such, use of the mean or tail values
are not recommended.
jkarlin@chromium.org
The time since navigation start before the user presses the back button on a
page. Only measures page loads that remained in foreground and were created
by user gesture inside the renderer (as opposed to browser UX gestures).
bmcquade@chromium.org
shivanisha@chromium.org
Measures the time from navigation timing's navigation start to the time the
provisional load failed. Only measures provisional loads that failed in the
foreground.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
user first foregrounds an initially backgrounded tab. Only measures
navigations that started in the background.
ksakamoto@chromium.org
Measures the time from a background tab being switched to the foreground to
the time the first contentful paint is performed, for main frame documents.
pkotwicz@chromium.org
Measures the time from a background tab being switched to the foreground to
the time the first paint is performed, for main frame documents.
ksakamoto@chromium.org
The time from navigation start to first "contentful" paint.
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the time the
first image is painted, for main frame documents. For images that render
progressively, this is recorded as soon as any image pixels have been drawn.
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the time the
first paint is performed, for main frame documents.
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the time the
first non-blank text is painted, for main frame documents.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from when the HTML parser started, to when the page first
paints content.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
parser started, for main frame documents.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the execution of
scripts, for main frame documents that finished parsing.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the execution of
scripts inserted from document.write, for main frame documents that finished
parsing.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the load of scripts,
for main frame documents that finished parsing.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the load of scripts
inserted from document.write, for main frame documents that finished
parsing.
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser was active, for main frame documents
that finished parsing.
deprecated in favor of PageLoad.Timing2.*
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
DOMContentLoaded event is fired, for main frame documents.
deprecated in favor of PageLoad.Timing2.*
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
first layout is performed, for main frame documents.
deprecated in favor of PageLoad.Timing2.*
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
load event is fired, for main frame documents.
deprecated in favor of PageLoad.DocumentTiming.ParseDuration
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from when DOM loading occurs (the time that HTML parsing
begins) to the time the DOMContentLoaded event is fired, for main frame
documents. This is equivalent to the time that the HTML document resource
was being parsed.
deprecated in favor of PageLoad.PaintTiming.ParseStartToFirstContentfulPaint
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from when DOM loading occurs (the time that HTML parsing
begins) to first "contentful" paint.
deprecated in favor of PageLoad.PaintTiming.ForegroundToFirstPaint
pkotwicz@chromium.org
Measures the time from a background tab being switched to the foreground to
the time the first paint is performed, for main frame documents.
Deprecated in favor of PageLoad.ParseTiming.NavigationToParseStart
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
navigation committed, for main frame documents.
deprecated in favor of
PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
DOMContentLoaded event is fired, for main frame documents. This metric is
being phased out in favor of the PageLoad.DocumentTiming equivalent and will
be deprecated in M54.
deprecated in favor of PageLoad.PageTiming.NavigationToFailedProvisionalLoad
bmcquade@chromium.org
shivanisha@chromium.org
Measures the time from navigation timing's navigation start to the time the
provisional load failed. Only measures provisional loads that failed in the
foreground.
deprecated in favor of PageLoad.AbortTiming.Background.*
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
user first backgrounds the tab. Only measures navigations that started in
the foreground.
deprecated in favor of PageLoad.PaintTiming.NavigationToFirstContentfulPaint
ksakamoto@chromium.org
The time from navigation start to first "contentful" paint. This
metric is being phased out in favor of the PageLoad.PaintTiming equivalent
and will be deprecated in M54.
deprecated in favor of PageLoad.PageTiming.NavigationToFirstForeground
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
user first foregrounds an initially backgrounded tab. Only measures
navigations that started in the background.
deprecated in favor of PageLoad.PaintTiming.NavigationToFirstImagePaint
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the time the
first image is painted, for main frame documents. For images that render
progressively, this is recorded as soon as any image pixels have been drawn.
This metric is being phased out in favor of the PageLoad.PaintTiming
equivalent and will be deprecated in M54.
deprecated in favor of PageLoad.DocumentTiming.NavigationToFirstLayout
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
first layout is performed, for main frame documents. This metric is being
phased out in favor of the PageLoad.DocumentTiming equivalent and will be
deprecated in M54.
deprecated in favor of PageLoad.PaintTiming.NavigationToFirstPaint
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the time the
first paint is performed, for main frame documents. This metric is being
phased out in favor of the PageLoad.PaintTiming equivalent and will be
deprecated in M54.
deprecated in favor of PageLoad.PaintTiming.NavigationToFirstTextPaint
ksakamoto@chromium.org
Measures the time from navigation timing's navigation start to the time the
first non-blank text is painted, for main frame documents. This metric is
being phased out in favor of the PageLoad.PaintTiming equivalent and will be
deprecated in M54.
deprecated in favor of PageLoad.DocumentTiming.NavigationToLoadEventFired
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from navigation timing's navigation start to the time the
load event is fired, for main frame documents. This metric is being phased
out in favor of the PageLoad.DocumentTiming equivalent and will be
deprecated in M54.
deprecated in favor of PageLoad.ParseTiming.ParseBlockedOnScriptLoad
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the load of scripts,
for main frame documents that started parsing.
deprecated in favor of PageLoad.ParseTiming.ParseBlockedOnScriptLoad
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the load of scripts,
for main frame documents that finished parsing. This metric is being phased
out in favor of the PageLoad.ParseTiming equivalent and will be deprecated
in M54.
deprecated in favor of
PageLoad.ParseTiming.ParseBlockedOnScriptLoadFromDocumentWrite
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the load of scripts
inserted from document.write, for main frame documents that started parsing.
deprecated in favor of
PageLoad.ParseTiming.ParseBlockedOnScriptLoadFromDocumentWrite
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser spent blocked on the load of scripts
inserted from document.write, for main frame documents that finished
parsing. This metric is being phased out in favor of the
PageLoad.ParseTiming equivalent and will be deprecated in M54.
deprecated in favor of PageLoad.ParseTiming.ParseDuration
bmcquade@chromium.org
csharrison@chromium.org
Measures the time that the HTML parser was active, for main frame documents
that finished parsing. This metric is being phased out in favor of the
PageLoad.ParseTiming equivalent and will be deprecated in M54.
deprecated in favor of PageLoad.PaintTiming.ParseStartToFirstContentfulPaint
bmcquade@chromium.org
csharrison@chromium.org
Measures the time from when the HTML parser started, to when the page first
paints content. This metric is being phased out in favor of the
PageLoad.PaintTiming equivalent and will be deprecated in M54.
fmeawad@chromium.org
panicker@chromium.org
Tracks the transitions of the page between the various PageLifecycleStates:
active, hidden/backgrounded, hidden/foregrounded, and frozen. A page is
considered active if is visible. A page is considered backgrounded if not
visible and not currently providing a useful service, such as playing audio.
A page is considered foregrounded if it is not backgrounded. A page can be
frozen due to being hidden/backgrounded for a specified amount of time, or
frozen due to critical resources.
carlosk@chromium.org
Total time the browser process waited for all render processes to save their
respective frames while saving a page into MHTML.
carlosk@chromium.org
Time the browser process waited on a single frame to be saved by a render
processes while saving a page into MHTML.
carlosk@chromium.org
Time taken to encode into MTHML the fully serialized contents of a frame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
carlosk@chromium.org
Final status of the MHTML save operation for a page.
carlosk@chromium.org
Time taken to save a page into an MHTML file.
jianli@chromium.org
Recorded when the popup overlays are removed from MHTML serialization.
carlosk@chromium.org
Time spent by the main threads of all involved render processes while saving
the frame tree of a page to MHTML.
carlosk@chromium.org
Time spent by the renderer main thread while saving one frame of a page to
MHTML.
carlosk@chromium.org
The longest time taken by the main thread of a render processes to save one
frame of a page being saved to MHTML. In other words this is the maximum
value reported in
PageSerialization.MhtmlGeneration.RendererMainThreadTime.SingleFrame for one
page save operation.
carlosk@chromium.org
Time taken to fully serialize the contents of a frame, including HTML and
CSS and image resources.
carlosk@chromium.org
Time spent writing a frame's encoded MHTML data to the file on disk.
romax@chromium.org
Percentage of loaded CSS elements in the main frame at the time of
serialization.
romax@chromium.org
Percentage of loaded images in the main frame at the time of serialization.
romax@chromium.org
Total number of CSS elements in the main frame for serialization.
romax@chromium.org
Total number of images in the main frame for serialization.
carlosk@chromium.org
Time spent serializing a CSS element (including embedded "sub"-CSS
and images).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
carlosk@chromium.org
Time taken to generate HTML data from a frame's DOM and serialize it
(without sub-resources like CSS and images).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
carlosk@chromium.org
Time spent serializing an image element.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated Aug 2017
csharrison@chromium.org
The delay from when bytes are received on the main thread to when the
BackgroundHTMLParser starts tokenizing them. Always a shorter time than the
time emitted to Parser.PreloadTokenizeDelay.
Deprecated May 2017
csharrison@chromium.org
The time it takes to enqueue a ParsedChunk onto the shared parser queue.
csharrison@chromium.org
The number of speculative tokens discarded by the parser when a rewind is
needed.
Deprecated Aug 2017
csharrison@chromium.org
The maximum number of pending Chunks in the ParsedChunkQueue after the
parser is detached.
Deprecated Aug 2017
csharrison@chromium.org
The maximum number of pending tokens in the ParsedChunkQueue after the
parser is detached.
Deprecated May 2017
csharrison@chromium.org
The delay from when bytes are received on the main thread to when they are
tokenized and preloads are sent back to the main parser. Always a greater
time than the time emitted to Parser.AppendBytesDelay.
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.
Deprecated 2017-12 by PartnerBookmark.Count2.
wychen@chromium.org
The number of partner bookmark entries. Note that zero would be
under-represented because reading is throttled if the last result is zero.
Logged when using the bookmark, not skipped (PartnerBookmark.Skipped ==
False), and at most once per cold start. Note that the distribution is
weighted by bookmark usage.
wychen@chromium.org
The number of partner bookmark entries. Logged when using the bookmark, and
at most once per cold start. Note that the distribution is weighted by
bookmark usage.
thildebr@chromium.org
The response we got back from our favicon fetching throttler, once for each
bookmark at each cold start. Only recorded on Android.
wychen@chromium.org
The time spent on loading partner bookmarks, from kickOffReading() to
bookmarkModelLoaded() callback.
No longer recorded as of Apr 2018
wychen@chromium.org
Whether there's no partner bookmark provider. By default, the system image
contains a dummy partner bookmarks provider that provides zero entries.
Logged when using the bookmark, not skipped (PartnerBookmark.Skipped ==
False), and at most once per cold start.
No longer recorded as of Apr 2018
wychen@chromium.org
Whether reading of partner bookmark is skipped. Logged when using the
bookmark, and at most once per cold start.
Deprecated 2017-12. Use PartnerBookmark.TimeSinceLastEmptyRead2.
wychen@chromium.org
When trying to load the partner bookmarks, if no partner bookmark is read
last time, record the time elapsed since then. It is recorded no matter
whether loading would be skipped.
No longer recorded as of Apr 2018
wychen@chromium.org
When trying to load the partner bookmarks, if no partner bookmark is read
last time, record the time elapsed since then. It is recorded no matter
whether loading would be skipped.
thildebr@chromium.org
Number of elements read from the partner bookmarks favicon cache, recorded
once per cold start when reading partner bookmarks. Only recorded on
Android.
vasilii@chromium.org
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.
kolos@chromium.org
Measures the frequency of user editing of generated passwords. Uploaded once
per generated password save. Applicable to automatic and manual generations.
kolos@chromium.org
Measures the frequency of manually triggered password generations.
gcasto@chromium.org
vabr@chromium.org
Measures the frequency of submission events for passwords that could have
been generated, but the user didn't choose to use the feature. This is to
compare with PasswordGeneration.SubmssionEvent.
gcasto@chromium.org
vabr@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.
alexmos@chromium.org
battre@chromium.org
Records attempts to submit a password on a form in an about:blank frame,
indicating whether this attempt is for a main frame or subframe. Recorded
once per form submission.
dvadym@chromium.org
vasilii@chromium.org
The type of event that the Password Manager used for detecting a password
form submission when saving or updating a password. Recorded each time a
user accepts a password save/update prompt.
vabr@chromium.org
Recorded whenever the user accesses the passwords in the settings page.
Deprecated as of Chrome 56. See the histograms for one and more accounts.
vasilii@chromium.org
The dismissal reason of the account chooser.
vasilii@chromium.org
The number of accounts displayed in the account chooser.
vasilii@chromium.org
The count of the placeholder avatars shown in the account chooser.
vasilii@chromium.org
The dismissal reason of the account chooser with multiple accounts.
vasilii@chromium.org
The dismissal reason of the account chooser with one account.
vasilii@chromium.org
Whether the account chooser includes an empty username or any duplicates
gcasto@chromium.org
vabr@chromium.org
The number of accounts stored per site in the password manager (one event
per site)
engedy@chromium.org
vabr@chromium.org
Records, for each account, the number of other accounts (across all sites
and usernames) that reuse the same password. Only non-blacklisted,
HTML-form-based accounts are considered.
For each account, samples will only be recorded into the histograms that
have the first suffix corresponding to whether that account was saved on a
secure website or not. The second suffix is used to further categorize the
other accounts that reuse the same password based on how they relate to the
account in question, and whether they are secure. The number of other
accounts in each category will be reported into histogram with the
respective second suffixes.
Metrics are collected once per browser start-up. In case of multiple
profiles, the counts are for the profile for which a WebContents is first
created.
Deprecated as of Chrome 32. See PasswordManagerActionsTakenWithPsl
vabr@chromium.org
Stats documenting how we handle every form containing a password, bucketed
by the actions taken.
estark@chromium.org
Stats documenting how we handle every form containing a password on a
non-secure page, bucketed by the actions taken.
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.
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. Become obsolete in Feb. 2015.
melandory@chromium.org
vasilii@chromium.org
Why was "Allow to collect URL?" bubble closed?
vabr@chromium.org
Records what happened to the progress bar during exporting passwords when
its dismissal was requested.
jdoerrie@chromium.org
melandory@chromium.org
Records the action taken with a password credential entry on Android.
jdoerrie@chromium.org
melandory@chromium.org
Records the action taken with a password of a password credential entry on
Android.
jdoerrie@chromium.org
melandory@chromium.org
Records the action taken with a username of a password credential entry on
Android.
jdoerrie@chromium.org
melandory@chromium.org
Records the action taken with a website of a password credential entry on
Android.
jdoerrie@chromium.org
melandory@chromium.org
Records the action taken with a password exception entry on Android.
jdoerrie@chromium.org
melandory@chromium.org
Records the action taken with a website of a password exception entry on
Android.
fhorschig@chromium.org
Records whether a user triggered the search function while visiting the
password preferences page on Android.
gcasto@chromium.org
If the password manager UI was suppressed because generation UI was already
being displayed for the same field.
vasilii@chromium.org
The dismissal reason of the auto-signin first run experience.
gemene@google.com
jdoerrie@chromium.org
The number of duplicates forms from the password store. Recorded once for
the profile on startup.
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
Records once on startup whether the blacklisted sites in the password store
need to be updated to remove username/password. Can be removed around Chrome
M69 (https://crbug.com/817754).
battre@chromium.org
vabr@chromium.org
When the password manager sees new forms on the page, it records in this
histogram whether there were any SSL certificate errors. The presence of SSL
errors likely means that the password manger will stop working, so the
reporting is done at the last point when password manager is still
guaranteed to be active. Some particular errors are distinguished, with the
rest being reported in a catch-all bucket.
battre@chromium.org
Indication whether users change the credentials (username and password) in
the save bubble of the password manager, considering only cases where the
user saves a new credential or updates a credential.
vasilii@chromium.org
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 number of password fields for password forms that do not have a username
field. This is recorded every time such a password form is successfully
parsed. Note that the parsing is attempted when the form is encountered (i.e
when the document is loaded) and also when it is submitted.
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.
vabr@chromium.org
Indicates whether the password manager is enabled when a tab is opened. This
includes prerendered tabs.
cfroussios@chromium.org
ioanap@chromium.org
vabr@chromium.org
The number of passwords exported in CSV format per user.
cfroussios@chromium.org
ioanap@chromium.org
vabr@chromium.org
The success or error type of exporting passwords into CSV.
msramek@chromium.org
engedy@chromium.org
When a credential is filled, whether it comes from an Android app.
msramek@chromium.org
engedy@chromium.org
When offering to fill the username and password, whether at least one of the
credentials in the dropdown comes from an Android app.
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.
gcasto@chromium.org
vabr@chromium.org
deepak.m1@samsung.com
When the generation state of a password was changed, records whether an
existing form corresponding to the password was found.
Deprecated as of 05/2017. This metric has been replaced by
PasswordManager.MediationOptional.
vasilii@chromium.org
Tracks result of navigator.credentials.get() with unmediated=false. That is
the result of account chooser.
Deprecated as of 05/2017. This metric has been replaced by
PasswordManager.MediationSilent.
vasilii@chromium.org
Tracks result of navigator.credentials.get() with unmediated=true. That is
the result of auto sign-in.
vasilii@chromium.org
Number of HTTP saved passwords that were migrated to HTTPS. Recorded on
HTTPS password form load when there are no credentials saved.
jdoerrie@chromium.org
The mode of migration applied to HTTP passwords migrating to HTTPS. Recorded
on HTTPS password form load when there are no credentials saved.
vabr@chromium.org
The result of importing passwords stored in IE7 into Chrome's password
store.
xunlu@chromium.org
vabr@chromium.org
The number of passwords imported in CSV format per user
xunlu@chromium.org
vabr@chromium.org
The response code of successful or failed password import attempt from a CSV
file.
vasilii@chromium.org
The number of saved passwords in the store that could not be decrypted.
Recorded once for the profile on startup.
Deprecated as of 03/2016. This metric has been replaced by
PasswordManager.UIDismissalReason.
vabr@chromium.org
The distribution of responses to the "Do you want Chrome to remember
this password"? info bar prompt.
dvadym@chromium.org
nparker@chromium.org
This metric reports whether a sync password hash is saved. Recorded shortly
after Chrome startup.
Deprecated as of 09/2016.
vasilii@chromium.org
After migration from the Mac Keychain fails, records the number of passwords
in the Keychain owned by Chrome but not accessible by it.
vasilii@chromium.org
After migration from the Mac Keychain fails, records the number of passwords
in the Chrome Password Manager database for which the corresponding values
in the Keychain are not accessible by Chrome.
vasilii@chromium.org
After migration from the Mac Keychain fails, records the number of passwords
in the Chrome Password Manager database to be migrated. As there is no
partial migration, it's the total number of passwords in the DB.
vasilii@chromium.org
The status of passwords migration from the Keychain. It's recorded shortly
after startup.
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.
vasilii@chromium.org
The version of LoginDatabase if the migration to a new one failed.
vasilii@chromium.org
An error on LoginDatabase initialization.
jdoerrie@chromium.org
vasilii@chromium.org
Tracks result of navigator.credentials.get() with
mediation="optional". That is the result of account chooser.
jdoerrie@chromium.org
vasilii@chromium.org
Tracks result of navigator.credentials.get() with
mediation="required". That is the result of forced account
chooser.
jdoerrie@chromium.org
vasilii@chromium.org
Tracks result of navigator.credentials.get() with
mediation="silent". That is the result of auto sign-in.
Deprecated 03/2018 in favor of PasswordManager.UpdateUIDismissalReason.
dvadym@chromium.org
A user action when a password update bubble with multiple accounts is shown.
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.
Deprecated as of 08/2015.
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.
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.
vabr@chromium.org
wfh@chromium.org
Indicates whether the user's OS password is blank or not at browser startup.
vabr@chromium.org
Breakdown of how other possible usernames are displayed. Recorded every time
we autofill a password form.
Deprecated as of May 17 2017. Replaced by
PasswordProtection.RequestOutcome.ProtectedPasswordEntry.
dvadym@chromium.org
jialiul@chromium.org
nparker@chromium.org
A password reuse is an event when the user typed a string that is equal to a
saved password on another domain, and this saved password is called reused
password.
This metric shows whether a password reuse happens on a page whose main
frame url matches CSD whitelist.
dvadym@chromium.org
nparker@chromium.org
This metric shows how many saved credentials (num unique registry-controlled
domains) have password that's equal to the reused password.
Before M63 this logged a "0" for sync-reuse.
A "password reuse" is when the user typed a string that is equal
to a saved password on another domain or is equal to the sync password on a
non google-login domain.
dvadym@chromium.org
nparker@chromium.org
This metric reports whether a password field had been detected on a page
when a password reuse happened.
A "password reuse" is when the user typed a string that is equal
to a saved password on another domain or is equal to the sync password on a
non google-login domain.
dvadym@chromium.org
nparker@chromium.org
This metric shows the length of the reused password.
Change in M63: If multiple passwords are matched simultaneously, this logs
the length of the longest password. Also, before M63, a "0" was
logged for sync-reuse.
A "password reuse" is when the user typed a string that is equal
to a saved password on another domain or is equal to the sync password on a
non google-login domain.
dvadym@chromium.org
nparker@chromium.org
This metric shows how many credentials are stored in Password Manager when a
password reuse happened. This counts unique registry-controlled domains with
passwords saved.
A "password reuse" is when the user typed a string that is equal
to a saved password on another domain or is equal to the sync password on a
non google-login domain.
During M61/M62 this metric logged a "1" for every sync-reuse. It
was fixed in M63 such that it logs actual Password Manager credential count.
kolos@chromium.org
Measures whether users save passwords with automatic prompt or manual
fallback.
gcasto@chromium.org
rouslan@chromium.org
Whether the passwords are syncing and, if not, then what's causing sync
failures. Recorded after the first sync attempt either succeeds or fails.
Deprecated as of 05/2018.
kolos@chromium.org
Measures whether users update passwords with automatic prompt or manual
fallback.
ioanap@chromium.org
Records successful fills of prefilled username values known as placeholders
and unsuccessful fills that were blocked because the prefilled value was not
identified as a placeholder. Recorded once per PasswordAutofillAgent
instance, when attempting to fill a password form that contains a username
value which was prepopulated by the website.
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.
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 (PSL) for
possible matches. In addition, this metric also counts cases where a
existing federated entry was successfully matched via PSL. For example, this
includes cases where an existing federated credential for
https://example.com was used for https://subdomain.example.com.
engedy@chromium.org
Records, for each password form seen by the password manager, whether the
PasswordStore responded quickly enough so that
PasswordManager.SuppressedAccount histogram samples could be computed.
vabr@chromium.org
Recorded whenever the user interacts with reauthentication in order to
access the passwords in settings, or when such reauthentication is skipped
for a well-defined reason.
battre@chromium.org
HTTP response code of fetching a password requirements file.
battre@chromium.org
Network error code of fetching a password requirements file.
battre@chromium.org
Time until the lookup for a password requirements file completed (or was
aborted).
battre@chromium.org
Result of fetching requirements for password during password generation.
dvadym@chromium.org
jialiul@chromium.org
Records the type of password (e.g saved password, sync password, enterprise
password etc) reused by the user. This is logged when a password reuse
happens.
dvadym@chromium.org
jialiul@chromium.org
Records the number of enterprise password hashes that have been saved for
password reuse detection. This is logged during the initialization of
PasswordStore class.
dvadym@chromium.org
jialiul@chromium.org
Records the number of Gaia password hashes that have been saved for password
reuse detection. This is logged during the initialization of PasswordStore
class.
Deprecated as of 03/2016.
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.
Deprecated as of 03/2016.
vabr@chromium.org
Indicates whether the save password prompt was displayed.
Deprecated as of 03/2016.
vabr@chromium.org
Breakdown of which response the user selected from the save password prompt.
vasilii@chromium.org
Why was the save password UI (bubble or infobar) closed?
Deprecated 06/2017
engedy@chromium.org
melandory@chromium.org
Tracks the pair of initial values and pair of final values for the legacy
preference for controlling the Chrome Password Manager and the new
preference for controlling Smart Lock on Android. A single sample is
recorded after sync has merged last snapshot and finished initialization for
sync users, and on profile initialization for non-sync users.
Deprecated 06/2017
engedy@chromium.org
melandory@chromium.org
Tracks the pair of initial values for both for the legacy preference for
controlling the Chrome Password Manager and new preference for controlling
Smart Lock on Android. Sample is recorded on every profile initialization
before reconciliation logic is taken place, e.g. when user logs in to
browser, on a startup of a browser.
jdoerrie@chromium.org
This metric is recorded every time Chrome detects a password form
submission. The credential might be proposed to be saved, or it might be
blocked. It is blocked if the previously detected password form submission
was successful, and the current submission is from a URL with the same
origin, but a different and insecure scheme. That is, if the previously
provisionally saved credential is for https://example.com, a new credential
for http://example.com would be blocked. More details can be found in the
doc associated with http://crbug.com/571580.
vasilii@chromium.org
Records if the user still has to click through the first run experience to
benefit from auto sign-in behavior. Recorded on every start-up.
dvadym@chromium.org
vabr@chromium.org
Records results of the new and the old algorithm for detecting whether to
show a password prompt to the user. Recorded on each password form
successful submission.
jdoerrie@chromium.org
melandory@chromium.org
Recorded when the "Show all saved passwords" fallback is accepted.
jdoerrie@chromium.org
melandory@chromium.org
Recorded when the "Show all saved passwords" fallback is shown.
Deprecated 05/2018 because the feature never launched.
estark@chromium.org
Recorded (at most once per main-frame navigation) when a password form shows
a warning that the form is not secure.
vasilii@chromium.org
User action on the Chrome Sync promo that appears in the password bubble.
The promo offers to sign in to Chrome.
Deprecated as of 12/16/16. New statistic is
PasswordManager.SignInPromoCountTil*.
vasilii@chromium.org
The number of times the Sign In promo in the password bubble was shown
before user clicked on it.
vasilii@chromium.org
The number of times the Sign In promo in the password bubble was shown
before user clicked on "No thanks".
vasilii@chromium.org
The number of times the Sign In promo in the password bubble was shown
before user clicked on "Sign in".
vasilii@chromium.org
The number of times the Sign In promo in the password bubble was implcitly
dismissed. Recorded each time the promo is implicitly dismissed.
Deprecated as of 14 September 2017, due to being no longer useful.
xunlu@chromium.org
vabr@chromium.org
Whether password manager stored passwords imported from CSV file
successfully.
vabr@chromium.org
When the user logs in with their sync credential, PasswordManager checks if
there are any outdated copies of it in the password store, in order to purge
them. This histogram records whether password store data are ready during
this check.
vabr@chromium.org
Indicates whether submitting a password login form changes the registry
controlled domain of the main frame.
dvadym@chromium.org
vasilii@chromium.org
Records a frame type (eg. main frame, iframe with the same url as the main
frame) of a submitted password form.
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.
estark@chromium.org
The type (e.g. signup, login, change password) of all submitted password
forms on non-secure pages. This is logged on form submission, but doesn't
require that the password manager saves.
dvadym@chromium.org
engedy@chromium.org
The type of event that the Password Manager used for detecting a password
form submission. Recorded for each successful password form submission.
vasilii@chromium.org
The type of password suggestion on iOS displayed in the keyboard accessory.
Recorded for each tap on the suggestion.
vasilii@chromium.org
The type of password suggestions on iOS displayed in the keyboard accessory.
Recorded each time the password suggestion is shown.
engedy@chromium.org
Records, for each password form seen by the password manager, whether there
were `suppressed` credentials, meaning stored credentials that were not
filled because they were for an origin that was similar to, but not exactly
(or PSL) matching the origin of the observed form (see the suffix
description for the possible classes of such near-matches). If there were
such credentials, the histogram also records whether the username and
password of such suppressed credentials matched those submitted.
gcasto@chromium.org
vabr@chromium.org
This histogram is reported for those forms on accounts.google.com, on which
Chrome is forced by Finch/flags during autofilling to remove sync
credentials from password store results. It reports true if sync credentials
were indeed removed from the store results, and false if there were no sync
credentials in the results to begin with.
gcasto@chromium.org
vabr@chromium.org
Information about the user's current sync status crossed with whether their
synced password is saved.
dvadym@chromium.org
nparker@chromium.org
This metric reports a type of a sync password hash change event. Recorded
when a sync password hash is saved or cleared.
dvadym@chromium.org
vabr@chromium.org
The time between receiving saved credentials from the password store and
predictions from the Autofill server. Recorded each time when predictions
for a form are received.
cfroussios@chromium.org
ioanap@chromium.org
vabr@chromium.org
The time it takes to fetch and serialise the passwords for export.
Deprecated as of 11/11/14. New statistic is
PasswordManager.TimesPasswordUsed.AutoGenerated.
gcasto@chromium.org
vabr@chromium.org
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)
engedy@chromium.org
vabr@chromium.org
The number of accounts stored in the password manager (across all sites) for
origins with the scheme (e.g., HTTP, HTTPS, FTP) as given in the histogram
suffix. For each scheme, the count is recorded once per browser start-up.
(In case of multiple profiles, the counts are for the profile that first has
a WebContents created.)
vasilii@chromium.org
Why was the password manager's UI (bubble or infobar) closed? Save and
update UI are tracked separately.
Deprecated 03/2018 in favor of PasswordManager.UpdateUIDismissalReason.
dvadym@chromium.org
vasilii@chromium.org
The password submission event happened when the user changes their password
on a website, say foo.com or types new password on a sign-in form for saved
credential (which might mean that the password was changed in a different
browser). The later case called password overriding. This histogram measures
whether the user has any passwords saved in the Chrome password manager for
foo.com or the password was overriden on sign-in form, and what action the
user performed on the offered bubble. It's recorded when the bubble is
closed.
vasilii@chromium.org
Why was the update password UI (bubble or infobar) closed?
kolos@chromium.org
Chrome saves locally all fields a user typed on a sign-up form. If Chrome
saved an incorrect username and the user changes the username on a sign-in
form to a value of another field from the sign-up form, then Chrome uploads
a username correction vote which points to the correct username field. This
histogram measures how many correction votes are uploaded.
kolos@chromium.org
Measures what method was used for username field detection in the renderer
code. The metric may be recorded several times for page visit because it is
recorded at every PasswordForm creation. If a site changes HTML attributes
of fields or server-side predictions is received, different values can be
recorded for the same form. If an outcome of HTML classifier or a
server-side prediction coincides with the outcome of base heuristic, the
metric points to base heuristic method.
Deprecated 07/2016 because this information is no longer stored in
PasswordForm. See also http://crbug.com/413020.
xunlu@chromium.org
gcasto@chromium.org
Whether saved password for HTTPS site had a valid SSL cert when the password
was saved.
jialiul@chromium.org
nparker@chromium.org
Records how a user interacts with the chrome://settings page that displays
the password protection warning. Logged when the page is shown and when the
user chooses to change their password on the page.
jialiul@chromium.org
nparker@chromium.org
The number of Gaia password reuse warnings shown to user before user changes
their password. Logged when we see that user has changed their Gaia
password. The number of reuses will be reset to zero if current session of
browser process ends. This count doesn't include the reuses that user marked
as legitimate.
jialiul@chromium.org
nparker@chromium.org
Records how a user interacts with the password protection interstitial
(a.k.a chrome://reset-password page). Logged when the interstitial is shown
and when the user chooses to change their password.
jialiul@chromium.org
nparker@chromium.org
When user manually navigates to chrome://reset-password page, records how
this user interacts with this page. Logged when the interstitial is shown
and when the user chooses to change their password.
jialiul@chromium.org
nparker@chromium.org
Records the type of strings shown to the user on chrome://reset-password
page. Logged when the interstitial in initialized.
jialiul@chromium.org
nparker@chromium.org
Records how a user interacts with the password protection modal warning
dialog. Logged when the dialog is shown and when the user chooses to change
their password, ignore warning, or navigate away.
jialiul@chromium.org
nparker@chromium.org
Number of password protection verdicts stored in content settings of a
profile before this profile is destructed.
jialiul@chromium.org
nparker@chromium.org
We start changing the way of caching password protection verdicts in M69.
This histogram counts the number of verdicts migrated to the new way during
initialization of PasswordProtectionService. It helps determine when we can
remove migration code.
jialiul@chromium.org
nparker@chromium.org
Records how a user interacts with page info bubble that displays the
password protection warning. Logged when such page info bubble is shown and
when the user chooses to change their password, ignore warning, or mark site
as legitimate via buttons on the page info bubble.
jialiul@chromium.org
nparker@chromium.org
Records the outcome of the password alert mode, indicating if password alert
warning is shown successfully or if it is skipped for some reason.
jialiul@chromium.org
nparker@chromium.org
Response or error codes for PasswordProtectionRequest. Logged after chrome
receives response of PasswordProtectionRequest from Safe Browsing service.
Deprecated since May 12 2017. Replaced by
PasswordProtection.Verdict.ProtectedPasswordEntry.
jialiul@chromium.org
nparker@chromium.org
Verdict types returned by Safe Browsing server for password reuse events.
jialiul@chromium.org
nparker@chromium.org
When password protection service detects a reuse of Chrome sync password,
record the type of Chrome sync account on which the reuse happens (e.g.
@gmail.com, @googlemail.com, or other dasher account).
drubery@chromium.org
jialiul@chromium.org
The referrer chain size of a password protection request. This is recorded
when Chrome receives a verdict for this request.
jialiul@chromium.org
nparker@chromium.org
The time it takes for PasswordProtectionService request. It is not recorded
for requests that were canceled.
jialiul@chromium.org
nparker@chromium.org
Records the outcome of the password protection request, indicating if
request is sent out successfully or if it is skipped or canceled for some
reason.
Deprecated since May 12 2017. Replaced by
PasswordProtection.Verdict.PasswordFieldOnFocus.
jialiul@chromium.org
nparker@chromium.org
Verdict types returned by Safe Browsing server for unfamiliar login pages.
jialiul@chromium.org
nparker@chromium.org
Whether the user has clicked through the Safe Browsing interstitial before
the password protection ping is triggered on the same page. Logged right
before password protection ping is sent.
jialiul@chromium.org
nparker@chromium.org
Verdict types returned by Safe Browsing server for a password protection
request. Request can be triggered when user focuses on a password field or
enters a protected password.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the flow was completed when CanMakePayment was not called by the
merchant.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the merchant used the CanMakePayment method during a Payment
Request.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
The effect of the CanMakePayment return value on whether Show was called.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the flow was completed when CanMakePayment was called by the
merchant and returned false.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the flow was completed when CanMakePayment was called by the
merchant and returned true.
sebsg@chromium.org
The reason that lead to an abort of the Payment Request.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
When the merchant has processed the user's Payment Request.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
When a Payment Request gets initiated by the user.
sebsg@chromium.org
The reason that leads to the Payment Request not being shown to the user.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
When the user clicks the "pay" button in the Payment Request UI.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
When the browser retrieves the instrument details from the payment app to
complete a purchase.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
When the Payment Request UI gets shown after initialization.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
When the Payment Request UI gets skipped to go directly to the payment app.
sebsg@chromium.org
A bitfield representing the different events that happened during the
Payment Request.
sebsg@chromium.org
The number of times the user added an entry during a Payment Request.
sebsg@chromium.org
The number of times the user changed an entry during a Payment Request.
sebsg@chromium.org
The number of times the user edited an entry during a Payment Request.
sebsg@chromium.org
The number of suggestions shown to the user during a payment request.
M62+ Included in PaymentRequest.Events
sebsg@chromium.org
Tracks what user information is required by merchants to complete a Payment
Request.
M62+ Included in PaymentRequest.Events
sebsg@chromium.org
Tracks what payment method was used to complete a transaction in Payment
Request.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the flow was completed when the user did not have a complete
suggestion offered for each requested information.
Replaced by PaymentRequest.NumberOfSuggestionsShown.PaymentMethod on July
19th 2017.
sebsg@chromium.org
Whether the flow was completed when the user did not have a a form of
payment on file when the Payment Request was shown.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the flow was completed when the user did not have suggestions
offered for each requested information.
M62+ Part of PaymentRequest.Events
sebsg@chromium.org
Whether the flow was completed when the user had at least one complete
suggestion offered for each requested information.
Replaced by PaymentRequest.NumberOfSuggestionsShown.PaymentMethod on July
19th 2017.
sebsg@chromium.org
Whether the flow was completed when the user had a form of payment on file
when the Payment Request was shown.
sebsg@chromium.org
Whether the flow was completed when the user had suggestions offered for
each requested information.
hnakashima@chromium.org
Tracks user actions in the PDF viewer. Logged when the document is opened
and when one of the relevant user actions is taken, such as opening the
bookmarks bar or setting the zoom mode to fit-to-page. The enum values that
are named "First" are logged only once per document, so that we
can measure in what percentage of documents a given action was performed at
least once.
hnakashima@chromium.org
Tracks documents opened in the PDF viewer that displayed one or more pages
with the given annotation type.
tsergeant@chromium.org
Tracks which features are used by documents opened in the PDF viewer, logged
when the document finishes loading.
thestig@chromium.org
The size of PDF documents opened in the PDF viewer.
rharrison@chromium.org
Tracks what types of forms are present in PDF document, logged when the
document finishes loading.
hnakashima@chromium.org
Measures if PDFs opened in the PDF viewer have attachments. This is logged
whenever a document is opened in the PDF viewer.
npm@chromium.org
Measures if PDFs opened in the PDF viewer require fonts to be substituted.
This is logged whenever a document is opened in the PDF viewer.
hnakashima@chromium.org
Measures if PDFs opened in the PDF viewer are Linearized PDFs. This is
logged whenever a document is opened in the PDF viewer.
hnakashima@chromium.org
Tracks documents opened in the PDF viewer that are Tagged PDFs.
tommycli@chromium.org
Tracks what happens when Chrome tries to load a PDF. This metric tracks all
cases, but is focused on measuring failed PDF embeds, which occur if the
user is on Android, or if PDF plugin is disabled.
hnakashima@chromium.org
Tracks the number of pages in PDF documents opened in the PDF viewer.
raymes@chromium.org
Counts various actions related to the Pepper Broker interface.
jbauman@chromium.org
True if a non-flash Pepper Graphics3D context has a share group.
sehr@chromium.org
bradnelson@chromium.org
bbudge@chromium.org
raymes@chromium.org
The number of out-of-process plugin processes that have loaded a particular
PPB interface version.
raymes@chromium.org
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.
Deprecated as of 8/2017.
raymes@chromium.org
Whether a Pepper media stream request (mic/cam access) comes from a plugin
in a secure or an insecure origin.
Deprecated 05/2018. Made decision in issue 758385 with already acquired
data. So this is no longer needed.
maxlg@chromium.org
The count of possible string of the endMark parameter in
performance.measure().
Deprecated 05/2018. Made decision in issue 758385 with already acquired
data. So this is no longer needed.
maxlg@chromium.org
The count of possible string of the startMark parameter in
performance.measure().
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).
lgrey@chromium.org
The average CPU idle wakeups per second, sampled every two minutes.
lgrey@chromium.org
(Mac only) The average package exit idle wakeups per second, sampled every
two minutes. This is a subset of wakeups that indicate that the processor
complex was taken out of low-power state. For more info, see the
powermetrics man page on macOS.
dominickn@chromium.org
kcarattini@chromium.org
miguelg@chromium.org
mlamouri@chromium.org
Tracks whether a permission was granted, rejected, etc. The suffix of the
histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
miguelg@chromium.org
mlamouri@chromium.org
Tracks whether a permission was granted, rejected, etc on an insecure
origin. The suffix of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
miguelg@chromium.org
mlamouri@chromium.org
Tracks whether a permission was granted, rejected, etc on a secure origin.
The suffix of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
For every permission request that would show a prompt to the user, this
metric tracks whether the request is suppressed by embargo (and the source
of that embargo), or whether there is no embargo and the prompt is shown.
This is the proportion of permission prompts that the user would have seen
that have been blocked due to embargo.
If the (origin, permission) pair was previously placed under embargo, no
prompt is displayed and the reason for embargo is recorded. Otherwise, the
prompt is shown and a no embargo reason is recorded.
dominickn@chromium.org
kcarattini@chromium.org
Tracks the reason that an (origin, permission) pair has been placed under
embargo (blocked from making requests for that permission for a period of
time). This is triggered when a permission is placed under embargo for
blacklisting (once Safe Browsing has returned a result), when a permission
prompt has been shown and it is placed under embargo for repeated
dismissals, or when a permission prompt is shown and not embargoed.
Permission blacklisting was removed in M67.
dominickn@chromium.org
kcarattini@chromium.org
Tracks the response (if received) from Safe Browsing when the API blacklist
is queried for an (origin, permission) pair. The response could be that the
origin was blacklisted, not blacklisted, or Safe Browsing timed out before a
response was received.
Permission blacklisting was removed in M67.
dominickn@chromium.org
kcarattini@chromium.org
Records the elapsed time between the client sending a request to Safe
Browsing and receiving a result, or the maximum wait time is exceeded and
Safe Browsing is deemed to have timed out.
timloh@chromium.org
Battery percentage when a geolocation permission prompt was accepted on
Android.
timloh@chromium.org
Battery percentage when a location settings dialog was accepted.
timloh@chromium.org
Battery percentage when a geolocation permission prompt was denied on
Android.
timloh@chromium.org
Battery percentage when a location settings dialog was denied.
timloh@chromium.org
Battery percentage when a geolocation permission prompt was dismissed on
Android.
dominickn@chromium.org
kcarattini@chromium.org
timloh@chromium.org
Tracks the engagement score for sites where permission prompts are accepted.
dominickn@chromium.org
kcarattini@chromium.org
timloh@chromium.org
Tracks the engagement score for sites where permission prompts are denied.
dominickn@chromium.org
kcarattini@chromium.org
timloh@chromium.org
Tracks the engagement score for sites where permission prompts are
dismissed.
dominickn@chromium.org
kcarattini@chromium.org
timloh@chromium.org
Tracks the engagement score for sites where permission prompts are ignored.
dominickn@chromium.org
kcarattini@chromium.org
Tracks the permission bubbles (merged and non-merged) that are accepted.
Merged bubbles are considered accepted if all permissions are allowed.
Persist toggle experiments ran from M56 to M59.
dominickn@chromium.org
kcarattini@chromium.org
For each granted permission prompt displayed with a persistence toggle
(remember my decision), records whether the persistence toggle was enabled
(persist) or not enabled (don't persist).
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt accept, records the
total number of prompt dismissal events for this origin since the last time
the user cleared their history or site data and prior to the accept. The
suffix of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt accept, records the
total number of prompt ignore events for this origin since the last time the
user cleared their history or site data and prior to the accept. The suffix
of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
Tracks the permission bubbles (merged and non-merged) that are denied.
Merged bubbles are considered denied if any permission is denied.
Persist toggle experiments ran from M56 to M59.
dominickn@chromium.org
kcarattini@chromium.org
For each denied permission prompt displayed with a persistence toggle
(remember my decision), records whether the persistence toggle was enabled
(persist) or not enabled (don't persist).
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt deny, records the
total number of prompt dismissal events for this origin since the last time
the user cleared their history or site data and prior to the accept. The
suffix of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt deny, records the
total number of prompt ignore events for this origin since the last time the
user cleared their history or site data and prior to the accept. The suffix
of the histogram indicates which particular permission.
Renamed to Permissions.Prompt.Dismissed.PriorDismissCount on 17 August 2016.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt dismissal, records
the total number of prompt dismissal events for this origin since the last
time the user cleared their history or site data, inclusive of the current
dismissal. Every event in a bucket larger than 1 in this histogram will also
have an event in each smaller bucket. The suffix of the histogram indicates
which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt dismiss, records
the total number of prompt dismissal events for this origin since the last
time the user cleared their history or site data and prior to the dismiss.
The suffix of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt dismiss, records
the total number of prompt ignore events for this origin since the last time
the user cleared their history or site data and prior to the dismiss. The
suffix of the histogram indicates which particular permission.
Renamed to Permissions.Prompt.Dismissed.PriorDismissCount on 17 August 2016.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt ignore, records the
total number of prompt ignore events for this origin since the last time the
user cleared their history or site data, inclusive of the current ignore.
Every event in a bucket larger than 1 in this histogram will also have an
event in each smaller bucket. The suffix of the histogram indicates which
particular permission.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt ignore, records the
total number of prompt dismissal events for this origin since the last time
the user cleared their history or site data and prior to the ignore. The
suffix of the histogram indicates which particular permission.
dominickn@chromium.org
kcarattini@chromium.org
This metric, recorded at the time of a permission prompt ignore, records the
total number of prompt ignore events for this origin since the last time the
user cleared their history or site data and prior to the ignore. The suffix
of the histogram indicates which particular permission.
Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same
counts are available in Permissions.Prompt.Accepted.
dominickn@chromium.org
kcarattini@chromium.org
Tracks acceptance of permission bubble request types that have been merged
into coalesced bubbles.
Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same
counts are available in Permissions.Prompt.Denied.
dominickn@chromium.org
kcarattini@chromium.org
Tracks denial of permission bubble request types that have been merged into
coalesced bubbles.
Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same
counts are available in Permissions.Prompt.Shown.
dominickn@chromium.org
kcarattini@chromium.org
Tracks the permission bubble request types that are being merged into
coalesced bubbles.
Redundant since M61 (bug 728483) as we now only merge Mic+Camera. The same
counts are available in Permissions.Prompt.Shown.
dominickn@chromium.org
kcarattini@chromium.org
How many permission requests each permissions prompt shown to the user
contains.
dominickn@chromium.org
kcarattini@chromium.org
Tracks how many times permission prompts are shown to users.
Deprecated 02/2017, no longer used
dominickn@chromium.org
kcarattini@chromium.org
keenanb@google.com
jww@chromium.org
The embedder's permission setting at the time of a cross-origin iframe
permission request for a given permission type. See the corresponding
histogram suffixes.
A request is when a website makes a permission request and the user has the
permission set to prompt (i.e. not blocked or allowed).
Note this is probably not the metric you want - it does not correspond to
the total number of times websites request a permission. Also, because
specific permissions have code that can automatically block or grant
permissions based on things like incognito, installed extensions etc., this
does also not correspond to the number of times users are prompted to allow
permissions.
See https://crbug.com/638076 for more details.
Deprecated 02/2017, no longer used
dominickn@chromium.org
kcarattini@chromium.org
keenanb@google.com
jww@chromium.org
The permission type (geolocation, and such) of a same-origin permission
request.
A request is when a website makes a permission request and the user has the
permission set to prompt (i.e. not blocked or allowed).
Note this is probably not the metric you want - it does not correspond to
the total number of times websites request a permission. Also, because
specific permissions have code that can automatically block or grant
permissions based on things like incognito, installed extensions etc., this
does also not correspond to the number of times users are prompted to allow
permissions.
See https://crbug.com/638076 for more details.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Referer used by user to reach the main Physical Web Activity.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Initial state of the Physical Web in Chrome for iOS.
Deprecated 01/2017, no longer used
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Time between the most recent opt in notification update and when the user
arrives at the ListUrlsActivity.
Deprecated 01/2017, no longer used
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Time between the most recent standard notification update and when the user
arrives at the ListUrlsActivity.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Round trip time to the metadata server for a Physical Web URL resolution
which the client requests during a background scan.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Round trip time to the metadata server for a Physical Web URL resolution
which the client requests during a foreground scan, that is not explicitly
requested via a refresh.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Round trip time to the metadata server for a Physical Web URL resolution
which the client requests during a foreground scan, that is explicitly
requested via a refresh.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
olivierrobin@chromium.org
Round trip time to the metadata server for Physical web.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Whether bluetooth is on, off, or unknown.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Whether the data connection is active.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Whether location permission has been accepted.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Whether location services are enabled.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Whether the preference is on, off, or if the user is in an onboarding state
when Chrome first starts up.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
The number of URLs displayed to a user when a list of nearby URLs is first
displayed.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
The number of URLs displayed to a user when a list of nearby URLs is
displayed after refreshing.
Obsolete 4/2018, Physical Web is disabled (crbug.com/826540).
cco3@chromium.org
mattreynolds@chromium.org
mmocny@chromium.org
Count of how many times the user selected a nearby URL at the specified
index in the Physical Web WebUI list view (zero-based). Capped at 50.
semenzato@chromium.org
bsimonnet@chromium.org
Count of crashes (user, kernel, and unclean shutdowns) during the previous
day, or the most recent day the device was in use. Reported at most once a
day.
semenzato@chromium.org
bsimonnet@chromium.org
Count of crashes (user, kernel, and unclean shutdowns) during the previous
epoch-week, or the most recent epoch-week the device was in use. Reported
at most once a week. Epoch-weeks divide the time in 7-day intervals
starting at the UNIX epoch.
Please list the metric's owners. Add more owner tags as needed.
Chrome OS (ARM Chromebooks using Exynos 5250 only) Adaptive Support Voltage
Group, recorded once per bootup. Indicates which "bin" the SoC is
part of, which sets the voltage that different rails on the system will run
at. The values 0-11 are valid. A value of 12 indicates an error parsing
dmesg and should be investigated. See also Platform.LotIdEnum.
cernekee@chromium.org
Indicates whether the kernel's ACPI Smart Battery System driver logged an
error trying to find the battery on boot.
mnissler@chromium.org
Indicates the status of the developer switch on Chrome OS hardware. The
developer switch allows users to run their own code on the device.
mnissler@chromium.org
On Chrome OS hardware, indicates whether flash write protection is enabled
for the firmware indicated by the histogram suffix.
mnissler@chromium.org
Indicates the status of the hardware write protect switch on Chrome OS
hardware. The write protect switch protects firmware from being rewritten.
sonnyrao@chromium.org
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.
halliwell@chromium.org
/proc/meminfo's 'MemAvailable' in Mbytes. Collected on Cast devices with
kernel version 3.14 and above and capped at 500.
halliwell@chromium.org
free + buffers + cache memory in Mbytes on Cast devices, capped at 500.
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.
vbendeb@chromium.org
A sparse histogram of values of Board ID flags programmed in H1 devices in
the field. Board ID flags is a 32 bit field, and while there only are a few
expected values, conceivably any bit combination could be encountered.
vbendeb@chromium.org
A sparse histogram of values indexed by 4 byte Board ID code programmed in
H1 reported by devices where there is a mismatch between the RLZ code and
the Board ID value programmed in the H1.
vbendeb@chromium.org
A sparse histogram of values indexed by 4 byte Board ID code programmed in
H1, reported by devices where there is no mismatch between the RLZ code and
the Board ID value.
vbendeb@chromium.org
A sparse histogram of values indexed by 4 byte RLZ code reported by devices
where there is a mismatch between the RLZ code and the Board ID value
programmed in the H1. Since RLZ code could be misprogrammed, a sparse
histogram is used to allow keeping track of outliers.
dkrahn@chromium.org
jwerner@chromium.org
vapier@chromium.org
Generic event of interest from Chrome OS. Intended mainly to help assess
the frequency of rare error conditions.
drinkcat@chromium.org
Detects presence of /run/crouton, indicating that crouton has been started
since the previous boot. Value 0/"Total count" is reported on
boot, 1/"Started" is reported after the file presence is detected
(checked periodically).
semenzato@chromium.org
bsimonnet@chromium.org
Total CPU time accumulated since the last version update. Reported at most
once a day.
semenzato@chromium.org
bsimonnet@chromium.org
Total use time (device ON and not asleep) since last version update.
Reported at most once a day.
semenzato@chromium.org
bsimonnet@chromium.org
Total use time (device ON and not asleep) in the previous day, or the most
recent day the device was in use. Reported at most once a day.
kitching@google.com
Ratio of time a detachable base keyboard is active, i.e. when the USB
interface is not auto-suspended. Reported every 30 seconds when the base is
connected.
kitching@google.com
For devices with a detachable base: whether or not the base is connected on
boot. Recorded by upstart task on boot.
kitching@google.com
Result of a detachable base pair operation.
kitching@google.com
Detachable base firmware updates can be configured to only occur on boot. In
this mode, any update will be considered "pending" until the
system is rebooted, at which point the update may take place. Every time a
detachable base is connected to the system, a metric representing the
pending update status is recorded. Its possible values are as follows: (0)
communication error; (1) no update available; (2) critical update available;
or (3) non-critical update available. The definition of
"critical" is up to the software performing updates, and would
typically be used in the case of a security issue, or broken functionality
in a previous firmware version.
kitching@google.com
Result of a detachable base RO firmware update.
kitching@google.com
Result of a detachable base RW firmware update.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Average size of user's Cache directory. Logged once a day, if disk usage is
high.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Maximum size of user's Cache directory. Logged once a day, if disk usage is
high.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Average size of user's Cache directory. Logged once a day, if disk usage is
high.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Maximum size of user's Cache directory. Logged once a day, if disk usage is
high.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Average size of user's GCache directory. Logged once a day, if disk usage is
high.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Maximum size of user's GCache directory. Logged once a day, if disk usage is
high.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Days since the least frequently used account signed in. Logged once a day,
if disk usage is high.
achuith@chromium.org
tls@chromium.org
Number of users home directories on the device. Logged once a day.
achuith@chromium.org
omrilio@chromium.org
Days since last login of the least recently user on device. Logged once a
day, if disk usage is high.
achuith@chromium.org
omrilio@chromium.org
Number of user home dirs on device. Logged once a day, if disk usage is
high.
keescook@google.com
Chrome OS KB in use in the /home/chronos filesystem tree. Logged once a day
during log file cleanup.
keescook@google.com
Chrome OS KB in use in the /var filesystem tree. Logged once a day during
log file cleanup.
gwendal@google.com
eMMC [5.0] Device life time estimation for flash. This field provides an
estimated indication about the device life time that is reflected by the
averaged wear out of memory of a given type relative to its maximum
estimated lifetime.
gwendal@google.com
Number of file system errors, as reported by dumpe2fs "FS Error
count" field. Reported once per boot.
gwendal@google.com
True when kernel reports that the file system needs deep recovery. File
system has corruption the kernel can not fix by itself. Reported once per
boot.
gwendal@google.com
True when kernel reports that the file system needed recovery at boot. It
indicates the filesytem was not properly unmounted, but was recovered.
Reported once per boot.
fbarchard@chromium.org
The maximum supported micro-architecture on an Intel platform. This value
is logged at program start time.
semenzato@chromium.org
bsimonnet@chromium.org
Count of kernel crashes during the previous day, or the most recent day the
device was in use. Reported at most once a day.
semenzato@chromium.org
bsimonnet@chromium.org
Count of kernel crashes since the last OS update, normalized as number of
crashes per year of active use (active use = device is ON and not asleep).
Reported daily.
semenzato@chromium.org
bsimonnet@chromium.org
Count of kernel crashes since the last OS update, normalized as number
crashes per year of CPU time. Reported daily.
semenzato@chromium.org
bsimonnet@chromium.org
Count of kernel crashes since the last OS update, reported daily.
semenzato@chromium.org
bsimonnet@chromium.org
Count of kernel crashes during the previous epoch-week, or the most recent
epoch-week the device was in use. Reported at most once a week. Epoch-weeks
divide the time in 7-day intervals starting at the UNIX epoch.
semenzato@chromium.org
bsimonnet@chromium.org
Time elapsed between the last two kernel crashes. Sent after every kernel
crash.
Please list the metric's owners. Add more owner tags as needed.
The 32-bit hash of a kernel warning. This is the hash of the
"file:line" string corresponding to the location of the warning,
for instance: "/mnt/host/source/src/third_party/kernel/files/drivers
/gpu/drm/i915/intel_dp.c:351" (ignore spurious spaces). The hash is
produced by this code: while (*string) hash = (hash << 5) + hash +
*string++; Separately each warning is also collected (with its hash) via
the crash reporter, but only its first occurrence in each boot session.
sonnyrao@chromium.org
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
semenzato@chromium.org
bccheng@chromium.org
Various memory usage % of total memory on Chrome OS devices (snapshotted
every 30s).
hajimehoshi@chromium.org
kouhei@chromium.org
sonnyrao@chromium.org
semenzato@chromium.org
bccheng@chromium.org
Various memory usage amount on Chrome OS devices (snapshotted every 30s).
hajimehoshi@chromium.org
kouhei@chromium.org
cast-analytics@google.com
Peak memory bandwith (read and write) usage during the last sample interval.
The sample interval may vary from seconds to several minutes.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory 1
minute after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory 5
minutes after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory 30
minutes after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory
150 minutes after boot.
hajimehoshi@chromium.org
kouhei@chromium.org
Chrome OS total anonymous memory (active + inactive) as % of total memory
750 minutes after boot.
apronin@chromium.org
mnissler@chromium.org
File system encryption key status for the encrypted stateful file system on
Chrome OS. The encryption key is the one that is used by the kernel to
protect actual file contents on disk.
apronin@chromium.org
mnissler@chromium.org
Type/Origin of the system key used for the encrypted stateful file system on
Chrome OS. This key is used to wrap the actual file system encryption key.
sonnyrao@chromium.org
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)
ddavenport@chromium.org
The 32-bit hash of the name of the service that failed. The name of the
service is hashed using the same algorithm as used for the hashes in
Platform.KernelWarningHashes. The first instance of each service failure is
also collected separately via the crash reporter.
gwendal@google.com
Disk communication errors (SMART 199), sent at boot.
gwendal@google.com
Uncorrectable disk errors (SMART 187), sent at boot.
vpalatin@google.com
USB device ID of the charger plugged into a Spring device (if any), sent
once a minute. The Device ID is composed from the following 4 8-bit
registers of the TSU6721 chip: ADC (07h), Device Type 3 (15h), Device Type 2
(0Bh), Device Type 1 (0Ah). Device Type 1/2/3 is a bitmap and most of bits
are mutually exclusive (excepted VBUS debounce). ADC is the 5-bit value of
the ID pin, but for most types (as in Device Type), there are only one or
two possible ID pin connections/values. The datasheet can be found here:
http://www.ti.com/lit/ds/symlink/tsu6721.pdf.
Note that different brand/models of the charger can have the same ID.
achuith@chromium.org
omrilio@chromium.org
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Page faults/second for the specified swap group and time interval after a
scroll event. See src/chrome/browser/chromeos/swap_metrics.cc.
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 Chrome OS.
mka@chromium.org
Temperature reading at wireless interface 0 collected every few seconds (may
vary between devices).
This metric is specific to Chrome OS.
mka@chromium.org
Temperature reading at wireless interface 1 collected every few seconds (may
vary between devices).
This metric is specific to Chrome OS.
mka@chromium.org
Temperature reading at wireless interface 2 collected every few seconds (may
vary between devices).
This metric is specific to Chrome OS.
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 Chrome OS.
mka@chromium.org
State of the thermal zone of wireless interface 0 collected every second.
State depends on device, higher state corresponds to a higher temperature.
This metric is specific to Chrome OS.
mka@chromium.org
State of the thermal zone of wireless interface 1 collected every second.
State depends on device, higher state corresponds to a higher temperature.
This metric is specific to Chrome OS.
mka@chromium.org
State of the thermal zone of wireless interface 2 collected every second.
State depends on device, higher state corresponds to a higher temperature.
This metric is specific to Chrome OS.
semenzato@chromium.org
Each sample is the result code of a TPM authorized command issued through
tcsd. Success is 0. For the other error codes, see
/usr/include/tss/tpm_error.h.
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.
mnissler@chromium.org
Number of attempts until a successful TPM firmware update. This is the total
sum of attempts, i.e. number of failed attempts + 1 for the final successful
attempt. Note that we're not in a position to report UMA after failed
attempts, so this will only be reported by devices that eventually see a
successful attempt.
mnissler@chromium.org
Status of a complete TPM firmware update attempt.
mnissler@chromium.org
Exit status of the TPM firmware updater script.
anatol@google.com
Trusted Platform Module hardware alerts that signal about the chip abnormal
situation.
mnissler@chromium.org
Indicates a fingerprint of hardware + firmware versions for the TPM chip
present in a Chrome OS device.
dkrahn@chromium.org
Each sample is the number of consecutive reboots performed while attempting
to clear a TPM (Trusted Platform Module) error.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Retries needed to enable a FET on tps65090 (AKA tpschrome). Tps65090 is a
power management unit (PMU) used on many ARM Chromebooks. Until version ES7
was rolled into production we would sometimes run into a problem where FET1
(the FET used to switch on and off the backlight) wouldn't turn on properly.
This problem was especially prevalent when the voltage was high (like when
the device was plugged into the wall). Retrying by turning the FET off and
on again is nearly always effective, so the kernel will retry up to 5 times
(currently) and will also log the fact that it needed to retry. On newest
kernels (kernel 3.8 and up) a kernel warning will be logged with WARN_ON if
the FET still failed to turn on after 5 tries. Refer to the kernel warning
reports to find that information. For more details about this bug refer to
http://crbug.com/338657 and http://crosbug.com/p/16009. Note that we log
retries on all 7 FETs even though we've only ever seen failures of FET1.
semenzato@chromium.org
bsimonnet@chromium.org
Count of crashes (unclean shutdown) during the previous day, or the most
recent day the device was in use. Reported at most once a day.
semenzato@chromium.org
bsimonnet@chromium.org
Count of crashes (user) during the previous day, or the most recent day the
device was in use. Reported at most once a day.
tnagel@chromium.org
Number of unknown RW_VPD entries on Chrome OS, sent once per boot.
cernekee@chromium.org
semenzato@chromium.org
Sample collected 10s after boot, showing how many WiFi interfaces are
present.
rajatja@chromium.org
kirtika@chromium.org
Shows the wifi status after the pci bus is rescanned to recover wifi. The UI
depends on shill noticing that wlan0 is back up, so the only happy case is
one where shill recognizes wlan0 after the rescan completes.
gwendal@google.com
Number of disk sectors per second written by Chrome OS in a long interval
(currently 30s)
gwendal@google.com
Number of disk sectors per second written by Chrome OS in a short interval
(currently 1s, sampled every 30s)
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.
Deprecated as of 2016-07 because the histogram's purpose of adding colour to
the description of File::Flush() has been fulfilled.
tnagel@chromium.org
The time it takes to run File::Flush().
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.
Use PageLoad.Timing2.NavigationToCommit instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "begin" to "commit." "Begin"==
"request" if user requested, and "start" otherwise.
"Request"== time when user requested document. "Start"==
time when renderer requested load of document, after any unload of last
document. "Commit"== time when renderer got first byte of
document.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
Please list the metric's owners. Add more owner tags as needed.
TBD
Deprecated as of http://crrev.com/392823002
kouhei@chromium.org
PLT.BeginToFinish, but for pages requested just after a new preconnect
request.
No longer needed.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinish, but for pages which contained prefetch links.
No longer needed.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinish, but for pages which were referred to by pages which
contained prefetch links.
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.
No longer 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.
No longer 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.
No longer 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.
No longer 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.
Use PLT.PT_BeginToFinish_DataReductionProxy instead.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinish, but for pages fetched over a SPDY proxy.
Use PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired instead.
Please list the metric's owners. Add more owner tags as needed.
TBD
Deprecated as of http://crrev.com/392823002
kouhei@chromium.org
PLT.BeginToFinishDoc, but for pages requested just after a new preconnect
request.
No longer needed.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinishDoc, but for pages which contained prefetch links.
No longer needed.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinishDoc, but for pages which were referred to by pages which
contained prefetch links.
Use PLT.PT_BeginToFinishDoc_DataReductionProxy instead.
Please list the metric's owners. Add more owner tags as needed.
PLT.BeginToFinshDoc, but for pages fetched over a SPDY proxy.
Use PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead.
pmeenan@chromium.org
Time from "begin" to "first paint." "Begin"==
"request" if user requested, and "start" otherwise.
"Request"== time when user requested document. "Start"==
time when renderer requested load of document, after any unload of last
document. "First paint"== time when first paint operation was
performed.
No longer needed.
bmcquade@chromium.org
Magnitude and difference between begin and first paint, when first_paint
precedes begin. This is a temporary metric used to better understand the
root cause of http://crbug.com/125273.
The first paint after load is not useful for most documents. Consider using
PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead.
pmeenan@chromium.org
Time from "big" to "first paint after load."
"Begin"== "request" if user requested, and
"start" otherwise. "Request"== time when user requested
document. "Start"== time when renderer requested load of document,
after any unload of last document. "First paint after load"== time
after onload() when first paint operation is performed.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "finish." "Commit"==
time when renderer got first byte of document. "Finish"==after
onload() and all resources are loaded.
Use PageLoad.ParseTiming.ParseDuration instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "finish doc." "Commit"==
time when renderer got first byte of document. "Finish doc" ==
main document loaded, before onload(). "Finish"==after onload()
and all resources are loaded.
Use PageLoad.PaintTiming.ParseStartToFirstContentfulPaint instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "first paint."
"Commit"== time when renderer got first byte of document.
"First paint"== time when first paint operation was performed.
The first paint after load is not useful for most documents. Consider using
PageLoad.PaintTiming.ParseStartToFirstContentfulPaint instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "commit" to "first paint after load."
"Commit"== time when renderer got first byte of document.
"First paint after load"== time after onload() when first paint
operation is performed.
No longer needed.
Please list the metric's owners. Add more owner tags as needed.
Time from "finish doc" to "finish." "Finish
doc"== main document loaded, before onload(). "Finish"==after
onload() and all resources are loaded.
The first paint after load is not useful for most documents. Consider using
PageLoad.PaintTiming.NavigationToFirstContentfulPaint instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "finish " to "first paint after load."
"Finish"==after onload() and all resources are loaded. "First
paint after load"== time after onload() when first paint operation is
performed.
Use PageLoad.PaintTiming.NavigationToFirstContentfulPaint.LoadType.*
instead.
Please list the metric's owners. Add more owner tags as needed.
Probability distribution for enumerated varieties of page loads.
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/
Deprecated 09/2016.
bolian@chromium.org
Time from connectStart to connectEnd based on Navigation Timing.
Deprecated as of 7/19/2016.
bolian@chromium.org
Time from domanLookupEnd to connectStart based on Navigation Timing.
Deprecated as of 7/19/2016.
bolian@chromium.org
Time from fetchStart to domainLookupStart based on Navigation Timing.
Deprecated as of 7/19/2016. Replaced by
PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired.
bolian@chromium.org
Time from responseStart to domLoading based on Navigation Timing.
Deprecated as of 7/19/2016.
bolian@chromium.org
Time from navigationStart to fetchStart based on Navigation Timing when no
redirect.
Deprecated as of 7/19/2016.
bolian@chromium.org
Time from navigationStart to fetchStart excluding time spent on redirects
based on Navigation Timing. Only page loads with redirects are considered.
Deprecated as of 7/19/2016. Replaced by
PageLoad.DocumentTiming.NavigationToLoadEventFired.
bolian@chromium.org
Time from domContentLoadedEventEnd to loadEventStart based on Navigation
Timing.
Deprecated as of 7/19/2016.
bolian@chromium.org
Time from connectEnd to requestStart based on Navigation Timing.
Deprecated 09/2016.
bolian@chromium.org
Time from domainLookupStart to domainLookupEnd based on Navigation Timing.
Deprecated 09/2016. Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToDOMContentLoadedEventFired
instead.
bolian@chromium.org
Time from domContentLoadedEventStart to domContentLoadedEventEnd based on
Navigation Timing.
Deprecated 09/2016.
bolian@chromium.org
Time from domInteractive to domContentLoadEventStart based on Navigation
Timing.
Deprecated 09/2016.
bolian@chromium.org
Time from domLoading to domInteractive based on Navigation Timing.
Deprecated 09/2016. Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired
instead.
bolian@chromium.org
Time from loadEventStart to loadEventEnd based on Navigation Timing.
Deprecated as of 7/19/2016.
bolian@chromium.org
Time from redirectStart to redirectEnd based on Navigation Timing when
redirects exist.
Deprecated as of 7/19/2016. Replaced by
PageLoad.ParseTiming.NavigationToParseStart.
bolian@chromium.org
Time from requestStart to responseStart based on Navigation Timing.
Deprecated as of 7/19/2016. Replaced by PageLoad.ParseTiming.ParseDuration.
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.
Deprecated. Use PageLoad.Timing2.* instead.
bmcquade@chromium.org
Measures the time from navigation timing's navigation start to the time the
first document layout is performed.
Deprecated. Use PageLoad.Timing2.* instead.
bmcquade@chromium.org
Measures the time from navigation timing's response start to the time the
first document layout is performed.
Use PageLoad.Timing2.NavigationToCommit instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or
navigationStart if user-initiated request.
Deprecated 9/2016. Use Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToCommit
instead.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.BeginToCommit. Commit: responseStart. Begin: requestStart or
navigationStart if user-initiated request. Only page loads through the data
reduction proxy are considered.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.BeginToFinish. Finish: loadEventEnd. Begin: requestStart or
navigationStart if user-initiated request.
Deprecated 9/2016. Use Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired
instead.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.BeginToFinish_SpdyProxy. Finish: loadEventEnd. Begin:
requestStart or navigationStart if user-initiated request. Only page loads
through the data reduction proxy are considered.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.BeginToFinishDoc. FinishDoc: loadEventStart. Begin:
requestStart or navigationStart if user-initiated request.
Deprecated 09/2016. Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired
instead.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.BeginToFinishDoc_SpdyProxy. FinishDoc: loadEventStart. Begin:
requestStart or navigationStart if user-initiated request. Only page loads
through the data reduction proxy are considered.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd.
Deprecated 09/2016. Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired
instead.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.CommitToFinish. Commit: responseStart. Finish: loadEventEnd.
Only page loads through the data reduction proxy are considered.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc:
loadEventStart.
Deprecated 09/2016. Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired
instead.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.CommitToFinishDoc. Commit: responseStart. FinishDoc:
loadEventStart. Only page loads through the data reduction proxy are
considered.
No longer needed.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc:
loadEventStart.
Deprecated 09/2016.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.FinishDocToFinish. Finish: loadEventEnd. FinishDoc:
loadEventStart. Only page loads through the data reduction proxy are
considered.
Use PageLoad.Timing2.NavigationToCommit instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and measures the time until
the renderer got first byte of document. Commit: time when renderer got
first byte of document. Request: navigationStart.
Use PageLoad.DocumentTiming.NavigationToDOMContentLoadedEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and measures the time until
the beginning of the DOMContentLoaded event. DOMContentLoaded:
domContentLoadedEventStart. Request: navigationStart.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.RequestToFinish. Finish: loadEventEnd. Request:
navigationStart.
Deprecated 09/2016. Use
PageLoad.Clients.DataReductionProxy.DocumentTiming.NavigationToLoadEventFired
instead.
pmeenan@chromium.org
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.RequestToFinish. Finish: loadEventEnd. Request:
navigationStart. Only page loads through the data reduction proxy are
considered.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
pmeenan@chromium.org
This time is based on the NavigationTiming spec and measures the page load
time until the beginning of the load event. Finish: loadEventStart. Request:
navigationStart.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.RequestToStart. Start: requestStart. Request:
navigationStart.
Deprecated 09/2016.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.RequestToStart. Start: requestStart. Request:
navigationStart. Only page loads through the data reduction proxy are
considered.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.StartToCommit. Start: requestStart. Commit: responseStart.
Deprecated 09/2016.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.StartToCommit. Start: requestStart. Commit: responseStart.
Only page loads through the data reduction proxy are considered.
Please list the metric's owners. Add more owner tags as needed.
This time is based on the NavigationTiming spec and is a more accurate
version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd.
Deprecated 09/2016.
bengr@chromium.org
megjablon@chromium.org
This time is based on the PerformanceTiming spec and is a more accurate
version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd.
Only page loads through the data reduction proxy are considered.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "request" to "finish." "Request" ==
time when user requested document. "Finish" == after onload() and
all resources are loaded.
Please list the metric's owners. Add more owner tags as needed.
Time from "request" to "start." "Request"==
time when user requested document. "Start"== time when renderer
requested load of document, after any unload of last document.
Use PageLoad.Timing2.NavigationToCommit instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "start" to "commit." "Start"== time
when renderer requested load of document, after any unload of last document.
"Commit"== time when renderer got first byte of document.
Use PageLoad.DocumentTiming.NavigationToLoadEventFired instead.
Please list the metric's owners. Add more owner tags as needed.
Time from "start" to "finish." "Start"== time
when renderer requested load of document, after any unload of last document.
"Finish"==after onload() and all resources are loaded.
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.
Deprecated as of 09/2016.
pmeenan@chromium.org
This time is based on the User Timing spec and measures the time from
Navigation Timing navigationStart until the point where the page called
performance.mark().
Deprecated as of 09/2016.
pmeenan@chromium.org
This time is based on the User Timing spec and reports the time between two
arbitrary points defined by the page being loaded and directly matches the
measurement exposed by performance.measure().
Deprecated as of 01/2017 (M65).
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).
pastarmovj@chromium.org
tommycli@chromium.org
Tracks whether plugins that were disabled were migrated.
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.
Deprecated 12/2017 in Issue 781644 as we no longer use Site Engagement Index
as a signal for Flash display.
dominickn@chromium.org
The engagement score of origins which have passed through a site engagement
check to permit or block Flash. Recorded every time the Flash plugin is
requested with the PreferHtmlOverPlugins feature active.
tommycli@chromium.org
Collects the sizes of all loaded Flash plugin instances. This is for
determining the prevalence of tiny flash plugin instances.
mlamouri@chromium.org
kdsilva@google.org
Records the YouTube Flash embed rewrite status when attempted.
Please list the metric's owners. Add more owner tags as needed.
Record usage of PPB_Flash.Navigate() Pepper API.
yzshen@chromium.org
thestig@chromium.org
Collects Flash usage data.
Deprecated due to NPAPI removal.
wfh@chromium.org
The plugin group of an NPAPI plugin that is no longer supported. Recorded
when the NPAPI removal infobar is shown for a plugin which is no longer
supported.
Deprecated due to NPAPI removal.
wfh@chromium.org
The plugin group of an NPAPI plugin that will be unsupported soon. Recorded
when the NPAPI removal infobar is shown after an NPAPI plugin first loads to
warn the user that NPAPI support for this plugin will be removed soon.
Deprecated due to NPAPI removal.
wfh@chromium.org
Records whether NPAPI plugins are supported by the platform, and if so,
whether they are enabled or disabled. Recorded once at browser startup.
Deprecated in favor of Plugin.PowerSaver.PeripheralHeuristicInitialDecision.
tommycli@chromium.org
Records each decision of the Plugin Power Saver peripheral content
heuristic. This UMA is counted once per peripheral query, and may count a
single plugin instance multiple times as it is resized.
tommycli@chromium.org
Records the initial decision of the Plugin Power Saver peripheral content
heuristic for each plugin instance. This is recorded once per plugin
instance.
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. Only reported on Windows.
xhwang@chromium.org
The result from an attempt to load a PPAPI broker.
xhwang@chromium.org
The time spent to load a PPAPI broker.
xhwang@chromium.org
The error code of a PPAPI plugin load failure. Only reported on Windows.
xhwang@chromium.org
The result from an attempt to load a PPAPI plugin.
xhwang@chromium.org
The time spent to load a PPAPI plugin.
gab@chromium.org
The time it took to complete a synchronous IPC made from the PPAPI process.
mlamouri@chromium.org
Result of HTMLPluginElement::requestObject in Blink.
Deprecated due to NPAPI removal.
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.
Deprecated 02/2017 in favor of power benchmarks that have less variability
than data from users' machines.
jeremy@chromium.org
The percentage of battery capacity used per hour relative to a full
battery. Reported once when the power adaptor is plugged back in after the
system is on battery power for more than 30 minutes. If at any point the
system is suspended or all Chrome renderers are closed the measurement is
not recorded. Anytime the user unplugs the power adaptor, a new measurement
will begin being recorded. Collection of this histogram only starts after 30
minutes of uptime at which point the clock starts (assuming the user is on
battery power at that point). The system will need to remain unplugged for
at least another 30 minutes in order for any measurement to be recorded.
Values are normalized to a percent per hour scale. This measurement is tied
tightly to hardware model/OS and is not comparable across different hardware
configurations.
derat@chromium.org
Chrome OS battery discharge rate in mW sampled every 30 seconds while the
device runs on battery.
Deprecated 02/2017 in favor of power benchmarks that have less variability
than data from users' machines.
jeremy@chromium.org
The percent of depleted battery capacity relative to a full battery over
the first 15 minutes after battery power collection information starts.
Collection of this histogram only starts after 30 minutes of uptime at which
point the clock starts (assuming the user is on battery power at that
point). The system will need to remain unplugged for at least another 15
minutes in order for any measurement to be recorded. Values are normalized
to a percent per hour scale. This measurement is tied tightly to hardware
model/OS and is not comparable across different hardware configurations.
Deprecated 02/2017 in favor of power benchmarks that have less variability
than data from users' machines.
jeremy@chromium.org
The percent of depleted battery capacity relative to a full battery over
the first 30 minutes after battery power collection information starts.
Collection of this histogram only starts after 30 minutes of uptime at which
point the clock starts (assuming the user is on battery power at that
point). The system will need to remain unplugged for at least another 30
minutes in order for any measurement to be recorded. Values are normalized
to a percent per hour scale. This measurement is tied tightly to hardware
model/OS and is not comparable across different hardware configurations.
Deprecated 02/2017 in favor of power benchmarks that have less variability
than data from users' machines.
jeremy@chromium.org
The percent of depleted battery capacity relative to a full battery over
the first 5 minutes after battery power collection information starts.
Collection of this histogram only starts after 30 minutes of uptime at which
point the clock starts (assuming the user is on battery power at that
point). The system will need to remain unplugged for at least another 5
minutes in order for any measurement to be recorded. Values are normalized
to a percent per hour scale. This measurement is tied tightly to hardware
model/OS and is not comparable across different hardware configurations.
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.
bleung@chromium.org
derat@chromium.org
Connected charging ports on Chrome OS. A sample is reported every time that
the power manager polls sysfs (typically every 30 seconds). Ordinals are
assigned based on the lexicographical ordering of power supply names from
sysfs and have no implied correspondence with ports' physical locations. For
example, with ports 'CROS_USB_PD_CHARGER0' and 'CROS_USB_PD_CHARGER1',
'first' refers to the former and 'second' to the latter. To determine a
port's physical location, see the powerd charging_ports pref in the device's
overlay.
chirantan@chromium.org
The amount of time a system spent awake every time it woke up in dark
resume.
chirantan@chromium.org
samueltan@chromium.org
The amount of time a system spent awake every time it woke up in dark resume
triggered by an unknown or unsupported wake trigger.
chirantan@chromium.org
samueltan@chromium.org
The amount of time a system spent awake every time it woke up in dark resume
triggered by a WiFi disconnect.
chirantan@chromium.org
samueltan@chromium.org
The amount of time a system spent awake every time it woke up in dark resume
triggered by a WiFi packet pattern match.
chirantan@chromium.org
samueltan@chromium.org
The amount of time a system spent awake every time it woke up in dark resume
triggered by a net detect SSID match.
chirantan@chromium.org
The number of times a system woke up in dark resume in an hour. Note that
this value is scaled up or down to an hour based on the amount of time the
system spent in suspend. So if the system suspended for 20 minutes and woke
up 3 times, it would report a value of 9.
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
Number of times that that the screen has been dimmed in response to user
inactivity, reported daily. The count is accumulated through the day,
spanning reboots, and sent once the system clock indicates that a full day
or more has passed since the last report. If the system is suspended or off
for more than a day, the current count will be reported immediately the next
time the system boots, but the skipped days will not be reported. Chrome OS
only.
derat@chromium.org
Number of times that that the screen has been turned off in response to user
inactivity, reported daily. The count is accumulated through the day,
spanning reboots, and sent once the system clock indicates that a full day
or more has passed since the last report. If the system is suspended or off
for more than a day, the current count will be reported immediately the next
time the system boots, but the skipped days will not be reported. Chrome OS
only.
derat@chromium.org
Number of times that that the system has suspended in response to user
inactivity, reported daily. The count is accumulated through the day,
spanning reboots, and sent once the system clock indicates that a full day
or more has passed since the last report. If the system is suspended or off
for more than a day, the current count will be reported immediately the next
time the system boots, but the skipped days will not be reported. Chrome OS
only.
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.
derat@chromium.org
Number of times that that the system has suspended in response to its lid
being closed, reported daily. The count is accumulated through the day,
spanning reboots, and sent once the system clock indicates that a full day
or more has passed since the last report. If the system is suspended or off
for more than a day, the current count will be reported immediately the next
time the system boots, but the skipped days will not be reported. Chrome OS
only.
derat@chromium.org
Reasons why power-management-related daily metrics were reported. Chrome OS
only.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, when sync
invalidator listens to on_application_active events. Values for this metric
are per session, i.e. from battery level at application entering foreground
to returning to background, and normalized to an hourly average consumption.
This is an iOS only measurement. Due to how iOS reports battery levels, it
is likely to see many readings of 0.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, for other
sync invalidator methods. Values for this metric are per session, i.e. from
battery level at application entering foreground to returning to background,
and normalized to an hourly average consumption. This is an iOS only
measurement. Due to how iOS reports battery levels, it is likely to see many
readings of 0.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, when sync
invalidator uses peer-to-peer notifications. Values for this metric are per
session, i.e. from battery level at application entering foreground to
returning to background, and normalized to an hourly average consumption.
This is an iOS only measurement. Due to how iOS reports battery levels, it
is likely to see many readings of 0.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The average power consumption, measured in milli-units per hour, when sync
invalidator uses server-based non-blocking invalidator. Values for this
metric are per session, i.e. from battery level at application entering
foreground to returning to background, and normalized to an hourly average
consumption. This is an iOS only measurement. Due to how iOS reports battery
levels, it is likely to see many readings of 0.
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.
minch@chromium.org
Actions performed while the power button menu is open.
minch@chromium.org
Press power button in laptop mode will result in different scenarios
according to the power button up state. Counts the different power button
press scenarios in laptop mode.
minch@chromium.org
Press power button in tablet mode will result in different scenarios
according to the power button up state. Counts the different power button
press scenarios in tablet mode.
bleung@chromium.org
derat@chromium.org
The maximum power supported by the connected power supply on Chrome OS. A
sample is reported every time that the power manager polls sysfs (typically
every 30 seconds) and sees a connected supply.
bleung@chromium.org
derat@chromium.org
The maximum voltage supported by the connected power supply on Chrome OS. A
sample is reported every time that the power manager polls sysfs (typically
every 30 seconds) and sees a connected supply.
bleung@chromium.org
derat@chromium.org
The type of the connected power supply on Chrome OS. A sample is reported
every time that the power manager polls sysfs (typically every 30 seconds)
and sees a connected supply.
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.
jiameng@chromium.org
Status of logging previous idle event after a screen dim imminent signal is
received.
Deprecated July 11 2017.
bengr@chromium.org
rajendrant@chromium.org
The battery level in percentage when the precache task was started.
Deprecated July 11 2017.
bengr@chromium.org
rajendrant@chromium.org
Measures the difference between the battery level percentage when the
precache task is started and ended. This value indicates the possible
battery usage due to the precache task. Logged when the precache task ends,
which could be due to successful completion, time-out, error conditions, max
download limit exceeded, etc.
Deprecated July 11 2017.
jamartin@chromium.org
bengr@chromium.org
The size in kilobytes occupied by all the entries existing in the cache at
the time of the last precache.
Deprecated July 11 2017.
jamartin@chromium.org
bengr@chromium.org
Like HttpCache.Pattern but only for requests not made during precaching.
Logged per-request.
Deprecated July 11 2017.
jamartin@chromium.org
bengr@chromium.org
Like Precache.CacheStatus.NonPrefetch but only for requests which having a
matching URL in the precache. Measures the amount of precache misses due to
expiration or eviction. Logged per-request.
Deprecated July 11 2017.
twifkak@chromium.org
jamartin@chromium.org
Like Precache.CacheStatus.NonPrefetch, but only for requests with a referer
not in the user's top visited hosts. See History.TopHostsVisitsByRank for
details on the top hosts computation.
Deprecated July 11 2017.
twifkak@chromium.org
jamartin@chromium.org
Like Precache.CacheStatus.NonPrefetch, but only for requests with a referer
in the user's top visited hosts. See History.TopHostsVisitsByRank for
details on the top hosts computation.
Deprecated July 11 2017.
jamartin@chromium.org
twifkak@chromium.org
Like HttpCache.Pattern but only for requests made during precaching. Logged
per-request.
Deprecated July 11 2017.
bengr@chromium.org
The number of bytes that were downloaded over the network for HTTP/HTTPS
fetches that were not motivated by precaching. Logged per-request.
Deprecated July 11 2017.
bengr@chromium.org
The number of bytes that were downloaded because of precaching. Logged
per-request.
Deprecated July 11 2017.
rajendrant@chromium.org
bengr@chromium.org
Enumerates the various failure reasons and events of interest for
precaching. The events are persisted when the native library is not loaded,
and recorded when the library loads next time.
Deprecated July 11 2017.
twifkak@chromium.org
bengr@chromium.org
A bit vector of reasons why the precache fetch failed to start. Bit values
are documented in the FailureReason Java enum.
Deprecated July 11 2017.
twifkak@chromium.org
The minimum resource weight that is fetched in a given precache run.
Reported if the precache completed successfully or was canceled due to the
byte cap, but not if it was cancelled due to an ill-formed manifest or
exceeding the time limit. Reported only if global_ranking is true.
Deprecated July 11 2017.
twifkak@chromium.org
bengr@chromium.org
The percent of manifests for which all resources have been downloaded.
Logged per prefetch run.
Deprecated July 29 2015.
twifkak@chromium.org
bengr@chromium.org
The total number of response bytes received from all prefetch requests,
including config, manifests, and resources. Logged per prefetch run.
Deprecated July 11 2017.
twifkak@chromium.org
The total number of response bytes in 24 hours received over the network
from all prefetch requests, including config, manifests, and resources.
Logged during the next precache run after the 24 hours has elapsed.
Deprecated July 11 2017.
twifkak@chromium.org
bengr@chromium.org
The total number of response bytes received over the network from all
prefetch requests, including config, manifests, and resources. Logged per
prefetch run.
Deprecated July 11 2017.
rajendrant@chromium.org
bengr@chromium.org
The total number of response bytes received over the network for a wasted
resource precache fetch. Logged when a partially downloaded resource
precache fetch gets cancelled due to per-resource size limit or max precache
size limit.
Deprecated July 11 2017.
twifkak@chromium.org
bengr@chromium.org
The total number of response bytes contained in all prefetch requests,
including config, manifests, and resources. Logged per prefetch run.
Deprecated July 11 2017.
twifkak@chromium.org
bengr@chromium.org
The time, in milliseconds, to complete a prefetch run. Only applies to
non-cancelled runs (those for which PercentCompleted is 100).
Deprecated July 11 2017.
jamartin@chromium.org
bengr@chromium.org
The freshness lifetimes of the resources that were precached from the moment
they were fetched or revalidated as described in RFC 2616 13.2.4. Logged per
precache request.
Deprecated March 7 2017.
twifkak@chromium.org
bengr@chromium.org
The latency for requests that were not made during precaching. Logged
per-request.
Deprecated March 7 2017.
twifkak@chromium.org
bengr@chromium.org
Like Precache.Latency.NonPrefetch, but limited to requests with a referer
not in the user's top visited hosts. See History.TopHostsVisitsByRank for
details on the top hosts computation.
Deprecated March 7 2017.
twifkak@chromium.org
bengr@chromium.org
Like Precache.Latency.NonPrefetch, but limited to requests with a referer in
the user's top visited hosts. See History.TopHostsVisitsByRank for details
on the top hosts computation.
Deprecated March 7 2017.
twifkak@chromium.org
bengr@chromium.org
The latency for requests that were made during precaching. Logged
per-request.
Deprecated July 11 2017.
rajendrant@chromium.org
bengr@chromium.org
The time between successive precache periodic GCM task invocations. When
precache task is started, the time interval from previous task invocation is
logged.
Deprecated July 11 2017.
bengr@chromium.org
The number of bytes during user browsing that were served from the cache,
but would have been downloaded over a network if precaching was disabled.
Logged per-request.
Deprecated July 11 2017.
jamartin@chromium.org
bengr@chromium.org
The freshness lifetimes (RFC 2616 13.2.4) of the resources that were
precached and later used (and thus served from the cache). This is computed
at serving time and thus possibly different from the precached value if the
cache entry was revalidated. Logged per-request but only once per URL and
precaching cycle (as Precache.Saved).
Deprecated July 11 2017.
jamartin@chromium.org
bengr@chromium.org
The time between the the beginning of the last precache session and each of
the URL fetches made by the user ever since. Logged per-request.
rkaplow@chromium.org
The amount of time that elapsed during CreateProfilePrefs.
petewil@chromium.org
Count events where Network Prediction was enabled or disabled.
holte@chromium.org
The status when loading PersistedLogs from Prefs.
csharp@chromium.org
Enumeration of errors that happened when reading Preferences files.
Deprecated 5/25/2016 in favor of PreloadScanner.Counts2
csharrison@chromium.org
The number of preloads generated by the preload scanner.
Deprecated 5/25/2016 in favor of PreloadScanner.Counts2.Miss
csharrison@chromium.org
The number of unused preloads generated by the preload scanner. Note that
some link rel preloads are not referenced until after this point, so they
will be falsely marked as preload misses. These will show up in the Raw
bucket.
Removed Feb 2018, no longer useful.
csharrison@chromium.org
The number of preloads generated by the preload scanner.
Removed Feb 2018, no longer useful.
csharrison@chromium.org
The number of unused preloads generated by the preload scanner. Note that
some link rel preloads are not referenced until after this point, so they
will be falsely marked as preload misses.
DocumentWriteEvaluator was removed in 07/2017
csharrison@chromium.org
Time spent executing a script tag in the blink preload scanner, for the
purpose of preloading scripts that will be fetched via a call to
document.write. The execution failed to generate a preload request.
DocumentWriteEvaluator was removed in 07/2017
csharrison@chromium.org
Time spent executing a script tag in the blink preload scanner, for the
purpose of preloading scripts that will be fetched via a call to
document.write. The execution successfully resulted in a preload request.
DocumentWriteEvaluator was removed in 07/2017
csharrison@chromium.org
The reason a particular inline script was blocked from evaluation.
DocumentWriteEvaluator was removed in 07/2017
csharrison@chromium.org
Time spent initializing a new V8 context for the purpose of evaluating it
and preloading document.written strings.
No longer needed
csharrison@chromium.org
The length of the inline script that is being considered for document write
evaluation.
csharrison@chromium.org
The number of preloads generated by scanning an external preloaded CSS
resource. As of 4/25/2016 this only includes @import declarations.
csharrison@chromium.org
Microseconds it took to scan the first chunk of external CSS for preloads.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated May 2018
csharrison@chromium.org
The time between preload discovery and when the resource is actually
referenced. This is implemented by marking when a preload is discovered by
the scanner, and when it has its first ResourceClient added to it. Note that
for link rel preloads, this tracks the time from scanner discory to DOM
discovery of the link declaration, not the actual resource.
Deprecated May 2018
csharrison@chromium.org
The time between preload discovery and when the first bytes of the response
data arrive.
Deprecated 2017-09 as prerenders can no longer be 'used' (=='swapped-in').
davidben@chromium.org
pasko@chromium.org
Time from when a prerendered page is abandoned to when it is first used due
to user navigation. If the page is swapped before begin abandoned, a zero is
recorded.
Deprecated March 13 2015.
pasko@chromium.org
Enumeration of what types of cookies were sent for a prerender.
Deprecated March 13 2015.
pasko@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.
pasko@chromium.org
Final status for prerender pages - either success, or why it was canceled.
deprecated 2016-05-12
Final status for prerender pages - either success, or why it was canceled.
This is for the MatchComplete set of pages (including some pages that were
not actually prerendered), to match the control group.
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
pasko@chromium.org
Enumeration of what events related to the local predictor have occurred
Deprecated April 2015
pasko@chromium.org
Time to perform the LoggedIn Lookup for the local predictor. This operation
checks whether a user is likely logged into a page that we would like to
prerender.
Deprecated April 2015
pasko@chromium.org
The PrerenderLocalPredictor uses local browsing history and the prerender
service to predict pages likely visited soon. Some of these URLs are
prefetched. When such prefetched likely next pages are visited, this
histogram records the PLT for such pages. In particular, this also happens
if prefetch is actually disabled, allowing (by pivoting on whether or not
prefetch is enabled) to compare the effect of prefetch on PLT.
Deprecated April 2015
pasko@chromium.org
Time to perform the Service Lookup for the local predictor. This operation
queries a Google service to obtain pages to prerender, as well as whether
prerender candidate pages are likely safe for prerendering.
Deprecated April 2015
pasko@chromium.org
Time from when a prerendered page is started to when it is first used due to
user navigation. If the page is never used, it is not included in this
histogram. This only refers to prerenders based on the local predictor.
Deprecated April 2015
pasko@chromium.org
Time to perform the URL Lookup for the local predictor. This operation
retrieves from the user's local browsing history the URLs corresponding to
URLIDs.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
The transition type for each new visit as recorded in the local visits
database.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Size of the local visits database (number of entries).
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Enumeration of what events related to local visits have occurred
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.
Deprecated 2017-09 as prerenders can no longer be 'used' (=='swapped-in').
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead) for a prerender that was used (or would have been
used).
hajimehoshi@chromium.org
jkarlin@chromium.org
kouhei@chromium.org
Number of bytes transferred on the network for URLRequests (not including
HTTP/TLS/TCP/IP overhead) for a prerender that was not used. All
nostate-prefetch bytes are currently counted as wasted because it is hard to
track byte use in HTTP cache.
Deprecated December 28, 2016, use Prerender.PrefetchAge instead.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Time between the prefetch and the actual load of the page.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Length of the redirect chain for main resources loaded by NoStatePrefetch.
Recorded when the final response in the chain is received.
jam@chromium.org
Time a prefetch renderer is kept alive after parsing to wait for
subresources to finish loading.
jam@chromium.org
Time between prefetch renderer startup and when parsing is complete.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Type of responses received by NoStatePrefetch, distinguishing cacheable
resources from no-store resources, and main resources from sub-resources.
Recorded when a response is received, including on each redirect.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Length of the redirect chain for sub-resources loaded by NoStatePrefetch.
Recorded when the final response in the chain is received.
pasko@chromium.org
A boolean that indicates whether the Omnibox navigation being committed
could have been prerendered by the Omnibox Prerender system. This provides
an upper bound for Prerender.OmniboxNavigationsUsedPrerenderCount and allows
the potential for Omnibox Prerendering coverage to be understood. If Omnibox
Prerendering is disabled, this histogram will register a 'false' entry. The
total count is the equivalent of the deprecated
NetworkActionPredictor.NavigationCount histogram.
Deprecated 2017-09 as prerenders can no longer be 'used' (=='swapped-in').
pasko@chromium.org
The number of navigations that use a prerender initiated from the Omnibox.
The count is incremented when the Prerendered tab is swapped in if the
Prerender was initiated by the Omnibox, which obviously requires
Prerendering from the Omnibox to be enabled.
Deprecated 2017-09.
pasko@chromium.org
The number of prerenders initiated from the Omnibox. This is incremented
when the NetworkActionPredictor suggests Prerendering as an optimal strategy
given the text the user has entered and the Autocomplete suggestion
currently selected. It is only incremented if Prerendering from the Omnibox
is enabled.
Deprecated April 2018
pasko@chromium.org
The number of responses received bucketed into the range [0,4]: bucket 0 is
the total number of responses received; bucket 1 is the number of responses
received with an X-Mod-Pagespeed header [indicating a mod_pagespeed server];
bucket 2 is the number of responses received with an X-Page-Speed header and
a header value in the X-Mod-Pagespeed format (a.b.c.d-e) [indicating an
ngx_pagespeed server]; bucket 3 is the number of responses received with an
X-Page-Speed header and a header value in the PageSpeed Service format
(a_b_c) [indicating a PSS server]; and bucket 4 is the number of responses
received with an X-Page-Speed header and a header value in neither of the
preceding formats [indicating some other server; IISpeed is the only known
one at this stage].
Deprecated April 2018
pasko@chromium.org
The number of responses received that either have an X-Mod-Pagespeed header
or have an X-Page-Speed header with a value in the X-Mod-Pagespeed format
(a.b.c.d-e), bucketed into the range [1,99]: bucket 1 is for header values
that aren't in the a.b.c.d-e format, the remaining buckets are an encoding
of the value: 2 + 2 * (max(c, 10) - 10) + (d > 1 ? 1 : 0). The rationale
is that 'c' is incremented with each new release and 'd' is initially 0 but
is incremented for each patch to a release.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Types of pages rendered.
deprecated March 30, 2015
pasko@chromium.org
Indicates whether the user has ever visited (in the past) a URL for which a
prerender is launched.
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.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for all pages loaded in a session.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for the first page load completing immediately after a
prerender.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
"FirstAfterMiss" means the first pageload after a prerender miss.
There are two types: Any, and Non-overlapping. The latter only applies to
page loads initiated after the prerender. This variable records cases where
only Any triggered.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
"FirstAfterMiss" means the first pageload after a prerender miss.
There are two types: Any, and Non-overlapping. The latter only applies to
page loads initiated after the prerender. This variable records cases where
both triggered.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for the first page load completing immediately after a
prerender, but which has also started after the prerender has been
initiated.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
"FirstAfterMiss" means the first pageload after a prerender miss.
There are two types: Any, and Non-overlapping. The latter only applies to
page loads initiated after the prerender. This variable records cases where
only Non-overlapping triggered.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded only for prerendered pages, or for pages which would have
been prerendered in the control case.
Deprecated August 2016
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded only for prerendered pages, or for pages which would have
been prerendered in the control case.
In MatchedComplete, the prerender group also contains cancelled prerenders,
so as to produce a perfect match of page views attributed this group in the
prerender group with those attributed to this group in the control group.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for all page loads which happen within 30 seconds after a
prefetch tag is observed.
Deprecated 2017-03.
pasko@chromium.org
Time from when a user navigates to a page to when it loads. Since the pages
may start loading before the user navigates to it, this does not include any
portion of load prior to navigation.
This is recorded for all page loads which happen within 30 seconds after a
prefetch tag is observed and which do not correspond to a prerender tag.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Whether the perceived Time to First Contentful Paint (TTFCP) was recorded
successfully for a prerendered page. Since a prerendered page will start
loading before a user navigates to it, the perceived TTFCP does not include
an time prior to the user navigation. If true, there is an associated
PrefetchTTFCP that records the TTFCP from the swapped-in navigation start.
If false, no PrefetchTTFCP was recorded.
Deprecated 2017-09 as prerenders can no longer be 'used' (=='swapped-in').
pasko@chromium.org
For prerenders that are swapped in, the percentage of the time from load
start until the onload event fires that has elapsed at the time of the
swapin.
pasko@chromium.org
How long the cleanup portion of PrerenderManager::PeriodicCleanup takes, to
measure jank.
pasko@chromium.org
How long the resource check portion of PrerenderManager::PeriodicCleanup
takes, to measure jank.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Time between a prefetch or effective prefetch and the actual load of the
page. For NoState prefetch, this is the time of the actual prefetch. For
prerendering, it is the time that prerender began. For control groups in
NoState prefetch experiments, it is the time that prefetch would have
occurred.
droger@chromium.org
mattcary@chromium.org
pasko@chromium.org
Time to first contentful paint (TTFCP) for navigations related to prefetch
(including prerender, no-state prefetch, and associated experiments). This
measures user-visible TTFCP. For no-state prefetch this is standard
navigation-to-FCP; for prerender this is the time from navigation start when
the prerender is swapped in to FCP.
Deprecated 2017-03.
pasko@chromium.org
After launching a prerender, how many simultanious prerenders are recorded
as running, out of a maximum of three.
Deprecated 2017-03.
pasko@chromium.org
For prerenders that finish loading before they are ever swapped in, their
page load time until the onload event fires.
pasko@chromium.org
The number of sessions that have at least X successful prerenders. Recorded
only on iOS since 2017-09.
pasko@chromium.org
For each prerender link added to a document, records the rel types present
on the link element.
pasko@chromium.org
For each prerender in a document which starts prerendering, records the rel
types present on the link element.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
This is the time from when a prerendered page finishes loading to when it is
displayed, as measured by the renderer process. When a page is displayed
before it finishes loading, no value is recorded in this histogram.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Perceived load time of a page, as measured by the renderer process. For
non-prerendered pages, this is just BeginToFinish. For displayed prerendered
pages, this is the time from when the prerendered page is moved into a
TabContents until finish. "Finish" == after onload() and all
resources are loaded. Note that this is 0 if the loading finishes before the
page is moved into a TabContents.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Perceived load time of a prerendered page that is displayed, as measured by
the renderer process. This is the time from when the prerendered page is
moved into a TabContents until finish. "Finish" == after onload()
and all resources are loaded. Note that this is 0 if the loading finishes
before the page is moved into a TabContents.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
The time elapsed between when the prerendering of a page starts and when the
page is displayed, as measured by the renderer process. Prerendered pages
discarded without being displayed are excluded from this count.
pasko@chromium.org
The detailed reason why a prerender is canceled with
FINAL_STATUS_UNSUPPORTED_SCHEME
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Enumeration of how prerender was used per session.
Deprecated Dec 12 2014.
pasko@chromium.org
Time to perform the session storage namespace merge.
Deprecated April 2015
pasko@chromium.org
For simulated local browsing prerendering, the baseline PLT of pages without
any prerendering for pages that would be prerendered.
Deprecated April 2015
pasko@chromium.org
For simulated local browsing prerendering, the estimated PLT of pages with
prerendering enabled for pages that would be prerendered.
pasko@chromium.org
A boolean that indicates how often we suppress a dialog from a tab when
swapping it with a prerender.
pasko@chromium.org
A boolean that indicates how often we fail to delete an old prerendered tab
before the timeout.
Deprecated April 2015
pasko@chromium.org
Enumeration of what events related to the TabHelper class have occurred.
Deprecated 2017-09.
pasko@chromium.org
Time between subsequent prerender requests.
Deprecated 2017-09.
pasko@chromium.org
The time elapsed between the most recent visit to a URL and when an
attempted prerender of the same URL is cancelled with
FINAL_STATUS_RECENTLY_VISITED.
deprecated Nov 16 2012
Please list the metric's owners. Add more owner tags as needed.
Duration that a user hovers a link before clicking on it.
deprecated Nov 16 2012. See Prerender.TimeUntilUsed2, which has a larger
range.
Please list the metric's owners. Add more owner tags as needed.
Time from when a prerendered page is started to when it is first used due to
user navigation. If the page is never used, it is not included in this
histogram.
Deprecated 2017-09 as prerenders can no longer be 'used' (=='swapped-in').
pasko@chromium.org
Time from when a prerendered page is started to when it is first used due to
user navigation. If the page is never used, it is not included in this
histogram.
dougarnett@chromium.org
Blocked previews due to Cache-Control:no-transform directive.
ryansturm@chromium.org
The actual data used for a page load using a preview optimization.
bengr@chromium.org
megjablon@chromium.org
User interactions with the Lo-Fi context menu options. These include:
Displays and clicks on the "Load image" and "Load
images" context menu options. Count of pages where the user has clicked
"Load image" at least once.
ryansturm@chromium.org
The estimated amount that the content was inflated for a page load using a
previews optimization. Recorded when a page load using a previews
optimization inflates the data used.
ryansturm@chromium.org
The estimated percent of data used that a page load would have otherwise
cost for a page load using a previews optimization. Recorded when a page
load using a previews optimization inflates the data used.
ryansturm@chromium.org
The estimated data savings for a page load using a previews optimization.
Recorded when a page load using a previews optimization reduces the data
used.
ryansturm@chromium.org
The estimated percent of data savings for a page load using a previews
optimization. Recorded when a page load using a previews optimization
reduces the data used.
ryansturm@chromium.org
When evaluating whether to show a user a preview, the preview might be
disallowed for various reasons. If the preview is disallowed, then this
reports the reason for disallowing it. If the preview is allowed, then this
generally reports "Previews Allowed". It may instead report
"Previews Allowed without server rule check" for a preview that
expects to check server rules but they are not enabled.
bengr@chromium.org
megjablon@chromium.org
User interactions with the previews "Saved data" infobar. These
include:
Displays of the infobar and clicks on the "Load original" link.
Whether the infobar was dismissed by navigation or the user clicking on
"X" close button.
megjablon@chromium.org
Whether the timestamp for a stale preview was shown on the infobar. If the
timestamp was not shown, states the reason why.
No longer used as of 06/2018.
ryansturm@chromium.org
The number of rows in the Previews opt out SQLite table at profile startup.
No longer used as of 06/2018.
ryansturm@chromium.org
The SQLite error code that the previews opt out store saw when trying to
open the SQLite database. This is logged when an unexpected error occurs
when trying to open the database file.
ryansturm@chromium.org
Whether the user chose to reload the original page when shown a preview.
ryansturm@chromium.org
The estimated content length of a page load using a preview optimization.
dougarnett@chromium.org
Whether processing the previews hints succeeded and if any previews hints
were found. Recorded when the PreviewsOptimizationGuide receives a
notification to process hints.
vitalybuka@chromium.org
Count of events in PrinterService on Chrome OS related to USB printers.
thestig@chromium.org
On Windows, the average size of a printed page after converting to EMF.
thestig@chromium.org
On Windows, the average size of a printed page after converting to EMF with
the GDI Text experiment turned on.
thestig@chromium.org
On Windows, the average size of a printed page after converting to level 2
PostScript.
thestig@chromium.org
On Windows, the average size of a printed page after converting to level 3
PostScript.
thestig@chromium.org
On desktop, the average size of a printed page after converting to PWG
Raster format.
skau@chromium.org
Records whether resolution of a .local address via mDNS was successful. The
metric is recorded during attempted setup of a printer discovered via mDNS.
skau@chromium.org
Record if the request for IPP attributes was successful during printer
setup. This only occurs for setup attempts of IPP and IPPS printers.
skau@chromium.org
The final status of every print job that was succesfully queued. Only used
on Chrome OS.
skau@chromium.org
Records the source of PostScript Printer Description files used during
printer setup. Entries are recorded for every attempted configuration. Only
recorded on Chrome OS.
skau@chromium.org
The protocol for a printer that was added. Used to track printer churn by
protocol. Only on Chrome OS.
skau@chromium.org
The protocol for a printer that was removed. Used to track printer churn by
protocol. Only on Chrome OS.
skau@chromium.org
The number of printers shown in the discovered printers dialog during
printer set up. Only recorded on Chrome OS.
skau@chromium.org
The success or error code for the setup of a CUPS printer. Recorded when
setup is attempted through the settings dialogs. Only recorded on Chrome
OS.
skau@chromium.org
The size of the print queue when a print job is initially queued. When the
first job is started, a zero is recorded. Only used on Chrome OS.
skau@chromium.org
Records the protocol for a selected printer in Chrome OS. Used to track
usage of the various printer protocols. Since a selection occurs when print
preview is opened, this will count at least one every time that happens if a
CUPS printer was selected.
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.
No longer used as of 09/2017.
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.
nasko@chromium.org
Logged when a document calls the window.print() API. The boolean value
indicates whether it is invoked by the main frame. It will be false for
documents in subframes.
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.
nasko@chromium.org
Logged when a document calls the window.print() API in any frame. The
boolean value will be true when the API call is invoked by a document which
is in a process different than the top level document. It will be false in
all other cases.
vitalybuka@chromium.org
The page count of the initial print preview, a.k.a. the total number of
pages in documents to be printed.
thestig@chromium.org
The final page count (after page selection) of documents printed to PDF and
opened in Preview.app on Mac.
vitalybuka@chromium.org
The final page count (after page selection) of documents printed to a cloud
printer.
No longer used as of 01/2016.
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.
rbpotter@chromium.org
Actions taken on the PDF viewer inside Print Preview's preview area.
vitalybuka@chromium.org
Print preview events.
thestig@chromium.org
The average size of a page in the printed document when the source is HTML.
thestig@chromium.org
The average size of a page in the printed document when the source is PDF.
rbpotter@chromium.org
Track type of documents printed (HTML vs PDF). Recorded immediately after a
user requests that a document be printed.
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.
markusheintz@google.com
msramek@google.com
Logged each time the user grants a consent for a feature integrated with the
consent auditor. The value indicates which feature.
markusheintz@google.com
msramek@google.com
Logged each time the user denies or revokes a consent for a feature
integrated with the consent auditor. The value indicates which feature.
Deprecated as of 4/2018.
dullweber@google.com
msramek@google.com
Logs whether the UserEventServiceReady is ready when recording a consent.
This should always be true as the service is created at startup.
pastarmovj@chromium.org
Measure how often the automatic recognition for terminal services
environment would have incorrectly decided that the job object should be
applied, when it shouldn't have been as dictated by the flag
--allow-no-sanbox-job. This histogram will guide the final removal of the
flag, which will be possible when the number of false values becomes
insignificant.
shrikant@chromium.org
Errors returned while launching sandboxed process on Windows. For decoding
error code please refer to http://goo.gl/fJJiAv.
forshaw@chromium.org
Warnings returned while launching sandboxed process on Windows. For decoding
error code please refer to http://goo.gl/fJJiAv. This will only be logged
when SpawnTarget succeeds with SBOX_ALL_OK but the last warning result does
not equal SBOX_ALL_OK.
forshaw@chromium.org
The warning launch error returned while launching sandboxed process on
Windows. This will only be logged when SpawnTarget succeeds with SBOX_ALL_OK
but the last warning result does not equal SBOX_ALL_OK.
shrikant@chromium.org
Errors returned while launching lowbox enabled sandboxed process on Windows.
For decoding error code please refer to http://goo.gl/fJJiAv.
mrefaat@google.com
The time spent in product tour screens for ios.
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.
chengx@chromium.org
Load status of an avatar for decorating the Windows taskbar
Please list the metric's owners. Add more owner tags as needed.
Size of the bookmarks database.
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.
tangltom@chromium.org
This histogram tracks whether the accounts cached in the GAIA cookie service
manager are stale when presenting the user menu when DICE is enabled.
Please list the metric's owners. Add more owner tags as needed.
Size of the extension cookies database.
Please list the metric's owners. Add more owner tags as needed.
Size of the favicons database.
Deprecated 02/2015. Profile.CreateAndInitializeProfile is more useful.
rkaplow@chromium.org
Length of time to retrieve profile.
anthonyvd@chromium.org
Whether Profile::GetProfileInfoPath is called with a profile outside the
user data directory. We expect this to never happen but need to verify in
stable. This metric may be removed after M54.
hajimehoshi@chromium.org
kouhei@chromium.org
Size of the history database.
anthonyvd@chromium.org
Whether Profile::InitProfileUserPrefs is called with a profile outside the
user data directory. We expect this to never happen but need to verify in
stable. This metric may be removed after M54.
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.
Deprecated 2017-10-16. No longer tracked. Feature removed.
mlerman@chromium.org
Tracks user interactions with the 'Not You?' bubble that users can navigate
to from the Upgrade bubble after upgrade to the New Avatar Menu.
Deprecated 2017-10-19. No longer tracked. Feature removed.
mlerman@chromium.org
Tracks user interactions with the signin bubble that appears in the New
Avatar Menu upon signin. This bubble appears after the user signs in using
the Inline Signin flow.
Deprecated 2017-10-16. No longer tracked. Feature removed.
mlerman@chromium.org
Tracks user interactions with the bubble that appears for users in the new
avatar menu after upgrade.
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.
feuunk@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.
As opposed to Profile.NumberOfProfiles, this counts only profiles that have
been used in the last 28 days.
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.
This counts only profiles that have been used in the last 28 days.
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.
This counts the total number of profiles on the user's device, regardless of
whether they've been used recently.
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.
This counts only profiles that have been used in the last 28 days.
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.
This counts only profiles that have been used in the last 28 days.
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.
This counts only profiles that have been used in the last 28 days.
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().
dullweber@chromium.org
The amount of time that elapsed during profile statistics calculation.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Size of the thumbnails database.
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).
robertshield@chromium.org
Indicates whether a profile had a reset trigger that caused it to launch a
reset flow. The presence of this trigger is recorded during profile
creation.
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.
vasilii@chromium.org
ewald@chromium.org
Whether any profile was shown in the list when the profile chooser was
opened.
alito@chromium.org
Encodes from where the request for resetting the profile settings
originated.
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.
hansberry@chromium.org
Provides a breakdown of how often each BLE weave connection result occurs.
hansberry@chromium.org
Provides a breakdown of how many times each possible Bluetooth GATT
connection result occurs.
The bucket "Unknown result" indicates that the Bluetooth platform
returned an unknown error code; if it has any counts, the client code should
be changed to account for the new error code.
hansberry@chromium.org
Provides a breakdown of how many times each possible Bluetooth GATT
"notify session" attempt result occurs.
The bucket "Unknown result" indicates that the Bluetooth platform
returned an unknown error code; if it has any counts, the client code should
be changed to account for the new error code.
hansberry@chromium.org
Provides a breakdown of how many times each possible Bluetooth GATT
"write characteristic" attempt result occurs.
Deprecated 9/2016. Never added to histograms.xml and value is always 1.
The number of extensions overriding the proxy, triggering the proxy override
extension warning bubble.
rdevlin.cronin@chromium.org
The action taken by the user when the "proxy overridden" extension
warning bubble is shown. Logged immediately after the action is taken.
tasak@google.com
The growth of the background renderer's memory usage after a background
renderer is purged. This is recorded 5, 10 and 15 minutes after the purge.
tasak@google.com
Time elapsed from when the backgrounded and purged renderer is foregrounded
until the renderer is painted. This is recorded every time the backgrounded
and purged renderer is foregrounded.
tasak@google.com
Time elapsed from when the renderer, which is kept backgrounded for more
than 5 minutes, is foregrounded until the renderer is painted. This is
recorded every time such renderer is foregrounded.
Deprecated April 2017.
tasak@google.com
The memory usage of the BlinkGC allocator after a background renderer is
purged and suspended. Note: this metric is for A/B testing.
Deprecated April 2017.
tasak@google.com
The memory usage of the discardable memory after a background renderer is
purged and suspended. Note: this metric is for A/B testing.
Deprecated April 2017.
tasak@google.com
The memory usage of the malloc after a background renderer is purged and
suspended. Note: this metric is for A/B testing.
Deprecated April 2017.
tasak@google.com
The memory usage of PartitionAlloc after a background renderer is purged and
suspended. Note: this metric is for A/B testing.
Deprecated April 2017.
tasak@google.com
The sum of the memory usages of PartitionAlloc, malloc, discardable memory,
mainThreadIsolate() and BlinkGC allocator after a backgrounded renderer is
purged and suspended. Note: this metric is for A/B testing.
Deprecated April 2017.
tasak@google.com
The memory usage of mainThreadIsolate() after a backgrounded renderer is
purged and suspended. Note: this metric is for A/B testing.
Deprecated Oct 2017.
tasak@google.com
This records how many tasks are still in task queues when a backgrounded
renderer is suspended.
peter@chromium.org
Whenever a Service Worker receives a push message, this records the budget
available to the service worker, which is an internal Chrome value for the
amount of background processing a service worker is allowed to do without
visibly alerting the user. Scale for the budget is 0 to 100.
johnme@google.com
When a Service Worker receives a push message, this records whether the
overall operation was successful, or otherwise the type of error
encountered.
johnme@google.com
When attempting to deliver a push message to a Service Worker, this records
the result of finding the Service Worker registration given its ID and
origin.
johnme@google.com
When a Service Worker receives a push message, this records the precise
result received from the Service Worker code.
johnme@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.
dgn@chromium.org
Whenever a Service Worker receives a push message, this records whether
Chrome is completely running in the background. A successful report means
that the message was received when Chrome was in complete background mode,
without UI, while a failure means it was in some other state: in background
with some apps running, showing browser windows, etc.
johnme@google.com
When a webpage registers for push messaging, this records whether the
request is successful, or otherwise the type of error encountered.
peter@chromium.org
When a Service Worker hits low budget when servicing a push message, this
records what the Site Engagement Service score is at that time.
peter@chromium.org
When a Service Worker hits zero budget when servicing a push message, this
records what the Site Engagement Service score is at that time.
johnme@google.com
When unregistering a legacy non-InstanceID push messaging subscription, this
records the result returned by the GCMDriver (note that exceeding the
maximum number of retries due to network errors is logged as SERVER_ERROR).
johnme@google.com
When unregistering an InstanceID push messaging subscription, this records
the result returned from deleting the InstanceID (note that exceeding the
maximum number of retries due to network errors is logged as SERVER_ERROR).
johnme@google.com
When unregistering a website from push messaging, this records the reason
why it is being unregistered.
johnme@google.com
When unregistering a website from push messaging, this records whether the
request is successful, or otherwise the type of error encountered.
johnme@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.
michaeln@chromium.org
How many kilobytes are how old. Similar to |AgeOfOrigin| except a sample is
added for each kilobyte of an origin's data. Logged hourly for all origins
with stored data.
michaeln@chromium.org
How many days it's been since an origin's temporary storage has been
accessed. Logged hourly for all origins with stored data.
michaeln@chromium.org
Amount of free disk space for the storage directory. Logged at irregular
intervals.
calamity@chromium.org
The number of days since an origin was last chosen to be evicted from the
storage, recorded each time the origin is evicted (except for the first
eviction).
michaeln@chromium.org
The number of days since an origin's data was last accessed. Logged upon
access when the time since last access is at least 24 hours.
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.
calamity@chromium.org
The number of times the evicted origin was accessed. Logged when the origin
is evicted.
calamity@chromium.org
The number of days since the evicted origin was last accessed. Logged when
the origin is evicted.
tzik@chromium.org
Number of evicted origins in an hour.
calamity@chromium.org
The time since the evicted origin was last accessed. Logged when the origin
is evicted.
tzik@chromium.org
Number of eviction rounds in an hour.
tzik@chromium.org
Amount of free disk space for profile directory.
michaeln@chromium.org
The size of the global temporary storage pool. Logged at irregular
intervals.
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.
dgrogan@chromium.org
Types of origins that are initially selected for eviction via LRU. Some of
these types are exempt from eviction.
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.
michaeln@chromium.org
If our hardcoded OS accomodation is too large for the volume size, we define
the value as a fraction of the total volume size instead. The
OSAccomodationDelta is the difference between the hardcoded and computed
values.
michaeln@chromium.org
Percentage of the storage device that is free. Logged at irregular
intervals.
michaeln@chromium.org
Percentage of an origin's quota that is being used by the origin. Logged at
irregular intervals.
michaeln@chromium.org
Percentage of the storage device that ia being use for temporary storage.
Logged at irregular intervals.
michaeln@chromium.org
The quota value computed for an origin using temporary storage. Logged at
irregular intervals. (In the process of writing new data, storage systems
consult the quota system for "usage and quota" to determine if
there is sufficient space available for the new data. This value is logged
at the time of that consultation. The frequency is dependent on how
individual websites use the various storage apis.)
tzik@chromium.org
Number of skipped eviction rounds in an hour.
calamity@chromium.org
Time since an origin was last chosen to be evicted from the storage,
recorded each time the origin is evicted (except for the first eviction).
tzik@chromium.org
Time between two consecutive active eviction rounds.
tzik@chromium.org
Time spent to an eviction round.
michaeln@chromium.org
Time spent querying the embedder for the settings values. Logged at
irregular intervals as the values are refreshed.
Removed November 2016
michaeln@chromium.org
Time spent initializing the global quota. Logged when the storage
partition's quota manager is initialized.
michaeln@chromium.org
Total disk space for the storage directory. Logged at irregular intervals.
tzik@chromium.org
Overage of the temporary global storage usage at beginning of an eviction
round.
holte@chromium.org
Counts how often daily interval events were fired.
holte@chromium.org
For each Rappor log that is discarded, the reason that it was discarded.
holte@chromium.org
Net error codes for failed Rappor uploads.
Removed 2015/05/05.
holte@chromium.org
Rappor.DailyEvent.IntervalType reported under the wrong name.
holte@chromium.org
Success or errors encountered when loading Rappor cohort pref.
holte@chromium.org
Success or errors encountered when loading Rappor secret pref.
holte@chromium.org
For each upload to the Rappor server, log the response received from the
server.
gambard@chromium.org
The action chosen by the user after displaying the reading list context
menu.
gambard@chromium.org
Number of tries before the download of the entry is successful.
gambard@chromium.org
Final status of the download of a reading list entry.
gambard@chromium.org
Time since the first read of the reading list entry getting deleted. 0 if it
has never been read.
gambard@chromium.org
Whether the displayed version is the offline one.
gambard@chromium.org
Time since the creation of the read reading list entry getting deleted.
gambard@chromium.org
Number of read entries in reading list.
gmabard@chromium.org
Time since the creation of the unread reading list entry getting deleted.
gambard@chromium.org
Number of unread entries in reading list.
robertshield@chromium.org
Log each stage of a recovery component event.
grt@chromium.org
The result of an attempt to show a relaunch notification dialog.
Deprecated Dec 2016. This metric did not report the number of shared workers
correctly, since it used the RenderProcessHostImpl ref counts, which in the
shared worker case is more like a boolean flag (zero or one or maybe two)
than the number of shared workers. So its results can be thought of as
roughly the number of service workers only.
kinuko@chromium.org
Maximum number of workers (SharedWorker or ServiceWorker) that are
simultaneously hosted in a single renderer process. Recorded when the
renderer process host is being destructed.
Deprecated May 2018. There are no longer accelerated fixed root backgrounds.
Please list the metric's owners. Add more owner tags as needed.
Keeps track of the number of main frame scrolls with an accelerated fixed
root background, the number of main frame scrolls with an unaccelerated
fixed root background, and the total number of main frame scrolls.
hartmanng@chromium.org
Total count of the number of RenderLayers which are scrollable areas, need
to be promoted to stacking containers, and will use composited scrolling.
Each bucket is sampled at most once per RenderLayer, when the RenderLayer
first becomes scrollable, first needs to become a stacking container, and
first uses composited scrolling, respectively.
Replaced by Scheduling.Renderer.DrawDuration. This metric did not
differentiate between processes.
brianderson@chromium.org
The time it takes for the compositor to draw a frame.
Measurement no longer taken.
brianderson@chromium.org
The amount by which the compositor's draw duration was overestimated in a
particular frame (0 if the duration was perfectly predicted or
underestimated).
Measurement no longer taken.
brianderson@chromium.org
The amount by which the compositor's draw duration was underestimated in a
particular frame (0 if the duration was perfectly predicted or
overestimated).
Measurement no longer taken.
brianderson@chromium.org
The delay between the compositor submitting a command to the GPU and that
command executing on the GPU. This delay is measured once per frame.
Measurement no longer taken.
brianderson@chromium.org
The amount by which GPU latency was overestimated in a particular frame (0
if the latency was perfectly predicted or underestimated).
Measurement no longer taken.
brianderson@chromium.org
The amount by which GPU latency was underestimated in a particular frame (0
if the latency was perfectly predicted or overestimated).
avi@chromium.org
The length of time render processes are hung, in milliseconds. Note that
because technically speaking render processes are "hung" from the
moment an input event is sent to them until the moment that they return an
ACK, only hangs of minimum length 5s are recorded. Note that this combines
measurements from both renderer processes that recover on their own, and
render processes that are killed.
dfalcantara@chromium.org
Android: Records the terminal event associated with a hung renderer infobar.
This includes both the explicit user actions as well as implicit dismissals,
e.g., when the renderer regains responsiveness before the infobar is
interactively dismissed.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
A lower-bound on the percentage increase in memory that would result from
promoting all layers that have a webkit-transition on opacity or transform.
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.
kkhorimoto@chromium.org
[iOS] A boolean that is used to indicate that the WebKit rendering bug in
http://crbug.com/583231 has occurred. This occurs when a page with no
viewport tag is rendered with an unusable zoom scale. Only logged on iOS.
michaeldo@chromium.org
[iOS] Counts the number of times a WKNavigationDelegate callback was called
after the CRWWebController was closed. This is unexpected and could be the
cause of many crashes. If this histogram is ever logged, it means that
Chrome needs to gracefully handle the case when WKNavigationDelegate
callbacks are called for a destroyed web controller. Only logged on iOS.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a document finished loading to when all it's resources
are also loaded.
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.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to when it is fully
loaded.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to its first layout.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page was requested by a user to when it starts loading.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page started loading to when it is fully loaded.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page starts loading to when the main document is
finished loading.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
The time from when a page starts loading to its first layout.
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.
ericrk@chromium.org
Percentage of pixels which would have been rastered, but were skipped due to
the partial raster optimization. Logged for each raster task run in a
Browser process. The histogram is suffixed by the RasterBufferProvider which
is in use.
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.
Deprecated in 12/2017. Renderer4.MainThreadGestureScrollReason and
Renderer4.MainThreadWheelScrollReason could track more detailed reasons of
main thread scrolling.
vollick@chromium.org
It's possible for compositor hit testing to determine conclusively that
compositor thread scrolling can or cannot be done. It's also possible that
the hit testing result is inconclusive. We would like to see the I-don't-
know result as little as possible. This histogram tracks the ratios.
Deprecated in 06/2018, M69. Renderer4.CompositorThreadImplDrawDelay is no
longer needed due to issue 851784.
wiltzius@chromium.org
Time between frames, as measured on the compositor thread. This is collected
once per frame while it is being drawn to the screen in the compositor.
tdresser@chromium.org
Whether the scroll from touch is executed on main thread.
tdresser@chromium.org
Whether the scroll from mouse wheel is executed on main thread.
Renamed to Renderer4.pixelCountCulled_Draw.
wiltzius@chromium.org
Number of pixels that culling prevented being drawn to the screen,
normalized to the viewport size. This is collected once per frame while it
is being drawn to the screen in the compositor.
Renamed to Renderer4.pixelCountOpaque_Draw.
wiltzius@chromium.org
Number of pixels drawn to the screen and known opaque, normalized to the
viewport size. This is collected once per frame while it is being drawn to
the screen in the compositor.
Renamed to Renderer4.pixelCountTranslucent_Draw.
wiltzius@chromium.org
Number of pixels drawn to the screen and not known opaque, normalized to the
viewport size. This is collected once per frame while it is being drawn to
the screen in the compositor.
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.
tdresser@chromium.org
For every gesture, we record whether the scroll occurred on the main thread,
on the compositor thread, or on the compositor thread but blocked on the
main thread. The last case will happen when there is a blocking event
listener.
vmpstr@chromium.org
Gpu image decode usage statistics. Images are decoded and locked prior to
upload; this indicates how that decode is used during tile management.
vmpstr@chromium.org
Indication whether the first lock of an image decode was wasted (image was
not used). Images are decoded and locked prior to raster; this indicates
whether the decode was used or not during the first lock.
ericrk@chromium.org
Gpu image upload usage statistics. Images are uploaded and locked prior to
use; this indicates how that upload is used during tile management.
ericrk@chromium.org
Indication whether the first lock of an image upload was wasted (image was
not used). Images are uploaded and locked prior to raster; this indicates
whether the upload was used or not during the first lock.
Deprecated as of 06/2017. No longer generated.
vmpstr@chromium.org
Indication whether the first ref of a GPU image upload was wasted (not used
in raster). Images are uploaded prior to raster; this indicates whether the
upload was used during the first ref.
Deprecated as of 06/2017. No longer generated.
vmpstr@chromium.org
Indication whether the GPU image upload was used in raster. Images are
uploaded prior to raster; this indicates whether the upload was used during
raster.
alokp@chromium.org
Whether gpu rasterization is enabled (checked once after the page is painted
for the first time).
ericrk@chromium.org
If gpu rasterization is enabled, whether this page contains both slow-paths
(making it suitable for MSAA) and non-AA paints (making it not-suitable for
MSAA). This indicates a case where we would like to use MSAA, but may have
to avoid it for correctness reasons.
alokp@chromium.org
If gpu rasterization is enabled, whether the page contents contain no more
than 5 slow paths, and is suitable for non-MSAA gpu rasterization (checked
once after the page is painted for the first time).
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).
Deprecated 02/2018. The ideal content scale closely matches the default
device scale factor.
vmpstr@chromium.org
The contents scale at which picture layer impl should be rasterized in order
to appear crisp. This is also known as ideal contents scale. This value is
recorded any time the ideal contents scale changes. Some examples of this
are pinch-zoom and JavaScript transform changes.
khushalsagar@chromium.org
The mip level at which images are decoded for rasterization in the renderer.
This value is recorded each time an image is decoded in the compositor and
records the mip level used for the decode. Note that the mip levels recorded
lie between [1, 32], with the value of 1 indicating the use of the original
image.
vmpstr@chromium.org
This metric records the duration of an image decode for the raster path in
the compositor. It is recorded every time we decode an image. It is suffixed
by the type of rasterization we're in (either Gpu or Software).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
vmpstr@chromium.org
khushalsagar@chromium.org
This metric records the duration of an image decode for out of raster path
in the compositor. It is recorded every time we decode an image. It is
suffixed by the type of rasterization we're in (either Gpu or Software).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ccameron@chromium.org
For each cc::Layer that has more than zero discardable images, this metric
records the percent of image pixels that were from images that were
originally specified in an sRGB color space.
ccameron@chromium.org
For each cc::Layer that has more than zero discardable images, this metric
records the percent of images that were originally specified in an sRGB
color space.
wiltzius@chromium.org
Number of rects inside of a PictureLayer's invalidation region per commit.
Deprecated in 06/2018, M69. Renderer4.LanguageDetection is no longer needed
due to issue 851784.
wiltzius@chromium.org
Time to determine the page language. This is done after the page has been
loaded.
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.
vmpstr@chromium.org
For each attempted lock of a cached image, records whether it was
successful.
tdresser@chromium.org
Ideally we'd always scroll on the impl thread, but there are a variety of
situations where we need to scroll on main. We should try to drive these
down. For every gesture, we record whether or not the scroll occurred on the
main thread, and if it did, what the reason was.
tdresser@chromium.org
Ideally we'd always scroll on the impl thread, but there are a variety of
situations where we need to scroll on main. We should try to drive these
down. For every wheel tick, we record whether or not the the scroll occurred
on the main thread, and if it did, what the reason was.
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.
ericrk@chromium.org
The type of clear which was needed for each cc::RasterSource rasterized.
Deprecated 02/2017 in Issue 675840.
vmpstr@chromium.org
For each tile that was ready to draw at some point, logs whether the tile
was actually used in a draw. This is logged at tile destruction time.
ericrk@chromium.org
Percentage of pixels which would have been rastered, but were skipped due to
the partial raster optimization. Logged for each raster task run in a
Renderer process. The histogram is suffixed by the RasterBufferProvider
which is in use.
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.
bbudge@chromium.org
bradnelson@chromium.org
The size of the contiguous memory block reserved in the renderer so that
large allocations are more likely to succeed. The reservation is currently
made in BlinkInitializer.
ericrk@chromium.org
Size of the in-use portion of the ResourcePool. Recorded each time resources
are reclaimed after tile work completes.
wiltzius@chromium.org
Time to capture a renderer snapshot.
Deprecated in 06/2018, M69. Renderer4.SoftwareCompositorThreadImplDrawDelay
is no longer needed due to issue 851784.
wiltzius@chromium.org
Time between frames when the software renderer is being used, as measured on
the compositor thread. This is collected once per frame while it is being
drawn to the screen in the compositor.
wiltzius@chromium.org
Time between frames when the page is not GPU accelerated.
vmpstr@chromium.org
Software image decode usage statistics. Images are decoded and locked prior
to raster; this indicates how that decode is used during tile management.
vmpstr@chromium.org
Indication whether the first lock of an image decode was wasted (image was
not used). Images are decoded and locked prior to raster; this indicates
whether the decode was used or not during the first lock.
Deprecated in issue 755432 as no longer being needed.
wiltzius@chromium.org
Time spent by WebKit painting the page, in milliseconds, when the page is
not GPU accelerated.
Deprecated in issue 755432 as no longer being needed.
wiltzius@chromium.org
WebKit paint throughput, measured in megapixels per second, when the page is
not GPU accelerated.
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.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
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.
tdresser@chromium.org
For every wheel tick, we record whether the scroll occurred on the main
thread, on the compositor thread, or on the compositor thread but blocked on
the main thread. The last case will happen when there is a blocking event
listener.
Deprecated 6/2018 and replaced with
PageScheduler.PageLifecycleStateTransition.
fmeawad@chromium.org
panicker@chromium.org
Tracks the transitions of the renderer scheduler when it is backgrounded.
Once it is backgrounded, it can be stopped after a timeout, stopped due to
critical resources, resumed or foregrounded.
Replaced with RendererScheduler.BackgroundRendererMainThreadLoad2 as of May
2017.
altimin@chromium.org
Renderer main thread load when renderer is backgrounded, i.e. percentage of
time spent on running tasks.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per minute per
renderer amortized.
Replaced with
RendererScheduler.RendererMainThreadLoad3.Background.AfterFirstMinute as of
July 2017.
altimin@chromium.org
Renderer main thread load when renderer is backgrounded, i.e. percentage of
time spent on running tasks.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per minute per
renderer amortized.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.ExpectedQueueingTimeByFrameStatus2 as of Feb
2018. Buckets were changed.
npm@chromium.org
tdresser@chromium.org
Expected queueing time split by tasks according to their frame status, in
microseconds. The sum of the split values will be equal to the total,
reported on RendererScheduler.ExpectedTaskQueueingDuration2. Recorded for
each 1000 ms window.
npm@chromium.org
tdresser@chromium.org
Expected queueing time split by tasks according to their frame status, in
microseconds. The sum of the split values will be equal to the total,
reported on RendererScheduler.ExpectedTaskQueueingDuration3. Recorded for
each 1000 ms window.
Replaced with RendererScheduler.ExpectedQueueingTimeByFrameStatus as of
December 2017.
npm@chromium.org
Expected queueing time split by tasks according to their frame type. The sum
of the split values should be equal to the total, reported on
RendererScheduler.ExpectedTaskQueueingDuration. Recorded for each 1000 ms
window.
Replaced with RendererScheduler.ExpectedQueueingTimeByTaskQueue2 as of Feb
2018. Buckets were changed.
npm@chromium.org
tdresser@chromium.org
Expected queueing time split by tasks according to the type of their task
queue, in microseconds. The sum of the split values should be equal to the
total, reported on RendererScheduler.ExpectedTaskQueueingDuration2. Recorded
for each 1000 ms window.
npm@chromium.org
tdresser@chromium.org
Expected queueing time split by tasks according to the type of their task
queue, in microseconds. The sum of the split values should be equal to the
total, reported on RendererScheduler.ExpectedTaskQueueingDuration3. Recorded
for each 1000 ms window.
Replaced with RendererScheduler.ExpectedQueueingTimeByTaskQueue as of
December 2017.
npm@chromium.org
Expected queueing time split by tasks according to the type of their task
queue. The sum of the split values should be equal to the total, reported on
RendererScheduler.ExpectedTaskQueueingDuration. Recorded for each 1000 ms
window.
Deprecated 04/2018.
tdresser@chromium.org
Expected queueing time for events which were queued on the main thread
longer or shorter than a threshold, given by the QueueingTimeThreshold
suffix.
Team: input-dev@chromium.org.
tdresser@chromium.org
The estimated queueing duration which would be observed for additional high
priority tasks posted to the RendererScheduler. Recorded for each 1000 ms
window.
Replaced with RendererScheduler.ExpectedTaskQueueingDuration3 as of Feb
2018. Buckets were changed.
tdresser@chromium.org
npm@chromium.org
The estimated queueing duration which would be observed for additional high
priority tasks posted to the RendererScheduler, in microseconds. Recorded
for each 1000 ms window.
tdresser@chromium.org
npm@chromium.org
The estimated queueing duration which would be observed for additional high
priority tasks posted to the RendererScheduler, in microseconds. Recorded
for each 1000 ms window.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
tdresser@chromium.org
npm@chromium.org
The estimated queueing duration which would be observed for additional high
priority tasks posted to the RendererScheduler, in microseconds, for
renderer processes that do not host any main frame. Recorded for each 1000
ms window.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced with RendererScheduler.ForegroundRendererMainThreadLoad2 as of May
2017.
altimin@chromium.org
Renderer main thread load when renderer is foregrounded, i.e. percentage of
time spent on running tasks.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per minute per
renderer amortized.
Replaced with
RendererScheduler.RendererMainThreadLoad3.Foreground.AfterFirstMinute as of
July 2017.
altimin@chromium.org
Renderer main thread load when renderer is foregrounded, i.e. percentage of
time spent on running tasks.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per minute per
renderer amortized.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
lpy@chromium.org
This boolean keeps track the count of the visibility change of a frame.
Recorded every time when the visibility of a frame is changed.
maxlg@chromium.org
The single maximum estimated queueing duration (or max queueing time)
between when user starts navigation and user navigates away. Navigate-away
is defined as a fast shutdown or a natural ending of renderer, or the new
navigation start which replacing the old navigation.
The queueing time is estimated on a sliding window basis. The width of the
sliding window is 1 second, the sliding step being 50ms. The max queueing
time keeps track of the largest queueing time on each slide.
This metric resets itself at navigation start, updates the max of queueing
time with the sliding window moving, reports the max queueing times to the
histogram at the next navigation start of the same or different renderer
process.
Replaced with RendererScheduler.NumberOfTasksPerQueueType2 as of May 2017.
altimin@chromium.org
alexclarke@chromium.org
The number of completed renderer tasks split per task queue type. Used to
monitor usage of each type of task queue. Reported each time when task is
completed.
Replaced with RendererScheduler.TaskCountPerQueueType as of July 2017.
altimin@chromium.org
alexclarke@chromium.org
The number of completed renderer tasks split per task queue type. Used to
monitor usage of each type of task queue. Reported each time when task is
completed.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Deprecated as of 08/2017. Replaced with
RendererScheduler.ExpectedQueueingTimeWhenQueueingTime.
tdresser@chromium.org
Time between sending an event to the renderer main thread and when the
renderer begins to process that event, for events which were dispatched when
the expected queueing time was past some threshold.
Team: input-dev@chromium.org.
This metric still used 1-minute reporting chunks. Replaced with
RendererMainThreadLoad4 as of July 2017.
altimin@chromium.org
Renderer main thread load (percentage of time spent in tasks), reported in
one minute chunks.
See http://bit.ly/chromium-renderer-main-thread-load-metric for details.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per second per
renderer amortized.
Replaced with RendererMainThreadLoad5 as of August 2017.
altimin@chromium.org
Renderer main thread load (percentage of time spent in tasks), reported in
one second chunks.
See http://bit.ly/chromium-renderer-main-thread-load-metric for details.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per second per
renderer amortized.
altimin@chromium.org
Renderer main thread load (percentage of time spent in tasks), reported in
one second chunks.
See http://bit.ly/chromium-renderer-main-thread-load-metric for details.
This metric is emitted when the renderer main thread task is completed or
renderer is backgrounded or foregrounded, at most once per second per
renderer amortized.
altimin@chromium.org
The number of completed renderer tasks split per frame type. Used to monitor
usage of each type of frame. Reported each time when task is completed.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
The number of completed renderer tasks split per task queue type. Used to
monitor usage of each type of task queue. Reported each time when task is
completed.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.TaskCPUDurationPerTaskType2.DedicatedWorker
as of June 2018 due to overflows (crbug.com/809668). Some metrics are
incremented with large amounts that they sometimes overflow and roll
negative before they get uploaded.
altimin@chromium.org
Total duration of dedicated worker tasks (thread time) split by per thread
type. Reported each time when task is completed and current accumulated
duration is longer than 1ms.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
Total duration (reported in full seconds) of dedicated worker tasks (thread
time) split by per thread type. Note that partial seconds are rounded
up/down so that they average to the correct value when many reports are
added. For more details, check base::ScaledLinearHistogram.
This is reported each time a task is completed.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.TaskCPUDurationPerThreadType2 as of June
2018 due to overflows (crbug.com/809668). Some metrics are incremented with
large amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
Total cpu time of renderer tasks split by per thread type. Wall time is
tracked by RendererScheduler.TaskDurationPerThreadType histogram. This
histogram is used to compare CPU usage of tasks from different threads.
Only 1% of randomly sampled tasks have cpu time measured and report duration
for this histogram.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
Total cpu time (reported in full seconds) of renderer tasks split by per
thread type. Note that partial seconds are rounded up/down so that they
average to the correct value when many reports are added. For more details,
check base::ScaledLinearHistogram.
Wall time is tracked by RendererScheduler.TaskDurationPerThreadType
histogram. This histogram is used to compare CPU usage of tasks from
different threads.
Only 1% of randomly sampled tasks have cpu time measured and report duration
for this histogram.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.TaskDurationPerFrameOriginType2 as of June
2018 due to overflows (crbug.com/809668). Some metrics are incremented with
large amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
Total cpu time of renderer tasks split by per frame origin type (main frame
vs same-origin frame vs cross-origin frame).
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
Total cpu time (reported in full seconds) of renderer tasks split by per
frame origin type (main frame vs same-origin frame vs cross-origin frame).
Note that partial seconds are rounded up/down so that they average to the
correct value when many reports are added. For more details, check
base::ScaledLinearHistogram.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.TaskDurationPerFrameType2 due to the
introduction of new types of frames as of 11/2017.
altimin@chromium.org
Total duration of renderer per-frame tasks split per frame type. Used to
monitor workload coming from different frames. Reported each time when task
is completed and current accumulated duration is longer than 1ms.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
Replaced with RendererScheduler.TaskDurationPerFrameType3 as of June 2018
due to overflows (crbug.com/809668). Some metrics are incremented with large
amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
Total duration of renderer per-frame tasks split per frame type. Used to
monitor workload coming from different frames. Reported each time when task
is completed and current accumulated duration is longer than 1ms.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
altimin@chromium.org
Total duration (reported in full seconds) of renderer per-frame tasks split
per frame type. Note that partial seconds are rounded up/down so that they
average to the correct value when many reports are added. For more details,
check base::ScaledLinearHistogram.
Used to monitor workload coming from different frames. Reported each time a
task is completed.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
Replaced with RendererScheduler.TaskDurationPerQueueType2 as of May 2017.
altimin@chromium.org
alexclarke@chromium.org
Total duration of renderer tasks split per task queue type. Used to monitor
usage of each type of task queues. Reported each time when task is completed
and current accumulated duration is longer than 1ms.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
Replaced with RendererScheduler.TaskDurationPerQueueType3 as of June 2018
due to overflows (crbug.com/809668). Some metrics are incremented with large
amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
alexclarke@chromium.org
Total duration of renderer tasks split per task queue type. Used to monitor
usage of each type of task queues. Reported each time when task is completed
and current accumulated duration is longer than 1ms.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
alexclarke@chromium.org
Total duration (reported in full seconds) of renderer tasks split per task
queue type. Note that partial seconds are rounded up/down so that they
average to the correct value when many reports are added. For more details,
check base::ScaledLinearHistogram.
Used to monitor usage of each type of task queues. Reported each time a task
is completed.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
Replaced with RendererScheduler.TaskDurationPerTaskType2 as of June 2018 due
to overflows (crbug.com/809668). Some metrics are incremented with large
amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
hajimehoshi@chromium.org
Total duration of renderer per-frame tasks split per task type. Used to
monitor usage of each task type. Reported each time when task is completed
and current accumulated duration is longer than 1ms.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
Replaced with RendererScheduler.TaskDurationPerTaskType2.DedicatedWorker as
of June 2018 due to due to overflows (crbug.com/809668). Some metrics are
incremented with large amounts that they sometimes overflow and roll
negative before they get uploaded.
altimin@chromium.org
Total duration of dedicated worker tasks (wall time) split by per thread
type. Reported each time when task is completed and current accumulated
duration is longer than 1ms.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
hajimehoshi@chromium.org
Total duration (reported in full seconds) of renderer per-frame tasks split
per task type. Note that partial seconds are rounded up/down so that they
average to the correct value when many reports are added. For more details,
check base::ScaledLinearHistogram.
Used to monitor usage of each task type. Reported each time a task is
completed.
This metric is susceptible to problematic outliers and should be analyzed
with custom scripts accounting for that rather than from a dashboard.
altimin@chromium.org
Total duration (repored in full seconds) of dedicated worker tasks (wall
time) split by per thread type. Note that partial seconds are rounded
up/down so that they average to the correct value when many reports are
added. For more details, check base::ScaledLinearHistogram.
Reported each time a task is completed.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.TaskDurationPerThreadType2 as of June 2018
due to overflows (crbug.com/809668). Some metrics are incremented with large
amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
lpy@chromium.org
Total duration of renderer tasks split by per thread type. Used to compare
CPU usage of tasks from different threads. Reported each time when task is
completed and current accumulated duration is longer than 1ms.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
altimin@chromium.org
lpy@chromium.org
Total duration (reported in full seconds) of renderer tasks split by per
thread type. Note that partial seconds are rounded up/down so that they
average to the correct value when many reports are added. For more details,
check base::ScaledLinearHistogram.
Used to compare CPU usage of tasks from different threads. Reported each
time a task is completed.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Replaced with RendererScheduler.TaskDurationPerUseCase2 as of June 2018 due
to overflows (crbug.com/809668). Some metrics are incremented with large
amounts that they sometimes overflow and roll negative before they get
uploaded.
altimin@chromium.org
farahcharab@chromium.org
Total duration (measured in ms) of renderer main thread tasks split by
scheduler use case. Use case is a scheduler's educated guess of the current
state of the world. See renderer/use_case.h and
RendererSchedulerImpl::UpdatePolicy for more details.
altimin@chromium.org
farahcharab@chromium.org
Total duration (reported in full seconds) of renderer main thread tasks
split by scheduler use case. Note that partial seconds are rounded up/down
so that they average to the correct value when many reports are added. For
more details, check base::ScaledLinearHistogram.
Use case is a scheduler's educated guess of the current state of the world.
See renderer/use_case.h and
RendererSchedulerImpl::UpdatePolicy for more details.
Removed from code 2017-08.
alexclarke@chromium.org
The delta between when a delayed task was scheduled to run and when the
RendererScheduler actually ran it. Note: to reduce overhead only 10% of
tasks are sampled.
Removed from code 2017-08.
alexclarke@chromium.org
The queueing duration for non-delayed tasks posted to the RendererScheduler.
This metric is only recorded if TrackingInfo::time_posted is set (i.e. not
on android). Note: to reduce overhead only 10% of tasks are sampled.
Replaced with RendererScheduler.TaskTime2 as of May 2017.
sunyunjia@chromium.org
tdresser@chromium.org
The duration of every task queued in the _renderer_ scheduler to see the
distribution of the task duration.
sunyunjia@chromium.org
tdresser@chromium.org
The duration of every task queued in the _renderer_ scheduler to see the
distribution of the task duration.
Note that this metric discards tasks longer than 30 seconds because they are
considered to be a result of measurement glitch.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
maxlg@chromium.org
The count of same-document-navigations split by whether it is the
same-document backward/forward navigation, history API navigation, or other
fragment navigation.
Removed from code 2017-08.
alexclarke@chromium.org
Duration of gestures (scrolls and pinches).
Removed from code 2017-08.
alexclarke@chromium.org
Whether a user gesture was predicted correctly.
Removed from code 2017-08.
alexclarke@chromium.org
Time between when the UserModel was last reset (which happens on navigation)
and a gesture starting.
Removed from code 2017-08.
alexclarke@chromium.org
Time between subsequent gestures (scrolls and pinches).
altimin@chromium.org
Number of web frame schedulers per renderer scheduler. Recorded once per
navigation.
altimin@chromium.org
Number of web view schedulers per renderer scheduler. Recorded once per
navigation.
ppi@chromium.org
Roundtrip times for synchronous IPC calls from the renderer to browser.
engedy@chromium.org
For each load and dropped Mojo interface request in a frame, records a
sample with a value corresponding to the hash of the interface name,
calculated as the lower 31 bits of the interface name's metric name hash.
Interface requests to RenderFrame::GetRemoteInterfaces are dropped when they
arrive to the RenderFrameHostImpl after the RenderFrameHostImpl had already
committed the next cross-document navigation.
This means that |document_scoped_interface_provider_binding_| was already
unbound at the time from the interface connection that had been used to
service RenderFrame::GetRemoteInterface for the previous load, so those
interface requests are dropped.
engedy@chromium.org
For each load in a frame, records the number of interface requests to
RenderFrame::GetRemoteInterfaces that arrived to the RenderFrameHostImpl
after the RFHI had already committed the next cross-document navigation.
This means that |document_scoped_interface_provider_binding_| was already
unbound at the time from the interface connection that had been used to
service RenderFrame::GetRemoteInterface for the previous load, so those
interface requests are dropped. This histogram measures how often, if at
all, that happens in practice.
alexmos@chromium.org
boliu@chromium.org
Record whether a local root frame ever received post messages from another
cross origin frame that's not a descendent. This is useful to evaluate if a
frame is safe to be reloaded automatically. Recorded when a frame crashed
while invisible, and then becomes visible to the user; this is the point a
crashed frame would be reloaded. Note this is not logged for the main frame,
which only has descendant frames.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidChangeScrollOffset.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidClearWindowObject.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidCommitProvisionalLoad.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidCreateScriptContext.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidFailProvisionalLoad.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidFinishDocumentLoad.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidFinishLoad.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidMeaningfulLayout.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.DidStartProvisionalLoad.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.FocusedNodeChanged.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.OnMessageReceived.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.ScriptedPrint.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.WillCommitProvisionalLoad.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.WillSendSubmitEvent.
Deprecated 2/2018
joelhockey@chromium.org
Cumulative time spent by all RenderFrameObservers in
RenderFrameImpl.WillSubmitForm.
jochen@chromium.org
State of the profile that is activated via the "Open Link as User"
menu. Logged when one of the "Open Link as User" context menu
options is selected.
jochen@chromium.org
Whether or not other profiles are active when the "Open Link as
User" context menu is shown. Logged when the context menu is created.
jochen@chromium.org
Count of the profiles shown for the "Open Link as User" context
menu. Logged when the context menu is created.
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.
Moved to Net.Reporting.HeaderEndpointGroupOutcome.
juliatuttle@chromium.org
The outcome of Reporting trying to process a single endpoint group in a
Report-To header once the header itself has been parsed.
Moved to Net.Reporting.HeaderEndpointOutcome.
juliatuttle@chromium.org
The outcome of Reporting trying to process a single endpoint in a Report-To
header once the header itself has been parsed.
Moved to Net.Reporting.HeaderOutcome.
juliatuttle@chromium.org
The outcome of Reporting trying to process a Report-To header. Once it is
parsed, Reporting.HeaderEndpointOutcome records the outcome of the endpoints
within it.
Moved to Net.Reporting.ReportDeliveredAttempts.
juliatuttle@chromium.org
When Reporting successfully delivers a report, the number of unsuccessful
delivery attempts that preceded the successful one.
Moved to Net.Reporting.ReportDeliveredLatency.
juliatuttle@chromium.org
The delivery latency of reports successfully delivered by Reporting. Starts
when the report is queued and finishes when the delivery attempt returns
successfully.
Moved to Net.Reporting.ReportOutcome.
juliatuttle@chromium.org
The outcome of Reporting trying to deliver a report, recorded when the
report is finally erased from memory.
Deprecated as of 5/5/2016.
estade@chromium.org
The state of the requestAutocomplete() dialog when it was dismissed.
Deprecated as of 5/5/2016.
estade@chromium.org
The initial state of a user that's interacting with a freshly shown
requestAutocomplete() dialog.
Deprecated as of 5/5/2016.
estade@chromium.org
User interactions with the Autofill popup shown while filling an
requestAutocomplete() dialog.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the frequency of security warnings and errors in the
RequestAutocomplete dialog.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the duration for which an requestAutocomplete() dialog was shown.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the duration for which an requestAutocomplete() dialog was shown,
in cases where the user ended up canceling out of the dialog.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the duration for which an requestAutocomplete() dialog was shown,
in cases where the user ended up accepting the dialog.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures how users are interacting with the requestAutocomplete() dialog UI.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the duration of time it takes for the requestAutocomplete() UI to
be actionable by the user after it is shown.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the frequency of errors in communicating with the Google Online
Wallet server.
Deprecated as of 5/5/2016.
estade@chromium.org
Measures the frequency of required user actions returned by the Google
Online Wallet server.
merkulova@chromium.org
Records the number of times the factory reset dialog was shown. Grouped by
the viewtype.
lpy@chromium.org
The number of IPCs from frame to GRC. Recorded every 1 minute.
lpy@chromium.org
The number of IPCs from page to GRC. Recorded every 1 minute.
lpy@chromium.org
The number of IPCs from process to GRC. Recorded every 1 minute.
sebmarchand@chromium.org
The result of opening the Local Site Characteristics database.
sebmarchand@chromium.org
The result of opening the Local Site Characteristics database after deleting
it after a failed repair attempt.
sebmarchand@chromium.org
The result of opening the Local Site Characteristics database after a repair
attempt.
sebmarchand@chromium.org
The result of trying to repair the Local Site Characteristics database after
a failed open.
sebmarchand@chromium.org
The cumulative observation time before a feature tracked in the Local Site
Characteristics database gets used.
sebmarchand@chromium.org
The size of the Local Site Characteristics database on disk. Recorded at
startup when the database gets opened.
sebmarchand@chromium.org
Boolean indicating if the read operation from the Local Site Characteristics
database has completed when we query for the characteristics of a site.
tbansal@chromium.org
The count of resource loading blocking patterns received by the renderer.
Recorded every time resource loading hints mojom message is received.
Recorded at most once per triggered navigation.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
Like HttpCache.Pattern but only for requests made during speculative
prefetch. Logged per successful request.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
This metric measures the host coverage of the predictor database: On each
navigation, it records what percentage of the top X history entries are
found in the predictor DB. Caveats: (1) This metric is only recorded once
the user has accumulated enough browsing history, implemented as a minimum
threshold of total page visits by the user. (2) This metric is sampled, so
it's actually only recorded for 1 out of every K navigations.
Deprecated October 2016. No longer recorded.
zhenw@chromium.org
A boolean that used to indicate a corner case when certain resources are not
written to the Predictor database becuase their URLs are too long. We
monitor this number to ensure that we do not discard too many resources.
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.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
A boolean that used to indicate a corner case when we may not have prefetch
results even though prefetching is enabled and predictions are present,
because another navigation in the same tab canceled the prefetching of the
previous load.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
The visit count of a URL in the history database, measured when the onload
fires for the URL. Helpful in figuring out what visit count should be used
to start learning about a URL.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Assuming a fixed number (25 or 50) of URLs could be prefetched max, how many
would be available for prefetch (after we apply our heuristics for picking
subresources to prefetch for a navigation).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the cache restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the network restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Similar to ResourcePrefetchPredictor.Host.PredictedPrefetchFromNetwork but
as a percent of the total number of resources the page actually fetched from
the network. This depcits the major gains that we can get.
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page not used
by the page, restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the host of the main frame url
as the key for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
prefetches cancelled as a percentage of the total number of resources that
the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
prefetches failed as a percentage of the total number of resources that the
predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching but were not
requested by the page, as a percentage of the total number of resources that
the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching and also came
from the cache when the page requested it, as a percentage of the total
number of resources that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching but came from
the network when the page requested it, as a percentage of the total number
of resources that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from network while prefetching but were not
requested by the page, as a percentage of the total number of resources that
the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from network while prefetching but came from
the cache when the page requested it, as a percentage of the total number of
resources that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of
successful prefetches that came from cache while prefetching and also came
from the network when the page requested it, as a percentage of the total
number of resources that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of resources
that were prefetchable but were not prefetched as a percentage of
prefetchable resources.
Deprecated January 2017. This is effectively the same as
ResourcePrefetchPredictor.HostTableRowCount2 after refactoring of the
predictor database.
zhenw@chromium.org
The count of number of unique hosts in the HostTable, i.e. the number of
hosts that the database has prediction data for. This data is useful for
determining the recall/precision as a function of the number of hosts that
need to be tracked by the database. Measured at startup.
Deprecated January 2017. Replaced by
ResourcePrefetchPredictor.HostTableRowCount2.
zhenw@chromium.org
The count of number of rows in the HostTable. This is effecively the number
of (host, resource URL) pairs in the database. This is measured at startup
and used to get an estimate of the data size.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
The number of rows in the HostTable. This is effectively the number of hosts
in the database. This is measured at startup and used to get an estimate of
the data size.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
When the prefetch predictor has resources in the local database for a given
navigation, the count of predicted urls.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
When the prefetch predictor has resources in the local database for a given
navigation, the precision of the predictions, in percentage. This is
computed as 100 \times \frac{correct predictions}{predictions}.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
When the prefetch predictor has resources in the local database for a given
navigation, the recall of the predictions, in percentage. This is computed
as 100 \times \frac{correct predictions}{all prefetchable subresources}.
alexilin@chromium.org
Records stats about main frame navigations. Records the total number of
requests/responses/redirects for main frame urls along with the numbers for
how often the predictor can process such events. This is useful to figure
out what percentange of requests are handled by the predictor and also for
sanity checking the other stats.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Records stats about various interesting events such as - request start,
response start, redirect, onload, etc during the load of a main frame.
Essential for understanding the complete life of a navigation request start
to the onload fire and the events that occur in between.
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.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Records the number of pages on each type of network after a page is loaded.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Page load time. It starts from when the main frame URL request is sent out
to when the main frame document load is completed.
This is recorded for both prefetched and non-prefetched pages.
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.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
The count of successfully prefetched subresources for a single page.
Recorded after all subresource prefetches have reached a terminal
success/failure state.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
The total amount of data consumed by predictor for a single page. Only
successfully finished requests taken into account. Recorded after all
subresource prefetches have reached a terminal success/failure state.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
Number of resources that were prefetched and requested by a page load, for
cached requests. Logged after the prefetcher completes.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
Number of resources that were prefetched and requested by a page load, for
non cached requests. Logged after the prefetcher completes.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
Amount of useful data fetched from the network for a prefetch request. This
is the total size of the resources accounted for in
ResourcePrefetchPredictor.PrefetchHitsCount.NotCached. Logged after the
prefetcher completes.
alexilin@chromium.org
Amount of time available for prefetching. Specifically, this is a time
interval between corresponding StartPrefetching() and StopPrefetching()
calls. This is recorded for both prefetched and non-prefetched pages.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
Number of resources that were prefetched but not requested by a page load,
for cached requests. Logged after the prefetcher completes.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
Number of resources that were prefetched but not requested by a page load,
for non cached requests, that is waste. Logged after the prefetcher
completes.
Deprecated at M66. No longer recorded.
lizeb@chromium.org
Amount of wasted data fetched from the network for a prefetch request. This
is the total size of the resources accounted for in
ResourcePrefetchPredictor.PrefetchMissesCount.NotCached. Logged after the
prefetcher completes.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
When the prefetch predictor has resources in the local database for a given
navigation, records stats about whether redirect was predicted correctly or
incorrectly.
alexilin@chromium.org
Records stats about various interesting events such as - when partial or all
of history is cleared. It will include events which do not necessarily
happen during a navigation (which are reported in
ResourcePrefetchPredictor.NavigationEvent).
alexilin@chromium.org
Records stats about requests, redirects, and responses observed by the
LoadingPredictorObserver. These stats are useful as a baseline for other
stats.
Deprecated 08/2016 with the removal of the recording code.
zhenw@chromium.org
The distribution of the reasons for which subresources are ignored during
prefetching. This helps us prioritze reasons we should further investigate
to increase coverage. This is reported as a bit map and every status will be
a bitwise or of the underlying reasons.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Assuming a fixed number of URLs could be prefetched max (25 or 50), how many
would be available for prefetch (after we apply our heuristics for picking
subresources to prefetch for a navigation).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the cache restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page and served
from the network restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
Similar to ResourcePrefetchPredictor.Url.PredictedPrefetchFromNetwork but as
a percent of the total number of resources the page actually fetched from
the network. This depcits the major gains that we can get.
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
When we have predictions for a navigation, we measure the accuracy of the
predictions against the actual resources downloaded. This histogram gives
the distribution of the predictions that were fetched by the page not used
by the page, restricted to some max predictions (25 or 50).
This stat is recorded when the predictor uses the main frame url as the key
for prediction.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of prefetches
cancelled as a percentage of the total number of resources that the
predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of prefetches
failed as a percentage of the total number of resources that the predictor
tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching but were not requested by
the page, as a percentage of the total number of resources that the
predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching and also came from the
cache when the page requested it, as a percentage of the total number of
resources that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching but came from the network
when the page requested it, as a percentage of the total number of resources
that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from network while prefetching but were not requested
by the page, as a percentage of the total number of resources that the
predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from network while prefetching but came from the cache
when the page requested it, as a percentage of the total number of resources
that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on the main frame URL, the percentage of successful
prefetches that came from cache while prefetching and also came from the
network when the page requested it, as a percentage of the total number of
resources that the predictor tried to prefetch.
Deprecated September 2016. No longer recorded.
zhenw@chromium.org
For prefetching based on host of main frame URL, the percentage of resources
that were prefetchable but were not prefetched as a percentage of
prefetchable resources.
Deprecated September 2016. This is effectively the same as
ResourcePrefetchPredictor.UrlTableRowCount2 after refactoring of the
predictor database.
zhenw@chromium.org
The count of number of unique main frame urls in the UrlTable, i.e. the
number of webpages that the database has prediction data for. This data is
useful for determining the recall/precision as a function of the number of
webpages that need to be tracked by the database. Measured at startup.
Deprecated October 2012. No longer recorded.
zhenw@chromium.org
The count of number of unique main frame urls that are deleted from the URL
table at startup because they are no longer in history. Essential to figure
out how much data we are loosing out.
Deprecated October 2012. No longer recorded.
zhenw@chromium.org
Same as ResourcePrefetchPredictor.UrlTableMainFrameUrlsDeletedNotInHistory
but recording percentage of URLs in the table rather than absolute numbers.
Deprecated January 2017. Replaced by
ResourcePrefetchPredictor.UrlTableRowCount2.
zhenw@chromium.org
The count of number of rows in the UrlTable. This is effecively the number
of (main frame URL, resource URL) pairs in the database. This is measured at
startup and used to get an estimate of the data size.
Deprecated at M66. No longer recorded.
alexilin@chromium.org
The number of rows in the UrlTable. This is effectively the number of main
frame URLs in the database. This is measured at startup and used to get an
estimate of the data size.
afakhry@chromium.org
The CPU usage range reported for the browser process when the Chrome OS
device memory pressure (which is the percentage of total memory used by the
system) is critical. This is emitted only when memory pressure changes from
a low pressure to a higher pressure.
afakhry@chromium.org
The system memory usage range reported for the browser process when the
Chrome OS device memory pressure (which is the percentage of total memory
used by the system) is critical. This is emitted only when memory pressure
changes from a low pressure to a higher pressure.
afakhry@chromium.org
The CPU usage range reported for the GPU process when the Chrome OS device
memory pressure (which is the percentage of total memory used by the system)
is critical. This is emitted only when memory pressure changes from a low
pressure to a higher pressure.
afakhry@chromium.org
The system's RAM memory usage range reported for the GPU process when the
Chrome OS device memory pressure (which is the percentage of total memory
used by the system) is critical. This is emitted only when memory pressure
changes from a low pressure to a higher pressure.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between when the ResourceScheduler is informed of a
Client's creation or starts loading and when that Client finishes loading in
a Client which has been user-observable the entire time.
Note: Will not include time for the main resource if PlzNavigate is in use.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between when the ResourceScheduler is informed of a
Client's creation or starts loading and when that Client finishes loading in
a Client which has been background the entire time.
Note: Will not include time for the main resource if PlzNavigate is in use.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between when the ResourceScheduler is informed of a
Client's creation or starts loading and when that Client finishes loading in
a Client which has switched between Active and Background.
Note: Will not include time for the main resource if PlzNavigate is in use.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between the last time that a Client becomes
user-observable and when that Client finishes loading in a Client that was
user-observable when the load completed.
Note: Will not include time for the main resource if PlzNavigate is in use.
devdeepray@chromium.org
tbansal@chromium.org
Records the number of delayable requests in-flight when a non-delayable
request is started.
csharrison@chromium.org
The number of LoadAnyStartablePendingRequests scans that were skipped due to
smarter task scheduling around reprioritization.
tbansal@chromium.org
Records the highest number of delayable requests that were in-flight when
the given request with higher priority was in-flight.
tbansal@chromium.org
Records the count of number of requests in-flight. Recorded when a request
is started by the resource scheduler.
Deprecated 1/2016
aiolos@chromium.org
The amount of time the ResourceScheduler is throttling a request after
WillStartRequest is called for a request in a client that was
user-observable at creation and start time.
Deprecated 1/2016
aiolos@chromium.org
The amount of time the ResourceScheduler is throttling a request after
WillStartRequest is called for a request in a client that was background at
creation and start time.
Deprecated 1/2016
aiolos@chromium.org
The amount of time the ResourceScheduler is throttling a request after
WillStartRequest is called on a request without a Client or a request in a
Client which is in a different state since the request was made. Note that
this won't capture requests which have switched state an even number of
times. Switching from Active to Background back to Active will be recorded
in the Active version of this histogram.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between when the request was created and when the
ResourceScheduler stops throttling the request in a client that was
user-observable at creation and start time.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between when the request was created and when the
ResourceScheduler stops throttling the request in a client that was
background at creation and start time.
Deprecated 1/2016
aiolos@chromium.org
The amount of time between when the request was created and when the
ResourceScheduler stops throttling a request without a client or a request
in a Client which is in a different state since the request was made. Note
that this won't capture requests which have switched state an even number of
times. Switching from Active to Background back to Active will be recorded
in the Active version of this histogram.
wzang@chromium.org
Record if updating |should_send_rlz_ping| in RW_VPD is successful within the
maximum retry counts.
Replaced with Tabs.SadTab.* in R20.
Please list the metric's owners. Add more owner tags as needed.
Track number of times we built a sad tab page for a renderer crash or kill.
The user may not have seen the page if it was not the frontmost tab.
Replaced with Tabs.SadTab.* in R20.
Please list the metric's owners. Add more owner tags as needed.
Track number of times the user actually saw a sad tab page for a renderer
crash or kill.
Not in the code anymore (10/2015).
feng@chromium.org
Records the user action that enables/disables safe browsing feature in the
Settings page on Android.
nparker@chromium.org
The result of reading/parsing/accepting a new proto for the FileTypePolices
repo of file extensions and their meta data.
This is for the file types loaded from the component-update system. This
includes both those loaded from disk shortly after startup, and those
received over the network when the component version changes
nparker@chromium.org
Number of file types (aka file extensions) present in the FileTypePolicies
proto loaded.
This is for the file types loaded from the component-update system. This
includes both those loaded from disk shortly after startup, and those
received over the network when the component version changes
nparker@chromium.org
Integer version number citing which version of the proto data chrome just
loaded. Latest version is in download_file_types.asciipb.
This is for the file types loaded from the component-update system. This
includes both those loaded from disk shortly after startup, and those
received over the network when the component version changes
nparker@chromium.org
The result of reading/parsing/accepting a new proto for the FileTypePolices
repo of file extensions and their meta data.
This is for the file types loaded from the resource bundle packaged with
Chrome, which is always loaded at startup.
nparker@chromium.org
Number of file types (aka file extensions) present in the FileTypePolicies
proto loaded.
This is for the file types loaded from the resource bundle packaged with
Chrome, which is always loaded at startup.
nparker@chromium.org
Integer version number citing which version of the proto data chrome just
loaded. Latest version is in download_file_types.asciipb.
This is for the file types loaded from the resource bundle packaged with
Chrome, which is always loaded at startup.
Replaced by SafeBrowsing.V4GetHash.Network.Result.
kcarattini@google.com
Response or error codes from the SafeBrowsing Pver4 service. Logged after a
GetHash or request finishes to capture the response code or error code for
that call.
Replaced by SafeBrowsing.V4GetHash.Network.Time.
kcarattini@chromium.org
The time that it took to receive a response from the Safe Browsing servers
for a V4 GetHash request.
Replaced by SafeBrowsing.V4GetHash.Result.
kcarattini@chromium.org
Track return status from V4 GetHash attempts. The buckets of this histogram
overlap, so the counts cannot be used as percentages.
ntfschr@chromium.org
Which interstitial type is being displayed to the user? This currently
applies only to WebView (where we show Loud vs. Quiet interstitials).
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.
jialiul@chromium.org
Count of how many ResolvedIPAddresses get removed in each periodic clean up.
This is a rough estimation of the number of IPs associated with main frame
and sub-frame navigations every two minutes.
jialiul@chromium.org
Count of how many NavigationEvents get removed in each periodic clean up.
This is a rough estimation of the number of navigations every two minutes.
nparker@chromium.org
The net error code for failed reports sent by NotificationImageReporter, or
net::OK if successful.
Replaced by SafeBrowsing.V4GetHash.Parse.Result.
kcarattini@chromium.org
Track the parsing results of a status 200 GetV4Hash request.
Replaced by SafeBrowsing.V4Update.Parse.Result.
vakh@chromium.org
Track the parsing results of a status 200 GetV4Update request.
nparker@chromium.org
Whether the Safe Browsing extended reporting service is currently enabled.
Recorded for all non-Incognito profiles on profile startup.
nparker@chromium.org
Whether the Safe Browsing service is currently enabled. Recorded for all
non-Incognito profiles on profile startup.
lpz@chromium.org
Whether the current user has ever seen a security interstitial. Recorded for
all non-Incognito profiles on profile startup.
lpz@chromium.org
Tracks the Extended Reporting preference transition. Suffixes track which
opt-in text users are viewing and the values of each Extended Reporting
preference. Recorded for all non-Incognito profiles on profile startup.
lpz@chromium.org
Tracks user decisions about the Extended Reporting opt-in on security
interstitials by comparing the initial and final states of the preference.
Suffixes specify the type of change that was made. Recorded when a user
closes a security interstitial or navigates away.
lpz@chromium.org
Tracks the Extended Reporting preference being changed. Suffixes track which
Extended Reporting preference was changed, and the specific UI that the
change was made on. Recorded when a user changes the preference on any UI.
lpz@chromium.org
Tracks reasons for the Extended Reporting preference transition, such as a
user entering an experiment group or seeing a security interstitial for the
first time. Recorded for all non-Incognito profiles on profile startup.
jialiul@chromium.org
The result of referrer attribution, including different types of success or
failure. This is incremented each time a safe browsing ping or download ping
is generated.
jialiul@chromium.org
Number of times referrer attribution encounters an invalid tab ID. This is
incremented a safe browsing ping or download ping is generated and an
invalid tab ID is encountered during attribution.
jialiul@chromium.org
The length of referrer URL chain we get from referrer attribution. This is
incremented each time a safe browsing ping or download ping is generated.
lpz@chromium.org
A threat report contains a DOM hierarchy that is ambiguous. This indicates
that the parent/child relationship among the elements in the DOM may not be
accurate.
lpz@chromium.org
Whether the threat report generated for a subframe of a page hit the maximum
number of nodes. When this is true, the data from that frame will be
truncated.
lpz@chromium.org
Tracks the actions taken by the Ad Sampling trigger whenever it is executed.
lpz@chromium.org
Tracks the state of the Suspicious Site trigger when its report delay timer
fires. Used to investigate variance in event order.
lpz@chromium.org
Tracks the events occurring in the Suspicious Site trigger whenever it is
executed.
lpz@chromium.org
Tracks the reasons that a report requested by the Suspicious Site trigger is
rejected by the Trigger Manager.
asanka@chromium.org
File types that were allowed to be downloaded without verifying their
content nor their source URLs with Safe Browsing.
asanka@chromium.org
File types that were allowed to be downloaded without verifying their
content nor their source URLs with Safe Browsing due to the requestor URL
being on the Safe Browsing whitelist. Each sample recorded on this histogram
is also recorded in SafeBrowsing.UnverifiedDownloads.Allowed.
asanka@chromium.org
File types that were allowed to be downloaded without verifying their
content nor their source URLs with Safe Browsing due to the SafeBrowsing
service being disabled. Each sample recorded on this histogram is also
recorded in SafeBrowsing.UnverifiedDownloads.Allowed.
asanka@chromium.org
Count of alternate extensions that were supplied when attempting to download
a file without verifying their content nor their source URLs with Safe
Browsing.
asanka@chromium.org
File types that were blocked from downloaded without verifying their content
nor their source URLs with Safe Browsing.
Deprecated 04/25/2018 since it was not being used actively or monitored.
vakh@chromium.org
Records the time it takes to copy the SafeBrowsing list update as a string,
into a map which contains the hash prefixes that are looked up when a client
queries for the reputation of a resource (URL, full hash, etc.).
Replaced by SafeBrowsing.V4AddUnlumpedHashes.Time.
vakh@chromium.org
Records the time it takes to copy the SafeBrowsing list update as a string,
into a map which contains the hash prefixes that are looked up when a client
queries for the reputation of a resource (URL, full hash, etc.).
Replaced by SafeBrowsing.V4*.ApplyUpdate.Result.
vakh@chromium.org
Track the result of applying the update fetched from the PVer4 service for a
particular store.
Replaced by SafeBrowsing.V4ReadFromDisk.ApplyUpdate.Result.
vakh@chromium.org
Track the result of applying an update read from disk after parsing it
successfully as a protobuf.
vakh@chromium.org
The size of the SafeBrowsing database or file on disk in kilobytes, after
reading it from disk on startup and after a database update has occurred.
vakh@chromium.org
The time it takes to parse and load the SafeBrowsing database from disk, in
milliseconds.
Replaced by SafeBrowsing.V4*.DecodeAdditions.Result.
vakh@chromium.org
Track the result of decoding the Rice-encoded list of additions of 4-byte
hash prefixes. This is logged once per store, per update containing
Rice-encoded additions.
Replaced by SafeBrowsing.V4*.DecodeAdditions.Time.
vakh@chromium.org
Records the time it takes to decode the Rice-encoded additions to the
blacklist into raw format.
Replaced by SafeBrowsing.V4ProcessPartialUpdate.DecodeRemovals.Result.
vakh@chromium.org
Track the result of decoding the Rice-encoded list of indexes of hash
prefixes to remove since the last update. This is logged once per store, per
update containing Rice-encoded removals.
Replaced by SafeBrowsing.V4ProcessPartialUpdate.DecodeRemovals.Time.
vakh@chromium.org
Records the time it takes to decode the Rice-encoded removals from the
blacklist into raw format.
Replaced by SafeBrowsing.V4GetHash.CacheHit.Result.
kcarattini@chromium.org
vakh@chromium.org
Track cache hits for V4 full hashes.
kcarattini@chromium.org
vakh@chromium.org
Track cache hits for V4 full hashes.
kcarattini@chromium.org
vakh@chromium.org
Track get hash response hits for V4 full hash requests.
kcarattini@google.com
vakh@google.com
Response or error codes from the SafeBrowsing Pver4 service. Logged after a
GetHash or request finishes to capture the response code or error code for
that call.
kcarattini@chromium.org
vakh@chromium.org
The time that it took to receive a response from the Google SafeBrowsing
servers for a full hash request.
kcarattini@chromium.org
vakh@chromium.org
Track the parsing results of a status 200 GetV4Hash request.
kcarattini@chromium.org
vakh@chromium.org
Track return status from V4 GetHash attempts. The buckets of this histogram
overlap, so the counts cannot be used as percentages.
Replaced by SafeBrowsing.V4GetHash.Check.Result.
kcarattini@chromium.org
vakh@chromium.org
Track get hash response hits for V4 full hash requests.
Replaced by SafeBrowsing.V4GetHash.Network.Time.
vakh@chromium.org
The time that it took to receive a response from the Google SafeBrowsing
servers for a full hash request.
Deprecated in favor of the TimeUs variant
vakh@chromium.org
The time that it took to check a URL against our in-memory database. It is
dominated by the time to perform checks for CheckBrowseUrl.
csharrison@chromium.org
vakh@chromium.org
The time that it took to check a URL against our in-memory database. It is
dominated by the time to perform checks for CheckBrowseUrl. Note that this
metric is recorded even for users with low resolution clocks.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by SafeBrowsing.V4*.MergeUpdate.Time.
vakh@chromium.org
Records the time it takes to merge the existing state of the list with the
update. The update may have been received from the server, or it may have
just been read from disk.
vakh@chromium.org
Track the result of applying a full update for a store received from PVer4
SafeBrowsing service.
vakh@chromium.org
Records the time it takes to process a SafeBrowsing list full update. It
includes V4AddUnlumpedHashes.Time for each prefix-sized list, and
V4ProcessFullUpdate.MergeUpdate.Time. Additionally, if the update is
Rice-encoded, it includes V4ProcessFullUpdate.DecodeAdditions.Time for each
prefix-sized list that's Rice-encoded.
vakh@chromium.org
Track the result of decoding the Rice-encoded list of additions of 4-byte
hash prefixes. This is logged once per store, per update containing
Rice-encoded additions. This histogram is specific to processing full
updates received from the server.
vakh@chromium.org
Records the time it takes to decode the Rice-encoded additions to the
blacklist into raw format when applying a full update to a store.
Deprecated 04/25/2018 since it was not being used actively or monitored.
vakh@chromium.org
Records the time it takes to merge the existing state of the list with a
full update received from the server.
Replaced by SafeBrowsing.V4ProcessFullUpdate.ApplyUpdate.Time.
vakh@chromium.org
Records the time it takes to process a SafeBrowsing list full update. It
includes V4AddUnlumpedHashesTime for each prefix-sized list, and
V4MergeUpdateTime. Additionally, if the update is Rice-encoded, it includes
V4DecodeAdditionsTime for each prefix-sized list that's Rice-encoded.
vakh@chromium.org
Track the result of applying a partial update for a store received from
PVer4 SafeBrowsing service.
vakh@chromium.org
Records the time it takes to process a SafeBrowsing list partial update. It
includes V4AddUnlumpedHashes.Time for each prefix-sized list, and
SafeBrowsing.V4ProcessPartialUpdate.MergeUpdate.Time. Additionally, if the
update is Rice-encoded, it includes
V4ProcessPartialUpdate.DecodeRemovals.Time, and
V4ProcessPartialUpdate.DecodeAdditions.Time for each prefix-sized list
that's Rice-encoded.
vakh@chromium.org
Track the result of decoding the Rice-encoded list of additions of 4-byte
hash prefixes. This is logged once per store, per update containing
Rice-encoded additions. This histogram is specific to processing partial
updates received from the server.
vakh@chromium.org
Records the time it takes to decode the Rice-encoded additions to the
blacklist into raw format when applying a partial update to a store.
vakh@chromium.org
Track the result of decoding the Rice-encoded list of indexes of hash
prefixes to remove since the last update. This is logged once per store, per
update containing Rice-encoded removals.
vakh@chromium.org
Records the time it takes to decode the Rice-encoded removals from the
blacklist into raw format when applying a partial update to a store.
Deprecated 04/25/2018 since it was not being used actively or monitored.
vakh@chromium.org
Records the time it takes to merge the existing state of the list with a
partial update received from the server.
Replaced by SafeBrowsing.V4ProcessPartialUpdate.ApplyUpdate.Time.
vakh@chromium.org
Records the time it takes to process a SafeBrowsing list partial update. It
includes V4AddUnlumpedHashesTime for each prefix-sized list, and
V4MergeUpdateTime. Additionally, if the update is Rice-encoded, it includes
V4DecodeRemovalsTime, and V4DecodeAdditionsTime for each prefix-sized list
that's Rice-encoded.
vakh@chromium.org
Track the result of applying an ListUpdateResponse read from disk after
parsing it successfully as a protobuf.
vakh@chromium.org
Records the time it takes to read, parse, and process a SafeBrowsing list
stored on disk. This happens at Chromium start-up. It includes
V4AddUnlumpedHashes.Time for each prefix-sized list, and
SafeBrowsing.V4ReadFromDisk.MergeUpdate.Time. Additionally, if the file is
Rice-encoded, it includes V4ReadFromDisk.DecodeAdditions.Time for each
prefix-sized list that's Rice-encoded.
vakh@chromium.org
Track the result of decoding the Rice-encoded list of additions of 4-byte
hash prefixes. This is logged once per store, per Chrome launch. It is
specific to processing V4StoreFileFormat proto read from disk.
vakh@chromium.org
Records the time it takes to decode the Rice-encoded additions to the
blacklist into raw format when reading a store file from disk.
Deprecated 04/25/2018 since it was not being used actively or monitored.
vakh@chromium.org
Records the time it takes to perform in-memory copy of the map of raw hash
prefixes read from disk.
Replaced by SafeBrowsing.V4ReadFromDisk.ApplyUpdate.Time.
vakh@chromium.org
Records the time it takes to read, parse, and process a SafeBrowsing list
stored on disk. This happens at Chromium start-up. It includes
V4AddUnlumpedHashesTime for each prefix-sized list, and V4MergeUpdateTime.
Additionally, if the file is Rice-encoded, it includes V4DecodeAdditionsTime
for each prefix-sized list that's Rice-encoded.
vakh@chromium.org
Track the parsing results of reading the SafeBrowsing V4 store file from
disk. Recorded every time a store is read from disk.
Replaced by SafeBrowsing.V4StoreRead.Result.
vakh@chromium.org
Track the parsing results of reading the SafeBrowsing V4 store file from
disk. Recorded every time a store is read from disk.
vakh@chromium.org
Version of V4Store read from a store file. This would be useful in tracking
the usage and rollout of new V4Store versions.
vakh@chromium.org
Track the results of writing the SafeBrowsing V4 store file to disk.
Recorded every time a store is written to disk.
Replaced by SafeBrowsing.V4StoreWrite.Result.
vakh@chromium.org
Track the results of writing the SafeBrowsing V4 store file to disk.
Recorded every time a store is written to disk.
vakh@chromium.org
Track the presence of store files that were previously created but have been
deprecated since so need to be removed from disk. Logged once per startup.
vakh@chromium.org
Track the presence of Safe Browsing list files used for PVer3, which has
been deprecated. Logged once per startup.
vakh@chromium.org
Response or error codes when fetching updates from the SafeBrowsing PVer4
service.
vakh@chromium.org
Track the parsing results of a status 200 GetV4Update request.
vakh@chromium.org
The size of the response sent by the SafeBrowsing PVer4 service, in KB.
vakh@chromium.org
Track return status from V4 update attempts. The buckets of this histogram
overlap, so the counts cannot be used as percentages.
vakh@chromium.org
True if a PVer4 update request timed out.
Replaced by SafeBrowsing.V4Update.Network.Result.
vakh@chromium.org
Response or error codes when fetching updates from the SafeBrowsing PVer4
service.
Replaced by SafeBrowsing.V4Update.ResponseSizeKB.
vakh@chromium.org
The size of the response sent by the SafeBrowsing PVer4 service, in KB.
Replaced by SafeBrowsing.V4Update.Result.
vakh@chromium.org
Track return status from V4 update attempts. The buckets of this histogram
overlap, so the counts cannot be used as percentages.
ricea@chromium.org
Time spent on SafeBrowsing lookup. Since this includes any time spent on the
interstitial page the average may not be useful.
ricea@chromium.org
Results of a SafeBrowsing lookup for a WebSocket handshake. All lookups are
counted. Note: the "ABANDONED" bucket contains both connections
that were abandoned before the check completed and those that were cancelled
when the user navigated away from the SafeBrowsing interstitial.
ntfschr@chromium.org
Records whether the application has explicitly opted in or out of Safe
Browsing by manifest tag, or if they're relying on the default behavior.
This is recorded once during startup.
ntfschr@chromium.org
WebView can simultaneously check for user opt-in and Safe-Browsing-check the
first URL, with both asynchronous checks racing to finish. This records the
outcome of that race: (1) which asynchronous method finished first; (2) if
user consent finished first, what was the outcome; and (3) did we show
malicious content to the user. This is recorded only once, for the first
Safe Browsing check.
ntfschr@chromium.org
Records whether the user has explicitly opted in or out of Safe Browsing
(determined by the Google Play Protect Verify Apps setting in GMS). This
also captures when WebView cannot determine user preference due to a GMS API
failure. This is recorded once during startup.
ntfschr@chromium.org
When encountering an unsafe resource, this indicates whether the WebView is
considered to be viewable or not. Currently, we define "viewable"
as getVisibility() == View.VISIBLE and attached to the Android View
hierarchy.
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.
vakh@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.
vakh@chromium.org
The size of the browsing SafeBrowsing database file on disk in kilobytes,
after an update has occurred.
vakh@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.
vakh@chromium.org
The number of kilobytes read by the browser process during the filter
generation phase.
vakh@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.
vakh@chromium.org
The number of kilobytes written by the browser process during the filter
generation phase.
vakh@chromium.org
The number of write operations issued by the browser process during the
filter generation phase.
vakh@chromium.org
The time that it takes to write one redirect URL (which can contain multiple
chunks) to the database.
vakh@chromium.org
The network time between the request and response for a chunk.
vakh@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.
vakh@chromium.org
Track failures when updating the safe-browsing database.
Replaced by SB2.BrowseDatabaseKilobytes.
vakh@chromium.org
The size of the SafeBrowsing database file on disk in kilobytes.
vakh@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).
vakh@chromium.org
The size of the update file before merging with the database file, in
kilobytes.
vakh@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. This is the sum of .Mainframe and .Subresource
breakout metrics.
vakh@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. Logged for main frame resources only.
vakh@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. Logged for non-main frame resources only.
Deleted in M-34 (February 2014).
Please list the metric's owners. Add more owner tags as needed.
Obsolete download BINHASH add chunks deleted.
Deleted in M-34 (February 2014).
Please list the metric's owners. Add more owner tags as needed.
Obsolete download BINHASH sub chunks deleted.
vakh@chromium.org
Records results of SafeBrowsing download check, including both url check and
downloaded file hash check.
Deprecated 12/2014. Moved to SB2.DatabaseSizeKilobytes.Download.
vakh@chromium.org
The size of the downloads SafeBrowsing database file on disk in kilobytes,
after an update has occurred.
Deprecated 01/2017. Was measuring the lifetime of a network request
corresponding to a download, which may or may not correspond to the total
duration of a download.
vakh@chromium.org
The time it takes for a download to finish.
vakh@chromium.org
The time it takes for SafeBrowsing to check hash of a download file.
vakh@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.
Deprecated in favor of SafeBrowsing.V4GetPrefixMatches.TimeUs
vakh@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.
vakh@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.
vakh@chromium.org
Collection of boolean events for SafeBrowsingFileStore instances. Includes
corruptions detected, old versions detected, and various failures detected.
vakh@google.com
Response or error codes from the SafeBrowsing service. Logged after a
GetChunk request finishes to capture the response code or error code for
that call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49.
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).
vakh@google.com
Response or error codes from the SafeBrowsing service. Logged after a
GetHash request finishes to capture the response code or error code for that
call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49.
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.
vakh@chromium.org
The time that it took to receive a response from the Google SafeBrowsing
servers for a GetHash request.
yzshen@chromium.org
The total delay, in milliseconds, caused by SafeBrowsing for a resource
load, if the SafeBrowsing interstitial page is not shown and therefore no
user action is involved. At most one value is reported for each resource
load. If SafeBrowsing causes delays at different stages of a load, the sum
of all the delays will be reported.
Deprecated 7/2014. No longer generated.
vakh@chromium.org
Size of v1 database deleted from client profile.
vakh@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.
vakh@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.
vakh@chromium.org
The size of one of the PrefixSet files in kilobytes.
vakh@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.
vakh@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.
vakh@chromium.org
Version read from one of the PrefixSet files.
vakh@chromium.org
Time to store one of the PrefixSet files.
nparker@chromium.org
Count of how many URLs were actually checked vs skipped via
RemoteSafeBrowsingDatabaseManager because the scheme is not supported by
Safe Browsing. Incremented each time a resource load is initiated.
csharrison@chromium.org
vakh@chromium.org
The microseconds between sending the Safe Browsing API call and receiving
the response. Logged in java code and does not include any thread hops or
extra work. Note that this does include task queue time to respond to the
IPC (and that queue time is often non-trivial).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
csharrison@chromium.org
vakh@chromium.org
Wall time in microseconds for calling
Java_SafeBrowsingApiBridge_startUriLookup. Logged at every Safe Browsing
check on Android.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in M64 (Nov 2017). No longer generated.
nparker@chromium.org
Number of outstanding calls for URLs getting classified through
RemoteSafeBrowsingDatabaseManager. The size of the queue is logged before
initiating each request.
nparker@chromium.org
Latency of URL-classification API calls from Chrome via
RemoteSafeBrowsingDatabaseManager, logged per-request. This includes the
time to go through JNI, check the URL, and return the result and includes
several thread hops betwetween IO and UI threads. The resource-load will not
necessarily be delayed this much (see SB2.Delay for that).
No longer generated. Replaced by SB2.RemoteCall.InternalErrorStatusCode2
vakh@chromium.org
The status code provided by GmsCore if it is unable to respond to a URL
check request due to incorrect initialization, not being ready, etc. Logged
on each URL check that hits the internal error condition. The total number
of these should add up to the INTERNAL_ERROR reports under
SB2.RemoteCall.Result.
vakh@chromium.org
The status code provided by GmsCore if it is unable to respond to a URL
check request due to incorrect initialization, not being ready, etc. Logged
on each URL check that hits the internal error condition. The total number
of these should add up to the INTERNAL_ERROR reports under
SB2.RemoteCall.Result.
nparker@chromium.org
Result of URL-classification API calls from Chrome via
RemoteSafeBrowsingApiHandler. Logged after each URL is judged
safe/not-safe, or hits a deadline. The INTERNAL_ERROR cases are further
classified under SB2.RemoteCall.InternalErrorStatusCode.
nparker@chromium.org
The threat sub-type annotated for URLs classified as PHA via remote calls
through RemoteSafeBrowsingApiHandler. "PHA" classifications
generate "malware" interstitials.
nparker@chromium.org
The threat sub-type annotated returned for URLs classified as social
engineering via remote calls through RemoteSafeBrowsingApiHandler.
"Social engineering" classifications generate "phishing"
interstitials.
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.
Superseded by SB2.ResourceTypes2 in December 2015.
nparker@chromium.org
Resource types of resources that were inspected by Safe Browsing in the
SafeBrowsingResourceThrottle.
nparker@chromium.org
Resource types of resources that were inspected by Safe Browsing in the
SafeBrowsingResourceThrottle.
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.
vakh@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.
vakh@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.
vakh@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.
vakh@chromium.org
Time to load the Side Effect Free Whitelist PrefixSet file.
Deprecated 4/2015.
vakh@chromium.org
The instantiation status of the SideEffectFreeWhitelist.
vakh@chromium.org
Version read from the store file.
vakh@chromium.org
The number of sub prefixes stored in the database after the last update.
vakh@chromium.org
The time from the receipt of the update request to the receipt of the final
update chunk.
vakh@chromium.org
The payload size of update requests to the server.
vakh@chromium.org
Result from trying to update the SafeBrowsing data.
vakh@chromium.org
The size of all the chunk URLs in an update response.
Was used for an experiment in late 2014.
nparker@chromium.org
The size of all the chunk URLs in an update response when Chrome is in the
background.
Was used for an experiment in late 2014.
nparker@chromium.org
The size of all the chunk URLs in an update response when Chrome is in the
foreground.
vakh@chromium.org
The number of chunk URLs in an update response.
The operation this is tracking has been deleted as of 09/2014.
vakh@chromium.org
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 .
asanka@chromium.org
Records a histogram of archive file types that were found while examining a
downloaded ZIP file. Each archive file type in a single ZIP file is recorded
at most once. The relative incidence rate of each filetype in this histogram
should indicate the probability of finding that file type in a ZIP file
given that that ZIP file contains an archive file.
mattm@chromium.org
Records a histogram of the reason why downloads are marked as being
malicious or clean by the improved SafeBrowsing binary download protection.
Note that UNSUPPORTED_URL_SCHEME was split out of the INVALID_URL bucket in
M41. The NOT_BINARY_FILE check was moved before the UNSUPPORTED_URL_SCHEME
check in M42. The WHITELISTED_URL check was moved to before NOT_BINARY_FILE
in M62.
jialiul@chromium.org
For each download supported by the SafeBrowsing download protection service,
records if it matches a certain whitelist (e.g. matches URL whitelist,
matches signature whitelist, or does not match any whitelists).
nparker@chromium.org
The original number of archived_binaries found in a DMG-like file when it's
scanned, if at least one is found. The actual number sent in the download
request may be capped below this value.
nparker@chromium.org
Counts of DMG-like file types that failed to be successfully analyzed by the
SafeBrowsing download service.
Replaced by SBClientDownload.DmgFileHas[No]ExecutableByType in M51.
rsesek@chromium.org
For each DMG file analyzed by the SafeBrowsing download service, records if
the DMG contained an executable file.
nparker@chromium.org
Counts of DMG-like file types which were analyzed by the SafeBrowsing
download service that contained an executable file.
nparker@chromium.org
Counts of DMG-like file types which were analyzed by the SafeBrowsing
download service that did NOT contain an executable file.
Replaced by SBClientDownload.DmgFile{Success,Failure}ByType in M51.
rsesek@chromium.org
For each DMG file analyzed by the SafeBrowsing download service, records
true if the analysis was successful, or false if there was an error
analyzing the file.
nparker@chromium.org
Counts of DMG-like file types that were successfully analyzed by the
SafeBrowsing download service.
jialiul@chromium.org
Records whether a given DMG download was too big to unpack, as specified by
configuration option set in SafeBrowsing download service. This metric is
logged each time the user downloads a DMG file on Mac.
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).
jialiul@chromium.org
A Mac-only metric that records whether a given download contains a detached
code signature file. This metric is logged before Chrome sends SafeBrowsing
download pings.
jialiul@chromium.org
A Mac-only metric that records whether a given download file is a
cryptographically signed DMG archive. This metric is logged before Chrome
sends SafeBrowsing download pings.
jialiul@chromium.org
Records whether download files without an Apple disk image file extension
have a 'koly' signature. This can be used to identify distribution of disk
image files to Mac users without simply relying on file extension. This
metric is logged before Chrome sends SafeBrowsing download pings.
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).
rsesek@chromium.org
Records the time it takes for the SafeBrowsing download service to extract
info from a downloaded DMG file.
grt@chromium.org
Records the time it takes for the SafeBrowsing download service to extract
image headers from a downloaded binary.
vakh@chromium.org
Records the time it takes for the SafeBrowsing download service to extract
info from a downloaded rar file.
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.
asanka@chromium.org
Time taken to complete a PPAPIDownloadRequest.
asanka@chromium.org
Outcome of running CheckPPAPIDownloadRequest. Most failure modes cause an
UNKNOWN result to be returned to the caller. If the attempt succeeds, the
result returned to the caller is based on the SafeBrowsing resopnse. The
final result returned is counted in
SBClientDownload.PPAPIDownloadRequest.Result.
asanka@chromium.org
Result returned to the caller of CheckPPAPIDownloadRequest.
vakh@chromium.org
The original number of archived_binaries found in a rar-like file when it's
scanned, if at least one is found. The actual number sent in the download
request may be capped below this value.
vakh@chromium.org
For each rar file analyzed by the SafeBrowsing download service, records
true if the rar did not contain any executables but did contain another
archive file, false otherwise.
vakh@chromium.org
For each rar file analyzed by the SafeBrowsing download service, records if
the rar contained an executable file.
vakh@chromium.org
For each rar file analyzed by the SafeBrowsing download service, records if
the unpacking was 100% successful.
vakh@chromium.org
For each rar file analyzed by the SafeBrowsing download service, records if
the file could be opened. This should be close to 100% success because the
library doesn't actually open the file; it is handed an open file handle and
the Open() function call sets that as the file handle to use.
vakh@chromium.org
For each rar file analyzed by the SafeBrowsing download service, records if
the unrar library considers this file a valid RAR archive. It includes
checking the following, and more: magic number is present, valid RAR version
format can be parsed, headers are valid, etc.
mattm@chromium.org
Records the number of signed vs. unsigned executables that are downloaded.
Deprecated in Chrome 50. Replaced by
SBClientDownload.CheckWhitelistResult.*.
mattm@chromium.org
Counter which is incremented whenever an executable is downloaded which is
either signed or whose URL matches the download whitelist.
jialiul@chromium.org
Records how often different file extensions are downloaded with schemes that
aren't supported by Safe Browsing (e.g. ftp, gopher, content, cid, etc).
nparker@chromium.org
The original number of archived_binaries found in a zip-like file when it's
scanned, if at least one is found. The actual number sent in the download
request may be capped below this value.
jialiul@chromium.org
A Mac-only metric that records whether a downloaded zip file contains an
.app directory, signifying the presence of installable software.
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.
nparker@chromium.org
For each zip file analyzed by the SafeBrowsing download service, records if
the unpacking was 100% successful.
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.
jialiul@chromium.org
True if at least one resource url matched the malware IP list. Recorded when
client side malware feature extraction is done.
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.
jialiul@chromium.org
The counts for malware verdicts given by server side model.
Deprecated 03/2014. That part of the code got deleted.
noelutz@chromium.org
Counts the number of times the page ID that completed the page load does not
match the browse info page ID. We expect that number to be zero.
nparker@chromium.org
The counts for various reasons why an in-progress phishing classification
was canceled.
Removed in M47.
noelutz@chromium.org
The number of times client-side phishing classifier expected to have no
pending classifications running but that check failed.
noelutz@chromium.org
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.
jialiul@chromium.org
The counts for phishing verdicts given by client side model.
vakh@google.com
Response or error codes from the SafeBrowsing service. Logged after a
request for the client side model finishes to capture the response code or
the error code for that HTTP request.
nparker@chromium.org
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.
Removed in M47
noelutz@chromium.org
Time spent generating the thumbnail.
nparker@chromium.org
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.
noelutz@chromium.org
The number of phishing classifications that were previously cached as being
phishing but that will get re-classified (to possibly fix false positives).
noelutz@chromium.org
The number of phishing classifier pingbacks that were skipped because
serializing the request protocol buffer to string failed.
noelutz@chromium.org
The number of times that a cached phishing classification result was used,
rather than pinging the server.
noelutz@chromium.org
Records the status when we create a scorer object for the client-side
phishing detection classifier.
jialiul@chromium.org
The counts for phishing verdicts given by server side model.
jialiul@chromium.org
The counts for various reasons why a phishing classification is skipped.
noelutz@chromium.org
The number of phishing classifications that were aborted because the term
feature extractor failed to initialize an ICU break iterator.
noelutz@chromium.org
The time that an individual chunk of term feature extraction work took.
noelutz@chromium.org
The number of iterations that the term feature extractor took to finish.
noelutz@chromium.org
The number of phishing classification that were aborted because term feature
extraction took too long.
noelutz@chromium.org
The time that the term feature extarctor took to finish, summed across all
chunks of work.
noelutz@chromium.org
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.
noelutz@chromium.org
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.
jialiul@chromium.org
Count of times download feedback cannot be sent due to empty file path.
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.
nparker@chromium.org
For each non-SAFE file, records whether the server requested that that file
be uploaded.
Logged before checking the file size, so it may be dropped there.
mattm@chromium.org
Final result of attempt to upload binary to download feedback service.
Blacklist Load analysis was removed in M63.
caitkp@google.com
The elapsed time to compute the hash of a blacklisted module.
Blacklist Load analysis was removed in M63.
caitkp@google.com
The elapsed time to validate the signature of a blacklisted module.
caitkp@google.com
The type of incident discarded by the safe browsing incident reporting
service as a result of profile or service destruction.
caitkp@chromium.org
The result of deleting a profile's download metadata file.
caitkp@chromium.org
The result of reading a profile's download metadata file.
caitkp@chromium.org
The result of writing a profile's download metadata file.
caitkp@google.com
The type of incident given to the safe browsing incident reporting service
but dropped as a result of not participating in safe browsing.
caitkp@google.com
The elapsed time to collect environmental data for a safe browsing incident
report.
caitkp@google.com
The elapsed time to find the most recent binary download from all loaded
profiles when creating a safe browsing incident report.
caitkp@google.com
The type of incident included in an incident report by the safe browsing
incident reporting service.
caitkp@google.com
The number of incidents collated into a single safe browsing incident
report.
caitkp@google.com
The elapsed time between two successive incidents collated into the same
incident report by the safe browsing incident reporting service.
proberge@google.com
The type of incident pruned by the safe browsing incident reporting service
as a result of not having a matching binary download.
proberge@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.
Deprecated 08/2015.
caitkp@google.com
The percentage of incidents pruned from a safe browsing incident report on
account of having been previously reported.
grt@google.com
The size, in bytes, of a profile's platform state store. This hisogram is
logged on each write, which always replaces any previous contents.
grt@google.com
The result of loading data from the platform state store.
caitkp@google.com
The type of incident received by the safe browsing incident reporting
service.
proberge@google.com
The size, in bytes, of a safe browsing incident report.
caitkp@google.com
The elapsed time to upload a safe browsing incident report.
proberge@google.com
The result of initializing the state store and comparing the preferences to
the platform-specific state store.
Suspicious Module detection was removed in M63.
proberge@google.com
The elapsed time to check loaded modules against the module whitelist.
Suspicious Module detection reporting removed in M63.
proberge@google.com
The number of suspicious modules found.
Suspicious Module detection reporting removed in M63.
proberge@google.com
The elapsed time to create incidents for suspicious modules.
caitkp@google.com
The result of an attempted report upload by the safe browsing incident
reporting service.
caitkp@google.com
The elapsed time to verify the binary integrity of chrome.exe.
caitkp@google.com
The elapsed time to verify the binary integrity of chrome.dll.
caitkp@google.com
The elapsed time to verify the binary integrity of chrome_child.dll.
caitkp@google.com
The elapsed time to verify the binary integrity of chrome_elf.dll.
Superseded by SBOffDomainInclusion2.Abort in December 2015.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis was aborted. This histogram is suffixed with the abort
reason.
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.
Superseded by SBOffDomainInclusion2.InHistory in December 2015.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis concluded in no inclusion whitelist hit but a browsing
history hit.
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.
Superseded by SBOffDomainInclusion2.RequestAnalyzed in December 2015.
gab@chromium.org
Logs the resource type of each resource request analyzed by the
OffDomainInclusionDetector.
Superseded by SBOffDomainInclusion2.Suspicious in December 2015.
gab@chromium.org
Logs the resource type of each resource request for which an off-domain
inclusion was detected by the OffDomainInclusionDetector and considered
suspicious.
Superseded by SBOffDomainInclusion2.Suspicious in December 2015.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis concluded in an inclusion whitelist hit.
Deprecated 2016-05 as the OffDomainInclusionDetector was removed.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis was aborted. This histogram is suffixed with the abort
reason.
Deprecated 2016-05 as the OffDomainInclusionDetector was removed.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis concluded in no inclusion whitelist hit but a browsing
history hit.
Deprecated 2016-05 as the OffDomainInclusionDetector was removed.
gab@chromium.org
Logs the resource type of each resource request analyzed by the
OffDomainInclusionDetector.
Deprecated 2016-05 as the OffDomainInclusionDetector was removed.
gab@chromium.org
Logs the resource type of each resource request for which an off-domain
inclusion was detected by the OffDomainInclusionDetector and considered
suspicious.
Deprecated 2016-05 as the OffDomainInclusionDetector was removed.
gab@chromium.org
Logs the resource type of each resource request for which the off-domain
inclusion analysis concluded in an inclusion whitelist hit.
altimin@chromium.org
Total cpu time of scheduler-managed threads in the renderer process.
It is supposed that Scheduler.Experimental.Renderer.CPUTimePerThread.Tracked
and Scheduler.Experimental.Renderer.CPUTimePerThread.Untracked histograms
should be analysed together.
The bucket value is the sum of thread durations of all tasks in this thread
across all browsing instances. This metric is reported each time we execute
a task. Due to thread time being expensive to measure, only 0.01% of threads
report this metric.
altimin@chromium.org
Sum of durations of all scheduler-managed tasks in the renderer process.
Due to implementation constraints a difference between .Positive and
.Negative subhistograms should be analysed. See
blink::scheduler::TotalDurationMetricReporter for details.
These metrics are updated each time a new task is executed.
Replaced by ActivateDuration2, due to inefficient bucketing scheme.
brianderson@chromium.org
How long it takes for the compositor to simply activate the pending tree.
Does not include any PrepareTiles or raster time.
brianderson@chromium.org
How long it takes for the compositor to simply activate the pending tree.
Does not include any PrepareTiles or raster time.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
stanisc@chromium.org
The time from v-sync to when the main side actually starts the
BeginImplFrame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by BeginMainFrameIntervalCritical2, due to inefficient bucketing
scheme.
brianderson@chromium.org
This is the time delta between back-to-back BeginMainFrames completions on
the compositor side when the on_critical_path flag is set, regardless of
whether they abort (have no updates) or commit (have updates).
The interval is only recorded when the BeginMainFrames are running
continuously; sepcifically when another BeginMainFrame is requested by the
next BeginImplFrame after a) an abort or b) activation.
Replaced by BeginMainFrameIntervalNotCritical2, due to inefficient bucketing
scheme.
brianderson@chromium.org
This is the time delta between back-to-back BeginMainFrames completions on
the compositor side when the on_critical_path flag is not set, regardless of
whether they abort (have no updates) or commit (have updates).
The interval is only recorded when the BeginMainFrames are running
continuously; sepcifically when another BeginMainFrame is requested by the
next BeginImplFrame after a) an abort or b) activation.
Replaced by BeginMainFrameQueueDurationCritical2, due to inefficient
bucketing scheme.
brianderson@chromium.org
How long it takes for the main side to start the BeginMainFrame in response
to the compositor's SendBeginMainFrame when the on_critical_path flag is
set.
brianderson@chromium.org
How long it takes for the main side to start the BeginMainFrame in response
to the compositor's SendBeginMainFrame when the on_critical_path flag is
set.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by BeginMainFrameQueueDurationNotCritical2, due to inefficient
bucketing scheme.
brianderson@chromium.org
How long it takes for the main side to start the BeginMainFrame in response
to the compositor's SendBeginMainFrame when the on_critical_path flag is not
set.
Replaced by BeginMainFrameStartToCommitDuration2, due to inefficient
bucketing scheme.
brianderson@chromium.org
The time from when the main side actually starts the BeginMainFrame to when
the commit completes on the impl side.
brianderson@chromium.org
The time from when the main side actually starts the BeginMainFrame to when
the commit completes on the impl side.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by BeginMainFrameQueueDurationCritical,
BeginMainFrameQueueDurationNotCritical, and
BeginMainFrameStartToCommitDuration.
brianderson@chromium.org
How long it takes for the blink main thread to respond to the compositor's
SendBeginMainFrame.
Deprecated in 06/2018, M69, due to too much noise in the collected data.
brianderson@chromium.org
This is the time delta between back-to-back BeginMainFrames completions on
the compositor side when the on_critical_path flag is set, regardless of
whether they abort (have no updates) or commit (have updates).
The interval is only recorded when the BeginMainFrames are running
continuously; sepcifically when another BeginMainFrame is requested by the
next BeginImplFrame after a) an abort or b) activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for
the solution.
Deprecated in 07/2018, M69. All begin frames are in critical path for
browser, no data is reported.
brianderson@chromium.org
This is the time delta between back-to-back BeginMainFrames completions on
the compositor side when the on_critical_path flag is not set, regardless of
whether they abort (have no updates) or commit (have updates).
The interval is only recorded when the BeginMainFrames are running
continuously; sepcifically when another BeginMainFrame is requested by the
next BeginImplFrame after a) an abort or b) activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in 07/2018, M69. All begin frames are in critical path for
browser, no data is reported.
brianderson@chromium.org
How long it takes for the main side to start the BeginMainFrame in response
to the compositor's SendBeginMainFrame when the on_critical_path flag is not
set.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by BeginMainFrameStartToCommitDuration. This was recorded as a
result of a typo in the code that didn't include "Duration".
brianderson@chromium.org
The time from when the main side actually starts the BeginMainFrame to when
the commit completes on the impl side.
Replaced by BeginMainFrameStartToCommitDuration2. This was recorded as a
result of a typo in the code that didn't include "Duration".
brianderson@chromium.org
The time from when the main side actually starts the BeginMainFrame to when
the commit completes on the impl side.
Deprecated in 06/2018, M69, due to too much noise in the collected data.
brianderson@chromium.org
The time delta between the *draw* times of back-to-back BeginMainFrames that
result in a commit.
The interval is only recorded when the BeginMainFrames are running and
committing continuously, where continuously means when another
BeginMainFrame is requested by the next BeginImplFrame after activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for
the solution.
Deprecated in 06/2018, M69, due to too much noise in the collected data.
brianderson@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames,
regardless of whether or not they result in a swap.
The interval is only recorded when every BeginImplFrame wants to draw.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for
the solution.
Deprecated in 07/2018, M69, due to too much noise in the data.
paint-dev@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames,
regardless of whether or not they result in a swap, when there is at least
one composited animation.
The interval is only recorded when every BeginImplFrame wants to draw.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in 07/2018, M69, due to too much noise in the data.
paint-dev@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames of new
active trees only, regardless of whether or not they result in a swap, when
there is at least one main thread animation.
The interval is only recorded when every BeginImplFrame wants to draw.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in 07/2018, M69. Since there is no pending tree in Browser, no
data is ever reported.
ericrk@chromium.org
Time between creating a pending tree and activating that tree. This differs
from Scheduling.ActivateDuration in that it includes time taken to raster
the pending tree, not just the time to activate it.
The interval is recorded each time a pending tree is activated.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in 07/2018, M69. Since there is no pending tree in Browser, no
data is ever reported.
khushalsagar@chromium.org
Time between starting raster work on the pending tree and when it is ready
to activate. Unlike PendingTreeDuration which - includes the time to commit
to this tree, the raster duration and the time for which the pending tree
waits before it can be activated - this only measures the time taken to
rasterize tiles required for activation.
The interval is recorded each time we are notifed that a pending tree is
ready for activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in 07/2018, M69. No data reported because there is no pending
tree on impl thread for browser side.
brianderson@chromium.org
How long does the pending tree wait after it is ready to be activated and
before it is activated.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution. Impl side invalidation initiated pending tree
brianderson@chromium.org
How long does the pending tree wait after it is ready to be activated and
before it is activated.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution. Commit initiated pending tree.
Replaced by CommitInterval2, due to inefficient bucketing scheme.
brianderson@chromium.org
The time delta between the *draw* times of back-to-back BeginMainFrames that
result in a commit.
The interval is only recorded when the BeginMainFrames are running and
committing continuously, where continuously means when another
BeginMainFrame is requested by the next BeginImplFrame after activation.
Replaced by CommitToReadyToActivateDuration2, due to inefficient bucketing
scheme.
brianderson@chromium.org
How long it takes for the compositor to rasterize pending tree content after
a commit before it is ready for activation.
brianderson@chromium.org
How long it takes for the compositor to rasterize pending tree content after
a commit before it is ready for activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by DrawDuration2, due to inefficient bucketing scheme.
brianderson@chromium.org
How long it takes the compositor to draw a frame.
brianderson@chromium.org
How long it takes the compositor to draw a frame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by DrawInterval2, due to inefficient bucketing scheme.
brianderson@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames,
regardless of whether or not they result in a swap.
The interval is only recorded when every BeginImplFrame wants to draw.
Deprecated 05/2018 because the experiment described in Issue 754471 is
completed.
paint-dev@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames of new
active trees only, regardless of whether or not they result in a swap, when
there is at least one main thread animation that could be composited but
not, due to running experiment.
The interval is only recorded when every BeginImplFrame wants to draw.
Deprecated 03/28/2018
khushalsagar@chromium.org
Duration for updating animated images and invalidating layers for images
invalidated on the sync tree in the compositor. This interval is recorded
each time the sync tree is updated after a commit or an impl-side
invalidation.
brianderson@chromium.org
How long it takes for the compositor to rasterize pending tree content after
an impl-side invalidation before it is ready for activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by MainAndImplFrameTimeDelta2, due to inefficient bucketing scheme.
brianderson@chromium.org
Recorded every time the compositor draws with a new active tree. A value of
0 indicates the main-side started and finished within the same frame
interval as the impl-side. Positive values correspond to how old any
main-side updates are compared to the impl-side updates. If there are no
mid-frame updates, this metric is a good proxy for how well the main and
impl threads are synchronized.
brianderson@chromium.org
Recorded every time the compositor draws with a new active tree. A value of
0 indicates the main-side started and finished within the same frame
interval as the impl-side. Positive values correspond to how old any
main-side updates are compared to the impl-side updates. If there are no
mid-frame updates, this metric is a good proxy for how well the main and
impl threads are synchronized.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by PrepareTIlesDuration2, due to inefficient bucketing scheme.
brianderson@chromium.org
How long it takes the compositor to PreapreTiles, which determines what
rasterization work to do.
brianderson@chromium.org
How long it takes the compositor to PreapreTiles, which determines what
rasterization work to do.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Replaced by ReadyToActivateToActivationDuration2, due to inefficient
bucketing scheme.
brianderson@chromium.org
How long does the pending tree wait after it is ready to be activated and
before it is activated.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
brianderson@chromium.org
This is the time delta between back-to-back BeginMainFrames completions on
the compositor side when the on_critical_path flag is set, regardless of
whether they abort (have no updates) or commit (have updates).
The interval is only recorded when the BeginMainFrames are running
continuously; sepcifically when another BeginMainFrame is requested by the
next BeginImplFrame after a) an abort or b) activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for
the solution.
brianderson@chromium.org
This is the time delta between back-to-back BeginMainFrames completions on
the compositor side when the on_critical_path flag is not set, regardless of
whether they abort (have no updates) or commit (have updates).
The interval is only recorded when the BeginMainFrames are running
continuously; sepcifically when another BeginMainFrame is requested by the
next BeginImplFrame after a) an abort or b) activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
brianderson@chromium.org
How long it takes for the main side to start the BeginMainFrame in response
to the compositor's SendBeginMainFrame when the on_critical_path flag is not
set.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
brianderson@chromium.org
The time delta between the *draw* times of back-to-back BeginMainFrames that
result in a commit.
The interval is only recorded when the BeginMainFrames are running and
committing continuously, where continuously means when another
BeginMainFrame is requested by the next BeginImplFrame after activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for
the solution.
brianderson@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames,
regardless of whether or not they result in a swap.
The interval is only recorded when every BeginImplFrame wants to draw.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_HIGH_RESOLUTION_TIMES for
the solution.
paint-dev@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames,
regardless of whether or not they result in a swap, when there is at least
one composited animation.
The interval is only recorded when every BeginImplFrame wants to draw.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
paint-dev@chromium.org
The time delta between the draw times of back-to-back BeginImplFrames of new
active trees only, regardless of whether or not they result in a swap, when
there is at least one main thread animation.
The interval is only recorded when every BeginImplFrame wants to draw.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ericrk@chromium.org
Time between creating a pending tree and activating that tree. This differs
from Scheduling.ActivateDuration in that it includes time taken to raster
the pending tree, not just the time to activate it.
The interval is recorded each time a pending tree is activated.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
khushalsagar@chromium.org
Time between starting raster work on the pending tree and when it is ready
to activate. Unlike PendingTreeDuration which - includes the time to commit
to this tree, the raster duration and the time for which the pending tree
waits before it can be activated - this only measures the time taken to
rasterize tiles required for activation.
The interval is recorded each time we are notifed that a pending tree is
ready for activation.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
brianderson@chromium.org
How long does the pending tree wait after it is ready to be activated and
before it is activated.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated in 07/2018, M69. The swap ack is always received within 8
seconds.
brianderson@chromium.org
True if the swap ack was received within approximately 8 seconds of the
swap. Although 8 seconds isn't exactly fast, it is a threshold that
represents a hang or the appearance of a hang.
Replaced by SwapToAckLatency2, due to inefficient bucketing scheme.
brianderson@chromium.org
How long it takes the swap ack to return after a swap.
brianderson@chromium.org
How long it takes the swap ack to return after a swap.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
sammiequon@chromium.org
What type of authentication was attempted when the user failed to unlock the
lock screen.
sammiequon@chromium.org
The time spent for authentication in case of a failure.
sammiequon@chromium.org
What type of authentication was attempted when the user successfully
unlocked the lock screen.
sammiequon@chromium.org
The time spent for authentication in case of a success.
sammiequon@chromium.org
The time spent before the screen locker is ready.
Experiment complete, histogram gathering code removed.
ellyjones@chromium.org
Whether an SDCH dictionary was advertised over a secure scheme or not. This
histogram is logged inside SdchManager at advertisement time.
Deprecated 2017-9.
The number of dictionaries advertised in an HTTP GET transaction that
supports SDCH. Note that only non-zero advertisements are logged.
Deprecated 2017-9.
The reason why a blacklist blocking a request from advertising SDCH was
implemented. There is one entry in this histogram per inhibited request.
Deprecated 2017-9.
Each sample is the byte count for a dictionary that is loaded by Chrome. A
dictionary is loaded shortly after the first Google query performed in each
session, and allows future SDCH transactions to be encoded/decoded using
that dictionary.
Deprecated 2017-9.
The fate, both on input and output, of dictionary requests. There is
intended to be two entries in this histogram for each Get-Dictionary seen
(except failed requests are not currently tracked).
Deprecated 2017-9.
The number of times a dictionary has been successfully used for decoding,
recorded at the time it is evicted from the manager.
Replaced by Sdch3.Experiment3_Holdback.
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of an SDCH encoded transmission made after the link had proven it
was capable of handling SDCH compression.
Replaced by Sdch3.Experiment3_Holdback.
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of a holdback, which precluded SDCH despite the fact that the link
had proven it was capable of handling SDCH compression.
Deprecated 2017-9.
Duration in time from the first byte of a request was received, until all
bytes were received. During the running of an SDCH latency experiment,
these packets were part of an SDCH encoded transmission made after the link
had proven it was capable of handling SDCH compression.
Deprecated 2017-9.
Duration in time from the first byte of a request was received, until all
bytes were received. During the running of an SDCH latency experiment,
these packets were part of a holdback, which precluded SDCH despite the fact
that the link had proven it was capable of handling SDCH compression.
Replaced by Sdch3.Experiment2_Decode.
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of an SDCH encoded transmission made after the link had proven it
was capable of handling SDCH compression.
Replaced by Sdch3.Experiment2_Holdback.
Duration in time from when a request was made, until all bytes were
received. During the running of an SDCH latency experiment, these packets
were part of a holdback, which precluded SDCH despite the fact that the link
had proven it was capable of handling SDCH compression.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
Deprecated 2016-11.
The duration between receipt of the 1st holdback (non-SDCH encoded) packet
and receipt of the last packet. Only groups that are part of the holdback
(i.e., could have been sdch encoded) are sampled.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
During the running of an SDCH latency experiment, these packets were part of
a holdback, which precluded SDCH despite the fact that the link had proven
it was capable of handling SDCH compression.
Deprecated 2016-11.
If SDCH decoding was disabled client side, this records how many URLs were
processed by the SDCH filter before disabling this feature. The most common
number is 1, which happens when there is one home-page tab that contains
SDCH encoded data, for which there is no dictionary loaded into the Chrome
process (yet), since Chrome was just restarted. Large values in this
histogram are indicative of flaky decompression, that works for a while, and
then is disabled. Values of 2 or 3 may appear if a user has more than one
home page with a query, and restarts there browser.
Deprecated 2017-9.
The amount of time between creation/load of an SDCH dictionary and its first
use.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 1st SDCH encoded packet and receipt of the 2nd packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
The duration between receipt of the 1st SDCH encoded packet and receipt of
the last packet, for processing by the SDCH filter.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 2nd SDCH encoded packet and receipt of the 3rd packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 3rd SDCH encoded packet and receipt of the 4th packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 4th SDCH encoded packet and receipt of the 5th packet, for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
(discontinued 7/29/2009, and replaced by
Sdch3.Network_Decode_Bytes_Processed_b) The number of bytes processed
(received over the net or from cache) by the SDCH filter chain.
Deprecated 2017-9.
The number of bytes processed (received over the net or from cache) by the
SDCH filter chain.
Deprecated 2016-11.
The number of bytes emitted after decoding by the SDCH filter.
Deprecated 2016-11.
The duration between putting the first byte of a request (such as a GET) on
the wire, until the last by of compressed SDCH encoded content is received
(with durations over 10 minutes discarded). During a planned latency
experiment, some clients will receive encoded SDCH data, and other will
received mere gzip'ed data (that passes through the SDCH filter unchanged).
Deprecated 2016-11.
An approximation to the total number of SDCH encoded packets received for
processing by the SDCH filter. Packet count boundaries are calculated each
time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
The ratio of the number of bytes read from the network (or cache) and fed to
the filter chain (usually the gunzip filter) vs. the number of bytes emitted
by the SDCH filter to be rendered. This is commonly described as the SDCH
compression ratio.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 1st **NON**-SDCH encoded packet to receipt of the 2nd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
The duration between receipt of the 1st **NON**-SDCH encoded packet to
receipt of the last packet, for processing by the SDCH filter.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 2nd **NON**-SDCH encoded packet to receipt of the 3rd packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 3rd **NON**-SDCH encoded packet to receipt of the 4th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
Sampling only transmissions with 5 or more packets, the duration between
receipt of the 4th **NON**-SDCH encoded packet to receipt of the 5th packet,
for processing by the SDCH filter. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
The duration between putting the first byte of a request (such as a GET) on
the wire, until the last by gzip compressed content is received and
passed-through unchanged by the SDCH filter (with durations over 10 minutes
discarded). During a planned latency experiment, some clients will receive
encoded SDCH data, and other will received mere gzip'ed data (that passes
through the SDCH filter unchanged).
Deprecated 2016-11.
The total number of **NON**-SDCH encoded packets received for processing by
the SDCH filter in one URL fetch. Packet count boundaries are calculated
each time a read from the filter is called, assuming 1430 bytes of data per
packet since the last boundary calculation. This *tends* to properly count
small packets, but can err if small packets come at roughly the same time.
Deprecated 2016-11.
ellyjones@chromium.org
The absolute difference in bytes between the amount of data entering the
SDCH filter and the amount of data exiting the SDCH filter.
Deprecated 2017-9.
ellyjones@chromium.org
Absolute sizes, in bytes, of SDCH dictionaries fetched over the network.
These are logged in SdchOwner when dictionary fetches complete.
Deprecated 2016-11.
If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF
decoder still has internally buffered data that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to the start of the filter chain (usually to the
gunzip filter).
Deprecated 2016-11.
If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF
decoder still has internally buffered data that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to VCDIFF decoder (usually after gunzipping).
Deprecated 2016-11.
If/when a ProblemCode INCOMPLETE_SDCH_CONTENT reports that the VCDIFF
decoder still has internally buffered data that has never been read, this
histogram reports the number of bytes that were output by the VCDIFF decoder
(and sent toward the renderer).
Deprecated 2017-9.
Tracks failures that occur when reading in or writing out persisted
dictionary information.
Deprecated 2014-11. Sdch3.ProblemCodes_5 used instead.
Each sample is the report of a distinct problem code.
Deprecated 2014-11. Sdch3.ProblemCodes_5 used instead.
Each sample is the report of a distinct problem code.
Deprecated 2017-9.
Each sample is the report of a distinct problem code.
Deprecated 2017-9.
Attempted SDCH decoding can fail at the Read() filter processing stage. In
some of those cases, the request is corrupted enough that it must be either
retried or failed completely. This histogram records the details of why the
request was considered corrupted, for results returned from the cache.
Deprecated 2017-9.
Attempted SDCH decoding can fail at the Read() filter processing stage. In
some of those cases, the request is corrupted enough that it must be either
retried or failed completely. This histogram records the details of why the
request was considered corrupted for results returned from the network.
Deprecated 2017-9.
ellyjones@chromium.org
Measures the time-weighted memory use of SDCH dictionaries, in bytes. The
numerator is bytes of dictionary times seconds that dictionary was in
memory, and the denominator is seconds that the Chrome process lives.
Deprecated 2016-11.
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were in that buffer.
Deprecated 2016-11.
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to the start of the filter chain (usually to the
gunzip filter).
Deprecated 2016-11.
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were received over the net (or
from the cache) and fed to VCDIFF decoder (usually after gunzipping).
Deprecated 2016-11.
If/when a ProblemCode UNFLUSHED_CONTENT reports that the SDCH filter is
still buffering output of the VCDIFF decoder that has never been read, this
histogram reports the number of bytes that were output by the VCDIFF decoder
(and sent toward the renderer).
Use Sdch3.UsageInterval2 instead.
The amount of time from the last time an SDCH dictionary was used. For the
first use of a dictionary, the maximum time is used.
Deprecated 2017-9.
The amount of time from the last time an SDCH dictionary was used. Not
recorded on first dictionary use. First use is recorded as
Sdch3.FirstUseInterval.
Replaced by Search.AddSearchProvider2, which is also now obsolete.
estade@chromium.org
Measures how much the user modifies their search engines, whether through
window.external.AddSearchProvider or chrome://settings.
AddSearchProvider was removed 05/2016.
estade@chromium.org
Measures usage of window.external.AddSearchProvider and user interaction
with the resulting confirmation dialog (if any). Only works on Views
platforms (Win, Linux, CrOS).
donnd@chromium.org
twellington@chromium.org
Records whether the user opened the panel when it was shown. Recorded for
all gestures for all users when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Logs that the UX has entered a state where features are available to be
recorded to Ranker. A value of true indicates that the available features
include outcomes, false if they are just features at inference-time. Use to
correlate with what actually gets recorded in the Search.
ContextualSearch.Ranker.Recorded histogram. Recorded when a tap gesture is
recognized that might trigger our UX (for pure features), and when the UX is
actually shown (for outcomes). Implemented for Android.
hamelphi@google.com
Tracks the outcome of attempts to download a Ranker Model.
donnd@chromium.org
twellington@chromium.org
Records whether the user opened the panel when a tap was not suppressed by
Ranker. Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Logs that features were recorded to Ranker and whether it was an outcome or
not. Recorded when the UX is shown or hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Logs that features were recorded to Ranker from native code and whether it
was an outcome or not. Recorded when the UX is shown or hidden. Implemented
for Android.
donnd@chromium.org
twellington@chromium.org
Records Ranker's prediction about whether a tap should be suppressed or not.
Recorded when the UX is hidden. Implemented for Android.
hamelphi@google.com
Time taken for the Ranker Model Loader to download its model from the
configured URL, in ms.
hamelphi@google.com
Time taken for the Ranker Model Loader to parse its model, in ms.
hamelphi@google.com
Time taken for the Ranker Model Loader to read its model from local storage
(cache), in ms.
hamelphi@google.com
Time taken for the Ranker Model Loader to write its model to local storage,
in ms.
donnd@chromium.org
twellington@chromium.org
Records whether Ranker was able to make a prediction about tap suppression.
Recorded when the UX is triggered by tap. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Records whether the user opened the panel when a tap would be suppressed by
Ranker if suppression was enforced. Recorded when the UX is hidden.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Records whether the user opened the panel when it was shown in response to a
tap gesture, for all users. Recorded when the UX is hidden. Implemented for
Android.
Deprecated 05/2017 because it's no longer ever used.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen during a contextual search where the
selected text consisted of all capital letters. Only logged when contextual
search is triggered due to a tap. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The duration that the panel was peeking before being opened when triggered
by a tap that was in a part of the screen where it overlaps the Bar. Logged
when the panel is closed after being opened. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether a Tap was suppressed because the Bar overlapped the selection area.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The duration that the panel was peeking before being opened when triggered
by a tap at the bottom of the screen where it overlaps the Bar. Logged when
the panel is closed after being opened. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether the Bar overlapped the selection area and whether the results were
seen. Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The protocol of the base page, logged at the time that any Search Term
Resolution Response is recieved.
Discontinued on 5/2017 due to experiment being completed.
donnd@chromium.org
pedrosimonetti@chromium.org
twellington@chromium.org
The details (blacklist reason and whether the results were seen) of every
search term issued by a tap gesture. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether Contextual Cards data was shown in the Contextual Search Bar.
Contextual Cards data is included with the search term resolution response.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen as part of a Contextual Search when
Contextual Cards data was shown. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The duration between the panel being triggered and the panel being dismissed
due to a scroll when search results were not seen. Implemented for Android.
Prior to M57 this was recorded on tap and longpress; on M57+ it is only
recorded on tap.
donnd@chromium.org
twellington@chromium.org
The duration between the panel being triggered and the panel being dismissed
due to a scroll when search results were seen. Implemented for Android.
Prior to M57 this was recorded on tap and longpress; on M57+ it is only
recorded on tap.
Discontinued on 2/2017 Due to data being buggy and not useful.
donnd@chromium.org
twellington@chromium.org
The time from opening the panel until the SERP is fully loaded. Applies only
to non-prefetched requests. Implemented for Android.
Discontinued on 2/2017 Due to data being buggy and not useful.
donnd@chromium.org
twellington@chromium.org
The time from opening the panel until the SERP is fully loaded. Applies only
to prefetched requests. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from initiating to ending a contextual search, when results were
seen as part of the search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from initiating to ending a contextual search, when results were
not seen as part of the search and the search did not end with the beginning
of another contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from initiating to ending a contextual search, when results were
not seen as part of the search and the search ended with the beginning of
another contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (previous state and reason) of the first entry into the closed
panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (previous state and reason) of the first entry into the expanded
panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (previous state and reason) of the first entry into the
maximized panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (previous state and reason) of the first entry into the peeked
panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen as part of a Contextual Search when a tap
was on a word that we think is an entity. Recorded when Contextual Search is
dismissed. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (destination state and reason) of the first exit out of the
closed panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (destination state and reason) of the first exit out of the
expanded panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (destination state and reason) of the first exit out of the
maximized panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The details (destination state and reason) of the first exit out of the
peeked panel state within a contextual search. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The status of the Contextual Search fallback Search request. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
The state of the Contextual Search Preference after the first run flow.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether the first run flow's panel was seen as part of a contextual search.
Only logged when the user triggered the first run flow yet exited the search
still in the undecided preference state. Implemented for Android.
Contextual Search icon sprite removed 04/2017.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen, whether the search provider icon sprite
was animated when the panel first appeared, and the triggering gesture. If
animation is disabled due to a field trial, we still log
"animated" if the animation would have run otherwise.
donnd@chromium.org
mahmoudi@chromium.org
twellington@chromium.org
The number of times the Contextual Search panel is opened, categorized by
whether In-Product Help for Contextual Search was shown before. Logged when
the panel is opened. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from starting a literal search until the results in the SERP start
to become viewable. Applies only to prefetched requests. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
The status of the Contextual Search low priority Search request. Implemented
for Android.
donnd@chromium.org
pedrosimonetti@chromium.org
twellington@chromium.org
The outcome of the mandatory Promo broken down by original triggering
gesture. Logged for each view of the promo. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The status of the Contextual Search normal priority Search request.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from opening the panel beyond peek until the panel is closed.
Implemented for Android.
donnd@chromium.org
mahmoudi@chromium.org
twellington@chromium.org
The number of times the Contextual Search panel is opened, categorized by
whether In-Product Help for opening the panel was shown before. Logged when
the panel is opened. Implemented for Android.
Removed because the feature no longer exists.
donnd@chromium.org
pedrosimonetti@chromium.org
twellington@chromium.org
The number of times the Peek Promo was seen. This histogram will be emitted
when the Panel closes. The panel is always visible when the Peek Promo is
shown, so this histogram will always be emitted after a Promo is shown
(except in the case of a crash). This histogram does not care whether the
Panel was opened.
Removed because the feature no longer exists.
donnd@chromium.org
pedrosimonetti@chromium.org
twellington@chromium.org
The number of times the Peek Promo was seen until the Panel was opened. This
histogram will be emitted when the Panel closes, if the Panel was opened
with the Peek Promo visible. If the Panel is not opened, nothing will be
emitted.
Removed because the feature no longer exists.
donnd@chromium.org
pedrosimonetti@chromium.org
twellington@chromium.org
The outcome of the Contextual Search Peek Promo for those who have seen the
promo and for those who would have seen the promo if it was enabled, so we
can compare the effect of the promo on users opening the Panel. This
histogram will be emitted when the Panel closes, if the conditions to
display the Peek Promo are met, regardless of whether the Peek Promo was
actually visible (the Promo is controlled by Finch) and regardless of
whether the Panel was opened.
donnd@chromium.org
twellington@chromium.org
The state of the Contextual Search Preference. Can be logged multiple times.
Used to determine the population size (user view). Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The Contextual Search preference state after a modification from the
preference menu. Implemented for Android.
Discontinued on 2/2017 Due to data not being useful.
donnd@chromium.org
twellington@chromium.org
A summary histogram for prefetch timings, indicating fully preloaded, etc.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The CTR from the previous 28 day period for each user, expressed as a
percentage. Logged the first time the panel is closed in each new week.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The number of user impressions of the Bar from the previous 28 day period.
Logged the first time the panel is closed in each new week. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
The CTR from the previous week for each user, expressed as a percentage.
Logged the first time the panel is closed in each new week. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
The number of user impressions of the Bar from the previous week. Logged the
first time the panel is closed in each new week. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The total count of times that the bar with the promo has been opened. Once
the user decides, this counter is no longer updated.
donnd@chromium.org
twellington@chromium.org
The outcome of the promo broken down by original triggering gesture. Logged
for each view of the promo. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether the promo was seen, broken down by original triggering gesture.
Logged each time the promo was activated. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The historic number of taps that showed a peeking bar with the opt-out promo
before the first time the user opened the panel.
donnd@chromium.org
twellington@chromium.org
The historic number of taps that showed a peeking bar with the opt-out promo
for users who have never opened the panel. This count may be limited by the
Finch config param promo_on_limited_taps.
donnd@chromium.org
twellington@chromium.org
The number of remaining taps that can trigger the promo for this user.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The category of quick actions shown in the Contextual Search bar. Recorded
when the quick action is set. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether a quick action in the Contextual Search bar was clicked. Recorded
when Contextual Search is dismissed. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether a Contextual Search quick action intent resolved to zero, one, or
many apps. Recorded when the quick action intent URI is resolved.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen as part of a Contextual Search when a quick
action was shown. Recorded when Contextual Search is dismissed. Implemented
for Android.
donnd@chromium.org
twellington@chromium.org
Whether a quick action was shown in the Contextual Search bar. Recorded when
the quick action is set. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether a Quick Answer was activated, considered an answer, and seen.
Implemented for Android.
Deprecated 02/2017.
donnd@chromium.org
twellington@chromium.org
The duration since a recent scroll when the results were not seen. Recorded
when the UX is hidden. Implemented for Android.
Deprecated 02/2017.
donnd@chromium.org
twellington@chromium.org
The duration since a recent scroll when the results were seen. Recorded when
the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether showing the Tap to Search UX in response to a Tap was suppressed by
a recent scroll. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from starting a resolving search until the Search Term Resolves.
Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time from starting a resolving search until the results in the SERP
start to become viewable. Applies only to prefetched requests. Implemented
for Android.
donnd@chromium.org
twellington@chromium.org
Whether the search term was single or multi-word, logged at the time that
any Search Term Resolution Response is recieved.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen as part of a contextual search. Implemented
for Android.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen, broken down by original triggering
gesture. Only includes users that have enabled. Implemented for Android.
Deprecated 05/2017 because it's no longer ever used.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen (Contextual Search panel was opened) when
the selection was part of a URL, broken down by original triggering gesture.
Includes both users that have enabled Contextual Search and users that are
undecided (have neither enabled or disabled the feature). Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
Whether Taps near the top of the screen was suppressed. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a second tap that was allowed to override ML
Tap Suppression. Recorded when the UX is hidden. Implemented for Android.
Removed 11/2017 because the data is no longer valuable.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap during suppression when Tap Suppression
is enabled. Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The length of the triggering selection when search results were not seen.
Only logged when contextual search is triggered due to a tap. Implemented
for Android.
donnd@chromium.org
twellington@chromium.org
The length of the triggering selection when search results were seen. Only
logged when contextual search is triggered due to a tap. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
Whether a Tap was suppressed because the selection length was less than the
minimum selection length. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether a Contextual Search selection was valid. Implemented for Android.
Removed 02/2017 because the data is no longer valuable.
donnd@chromium.org
twellington@chromium.org
Whether the SERP was fully loaded when an opened panel was closed.
donnd@chromium.org
twellington@chromium.org
Emitted when a translate one-box should be forced, to indicate if it
actually was forced or simply would have been forced if not disabled by a
flag in the variations_service.
Removed 05/2017 because the data is no longer needed.
donnd@chromium.org
twellington@chromium.org
Whether search results were seen during a contextual search where the
selected text started with a capital letter but was not all capital letters.
Only logged when contextual search is triggered due to a tap. Implemented
for Android.
donnd@chromium.org
twellington@chromium.org
The duration of a tap that triggered a Contextual Search when the user does
not open the panel. Implemented for Android. Logged when the panel closes
after being triggered by a tap.
donnd@chromium.org
twellington@chromium.org
The duration of a tap that triggered a Contextual Search when the user does
open the panel. Implemented for Android. Logged when the panel closes after
being triggered by a tap and subsequently opened.
donnd@chromium.org
mahmoudi@chromium.org
twellington@chromium.org
The number of times the Contextual Search is triggered by tapping,
categorized by whether In-Product Help for tapping was shown before. Logged
when Contextual Search is triggered by tapping. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap that was of long duration. Recorded when
the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap that was on a word considered long.
Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap that was on the middle part of a word.
Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap that was of short duration. Recorded
when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap that was on a word considered short.
Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The count of taps that showed a peeking bar without the opt-out promo since
this user has last opened the panel.
donnd@chromium.org
twellington@chromium.org
The count of taps that showed a peeking bar with the opt-out promo since
this user has last opened the panel.
Removed 11/2017 because the data is no longer valuable.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap before suppression when Tap Suppression
is enabled. Recorded when the UX is hidden. Implemented for Android.
donnd@chromium.org
twellington@chromium.org
Whether results were seen for a Tap and whether any suppression heuristic
was satisifed. Recorded when the UX is still shown (suppression not enabled,
only logged). Implemented for Android.
donnd@chromium.org
twellington@chromium.org
The time between tapping on a word and performing a search. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
The DPs count histogram for Taps that were not seen. Implemented for
Android.
donnd@chromium.org
twellington@chromium.org
The DPs count histogram for Taps that were seen. Implemented for Android.
donnd@chromium.org
mahmoudi@chromium.org
twellington@chromium.org
For each contextual search that is triggered by tap, records whether the
translation conditions are met. Implemented for Android.
mathp@chromium.org
The origin/cause of a change to the default search provider.
Made obsolete around Chrome 32. Use Search.DefaultSearchProviderType
instead.
Please list the metric's owners. Add more owner tags as needed.
The id of the default search engine that is loaded after Chrome startup. See
src/chrome/browser/search_engines/prepopulate_engines.json for more info.
mpearson@chromium.org
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.
Deprecated 05/2016 because desktop searches are no longer opened in the
default browser.
fdoray@chromium.org
The action performed by the user to close the infobar explaining that a
desktop search has been redirected to the default search engine.
Deprecated 05/2016 because desktop searches are no longer opened in the
default browser.
fdoray@chromium.org
The action performed when a desktop search URL is passed to the browser
through the command line.
lizeb@chromium.org
On Android, when GSA tells Chrome about an account change, what is the
notification mechanism used, which is either the service connection, or a
broadcast. Recorded once per account change.
lizeb@chromium.org
On Android, whether GSA tells Chrome about account changes through the
service or through a broadcast. This is reported at most once per Chrome
startup.
Deprecated 06/2017, no longer recorded.
lizeb@chromium.org
On Android, when Chrome connects to a bound service exposed by GSA, the
memory footprint of the GSA process in KB, as measured by PSS. Reported at
most once per Chrome startup.
wychen@chromium.org
yusufo@chromium.org
The last sequential number in the delta file for Icing. This is measured on
cold start.
wychen@chromium.org
yusufo@chromium.org
The number of entries in the delta file level DB for Icing. This is measured
on cold start.
wychen@chromium.org
yusufo@chromium.org
The number of entries in the usage report level DB for Icing. This is
measured on cold start.
joaodasilva@chromium.org
Records the reason why a context report to Icing failed, every time Chrome
attemps to record the current context (tab switching, navigations, etc).
Also records reasons why context reporting might be disabled. Recorded on
Android only.
Deprecated after migrator is deleted in 12/2016.
caitkp@chromium.org
The number of times that a user-selected DSE was migrated from separate
String/List/..Value preferences to the new single DictionaryValue used in
M36.
yusufo@chromium.org
The entry point used for all searches performed under partnership after the
Android search engine promo dialog was shown. This is a dialog prompting the
user to pick a default search engine. This metric is collected for every
search query performed.
yusufo@chromium.org
The search engines listed in the options for search engine promo. This is an
Android specific dialog prompting the user to pick a default search engine.
The dialog was shown on a device that had Chrome before it was first
introduced.
yusufo@chromium.org
The search engine selected by the user from the search engine promo. This is
an Android specific dialog prompting the user to pick a default search
engine. The dialog was shown on a device that had Chrome before it was first
introduced.
yusufo@chromium.org
The current state for search widget use and whether the device is a
partnership device related with the Android Search Widget. Collected on
every cold start.
vadimt@chromium.org
Time between showing and hiding the answer card.
vadimt@chromium.org
Time between sending an answer server request and the end of loading of the
answer card. Failed requests and requests not returning an answer are not
counted.
vadimt@chromium.org
Time between sending an answer server request and successful finish of
navigation. Failed requests and requests not returning an answer are not
counted.
vadimt@chromium.org
Result of a answer server request.
vadimt@chromium.org
Time between successfully loading an answer card request and updating its
preferred size. There might be no or more than one size update per card
load. Size updates that happen before the card finishes loading are ignored
since they are not visible.
estark@chromium.org
The compliance of each main frame navigation's connection with the
Certificate Transparency policy. Recorded whenever a main-frame,
non-same-page navigation is committed. Connections can be compliant, or they
can be non-compliant for one of several reasons (not enough Signed
Certificate Timestamps [SCTs], not diverse enough SCTs, or the build was old
so CT compliance wasn't checked).
estark@chromium.org
Records the time from when a page was put into a warning state because of a
sensitive input on an HTTP page until a navigation starts. Recorded at most
once per main-frame navigation. The Finch trial 'mark-non-secure-as'
controls whether the user sees an omnibox warning for this state, or just a
console warning.
Deprecated on 2016-11-10 because this is replaced by two separate metrics:
Security.HTTPBad.UserWarnedAboutSensitiveInput.CreditCard and
Security.HTTPBad.UserWarnedAboutSensitiveInput.Password.
elawrence@chromium.org
estark@chromium.org
Whether a "Not Secure" warning was shown in the omnibox because a
security-sensitive form field was rendered in a non-secure context. Logged
at most once per main-frame navigation.
elawrence@chromium.org
estark@chromium.org
Whether a "Not Secure" warning was shown in the omnibox because a
credit card form field was rendered in a non-secure context. Logged at most
once per main-frame navigation.
elawrence@chromium.org
estark@chromium.org
Whether a "Not Secure" warning was shown in the omnibox because a
password form field was rendered in a non-secure context. Logged at most
once per main-frame navigation.
estark@chromium.org
Records the time delta between when a page was put into a warning state
because of a sensitive input on an HTTP page and when the WebContents was
destroyed. Recorded at most once per main-frame navigation, and it is not
recorded if the user starts a navigation before the WebContents is
destroyed. The Finch trial 'mark-non-secure-as' controls whether the user
sees an omnibox warning for this state, or just a console warning.
cthomp@chromium.org
Records the reason the page visit ended (e.g., reload, tab closed, new
navigation, etc.) for page loads that committed.
estark@chromium.org
Tracks Page Info bubble actions that take place on an HTTPS URL that has
been marked dangerous or not secure (such as for malware or broken HTTPS).
estark@chromium.org
Tracks Page Info bubble actions that take place on a valid HTTPS URL that
has a security issue (e.g. mixed content).
Deprecated 2018-01-31, split into ValidEV and ValidNonEV.
estark@chromium.org
Tracks Page Info bubble actions that take place on a valid HTTPS URL with no
security issues (e.g. no mixed content).
estark@chromium.org
Tracks Page Info bubble actions that take place on a valid HTTPS URL with no
security issues (e.g. no mixed content) and an Extended Validation
Certificate.
estark@chromium.org
Tracks Page Info bubble actions that take place on a valid HTTPS URL with no
security issues (e.g. no mixed content), but no Extended Validation
Certificate.
estark@chromium.org
Tracks Page Info bubble actions that take place on an HTTP URL that has been
marked dangerous (such as for malware).
estark@chromium.org
Tracks Page Info bubble actions that take place on an HTTP URL that does not
have an omnibox security indicator warning associated with it.
estark@chromium.org
Tracks Page Info bubble actions that take place on an HTTP URL that has been
given a "Not secure" warning in the omnibox.
cthomp@chromium.org
Records the amount of time the Page Info bubble is open before the user
closes it or takes an action which closes it.
cthomp@chromium.org
Records the amount of time the Page Info bubble is open before the user
closes it, for cases where the user has performed an action inside it.
cthomp@chromium.org
Records the amount of time the Page Info bubble is open before the user
closes it, for cases where the user performed no action inside it.
estark@chromium.org
Records the security level of a page with a cryptographic scheme (e.g.
https). This histogram is recorded once at navigation commit time, and can
be called again for the same document if the security level changes
dynamically. Note that the security level can change very quickly after
commit time, for example if the page includes mixed content on load (which
can downgrade the security level). This histogram should be analyzed with
care because each recorded security level is not necessarily user-visible:
in particular, a page may commit as a secure level (SECURE, EV_SECURE,
SECURE_WITH_POLICY_INSTALLED_CERT) but get quickly downgraded to NONE if it
shows mixed content on load. Therefore the histogram values should be
regarded as an upper-bound on what the user actually sees for these security
levels.
cthomp@chromium.org
Records the security level of the page that initiated a download (rather
than the security state of the connection to the download URL itself). The
recorded security level is the level of the page the download was initiated
from, not that of the download URL. This histogram is not recorded for
downloads that are initiated in a new tab or window, as the security level
of the initiating page cannot be tracked.
carlosil@chromium.org
cthomp@chromium.org
Records the security level of a page when submitting a form. This histogram
is recorded whenever a form submission navigation begins. The recorded
security level is the level of the page the form was submitted from, not the
one that the form targets.
estark@chromium.org
Records the security level of a page with a non-cryptographic scheme (e.g.
http). This histogram is recorded once at navigation commit time, and can be
called again for the same document if the security level changes
dynamically. Note that the security level can change very quickly after
commit time, for example if the page includes a password field on load
(which can downgrade the security level). This histogram should be analyzed
with care because each recorded security level is not necessarily
user-visible: in particular, a page may commit as NONE or HTTP_SHOW_WARNING
but get quickly downgraded to HTTP_SHOW_WARNING or DANGEROUS, depending on
field trial configuration, if it shows a password field on load. Therefore
the histogram values should be regarded as an upper-bound on what the user
actually sees for the NONE and HTTP_SHOW_WARNING levels.
cthomp@chromium.org
Records the security level of a page at the time the navigation commits.
Note that the security level of a page can change after commit time, so this
histogram should often be compared against
Security.SecurityLevel.OnComplete.
cthomp@chromium.org
Records the security level of a page at the end of the page visit (i.e.,
navigating away from the page, reloading the page, clicking a link, closing
the tab, etc.). Note that this security level can be different than the
initial security level of the page, so this histogram should often be
compared against Security.SecuritLevel.OnCommit.
cthomp@chromium.org
The final Site Engagement score (0 to 100) of a URL during a visit to a
page. Recorded when the user closes the page or initiates a new navigation.
cthomp@chromium.org
The change in Site Engagement score for a site between the page navigation
committing and the user closing the page or navigating away. Recorded when
the user closes the page or initiates a new navigation.
The delta is logged as a linear count in [0, 100]. To use, convert back to
the original difference (in the range [-100,100]) by multiplying by 2 and
subtracting 100.
cthomp@chromium.org
Records the time spent on the page (the time that the page was in the
foreground from the start of the navigation to the page visit completing due
to a new navigation or the tab being closed). This aggregates all foreground
time over the entire visit (multiple times in the foreground are added
together).
mkwst@chromium.org
Records the number of origins which will be treated as secure based on their
presence in the '--unsafely-treat-insecure-origin-as-secure' command-line
flag.
mkwst@chromium.org
arthursonzogni@chromium.org
Record uses of the X-Frame-Options header when a page is loaded as an
iframe.
Deprecated 02/2018. SequencedWorkerPool has been removed.
gab@chromium.org
How long it takes to wait for tasks that block shutdown to complete.
Histogram wasn't even reported anymore when ownership was taken in 11/2015.
gab@chromium.org
How many pending tasks there are on each request for work from a worker
thread.
Histogram wasn't even reported anymore when ownership was taken in 11/2015.
gab@chromium.org
How many tasks we skip over to find the next runnable task.
alemate@chromium.org
Records result of fetching and parsing OEM customization manifest. See
ServicesCustomizationDocument class for more info. Used only on Chrome OS.
jinho.bang@samsung.com
The time taken between dispatching an AbortPaymentEvent to a Service Worker
and receiving a message that it finished handling the event. Includes the
time for the waitUntil() promise to settle.
horo@chromium.org
The time taken for the browser to find and possibly start an active worker
to dispatch a FetchEvent for a main frame resource request. BEWARE: This
metric includes the time taken for redirects. It starts when the URLRequest
is created, and ends when the worker is ready. For context, a FetchEvent can
only be dispatched to an ACTIVATED worker that is running (it has been
successfully started). The measurements starts when the browser process
receives the request. The browser then finds the worker appropriate for this
request (if there is none, this metric is not recorded). If that worker is
already started, the browser process can send the request to it, so the
measurement ends quickly. Otherwise the browser process has to start the
worker and the measurement ends when the worker is successfully started (we
do not include in the time it takes for the worker to become ACTIVATED). The
metric is not recorded in the following situations: 1) The worker was in
state INSTALLED or ACTIVATING, and the browser had to wait for it to become
ACTIVATED. This is to avoid including the time to execute the activate event
handlers in the worker's script. 2) The worker was started for the fetch AND
DevTools was attached during startup. This is intended to avoid including
the time for debugging. 3) The request is for New Tab Page. This is because
it tends to dominate the stats and makes the results largely skewed.
It will be removed after NetS13nSW ships. https://crbug.com/715640
falken@chromium.org
The type of preparation needed for the browser to find and possibly start an
active worker to dispatch a FetchEvent for a main frame resource request.
See details at ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time.
The suffixed histograms for .Time record the time required for each type.
This is recorded regardless of whether NetS13nSW (https://crbug.com/715640)
is enabled or disabled.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for
waitUntil() promise to settle.
Deprecated 2015-05 in favor of ServiceWorker.ActivateEvent.Time.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for
waitUntil() promise to settle.
falken@chromium.org
The result of dispatching the activate event to the worker. This is recorded
to both ServiceWorker.ActivateEventStatus and whichever of
ServiceWorker.ActivateEventStatus_InShutdown
ServiceWorker.ActivateEventStatus_NotInShutdown is appropriate. (InShutdown
means the context was null or ServiceWorkerProcessManger::Shutdown was
called.)
peter@chromium.org
The time taken between dispatching a BackgroundFetchAbortEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
peter@chromium.org
The time taken between dispatching a BackgroundFetchClickEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
peter@chromium.org
The time taken between dispatching a BackgroundFetchedEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
peter@chromium.org
The time taken between dispatching a BackgroundFetchFailEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
jkarlin@chromium.org
The time taken between dispatching a SyncEvent to a Service Worker and
receiving a message that it finished handling the event. Includes the time
for the waitUntil() promise to settle.
horo@chromium.org
The length of cached metadata of scripts which are stored to the
CacheStorage by the installing service worker.
horo@chromium.org
The total length of cached metadata of scripts which are stored to the
CacheStorage by the installing service worker.
horo@chromium.org
The counts of scripts which are stored to the CacheStorage by the installing
service worker.
horo@chromium.org
The length of scripts which are stored to the CacheStorage by the installing
service worker.
horo@chromium.org
The total length of scripts which are stored to the CacheStorage by the
installing service worker.
jinho.bang@samsung.com
The time taken between dispatching an CanMakePaymentEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
falken@chromium.org
The result of ServiceWorkerContextRequestHandler handling a request for a
service worker script. The histogram is suffixed to distinguish new vs
installed workers and main vs imported scripts.
Note that since M64, this no longer includes most script loads because those
are handled by ServiceWorkerInstalledScriptsManager, which doesn't record
this histogram.
It will be removed after NetS13nSW ships. https://crbug.com/715640
pwnall@chromium.org
The time taken between dispatching a CookieChangeEvent to a Service Worker
and receiving a message that it finished handling the event. Includes the
time for the waitUntil() promise to settle.
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.
bashi@chromium.org
nhiroki@chromium.org
Records result of writing response into ServiceWorkerDiskCache. This is not
recorded when response has no body. Note that this is recorded on every
write operation, and can there can be multiple write operations for the same
response if it is large enough.
This is recorded regardless of whether NetS13nSW (https://crbug.com/715640)
is enabled or disabled.
Deprecated because the migrator was removed as of 12/2015.
nhiroki@chromium.org
Records result of ServiceWorkerDiskCacheMigrator::Start that migrates
resources in BlockFile backend to Simple backend.
Deprecated because the migrator was removed as of 12/2015.
nhiroki@chromium.org
Execution time of ServiceWorkerDiskCache migration from BlockFile to Simple.
Deprecated because the migrator was removed as of 12/2015.
nhiroki@chromium.org
The counts of resources migrated by ServiceWorkerDiskCacheMigrator. This
includes the main script and imported scripts.
panicker@chromium.org
Records when StartWorker is received on the renderer. This is used to
surface discrepancy between StartWorker being sent on the browser side and
not getting received by renderer.
EmbeddedWorkerInstance.Start.TimeToSendStartWorker should be used as a
baseline. TODO(panicker): This should be removed after investigation of
crbug/790903, potentially in M68.
horo@chromium.org
The time taken between sending an event IPC from the browser process to a
Service Worker and executing the event handler in the Service Worker.
For subresource fetch events (_FETCH_SUB_RESOURCE suffix) When NetS13nSW
(https://crbug.com/715640) is enabled, this is the time between sending a
DispatchFetchEvent message from the main thread and executing the event
handler in the Service Worker.
Removed July 2018 (M69)
kinuko@chromium.org
Records the proportion of (non foreign) fetch events that are handled
compared to the number of events that are fired for a ServiceWorker.
Recorded each time the ServiceWorker is stopped when at least one event was
fired.
Removed July 2018 (M69)
mek@chromium.org
Records the proportion of foreign fetch events that are handled compared to
the number of events that are fired for a ServiceWorker. Recorded each time
the ServiceWorker is stopped when at least one event was fired.
nhiroki@chromium.org
The time taken between dispatching an ExtendableMessageEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
lazyboy@chromium.org
The duration an external request spent to keep a service worker alive.
Currently, extension service workers use external requests to keep the
worker alive during the time the worker requests an extension API.
jeremyarcher@chromium.org
The time taken between dispatching a FetchEvent to a Service Worker and
receiving a fallback-to-network reply.
jeremyarcher@chromium.org
The time taken between dispatching a FetchEvent to a Service Worker and
receiving a response. Includes the time for the respondWith() promise to
settle.
falken@chromium.org
The result of dispatching a fetch event to a Service Worker for a main
resource request (i.e., a request for a navigation or a shared worker).
This is recorded regardless of whether NetS13nSW (https://crbug.com/715640)
is enabled or disabled.
falken@chromium.org
The result of dispatching a fetch event to a Service Worker for a
subresource request (i.e., not a navigation or a shared worker request).
This is recorded regardless of whether NetS13nSW (https://crbug.com/715640)
is enabled or disabled.
Deprecated on 2015-07-13; please use
ServiceWorker.FetchEvent.HasResponse.Time or
ServiceWorker.FetchEvent.Fallback.Time.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for
the respondWith() promise to settle.
shimazu@chromium.org
The time taken between dispatching a FetchEvent to a Service Worker and
finishing the FetchEvent. Includes the time for the waitUntil() promise to
settle. If there is no waitUntil promise, this will be almost the same with
HasResponse.Time or Fallback.Time.
Deprecated 2015-05 in favor of ServiceWorker.FetchEvent.Time.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onfetch. Includes the time for
the respondWith() promise to settle.
Deprecated April 2018.
mek@chromium.org
The number of origins a particular service worker with foreign fetch
registrations will intercept fetches from. A value of zero indicates that
the foreign fetch service worker intercepts requests from any origin.
Recorded at the end of a successful install event, if the service worker
registered for foreign fetch. A service worker that registers for foreign
fetch must always intercept fetches from at least one origin or intercept
fetches from all origins.
Deprecated April 2018.
mek@chromium.org
The number of foreign fetch scopes a particular service worker registered
for. Recorded at the end of every successful install event. A value of zero
indicates that the service worker did not register for foreign fetch.
mek@chromium.org
The time taken between dispatching a ForeignFetchEvent to a Service Worker
and receiving a fallback-to-network reply. Includes the time for the
waitUntil() promise to settle, if any.
mek@chromium.org
The time taken between dispatching a ForeignFetchEvent to a Service Worker
and receiving a response. Includes the time for the respondWith() promise to
settle.
shimazu@chromium.org
The time taken between dispatching a ForeignFetchEvent to a Service Worker
and finishing the ForeignFetch. Includes the time for the waitUntil()
promise to settle. If there is no waitUntil promise, this will be almost the
same with HasResponse.Time or Fallback.Time.
shimazu@chromium.org
The time taken between dispatching an InstallEvent to a Service Worker and
receiving a message that it finished handling the event. Includes the time
for the waitUntil() promise to settle.
Deprecated 2015-05 in favor of ServiceWorker.InstallEvent.Time.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.oninstall. Includes the time for
the waitUntil() promise to settle.
falken@chromium.org
The result of dispatching the install event to the worker.
horo@chromium.org
Counts main frame page loads controlled by a service worker.
Deprecated 2018-01 in favor of
PageLoad.Clients.ServiceWorker.PageTransition.
horo@chromium.org
The transition type for main frame page loads controlled by a service
worker.
Deprecated 2018-01.
horo@chromium.org
Total length of the server redirects during main frame page loads controlled
by a service worker.
Deprecated 2016-04 in favor of ServiceWorker.ExtendableMessageEvent.Time.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onmessage.
Deprecated 2015-05 in favor of ServiceWorker.MessageEvent.Time.
shimazu@chromium.org
Execution time of ServiceWorkerGlobalScope.onmessage.
This experiment was turned down, see https://crbug.com/616502.
horo@chromium.org
The precision of the speculative launch of Service Workers for navigation
hints. Recorded when the worker is stopped. If there was no main/sub frame
fetch event fired on the worker, this value is false. This means that the
speculative launch wasn't helpful.
Deprecated June 2017 in favor of ServiceWorker.NavPreload.ConcurrentTime,
see https://crbug.com/728035.
falken@chromium.org
The duration of time when both (1) a service worker is being found and
possibly started up, (2) the navigation preload request is in-flight. The
measurement ends once either the worker is prepared, or the navigation
preload response is received (OnReceiveResponse() is called). This is a
rough estimate of the performance win of using navigation preload, ignoring
concurrency overhead. This histogram is recorded when a navigation preload
response is succesfully forwarded to the service worker's fetch event, with
the same restrictions as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
additionally recorded to the appropriate suffixed histograms.
Deprecated June 2017 in favor of ServiceWorker.NavPreload.FinishedFirst, see
https://crbug.com/728035.
falken@chromium.org
Whether the navigation preload response arrived before the activated and
running service worker was prepared. This histogram is recorded when a
navigation preload response is succesfully forwarded to the service worker's
fetch event, with the same restrictions as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
additionally recorded to the appropriate suffixed histograms.
horo@chromium.org
The size of Service-Worker-Navigation-Preload header when the navigation
preload request is to be sent. The default value of the header is
"true", so the default size is 4.
Deprecated June 2017. No replacement exists. See https://crbug.com/728035.
falken@chromium.org
This is recorded in the case where the activated and running service worker
was prepared before the navigation preload response arrived. It is the
remaining time it took to receive the response after the worker was
prepared.
This histogram is recorded when a navigation preload response is succesfully
forwarded to the service worker's fetch event (for the case mentioned
above), with the same restrictions as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
additionally recorded to the appropriate suffixed histograms.
Deprecated June 2017 in favor of ServiceWorker.NavPreload.ResponseTime. See
https://crbug.com/728035.
falken@chromium.org
The time taken for the navigation preload response to start, i.e., when
OnReceiveResponse() is called. This histogram is recorded when a navigation
preload response is successfully forwarded to the service worker's fetch
event, with the same restrictions as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
additionally recorded to the appropriate suffixed histograms.
Deprecated June 2017 in favor of ServiceWorker.NavPreload.WorkerWaitTime.
See https://crbug.com/728035.
falken@chromium.org
This is recorded in the case where the navigation preload response arrived
before the activated and running service worker was prepared. It is the
remaining time it took to prepare the worker after the response arrived.
This histogram is recorded when a navigation preload response is succesfully
forwarded to the service worker's fetch event (for the case mentioned
above), with the same restrictions as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
additionally recorded to the appropriate suffixed histograms.
falken@chromium.org
The duration of time when both (1) a service worker is being found and
possibly started up, (2) the navigation preload request is in-flight. The
measurement ends once either the worker is prepared, or the navigation
preload response is received (OnReceiveResponse() is called). This is a
rough estimate of the performance win of using navigation preload, ignoring
concurrency overhead. This histogram is recorded when a navigation preload
response is succesfully forwarded to the service worker's fetch event, with
the same restrictions enumerated 1) through 3) for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
only recorded to the appropriate suffixed histograms.
It will be removed after NetS13nSW ships. https://crbug.com/715640
falken@chromium.org
Whether the navigation preload response arrived before the activated and
running service worker was prepared. This histogram is recorded when a
navigation preload response is succesfully forwarded to the service worker's
fetch event, with the same restrictions numbered 1) through 3) for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
only recorded to the appropriate suffixed histograms.
It will be removed after NetS13nSW ships. https://crbug.com/715640
falken@chromium.org
The time taken for the navigation preload response to start, i.e., when
OnReceiveResponse() is called. This histogram is recorded when a navigation
preload response is successfully forwarded to the service worker's fetch
event, with the same restrictions numbered 1) through 3) for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
only recorded to the appropriate suffixed histograms.
It will be removed after NetS13nSW ships. https://crbug.com/715640
falken@chromium.org
The type of preparation needed for the browser to find and possibly start an
active worker to dispatch a FetchEvent for a main frame resource request,
when navigation preload also occurred.
This histogram is recorded when a navigation preload response is succesfully
forwarded to the service worker's fetch event (for the case mentioned
above), with the same restrictions numbered 1) through 3) as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
only recorded to the appropriate suffixed histograms.
This is similar to
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Type_NavigationPreloadEnabled.
The difference is ServiceWorker.NavPreload.WorkerPreparationType gets logged
if the navigation preload successfully occurred, at the same time as the
other ServiceWorker.NavPreload.* metrics so is more safely comparable to
them. We could deprecate the Type_NavigationPreloadEnabled histogram if it
turns out there is no significant difference.
It will be removed after NetS13nSW ships. https://crbug.com/715640
falken@chromium.org
This is recorded in the case where the navigation preload response arrived
before the activated and running service worker was prepared. It is the
remaining time it took to prepare the worker after the response arrived.
This histogram is recorded when a navigation preload response is succesfully
forwarded to the service worker's fetch event (for the case mentioned
above), with the same restrictions numbered 1) through 3) as for
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time. The sample is
only recorded to the appropriate suffixed histograms.
peter@chromium.org
The time taken between dispatching a NotificationClickEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
Deprecated 2015-05 in favor of ServiceWorker.NotificationClickEvent.Time.
peter@chromium.org
Execution time of ServiceWorkerGlobalScope.onnotificationclick.
nsatragno@chromium.org
peter@chromium.org
The time taken between dispatching a NotificationCloseEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
falken@chromium.org
Counts page loads controlled by a service worker.
jinho.bang@samsung.com
The time taken between dispatching an PaymentRequestEvent to a Service
Worker and receiving a message that it finished handling the event. Includes
the time for the waitUntil() promise to settle.
johnme@chromium.org
The time taken between dispatching a PushEvent to a Service Worker and
receiving a message that it finished handling the event. Includes the time
for the waitUntil() promise to settle.
Deprecated 2015-05 in favor of ServiceWorker.PushEvent.Time.
johnme@chromium.org
Execution time of ServiceWorkerGlobalScope.onpush.
falken@chromium.org
The number of origins that have a service worker registration. Recorded near
browser startup, when the service worker storage system is initialized.
jeremyarcher@google.com
The number of Service Worker request timeouts, by request type.
falken@chromium.org
The amount of time a service worker ran for (wall time). Starts recording
when the service worker finished starting, and stops when the service worker
finished stopping. Not recorded if DevTools was attached to the service
worker at some point while it was running.
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.
Removed June 2018 (M69). This was recorded as 100% success since service
worker script streaming launched in M64, since load failures didn't reach
this UMA. When there is an error reading the script from storage, it's
typically recorded as a start worker failure under
SERVICE_WORKER_ERROR_DISK_CACHE.
falken@chromium.org
Whether loading the service worker script succeeded. Only recorded for
installed service workers. Recorded by the browser process when reported
back by the renderer during worker startup.
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 send the IPC message to a renderer process telling
it to stop an embedded worker. Recorded in EmbeddedWorkerInstance::Stop.
This was previously recorded for both the IPC and Mojo service worker
implementations, but as of Jan 2017, this is only recorded for the IPC
implementation. This histogram will be removed after the IPC implementation
is removed.
horo@chromium.org
The result of starting a service worker for a navigation hint.
horo@chromium.org
The precision of the speculative launch of Service Workers for navigation
hints. Recorded when the worker is stopped. True if a fetch event for a
main/sub frame navigation was fired on the worker before it stopped;
otherwise, false. False means the speculative launch wasn't helpful.
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
shimazu@chromium.org
Recorded on each successful service worker startup.
ServiceWorker.StartTiming.* uses timing data from both the renderer process
and browser process. This histogram describes whether the clocks are known
to be accurate and consistent accross processes, and whether the actual
timing data for this worker startup was consistent, i.e., TimeTicks did not
go backwards.
If the clocks and timing were inconsistent, ServiceWorker.StartTiming.*
metrics (other than this one) are not recorded.
falken@chromium.org
shimazu@chromium.org
The time taken to start a service worker that is already installed, from
start of the start sequence (finding a renderer) to ACK of started from the
renderer (which occurs after script execution). The metric is not recorded
if DevTools was ever attached to the Service Worker during startup. It does
not include time, if any, waiting for the service worker to finish stopping
before asking it to start, if that occurred.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) the renderer receiving the start worker IPC message,
to (b) initial JavaScript evaluation starting on the worker thread. Recorded
when ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) initial JavaScript evaluation finishing on the
worker thread, to (b) the browser receiving the worker started IPC message
(the final step of worker startup). Recorded when
ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) initial JavaScript evaluation starting on the worker
thread, to (b) initial JavaScript evaluation finishing on the worker thread.
Recorded when ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) the browser sending the start worker IPC message, to
(b) the renderer receiving the start worker IPC message. Recorded when
ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) the start of service worker startup, to (b) the
renderer receiving the start worker IPC message. Recorded when
ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) the start of service worker startup, to (b) initial
JavaScript evaluation finishing on the worker thread. Recorded when
ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) the start of service worker startup, to (b) initial
JavaScript evaluation starting on the worker thread. Recorded when
ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
shimazu@chromium.org
The time taken from (a) the start of service worker startup, to (b) the
browser sending the start worker IPC message. Recorded when
ServiceWorker.StartTiming.Duration is recorded.
falken@chromium.org
The result of trying to start a service worker after it has failed
consecutively. Recorded only for installed workers.
falken@chromium.org
The number of consecutive startup failures of a service worker. Recorded
each time the service worker failed (so there is double counting: failing
twice results in 1 and 2 being logged). Only for installed workers.
falken@chromium.org
When a worker startup succeeded after failing, the number of times the
worker had consecutively failed. Recorded only for installed workers.
shimazu@chromium.org
The result of sending installed scripts over
ServiceWorkerInstalledScriptsSender. This is recorded after every start
worker attempt that sent the scripts through
ServiceWorkerInstalledScriptsSender.
falken@chromium.org
The purpose for starting up a service worker. Recorded only 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. See also
ServiceWorker.StartWorker.StatusByPurpose_* for the breakdown by event type.
falken@chromium.org
The result of trying to start a service worker for a particular event type
(see ServiceWorker.StartWorker.Status for the total). Only recorded for
installed workers. For event type:
falken@chromium.org
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
Records the start purpose for a service worker that timed out while starting
up. Recorded only for installed workers.
falken@chromium.org
The phase the EmbeddedWorker was in when ServiceWorker startup timed out.
Removed from code in Oct 2015, replaced with ServiceWorker.WorkerStopped.
falken@chromium.org
The result of trying to stop a Service Worker. Recorded only for installed
Service Workers that succesfully stopped or were detected as stalling. If a
worker stalled and later stopped, it will be recorded as both STALLED and
STALLED_THEN_STOPPED.
falken@chromium.org
The time taken to stop a Service Worker.
nhiroki@chromium.org
Records result of storage recovery operations in ServiceWorkerStorage.
Deprecated because the migrator was removed as of 12/2015.
nhiroki@chromium.org
Records the final result of diskcache migration in ServiceWorkerStorage.
ServiceWorker.DiskCacheMigrator.MigrationResult records more detailed status
of migration operations.
nhiroki@chromium.org
Records successes and failures of purging a stale resource in
ServiceWorkerStorage.
Deprecated in June 2017.
falken@chromium.org
The time taken in the renderer process between the main thread asking the
worker thread to terminate and getting ACK that it terminated.
Deprecated in June 2017.
falken@chromium.org
Called at the beginning of each ServiceWorkerVersion::Dispatch*Event
function: the time elapsed since idle. Generally this is the time between
one event ending and one event starting, if the worker remained running in
the interim.
Deprecated 2015-06 in favor of ServiceWorker.EventHandledStatus*.
kinuko@chromium.org
Records the ratio of unhandled events to all events that are dispatched to
each ServiceWorker. Recorded when each ServiceWorkerVersion is destructed.
horo@chromium.org
Records the the mode of request that was fallbacked to the network by the
Service Worker.
falken@chromium.org
Records the result of a main resource request forwarded to a Service Worker.
falken@chromium.org
Records the error provided when the renderer returns a response with status
code zero to a main resource request forwarded to a Service Worker (i.e.,
ServiceWorker.URLRequestJob.MainResource.Result was
REQUEST_JOB_ERROR_RESPONSE_STATUS_ZERO).
falken@chromium.org
Records the result of a subresource request forwarded to a Service Worker.
falken@chromium.org
Records the error provided when the renderer returns a response with status
code zero to a subresource request forwarded to a Service Worker (i.e.,
ServiceWorker.URLRequestJob.Subresource.Result was
REQUEST_JOB_ERROR_RESPONSE_STATUS_ZERO).
falken@chromium.org
True if a message from the renderer intended for a browser-side embedded
worker instance found its recipient. False if the instance did not exist
when the message was received (e.g., it was a detached worker). Recorded in
EmbeddedWorkerRegistry::GetWorkerForMessage.
falken@chromium.org
The mechanism by which a service worker entered running status STOPPED.
dmurph@chromium.org
The time to perform operations on the Cache object in the ServiceWorker
Cache API.
nhiroki@chromium.org
Records the response type to be added in the Cache by Cache.add()/addAll().
jkarlin@chromium.org
Records the response type to be added in the Cache by all operations that
write to the cache.
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.
cmumford@chromium.org
The absolute difference between the ServiceWorker Cache size saved to the
CacheStorage index and the actual cache size when opened.
jkarlin@chromium.org
The result of opening the backend in the ServiceWorker Cache API.
horo@chromium.org
True if a response read from the CacheStorage has a url field. This field
was deprecated in M57.
jkarlin@chromium.org
An operation is slow (true) if it takes at least 10 seconds to run. If an
operation never completes, it will still be recorded as slow.
jkarlin@chromium.org
The time in ms from when an operation is started until it completes.
jkarlin@chromium.org
The time in ms from when an operation was queued until its task is posted.
jkarlin@chromium.org
The number of operations in the scheduling queue just before enqueuing a new
operation.
rohitrao@chromium.org
The number of tabs closed by the user during the current session
(launch/foregrounding to backgrounding).
This histogram is only logged on iOS when the application is backgrounded.
rohitrao@chromium.org
The number of tabs created by the user during the current session
(launch/foregrounding to backgrounding).
This histogram is only logged on iOS when the application is backgrounded.
rohitrao@chromium.org
The number of times the user changed the active tab (this can happen when
manually selecting a new tab, when a pre-rendered tab is made active, when
closing the current tab and the next one is selected) during the current
session (launch/foregrounding to backgrounding).
This histogram is only logged on iOS when the application is backgrounded.
asvitkine@chromium.org
chrisha@chromium.org
The length of a session (launch/foregrounding to backgrounding) in
milliseconds.
Desktop: This also takes into account user interaction and audio events.
Starting from M55 the session length is recorded by discounting for default
inactivity timeout. Also, until M69, there was a bug that caused
double-counting of some sessions.
Android: There is a known issue where JavaScript dialogs and other things
that take focus away from the Chrome activity can cause this metric to
record a session end prematurely. See: crbug.com/678276.
feuunk@chromium.org
The amount of active browsing time that was spent not being opted in to sync
but while having a refresh token for a user's account.
This time is measured from when the user starts interacting with the browser
until either they stopped interacting with the browser or their signin or
sync status changes. These end-points are when the metric is emitted.
Because a duration can end either because the user became inactive or
because their status changed, the distribution of individual durations
measured are unlikely to be helpful. Instead, please compare total
durations.
This metric is only recorded on Win/Mac/Linux.
One caveat with this metric is that if the user has multiple profiles open
at the same time, their session activity will be logged from all the
profiles, instead of only from the profile that the user is using at that
moment.
feuunk@chromium.org
The amount of active browsing time that was spent not being opted in to sync
and not having a refresh token for a user's account.
This time is measured from when the user starts interacting with the browser
until either they stopped interacting with the browser or their signin or
sync status changes. These end-points are when the metric is emitted.
Because a duration can end either because the user became inactive or
because their status changed, the distribution of individual durations
measured are unlikely to be helpful. Instead, please compare total
durations.
This metric is only recorded on Win/Mac/Linux.
One caveat with this metric is that if the user has multiple profiles open
at the same time, their session activity will be logged from all the
profiles, instead of only from the profile that the user is using at that
moment.
feuunk@chromium.org
The total session duration (see Session.TotalDuration) that was spent being
opted in to sync while having a valid refresh token for the account.
This time is measured from when the user starts interacting with the browser
until either they stopped interacting with the browser or their signin or
sync status changes. These end-points are when the metric is emitted.
Because a duration can end either because the user became inactive or
because their status changed, the distribution of individual durations
measured are unlikely to be helpful. Instead, please compare total
durations.
This metric is only recorded on Win/Mac/Linux.
One caveat with this metric is that if the user has multiple profiles open
at the same time, their session activity will be logged from all the
profiles, instead of only from the profile that the user is using at that
moment.
feuunk@chromium.org
The total session duration (see Session.TotalDuration) that was spent being
opted in to sync without a having a valid refresh token for the account.
This can for example be the case if the user signed out of the web, changed
their password, or otherwise invalidated their signin.
This time is measured from when the user starts interacting with the browser
until either they stopped interacting with the browser or their signin or
sync status changes. These end-points are when the metric is emitted.
Because a duration can end either because the user became inactive or
because their status changed, the distribution of individual durations
measured are unlikely to be helpful. Instead, please compare total
durations.
This metric is only recorded on Win/Mac/Linux.
One caveat with this metric is that if the user has multiple profiles open
at the same time, their session activity will be logged from all the
profiles, instead of only from the profile that the user is using at that
moment.
feuunk@chromium.org
The total session duration (see Session.TotalDuration) that was spent with
an account signed into the content area.
The difference between the With(out)Account measurements and the
Opted(In/Out)ToSyncWith(out)Account measurements is that these metrics are
derived from the user's cookies, not their refresh tokens.
This time is measured from when the user starts interacting with the browser
until either they stopped interacting with the browser or their signin
status changes. These end-points are when the metric is emitted.
Because a duration can end either because the user became inactive or
because their status changed, the distribution of individual durations
measured are unlikely to be helpful. Instead, please compare total
durations.
This metric is only recorded on Win/Mac/Linux.
One caveat with this metric is that if the user has multiple profiles open
at the same time, their session activity will be logged from all the
profiles, instead of only from the profile that the user is using at that
moment.
feuunk@chromium.org
The total session duration (see Session.TotalDuration) that was spent
without an account signed into the content area.
The difference between the With(out)Account measurements and the
Opted(In/Out)ToSyncWith(out)Account measurements is that these metrics are
derived from the user's cookies, not their refresh tokens.
This time is measured from when the user starts interacting with the browser
until either they stopped interacting with the browser or their signin
status changes. These end-points are when the metric is emitted.
Because a duration can end either because the user became inactive or
because their status changed, the distribution of individual durations
measured are unlikely to be helpful. Instead, please compare total
durations.
This metric is only recorded on Win/Mac/Linux.
One caveat with this metric is that if the user has multiple profiles open
at the same time, their session activity will be logged from all the
profiles, instead of only from the profile that the user is using at that
moment.
asvitkine@chromium.org
chrisha@chromium.org
The length of a session (launch/foregrounding to backgrounding) in
milliseconds.
Desktop: This also takes into account user interaction and audio events.
Starting from M55 the session length is recorded by discounting for default
inactivity timeout. Also, until M69, there was a bug that caused
double-counting of some sessions.
Android: This histogram isn't logged on Android. See instead
Session.TotalDuration.
yiyaoliu@chromium.org
How did the user interact with the SessionCrashed Bubble?
chrisha@chromium.org
The actions that have occurred in a session restore timeline. These are to
be interpreted as raw event counts. Tabs are almost certainly deferred due
to the existence memory pressure, but this may not always be the case.
chrisha@chromium.org
georgesak@chromium.org
The time from SessionRestore start until all tabs have finished loading.
Deprecated 2017-02 as not actionable.
The size of the commands written to disk. See SessionBackend for details.
Deprecated 2014-10 in favor of SessionRestore.ForegroundTabFirstPaint and
ultimately SessionRestore.ForegroundTabFirstPaint3.
jeremy@chromium.org
sky@chromium.org
TBD
chrisha@chromium.org
georgesak@chromium.org
The time from SessionRestore start until a visible tab has finished loading.
Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2
and ultimately SessionRestore.ForegroundTabFirstPaint3.
jeremy@chromium.org
sky@chromium.org
Deprecated 2015-03-13 in favor of SessionRestore.ForegroundTabFirstPaint2
and ultimately SessionRestore.ForegroundTabFirstPaint3.
Deprecated 2015-05 in favor of SessionRestore.ForegroundTabFirstPaint3.
jeremy@chromium.org
sky@chromium.org
The time from SessionRestore start until a visible tab's first paint. This
metric only records paints that have occurred after a tab has loaded.
chrisha@chromium.org
georgesak@chromium.org
The time from SessionRestore start until a visible tab's first paint.
Deprecated 2018-05-02. This data was used to confirm that the unique name
generation change succeeded in reducing memory usage, and is no longer
needed.
dcheng@chromium.org
The size of a unique name derived from the browsing context name. Emitted
when generating a unique name for a new subframe or when a subframe's
browsing context name is changed before the first real load is committed.
Only applies to subframes as main frames always have an empty unique name.
Deprecated 2017-08 due to unique name generation change. Please use
SessionRestore.FrameUniqueNameFromRequestedNameSize and
SessionRestore.FrameUniqueNameWithFramePathSize instead.
dcheng@chromium.org
Records the length of unique names for web frames that are saved as part of
session restore data. It is logged each time the unique name changes, which
typically happens when a web frame is first created or its name is changed
by mutating window.name.
Deprecated 2018-05-02. This data was used to confirm that the unique name
generation change succeeded in reducing memory usage, and is no longer
needed.
dcheng@chromium.org
The size of the browsing context name (based on the iframe name attribute or
window.name) when generating the unique name. Emitted when generating a
unique name for a new subframe or when a subframe's browsing context name is
changed before the first real load is committed. Only applies to subframes
as main frames always have an empty unique name.
Deprecated 2018-05-02. This data was used to confirm that the unique name
generation change succeeded in reducing memory usage, and is no longer
needed.
dcheng@chromium.org
The size of a unique name when falling back to the frame path algorithm. The
fallback path is used when the browsing context name is empty or non-unique.
Emitted when generating a unique name for a new subframe or when a
subframe's browsing context name is changed before the first real load is
committed. Only applies to subframes as main frames always have an empty
unique name.
Deprecated 2018-05-02. This data was used to confirm that the unique name
generation change succeeded in reducing memory usage, and is no longer
needed.
dcheng@chromium.org
The size of a unique name when falling back to the frame path algorithm,
divided by the depth of the frame. Used to normalize sizes for deeper nodes
in a frame tree. Emitted when generating a unique name for a new subframe or
when a subframe's browsing context name is changed before the first real
load is committed. Only applies to subframes as main frames always have an
empty unique name.
Deprecated 2017-02 as not actionable.
The size, in k, of the last session file on disk.
Deprecated 2017-02 as not actionable.
Like NavEntryCommittedPeriod, but specifically to provide a clearer
breakdown of samples in the 10 minutes - 8 hours range.
Deprecated 2017-02 as not actionable.
Milliseconds between subsequent Save() operations due to a nav entry being
committed (new tab created + nav initiated).
Deprecated 2017-02 as not actionable.
Like NavListPrunedPeriod, but specifically to provide a clearer breakdown of
samples in the 10 minutes - 8 hours range.
Deprecated 2017-02 as not actionable.
Milliseconds between subsequent Save() operations due to the navigation list
being pruned (typically a change in back/forward stacks).
Deprecated 2017-02 as not actionable.
The number of tabs that were loaded simultaneously when restoring a session.
Deprecated 2017-02 as not actionable.
Amount of time to read and assemble the commands from the last session.
creis@chromium.org
How often history navigations in subframes restore a different URL than the
frame's default src URL. This indicates how much users rely on subframe
session history items.
chrisha@chromium.org
The site engagement score associated with a tab restored by session restore,
recorded at the moment the tab is restored.
chrisha@chromium.org
The time since a restored tab was last active. This is the cumulative
amount of time that has passed since the tab was last visible. Time accrues
while a browser is active and the tab remains inactive. If the tab is
restored and remains inactive in a subsequent browsing session the time
continues to accrue. Visible tabs report a value of 0 for this. This is
recorded at the moment the tab is restored during a session restore.
creis@chromium.org
Records the length of unique names that include frame paths, for subframes
that are restoring a different URL than the frame's default src URL during a
history navigation. Large values here would indicate a possible challenge
for the plan to truncate frame unique names (to save memory).
Deprecated 2017-02 as not actionable.
Like SavePeriod, but specifically to provide a clearer breakdown of samples
in the 10 minutes - 8 hours range.
Deprecated 2017-02 as not actionable.
Amount of time between subsequent SessionService Save() operations (aka
updates to session data).
Periods longer than 10 minutes are grouped together; see SaveLongPeriod for
resolution.
dcheng@chromium.org
How often a subframe is assigned a new name between the initial empty
document and the first navigation.
chrisha@chromium.org
A breakdown of key events that occur to individual tabs as they are
processed by an ongoing session restore.
Deprecated 2017-02 as not actionable.
TabClosedPeriod, but specifically to provide a clearer breakdown of samples
in the 10 minutes - 8 hours range.
Deprecated 2017-02 as not actionable.
Milliseconds between subsequent Save() operations due to a tab being closed.
chrisha@chromium.org
The number of tabs involved in a single session restore event.
zhenw@chromium.org
The boolean indicates whether the tab load was initiated because a previous
tab load completed (including the tab was closed) or whether the tab load
was initiated because a timer fired to start the next load (true) during
session restore.
dmurph@chromium.org
Total size of the HTML5 SessionStorage browser-side cache purged in KB when
memory pressure signal was triggered or cache size hit the limits.
dmurph@chromium.org
Total size of the HTML5 SessionStorage databases in KB in the browser-side
cache. Recorded each time a new database is opened in memory.
dmurph@chromium.org
The result of an attempt to commit SessionStorage data to the database.
dmurph@chromium.org
The result of a failed attempt to open a LevelDB database for
SessionStorage.
dmurph@chromium.org
The result of a failed attempt to open a LevelDB database for SessionStorage
on disk.
dmurph@chromium.org
The result of a failed attempt to open a LevelDB database for SessionStorage
in memory.
dmurph@chromium.org
The result of attempting to delete the SessionStorage database.
dmurph@chromium.org
The reason opening a directory for the LevelDB database that backs
LocalStorage failed.
dmurph@chromium.org
The reason opening the LevelDB database that backs SessionStorage failed.
dmurph@chromium.org
The result of opening the LevelDB database that backs SessionStorage.
dmurph@chromium.org
The reason reading the namespaces metadata of the SessionStorage database
failed.
dmurph@chromium.org
The reason reading the next data map id metadata of the SessionStorage
database failed.
dmurph@chromium.org
The reason reading the schema version of the SessionStorage database failed.
cmumford@chromium.org
The result of a commit to the sessionStorage database.
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.
proberge@chromium.org
Whether generation of the RLZ deterministic machine-specific device id was
successful when creating the ProfilePrefStore.
stevenjb@chromium.org
The amount of time between the render frame host StartProvisionalLoad event
and the render frame DocumentOnLoadCompleted event for the settings page.
stevenjb@chromium.org
The amount of time between the render frame host StartProvisionalLoad event
and the render frame DocumentOnLoadCompleted event for the md-settings page.
stevenjb@chromium.org
The amount of time between the render frame host StartProvisionalLoad and
DidFinishDocumentLoad events for the settings page.
stevenjb@chromium.org
The amount of time between the render frame host StartProvisionalLoad and
DidFinishDocumentLoad events for the md-settings page.
Deprecated in Chrome 63, as we verified that machine id generation was not
flaky.
proberge@chromium.org
Whether generation of the deterministic machine-specific device id was
successful when initializing the PrefHashStore.
Deprecated in Chrome 54, as we stopped legacy migration of preferences.
csharp@chromium.org
gab@chromium.org
Whether, while loading a profile, any preference hashes were migrated from
Local State to either Preferences or Protected Preferences.
mpearson@chromium.org
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.
sammiequon@chromium.org
The users progress through the pin unlock setup wizard. Each type
corresponds to the user completeing a different stage of the setup wizard.
rkaplow@chromium.org
The amount of time that elapsed during RegisterProfilePrefs.
dschuyler@chromium.org
The number of characters typed in the chrome://settings page search box.
Intended to determine if we are making the user type too much to find what
they are looking for (the search is incremental).
dschuyler@chromium.org
If no matches are found when searching within the chrome://settings page,
record the length of the search text.
dschuyler@chromium.org
The number of search page hits within the chrome://settings page. This is
especially important when the count is zero (i.e. we returned no hits for a
given search in settings). A search is considered complete via timeout
since there is no concrete way to define the end of a search (the search is
incremental).
dschuyler@chromium.org
If there is no further activity in the search box for 1 second, this records
one tick each time a settings section is shown as a result of searching
withing the chrome://settings page. If multiple matches are found within
the same section, the section match is only recorded once.
dschuyler@chromium.org
The number of search subpage hits within the chrome://settings page. This
is different from Settings.SearchPageMatchCount in that it is tracking hits
in subpages rather than top level pages. See also
Settings.SearchPageMatchCount.
mpearson@chromium.org
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.
danielpark@chromium.org
If the home button is enabled or disabled at cold-start. This is only
recorded if the home page feature flag is enabled or the home button is
partner provided.
danielpark@chromium.org
The new state of the show home button preference after it is changed by the
user.
pmonette@chromium.org
The user clicked "Make Google Chrome the default browser" on the
settings page.
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.
Deprecated 12/2015.
mad@chromium.org
The startup URLs pref migration steps.
Deprecated 12/2015.
mad@chromium.org
The time elapsed in milliseconds in between startup URLs pref migration. A
value of 0 indicates that the last migration time was in the future due to
e.g. an incorrect system time.
dschuyler@chromium.org
The time between when the chrome://settings page is opened to the first time
a search is done within that page. This is intended to evaluate how long a
user looks for a setting before giving up and searching for it.
dbeam@chromium.org
The time until the settings Web UI is loaded, rendered, and interactive for
users (as in they can change a setting). Automatically logged each time the
settings page is opened (if not closed before interactive).
gab@chromium.org
The id of a tracked preference whose value has been changed since the last
time Chrome set it. Without a suffix, this histogram stands for preference
validation using MACs in the JSON pref files.
gab@chromium.org
The id of a tracked preference whose value has been cleared since the last
time Chrome set it. Without a suffix, this histogram stands for preference
validation using MACs in the JSON pref files.
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.
Without a suffix, this histogram stands for preference validation using MACs
in the JSON pref files.
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. Without a suffix, this histogram
stands for preference validation using MACs in the JSON pref files.
gab@chromium.org
The id of a tracked preference which was initialized despite the absence of
a MAC as its value was NULL. Without a suffix, this histogram stands for
preference validation using MACs in the JSON pref files.
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, inferring that this is a newly
tracked pref. Without a suffix, this histogram stands for preference
validation using MACs in the JSON pref files.
gab@chromium.org
The id of a tracked preference whose value has not changed since the last
time Chrome set it. Without a suffix, this histogram stands for preference
validation using MACs in the JSON pref files.
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.
Deprecated 2015-08-18.
wjmaclean@chromium.org
Tracks migration to per-partition zoom-level preferences during profile
initialization.
grt@chromium.org
Indicates whether or not the Windows Settings app monitor was initialized.
mad@chromium.org
Counts the number of times the user clicked on the No Thanks button of the
settings reset bubble before clicking on the Reset button in the same Chrome
session.
alito@chromium.org
Indicates if an error was detected in the settings reset prompt config data
while initializing the reset prompt configuration.
alito@chromium.org
The feature parameter determining the amount of time to wait after startup
before attempting to show the settings reset prompt. Logged once after
startup.
alito@chromium.org
Indicates whether the settings reset prompt dialog was shown to the user.
Deprecated on 2018-01-16.
alito@chromium.org
The number of extensions that were disabled after the user accepted the
settings reset prompt.
Deprecated on 2018-01-16.
alito@chromium.org
The number of extensions that will be disabled if the user accepts the
settings reset prompt. Logged once after startup.
alito@chromium.org
Indicates whether the user accepted the settings reset prompt.
alito@chromium.org
Indicates whether the settings reset prompt should be shown to the user
based on the state of the user's settings.
alito@chromium.org
Indicates whether the settings reset prompt is enabled for the user's
setting, or the reason for it being disabled. Logged once after startup.
alito@chromium.org
Indicates which settings were reset after the user accepted the settings
reset prompt.
alito@chromium.org
The time between the settings reset prompt dialog being shown and the user
accepting the prompt.
alito@chromium.org
The time between the settings reset prompt dialog being shown and the user
declining the prompt by clicking the cancel button.
Deprecated in M59 in April 2017 and replaced by
SettingsResetPrompt.TimeUntilCanceled and
SettingsResetPrompt.TimeUntilDismissed.
alito@chromium.org
The time between the settings reset prompt dialog being shown and the user
declining the prompt.
alito@chromium.org
The time between the settings reset prompt dialog being shown and the user
dismissing the prompt, for example by clicking on the 'x' in the dialog or
pressing the Escape key.
forshaw@chromium.org
True if the the installer successfully added AppContainer ACEs to the
application directory during installation and updating.
grt@chromium.org
The elapesed time to apply a patch to a previous version's chrome.7z archive
to generate a new chrome.7z archive. This histogram only applies to diff
updates.
grt@chromium.org
Hit following a successful install or update when the legacy
"app_host.exe" binary is deleted from the filesystem.
grt@chromium.org
Hit following a successful install or update when the legacy "app
launcher" Clients key is deleted from the registry.
grt@chromium.org
Hit following a successful install or update when the legacy
"binaries" Clients key is deleted from the registry.
grt@chromium.org
Hit following a successful install or update when the COM registration for
the legacy "IExecuteCommand" implementation class key is deleted
from the registry.
grt@chromium.org
Hit following a successful install or update when the legacy
"install-extension" app command is deleted from the registry.
grt@chromium.org
True if the chrome.packed.7z archive contains a patch (in which case a diff
update is taking place) or false if it contains a full archive (in which
case a new install or a full update is taking place).
zmin@chromium.org
Record the NTSTATUS code of unpacking the contents of a 7z file.
zmin@chromium.org
Record the status of unpacking the contents of a 7z file.
grt@chromium.org
Hit following a successful install or update when data from a legacy
multi-install Chrome Frame is deleted from the registry.
fdoray@chromium.org
Number of calls to DeleteOldVerions() made by a --delete-old-versions
process that didn't delete all files that belong to old versions of Chrome.
A --delete-old-versions process exits when another process tries to acquire
the SetupSingleton or after too many unsuccessful attempts to delete all old
files. A --delete-old-versions process that successfully acquires the
SetupSingleton records to either the
Setup.Install.NumDeleteOldVersionsAttemptsBeforeAbort histogram or the
Setup.Install.NumDeleteOldVersionsAttemptsBeforeSuccess histogram.
fdoray@chromium.org
Number of calls to DeleteOldVersions() made by a --delete-old-versions
process that successfully deleted all files that belong to old versions of
Chrome. A --delete-old-versions process that successfully acquires the
SetupSingleton records to either the
Setup.Install.NumDeleteOldVersionsAttemptsBeforeAbort histogram or the
Setup.Install.NumDeleteOldVersionsAttemptsBeforeSuccess histogram.
huangs@chromium.org
The peak page file usage by setup.exe in KB during install or uninstall
attempt.
huangs@chromium.org
The peak working set size of setup.exe in KB during install or uninstall
attempt.
grt@chromium.org
bcwhite@chromium.org
The final exit-result of the entire run of setup.exe on Windows.
fdoray@chromium.org
The result of trying to acquire a setup singleton. On Windows, a setup.exe
process must hold the setup singleton of a Chrome installation when it makes
changes to it.
grt@chromium.org
The disposition of a stranded Chrome install discovered while updating
multi-install Chrome Binaries. This metric is only logged in an edge case.
The buckets indicate whether or not the "stranded" Chrome install
has been used in the last 28 days. If so, it respresents a Chrome that has
not been updating due to a logic flaw in the installer and will be repaired
in the current update. If not, it likely represents Chrome Binaries that
were previously used by Chrome Frame that has since been uninstalled and
that will be uninstalled in a future update.
grt@chromium.org
The elapsed time to uncompress a chrome.7z patch. This histogram only
applies to diff updates.
grt@chromium.org
The elapsed time to uncompress a full chrome.7z archive. This histogram only
applies to new installs and to full updates.
grt@chromium.org
The elapsed time to unpack the uncompressed chrome.7z archive. This
histogram applies to all installs and updates.
erikchen@chromium.org
A histogram entry is emitted each time a base::SharedMemory object is
constructed. The value of the entry indicates the type of error encountered
during construction.
bcwhite@chromium.org
A histogram entry is emitted each time a base::SharedMemory object could not
be created due to a failed Windows system call. The value of the entry
indicates the result of the GetLastError() API call.
Deprecated 2015-06 because the Finch experiment SharedMemoryCreateStrategy
has finished running.
erikchen@chromium.org
The time spent making a new region of shared, anonymous memory. This metric
is not emitted if the shared memory region is read only.
Replaced with BrowserRenderProcessHost.KeepAliveDuration as of Aug 2017.
horo@chromium.org
A survival time of RenderProcessHostImpl for the In-renderer Shared Worker
from when FastShutdownIfPossible() is called.
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.
mpearson@chromium.org
The number of entries in shortcuts backend's database when initialized,
which happens during profile load.
davidben@chromium.org
The time it takes for the ShortcutsProvider to perform a query after the
user has typed N characters.
Replaced by Shutdown.browser_exit.time2 to get more resolution into the tail
of the distribution (10/2016).
hashimoto@chromium.org
Time for shutdown initiated by the browser exit menu command.
hashimoto@chromium.org
Time for shutdown initiated by the browser exit menu command.
hashimoto@chromium.org
Time for shutdown initiated by the browser exit menu command per renderer
process.
Replaced by Shutdown.end_session.time2 to get more resolution into the tail
of the distribution (10/2016).
hashimoto@chromium.org
Time for shutdown initiated by an end session (user logs off, shuts down or
reboots without explicitly exiting).
hashimoto@chromium.org
Time for shutdown initiated by an end session (user logs off, shuts down or
reboots without explicitly exiting).
hashimoto@chromium.org
Time for shutdown initiated by an end session (user logs off, shuts down or
reboots without explicitly exiting) per renderer process.
hashimoto@chromium.org
The number of renderer processes that couldn't be shutdown quickly due to
onbeforeunload or onunload listeners.
hashimoto@chromium.org
The number of renderer processes running when shutdown was called.
hashimoto@chromium.org
The type of the last shutdown.
Replaced by Shutdown.window_close.time2 to get more resolution into the tail
of the distribution (10/2016).
hashimoto@chromium.org
Time for shutdown initiated by the last browser window being closed.
hashimoto@chromium.org
Time for shutdown initiated by the last browser window being closed.
hashimoto@chromium.org
Time for shutdown initiated by the last browser window being closed per
renderer process.
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.
skym@chromium.org
There are two separate ways to test for account equality, using the account
id or the email. Historically the email was always used, but going forward
email will be modifiable. Now when we check account equality we use both
approaches and emit this metric to capture if they agreed or not.
bzanotti@chromium.org
Records the state of the account reconcilor when GAIA returns a specific
response.
mlerman@chromium.org
Track when chrome successfully adds an account. Failures are not tracked.
bsazonov@chromium.org
The time it takes to seed accounts before proceeding to the account
confirmation screen.
nyquist@chromium.org
The time it takes to retrieve the list of accounts from the system.
bsazonov@chromium.org
The time it takes to retrieve the list of accounts from the system on the UI
thread.
bsazonov@chromium.org
How long the "Waiting for Google Play Services to finish updating"
dialog is shown.
bsazonov@chromium.org
The time UI thread spent waiting for the list of accounts to be populated.
Removed this histogram since we have had newly designed histograms
Signin.SigninStartedAccessPoint, Signin.SigninCompletedAccessPoint, and
Signin.SigninReason.
guohui@chromium.org
Track how a user interfacts with the android signin promo.
zmin@chromium.org
Records the UI event when user clicks a locked profile on UserManager.
Please note that if the local reauth failed, UserManager might show Gaia
Reauth dialog.
mlerman@chromium.org
Log the type of GAIA authentication error that occur whenever the error
state changes.
droger@chromium.org
Logs the state of the Chrome account when the user signs out on the web.
This assumes that a logout of the web is always a complete logout of all the
web accounts (e.g. single session signout is not supported). TODO(droger):
make this histogram obsolete when Dice is launched.
skym@chromium.org
The relation between the account signed into chrome, and the account(s) in
the cookie jar. This metric is never recorded when not signed into chrome.
skym@chromium.org
The number of signed in accounts in the cookie jar.
skym@chromium.org
The number of signed out accounts in the cookie jar.
skym@chromium.org
The amount of time since the cookie jar last changed.
skym@chromium.org
The total number of accounts in the cookie jar.
Replaced by Signin.DiceMigrationStatus. Does not have any meaningful
information.
droger@chromium.org
Whether Dice is enabled for the current profile, recorded at startup.
droger@chromium.org
The Dice migration status, recorded at startup for each profile.
droger@chromium.org
Records Dice responses (signin and signout).
droger@chromium.org
Outcome of the token fetch in Dice signin.
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.
zmin@chromium.org
The number profile load events that needs a force-sign-in verification
request. It's recorded when profile is loaded with an authentication token
and force-sign-in policy is enabled.
zmin@chromium.org
Elapsed time of the force-sign-in verfication if it's finished. It includes
total network delay, retry delay and wait time due to no connection. The
verfication will not be recorded if it's not finished before profile is
signed out or removed from memory.
droger@chromium.org
Reason for invalid Gaia credentials. Recorded when Signin.AuthError records
invalid credentials.
skym@chromium.org
Records the general type of signin that is occuring in relation to previous
signin and local data.
skym@chromium.org
Current best guess if this device is shared between multiple users.
mlerman@chromium.org
Failure reason of ListAccounts call failure during account reconciliation,
Chrome OS login, or signin internals queries.
mlerman@chromium.org
Retry reason of failed ListAccounts call during Chrome OS login during
account reconciliation, Chrome OS login, or signin internals queries.
droger@chromium.org
Action taken for tokens being loaded from the token database, at Chrome
startup. Tokens can be either loaded into Chrome's token service or revoked.
mlerman@chromium.org
Reason fetching an OAuth2 Token failed. Available on all OSes.
mlerman@chromium.org
Reason fetching an OAuth2 Token is being retried. Available on all OSes.
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.
rogerta@chromium.org
Records the execution time of the account reconciler.
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.
Removed this histogram along with the code that was logging it.
pavely@chromium.org
Track when chrome successfully sends RefreshTokenAnnotationRequest.
droger@chromium.org
Tracks the progress of revocation requests for refresh tokens, and can be
used to check how many requests do not complete and why. Recorded for each
refresh token revocation request from the token service.
droger@chromium.org
Reports the status (including error details) of token revocation requests
after they complete.
mlerman@chromium.org
Track how many minutes of real time (not browser active time) elapsed
between profile signin and signout.
gogerald@chromium.org
Logs the original access point of each completed sign in.
gogerald@chromium.org
Logs the reason of each completed sign in.
Removed this histogram since we have had newly designed histograms
Signin.SigninStartedAccessPoint, Signin.SigninCompletedAccessPoint, and
Signin.SigninReason.
noms@chromium.org
Logs the original source that displayed the signin or reauth Gaia page,
before the page is displayed.
gogerald@chromium.org
Logs the original access point that displayed the signin or reauth Gaia
page, before the page is displayed.
skym@chromium.org
If the user chose to delete their profile or not when signing out of an
unmanaged account. When the user is not given a choice this metric is not
recorded.
mlerman@chromium.org
Track how a profile gets signed out.
bsazonov@chromium.org
Tracks the usage of different flows that switch sync accounts. Logged after
accounts have been switched.
droger@chromium.org
Tracks the changes of refresh token states for all accounts. Tokens can have
three states: Regular (retrieved from Gaia), Invalid (created by Chrome and
known to be invalid) or None (no token). Recorded when a token is loaded or
changed.
msarda@chromium.org
Counts how many times the SQL statements to get all tokens is valid.
msarda@chromium.org
Counts the results of loading a refresh token from the token database.
mlerman@chromium.org
Reason of failure to acquiring an ubertoken based on an already-minted
access token. Available on all OSes.
mlerman@chromium.org
Retry reason of failure to acquire an ubertoken based on an already-minted
access token. Available on all OSes.
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.
jkarlin@chromium.org
The size of the cache at the time that the index has finished initializing.
morlovich@chromium.org
Whether or not the CRC was checked at the moment when the last reference to
a read-only entry stream is closed.
morlovich@chromium.org
The time from the creation of the simple cache backend until the index has
been loaded from disk.
morlovich@chromium.org
The time from the creation of the simple cache backend until the index fails
to load.
morlovich@chromium.org
The time to close (write out footers and close the file) the cache entry on
disk. Includes only successful operations.
morlovich@chromium.org
The time to access (open for creation and write initial headers) the cache
entry on disk. Includes only successful operations.
morlovich@chromium.org
The time to remove the cache entry on disk. Includes only individually
doomed entries, not entries bulk-erased during eviction.
morlovich@chromium.org
The time to access (open and read headers from all files) the cache entry on
disk. Includes only successful operations.
morlovich@chromium.org
The time to open the stream 2 file successfully on disk cache entry open
with known key, when the size of payload is greater than 32 bytes.
morlovich@chromium.org
The time to open the stream 2 file successfully on disk cache entry open
with known key, when the size of payload is 32 bytes or less.
morlovich@chromium.org
The time to write a chunk to the cache entry on disk. Includes only
successful operations.
Removed 2018-02. Not creating stream 2 on CreateEntry entries is indeed a
good idea, since stream 2 writes are done on things opened with OpenEntry.
(Which also means this metric wasn't good at evaluating the prevalence of
stream 2 in general).
morlovich@chromium.org
Whether, upon creation of a new cache entry, the file for stream 2 was
omitted since that stream was empty.
morlovich@chromium.org
For entry creation operations that were sent to the disk, the result of
creation.
morlovich@chromium.org
The time, in ms, spent creating a new entry on disk.
morlovich@chromium.org
Whether, upon opening of an existing cache entry, stream 2 was empty and the
file for that stream was therefore removed.
morlovich@chromium.org
At the time that operations are run, the number of pending operations on a
particular entry.
Deprecated 2013 in favour of SimpleCache.Eviction.CacheSizeOnStart2
morlovich@chromium.org
The size of the cache at the beginning of an eviction.
morlovich@chromium.org
The size of the cache at the beginning of an eviction.
morlovich@chromium.org
The number of entries to be erased in an eviction.
Deprecated 2013 in favour of SimpleCache.Eviction.MaxCacheSizeOnStart2
morlovich@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
morlovich@chromium.org
The maximum allowed size of the cache at the beginning of an eviction.
morlovich@chromium.org
The result of an eviction.
Deprecated 2013 in favour of SimpleCache.Eviction.SizeOfEvicted2
morlovich@chromium.org
The number of bytes to be erased in an eviction.
morlovich@chromium.org
The amount of memory freed in an eviction.
Deprecated 2013 in favour of SimpleCache.Eviction.SizeWhenDone2
morlovich@chromium.org
The size of the cache after running an eviction.
morlovich@chromium.org
The size of the cache after running an eviction.
morlovich@chromium.org
Time spent completing an eviction.
morlovich@chromium.org
Time spent selecting entries for eviction.
morlovich@chromium.org
This even is emitted when SimpleCache is forced to either close some files
due to being over FD limit, or reopen files it had to close due to such
limit earlier.
morlovich@chromium.org
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.)
morlovich@chromium.org
The current limit of how many file descriptors a process can open. Emitted
each time the browser is launched, if the limit could be retrieved. (We can
raise this to the maximum limit if we like, without root access.)
morlovich@chromium.org
The result of trying to get the file descriptor limit. Emitted each time
the browser is launched.
morlovich@chromium.org
The number of open entries across all caches backed by the Simple Cache. An
entry is opened whenever a caller asks to open it to read or write cache
data, and remains open until the last caller asks to close it. Logged
whenever an entry is opened or closed.
morlovich@chromium.org
The size of the header stream of a Simple Cache entry, emitted every time
the headers are written or rewritten.
Removed 2018-06-05
morlovich@chromium.org
How the header size has changed in a Simple Cache entry, emitted every time
a write operation occurs on the header stream. (This includes the initial
write, rewrites, and other writes that we couldn't classify.)
Removed 2018-06-05
morlovich@chromium.org
The absolute size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
Removed 2018-06-05
morlovich@chromium.org
The relative size decrease of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a smaller size.
Removed 2018-06-05
morlovich@chromium.org
The absolute size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
Removed 2018-06-05
morlovich@chromium.org
The relative size increase of the header stream of a Simple Cache entry,
emitted every time the headers are rewritten with a larger size.
morlovich@chromium.org
For each index load, whether the index file was corrupt.
morlovich@chromium.org
The number of entries in a newly created index file.
morlovich@chromium.org
Number of entries loaded from the index file on start.
morlovich@chromium.org
Number of entries restored from disk when there was no index or the index
was corrupted.
morlovich@chromium.org
The state the index file is at when an attempt is made to load from it.
morlovich@chromium.org
At the time of index initialization, the number of enqueued jobs awaiting
index initialization.
morlovich@chromium.org
The method used to initialize the simple cache index.
morlovich@chromium.org
Time (as measured on the worker pool) spent loading the index file.
jkarlin@chromium.org
The number of entries in the index at the time that the index has finished
initializing.
morlovich@chromium.org
The number of entries written to the index on a flush.
morlovich@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.
morlovich@chromium.org
For each index load, whether the index file was stale.
morlovich@chromium.org
The interval between index saves, for apps in the background.
morlovich@chromium.org
The interval between index saves, for apps in the foreground.
morlovich@chromium.org
The reason an index was written to disk. Recorded every time an index is
saved.
morlovich@chromium.org
Recorded immediately after loading a fresh index (INDEX_STATE_FRESH or
INDEX_STATE_FRESH_CONCURRENT_UPDATES), the reason the loaded index was
written to disk.
Deprecated 2013-05 in favour of
SimpleCache.SimpleIndexWriteToDiskTime.Background and
SimpleCache.SimpleIndexWriteToDiskTime.Foreground.
morlovich@chromium.org
The amount of time spend writing the index file to disk, measured starting
at the beginning of the write on the callback thread, and calculated using
the completion time on the worker pool.
morlovich@chromium.org
The amount of time spend writing the index file to disk, for apps in the
background, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
morlovich@chromium.org
The amount of time spend writing the index file to disk, for apps in the
foreground, measured starting at the beginning of the write on the callback
thread, and calculated using the completion time on the worker pool.
Deprecated 2016-05 as the match checking was moved back into the entry
itself, so this result is now reported in the SimpleCache.x.SyncOpenResult
histograms.
morlovich@chromium.org
For each call to OpenEntry, whether the key on disk matched the request key.
Deprecated 2018-01; not viewed as actionable.
morlovich@chromium.org
For each file in the Simple Cache, the percentage of disk space used by the
cluster loss, the unused disk space in the last 4096 byte cluster of the
file.
Deprecated 2018-01; not viewed as actionable.
morlovich@chromium.org
For each file in the Simple Cache, the number of bytes in the last 4096 byte
cluster when the entry is saved to disk.
jkarlin@chromium.org
The maximum allowed size of the cache at the time that the index has
finished initializing.
morlovich@chromium.org
Number of operations that were queued behind a particular doom operation
(with a mass doom counting as a single operation).
morlovich@chromium.org
At the time that an entry is opened, the state of that entry in the index.
jkarlin@chromium.org
The fullness (in percent) of the cache at the time that the index has
finished initializing. The percentage is calculated as (cache_size * 100) /
max_cache_size.
morlovich@chromium.org
Delay between when the I/O portion of CreateEntry is enqueued and when its
execution begins.
morlovich@chromium.org
Delay between when the I/O portion of OpenEntry is enqueued and when its
execution begins.
morlovich@chromium.org
Delay between when an operation is deferred due to a pending doom for its
key, and when it can resume execution.
Removed 2018-07-02. See https://crrev.com/c/1122706
morlovich@chromium.org
For each Read operation, whether it could have been issued in parallel of a
previous Read operation.
morlovich@chromium.org
The outcome of Entry::ReadData in the simple cache.
morlovich@chromium.org
Whether a read from stream 1 (conventionally used for payload body) was
satisfied from prefetched data. Reported only on the first read operation on
the stream (including if there are multiple readers, or even some writers).
morlovich@chromium.org
Count of the number of entries recorded in the index, but not actually
present in the cache. Recorded each time a stale index is found and a
directory rescan is required.
morlovich@chromium.org
Count of the number of entries present in a cache, but not recorded in the
index. Recorded each time a stale index is found and a directory rescan is
required.
morlovich@chromium.org
The quality of a "stale" index compared to a full directory
rescan. Recorded immediately after every directory scan for stale indexes.
morlovich@chromium.org
For each EOFRecord found with a valid magic number, indicates if the record
also contains a CRC.
morlovich@chromium.org
The result, at the synchronous layer, of checking the EOF record of a cache
entry.
morlovich@chromium.org
The result, at the synchronous layer, of closing a cache entry.
morlovich@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
morlovich@chromium.org
The result, at the synchronous layer, reported when attempting to create a
new cache entry.
morlovich@chromium.org
The result of the the key SHA256 check done when opening stream 0 for each
entry.
morlovich@chromium.org
Whether an attempt was made to prefetch the entire file when executing
disk_cache::Backend::OpenEntry.
morlovich@chromium.org
The age of the entry (time since last modified), when opened at the
synchronous layer.
morlovich@chromium.org
The platform error reported when attempting to create a new cache entry at
the synchronous layer.
morlovich@chromium.org
The result, at the synchronous layer, reported when attempting to open a new
cache entry.
morlovich@chromium.org
The result, at the synchronous layer, of writing to a cache entry.
Removed 2018-07-02. See https://crrev.com/c/1122706
morlovich@chromium.org
Shows whether a write operation depends on the previous operation in queue
particularly in the aspect of its possibility to run in parallel.
Replaced 2013/09/03 by WriteResult2, which adds "fast empty
return", which previously showed up as "success".
morlovich@chromium.org
The outcome of Entry::WriteData in the simple cache.
morlovich@chromium.org
The outcome of Entry::WriteData in the simple cache.
alemate@chromium.org
Events in reqests processing of IP-based SimpleGeolocation.
skylarc@chromium.org
This boolean histogram counts SimpleGeolocationRequests carrying a nonzero
number of cell towers.
alemate@chromium.org
This boolean histogram counts SimpleGeolocationRequests carrying nonzero
number of WiFi access points.
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.
calamity@chromium.org
dominickn@chromium.org
The number of days between launches of an origin saved to homescreen or as a
bookmark app shortcut. Recorded at the second and each following launch of a
specific origin from a shortcut, independently per origin.
Removed in M60. See crbug.com/712493.
calamity@chromium.org
dominickn@chromium.org
felt@chromium.org
The percentage of total site engagement accumulated by this profile for
HTTPS URLs as a proportion of all engagement for HTTPS and HTTP URLs.
Recorded at startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter.
calamity@chromium.org
dominickn@chromium.org
Distribution of the engagement scores accumulated by a user, recorded at
startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter.
Removed in M60. See crbug.com/712493.
calamity@chromium.org
dominickn@chromium.org
felt@chromium.org
Distribution of the engagement scores accumulated by a user, recorded at
startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter. Limited specifically to
HTTP URLs.
Removed in M60. See crbug.com/712493.
calamity@chromium.org
dominickn@chromium.org
felt@chromium.org
Distribution of the engagement scores accumulated by a user, recorded at
startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter. Limited specifically to
HTTPS URLs.
charleszhao@chromium.org
dominickn@chromium.org
kcarattini@chromium.org
The distribution of zero versus non-zero engagement scores accumulated by
the user, recorded at the same time as
SiteEngagementService.EngagementScore.
calamity@chromium.org
The percentage of sites on a user's profile that have engagement scores that
fall in these buckets, recorded at startup per non-incognito profile, and
then upon the first engagement-increasing event every hour thereafter.
calamity@chromium.org
dominickn@chromium.org
The type of engagement (navigation, user input, etc.) which led to an
accumulation in site engagement.
calamity@chromium.org
dominickn@chromium.org
The mean site engagement per origin accumulated by this profile, recorded at
startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter.
calamity@chromium.org
dominickn@chromium.org
The median site engagement per origin accumulated by this profile, recorded
at startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter.
calamity@chromium.org
dominickn@chromium.org
The total number of origins with a non-zero site engagement score for this
profile, recorded at startup per non-incognito profile, and then upon the
first engagement-increasing event every hour thereafter.
calamity@chromium.org
dominickn@chromium.org
The number of origins which have reached the daily site engagement point
cap, recorded at startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter. Thus, each bin N contains
the number of clients where at least N origins have reached the maximum
daily site engagement point cap.
calamity@chromium.org
dominickn@chromium.org
The number of origins which have reached the absolute site engagement point
cap, recorded at startup per non-incognito profile, and then upon the first
engagement-increasing event every hour thereafter. Thus, each bin N contains
the number of clients where at least N origins have reached the maximum
absolute site engagement point cap.
calamity@chromium.org
dominickn@chromium.org
The percentage of all origins recorded by the site engagement service which
have reached the absolute site engagement point cap, recorded at startup per
non-incognito profile, and then upon the first engagement-increasing event
every hour thereafter.
calamity@chromium.org
dominickn@chromium.org
The site engagement score of an origin prior to applying decay. Recorded at
the first engagement event after decay, independently per decay event.
calamity@chromium.org
dominickn@chromium.org
The site engagement score of an origin once decay has occured. Recorded at
the first engagement event after decay, independently per decay event.
calamity@chromium.org
dominickn@chromium.org
The total site engagement accumulated by this profile, recorded at startup
per non-incognito profile, and then upon the first engagement-increasing
event every hour thereafter.
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.
alexmos@chromium.org
True if the --isolate-origins mode was enabled from the command line,
about:flags, or enterprise policy. Recorded on browser startup and then
once every 24 hours.
alexmos@chromium.org
True if the --site-per-process mode was enabled from the command line,
about:flags, or enterprise policy. Recorded on browser startup and then
once every 24 hours.
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.
nick@chromium.org
The upper bound of the predicted renderer process count if we isolated only
Chrome extensions, subject to the process limit. Recorded once per UMA
ping.
nick@chromium.org
The lower bound of the predicted renderer process count if we isolated only
Chrome extensions, subject to the process limit. Recorded once per UMA ping.
nick@chromium.org
The predicted renderer process count if we isolated only Chrome extensions
and if there were no process limit. Recorded once per UMA ping.
nick@chromium.org
The predicted total process count if we isolated only Chrome extensions,
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 upper bound of the estimated renderer process count if we isolated no
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 no
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 no sites and if there
were no process limit. Recorded once per UMA ping.
creis@chromium.org
The predicted total process count if we isolated no sites, subject to the
process limit. Recorded once per UMA ping.
alexmos@chromium.org
The number of currently enabled isolated origins. This includes origins
specified via the --isolate-origins command-line flag as well as those
configured via enterprise policy. Recorded on browser startup.
rsesek@chromium.org
The number of times a render process transitions its main thread isolate
into or out of memory savings mode. This is recorded per-renderer-process
upon the creation of the first main frame or the destruction of the last
main frame.
nasko@chromium.org
The count of all out-of-process iframes. Recorded once per UMA ping.
nick@chromium.org
The count of all RenderFrameProxyHosts. Recorded once per UMA ping.
nick@chromium.org
The count of RenderFrameProxyHosts in each BrowsingInstance. Recorded each
UMA ping, once per BrowsingInstance.
clamy@chromium.org
Whether SiteInstances with a ProcessReusePolicy of
REUSE_PENDING_OR_COMMITTED_SITE could reuse an existing RenderProcessHost or
they had to create a new one. True when they reused an existing process,
false when they created a new one.
nasko@chromium.org
The count of SiteInstances in a single BrowsingInstance. Recorded each UMA
ping, once per BrowsingInstance.
creis@chromium.org
Various actions related to cross-site document blocking in the browser
process, indicating whether the response was blocked from the renderer.
Recorded as the response is processed in the network stack.
creis@chromium.org
The total count of responses that were blocked by the cross-site document
blocking logic in the browser process. Sampled with a resource type (0-17)
when the response is blocked; up to 1024 bytes of the response are
considered. This is also recorded with a suffix indicating the MIME type
category.
creis@chromium.org
For each responses blocked by the cross-site document blocking logic in the
browser process, logs network::ResourceResponseInfo::content_length of the
response (but only if the content length value was available - if the value
was not -1).
creis@chromium.org
For each responses blocked by the cross-site document blocking logic in the
browser process, logs whether network::ResourceResponseInfo::content_length
was available (i.e. value was 0 or greated) or not available (i.e. value was
equal to -1) if the value was available (i.e. the value was not -1).
creis@chromium.org
The total count of responses that were blocked by the cross-site document
blocking logic in the browser process, due to the presence of a Javascript
parser-breaker pattern (like "for(;;);", or ")]}'", or a
non-empty JSON dictionary like "{\"a\":". Sampled with a
resource type (0-17) when the response is blocked; up to 1024 bytes of the
response are considered.
creis@chromium.org
The number of bytes of the network response buffered for sniffing purposes,
when attempting to sniff the response to determine if it should be blocked
as a cross-site document. Recorded after sniffing is attempted.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The number of bytes in the first network packet for a response with headers
that imply potential illegal cross-site access. Recorded when the first
network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of blocked cross-site document responses due to having HTML
content type header and contents sniffed as HTML. Sampled with value of 1
when the first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their HTML contents. Sampled with value
1 when the first network packet of a response of this type is received.
Superseded by SiteIsolation.XSD.HTML.Blocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.) among blocked
cross-site document responses due to their HTML contents. Sampled with a
resource type (0-14) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.) among blocked
cross-site document responses due to their HTML contents. Sampled with a
resource type (0-17) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having HTML content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
Superseded by SiteIsolation.XSD.HTML.NoSniffBlocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having HTML content type and nosniff
headers. Sampled with a resource type (0-14) when the first network packet
of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having HTML content type and nosniff
headers. Sampled with a resource type (0-17) when the first network packet
of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of not blocked responses despite having an HTML content type
header due to the failure of content sniffing. Sampled with value 1 when the
first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses. Sampled with value 1 when the first network packet of a response
of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of blocked cross-site document responses due to having JSON
content type header and contents sniffed as JSON. Sampled with value 1 when
the first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their JSON contents. Sampled with value
1 when the first network packet of a response of this type is received.
Superseded by SiteIsolation.XSD.JSON.Blocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their JSON contents. Sampled with a
resource type (0-14) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their JSON contents. Sampled with a
resource type (0-17) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having JSON content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
Superseded by SiteIsolation.XSD.JSON.NoSniffBlocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having JSON content type and nosniff
headers. Sampled with a resource type (0-14) when the first network packet
of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having JSON content type and nosniff
headers. Sampled with a resource type (0-17) when the first network packet
of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of not blocked responses despite having an JSON content type
header due to the failure of content sniffing. Sampled with value 1 when the
first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses with a JSON content type header. Sampled with value 1 when the
first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
MIME type codes for content type header values of potentially cross-site
document responses, excluding same-site or not http(s) urls. Sampled with a
MIME type code (0-4) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of blocked cross-site document responses due to having Plain
content type header and contents sniffed as HTML. Sampled with value 1 when
the first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
responses due to their Plain.HTML contents. Sampled with value 1 when the
first network packet of a response of this type is received.
Superseded by SiteIsolation.XSD.Plain.HTML.Blocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.HTML contents. Sampled with
a resource type (0-14) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.HTML contents. Sampled with
a resource type (0-17) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of blocked cross-site document responses due to having Plain
content type header and contents sniffed as JSON. Sampled with value 1 when
the first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their Plain.JSON contents. Sampled with
value 1 when the first network packet of a response of this type is
received.
Superseded by SiteIsolation.XSD.Plain.JSON.Blocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.JSON contents. Sampled with
a resource type (0-14) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.JSON contents. Sampled with
a resource type (0-17) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having Plain content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
Superseded by SiteIsolation.XSD.Plain.NoSniffBlocked.RenderableStatusCode2
in December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having Plain content type and nosniff
header. Sampled with a resource type (0-14) when the first network packet of
a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having Plain content type and nosniff
header. Sampled with a resource type (0-17) when the first network packet of
a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of not blocked responses despite having an Plain content type
header due to the failure of content sniffing. Sampled with value 1 when the
first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses with a Plain content type header. Sampled with value 1 when the
first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of blocked cross-site document responses due to having Plain
content type header and contents sniffed as XML. Sampled with value 1 when
the first network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to their Plain.XML contents. Sampled with
value 1 when the first network packet of a response of this type is
received.
Superseded by SiteIsolation.XSD.Plain.XML.Blocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with renderable HTTP status codes sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.XML contents. Sampled with
a resource type (0-14) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with renderable HTTP status codes sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their Plain.XML contents. Sampled with
a resource type (0-17) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of blocked cross-site document responses due to having XML content
type header and contents sniffed as XML. Sampled with value 1 when the first
network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with nonrenderable HTTP status codes among blocked
cross-site document responses due to their XML contents. Sampled with value
1 when the first network packet of a response of this type is received.
Superseded by SiteIsolation.XSD.XML.Blocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with renderable HTTP status codes sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their XML contents. Sampled with a
resource type (0-14) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with renderable HTTP status codes sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to their XML contents. Sampled with a
resource type (0-17) when the first network packet of a response of this
type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a nonrenderable HTTP status code among blocked
cross-site document responses due to having XML content type and nosniff
headers. Sampled with value 1 when the first network packet of a response of
this type is received.
Superseded by SiteIsolation.XSD.XML.NoSniffBlocked.RenderableStatusCode2 in
December 2015.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having XML content type and nosniff
headers. Sampled with a resource type (0-14) when the first network packet
of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses with a renderable HTTP status code sub-categorized by
their requesting context type (e.g., image, script, etc.), among blocked
cross-site document responses due to having XML content type and nosniff
headers. Sampled with a resource type (0-17) when the first network packet
of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of not blocked responses despite having an XML content type header
due to the failure of content sniffing. Sampled with value 1 when the first
network packet of a response of this type is received.
Removed in March 2018; in M67+, browser-process CORB policy is enabled.
creis@chromium.org
The count of responses that may be parsed as JavaScript among not blocked
responses with an XML content type. Sampled with value 1 when the first
network packet of a response of this type is received.
ericrk@chromium.org
The scale factor of any images drawn by Skia.
ericrk@chromium.org
Whether a call to drawBitmap(Rect) or drawImage(Rect) used the tiled or
non-tiled rasterization path.
ericrk@chromium.org
The count of images drawn by Skia with a given filter quality.
ericrk@chromium.org
The path taken by Skia when it attempts to lock a texture for use.
jhawkins@chromium.org
A count of the number of eligible SmartLock devices which can be used to
unlock the user's Chromebook. Logged each time the list of eligible devices
is updated. TODO(jhawkins): Log this again once we send this data from
eligible phones.
jhawkins@chromium.org
A count of the number of SmartLock devices which the user has enabled to
unlock the user's Chromebook, i.e., the device connected to in the SmartLock
setup flow. Logged each time the list of eligible devices is updated.
jhawkins@chromium.org
The state of the SmartLock feature for the current user, set at login. The
value is 'enabled' if the user has successfully enabled SmartLock via setup,
disabled if the user has explicitly disabled the feature after it has been
enabled, and unset if the feature is passively disabled, i.e., has never
been enabled by the user.
jhawkins@chromium.org
The number of times the user actively enabled or disabled the SmartLock
feature via Settings.
jhawkins@chromium.org
The result of the operation to disable SmartLock.
ianwen@chromium.org
Records how many times a particular snackbar was shown to the user.
alito@chromium.org
The time between sending the user's response to the Chrome Cleaner process
and the Cleaner process terminating. This histogram is logged only for
successfully completed runs of the cleaner.
ftirelo@chromium.org
The final status of the Chrome Cleanup Tool run (e.g. succeeded, failed,
reboot required).
Deprecated as of 09/2017. Replaced with
SoftwareReporter.Cleaner.DownloadStatusErrorCode.
ftirelo@chromium.org
The HTTP response code for the Chrome Cleanup Tool download request.
ftirelo@chromium.org
An indication if an attempt to download the Chrome Cleanup Tool succeeded or
the reason why it failed.
ftirelo@chromium.org
The HTTP response or net error code when trying to download the Chrome
Cleanup Tool.
mad@chromium.org
The state of software reporter cleaner tool runs. A value of "Not
Completed" can mean either the tool crashed, or the tool was still
running when Chrome checked.
mad@chromium.org
Whether a reboot happened since the software reporter cleaner tool has
finished execution with a pre-reboot exit code.
Deprecated on 2018-01-15.
ftirelo@chromium.org
The number of attempts to download the Chrome Cleanup tool until it either
succeeds or fails.
veranika@chromium.org
Indicates how the user was prompted to reboot the machine to complete a run
of the Chrome Cleanup Tool.
ftirelo@chromium.org
Indicates that the user accepted to initiate a reboot to complete a run of
the Chrome Cleanup Tool. This is logged the user starts a reboot from the
cleanup card in the Settings page. We can't track when the reboot is not
initiated, because it can happen at any moment in the future (there is no
prompt blocking the user).
mad@chromium.org
How long it took to run the software reporter cleaner tool.
alito@chromium.org
The time between launching the Chrome Cleaner process and the cleaner having
scanned the user's machine and Chrome receiving an IPC call with the
results.
ftirelo@chromium.org
Indicates if the Settings page was the active tab once a cleanup finished
with reboot required.
ftirelo@chromium.org
The time between the first attempt to download the Chrome Cleanup tool and a
successful download or the last unsuccessful attempt to download without
retrying.
mad@chromium.org
The build version of the software reporter cleaner tool.
ftirelo@chromium.org
Whether the user accepted to upload logs from Chrome Cleanup Tool. This is
logged when the user accepts the Chrome prompt to start a cleanup either
from the prompt dialog or from the cleanup card in the Settings page.
ftirelo@chromium.org
Whether the Chrome Cleanup Tool card in the Settings page has been shown.
ftirelo@chromium.org
Indicates where the user started a cleanup from (e.g. from the prompt dialog
or the settings page).
joenotcharles@chromium.org
Whether a configuration error prevented the experimental Software Reporter
from running.
mad@chromium.org
Whether there was an error reading the registry key containing UwS found by
the Software Removal Tool.
ftirelo@chromium.org
Indicates when the IPC with the Chrome Cleanup Tool process is disconnected
from Chrome. Success is logged when it's disconnected and no longer needed
(the user already responded to the prompt in Chrome or the cleaner process
terminated normally); failures are logged when the IPC is disconnected, but
communication between Chrome and the cleaner process is still required (e.g.
while Chrome is waiting for scanning results or when the cleaner is waiting
for the user's response from Chrome).
mad@chromium.org
The result of the most recent SRT log upload.
ftirelo@chromium.org
If logs uploads are enabled in the Software Reporter or the reason why it is
disabled. Recorded before each run of the Software Reporter.
ftirelo@chromium.org
The result of the most recent Software Reporter logs upload. Written by the
Software Reporter in the registry and sent by Chrome after the reporter
finishes.
ftirelo@chromium.org
Error encountered when reading the software reporter logs upload result from
the registry.
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.
alito@chromium.org
The memory used by the software reporter tool as reported by the tool itself
via the registry. Logged just after the software reporter tool has finished.
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.
ftirelo@chromium.org
The reason why the user has not been prompted to run the Chrome Cleanup Tool
(e.g. no unwanted software found, user recently prompted).
ftirelo@chromium.org
The number of files to be deleted by the Chrome Cleanup Tool.
ftirelo@chromium.org
Whether an on-demand update of the Software Reporter component was needed
for a user-initiated cleanup.
ftirelo@chromium.org
Whether an on-demand update of the Software Reporter component succeeded,
when needed for a user-initiated cleanup.
ftirelo@chromium.org
The number of profiles whose settings will be reset once a successful
cleanup completes.
alito@chromium.org
The time between the Chrome Cleaner dialog being shown and the dialog being
closed.
ftirelo@chromium.org
The user response on the modal Chrome Cleanup Tool prompt dialog (e.g.
accepted, cancelled).
Replaced 2017-08-01 with SoftwareReporter.PromptShownWithType.
ftirelo@chromium.org
Whether the user has been prompted to run the Chrome Cleanup Tool.
ftirelo@chromium.org
Whether the user has been prompted to run the Chrome Cleanup Tool and which
type of prompt has been shown.
This is logged once a prompt is presented to the user.
Deprecated as of 2017-11-01. Replaced with
SoftwareReporter.PromptDialogResponse.
mad@chromium.org
Usage of the Software Removal Tool (SRT) Prompt.
ftirelo@chromium.org
Indicates the result of a reporter sequence once it ends.
ftirelo@chromium.org
Indicates the type of a reporter sequence run on the user system. Logged
when the sequence is scheduled to start.
alito@chromium.org
The amount of time it took to run the software reporter tool as reported by
the tool itself via the registry. Logged just after the software reporter
tool has finished.
alito@chromium.org
The amount of time it took for the software reporter to run as measured by
chrome. Logged just after the software reporter tool has finished.
alito@chromium.org
Error encountered when reading the software reporter tool's start and end
times from the registry.
ftirelo@chromium.org
Whether the user accepted to upload scanner logs from Chrome Cleanup Tool.
This is logged when the user starts a scan for the Settings page and is only
logged for user-initiated cleanups.
mad@chromium.org
The registration and execution steps for the software reporter.
ftirelo@chromium.org
Registers when a profile is tagged for settings reset before a run of the
Chrome Cleanup Tool.
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.
ianwen@chromium.org
Records how users interact with the special locale promotion dialog.
timvolodine@chromium.org
Whether the Android spellchecking service was available at the start of a
new spellchecking session. Note that the user can disable the Android
spellchecking service in settings, in which case it will show up as not
available in the histogram.
timvolodine@chromium.org
Measures the amount of time it takes to receive results from the
spellchecking service on Android. More precisely this is the
SystemClock.elapsedRealtime() between the
SpellCheckerSession.getSentenceSuggestions() and the invocation of the
onGetSentenceSuggestions() callback.
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
Record times for INSERT/UPDATE/DELETE statements run outside of an explicit
transaction.
shess@chromium.org
Error which prevented database close.
shess@chromium.org
Record time spent in explicit COMMIT statements.
Moved to Sqlite.Error.Cookie in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the cookie db.
Moved to Sqlite.Error.DatabaseTracker in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the websqldb tracker db.
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
SQLite memory footprint from sqlite3_memory_used() recorded 1 day after
first database is opened by sql::Connection.
shess@chromium.org
SQLite memory footprint from sqlite3_memory_used() recorded 1 hour after
first database is opened by sql::Connection.
shess@chromium.org
SQLite memory footprint from sqlite3_memory_used() recorded 1 week after
first database is opened by sql::Connection.
shess@chromium.org
SQLite memory footprint from sqlite3_memory_used() recorded 10 minutes after
first database is opened by sql::Connection.
shess@chromium.org
Time used to migrate History database schema to a new version.
shess@chromium.org
Error which prevented database open.
shess@chromium.org
Error from first read of the database.
shess@chromium.org
Record times for all statements run against the database.
Moved to Sqlite.Error.Quota in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the quota db.
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
SQLite error code from failed ATTACH in sql::Recovery::Init().
shess@chromium.org
Records specific failure and success cases in sql::Recovery implementation,
to determine which cases warrant further development. This histogram tracks
detected errors, some of which may cause multiple results. See recovery.cc
for details.
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.
shess@chromium.org
Stats for different API calls in sql/.
Moved to Sqlite.Error.Text in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the full text db.
Moved to Sqlite.Error.Thumbnail in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite for the thumbnail db.
shess@chromium.org
Record times for statements which could update the database file. Includes
commit and autocommit time.
shess@chromium.org
Version of pre-existing database at startup.
Removed 2018/02/06.
shess@chromium.org
Buffer sizes passed to browser-process SQLite VFS functions.
Removed 2018/02/06.
shess@chromium.org
I/O operations measured by browser-process SQLite VFS wrapper.
Moved to Sqlite.Error.Web in M-27.
Please list the metric's owners. Add more owner tags as needed.
Error codes returned by sqlite the web db.
Removed 07/2017. Reference: crbug.com/708041
jww@chromium.org
When resources are checked for mismatching integrity and whether the
mismatch forces a refetch.
carlosil@chromium.org
When the "Learn more" link on an SSL interstitial is clicked, this
histogram records if the navigation succeded, if it failed with an
interstitial, or if it failed with a different error.
meacer@chromium.org
Users can opt in to send reports of certificate validation errors to Google.
This records the outcome whenever Chrome sends such a report.
Some certificate validation reports might not be received because proxies,
firewalls or other content filters might filter report uploads.
estark@chromium.org
Users can opt in to send reports of certificate validation errors to Google.
This records the error code whenever Chrome fails to send such a report.
Deprecated as of 07/2016. Replaced with SSL.ExpectCTReportFailure2.
estark@chromium.org
Sites can opt in to Expect CT, a reporting feature that sends a report
whenever a TLS connection does not have valid Certificate Transparency
information associated with it. This records the error code when Chrome
fails to send an Expect CT report.
estark@chromium.org
Sites can opt in to Expect CT, a reporting feature that sends a report
whenever a TLS connection does not have valid Certificate Transparency
information associated with it. This records the error code when Chrome
fails to send an Expect CT report.
estark@chromium.org
Sites can opt in to Expect CT, a reporting feature that sends a report
whenever a TLS connection does not have valid Certificate Transparency
information associated with it. This metric fires whenever Chrome attempts
to send an Expect CT report.
estark@chromium.org
Keeps track of various insecure content events, such as loading an HTTP
script from an HTTPS page.
Deprecated December 2017 (M65). This information in this histogram can be
found in LoginCustomFlags (for users who have set a flag) or by filtering to
users with the MarkHttpAs feature enabled (for seeing the field trial
breakdown).
estark@chromium.org
felt@chromium.org
Reports whether the user has selected to mark HTTP origins with an
experimental UI treatment (such as showing a warning on HTTP pages that
collect sensitive information). This histogram is recorded whenever the
security level (the overall security state of a page, roughly corresponding
to the lock icon) is computed for an HTTP page.
Deprecated 09/2016 and replaced with SSL.MarkHttpAsStatus.
palmer@chromium.org
Reports whether the user has selected to mark non-secure origins as Neutral
(the status quo), Dubious, or Non-Secure.
msarda@chromium.org
Number of accounts available for Single Sign On with the current device,
recorded at the time the SSO Promo is shown.
msarda@chromium.org
Action the user takes when the Single Sign On promotion is shown.
msarda@chromium.org
Number of times the promotion has been seen on the current device.
Deprecated in M60. Roughly 50% of Chrome startups that had *any* pending
minidumps had at least one pending minidump without any logcat output. About
5% had multiple minidumps without any logcat output.
isherman@chromium.org
The number of un-uploaded minidumps present in the Android Crash Reports
directory. Each minidump file (should) correspond to a crash. This is
recorded on startup, just prior to initiating uploading for these minidumps.
This is intended as a temporary metric, to be removed around M60:
http://crbug.com/699785
Deprecated in M60. Roughly 50% of Chrome startups that had *any* pending
minidumps had at least one pending minidump without any logcat output. About
5% had multiple minidumps without any logcat output.
isherman@chromium.org
The number of un-uploaded minidumps present in the Android Crash Reports
directory that do not yet have logcat output attached. Each minidump file
(should) correspond to a crash. This is recorded on startup, just prior to
initiating uploading for all pending minidumps. This is intended as a
temporary metric, to be removed around M60: http://crbug.com/699785
boliu@chromium.org
Individual enum counts specific conditions of child process terminations.
There are too many individual states to enumerate into a single histogram,
so this effectively does the aggregration that normally happens on the
server side in the client instead. The benefit is this is easily extensible
in the future, and downside is that it does not allow additional server side
analysis. Note a single child process termination may fall into multiple
enums.
wnwen@chromium.org
Counts renderer crashes including OOMs. Android only. Mirrors old stability
proto renderer crashes.
boliu@chromium.org
ssid@chromium.org
Record the state of child service bindings left when a child service with
strong binding is OOM killed by Android. Recorded when such a OOM kill is
detected by browser. Note this does not distinguish process type, and is for
example recorded for both GPU and renderer process.
nick@chromium.org
jamescook@chromium.org
Count of processes killed by chrome/browser because they sent an IPC that
couldn't be properly handled. Categories are the reasons (code locations)
for the kills.
jam@chromium.org
jamescook@chromium.org
Count of child processes killed because they sent an IPC that couldn't be
properly handled. Categories are the reasons (code locations) for the kills.
jamescook@chromium.org
Count of extension processes killed because they sent an IPC that couldn't
be properly handled. Categories are the reasons (code locations) for the
kills.
mcnee@chromium.org
nick@chromium.org
Count of processes killed because they sent a bad IPC that couldn't be
properly handled. Categories are the reasons (code locations) for the kills.
nick@chromium.org
jamescook@chromium.org
Count of processes killed because they sent a NaCl IPC that couldn't be
properly handled. Categories are the reasons (code locations) for the kills.
nick@chromium.org
jamescook@chromium.org
Count of processes killed because they sent a bad IPC that couldn't be
properly handled. Categories are the reasons (code locations) for the kills.
siggi@chromium.org
Records the exit code of the browser process (on Windows) from the previous
launch. On crash, the exit code will indicate the exception code of the
crash. This is emitted in stability data with the first report on a
subsequent launch. Note: Due to https://crbug.com/805754, the enum labels
for RESULT_CODE_* are off by 1 for M56 and earlier.
boliu@chromium.org
lfg@chromium.org
lukasza@chromium.org
Logged after detecting that a sad subframe is shown (logged at most once per
crash).
lukasza@chromium.org
The age of a crashed extension process. Not logged on iOS. Logged together
with CrashExitCodes.Extension.
lukasza@chromium.org
The age of a crashed extension process. Not logged on iOS. Logged together
with CrashExitCodes.Renderer.
siggi@chromium.org
Temporary instrumentation to record the Windows browser's exit path. See
http://crbug.com/412384.
manzagop@chromium.org
Number of times stability data was discarded. This is accumulated since the
last report, even across versions. This is logged during stability metric
recording for the following log sent.
manzagop@chromium.org
Number of times the initial stability log upload was deferred to the next
startup. This is logged during stability metric recording for the following
log sent.
siggi@chromium.org
Number of times a browser crash was detected, where the browser was last
known to be alive in a Windows system session that terminated abnormally.
manzagop@chromium.org
Number of times the version number stored in prefs did not match the
serialized system profile version number. This is logged during stability
metric recording.
lpromero@chromium.org
olivierrobin@chromium.org
Type of the shutdown. This histogram is recorded at startup and logs a
sample for the previous session. A clean shutdown is one where the app
enters the background before being killed. Other shutdowns are all some sort
of crash. The absence of a crash log indicates that the app was killed by
the OS, normally due to memory pressure. If memory pressure is extremely
high, the app may not have had a chance to response to a memory warning
before being killed. For first launch after upgrade, the crash reports may
be discarded before this histogram is written to so it's not possible to
determine if there's a valid crash log present or not.
dtapuska@chromium.org
If the renderer is considered unresponsive from the browser's perspective
before the process is terminated. This metric is being used to figure out
crash reports that have all idle threads and perhaps the process is being
terminated when it shouldn't be. crbug.com/615090.
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.
ianwen@chromium.org
Logs a UI location from which a bookmark is launched.
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.
pasko@chromium.org
alexilin@chromium.org
Android: The time from the activity creation point to the first contentful
paint of the first loaded page. It's not recorded when the first loaded page
is non http(s) page like a chrome error page, a new tab page, a blank page.
It's also not recorded if the application wasn't in the foreground since the
start till the end of event.
pasko@chromium.org
alexilin@chromium.org
Android: The time from the activity creation point to the moment the first
navigation is committed, i.e. when renderer gets the first byte of the
document. It's not recorded when the first loaded page is non http(s) page
like a chrome error page, a new tab page, a blank page. It's also not
recorded if the application wasn't in the foreground since the start till
the end of event.
This metric was deprecated in M68 in favour of
"Startup.Android.Cold.TimeToFirstContentfulPaint.Tabbed". It has
moved out of experimental and records a smaller range of numbers (medium
times instead of long times). The ".Tabbed" suffix is added since
the histogram is being tracked for WebApkActivity using the
".WebApk" suffix.
pasko@chromium.org
alexilin@chromium.org
Android: The time from the activity creation point to the first contentful
paint of the first loaded page. It's not recorded when the first loaded page
is non http(s) page like a chrome error page, a new tab page, a blank page.
It's also not recorded if the application wasn't in the foreground since the
start till the end of event.
This metric was deprecated in M68 in favour of
"Startup.Android.Cold.TimeToFirstNavigationCommit.Tabbed". It has
moved out of experimental and records a smaller range of numbers (medium
times instead of long times). The ".Tabbed" suffix is added since
the histogram is being tracked for WebApkActivity using the
".WebApk" suffix.
pasko@chromium.org
alexilin@chromium.org
Android: The time from the activity creation point to the moment the first
navigation is committed, i.e. when renderer gets the first byte of the
document. It's not recorded when the first loaded page is non http(s) page
like a chrome error page, a new tab page, a blank page. It's also not
recorded if the application wasn't in the foreground since the start till
the end of event.
Deprecated 03/2018 with Mash AppList refactoring.
tapted@chromium.org
Time for a newly created browser process to perform the first paint of the
app launcher, when started with the --show-app-list flag and with no
currently running Chrome processes.
Deprecated 03/2018 with Mash AppList refactoring.
tapted@chromium.org
Time for a running browser process to perform the first paint of the app
launcher. Measured from the time a second Chrome process started, which sent
its --show-app-list command line argument to the already-running process and
will soon exit.
crashpad-dev@chromium.org
The amount of time that elapsed during in
crash_report::BlockUntilHandlerStarted().
johnme@chromium.org
Records the cause, each time Chrome is brought to the foreground. Currently
only checks if a NotificationUIManager notification was shown in the last 5
seconds (includes Web Notifications, but not media or Cast).
rkaplow@chromium.org
Measured when Chrome is invoked, this counts the number of URLs passed via
command line. Note that this handles the case of a URL passed to Chrome
starting up, or when a running Chrome is given the message to open a new
URL.
robliao@chromium.org
The amount of time that elapsed during BrowserMainRunnerImpl::Initialize.
robliao@chromium.org
The amount of time that elapsed during the first section of
BrowserMainRunnerImpl::Initialize.
robliao@chromium.org
The amount of time that elapsed during the second section of
BrowserMainRunnerImpl::Initialize.
fdoray@chromium.org
Time from the ChromeMain() entry in the browser process to the first
RendererMain() entry.
Removed 2/2018, as MessageLoopStart is after MainNavigationStart with
browser-side navigation.
asvitkine@chromium.org
Time between Startup.BrowserMessageLoopStartTime and
Startup.FirstWebContents.MainNavigationStart. Recorded explicitly to allow
easy breakdown of Startup.FirstWebContents.MainNavigationStart when
diagnosing issues.
asvitkine@chromium.org
Time between Startup.BrowserMessageLoopStartTime and
Startup.FirstWebContents.NonEmptyPaint2. Recorded explicitly to allow easy
breakdown of Startup.FirstWebContents.NonEmptyPaint2 when diagnosing issues.
chrisha@chromium.org
fdoray@chromium.org
The number of hard faults incurred in the browser process from startup to
start of the main thread's message loop, not including first runs of the
browser. This is only reported on Windows 7 and greater.
Removed 1/2016.
chrisha@chromium.org
The number of hard faults incurred in the browser process from startup to
start of the main thread's message loop on first run. This is only reported
on Windows 7 and greater.
Deprecated 12/2015. No longer tracked because values collected on stable
show that the function pretty much never fails (succeeds 99.9996% of the
time).
chrisha@chromium.org
fdoray@chromium.org
If OS support was detected (Windows 7 and greater) indicates whether it was
possible to determine the number of hard faults that have occurred in the
process from startup to start of the main thread's message loop. This can
fail because the underlying call is inherently racy.
fdoray@chromium.org
Time from browser startup to the start of the main thread's message loop.
Deprecated 12/2016. crbug.com/634408
fdoray@chromium.org
gab@chromium.org
Time from main entry to the start of the main thread's message loop. This
stat is only recorded after 7 minutes of OS uptime to try to mitigate the
variance resulting from Chrome being autostarted. Replaced with
Startup.BrowserMessageLoopStartTimeFromMainEntry2 which is recorded all the
time.
Deprecated 12/2016. crbug.com/634408
fdoray@chromium.org
gab@chromium.org
Time from main entry to the start of the main thread's message loop on first
run. This stat is only recorded after 7 minutes of OS uptime to try to
mitigate the variance resulting from Chrome being autostarted. Replaced with
Startup.BrowserMessageLoopStartTimeFromMainEntry.FirstRun2 which is recorded
all the time.
fdoray@chromium.org
gab@chromium.org
Time from main entry to the start of the main thread's message loop on first
run.
Deprecated 2018-01 in favor of
Startup.BrowserMessageLoopStartTimeFromMainEntry3 which does not involve a
conversion from Time to TimeTicks.
fdoray@chromium.org
gab@chromium.org
Time from main entry to the start of the main thread's message loop.
fdoray@chromium.org
gab@chromium.org
Time from main entry to the start of the main thread's message loop.
fdoray@chromium.org
Time taken to open the initial tab or to restore tabs from previous session.
rkaplow@chromium.org
The amount of time that elapsed during
BrowserProcessImpl::PreMainMessageLoopRun.
mblsha@yandex-team.ru
Time from browser startup to the time the first Browser window has finished
painting its children.
mblsha@yandex-team.ru
Time from browser startup to the time the GPU has finished compositing after
first Browser window has finished painting its children. At this point the
Browser interface is visible on screen. Measures how much time does it take
for GPU to actually paint the first time.
fdoray@chromium.org
Time from browser startup to the time the browser window initially becomes
visible.
Deprecated 7/2015. To be replaced with Cast events.
jeremy@chromium.org
The elapsed time from the ChromeCast application launch to the first video
frame displayed.
jif@chromium.org
The duration of all initializations in a cold start triggered by an external
URL.
jif@chromium.org
The duration of all initializations in a cold start not triggered by an
external URL.
fdoray@chromium.org
How long it takes to load the original profile synchronously on the UI
thread.
Removed in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first main frame load of
the first web contents. Uses significantly more buckets, with reduced
ranges.
Moved to Startup.FirstWebContents.MainFrameLoad in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first main frame load of
the first web contents. Uses standard bucket ranges.
Removed in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first non-empty paint of
the first web contents. Uses significantly more buckets, with reduced
ranges.
Moved to Startup.FirstWebContents.NonEmptyPaint in M-41.
erikchen@chromium.org
An experimental metric only collected on the dev and canary channels.
Measure the elapsed time from process launch to the first non-empty paint of
the first web contents. Uses standard bucket ranges.
Replaced by Startup.FirstCommitNavigationTime2
pasko@chromium.org
[Android only] The time from the earliest entry point in the browser process
to the moment the first navigation is committed, i.e. when renderer gets the
first byte of the document.
Replaced with Startup.FirstCommitNavigationTime3 on 6/2017
pasko@chromium.org
wnwen@chromium.org
[Android only] The time from the first foreground entry point in the app to
the moment the first navigation is committed, i.e. when renderer gets the
first byte of the document.
Replaced with Startup.Android.Experimental.Cold.TimeToFirstNavigationCommit
on 11/2017
pasko@chromium.org
wnwen@chromium.org
[Android only] The time from the first foreground entry point in the app to
the moment the first navigation is committed, i.e. when renderer gets the
first byte of the document.
gab@chromium.org
[Desktop] The reason for which startup profiling was deemed complete. Logged
once per session on startup.
Deprecated with 3/2016 with M48.
erikchen@chromium.org
gab@chromium.org
[Desktop] DEPRECATED (but kept as a known basis until M48 is phased out).
Measure the elapsed time from process launch to the first main frame load of
the first web contents. Deprecated in favor of
Startup.FirstWebContents.MainFrameLoad2 which now avoids counting ill-cases
(ref. FirstWebContentsProfiler::FinishReason).
fdoray@chromium.org
gab@chromium.org
[Desktop] Measure the elapsed time from process launch to the first main
frame load of the first web contents. Only comprised of cases where the
initial foreground tab gets to complete its rendering task unimpeded (an
improvement over Startup.FirstWebContents.MainFrameLoad).
gab@chromium.org
[Desktop] Measure the elapsed time from process launch to the moment when
the navigation is committed (first bytes received) in the first web
contents' main frame.
gab@chromium.org
[Desktop] Measure the elapsed time from process launch to the beginning of
navigation in the first web contents' main frame.
Deprecated with 3/2016 with M48.
erikchen@chromium.org
gab@chromium.org
[Desktop] DEPRECATED (but kept as a known basis until M48 is phased out).
Measure the elapsed time from process launch to the first non- empty paint
of the first web contents. Deprecated in favor of
Startup.FirstWebContents.NonEmptyPaint2 which now avoids counting ill-cases
(ref. FirstWebContentsProfiler::FinishReason).
fdoray@chromium.org
gab@chromium.org
[Desktop] Measure the elapsed time from process launch to the first non-
empty paint of the first web contents. Only comprised of cases where the
initial foreground tab gets to complete its rendering task unimpeded (an
improvement over Startup.FirstWebContents.NonEmptyPaint).
hans@chromium.org
Time between RenderFrameHostImpl::Init and
Startup.FirstWebContents.NonEmptyPaint2.
Deprecated 10/2015.
gayane@chromium.org
[Desktop] Measures the execution time for a single task to execute on UI if
it was not possible to execute UI tasks under 1/60s within certain limits,
after WebContents was painted at least once. This is recorded at most once
per Chrome launch. Used as a measure of responsiveness on startup.
Deprecated 10/2015.
gayane@chromium.org
[Desktop] Measures the elapsed time for a single task to execute on UI if it
was not possible to execute it under 1/60s within certain limits, 10 second
after first WebContents was painted at least once. This is recorded at most
once per Chrome launch. Used as a measure of responsiveness on startup.
Deprecated 10/2015.
gayane@chromium.org
[Desktop] Measures the elapsed time for a single task to execute on UI if it
was not possible to execute it under 1/60s within certain limits, 1 second
after first WebContents was painted at least once. This is recorded at most
once per Chrome launch. Used as a measure of responsiveness on startup.
Deprecated 10/2015.
gayane@chromium.org
[Desktop] Measures the elapsed time it takes for a task to execute on UI
under 1/60s after first WebContents was painted at least once. This is
recorded at most once per Chrome launch. Used as a measure of responsiveness
on startup.
Deprecated 10/2015.
gayane@chromium.org
[Desktop] Measures the elapsed time it takes for a task to execute on UI
under 1/60s, 10 second after the first WebContents was painted. This is
recorded at most once per Chrome launch. Used as a measure of responsiveness
on startup.
Deprecated 10/2015.
gayane@chromium.org
[Desktop] Measures the elapsed time it takes for a task to execute on UI
under 1/60s, 1 second after the first WebContents was painted. This is
recorded at most once per Chrome launch. Used as a measure of responsiveness
on startup.
Deprecated 7/2015. To be replaced with Cast events.
jeremy@chromium.org
The elapsed time from the Fling application launch to the first video frame
displayed.
Deprecated 12/2011. Merged into MobileSessionStartType.
jeremy@chromium.org
Whether a startup is a resume (vs a cold start).
Deprecated 12/2016. crbug.com/634408
fdoray@chromium.org
gab@chromium.org
Time from the main() function in chrome.exe to chrome.dll's main(). This
stat is only recorded after 7 minutes of OS uptime to try to mitigate the
variance resulting from Chrome being autostarted. Replaced with
Startup.LoadTime.ExeMainToDllMain2 which is recorded all the time.
fdoray@chromium.org
gab@chromium.org
Time from the main() function in chrome.exe to chrome.dll's main().
Deprecated 12/2016. crbug.com/634408
fdoray@chromium.org
gab@chromium.org
Time from the process creation to chrome.dll's main(). This stat is only
recorded after 7 minutes of OS uptime to try to mitigate the variance
resulting from Chrome being autostarted. Replaced with
Startup.LoadTime.ProcessCreateToDllMain2 which is recorded all the time.
fdoray@chromium.org
gab@chromium.org
Time from the process creation to chrome.dll's main().
Deprecated 12/2016. crbug.com/634408
fdoray@chromium.org
gab@chromium.org
Time from the process creation to executing the main() function in
chrome.exe. This stat is only recorded after 7 minutes of OS uptime to try
to mitigate the variance resulting from Chrome being autostarted. Replaced
with Startup.LoadTime.ProcessCreateToExeMain2 which is recorded all the
time.
fdoray@chromium.org
gab@chromium.org
Time from the process creation to executing the main() function in
chrome.exe.
olivierrobin@chromium.org
The action requested on the application startup when called from another app
or the OS.
olivierrobin@chromium.org
The calling application (if any).
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
-[AppControllerMac awakeFromNib].
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
-[AppControllerMac didFinishLaunching:]. At that point, the dock icon will
finish its current animation and stop bouncing.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PostMainMessageLoopStart.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PostProfileInit.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PreMainMessageLoopStart.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
ChromeBrowserMainPartsMac::PreProfileInit.
erikchen@chromium.org
The amount of time that elapsed between main entry and the invocation of
-[AppControllerMac willFinishLaunching:].
rkaplow@chromium.org
The amount of time that elapsed during
ChromeBrowserMainParts::PreMainMessageLoopRunImpl.
rkaplow@chromium.org
The amount of time that elapsed during 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.
fdoray@chromium.org
gab@chromium.org
The number of startups the current version has been through. Reported once
per Chrome session, on startup. Any user that reports X for this version
will also have previously reported [1,X-1] for this version through the
previous X-1 Chrome sessions.
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.
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.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to load bookmarks from disk. This measurement is only sent for
startups that take >10 seconds after an uptime of 7 minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to finish initialization of the extension service including
loading built-in extensions. This measurement is only sent for startups that
take >10 seconds after an uptime of 7 minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time the final stages of profile initialization taking including
initialization of profile keyed services. This measurement is only sent for
startups that take >10 seconds after an uptime of 7 minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to load the NSS libraries and initialize it. This measurement
is only sent for startups that take >10 seconds after an uptime of 7
minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to load preferences from disk. This measurement is only sent
for startups that take >10 seconds after an uptime of 7 minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to initialize the ProfileIOData object - this includes
initialization of the cookie store. This measurement is only sent for
startups that take >10 seconds after an uptime of 7 minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to load the safe browsing database from disk. This measurement
is only sent for startups that take >10 seconds after an uptime of 7
minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes to initialize the safe browsing service. This measurement is
only sent for startups that take >10 seconds after an uptime of 7
minutes.
Deprecated 06/2015.
jeremy@chromium.org
Time it takes for session restore to finish initiating creation of restored
tabs and windows. This measurement is only sent for startups that take
>10 seconds after an uptime of 7 minutes.
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().
fdoray@chromium.org
The time elapsed between system boot and Chrome browser process launch. This
is recorded just before the main message loop starts.
chrisha@chromium.org
fdoray@chromium.org
Indicates whether or not the given startup was warm, cold or unable to be
determined. This is based off observing the number of hard faults that occur
during startup prior to Startup.BrowserMessageLoopStartTime.
feuunk@chromium.org
The time of day in GMT that the startup was performed. This is logged in
HHMM format, with the minutes rounded down to the nearest 10 minute
interval.
This can be used to make traffic estimates for requests made from startup.
fdoray@chromium.org
Time elapsed since the last startup that went up to the main message loop
start. This is recorded just before the main message loop starts.
fdoray@chromium.org
Time for a running browser process to start processing the command line
passed in by a second Chrome process, which just sent its command line
arguments to the already-running process and will soon exit. Measured from
the time the second Chrome process started.
Deprecated as of 10/2014.
rch@chromium.org
Time duration measured from the time the startup timebomb was started and
when it went off.
dmurph@chromium.org
This is recorded for every site that the user blacklists when they when they
clear browsing data. It indicates which signals were used to show the given
site to the user that the user then chose to exclude from clearing.
dmurph@chromium.org
If a newly constructed blob is broken. See Storage.Blob.BrokenReason for a
the broken reasons.
dmurph@chromium.org
The reason a blob is broken, reported only for broken blobs upon
construction. See Storage.Blob.Broken for the breakdown of blobs broken vs
unbroken.
mek@chromium.org
The result of constructing a blob using the BlobRegistry.RegisterFromStream
API.
dmurph@chromium.org
Recorded when the old blob storage directories are cleared. This occurs on
storage partition initialization, and is not recorded if there are no
directories to clear. The value indicates if the file operations were a
success.
dmurph@chromium.org
Recorded when we create the blob storage directory for the blob storage
system. When we need to write blob data to files, we create this directory
if it doesn't exist. We write blob data to files when either we have a new
blob that's larger than our memory limit, or we're approaching our in-memory
limit for blob storage.
Deprecated as of 3/2016. Use Storage.Blob.Broken to see the fraction of
blobs that are broken, and Storage.Blob.BrokenReason for the number of
broken blobs that are broken because of memory constraints.
dmurph@chromium.org
True if a created blob exceeded the internal in-memory storage memory limit
for blobs.
dmurph@chromium.org
Recorded when an error occurs in the FileReaderLoader, which is used to load
blobs in the Renderer. FileReaderUser is mostly used for Javascript's
'FileReader', but can also be used to read blobs for the IndexedDB
renderer-side implementation. For the read error category, see
Storage.Blob.FileReaderLoader.ReadError for a breakdown of the specific read
error reasons.
dmurph@chromium.org
The error code reported by the blob system while trying to read a blob in
the FileReaderLoader. Compare with the
Storage.Blob.IDBRequestLoader.ReadError histogram to eliminate IndexedDB
large-value blobs.
mek@chromium.org
The amount of time taken to complete the synchronous
BlobRegistry.GetBlobFromUUID mojo call.
dmurph@chromium.org
The error code reported by the blob system while trying to read an IndexedDB
large-value blob in the IDBRequestLoader. These blobs are automatically
created in Blink when a website writes a large value to IndexedDB.
dmurph@chromium.org
Counts the number of times we have an invalid refcount operation. An invalid
increment means the blob didn't exist, and an invalid decrement means we
don't have any record of the blob in our host.
dmurph@chromium.org
Counts the number of times we have an invalid url registration operation. An
invalid increment means the blob isn't in use by the host yet or the url is
already mapped. An invalid decrement means the url isn't registered.
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
Records the calculated max disk space the blob storage system can use.
Recorded on storage partition initialization.
dmurph@chromium.org
Recorded when the blob system changes adjustment types on its disk size. The
disk can either be Frozen, Adjusted (near min external available disk
space), or Normal. We record when we transition between these states, which
can happen after any file operations in the blob system (paging data to disk
or saving a new blob directly to disk).
dmurph@chromium.org
Size of a page file created for blob data by the blob storage system.
Recorded before we create the file and write the blob items. We page blob
data to files when we get close to our maximum blob memory usage.
dmurph@chromium.org
Recorded when we disable paging blobs to file in the blob storage system.
This occurs when we experience a filesystem error during writing blob data
to disk. We write blob data to files when either we have a new blob that's
larger than our memory limit, or we're approaching our in-memory limit for
blob storage. The relevant error is recorded here.
darin@chromium.org
The amount of time taken to complete the synchronous
BlobStorageMsg_RegisterBlob IPC.
darin@chromium.org
The amount of time taken to complete the synchronous
BlobStorageMsg_RegisterPublicURL IPC.
dmurph@chromium.org
Whether seeking within a file (in order to write a part of a blob) failed in
the renderer.
dmurph@chromium.org
Whether writing part of a blob to a file failed in the renderer.
dmurph@chromium.org
True if we reuse an item for a blob created from using Blob.slice, recorded
in BlobStorageContext on blob creation.
ssid@chromium.org
Records the total size of in-memory blobs evicted to disk.
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.
michaeln@chromium.org
The number of bytes read. Recorded on each read.
michaeln@chromium.org
The number of bytes written. Recorded on each write.
dmurph@chromium.org
When a user chooses to blacklist one or more sites when they clear browsing
data, this is recorded for every reason each chosen site was marked as
important. It indicates which signals were used to show the given site to
the user that the user then chose to exclude from clearing.
dmurph@chromium.org
This records the number of reasons each important site had that the user
chose to blacklist when clearing browsing data.
dmurph@chromium.org
When a user chooses to blacklist one or more sites when they clear browsing
data, this is recorded for every reason each unchosen site was marked as
important. It indicates which signals were used to show the given site to
the user, which the user then ignored and did not select to blacklist from
clearing data.
dmurph@chromium.org
This records the number of reasons each important site had that the user
chose to NOT blacklist when clearing browsing data.
dmurph@chromium.org
Recorded when we generate a list of important sites. This can happen when
the user opens the Clear Browsing Data dialog on Android, views the Storage
tab in Site Settings on Android, or launches 'Manage Storage' from Android
System Settings for Chrome. We record every reason each site was chosen in
this metric. This means that we can report this metric multiple times for a
single site.
dmurph@chromium.org
This records the number of reasons qualifying a site for being 'important'.
We record this for every site when we generate a list of important sites,
described in "Storage.ImportantSites.GeneratedReason".
dmurph@chromium.org
Records the size of a blob used in an IndexedDB add/put operation. Recorded
for every put operation that contains a blob.
dmurph@chromium.org
Records if a blob intended to be used in an IndexedDB add/put operation is a
valid blob. Recorded for every put operation that contains a blob.
csharrison@chromium.org
Microseconds spent in StyleSheetContents::parseAuthorStyleSheet.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
csharrison@chromium.org
Tracks % of lazy rules that ended up needing to be parsed. A sheet logs
counts into this histogram as it is parsed (i.e. as properties are parsed
lazily). Once a certain percent of rules have been parsed, we log a count
immediately. Note that this implies that a stylesheet which uses all of its
rules will log counts in every bucket.
csharrison@chromium.org
Tracks the total number of rules that have parsing lazily deferred in an
author style sheet.
csharrison@chromium.org
Tracks the total number of rules that have parsing lazily deferred in an
author style sheet, for sheets that ended up needing all their rules.
csharrison@chromium.org
Microseconds spent in Document::updateStyle.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
Deprecated June 2018 in favor of SubresourceFilter.Actions2
csharrison@chromium.org
Counts of various UI and user action events related to the
SubresourceFilter. This will be triggered in response to Content Settings
changes, as well as when portions of the UI are shown or interacted with.
Main frame navigations are also tracked for ease of comparison and analysis.
csharrison@chromium.org
jkarlin@chromium.org
Counts of various UI and user action events related to the
SubresourceFilter. This will be triggered when portions of the UI are shown
or interacted with.
csharrison@chromium.org
jkarlin@chromium.org
Logs the delay the ad delay throttle added to a request. Logged for every
subresource request that was delayed.
csharrison@chromium.org
jkarlin@chromium.org
Logs the expected delay the ad delay throttle added to a request. This is
the delay imposed assuming no task queuing delay. Logged for every
subresource request that was delayed.
csharrison@chromium.org
jkarlin@chromium.org
Logs the task queuing delay the ad delay throttle added to a request. This
is the actual delay minus the expected delay. Logged for every subresource
request that was delayed.
Deprecated July 2018. Replaced with Ads.Features.AdResourceIsIsolated.
csharrison@chromium.org
jkarlin@chromium.org
For a given ad request, logs information related to whether it is isolated
from the top-level context. Logged per ad subresource request.
Deprecated July 2018. Replaced with Ads.Features.ResourceIsSecure.
csharrison@chromium.org
jkarlin@chromium.org
For a given request, logs information related to whether it is marked as an
ad, and whether it is secure (e.g. https). Logged per subresource request.
pkalinnikov@chromium.org
Records how much thread CPU time it takes to decide whether subresource
filtering should be activated for a main frame or subframe.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
pkalinnikov@chromium.org
Records how long it takes to decide whether subresource filtering should be
activated for a main frame or subframe.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
csharrison@chromium.org
Records the total time the activation state navigation throttle within a
document is delayed while calculating activation. Recorded at resume time.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
csharrison@chromium.org
Records the total time the activation state navigation throttle within a
main frame document is delayed while calculating activation. Recorded at
resume time.
engedy@chromium.org
Whenever a document load is committed in a main frame or subframe, records
whether subresource filtering should be activated for that load.
engedy@chromium.org
Whenever a document load is finished in a main frame or subframe with
subresource filtering activated, records the total number of subresource
loads that have been disallowed. This only differs from `MatchedRules` when
filtering is performed in dry-run mode.
engedy@chromium.org
Whenever a document load is finished in a main frame or subframe with
subresource filtering activated, records the total number of subresource
loads that have been evaluated. This only differs from 'Total' when the
document is subject to a deactivating rule with DOCUMENT activation type.
engedy@chromium.org
Whenever a document load is finished in a main frame or subframe with
subresource filtering activated, records the total number of subresource
loads that have matched filtering rules. This only differs from `Disallowed`
when filtering is performed in dry-run mode.
engedy@chromium.org
Whenever a document load is finished in a main frame or subframe with
subresource filtering activated, records the total number of subresource
loads that have gone through the subresource filtering pipeline.
engedy@chromium.org
Whenever a document load is committed in a main frame or subframe and
subresource filtering should be activated, records whether the filtering
rules are available.
csharrison@chromium.org
Records the total time a subframe navigation was delayed while calculating
whether it should be disallowed or not. Logged for all navigations that were
allowed.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
csharrison@chromium.org
Records the total time a subframe navigation was delayed while calculating
whether it should be disallowed or not. Logged for all navigations that were
disallowed.
pkalinnikov@chromium.org
Whenever a document load is finished in a main frame or subframe with
subresource filtering activated, records the total thread CPU time spent on
processing subresource requests in allowLoad.
Note: this histogram is emitted for all clients, both ones which have
high-resolution timer available and those which don't.
pkalinnikov@chromium.org
Whenever a document load is finished in a main frame or subframe with
subresource filtering activated, records the total real time spent on
processing subresource requests in allowLoad, including the time spent on
waiting or being descheduled.
Note: this histogram is emitted for all clients, both ones which have
high-resolution timer available and those which don't.
pkalinnikov@chromium.org
The total CPU time it took to parse and index all rules. Does not include
time when the indexing thread was not doing actual work, e.g. waiting for
I/O or being descheduled. Recorded every time the RulesetService kicks off a
ruleset indexing process.
engedy@chromium.org
The number of rules that could be not be successfully indexed and therefore
have been ignored. Recorded every time the RulesetService kicks off a
ruleset indexing process and it reaches the point where rules are getting
indexed.
Deprecated in favor of the Verify2 metric
csharrison@chromium.org
The total time it took to verify the indexed ruleset in the browser process.
Logged every time verification occurs, which usually occurs when the first
page with activation is navigated to.
csharrison@chromium.org
The total time it took to verify the indexed ruleset in the browser process.
Logged every time verification occurs, which usually occurs when the first
page with activation is navigated to.
engedy@chromium.org
The total time it took to read and index all rules. Includes I/O time for
reading the unindexed rules, but not for writing the indexed ruleset.
Recorded every time the RulesetService kicks off a ruleset indexing process.
csharrison@chromium.org
Records how much thread CPU time it takes to decide whether subresource
filtering should be activated for a main frame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ericrobinson@chromium.org
For pages that trigger Safe Browsing activations (not including dry runs),
records the position in the redirect chain for the page the activation was
triggered by. If SubresourceFilterConsiderRedirects is disabled, then
always returns "Only navigation".
csharrison@chromium.org
Records how long it takes to decide whether subresource filtering should be
activated for a main frame.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
csharrison@chromium.org
Records the policy decision to activate subresource filtering for a page
load. 'Activated' indicates that subresource filtering was activated. All
other reasons indicate that subresource filtering was not activated.
csharrison@chromium.org
The ActivationList or NONE that the main frame navigation matched with.
Recorded at WillProcessResponse time for a main frame navigation.
csharrison@chromium.org
Whenever a document load is committed in a main frame, records whether
subresource filtering should be activated for that load.
Metric is broken and will be replaced by
ContentSettings.Popups.StringBlocked.NumBlocked. This only logged values for
sites which are also activated for subresource filtering, when most sites
will probably only be marked for popup blocking.
csharrison@chromium.org
Records the number of popups blocked per page load due to subresource filter
logic. Recorded when a new main frame navigation commits. Note that this
histogram is recorded for all pages which are activated by the subresource
filter, including ones which do not trigger the stronger popup blocker.
Deprecated in favor of SubresourceFilter.PageLoad.ActivationList.
melandory@chromium.org
Records, for each main frame navigation, whether the last URL in the
redirect chain matched the Safe Browsing blacklist specified by the
histogram suffix.
Deprecated May 2018 in favor of
SubresourceFilter.PageLoad.ActivationDecision
csharrison@chromium.org
Logged when the first resource is disallowed from a page with forced
activation. For example, if the devtools ad blocking option is set.
pkalinnikov@chromium.org
Whenever a page load is finished with subresource filtering activated,
records the total number of subresource loads that have been disallowed.
This only differs from `MatchedRules` when filtering is performed in dry-run
mode.
pkalinnikov@chromium.org
Whenever a page load is finished with subresource filtering activated,
records the total number of subresource loads that have been evaluated. This
only differs from 'Total' when some of subdocuments is subject to a
deactivating rule with DOCUMENT activation type.
pkalinnikov@chromium.org
Whenever a page load is finished with subresource filtering activated,
records the total number of subresource loads that have matched filtering
rules. This only differs from `Disallowed` when filtering is performed in
dry-run mode.
pkalinnikov@chromium.org
Whenever a page load is finished with subresource filtering activated,
records the total number of subresource loads that have gone through the
subresource filtering pipeline.
Deprecated May 2018
melandory@chromium.org
Total number of server redirects during the navigation. This histogram is
recorded in several for every list where subresource fiter is active.
Obsolete as of April 2017, since the don't have correct data to record
anymore.
melandory@chromium.org
For each main frame navigation, records a pattern that indicates which URLs
in the redirect chain matched Safe Browsing blacklists, and which did not.
For example, for the redirect chain A-B-C-D metric tracks: 1. If initial URL
(A) was on a Safe Browsing blacklist. 2. If any if middle urls (B, C) were
on a Safe Browsing blacklist. 3. If committed URL (B) was on a Safe Browsing
blacklist. This histogram is recorded in several flavours: with prefix
SubresourceFilterOnly in case the redirect chain contains url from the Safe
Browsing SubresourceFilter list and without the prefix for all other
redirect chains.
csharrison@chromium.org
The navigation delay imposed by the subresource filter on a given navigation
due to Safe Browsing checks.
Deprecated in May 2018 (M69). We have enough data to show that the redirect
speculations we do are necessary, especially for Android.
csharrison@chromium.org
The navigation delay that would have been imposed by the subresource filter
on a given navigation due to Safe Browsing checks if redirect speculation
was removed. Removing this feature would cause more delay if a navigation
has redirects.
pkalinnikov@chromium.org
Whenever a page load is finished with subresource filtering activated,
records the total thread CPU time spent on evaluating subresource requests,
aggregated across all frames.
Note: this histogram is emitted for all clients, both ones which have
high-resolution timer available and those which don't.
pkalinnikov@chromium.org
Whenever a page load is finished with subresource filtering activated,
records the total real time spent on evaluating subresource requests,
aggregated across all frames. This includes the time spent on waiting or
being descheduled.
Note: this histogram is emitted for all clients, both ones which have
high-resolution timer available and those which don't.
Deprecated in favor of the whitelisted bucket in SubresourceFilter.Actions2
melandory@chromium.org
Number of times the user has requested a reload for the page by clicking on
the reload button.
Deprecated in favor of SubresourceFilter.Action
melandory@chromium.org
Number of times Safebrowsing Subresource Filter decided to toggle visibility
of the prompt.
Deprecated in May 2018 in favor of the more general
SB2.RemoteCall.CheckDispatchTime.
csharrison@chromium.org
The microseconds it took to dispatch the Safe Browsing check. This includes
IPC descheduling delays to communicate with SafetyNet on Android, and
synchronous db checks on desktop.
Note: this histogram is emitted for all clients, both ones which have
high-resolution timer available and those which don't.
csharrison@chromium.org
The time an individual Safe Browsing URL check took before finishing. Logged
when a check is complete or cancelled due to a timeout.
csharrison@chromium.org
The time an individual Safe Browsing URL check took before finishing,
including posting tasks to and from the IO thread. Measured on the UI
thread.
pkalinnikov@chromium.org
Whenever a subresource of a document is evaluated against the ruleset,
records the thread CPU time spent on calculating whether it should be
allowed to load.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
pkalinnikov@chromium.org
Whenever a subresource of a document is evaluated against the ruleset,
records how much time was spent on calculating whether it should be allowed
to load.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
engedy@chromium.org
Records the exact error whenever writing a ruleset fails at the step where
the ruleset would be moved from the scratch directory to its final location.
engedy@chromium.org
Whether indexing a version of the ruleset and writing it to disk succeeded,
or failed at a particular step. Recorded every time the RulesetService kicks
off a ruleset indexing process.
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.
aberent@chromium.org
Time to get the response to requesting whether a URL should be accessible to
the supervised user, when Chrome was not previously running.
aberent@chromium.org
Time to get the response to requesting whether a URL should be accessible to
the supervised user, when Chrome was already running.
aberent@chromium.org
True if a request to find out whether a URL should be accessible to a
supervised user timed out.
Deprecated in M53.
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).
Deprecated 2018-04, Sync attachments were never launched.
maxbogue@chromium.org
Whether attachment checksums match on download or not.
Deprecated 2018-04, Sync attachments were never launched.
maxbogue@chromium.org
Response or error codes from downloading sync attachments.
Deprecated 2018-04, Sync attachments were never launched.
maxbogue@chromium.org
The total time a download takes including request and server overhead.
Deprecated 2018-04, Sync attachments were never launched.
maxbogue@chromium.org
The result of initializing the sync attachment store.
Deprecated 2018-04, Sync attachments were never launched.
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.
Deprecated in M53.
zea@chromium.org
Age of all auth tokens rejected by the invalidation server. Measured from
the time they were created.
Deprecated in M53.
zea@chromium.org
Age of auth tokens younger than one hour that were rejected by the
invalidation server. Measured from the time they were created.
Deprecated in M53.
zea@chromium.org
Time taken during initial authorization.
Deprecated in M53.
zea@chromium.org
Age of all auth tokens rejected by the sync server. Measured from the time
they were created.
No longer relevant since transition to OAuth.
zea@chromium.org
Age of auth tokens younger than one hour that were rejected by the sync
server. Measured from the time they were created.
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.
Deprecated in M53.
zea@chromium.org
Compares sync's has_setup_completed pref against the set of types actually
restored from the sync DB. Mismatches should be rare.
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.
Deprecated in M53.
zea@chromium.org
Number of bad requests since application startup, when the Sync error
infobar asking the user to update their account details is displayed.
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
Tracks state of local bookmark model version relative to the sync version
when a new bookmark duplication occurs during 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).
pavely@chromium.org
Records events encountered during sync's ClearServerData flow.
zea@chromium.org
Breakdown of sync data types being configured at first time signin, restart,
or user-initiated reconfiguration. This is different from Sync.CustomTypes
in that this captures all active devices, not just those that are choosing a
custom sync configuration.
Note that not all platforms support all data types. As such, comparing
across platforms should only look at the common data types.
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 the gaia cookie jar was empty. Recorded on every SESSIONS commit
where the gaia cookie jar does not include the signed in user (
CookieJarMatchOnNavigation == false).
zea@chromium.org
Whether the gaia cookie jar included the signed in user (matched) or not.
Recorded on every SESSIONS commit.
Deprecated in M53.
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.
Deprecated in M53.
zea@chromium.org
Number of clients that have fixed themselves up from a datatype preference
loss. Clients are not expected to have this happen more than once. This
value can be compared to Sync.BackendInitializeRestoreSuccess to determine
what percentage of users are still recovering.
zea@chromium.org
Histogram of the run failures for the different sync datatypes. These are
failures that occur after startup while the datatype is syncing. Note: Due
to an enumeration reordering, pre-M23 labels are inaccurate (see
sync/base/model_type.h).
zea@chromium.org
Histogram of the startup failures for the different sync datatypes. These
are failures due to missing top level sync nodes or model association Note:
Due to an enumeration reordering, pre-M23 labels are inaccurate (see
sync/base/model_type.h).
skym@chromium.org
The largest number of active syncing devices known to any profile. May be 0
when there are no signed in/syncing profiles open.
Deprecated in M53.
pavely@chromium.org
When signin_scoped_device_id from pref doesn't match the one in
DeviceInfoSpecfics this histogram tells if sync or pref copy was empty. This
will indicate how often such mismatch happens and what was the state before.
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.
Deprecated in M53.
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).
gangwu@chromium.org
Counts the total number of extra copies of sync data in memory. This count
is emitted once, after loading Sync Directory. The count will indicate how
many Directory entities fail to share client and server specifics.
zea@chromium.org
Whether a sync favicon cache lookup succeeded or not.
Deprecated in M53.
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.
Deprecated in M53.
zea@chromium.org
Number of client that have filled their sync favicon cache and must evict
old favicons vs those whose cache is not full.
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.
Deprecated in M53.
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.
Backup logic has been removed since 02/2016.
haitaol@chromium.org
First sync delay casued by backing up user data.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for apps. Used as estimate of datatype commit frequency.
Logged when a sync cycle is performed for apps.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for autofill entries. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for autofill
entries.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for autofill profiles. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for autofill
profiles.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for bookmarks. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for boomarks.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for dictionary. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for dictionary.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for extensions. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for extensions.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for favicon images. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for favicon images.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for favicon tracking. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for favicon
tracking.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for nigori. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for nigori.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for passwords. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for passwords.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for preferences. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for preferences.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for search engines. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for search engines.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for sessions. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for sessions.
Deprecated in M53.
zea@chromium.org
Time between nudges for synced notifications. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for synced
notifications.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for themes. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for themes.
Deprecated 03/2018 (M67). Replaced by Sync.SyncCycleInterval.
zea@chromium.org
Time between nudges for typed urls. Used as estimate of datatype commit
frequency. Logged when a sync cycle is performed for typed urls.
Deprecated in M53.
zea@chromium.org
Time between nudges for WiFi credentials. Used as estimate of datatype
commit frequency. Logged when a sync cycle is performed for WiFi
credentials.
skym@chromium.org
Two navigations with different unique_ids shared a global_id/timestmap. This
means that user events will be ambiguously referencing navigations.
maxbogue@chromium.org
An approximate state of sync at startup. Logs a few reasons sync definitely
wouldn't be able to start, or that it probably can start. The user having
turned off sync on mobile will be logged as "turned off by user".
A dashboard stop and clear will fall under "turned off and setup not
completed". See the SyncInitialState enum in profile_sync_service.h for
more information.
Deprecated as of 5/2016.
pkotwicz@chromium.org
Count of the number of session sync invalidations. The goal of the metric is
to track how the number of session sync invalidations changes over time.
zea@chromium.org
The reason for a failure decrypting the keystore decryptor token.
pastarmovj@chromium.org
Tracks the number of times the local sync backend was enabled by the user.
pastarmovj@chromium.org
Tracks the size of the local sync backend database file.
skym@chromium.org
Tracks the types of requests that caused errors inside of the local server.
pastarmovj@chromium.org
Tracks the number of times the Roaming profile cannot be retrieved.
vasilii@chromium.org
Counts cases when a sync type failed to load the local data during startup.
zea@chromium.org
Counts instances of out of sync local models detected during startup.
pnoland@chromium.org
Counts instances of navigations that are recorded locally but not synced.
Recorded once per active tab for every inferred sync cycle. Sync cycles are
inferred by examining the is_synced and is_syncing flags of sync directories
when recording local changes to tabs or windows. Sync cycles that occur
without changes to tabs or windows won't cause this metric to be logged.
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.
gangwu@chromium.org
Counts the number of entries for each model type in sync DB at startup.
pavely@chromium.org
Estimated memory usage by sync datatype in kilobytes. Recorded after sync
configuration.
pavely@chromium.org
Records the result of ModelTypeStoreBackend initialization. Used to analyze
frequency and causes of backend initialization failures.
zea@chromium.org
Breakdown of sync's nigori node keystore migration state.
Deprecated in M66.
skym@chromium.org
The client side execution time to check for revisits with bookmarks data.
Deprecated in M66.
skym@chromium.org
Age of bookmark that matches a navigation event, where matching means the
urls match. If multiple bookmarks match, the most recently created is used.
Deprecated in M66.
skym@chromium.org
Transition type to a page that matched a bookmark.
Deprecated in M66.
skym@chromium.org
Transition type to a page that didn't match a bookmark.
Deprecated in M66.
skym@chromium.org
Difference in time between finding the match and the creation of the most
recent foreign modification of the parent tab. The parent tab's modification
will not always be indicative of when the matching navigation occurred.
Deprecated in M66.
skym@chromium.org
The number of navigations forward or backwards the matching noncurrent
navigation is from the current navigation in its tab. Negative values
represent backwards and positive values represent forwards. Zero should not
occur since it would cease to be noncurrent.
Deprecated in M66.
skym@chromium.org
Transition type that matched a synced navigation.
Deprecated in M66.
skym@chromium.org
Transition type that didn't match a synced navigation.
Deprecated in M66.
skym@chromium.org
The client side execution time to check for revisits with session data.
Deprecated in M66.
skym@chromium.org
Difference in time between finding the match and the creation of the most
recent foreign modification of the given tab.
Deprecated in M66.
skym@chromium.org
Transition type that matched a synced tab.
Deprecated in M66.
skym@chromium.org
Transition type that didn't match a synced tab.
Deprecated in M66.
skym@chromium.org
The client side execution time to check for revisits with typed URL data.
Deprecated in M66.
skym@chromium.org
Difference in time between finding the match and the last time this URL was
typed on a foreign client.
Deprecated in M66.
skym@chromium.org
Transition type that matched a typed URL.
Deprecated in M66.
skym@chromium.org
Transition type that didn't match a typed URL.
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.
Deprecated in M53.
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).
Deprecated in M53.
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).
tschumann@chromium.org
treib@chromium.org
Counts the number of times a syncable pref got registered using a type that
mismatched the type present in the pref store. In these events, the
persisted value gets removed from the pref store.
tschumann@chromium.org
treib@chromium.org
Counts the number of times a client received a remote pref update with a
value type different from the registered pref type. The client will ignore
those remote updates.
tschumann@chromium.org
treib@chromium.org
The number of unknown prefs being synced. This number is computed after the
sync model has been associated. Preferences which get handled by sync even
before being registered are considered "unknown". This might be
limited to a whitelist of preferences.
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).
Deprecated in M53.
zea@chromium.org
Time taken from startup for the user to reauthorize.
Deprecated 04/2016 as not useful since it always logged true.
zea@chromium.org
Whether OAuth2 refresh token was available at the time when
ProfileSyncService was starting backend.
gangwu@chromium.org
The request content size for a single HTTP/HTTPS call from sync client to
server. The content is compressed by gzip.
gangwu@chromium.org
The original request content size for a single HTTP/HTTPS call from sync
client to server. It is the size before content got compressed.
maxbogue@chromium.org
Enumeration of types of conflict resolutions. Recorded every time a conflict
is resolved for a data type that has been converted to USS.
zea@chromium.org
Enumeration of types of simple conflict resolutions.
gangwu@chromium.org
The response content size for a single HTTP/HTTPS call from sync server to
client. The content is compressed by gzip.
gangwu@chromium.org
The original response content size for a single HTTP/HTTPS call from sync
server and client. It is the size after content got uncompressed.
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.
Deprecated in M53.
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.
Deprecated in M53.
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.
skym@chromium.org
Number of foreign sessions entries detected with bad client tag hash value
during MergeDataAndStartSyncing. These will be immediately deleted. The
overwhelming majority of clients should report a value of 0 upon startup.
zea@chromium.org
Enumeration of types of session configuration failures.
zea@chromium.org
Delay from the time chrome://history is loaded until the other devices'
sessions data became available.
Replaced by SessionsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of session association failures.
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
For each Chrome window, records the number of tabs present at the time Sync
associates the SESSIONS datatype.
zea@chromium.org
The number of windows present within Chrome at the time Sync associates the
SESSIONS datatype.
Deprecated in M69.
mastiz@chromium.org
https://crbug.com/639009, count of duplicate sync ids (tab node id) when any
are encountered. Likely caused from a persistence race between native tab
storage and sync db on Android. Should be trending to zero.
zea@chromium.org
Time taken from the start of sync shutdown (in ProfileSyncService) until the
backend (SyncEngine) is fully destroyed.
Deprecated in M53.
zea@chromium.org
Amount of time the UI thread waits (at shutdown) to stop the
SyncBackendRegistrar.
Deprecated in M53.
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 SyncEngine
initialization.
zea@google.com
Time spent after ProfileSyncService *creation* but before SyncEngine
initialization.
zea@chromium.org
Data type that first requests sync initialization.
maxbogue@chromium.org
Tracks how sync was turned off. Logged every time sync is told to stop
permanently by the user (e.g. it won't come back on by itself).
Deprecated in M53.
zea@chromium.org
Counts the number of times sync clients have encountered an auth error and
number of times auth errors are fixed.
treib@chromium.org
The interval between successive sync cycles. Recorded whenever a sync cycle
starts, except for the very first one after Chrome startup.
Deprecated in M53.
zea@chromium.org
Time taken during synced notifications association.
Deprecated in M53.
zea@chromium.org
Enumeration of types of synced notifications configuration failures.
Deprecated in M53. 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).
Deprecated in M53.
zea@chromium.org
Time taken during typed url association (M18 and earlier were mispelled with
this histogram).
Deprecated in M53.
zea@chromium.org
The percentage of history DB operations initiated by the typed URL change
processor that return an error. The cumulative count for the current sync
session is logged after every typed URL change.
zea@chromium.org
The percentage of history DB operations during merge data that return an
error. This is logged at the end of typed URL merge data, which happens once
each time sync starts up.
Deprecated in M53.
zea@chromium.org
The percentage of history DB operations during model association that return
an error. This is logged at the end of typed URL model association, which
happens once each time sync starts up.
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
Counts of responses (both http code and net error code) for Sync URL
fetches.
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.
Deprecated in M53.
zea@chromium.org
Time the user spends looking at the authorization dialog.
Deprecated in M53.
zea@chromium.org
Time taken during bookmark association.
pavely@chromium.org
Time it took sync to load models for USS datatypes.
maxbogue@chromium.org
Counts directory to USS migration failures per model type.
maxbogue@chromium.org
Counts directory to USS migration successes per model type.
Deprecated in M53.
zea@chromium.org
Time taken during WiFi credentials association.
Deprecated in M53.
zea@chromium.org
Enumeration of types of WiFi credentials configuration failures.
Replaced by WifiCredentialsConfigureFailure. See crbug.com/478226.
zea@chromium.org
Enumeration of types of WiFi credentials association failures.
Deprecated in M67. After more than a year, almost all clients are reporting
FALSE.
skym@chromium.org
Whether there are still encrypted updates that the cryptographer cannot
decrypt during ApplyUpdates in the ModelTypeWorker (USS Only). Emitting true
is an invalid state that hopefully never happens, as it is a potential data
loss scenario.
Deprecated in M66.
skym@chromium.org
Upon NTP load, the age of the youngest synced foreign tab.
Deprecated in M53.
petewil@chromium.org
zea@chromium.org
The actions taken on synced notifications, recorded every time they happen.
This histogram will record every single event that happens separately.
tzik@chromium.org
Overridden conflict resolution policy of Sync FileSystem API. Recorded for
each API call to override the policy.
tzik@chromium.org
The result of opening the Sync FileSystem backend database.
tzik@chromium.org
The number of cached backing remote file metadata in the Sync FileSystem
database. Recorded at the initialization phase of Sync FileSystem.
tzik@chromium.org
The number of Chrome Apps that uses Sync FileSystem with V2 backend.
Recorded at the initialization phase of Sync FileSystem.
tzik@chromium.org
The result of the registration of Chrome App to Sync FileSystem.
peria@chromium.org
tzik@chromium.org
Time elapsed to register a Chrome App to SyncFilesystem. Recorded for each
registration request by apps.
tzik@chromium.org
The result of opening the Sync FileSystem tracker database.
tzik@chromium.org
The number of the directory tree node that maps backing files to local files
in the Sync FileSystem database. Recorded at the initialization phase of
SyncFileSystem.
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.
georgesak@chromium.org
Record whether the deferred free mechanism was successfully enabled or not.
This is only recorded in syzyasan builds with the feature enabled.
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.
hzl@google.com
Count of upload success/failures by crash type.
ppi@chromium.org
Mobile-specific metric: when a tab that was opened in background (via
"Open link in new tab") is switched to, we record whether the
eagerly loaded tab was still memory resident, or we lost the loaded page due
to memory pressure.
pkotwicz@chromium.org
Whether a tab which was opened in the background (e.g. via "Open link
in new tab") is foregrounded prior to being closed.
pkotwicz@chromium.org
Counts the number of background tabs opened via the context menu per page
URL. The count is reset on each navigation of the parent tab. Zero counts
are not recorded.
Time in milliseconds from trying to close the tab to actually closing it.
Includes time that's spent in JS OnUnload handlers.
Time in milliseconds from when JS OnUnload handlers have finished to
actually closing tab. Doesn't include time that's spent in JS OnUnload
handlers. If there are no UnLoad handlers, should be idential to Tab.Close.
Deprecated 11/2016. No longer useful after finding out that it has no effect
on tab reactivation rates.
pmonette@chromium.org
A tab was deactivated. Closing tabs are not included. This histogram also
records if the tab's URL was bookmarked.
pmonette@chromium.org
A tab was deactivated. Closing tabs are not included. This histogram also
records if the tab had any form interaction.
pmonette@chromium.org
A tab was deactivated. Closing tabs are not included. This histogram also
records if the tab was pinned to the tab strip or not.
Deprecated 10/2015, not needed anymore.
georgesak@chromium.org
Metric to track counts of actions related to tab discarding. Namely, we get
an event for every tab switch, split into two groups, whether it was a
discarded tab not. We also get an event whenever a tab gets discarded as
well as when a tab that's playing audio gets discarded.
Deprecated 10/2015, and replaced by TabManager.Discarding.DiscardCount.
georgesak@chromium.org
Metric to track the number of discards tabs have gone through. Each time a
tab is discarded, this histogram is recorded. Therefore, this metric is
cumulative, ie. as a tab gets discarded over and over, it gets a hit in each
bin (1, 2, 3...).
Deprecated as of 10/2016.
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.
mrefaat@chromium.org
Used on External App launcher Prompt to determine if the user clicked open
or cancel.
Deprecated as of 10/2016.
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.
lpromero@chromium.org
Used on iOS 9+ iPad to report the usage of Compact or Regular horizontal
size class. This is logged at startup and on each size class change.
pkotwicz@chromium.org
[Android] When a tab that was opened in the background (e.g. via "Open
link in new tab") is evicted prior to the first time that it is shown,
we record the tab's age at the time that the tab is shown.
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.
treib@chromium.org
The time for the new tab page to fire the "load" event. Note: This
is usually recorded with a suffix (.Local/Google/Other). The base version is
recorded only on Android. Recorded only once per tab, i.e. excluding
back/forward navigations.
lliabraa@chromium.org
beaudoin@chromium.org
The time for the new tab page to start executing JavaScript.
Deprecated in favor of Tab.TabUnder.PopupToTabUnderTime.
csharrison@chromium.org
Measures the time from when a tab opens a popup to when it navigates itself
cross-origin in the background.
Deprecated in favor of Tab.TabUnder.VisibleTime.
csharrison@chromium.org
Measures the total time a tab is visible after it navigates itself
cross-origin in the background. Measured at WebContents destruction. The tab
must have opened a popup (as classified by the popup blocker) before the
navigation.
lpromero@chromium.org
Used on iOS 9+ iPad to report the usage of Compact or Regular horizontal
size class. Recorded on page load.
jif@chromium.org
The orientation of the device. Recorded on page load.
lliabraa@chromium.org
The number of page loads since the last switch to an evicted tab on Android.
This was sampled each time an evicted tab was reloaded.
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.
jbbegue@google.com
Record the action executed when the user performs a pull down gesture. This
feature is currently iOS only.
A pull down gesture is an action completed when the user scrolls past the
edge of the web page and continues scrolling in the same direction revealing
a specific UI on the header with multiple actions icons. The user can then
choose an action by scrolling left or right and lift the finger or cancel by
scrolling back up. This is currently an iOS specific feature.
Deprecated 11/2016. No longer useful after finding out that it has no effect
on tab reactivation rates.
pmonette@chromium.org
A tab was reactivated after being hidden. This histogram also records if the
tab's URL was bookmarked.
pmonette@chromium.org
A tab was reactivated after being hidden. This histogram also records if the
tab had any form interaction.
pmonette@chromium.org
A tab was reactivated after being hidden. This histogram also records if the
tab was pinned to the tab strip.
jaekyun@chromium.org
The status of a tab and an application when a renderer crashes. This is
recorded only for Android when a renderer crashes.
wnwen@chromium.org
Breakdown of renderer exit status for renderers that have strong bindings.
An extension of the counts in Tab.RendererExitStatus. Only recorded on
Android.
wnwen@chromium.org
Breakdown of renderer exit status for renderers that do not have strong
bindings. An extension of the counts in Tab.RendererExitStatus. Only
recorded on Android.
wnwen@chromium.org
The status of a renderer when the browser notices that the process has
exited. Only recorded on Android.
gchatz@chromium.org
[iOS] A count of the number of alive renderers when a renderer termination
occurs.
gchatz@chromium.org
[iOS] The number of renderers which are either currently alive or recently
terminated at the time of a renderer termination.
gchatz@chromium.org
[iOS] Records whether a memory warning had recently been received before a
renderer termination.
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.
stuartmorgan@chromium.org
The state (foreground/background) of a tab when its renderer is terminated.
lliabraa@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
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
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.
csharrison@chromium.org
The position of the URL in the framebust UI list (desktop only) when it is
clicked. Note that this UI surface is shared with the framebusting
intervention, so elements in the list could come from either features. This
metric will only be logged when a URL from the tab under intervention is
clicked.
csharrison@chromium.org
Measures the engagement score associated with the URL that is detected as
the target of a tab-under navigation.
csharrison@chromium.org
Measures the time from when a tab opens a popup to when it performs a
tab-under (i.e. navigates cross origin, in the background without a user
gesture).
csharrison@chromium.org
Measures the total time a tab is visible after it navigates itself
cross-origin in the background, without a user gesture. The tab must have
opened a popup since the last user gesture in the tab. Measured at
WebContents destruction. The total visible time for the tab is the sum of
this metric and Tab.TabUnder.VisibleTimeBefore.
csharrison@chromium.org
Measures the total time a tab is visible before it navigates itself
cross-origin in the background, without a user gesture. The tab must have
opened a popup since the last user gesture in the tab. Measured at
WebContents destruction. The total visible time for the tab is the sum of
this metric and Tab.TabUnder.VisibleTime.
csharrison@chromium.org
Various actions related to the tab under intervention, logged during main
frame navigation.
Deprecated as of 10/2016.
lliabraa@chromium.org
[iOS] When an existing tab becomes active, this histogram records the time
since it was made inactive.
Deprecated as of 10/2016.
lliabraa@chromium.org
[iOS] When an evicted tab becomes active, this histogram records the time
since it was made inactive.
Deprecated as of 10/2016.
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.
pmonette@chromium.org
The time elapsed from the moment a tab was deactivated until it was
reactivated. Only recorded for tabs that are pinned or had form interaction.
pmonette@chromium.org
The time elapsed from the moment a tab was deactivated until it was
reactivated. Only recorded for tabs that are not pinned nor had form
interaction.
jaekyun@chromium.org
The total count of tabs which were kept while Chrome process is in the
foreground. This is recorded only for Android right before Chrome process
goes into the background.
fdoray@chromium.org
Time spent by a tab in a given visibility state. Recorded when the
visibility changes and when the tab is closed.
csharrison@chromium.org
Measures the total time a tab is visible. Measured at the WebContents layer
so this metric does not attempt to account for things like session restore.
Logged at WebContents destruction.
This metric was deprecated in favor of just using Tab.TabUnder.VisibleTime
directly. Consider bringing it back if we care about visible time after a
suspicious redirect without an associated popup.
csharrison@chromium.org
Measures the total time a tab is visible after it navigates itself
cross-origin in the background. Measured at WebContents destruction.
fmeawad@chromium.org
The expected queueing duration of tasks in a foreground tab during a
background tab opening session (the duration of time from when the browser
starts to open background tabs until the time the browser has finished
loading those tabs or otherwise decided to stop loading them). The metric
reflects the responsiveness of a tab. A lower value means the tab will
respond to inputs faster. This metric is equivalent to
RendererScheduler.ExpectedTaskQueueingDuration. It is emitted once for all
tasks in each 1000-ms window. The metric is not recorded when the session
overlaps with session restore.
zhenw@chromium.org
The loading state of a tab at the time the user switches to it during a
background tab opening session (the duration of time from when the browser
starts to open background tabs until the time the browser has finished
loading those tabs or otherwise decided to stop loading them). The metric is
only recorded when a tab is switched to from another tab within the same
tabstrip. As a result, the case when switching between different windows is
not included, either between two tabs in different browser windows, or when
switching to a different application and switching back to the browser. The
metric is not recorded when the session overlaps with session restore.
zhenw@chromium.org
The max number of background tabs pending or loading when opening background
tabs. This is recorded at the end of the background tab opening session (the
duration of time from when the browser starts to open background tabs until
the time the browser has finished loading those tabs or otherwise decided to
stop loading them). The metric is not recorded when the session overlaps
with session restore.
zhenw@chromium.org
The number of background tabs whose loading was triggered by TabManager
automatically when opening background tabs. This is recorded at the end of
the background tab opening session (the duration of time from when the
browser starts to open background tabs until the time the browser has
finished loading those tabs or otherwise decided to stop loading them). The
metric is not recorded when the session overlaps with session restore.
zhenw@chromium.org
Whether the tab load is timed out during background tab opening session (the
duration of time from when the browser starts to open background tabs until
the time the browser has finished loading those tabs or otherwise decided to
stop loading them). The metric is not recorded when the session overlaps
with session restore.
zhenw@chromium.org
The number of background tabs whose loading was triggered by user action
when opening background tabs. For example, when the user selects a
background tab and brings it to foreground, that tab will start to load
immediately if not already loading. This is recorded at the end of the
background tab opening session (the duration of time from when the browser
starts to open background tabs until the time the browser has finished
loading those tabs or otherwise decided to stop loading them). The metric is
not recorded when the session overlaps with session restore.
zhenw@chromium.org
The max number of background tabs paused to load due to memory pressure when
opening background tabs. This is recorded at the end of the background tab
opening session during a background tab opening session (the duration of
time from when the browser starts to open background tabs until the time the
browser has finished loading those tabs or otherwise decided to stop loading
them). The metric is not recorded when the session overlaps with session
restore.
georgesak@chromium.org
Cumulative number of tabs discarded due to low memory conditions, recorded
once per tab discard event. For example, a user who had 3 tabs discarded
records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is the
number of sessions where users experienced N or more tab discard events.
Deprecated 11/2017. Analysis showed that MRU was as good as engagement score
to choose which tabs to discard. The new plan is to build a machine learning
model to choose which tabs to discard.
georgesak@chromium.org
Site engagement score of a discarded tab. Recorded for each discard if the
score is available.
oysteine@chromium.org
Recorded for each discarding, indicates whether the discarded tab succeeded
in doing a render process fast shutdown or not.
oysteine@chromium.org
Recorded for each discarding, allowing us to know whether the discarded tab
succeeded an unsafe process shutdown (not invoking unload handlers).
georgesak@chromium.org
Recorded for each discarding, allowing us to know whether the discarded tab
had a before unload handler or not.
georgesak@chromium.org
Elapsed time between a tab getting discarded to eventually being reloaded by
the user.
georgesak@chromium.org
Elapsed time between the time a tab switched from being active to inactive
(that eventually gets discarded) until it gets reloaded.
Deprecated 07/2018, and replaced by
ResourceCoordinator.LocalDB.DatabaseInit.
sebmarchand@chromium.org
The result of opening the Local Site Characteristics database.
Deprecated 07/2018, and replaced by
ResourceCoordinator.LocalDB.DatabaseInitAfterDelete.
sebmarchand@chromium.org
The result of opening the Local Site Characteristics database after deleting
it after a failed repair attempt.
Deprecated 07/2018, and replaced by
ResourceCoordinator.LocalDB.DatabaseInitAfterRepair.
sebmarchand@chromium.org
The result of opening the Local Site Characteristics database after a repair
attempt.
Deprecated 07/2018, and replaced by
ResourceCoordinator.LocalDB.DatabaseRepair.
sebmarchand@chromium.org
The result of trying to repair the Local Site Characteristics database after
a failed open.
cywang@chromium.org
georgesak@chromium.org
Elapsed time to collect memory usage of each tab triggered by a LogMemory()
call().
georgesak@chromium.org
Cumulative number of discarded tabs that have been reloaded by the user,
recorded once per tab discard event. For example, a user who had 3 tabs
reloaded records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is
the number of sessions where users experienced N or more tab reload events.
Deprecated 11/2017. Analysis showed that MRU was as good as engagement score
to choose which tabs to discard. The new plan is to build a machine learning
model to choose which tabs to discard.
georgesak@chromium.org
Site engagement score of a reloaded tab. Recorded for each reload if the
score is available. Note that this will be the same score the tab had when
discarded (which could have changed by the time it gets reloaded).
georgesak@chromium.org
Elapsed time between the last time a discarded tab was reloaded and the time
it gets closed.
fmeawad@chromium.org
The number of pages compressed per second when opening background tabs. This
is recorded at the end of the background tab opening session as an average
over the entire period (the duration of time from when the browser starts to
open background tabs until the time the browser has finished loading those
tabs or otherwise decided to stop loading them). The metric is not recorded
when the session overlaps with session restore. Only recorded on macOS.
Warning: This metric is a ratio and the session interval differs for each
session. It is hard to tell if it is average rate for each second in the
interval or it has a huge spike.
fmeawad@chromium.org
The number of pages decompressed per second when opening background tabs.
This is recorded at the end of the background tab opening session as an
average over the entire period (the duration of time from when the browser
starts to open background tabs until the time the browser has finished
loading those tabs or otherwise decided to stop loading them). The metric is
not recorded when the session overlaps with session restore. Only recorded
on macOS. Warning: This metric is a ratio and the session interval differs
for each session. It is hard to tell if it is average rate for each second
in the interval or it has a huge spike.
fmeawad@chromium.org
The number of swap-ins per second when opening background tabs. This is
recorded at the end of the background tab opening session as an average over
the entire period (the duration of time from when the browser starts to open
background tabs until the time the browser has finished loading those tabs
or otherwise decided to stop loading them). The metric is not recorded when
the session overlaps with session restore. Warning: This metric is a ratio
and the session interval differs for each session. It is hard to tell if it
is average rate for each second in the interval or it has a huge spike.
fmeawad@chromium.org
The number of swap-outs per second when opening background tabs. This is
recorded at the end of the background tab opening session as an average over
the entire period (the duration of time from when the browser starts to open
background tabs until the time the browser has finished loading those tabs
or otherwise decided to stop loading them). The metric is not recorded when
the session overlaps with session restore. Warning: This metric is a ratio
and the session interval differs for each session. It is hard to tell if it
is average rate for each second in the interval or it has a huge spike.
Deprecated 08/2017, and replaced by
TabManager.Experimental.BackgroundTabOpening.TabSwitchLoadTime.UntilTabIsLoaded.
zhenw@chromium.org
The tab load time of a tab that is switched to during a background tab
opening session (the duration of time from when the browser starts to open
background tabs until the time the browser has finished loading those tabs
or otherwise decided to stop loading them). Tab load time is defined as the
time between when the user switches to a backround tab, and the time when
that tab finishes loading in the foreground. If the user switches away
before the tab finishes loading, a metric will not be recorded unless the
user switches back, in which case the tab load time is measured from that
point in time. The metric is only recorded when a tab is switched to from
another tab within the same tabstrip. As a result, the initial forground tab
is not included in this metric since it was not switched to from another
tab. The metric is not recorded when the session overlaps with session
restore.
zhenw@chromium.org
The tab load time of a tab that is switched to during a background tab
opening session (the duration of time from when the browser starts to open
background tabs until the time the browser has finished loading those tabs
or otherwise decided to stop loading them). Tab load time is defined as the
time between when the user switches to a backround tab, and the time when
that tab finishes loading in the foreground. If the user switches away
before the tab finishes loading, a metric will not be recorded unless the
user switches back, in which case the tab load time is measured from that
point in time. The metric is only recorded when a tab is switched to from
another tab within the same tabstrip. As a result, the initial forground tab
is not included in this metric since it was not switched to from another
tab. The metric is not recorded when the session overlaps with session
restore.
fmeawad@chromium.org
The number of pages compressed per second during session restore. Recorded
at the end of session restore as an average over the entire period, defined
as the period of time when session restore is actively loading tabs, which
ends when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure. The metric is not recorded when the session overlaps with
background tab opening session. Only recorded on macOS. Warning: This metric
is a ratio and the session interval differs for each session. It is hard to
tell if it is average rate for each second in the interval or it has a huge
spike.
fmeawad@chromium.org
The number of pages decompressed per second during session restore. Recorded
at the end of session restore as an average over the entire period, defined
as the period of time when session restore is actively loading tabs, which
ends when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure. The metric is not recorded when the session overlaps with
background tab opening session. Only recorded on macOS. Warning: This metric
is a ratio and the session interval differs for each session. It is hard to
tell if it is average rate for each second in the interval or it has a huge
spike.
fmeawad@chromium.org
Elapsed time between the start of the loading and the first contentful paint
of foreground tabs when the browser loads tabs in session restore.
fmeawad@chromium.org
Elapsed time between the start of the loading and the first meaningful paint
of foreground tabs when the browser loads tabs in session restore.
fmeawad@chromium.org
Elapsed time between the start of the loading and the first paint of
foreground tabs when the browser loads tabs in session restore.
fmeawad@chromium.org
The number of swap-ins per second during session restore. Recorded at the
end of session restore as an average over the entire period, defined as the
period of time when session restore is actively loading tabs, which ends
when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure. The metric is not recorded when the session overlaps with
background tab opening session. Warning: This metric is a ratio and the
session interval differs for each session. It is hard to tell if it is
average rate for each second in the interval or it has a huge spike.
fmeawad@chromium.org
The number of swap-outs per second during session restore. Recorded at the
end of session restore as an average over the entire period, defined as the
period of time when session restore is actively loading tabs, which ends
when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure. The metric is not recorded when the session overlaps with
background tab opening session. Warning: This metric is a ratio and the
session interval differs for each session. It is hard to tell if it is
average rate for each second in the interval or it has a huge spike.
Deprecated 08/2017, and replaced by
TabManager.Experimental.SessionRestore.TabSwitchLoadTime.UntilTabIsLoaded.
fmeawad@chromium.org
The tab load time of a tab that is switched to during a session restore. Tab
load time is defined as the time between when the user switches to a
backround tab, and the time when that tab finishes loading in the
foreground. If the user switches away before the tab finishes loading, a
metric will not be recorded unless the user switches back, in which case the
tab load time is measured from that point in time. The metric is only
recorded when a tab is switched to from another tab within the same
tabstrip. As a result, the initial forground tab is not included in this
metric since it was not switched to from another tab. The metric is only
recorded when session restore is actively loading tabs, which ends when
either all tabs have been loaded and their pages rendered, or tab loading
needs to be deferred in cases where the system is under memory pressure. The
metric is not recorded when the session overlaps with background tab opening
session.
fmeawad@chromium.org
The tab load time of a tab that is switched to during a session restore. Tab
load time is defined as the time between when the user switches to a
backround tab, and the time when that tab finishes loading in the
foreground. If the user switches away before the tab finishes loading, a
metric will not be recorded unless the user switches back, in which case the
tab load time is measured from that point in time. The metric is only
recorded when a tab is switched to from another tab within the same
tabstrip. As a result, the initial forground tab is not included in this
metric since it was not switched to from another tab. The metric is only
recorded when session restore is actively loading tabs, which ends when
either all tabs have been loaded and their pages rendered, or tab loading
needs to be deferred in cases where the system is under memory pressure. The
metric is not recorded when the session overlaps with background tab opening
session.
chrisha@chromium.org
lpy@chromium.org
Measures the time duration from when the tab is backgrounded to when a
JavaScript alert is updated. Only recorded when the tab is in the
background.
chrisha@chromium.org
lpy@chromium.org
Measures the time duration from when the tab is backgrounded to when audio
starts to play. Only recorded when the tab is in the background.
chrisha@chromium.org
lpy@chromium.org
Measures the time duration from when the tab is backgrounded to when its
favicon is updated. The first-time set of favicon will be ignored; this
metric will only be recorded after 5 minutes from main frame navigation
committed and when the tab is in the background.
chrisha@chromium.org
lpy@chromium.org
Measures the time duration from when the tab is backgrounded to when a
non-persistent notification is created. Only recorded when the tab is in the
background.
chrisha@chromium.org
lpy@chromium.org
Measures the time duration from when the tab is backgrounded to when its
title is updated. The first-time set of title will be ignored; this metric
will only be recorded after 5 minutes from main frame navigation committed
and when the tab is in the background.
zhenw@chromium.org
Whether background tab opening session is overlapped with other types of
session, e.g., session restore. Background tab opening session is the
duration of time from when the browser starts to open background tabs until
the time the browser has finished loading those tabs or otherwise decided to
stop loading them. This metric helps to understand how often background tab
opening has overlap with other sessions.
zhenw@chromium.org
Whether session restore is overlapped with other types of session, e.g.,
background tab opening. Session restore is the duration from the time when
the browser starts to restore tabs until the time when the browser has
finished loading those tabs or when the browser stops loading tabs due to
memory pressure. This metric helps to understand how often session restore
has overlap with other sessions.
Deprecated 08/2017, and replaced by
TabManager.Experimental.SessionRestore.CompressedPagesPerSecond.
fmeawad@chromium.org
The number of pages compressed per second during session restore. Recorded
at the end of session restore as an average over the entire period, defined
as the period of time when session restore is actively loading tabs, which
ends when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure. Only recorded on macOS.
Deprecated 08/2017, and replaced by
TabManager.Experimental.SessionRestore.DecompressedPagesPerSecond.
fmeawad@chromium.org
The number of pages decompressed per second during session restore. Recorded
at the end of session restore as an average over the entire period, defined
as the period of time when session restore is actively loading tabs, which
ends when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure. Only recorded on macOS.
fmeawad@chromium.org
The expected queueing duration of tasks in a foreground tab during session
restore. This metric reflects the responsiveness of a tab. A lower value
means the tab will respond to inputs faster. This metric is equal to
RendererScheduler.ExpectedTaskQueueingDuration. It is emitted once for all
tasks in each 1000-ms window. The metric is not recorded when the session
overlaps with background tab opening session.
Deprecated 08/2017, and replaced by
TabManager.Experimental.SessionRestore.SwapInPerSecond.
fmeawad@chromium.org
The number of swap-ins per second during session restore. Recorded at the
end of session restore as an average over the entire period, defined as the
period of time when session restore is actively loading tabs, which ends
when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure.
Deprecated 08/2017, and replaced by
TabManager.Experimental.SessionRestore.SwapOutPerSecond.
fmeawad@chromium.org
The number of swap-outs per second during session restore. Recorded at the
end of session restore as an average over the entire period, defined as the
period of time when session restore is actively loading tabs, which ends
when either all tabs have been loaded and their pages rendered, or tab
loading needs to be deferred in cases where the system is under memory
pressure.
fmeawad@chromium.org
The loading state of a tab at the time the user switched to it during a
session restore. The metric is only recorded when a tab is switched to from
another tab within the same tabstrip. As a result, there are two cases where
tabs are not included. The first case is when the initial forground tab is
shown, since it was not switched to from another tab. The second case is
when switching between different windows, either between two tabs in
different browser windows, or when switching to a different application and
switching back to the browser. The metric is only recorded when session
restore is actively loading tabs, which ends when either all tabs have been
loaded and their pages rendered, or tab loading needs to be deferred in
cases where the system is under memory pressure. The metric is not recorded
when the session overlaps with background tab opening session.
michaelpg@chromium.org
charleszhao@chromium.org
Logged when calculating a tab reactivation score for a background tab. Any
value other than "none" may indicate a bug in the inference code,
a problem with the preprocessor configuration shipped with the model, or a
bug in the code that populates the RankerExample for a tab.
sky@chromium.org
Error code returned by [moveItemAtPath:toPath:error:] when moving previous
session file to backup file before restoring. 0 in case of success.
sky@chromium.org
Error code returned by [removeItemAtPath:error:] when removing previous
session backup file. 0 in case of success.
sky@chromium.org
Error code returned by [removeItemAtPath:error:] when removing previous
session file. 0 in case of success.
lliabraa@chromium.org
The number of tabs open when the app comes out of the background.
lliabraa@chromium.org
The number of tabs open at cold launch.
Deprecated 10/2015, and replaced by TabManager.Discarding.DiscardCount.
jamescook@chromium.org
Cumulative number of tabs discarded due to low memory conditions, recorded
once per tab discard event. For example, a user who had 3 tabs discarded
records a count in the 1 bin, 2 bin and 3 bin. Thus each bin N is the
number of sessions where users experienced N or more tab discard events.
Deprecated 11/2017. Average number of minutes between discard events is
available in Tabs.Discard.InitialTime2 and Tabs.Discard.IntervalTime2.
jamescook@chromium.org
Whether or not a tab was discarded in the last minute of usage. Total count
is number of minutes of device usage. 100 / discard percentage gives the
average number of minutes between discard events.
Deprecated May 4, 2012. Replaced by Tabs.Discard.InitialTime2 because this
stat had too low of a range maximum. No longer tracked.
jamescook@chromium.org
Time in seconds between system startup and when the first tab is discarded
due to low memory conditions. Higher is better.
Deprecated 11/2017. Replaced with Discarding.Urgent.TimeSinceStartup which
is recorded when Chrome has to discard tabs or apps urgently (instead of
before an individual tab is urgently or proactively discarded).
jamescook@chromium.org
Time in seconds between system startup and when the first tab is discarded
due to low memory conditions. Higher is better. Range maximum is
approximately one day.
Deprecated May 4, 2012. Replaced by Tabs.Discard.IntervalTime2 because this
stat had too low of a range maximum. No longer tracked.
jamescook@chromium.org
Time in seconds between tab discard events after the first one, recorded
once per discard event. Higher is better.
Deprecated 11/2017. Replaced with Discarding.Urgent.TimeSinceLastUrgent
which is recorded before a set of tabs/apps are urgently discarded (instead
of before an individual tab is urgently or proactively discarded).
jamescook@chromium.org
Time in milliseconds between tab discard events after the first one,
recorded once per discard event. Should occur no faster than once every 750
ms. Higher is better.
jamescook@chromium.org
System-wide memory allocation at the time a tab was discarded, roughly
equivalent to the sum of memory allocated with malloc() in userspace plus
graphics driver memory.
Deprecated December 7, 2012. Replaced by Tabs.Discard.MemAllocatedMB
because this stat has insufficient precision in the 2-4 GB range and does
not properly account for graphics memory on ARM.
jamescook@chromium.org
System-wide anonymous memory allocation at the time a tab was discarded,
roughly equivalent to memory allocated with malloc().
jamescook@chromium.org
System-wide file-backed memory plus free memory, roughly equivalent to what
the kernel uses to trigger low-memory notifications for tab discards. If
lower than the kernel's threshold then we are not effectively freeing memory
in response to the initial notification and are repeatedly being notified.
jamescook@chromium.org
Graphics driver (GEM object) memory at the time of a tab discard.
jamescook@chromium.org
System-wide shared memory at the time of a tab discard. Used primarily for
shared buffers in the graphics system. Tracked because it's a historical
source of leaks on Chrome OS.
Deprecated 10/2015, and replaced by TabManager.Discarding.ReloadCount.
jamescook@chromium.org
Cumulative number of times a tab was reloaded because it was discarded and
the user clicked on it later, recorded once per reload event. For example,
a user who clicks on 3 discarded tabs will record a count in the 1 bin, 2
bin, and 3 bin. Thus each bin N is the number of sessions where users
experienced N or more reload events. Compare to Tabs.Discard.DiscardCount.
Deprecated 11/2017. Replaced with Discarding.Urgent.NumAliveTabs which
records the number of tabs that are not pending load or discarded when an
urgent discard request is received (vs. this that records the total number
of tabs every time a tab is discarded, no matter the reason).
jamescook@chromium.org
The number of tabs open across all browser windows when a tab was discarded
due to low memory conditions.
joenotcharles@chromium.org
Fine-grained (in msec) time between closing a tab and opening another, to
track very frequent tabs.
joenotcharles@chromium.org
Fine-grained (in msec) time between opening a tab and opening another, to
track very frequent tabs.
joenotcharles@chromium.org
Fine-grained (in msec) time between opening a tab and closing it, to track
very short-lived tabs.
pkotwicz@chromium.org
Records the "Tab Creation Rank" for the first background tab which
was switched to the foreground. The "Tab Creation Rank" is
relative to other background tabs which were opened from the same URL via
the context menu. The oldest background tab has a rank of zero.
pkotwicz@chromium.org
Records the "Reverse Tab Creation Rank" for the first background
background tab which was switched to the foreground. The "Reverse Tab
Creation Rank" is relative to other background tabs which were opened
from the same URL via the context menu. The newest background tab has a
"Reverse Tab Creation Rank" of zero.
lliabraa@chromium.org
Age (time since the last display in previous sessions) of the foreground tab
being restored on the browser cold start.
pauljensen@chromium.org
Page load time (PLT) for iOS that does not include time spent following
redirects. On other platforms this is calculated from Navigation Timings but
on iOS Navigation Timings are not available so we're recreating a
calculation similar to PLT.PT_RequestToFinish but not including time spent
following redirects. This metric represents the time between when navigation
is initiated (prior to DNS, TCP connect, etc but after following redirects)
until loading ends (i.e. JS onload event). On non-iOS Chrome this is
(performance.timing.loadEventEnd - performance.timing.redirectEnd). On
Chrome for iOS we're calculating the time between the creation of the
top-level URLRequest and when webDidFinishWithURL is called.
sebmarchand@chromium.org
The maximum number of tabs that Chrome displays at the same time over the
course of a day.
sebmarchand@chromium.org
The maximum number of tabs per window that Chrome displays over the course
of a day.
sebmarchand@chromium.org
The maximum number of windows existing at the same time over the course of a
day.
sebmarchand@chromium.org
The number of tabs total at resume from sleep/hibernate. This is being
logged on all desktop platforms.
jamescook@chromium.org
Cumulative number of times a tab crashed with "Aw, Snap!",
recorded once per tab crash event. For example, a user who crashed 3 tabs
will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the
number of sessions where users experienced N or more crash events. The user
may not have actually seen the sad tab page, as it might have been an
inactive tab. Compare to Tabs.SadTab.CrashDisplayed.
jamescook@chromium.org
Cumulative number of times a tab crashed with "Aw, Snap!" and the
user saw the page, recorded once per tab crash event. For example, a user
who crashed 3 tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus
each bin N is the number of sessions where users experienced N or more crash
events. Compare to Tabs.SadTab.CrashCreated.
sdy@chromium.org
Counts of events from the style of sad tab which has a feedback button as
its primary action. Currently, events include being displayed (actually
visible in a window), and the actions a user can take on the page.
jamescook@chromium.org
Cumulative number of times a tab was killed with a "He's dead,
Jim!" page, which is usually due to the renderer being killed, recorded
once per tab kill event. For example, a user who loses 3 tabs will record a
count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of
sessions where users experienced N or more kill events. The user may not
have actually seen the sad tab page, as it might have been an inactive tab.
Compare to Tabs.SadTab.KillDisplayed. This can happen due to out of memory,
malformed IPC messages, or a SIGINT/TERM/KILL signal sent by a user.
oshima@chromium.org
Cumulative number of times a tab was killed with a "He's dead,
Jim!" page due to the kernel out-of-memory killer, recorded once per
tab kill event. For example, a user who loses 3 tabs will record a count in
the 1 bin, 2 bin, and 3 bin. Thus each bin N is the number of sessions
where users experienced N or more kill events. The user may not have
actually seen the sad tab page, as it might have been an inactive tab.
Compare to Tabs.SadTab.KillDisplayed.
jamescook@chromium.org
Cumulative number of times a tab was killed with a "He's dead,
Jim!" page and the user saw the page, recorded once per tab kill event.
For example, a user who loses 3 tabs will record a count in the 1 bin, 2
bin, and 3 bin. Thus each bin N is the number of sessions where users
experienced N or more kill events. Compare to Tabs.SadTab.CrashCreated.
oshima@chromium.org
Cumulative number of times a tab was killed with a "He's dead,
Jim!" page due to the kernel out-of-memory killer and the user saw the
page, recorded once per tab kill event. For example, a user who loses 3
tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is
the number of sessions where users experienced N or more kill events.
Compare to Tabs.SadTab.CrashCreated.
wfh@chromium.org
Cumulative number of times a tab crashed with "Aw, Snap!",
recorded once per tab oom event. For example, a user who ran out of memory
in 3 tabs will record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin
N is the number of sessions where users experienced N or more oom events.
The user may not have actually seen the sad tab page, as it might have been
an inactive tab. Compare to Tabs.SadTab.OomDisplayed.
wfh@chromium.org
Cumulative number of times a tab ran out of memory with "Aw,
Snap!" and the user saw the page, recorded once per tab oom event. For
example, a user who ran out of memory in 3 tabs will record a count in the 1
bin, 2 bin, and 3 bin. Thus each bin N is the number of sessions where
users experienced N or more oom events. Compare to Tabs.SadTab.OomCreated.
sdy@chromium.org
Counts of events from the style of sad tab which has a reload button as its
primary action. Compare to Tabs.SadTab.Feedback.Event.
jamescook@chromium.org
The number of times a tab was reloaded because it was killed (usually by the
kernel OOM killer) and the user clicked on it later, recorded once per
reload event. For example, a user who clicks on 3 discarded tabs will
record a count in the 1 bin, 2 bin, and 3 bin. Thus each bin N is the
number of sessions where users experienced N or more reload events. Compare
to Tabs.Discard.DiscardCount.
Please list the metric's owners. Add more owner tags as needed.
The distance a user 3 finger scrubbed to change tabs. Always positive
(ignores left / right).
lliabraa@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
Accuracy of the tab switch predictions made when the user begins the side
swipe gesture.
lliabraa@chromium.org
Accuracy of the tab switch predictions made when the user enters the tab
switcher.
lliabraa@chromium.org
Status of a tab recorded when the tab is targeted with speculative restore.
lliabraa@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
Time between starting the speculative load and actual tab switch for correct
speculative load predictions made when the user enters the tab switcher.
kouhei@chromium.org
tzik@chromium.org
Recorded once per tab activation. The number of tabs that were activated
while the tab was inactive.
This metric is to be removed after M46 hits stable. We don't expect this
metric to change over release, so we will remove this once we have the
numbers from stable.
kouhei@chromium.org
tzik@chromium.org
Number of tabs between the previously active tab and the new active tab.
This metric is to be removed after M46 hits stable. We don't expect this
metric to change over release, so we will remove this once we have the
numbers from stable.
kouhei@chromium.org
tzik@chromium.org
The state to which a tab transitioned. Recorded when a tab transitions from
the state in the histogram name to a new state.
kouhei@ and tzik@ will remove some variation of these once M46 hits stable.
Deprecated as of 4/2017.
kouhei@chromium.org
tzik@chromium.org
Tabs.StateTransfer.TimeA_B measures the time a tab was in state A before it
transferred to state B.
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.
rlanday@chromium.org
How many tabs a user moved forward or backward in the Android tab switcher.
Logged by the Android tab switcher when a user switches tabs (other than by
opening a new tab). If the user switches to an earlier tab in the stack, we
log a positive offset value indicating how many tabs back they moved. If the
user switches to a later tab, we log a negative offset value. If the user
stays on the same tab, we log 0. If the user switches to a tab in a
different stack (i.e. they switch from normal to incognito or vice-versa),
we don't log a value.
sebmarchand@chromium.org
Counts how often tab stats daily interval events were fired.
yusufo@chromium.org
wychen@chromium.org
The average tab group size, average number of tabs in a group, on a cold
start after all tabs are restored.
yusufo@chromium.org
wychen@chromium.org
The cumulative number of "spokes" from any "hub" page in
every tab. A "hub" is any page that the user navigates away from,
and a "spoke" is a page that's navigated to. The
"spokes" count is incremented and recorded each time the user
navigates back to a "hub" page via navigation back button and then
navigates to a new "spoke".
yusufo@chromium.org
wychen@chromium.org
The number of tab groups on a cold start after all tabs are restored.
yusufo@chromium.org
wychen@chromium.org
The tab group density, the ratio of the number of tab groups to the total
number of tabs, on a cold start after all tabs are restored.
yusufo@chromium.org
wychen@chromium.org
The number of tabs is belonging to a tab group on a cold start after all
tabs are restored.
yusufo@chromium.org
wychen@chromium.org
The ratio of all tabs in tab groups to the total number of tabs on a cold
start after all tabs are restored.
alexmos@chromium.org
dcheng@chromium.org
Reports the delta between the last user interaction time with a WebContents
and the time browser code wants to verify a recent user interaction with
that WebContents. Used to tune the threshhold for timing out a user
interaction.
sebmarchand@chromium.org
The number of tabs that haven't been interacted with, visible or audible
over a given interval time, but which no longer exist at all at the end of
this interval.
sebmarchand@chromium.org
The number of tabs that haven't been interacted with, visible or audible or
visible during a given interval of time and still exist at the end of this
interval.
sebmarchand@chromium.org
The number of tabs that have been interacted with, visible or audible over a
given interval of time, but which no longer exist at all at the end of this
interval.
sebmarchand@chromium.org
The number of tabs that have been interacted with, visible or audible during
a given interval of time, includes tabs that don't exist at the end of this
interval.
afakhry@chromium.org
The requested window creation state from the tabs extensions API when it's
used to create a new window or update the state of an existing one.
altimin@chromium.org
farahcharab@chromium.org
Used to track the number of active task queues in the task queue manager.
Reported every time a task is selected for execution.
altimin@chromium.org
farahcharab@chromium.org
Used to track the number of tasks serviced due to starvation versus the
number of tasks serviced due to priroity. Incremented whenever a task queue
is selected to service.
fdoray@chromium.org
Number of BLOCK_SHUTDOWN tasks that were posted to a base::TaskScheduler
after its Shutdown() method was called but before it returned.
fdoray@chromium.org
gab@chromium.org
robliao@chromium.org
Time elapsed between when the thread managed by a SchedulerWorker is
detached and when the main function of a new thread managed by the same
SchedulerWorker is entered (following a wake up). Recorded each time that a
thread is recreated for a given SchedulerWorker.
fdoray@chromium.org
gab@chromium.org
robliao@chromium.org
Latency of dummy "heartbeat" tasks posted with specific traits
(see suffix). The heartbeat recording avoids dependencies between this
report and other work in the system. See
TaskScheduler.TaskLatencyMicroseconds.* for a metric that is closer to the
real workload.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
fdoray@chromium.org
gab@chromium.org
robliao@chromium.org
Number of tasks executed by a SchedulerWorker before it detached. Recorded
when a SchedulerWorker detaches.
fdoray@chromium.org
gab@chromium.org
robliao@chromium.org
Number of tasks executed by a SchedulerWorker between two waits on its
WaitableEvent. This should be maximized without affecting perceived browser
performance.
Deprecated 4/2017. Units changed from milliseconds to microseconds.
fdoray@chromium.org
gab@chromium.org
robliao@chromium.org
Time elapsed between when a task is posted and when it starts to run.
Recorded for each task that runs inside the TaskScheduler. This metric is
useful to determine true latency of the average task in the average runtime
scenario. Its total count can also be used as a proxy for the number of
tasks posted to a given category. On the other hand, a fallout of this
metric is that timing every task means each report is dependent on the many
things that can cause an individual task to be delayed (e.g. tasks on a
single bogged down sequence will be reported with high latency even if not
stalling the scheduler itself). See
TaskScheduler.HeartbeatLatencyMicroseconds.* for a metric that is
independent of such factors.
fdoray@chromium.org
gab@chromium.org
robliao@chromium.org
Time elapsed between when a task is posted and when it starts to run.
Recorded for each task that runs inside the TaskScheduler.
dmazzoni@chromium.org
Events fired by the text-to-speech engine when speaking an utterance.
katie@chromium.org
dtseng@chromium.org
dmazzoni@chromium.org
The user picked a default voice of the specified voice ID, which is hashed
from a JSON string of the voice name and extension ID.
katie@chromium.org
dtseng@chromium.org
dmazzoni@chromium.org
When the user requests a preview of a text-to-speech voice, records which
voice was previewed.
dmazzoni@chromium.org
Indicates if an utterance spoken via synthesized text-to-speech was
triggered by the Chrome TTS extension API or the web speech API.
dmazzoni@chromium.org
True if an utterance spoken via synthesized text-to-speech requested a
specific gender.
dmazzoni@chromium.org
True if an utterance spoken via synthesized text-to-speech specified a
language code.
dmazzoni@chromium.org
True if an utterance spoken via synthesized text-to-speech requested a
specific pitch other than the default.
dmazzoni@chromium.org
True if an utterance spoken via synthesized text-to-speech requested a
specific speech rate other than the default.
dmazzoni@chromium.org
True if an utterance spoken via synthesized text-to-speech requested a
specific voice by name.
dmazzoni@chromium.org
True if an utterance spoken via synthesized text-to-speech requested a
specific volume other than the default.
dmazzoni@chromium.org
True if an utterance is spoken with native speech provided by the operating
system, otherwise it's spoken via a Chrome extension that implements
text-to-speech support.
dmazzoni@chromium.org
The length of an utterance to be spoken via synthesized text-to-speech.
katie@chromium.org
dtseng@chromium.org
dmazzoni@chromium.org
True if a voice parsed from a ttsEngine extension manifest has a specific
gender. This is recorded each time a TTS extension is parsed, which may
occur multiple times per extension, in tts_engine_manifest_handler:
TtsVoices::Parse.
katie@chromium.org
dtseng@chromium.org
dmazzoni@chromium.org
True if a voice specified in chrome.ttsEngine.updateVoices by a ttsEngine
extension has a specific gender.
chrisha@chromium.org
The total number of certificates for modules loaded (or potentially loaded)
into the browser process that are signed by Microsoft. A catalog counts as a
single certificate, and may refer to many modules. Measured shortly after
startup. Windows only.
chrisha@chromium.org
The total number of certificates for modules loaded (or potentially loaded)
into the browser process. A catalog counts as a single certificate, and may
refer to many modules. Measured shortly after startup. Windows only.
pmonette@chromium.org
Records whether an equivalent driver letter path was found for a device
path.
pmonette@chromium.org
The number of registered input method editors found on the user's machine.
This is emitted shortly after startup when the IME enumeration takes place.
pmonette@chromium.org
Records the time it took to gather the list of installed third-party
programs and their install location or components.
pmonette@chromium.org
Records whether retrieving the current user SID was successful.
Deprecated 12/2017.
pmonette@chromium.org
Records the size of the in-memory representation of the installed
third-party programs on the user's machine.
Deprecated 07/2018.
pmonette@chromium.org
Records the time it took to gather the list of installed third-party
programs and their install location or components.
chrisha@chromium.org
The total number of third-party modules (neither Microsoft nor Google) that
are loaded in the browser process. Measured shortly after startup. Windows
only.
chrisha@chromium.org
The total number of third-party modules (neither Microsoft nor Google) that
are not yet loaded in the browser process, but may potentially be (shell
extensions, for example). Measured shortly after startup. Windows only.
chrisha@chromium.org
The total number of signed modules loaded (or potentially loaded) into the
browser process. Measured shortly after startup. Windows only.
chrisha@chromium.org
The total number of modules loaded (or potentially loaded) into the browser
process that are signed via a catalog. Measured shortly after startup.
Windows only.
chrisha@chromium.org
The total number of modules loaded (or potentially loaded) into the browser
process that are signed by Microsoft. Measured shortly after startup.
Windows only.
chrisha@chromium.org
The total number of modules loaded (or potentially loaded) into the browser
process. Measured shortly after startup. Windows only.
pmonette@chromium.org
The number of registered shell extensions found on the user's machine. This
is emitted shortly after startup when the shell extensions enumeration takes
place.
pmonette@chromium.org
Indicates whether the TimeDateStamp for a loaded module was successfully
obtained.
pmonette@chromium.org
Records whether or not a loaded third party module could be uninstalled
using the Windows Apps & Features page.
rch@chromium.org
The time it takes indicated thread to respond with a pong message for a ping
message from WatchDog thread.
rch@chromium.org
This is the total number of watched threads that are responding when we got
no response from the watched thread.
rch@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.
rch@chromium.org
This is the total number of watched threads that are not responding when we
got no response from the watched thread.
treib@chromium.org
A page thumbnail (for use on the New Tab page) was added to TopSites.
treib@chromium.org
The result of trying to capture a thumbnail of the current page.
treib@chromium.org
While taking a screenshot of the current tab for use as a thumbnail on the
New Tab page, the time it took to copy the tab's contents into a bitmap.
peconn@chromium.org
The time it takes to detect whether a thumbnail requires a gradient overlay.
This is run when thumbnails are downloaded for content suggestions, as they
load and the result is cached for future use. It is Android specific.
peconn@chromium.org
Whether a thumbnail used for a suggestions image requires a gradient to be
overlaid to not fade into the background. It applies to the thumbnails used
for content suggestions and is Android specific.
treib@chromium.org
While taking a screenshot of the current tab for use as a thumbnail on the
New Tab page, the time it took to post-process the captured bitmap.
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.
xidachen@chromium.org
ericrk@chromium.org
The amount of GPU memory, in kilobytes. Recorded on devices with less than
or equal to 512MB of memory and when tile manager had sufficient memory to
schedule all visible tiles.
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.
rdevlin.cronin@chromium.org
The number of component action icons the Browser Actions Container knows
about (visible or in the overflow bucket). Does not count icons that have
been permanently hidden by the user. Measured once per startup per
(non-incognito) profile.
rdevlin.cronin@chromium.org
The total number of action icons the Browser Actions Container knows about
(visible or in the overflow bucket). Does not count icons that have been
permanently hidden by the user. Measured once per startup per
(non-incognito) profile.
rdevlin.cronin@chromium.org
The number of visible toolbar icons in the Browser Actions Container
(visible as in number of icons not in the overflow bucket). 0 means all
icons are in the overflow bucket. MAX_INT means the toolbar is always
showing all icons. Measured once per startup per (non-incognito) profile but
only for those profiles that have one or more browser actions showing in the
toolbar.
rdevlin.cronin@chromium.org
The number of millseconds between when the user opens the app menu and when
the app menu is closed. Logged once per app menu run when the menu closes.
Not recorded for menu runs that are initiated by a drag-and-drop sequence.
Note that the code paths for Views-platforms vs Mac are different, so cross-
platform comparison may not always be reasonable.
peterlaurens@chromium.org
The number of millseconds between the user requesting a new incognito tab,
e.g. by tapping the New Incognito Tab entry in the main tools menu, and it
completing its animation on screen.
peterlaurens@chromium.org
The number of millseconds between the user requesting a new tab, e.g. by
tapping the New Tab entry in the main tools menu, and it completing its
animation on screen.
peterlaurens@chromium.org
Number of milliseconds passed between the event that triggers the
presentation of the tools menu (the main menu of actions accessed from the
toolbar), and the actual appearance of the menu on screen. Includes the
animation duration.
peterlaurens@chromium.org
The number of millseconds between the user requesting a new incognito tab,
from within the tab switcher, e.g. by tapping the New Tab button from the
tab switcher UI, and it completing its animation on screen.
peterlaurens@chromium.org
The number of millseconds between the user requesting a new tab, from within
the tab switcher UI, e.g. by tapping the New Tab button from the tab
switcher UI, and it completing its animation on screen.
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.
hayleyferr@chromium.org
xidachen@chromium.org
Tracks how often each touch action is allowed (AKA the frequency of each
effective touch action) at the end of each touch sequence.
hayleyferr@chromium.org
xidachen@chromium.org
Tracks how often the effective touch action computed by blink is or is not
equivalent to the whitelisted touch action computed by the compositor at the
end of each touch sequence.
hayleyferr@chromium.org
xidachen@chromium.org
Tracks how often a gesture event is or is not dropped due to the current
allowed touch action state not matching the gesture event.
spqchan@chromium.org
Tracks the usage of the default touch bar buttons.
pthammaiah@google.com
Tracks touchpad device state.
Deprecated 8/2017.
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
input-dev@chromium.org
The touch device driver failed to send a TOUCHEVENTF_UP, and chromium
generated a simulated event to maintain consistency/correctness.
This workaround will be removed once usage drops off. See
https://crbug.com/811273 for details.
aelias@chromium.org
How the user interacted with the tap disambiguation feature on Android.
tdresser@chromium.org
Tracks whether Touch Event Feature Detection is enabled. This is based on
the touch events enabled flag and the presence of a touchscreen.
Team: input-dev@chromium.org.
NOTE: This metric was incorrectly recorded on Chrome OS for versions 42
through 45, see http://crbug.com/499476 for more details. As of
http://crbug.com/644318, we changed the internal name to
TouchEventFeatureDetection, but we still keep the old histogram name here to
keep consistensy.
semenzato@google.com
Reported at boot if the previous boot session was interrupted in the middle
of a TPM command during the first 30 seconds of uptime.
oysteine@chromium.org
The size, in kilobytes, of a finalized trace ready to be uploaded.
oysteine@chromium.org
Records state of the Background Tracing system, from when scenarios are
attempted to be activated until they're completed (successfully or failed)
Deprecated as of 09/2017. Code measured by this histogram no longer exists.
fdoray@chromium.org
Time spent in base::ThreadData::GetRetiredOrCreateThreadData(). This method
is called at most once per thread, when its name is set, when it posts a
task or when it runs a task (whichever comes first).
Deprecated 2018/07.
sclittle@chromium.org
bengr@chromium.org
The amount of time spent waiting to perform an amortization run. This is
logged at the end of each amortization run, before passing any DataUse
objects to their respective callbacks.
Deprecated 2018/07.
sclittle@chromium.org
bengr@chromium.org
The number of DataUse objects processed in an amortization run.
Deprecated 2018/07.
sclittle@chromium.org
bengr@chromium.org
The number of unique tabs seen across all DataUse objects buffered for a
single amortization run by the TrafficStatsAmortizer. This is recorded even
if TrafficStats byte counts are unavailable, but not recorded if no DataUse
objects have been buffered.
Deprecated 2018/07.
sclittle@chromium.org
bengr@chromium.org
The total bytes after performing amortization across all DataUse objects
buffered for a single amortization run by the TrafficStatsAmortizer. This is
recorded even if TrafficStats byte counts are unavailable, but not recorded
if no DataUse objects have been buffered.
Deprecated 2018/07.
sclittle@chromium.org
bengr@chromium.org
The total bytes before performing amortization across all DataUse objects
buffered for a single amortization run by the TrafficStatsAmortizer. This is
recorded even if TrafficStats byte counts are unavailable, but not recorded
if no DataUse objects have been buffered.
googleo@chromium.org
Time taken for the TranslateAcceptLanguages to decide if a given language is
available as Accept-Languages.
kenjibaheux@google.com
The number of times the always translate option was selected in the
translate infobar.
groby@google.com
Tracks UI events related to the translate bubble.
kenjibaheux@google.com
The time spent capturing plain text from the DOM. This is reported by
ChromeRenderViewObserver when a page is loaded completely.
Deprecated as of 11/2017, since cld2 is deprecated.
rkaplow@google.com
Accuracy of the language detected by CLD2. Only recorded if the detection
returned a "known" result.
Deprecated as of 11/2017, since cld2 is deprecated.
rkaplow@google.com
Language of page detected by CLD2.
abakalov@chromium.org
Language of the input page detected by CLD3. This information is logged on
every page load.
abakalov@chromium.org
Percentage of the bytes that are associated with the most popular language
on the input page. Only recorded if the detection returned a
"known" result.
ramyasharma@google.com
Various user actions performed in the translate infobar.
ramyasharma@google.com
Records the hashcode of the source language when always translate this
language option is clicked in the menu.
ramyasharma@google.com
Records the hashcode of the language clicked on the more languages menu.
ramyasharma@google.com
Records the hashcode of the source language when never translate this
language option is clicked in the menu.
ramyasharma@google.com
Records the hashcode of the language clicked on the menu to indicate the
page is not in the selected language.
ramyasharma@google.com
Records the hashcode of the language clicked on the infobar.
ramyasharma@google.com
Records the number of times a page is translated, every time the page is
translated. For instance on a page a) translation from A to B, we record
"1" b) from A to B - we record "1" and revert from B to
A - we record "2" c) from A to B - we record "1", then
translation to C - we record "2". d) from A to B - we record
"1", then translation to C - we record "2" and then
revert to A - we record "3". We increment the translation count:
a) every time the target language is changed. b) every time we revert to the
original language (user can only revert to original language and not
intermediate target languages). This essentially means 1 denotes >= 1
translations, 2 is >=2 translations per page and so on. This will give us
a sense of how often people try out several translates on a page, or flip
back and forth.
kenjibaheux@google.com
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.
ramyasharma@google.com
The number of times the translate infobar was shown in the old translate UI
on Android. Only true is recorded.
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.
yyushkina@chromium.org
This metric logs CLD3-detected languages for pages that specify a
conflicting English language in their markup. In these cases, we must decide
on a language source to favor.
Bucket names are of the form "x,y", where x is the common English
language code specified in the page markup (or "other" if the
English language code is uncommon), and y is the CLD3-detected language.
This histogram only logs detection conflicts. Hence, "matching"
buckets (e.g. "en,en", "en-AU,en") will never be
populated.
andrewhayden@chromium.org
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.
renjieliu@chromium.org
Log everytime the language settings page is shown. This can be either user
visits chrome://settings/languages or user visits the advanced languages
card in chrome://settings. With this stat, we will be able to understand how
well the language model is doing by looking into how the number changes over
time. In additiona to that, we are also interested in how many users ever
visit the languages settings card.
yyushkina@chromium.org
For each page load, measures whether the provided HTML language (i.e. the
page lang attribute if it exists, otherwise the header Content-Language
value) matches the language determined by CLD. Beyond directly matching or
mismatching the HTML language, CLD can complement the HTML language. For
example, suppose the HTML language is 'zh' (general Chinese), a language
code that the Translate server does not support. In this case, CLD can
detect a subcode like '-TW' or '-CN', resulting in language codes 'zh-TW'
and 'zh-CN', which the Translate server supports. This is referred to as
"complementing a language subcode".
kenjibaheux@google.com
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.
Deprecated 2/2018
joelhockey@chromium.org
The time spent capturing plain text from the DOM. This is reported by
ChromeRenderViewObserver when a page is loaded completely.
kenjibaheux@google.com
Counts translation target page schemes.
rogerm@google.com
Tracks the outcome of attempts to download a Translate Ranker Model.
rogerm@google.com
The date tamp (e.g., 20160916 -> 15 Sept 2016) which denotes the
TranslateRankerModel's version.
rogerm@google.com
Whether the TranslateRanker accepts or denies to show the translation
prompt.
rogerm@google.com
Time taken for the TranslateRanker to use the translate ranker model to
calculate a score for the translation, in ms.
rogerm@google.com
Time taken for the Translate Ranker Model Loader to download its model from
the configured URL, in ms.
rogerm@google.com
Time taken for the Translate Ranker Model Loader to parse its model, in ms.
rogerm@google.com
Time taken for the Translate Ranker Model Loader to read its model from
local storage (cache), in ms.
rogerm@google.com
Time taken for the TranslateRanker to decide if a given translation should
be offered or not, in ms. This includes the time taken to extract the
relevant features upon which to base the decision, as well as the time taken
to calculate the result.
rogerm@google.com
Time taken for the Translate Ranker Model Loader to write its model to local
storage, in ms.
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.
yyushkina@google.com
The number of requests sent to the Translate server, grouped by source
language.
yyushkina@google.com
The number of requests sent to the Translate server, grouped by target
language.
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.
Deprecated 02/2016 in Issue 1741103002, and replaced by
Renderer4.CompositorWheelScrollUpdateThread and
Renderer4.CompositorTouchScrollUpdateThread.
tdresser@chromium.org
Whether a scroll is executed on main thread.
fsamuel@chromium.org
The amount of time the CompositorResizeLock was held in milliseconds. This
is a measure of jank as UI will not generate new frames as long as the lock
is held.
fsamuel@chromium.org
Tracks whether the CompositorResizeLock is being released due to timing out
or not.
bsep@chromium.org
The device scales available on the system at startup. A system may report
more than one if it has multiple displays with varying device scales. Only
logged on Windows.
fsamuel@chromium.org
The amount of time it took for UI's CompositorFrame to activate due to a
surface synchronization event. This a measure of jank as UI will not
generate new frames as long synchronization is in progress. This metric is
similar to UI.CompositorResizeLock.Duration but measures the new
synchronization code path.
holte@chromium.org
rkaplow@chromium.org
The actual interval between log upload start and previous log upload
finished within the same process.
holte@chromium.org
rkaplow@chromium.org
Number of UKM entries that are dropped. Categorized by the cause of it being
dropped.
Deprecated 2/2018 by UKM.Entries.SerializedCount2.
holte@chromium.org
rkaplow@chromium.org
Number of serialized UKM entries when storing a UKM log.
holte@chromium.org
rkaplow@chromium.org
Number of serialized UKM entries when storing a UKM log.
holte@chromium.org
rkaplow@chromium.org
Logged during UkmService initialization whether the init task or the initial
log timer completed first. The expectation is the vast majority of the time,
the init task should complete first. If metrics show otherwise, then it may
indicate there's a bug in the UkmService init sequence and that it should be
investigated.
holte@chromium.org
rkaplow@chromium.org
Size in kilobytes (after compression) of an uploaded UKM log. Recorded after
a successful UKM upload.
holte@chromium.org
rkaplow@chromium.org
Logs whether a log was not uploaded due to cellular log throttling logic.
Android only.
holte@chromium.org
rkaplow@chromium.org
HTTP response codes and network errors encountered by UKM when attempting to
upload logs to the server.
holte@chromium.org
rkaplow@chromium.org
The status when loading UKM PersistedLogs from Prefs.
holte@chromium.org
rkaplow@chromium.org
Number of UKM sources that are dropped. Categorized by the cause of it being
dropped.
asvitkine@chromium.org
bmcquade@chromium.org
Number of unsent UKM sources that were kept in-memory to be potentially
transmitted in the next log.
holte@chromium.org
rkaplow@chromium.org
Number of serialized UKM sources when storing a UKM log.
asvitkine@chromium.org
bmcquade@chromium.org
Number of UKM sources that were not sent because they had no associated
entries.
bcwhite@chromium.org
rkaplow@chromium.org
Information about the determination by the SyncDisableObserver on why it
enabled or disabled UKM based on Sync status. This is recorded every time a
change is detected in Sync (which may be several just at startup).
holte@chromium.org
rkaplow@chromium.org
Number of bytes in an excessively large log that was discarded while
persisting UKM logs to disk to retry during next chrome run.
holte@chromium.org
rkaplow@chromium.org
Counter for number of UKM unsent logs removed from persistent storage.
Replaced by UKM.LogUpload.ResponseOrErrorCode
holte@chromium.org
rkaplow@chromium.org
For each upload to the UKM server, log the response received from the
server.
asvitkine@chromium.org
The actual interval between log upload start and previous log upload
finished within the same process.
wfh@chromium.org
Records the result of the attempt to enumerate the installed AntiVirus on
the machine. This is recorded once during metrics initialization.
siggi@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.
Removed in M45.
asvitkine@chromium.org
Recorded when the one-time UMA client id reset was performed (and the client
id of this user was migrated).
Deprecated as of August 2015. The histogram showed no unexpected slowness,
and a profiler is a better tool for identifying any future issues.
asvitkine@chromium.org
The time to run the external metrics collection task (Chrome OS).
Deprecated as of Jun 2016. The histogram was added for debugging purpose and
is not needed anymore.
asvitkine@chromium.org
yiyaoliu@chromium.org
Records attempts to compute the current the signin status and error
encountered when computing.
Removed April, 2018 as the information has never shown any problems.
asvitkine@chromium.org
bcwhite@chromium.org
Records attempts to create histograms in presistent space and any errors
encountered when doing so.
wnwen@chromium.org
Measures how much time it took to complete all async deferred startup tasks
on the background thread. Only logged on Android.
wnwen@chromium.org
Measures how much time since application was first in foreground till all
deferred tasks are done. Only logged on Android.
Deprecated 01/2017 for
UMA.Debug.EnableCrashUploadDeferredStartupAsyncTaskDuration.
wnwen@chromium.org
asvitkine@chromium.org
Measures how much time it took to complete deferred startup tasks on the UI
thread. Only logged on Android.
wnwen@chromium.org
asvitkine@chromium.org
Measures how much time it took to complete async deferred startup tasks on
the background thread. Only logged on Android.
wnwen@chromium.org
Measures the maximum amount of time a single deferred startup task took.
Replaced by UMA.Debug.EnableCrashUpload.DeferredStartUptime2
asvitkine@chromium.org
Measures how much time since start up it took for onDeferredStartup() to be
called, which schedules enablePotentialCrashUploading() to be executed on an
async task. Only logged on Android.
Deprecated 2017. No longer tracked.
wnwen@chromium.org
asvitkine@chromium.org
Measures how much time since application was first in foreground till
deferred tasks are initialized and queued on the idle handler. Only logged
on Android.
Replaced by UMA.Debug.EnableCrashUpload.PostDeferredStartUptime2
asvitkine@chromium.org
Measures how much time since start up it took before ChromeActivity's
postDeferredStartupIfNeeded() was called. Only logged on Android.
Deprecated 2017. No longer tracked.
wnwen@chromium.org
asvitkine@chromium.org
Measures how much time since application was first in foreground till
ChromeActivity's postDeferredStartupIfNeeded() was called exactly once. Only
logged on Android.
Replaced by UMA.Debug.EnableCrashUpload.Uptime2
asvitkine@chromium.org
Measures how much time since start up it took before crash reporting was
enabled via enablePotentialCrashUploading() as part of deferred start up.
Only logged on Android.
Replaced by UMA.Debug.EnableCrashUpload.Uptime3
asvitkine@chromium.org
Measures how much time since start up it took before crash reporting was
enabled via enablePotentialCrashUploading() as part of deferred start up.
Only logged on Android.
Deprecated 2017. No longer tracked.
wnwen@chromium.org
asvitkine@chromium.org
Measures how much time since application was first in foreground till crash
reporting was enabled as part of deferred start up. Only logged on Android.
Replaced by UMA.Truncate* metrics.
asvitkine@chromium.org
rkaplow@chromium.org
The number of events that would be discarded at log transmission time
because the event count was already too large. Note that this doesn't
measure actual discards - in case the UMAThrottleEvents feature is disabled,
the discards won't occur.
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.
gayane@chromium.org
Not logged. Used for testing histogram expiry checker.
gayane@chromium.org
Not logged. Used for testing histogram expiry checker.
gayane@chromium.org
Not logged. Used for testing histogram expiry checker.
gayane@chromium.org
Not logged. Used for testing histogram expiry checker.
asvitkine@chromium.org
Logged on Android whenever an external experiment is registered. The logged
value is the number of groups in the experiment. This will not be logged at
all if there are no external experiments, but will be logged on group
transitions (e.g. when going from 1 to 0 groups).
Deprecated 11/2016 for UMA.FieldTrialAllocator.Used
lawrencewu@chromium.org
bcwhite@chromium.org
asvitkine@chromium.org
Size, before padding, of objects allocated from persistent memory in the
browser process for field trials. Updated on each subprocess launch.
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
bcwhite@chromium.org
Records attempts to access a file for the purpose of extracting metrics.
Removed April, 2018 as the information it provides is no longer useful.
asvitkine@chromium.org
bcwhite@chromium.org
The number of old metrics files for which a delete was attempted. This is
logged once with each upload operation. Values greater than 1 indicate that
the files are not deletable by the browser and must be cleaned up by
whatever process is creating them.
Removed April, 2018 as no problems were ever indicated.
asvitkine@chromium.org
bcwhite@chromium.org
The number of metrics files in a directory that need to be uploaded. This is
logged once with each upload operation.
Deprecated 07/2017. Was only for short-term analysis. About 95% of dropped
files were less than 1 day old.
asvitkine@chromium.org
bcwhite@chromium.org
Records the last-modified age of a file that was dropped for lack of an
embedded profile.
asvitkine@chromium.org
bcwhite@chromium.org
Records the number of histograms present in a file that was dropped for lack
of an embedded profile.
asvitkine@chromium.org
bcwhite@chromium.org
Records attempts to upload metrics from files with embedded system profiles.
This metrics was to provide information for crbug/760317 which has been
resolved. Removed February, 2018.
bcwhite@chromium.org
Records various happenings within the FileMetricsProvider for debugging
purposes.
asvitkine@chromium.org
bcwhite@chromium.org
Records attempts to access a file for the purpose of extracting initial
stability metrics.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent checking and mapping an initial metrics
file on disk.
Removed April, 2018 as the information it provides is no longer useful.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent checking and mapping initial metrics
from all files on disk.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent collecting initial stability metrics
from a file on disk.
Removed April, 2018 as the information it provides is no longer useful.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent collecting initial stability metrics
from all files on disk.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent collecting metrics from a file on disk.
Removed April, 2018 as the information it provides is no longer useful.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent collecting metrics from all files on
disk.
Deprecated as of August 2015. No longer tracked.
asvitkine@chromium.org
For each attempt to generate the low entropy source, log whether or not the
load required generating a new low entropy source.
Deprecated as of October 2017. No longer tracked.
asvitkine@chromium.org
bcwhite@chromium.org
Type and flags of every histogram created plus other activities. Counts are
not mutually-exclusive except for the different types.
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
This is logged with a value of true in every log when the UMA client code
has detected that this is a potentially cloned install and has set the pref
to reset its UMA client id on the next startup.
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.
Deprecated as of August 2015. The histograms showed no unexpected slowness,
and a profiler is a better tool for identifying any future issues.
asvitkine@chromium.org
The time spent to load (de-serialize) unsent logs from local state, recorded
during the MetricsService startup sequence.
bcwhite@chromium.org
Failures, as reported in errno, encountered while allocating local
persistent memory under Posix.
bcwhite@chromium.org
Failures, as reported by GetLastError(), encountered while allocating local
persistent memory under Windows.
No longer tracked.
asvitkine@chromium.org
Simple counter of the number of times LogLoadComplete was called (bug
demonstration, as we're called more often than once per page load :-/ )
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
Logs whether a log was not uploaded due to cellular log throttling logic.
Android only.
Used for analyzing UMA log uploads on cellular connection, but necessary
after the analysis is finished.
asvitkine@chromium.org
gayane@chromium.org
The network connection type for each successful metrics log upload.
holte@chromium.org
asvitkine@chromium.org
HTTP response codes and network errors encountered by UMA when attempting to
upload logs to the server through an HTTPS connection.
holte@chromium.org
asvitkine@chromium.org
HTTP response codes and network errors encountered by UMA when attempting to
upload logs to the server through an HTTP connection.
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.
This metrics was to provide information for crbug/760317 which has been
resolved. Removed February, 2018.
bcwhite@chromium.org
Records the size of the metrics directory size, after failing to be deleted.
This is a temporary metric that will be removed in M63 or M64.
This metrics was to provide information for crbug/760317 which has been
resolved. Removed February, 2018.
bcwhite@chromium.org
Records the size of the metrics directory size, after being successfully
deleted. This should always be zero unless there is a bug in the return
code. This is a temporary metric that will be removed in M63 or M64.
Removed February, 2018 because persistent metrics are fully launched with no
observable change in operation time.
asvitkine@chromium.org
bcwhite@chromium.org
Records how much wall time was spent merging, taking snapshots, and
recording histograms for reporting to UMA.
asvitkine@chromium.org
bcwhite@chromium.org
The lower 32 bits of the ID of the histogram that went negative.
asvitkine@chromium.org
bcwhite@chromium.org
The amount of increment that caused a sample count to become negative.
asvitkine@chromium.org
bcwhite@chromium.org
Reasons why a negative sample count would have been created. Currently, only
negative samples from persistent sparse histograms are being checked.
asvitkine@chromium.org
A count of successes and various failure modes related to collecting and
processing performance data obtained through "perf" on Chrome OS.
Deprecated 2/2017 for Issue 689315 which indicated they weren't being used.
bcwhite@chromium.org
asvitkine@chromium.org
Size, before padding, of objects allocated from persistent memory. This is
updated with every allocation.
bcwhite@chromium.org
asvitkine@chromium.org
Errors detected by the persistent memory allocator. These are set when they
occur.
bcwhite@chromium.org
asvitkine@chromium.org
Percentage of persistent memory segment that has been allocated. This is
updated only once per reporting cycle.
bcwhite@chromium.org
A count of successes and failures for the creation of various forms of
persistent memory used to store histograms.
Deprecated as of Jun 2016. The histogram was added for debugging purpose and
is not needed anymore.
asvitkine@chromium.org
yiyaoliu@chromium.org
Record the number of loaded profiles when a profile is erased from the
profiles map kept by profile manager.
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.
Deprecated as of August 2015. See UMA.ProtoCompressionRatio instead.
asvitkine@chromium.org
Kilobytes saved from gzipping the protobufs before uploading them.
jwd@chromium.org
Sample rate applied to this client, expressed as number of clients per 1000
that are in the sample. Recorded on every log upload.
Deprecated as of August 2015. The histograms showed no unexpected slowness,
and a profiler is a better tool for identifying any future issues.
asvitkine@chromium.org
The time spent to store unsent logs to local state, which is done
periodically and also during start up if there was an initial stability log.
asvitkine@chromium.org
bcwhite@chromium.org
The number of subprocesses from which persistent metrics were collected,
logged once with every reporting cycle.
asvitkine@chromium.org
bcwhite@chromium.org
The number of subprocesses, by type, from which persistent metrics are NOT
collected because there is no information about this (likely new) process
type. Process numbers 1000 or greater are "custom" processes used
by embedders.
Deprecated as of August 2015.
asvitkine@chromium.org
The number of synthetic field trials added to the UMA log when the system
profile is recorded. Since this is done prior to capturing the histograms
from the current process, this will generally be logged once per UMA log.
rkaplow@chromium.org
The number of omnibox events that existed in the metrics log before we
truncated them to save bandwidth.
rkaplow@chromium.org
The number of user actions events that existed in the metrics log before we
truncated them to save bandwidth.
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
gayane@chromium.org
Counter for number of UMA unsent logs removed from persistent storage.
Deprecated as of August 2015. This failure case no longer exists.
asvitkine@chromium.org
For each attempted UMA upload, log whether the upload was successfully
constructed. An upload might fail to be constructed, for example, if we try
to upload before the system is fully initialized; or if serialization of the
data fails.
Replaced by UMA.LogUpload.ResponseOrErrorCode
asvitkine@chromium.org
For each upload to the protocol buffer (v2) UMA server, log whether the
upload was successful, or whether there was an error.
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.
No longer tracked.
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).
tangltom@chromium.org
msarda@chromium.org
The action the user takes when the unified consent bump is shown.
tangltom@chromium.org
msarda@chromium.org
The reason the consent bump isn't shown to the user. This is recorded at
startup during the migration to Unified Consent.
tangltom@chromium.org
droger@chromium.org
State of the user settings for Sync and Google services, recorded at
startup. Multiple samples may be recorded at once, except for 'None' which
is recorded when no other bucket is used.
sorin@chromium.org
The number of download jobs found in the Windows BITS queue. This value is
expected to be zero in most cases, or a small number otherwise. Large values
indicate a problem with the job creation or clean up code. The metric is
recorded before a new BITS job is created and inserted into BITS queue.
sorin@chromium.org
True if a new BITS job was created to download the url, or false, if an
existing job was found in the BITS queue. The metric is recorded when the
component updater background downloader is asked to download a CRX.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
zeuthen@chromium.org
The payload size, in mebibytes (1048576 bytes).
This is reported when an update attempt ends.
This metric is specific to Chrome OS.
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 Chrome OS.
zeuthen@chromium.org
The result of the update attempt.
This is reported when an update attempt ends.
This metric is specific to Chrome OS.
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 Chrome OS.
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 Chrome OS.
deymo@chromium.org
The status of the certificate check done when downloading a payload over
HTTPS. Note that most downloads are done over HTTP.
This is reported on every HTTPS connection to the payload download server.
Connection drops on the same payload may report different values.
This metric is specific to Chrome OS.
deymo@chromium.org
The status of the certificate check done when querying Omaha for a new
version.
This is reported on every update check.
This metric is specific to Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
hunyadym@chromium.org
First section of the Chrome OS target version set by device policy and sent
to Omaha if rollback is also allowed. This is a sparse histogram, since the
possible valid values are stable Chrome OS version prefixes (usually one per
milestone).
Example value: 10323 (meaning M65 stable).
This is reported on every update check if the TargetVersionPrefix device
policy is set and the value of the RollbackToTargetVersion device policy is
one of the values allowing rollback.
This metric is specific to Chrome OS.
hunyadym@chromium.org
First section of the Chrome OS target version set by device policy and sent
to Omaha. This is a sparse histogram, since the possible valid values are
stable Chrome OS version prefixes (usually one per milestone).
Example value: 10323 (meaning M65 stable).
This is reported on every update check if the TargetVersionPrefix device
policy is set.
This metric is specific to Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
hunyadym@chromium.org
First section of the Chrome OS version to which an enterprise rollback
(rollback initiated by the admin of the device) has failed. This is a sparse
histogram, since the possible valid values are stable Chrome OS version
prefixes (usually one per milestone).
Example value: 10323 (meaning M65 stable).
This is reported after a rollback image has failed installing.
This metric is specific to Chrome OS.
hunyadym@chromium.org
First section of the Chrome OS version to which an enterprise rollback
(rollback initiated by the admin of the device) has succeeded. This is a
sparse histogram, since the possible valid values are stable Chrome OS
version prefixes (usually one per milestone).
Example value: 10323 (meaning M65 stable).
This is reported after a rollback image has been successfully installed.
This metric is specific to Chrome OS.
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 Chrome OS.
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 Chrome OS.
hunyadym@chromium.org
Whether setting the MaxKernelKeyRollforward value in the TPM succeeded.
This is reported every time an update check happens. This is a bool value.
This metric is specific to Chrome OS.
hunyadym@chromium.org
Maximum value the device can roll forward the minimum kernel key version
value in the TPM during the next boot.
This value is set to infinity (0xfffffffe) for devices which doesn't allow
rollback.
Otherwise, the value is the kernel key version of the earliest image to
which the device is allowed to roll back.
This is reported every time an update check happens. This is a sparse value.
This metric is specific to Chrome OS.
hunyadym@chromium.org
Minimum kernel key version already set in the TPM. This value specifies
which images can be booted up with verified boot.
This is reported every time an update check happens. This is a sparse value.
This metric is specific to Chrome OS.
zeuthen@chromium.org
Whether rollback worked.
This is reported every time there's a rollback request.
This metric is specific to Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
zeuthen@chromium.org
The size of the payload, in mebibytes (1048576 bytes).
This is reported on every successful update.
This metric is specific to Chrome OS.
zeuthen@chromium.org
The payload type ("Delta", "Full",
"ForcedFull") used.
This is reported on every successful update.
This metric is specific to Chrome OS.
zeuthen@chromium.org
The total number of reboots during the update.
This is reported on every successful update.
This metric is specific to Chrome OS.
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 Chrome OS.
senj@chromium.org
The total number of minutes from when an update was detected until an update
(possibly another update) was applied. This does not include the time
waiting for update checks and time the device spent sleeping.
This is reported on every successful update.
This metric is specific to Chrome OS.
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 Chrome OS.
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 Chrome OS.
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 Chrome OS.
spqchan@chromium.org
Tracks the upgrade notification stage. This is recorded with every UMA log.
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 have been terminated during the logout process and when Chrome is
started again to show the login screen. Since at least ChromeOS M62,
equivalent to Uptime.XTerminatedToChromeExecAfterLogout.
Deprecated 05/2018 in Issue 721891 with removal of X11. Replaced by
Uptime.OtherProcessesTerminatedToChromeExecAfterLogout in ChromeOS M69.
Equal to 0 since at least ChromeOS M62.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when all user-associated
processes (including the X server) have been terminated during the logout
process. This statistic is not collected if the logout is part of a restart
or shutdown.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when the UI has stopped
(Chrome has exited), and when all other associated processes have been
terminated during the logout process. This statistic is not collected if the
logout is part of a restart or shutdown.
Replaced by Uptime.OtherProcessesTerminatedToChromeExecAfterLogout in
ChromeOS M69. Equivalent to the new name since at least ChromeOS M62.
hajimehoshi@chromium.org
kouhei@chromium.org
Measures the time elapsed on Chrome OS between when the X server has been
terminated from a previous logout and when Chrome is started again to show
the login screen.
grt@chromium.org
The time it took to build and set the URL blacklist on the main thread
within URLBlacklistManager's constructor.
Removed 10/2017.
mmenke@chromium.org
Size (in kilobytes) of response bodies retrieved as strings from URLFetcher.
Removed in M57.
rsleevi@chromium.org
svaldez@chromium.org
Distribution of Content-Disposition headers sent with x-x509-user-cert
content types.
achuith@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.
achuith@chromium.org
Distribution of the default images chosen on user image screen during
out-of-the-box experience (Chrome OS). One sample is taken each time the
user confirms the choice by clicking OK button.
achuith@chromium.org
Distribution of the default images that existing users login with (Chrome
OS). One sample is taken each time the user logs in.
achuith@chromium.org
Profile image download result for UserManager (either on behalf of the
Change Picture prefs page, OOBE or scheduled refresh after user login).
achuith@chromium.org
The time it took to download user's profile picture.
achuith@chromium.org
Time histogram of the "Choose Picture" OOBE screen display delay.
achuith@chromium.org
The number of users of different types that log in to the system (Chrome
OS).
alemate@chromium.org
omrilio@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.
atwilson@chromium.org
Whether the profile_ever_initialized() user attribute migration has
completed for the current user.
alemate@chromium.org
This is logged when new user type reported by Gaia is different from the old
one (for existing user).
msarda@chromium.org
The result of restoring account id on Chrome restart after crash.
achuith@chromium.org
Whether the user pods were enabled during login, and what could disable
them.
Deprecated 5/2017 in Issue 704922. Replaced by
V8.ArrayBufferLargeAllocations.
bradnelson@chromium.org
titzer@chromium.org
kschimpf@chromium.org
Number of bytes requested in an array buffer allocation.
bradnelson@chromium.org
titzer@chromium.org
kschimpf@chromium.org
Number of bytes requested in array buffer allocations greater than one
megabyte.
bradnelson@chromium.org
titzer@chromium.org
kschimpf@chromium.org
Array buffer sizes for which V8 failed to allocate memory.
bradnelson@chromium.org
titzer@chromium.org
aseemgarg@chromium.org
Size of asm.js module (in asm.js format).
bradnelson@chromium.org
titzer@chromium.org
aseemgarg@chromium.org
Time to convert asm.js code to WebAssembly.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
aseemgarg@chromium.org
Throughput of translation of asm.js code to WebAssembly in MB/s.
This histogram is no longer present in V8.
hablich@chromium.org
TBD
yangguo@chromium.org
Reason code data has been rejected when attempting to deserialize.
yangguo@chromium.org
Cache size to source size ratio when caching compiled code.
This histogram is no longer present in V8.
hablich@chromium.org
TBD
This histogram is no longer present in V8.
hablich@chromium.org
Time spent generating native code for functions.
This histogram is no longer present in V8.
hablich@chromium.org
rmcilroy@chromium.org
Fraction of the total generated code which was generated using the
Crankshaft optimizing compiler, after each GC in percent.
This histogram has been replaced by V8.CompileMicroSeconds.
hablich@chromium.org
yangguo@chromium.org
Time spent in V8 compiler (full codegen).
yangguo@chromium.org
Time spent compiling a script that may be subject to caching.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
This histogram has been replaced by V8.CompileDeserializeMicroSeconds.
vogelheim@chromium.org
Time spent deseriailzing code, used by V8 code caching.
vogelheim@chromium.org
Time spent deseriailzing code, used by V8 code caching.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
This histogram has been replaced by V8.CompileEvalMicroSeconds.
yangguo@chromium.org
Time spent in V8 compiler (full codegen) for eval.
yangguo@chromium.org
Time spent in V8 compiler (full codegen) for eval.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
This histogram has been replaced by V8.CompileTime.CacheBehaviour.
kouhei@chromium.org
V8 script compile function variant which was picked. This contains
information such as {if,why} v8 {code,parser} was
{produced,consumed,bypassed}.
This histogram has been replaced by
V8.CompileTimeMicroSeconds.NoCache.InlineScript.
yangguo@chromium.org
Time spent compiling an inline script.
This histogram has been replaced by V8.CompileLazyMicroSeconds.
hablich@chromium.org
Time spent compiling functions lazily on first run.
hablich@chromium.org
Aggregated time spent compiling functions lazily during a single script
execution.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
yangguo@chromium.org
Time spent in V8 compiler (full codegen) excluding parser.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
This histogram has been replaced by the subcategories of
V8.CompileTimeMicroSeconds.NoCache
yangguo@chromium.org
Time spent compiling a script that cannot be subject to caching.
This histogram has been replaced by V8.CompileScriptMicroSeconds.
yangguo@chromium.org
Total time spent in compiling a script (incl. parsing/caching).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
The cache behaviour of compiling a V8 script, including whether we produced
or consumed a code cache, whether we hit V8's isolate's cache, and if we
didn't use the code cache, the reason why not.
yangguo@chromium.org
Total time spent in compiling a script (incl. parsing/caching).
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
rmcilroy@chromium.org
Total time spent in compiling a script (incl. parsing) on a background
thread.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script when the 'compilation' is
deserializing it from the code cache.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing/caching) when the
compilation tried to deserialize it from the code cache, but failed.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing/caching) in the case
where the V8 isolate's compilation cache is hit.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing) when the cache is too
cold to use.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing) when the script is an
inline script.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing) when we do not want
to cache it.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing) when the script is
too small to be cached.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
leszeks@chromium.org
Total time spent in compiling a script (incl. parsing) and serializing it
for the code cache.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
This histogram has been replaced by V8.CompileSerializeMicroSeconds.
vogelheim@chromium.org
Time spent serializing code, used by V8 code caching.
vogelheim@chromium.org
Time spent serializing code, used by V8 code caching.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
yangguo@chromium.org
Debugger feature used at least once per isolate, recorded on first use.
This histogram is no longer present in V8
hablich@chromium.org
Time spent generating deferred code stubs.
ulan@chromium.org
Number of garbage collections that a detached global context survives,
recorded after each major garbage collection. Values greater than 7 indicate
a memory leak.
hablich@chromium.org
The amount of JavaScript errors thrown by V8 per context. It does not count
custom errors and ignores catched errors thrown by V8. This is collected
after the context is detached.
This histogram is no longer present in V8
hablich@chromium.org
The maximum memory used to store V8 compiled code on a given process.
rmcilroy@chromium.org
Time spent in JavaScript Execution, including runtime calls, callbacks, and
lazy compilation.
gab@chromium.org
Latency (post-to-schedule) of each parallel task posted during V8 garbage
collection.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
ulan@chromium.org
Time spent in background tasks doing marking in one GC cycle. It is recorded
after each GC.
ulan@chromium.org
Time spent in background tasks doing scavenging in one GC cycle. It is
recorded after each GC.
ulan@chromium.org
Time spent in background tasks doing sweeping in one GC cycle. It is
recorded after each GC.
hpayer@chromium.org
Time spent in mark-sweep phase of GC.
hpayer@chromium.org
Time spent in mark-sweep phase of GC in a background isolate.
hpayer@chromium.org
Time spent in mark-sweep phase of GC in a foreground isolate.
hpayer@chromium.org
Time spent doing a full GC during an IdleNotification.
ulan@chromium.org
hpayer@chromium.org
Time spent in the final atomic pause of incremental latency-optimized
Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the clearing phase of incremental latency-optimized
Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the epilogue of incremental latency-optimized Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the evacuation phase of incremental latency-optimized
Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the finish phase of incremental latency-optimized Mark-Compact
GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the marking phase of incremental latency-optimized
Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the prologue of incremental latency-optimized Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the sweeping phase of incremental latency-optimized
Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the final atomic pause of incremental latency-optimized
Mark-Compact GC in a background isolate.
ulan@chromium.org
hpayer@chromium.org
Time spent in the final atomic pause of incremental latency-optimized
Mark-Compact GC in a foreground isolate.
ulan@chromium.org
hpayer@chromium.org
Time spent in the final atomic pause of incremental memory-optimized
Mark-Compact GC.
ulan@chromium.org
hpayer@chromium.org
Time spent in the final atomic pause of incremental memory-optimized
Mark-Compact GC in a background isolate.
ulan@chromium.org
hpayer@chromium.org
Time spent in the final atomic pause of incremental memory-optimized
Mark-Compact GC in a foreground isolate.
hpayer@chromium.org
Time spent in IdleNotifications.
Deprecated in August 2017. No longer tracked.
hpayer@chromium.org
Idle time passed to V8 via IdleNotifications.
Deprecated in August 2017. No longer tracked.
hpayer@chromium.org
Milliseconds the idle time limit was overshot by the IdleNotification.
Deprecated in August 2017. No longer tracked.
hpayer@chromium.org
Milliseconds the idle time limit was undershot by the IdleNotification.
hpayer@chromium.org
Time spent doing incremental marking steps during GC.
hpayer@chromium.org
Time spent in finalizing incremental marking.
ulan@chromium.org
Reason an incremental marking was started in V8.
hpayer@chromium.org
Time spent in starting incremental marking.
ulan@chromium.org
The total time spent in incremental marking steps in one GC cycle. It is
only recorded if the time is non-zero.
hpayer@chromium.org
Time spent in LowMemoryNotifications.
ulan@chromium.org
Reason a mark-compact garbage collection was started in V8.
hpayer@chromium.org
Time spent in scavenging phase of GC.
hpayer@chromium.org
Time spent in scavenging phase of GC in a background isolate.
ulan@chromium.org
Reason a scavenge garbage collection was started in V8.
hpayer@chromium.org
Time spent in scavenging phase of GC in a foreground isolate.
mlippautz@chromium.org
Type of garbage collection strategy used to collect the young generation.
oth@chromium.org
Results from snapshot loading.
oth@chromium.org
Results from opening V8 snapshot files.
This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace.
hpayer@chromium.org
External memory fragmentation in the cell space after each GC in percent.
hpayer@chromium.org
External memory fragmentation in the code space after each GC in percent.
hpayer@chromium.org
External memory fragmentation in the large object space after each GC in
percent.
hpayer@chromium.org
External memory fragmentation in the map space after each GC in percent.
This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace.
hpayer@chromium.org
External memory fragmentation in the old data space after each GC in
percent.
This histogram has been replaced by V8.MemoryExternalFragmentationOldSpace.
hpayer@chromium.org
External memory fragmentation in the old pointer space after each GC in
percent.
hpayer@chromium.org
External memory fragmentation in the old space after each GC in percent.
hpayer@chromium.org
Total external memory fragmentation after each GC in percent.
This histogram has been replaced by Memory.Experimental.Renderer2.V8.
ulan@chromium.org
The committed memory used by V8 in KB averaged over time, logged before each
GC.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the cell space after each GC in percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the code space after each GC in percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the lo space after each GC in percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the map space after each GC in percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the new space after each GC in percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the old data space after each GC in
percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the old pointer space after each GC in
percent.
Deprecated as of 09/2017.
hpayer@chromium.org
Fraction of the total heap used by the old space after each GC in percent.
Deprecated as of 09/2017.
hpayer@chromium.org
The size of committed memory in the cell space after each GC in KB.
hpayer@chromium.org
The size of committed memory in the code space after each GC in KB.
hpayer@chromium.org
The size of committed memory in the map space after each GC in KB.
hpayer@chromium.org
The maximum size of committed memory used by V8 after each GC in KB.
hpayer@chromium.org
The total size of committed memory used by V8 after each GC in KB.
hpayer@chromium.org
The total size of live memory used by V8 after each GC in KB.
This histogram has been replaced by
Memory.Experimental.Renderer2.V8.AllocatedObjects.
ulan@chromium.org
The live memory used by V8 in KB averaged over time, logged before each GC.
This histogram has been replaced by V8.ParseMicroSeconds.
marja@chromium.org
Time spent in V8 parser.
This histogram has been replaced by V8.ParseLazyMicroSeconds.
marja@chromium.org
Time spent parsing functions when they are lazily compiled on first run.
Deprecated.
marja@chromium.org
Time spent parsing functions when they are lazily compiled on first run.
Deprecated.
marja@chromium.org
Time spent in V8 parser.
This histogram has been replaced by V8.PreParseMicroSeconds.
marja@chromium.org
Time spent preparsing source code.
Deprecated.
marja@chromium.org
Time spent preparsing source code.
This histogram is no longer present in V8.
hablich@chromium.org
Time spent on rewriting ASTs before compilation.
This histogram is no longer present in V8.
hablich@chromium.org
TBD
This histogram is no longer present in V8.
hablich@chromium.org
TBD
This histogram is no longer present in V8.
yangguo@chromium.org
The generation a compiled script was found in the compilation cache.
bradnelson@chromium.org
titzer@chromium.org
kschimpf@chromium.org
Number of megabytes requested in shared array buffer allocations.
This histogram is no longer present in V8.
hablich@chromium.org
Time spent analysing the usage of variables.
This histogram is no longer present in V8.
hablich@chromium.org
TBD
bradnelson@chromium.org
titzer@chromium.org
eholk@chromium.org
The amount of address space reserved by WebAssembly.Memory backing stores in
MiB.
bradnelson@chromium.org
titzer@chromium.org
Time to compile a WebAssembly function.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
Peak memory used to compile a WebAssembly function.
bradnelson@chromium.org
titzer@chromium.org
Time to compile a WebAssembly module.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
Time to decode a WebAssembly function.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
Time to decode a WebAssembly module.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
Peak memory used to decode a WebAssembly module.
bradnelson@chromium.org
titzer@chromium.org
eholk@chromium.org
kschimpf@chromium.org
Time spent executing WebAssembly.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
Size of a WebAssembly function.
bradnelson@chromium.org
titzer@chromium.org
Function count in each WebAssembly module.
bradnelson@chromium.org
titzer@chromium.org
Time to instantiate a WebAssembly module.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
aseemgarg@chromium.org
Time for lazy compilation of WebAssembly functions. This is recorded per
function for the functions that are lazily compiled.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
bradnelson@chromium.org
titzer@chromium.org
aseemgarg@chromium.org
Throughput of compilation of lazily compiled WebAssembly functions in KB/s
(size of function in wasm format divided by time to compile it). This is
recorded per function for functions that are lazily compiled.
bradnelson@chromium.org
titzer@chromium.org
Number of 64KiB pages a WebAssembly module declares as its maximum
requirement.
bradnelson@chromium.org
titzer@chromium.org
eholk@chromium.org
The result of attempts to allocate WebAssembly.Memory buffers.
bradnelson@chromium.org
titzer@chromium.org
Number of 64KiB pages a WebAssembly module declares as its minimum
requirement.
titzer@chromium.org
clemensh@chromium.org
The amount of code space in MiB used by individual WebAssembly modules.
Recorded for each module on finalization, i.e. when it is garbage-collected.
bradnelson@chromium.org
titzer@chromium.org
Size of a WebAssembly module.
asvitkine@chromium.org
fdoray@chromium.org
The result of verifying if the variations seed is expired, recorded before
trials are created from the seed. Expired seeds are treated as not existing.
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.
Deprecated 10/2016. Replaced by Variations.SeedFetchResponseOrErrorCode.
asvitkine@chromium.org
The counts of network error codes encountered by VariationsService when an
attempt to fetch a variations seed from the server fails.
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
The latency of connection to the variations server when fetching an initial
variations seed during Android Chrome first run. This is included in the
Variations.FirstRun.SeedFetchTime measurement. Only considers cases where an
HTTP 200 result was received.
asvitkine@chromium.org
The result of attempting to fetch an initial variations seed during Android
Chrome first run. Records both the HTTP code and various error values in one
enumeration.
asvitkine@chromium.org
The latency of fetching an initial variations seed during Android Chrome
first run. Only considers cases where an HTTP 200 result was received.
asvitkine@chromium.org
The result of attempting to import an initial variations seed during Android
Chrome first run. Logged from VariationsSeedStore::LoadSeed when seed prefs
do not exist.
jwd@chromium.org
If the registry value for Google Update experiment labels contains
Variations experiments, and therefore needs to have them cleared. This will
be recorderd once per sessions, right before attempting to clear the value.
asvitkine@chromium.org
How long it took to create the X-Client-Data header.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
asvitkine@chromium.org
Records number of experiment ids in the X-Client-Data header at the time the
header is constructed.
jwd@chromium.org
The result of the check of whether to append Variations headers to a url.
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 latest variations seed's signature, recorded
when the seed is loaded from Local State. Not recorded when running in safe
mode.
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.
Deprecated as of M66 / Jan 2018. Replaced by
Variations.SafeMode.FellBackToSafeMode2.
isherman@chromium.org
Whether or not the VariationsService /would/ fall back to Safe Mode, due to
either too many crashes or too many failures to fetch a new seed, given some
initial/unrefined heuristics. Recorded during Chrome startup, when the
VariationsService is created.
This metric was only reported before Safe Mode was actually implemented, as
a sanity-check for the forthcoming implementation.
isherman@chromium.org
Whether or not the VariationsService fell back to Safe Mode, due to either
too many crashes or too many failures to fetch a new seed. Recorded during
Chrome startup, immediately before field trials are created. Only recorded
if either a recent or a safe seed was loaded successfully.
isherman@chromium.org
Records whether the safe variations seed was successfully read from local
state on startup. Records a detailed reason on read failure. Only recorded
when attempting to run in safe mode.
isherman@chromium.org
The result of verifying the safe variations seed's signature, recorded when
the seed is loaded from Local State. Only recorded when attempting to run in
safe mode.
isherman@chromium.org
Records the result of storing a safe variations seed (and all associated
metadata) to the seed store.
isherman@chromium.org
The result of verifying the safe variations seed's signature, recorded when
the safe seed is stored to Local State.
isherman@chromium.org
The number of consecutive crashes observed by the VariationsService, without
a single intervening successful seed fetch. Recorded during Chrome startup,
when the VariationsService is created.
isherman@chromium.org
The number of consecutive failed attempts to fetch a new seed by the
VariationsService. Recorded during Chrome startup, when the
VariationsService is created.
jwd@chromium.org
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.
Deprecated as of 9/2015.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
build time is ahead of or within 24 hours of the kVariationsSeedDate. Used
as an experiment to see whether the build time could be used to discard very
old seeds.
Deprecated as of 9/2015.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
build time is behind the kVariationsSeedDate by a day or more. Used as an
experiment to see whether the build time could be used to discard very old
seeds.
Deprecated as of 9/2015.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
system clock is ahead of or within 24 hours of the kVariationsSeedDate. Used
as an experiment to see whether the system clock could be used to discard
very old seeds.
Deprecated as of 9/2015.
gab@chromium.org
Logged on startup when creating field trials from the variations seed if the
system clock is behind the kVariationsSeedDate by a day or more. Used as an
experiment to see whether the system clock could be used to discard very old
seeds.
Deprecated in M61, and replaced by Variations.SeedLoadResult. This histogram
incorrectly conflated failures from loading the seed with failures while
attempting to store seeds with delta compression.
asvitkine@chromium.org
Records whether the variations seed was successfully read from local state
on startup. Records a detailed reason on read failure.
Deprecated 10/2016. Replaced by Variations.SeedFetchResponseOrErrorCode.
asvitkine@chromium.org
The counts of HTTP response codes encountered by VariationsService when
attempting to fetch a variations seed from the server.
asvitkine@chromium.org
HTTP response codes and network error encountered by VariationsService when
attempting to fetch a variations seed from the server over an HTTPS
connection.
asvitkine@chromium.org
HTTP response codes and network error encountered by VariationsService when
attempting to fetch a variations seed from the server over an HTTP
connection.
asvitkine@chromium.org
The time interval between when the variations seed was downloaded and when
it was loaded for use. Not recorded for expired seeds, nor when the download
time is unknown (typically, for seeds imported via first run).
paulmiller@chromium.org
Records the time spent blocking WebView startup to wait for the variatinos
seed. This is less than the entire time needed to load the seed, since
startup is only blocked if loading is not complete by the time the seed is
needed. This is logged once per WebView startup, whether or not the load was
successful.
asvitkine@chromium.org
Records whether the latest variations seed was successfully read from local
state on startup. Records a detailed reason on read failure. Not recorded
when running in safe mode.
gayane@chromium.org
Records how long it takes to load and process variations seed. This metric
is recorded only when loading and processing of the seed is successful.
asvitkine@chromium.org
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
On successful save of a delta-compressed variations seed, records the size
of the delta in KiB.
asvitkine@chromium.org
On successful save of a delta-compressed variations seed, records the size
of the delta as a percentage of the decoded seed size.
asvitkine@chromium.org
Records the size of the gzip-compressed variations seed in KiB.
asvitkine@chromium.org
Records the size of the gzip-compressed variations seed as a percentage of
the decoded seed size. Note that variations seed could be first
delta-compressed and then gzip-compressed. In this case we record
gzip-compressed seed size as a percentage of the delta-compressed seed size.
asvitkine@chromium.org
Records whether a country code was present when storing the variations seed.
asvitkine@chromium.org
On successful save of a non-delta-compressed variations seed, records the
size of the received seed in KiB.
asvitkine@chromium.org
The result of verifying the variations seed signature, recorded when the
variations seed is stored to Local State after being retrieved from the
server.
asvitkine@chromium.org
Records the number of UI strings overriden for each study that overrides
strings. Recorded at start up when each study is evaluated.
asvitkine@chromium.org
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.
binlu@google.com
Records instances of navigator.vibrate. Includes whether or not it comes
with a user gesture, same-origin subframe or cross-origin subframe.
yoshiki@chromium.org
Chrome OS Video Player: the results of the cast API extension load. This is
recorded after the initialization of the extension is finished.
yoshiki@chromium.org
Chrome OS Video Player: the length of casted video (in seconds).
yoshiki@chromium.org
Chrome OS Video Player: the number of cast devices. This is recorded when
the cast extension finishes the discovery.
yoshiki@chromium.org
Chrome OS Video Player: the number of files being opened on launch.
yoshiki@chromium.org
Chrome OS Video Player: type of playback (eg. local play, cast). This is
recorded when a video starts playing.
bokan@chromium.org
Tracks the proportion of non-mobile optimized (i.e. zoom disabled or layout
width matches viewport) page views that had a user-initiated page scale
(e.g. pinch-zoom, double-tap). Recorded on navigation to a new page - on
Android only.
bokan@chromium.org
Tracks the maximum scale factor that a user has scaled to over the lifetime
of the page. The scale is counted at pinch end (e.g. zooming to 300% and
back out to 150% in one gesture would count as 150%). Reported only on
non-mobile optimized pages (i.e. zoom disabled or layout width matches
viewport) which have had a page scale changing gesture. Recorded on
navigation to a new page - on Android only.
bokan@chromium.org
The viewport meta tag type seen on each page load. Only recorded on Android.
bokan@chromium.org
The screen width as a percentage of viewport width (i.e. zoom at which we
can see the whole page). Only recorded on Android and for viewport meta tags
with constant width.
oka@chromium.org
An integer representing a state transition from x to y in the form of x *
1000 + y. If the transition is not expected, the value is negated. For
example an expected transition from SHOWING (= 2) to SHOWN (= 1) is denoted
as 2001, and an unexpected transition from SHOWING to SHOWING is denoted as
-2002. See KeyboardControllerState for the correspondence between the number
and the enum.
oka@chromium.org
Validity of a state transtion. This is equivalent to the positiveness of
VirtualKeyboard.ControllerStateTransition.
oka@chromium.org
Latency of the keyboard being loaded for the first time.
Please list the metric's owners. Add more owner tags as needed.
A count of various control events that can occur on the virtual keyboard,
such as showing and hiding.
Deprecated 04/2016 as doesn't have data nor owner.
Please list the metric's owners. Add more owner tags as needed.
Counts the number of keys typed by the virtual keyboard between each
backspace. This metric provides a rough approximation of an error rate for
the virtual keyboard.
oka@chromium.org
Records whenever an intermediate keyboard state has been active for longer
than a fixed timeout.
dcastagna@chromium.org
hoegsberg@chromium.org
Overlay strategies used to promote Hardware Overlays, per frame. Recorded
every time a frame is rendered by the display compositor.
thildebr@chromium.org
Android: The source of a dismissed voice search, such as omnibox or NTP.
thildebr@chromium.org
Android: The source of a failed voice search, such as omnibox or NTP.
thildebr@chromium.org
Android: The source of a successful voice search, such as omnibox or NTP.
muyuanli@chromium.org
Counts the number of requests to retrieve voice interaction context when no
user interaction is initiated.
xiaohuic@chromium.org
Records the time between a voice interaction session start and end.
thildebr@chromium.org
Android: The source of a voice search start event, such as omnibox or NTP.
muyuanli@chromium.org
Records the time between user interaction and the actual request arrival.
thildebr@chromium.org
Android: Records the confidence value of a successful voice search as a
percentage.
thildebr@chromium.org
Android: Records whether the voice search produced results.
Deprecated 02/2018 in issue 799074.
VR.Component.Assets.DurationUntilReady.OnRegisterComponent measures the
intended metric more accurately.
tiborg@chromium.org
Duration from starting Chrome until VR assets component is ready to use.
tiborg@chromium.org
Duration from entering a VR mode until the VR assets component is ready to
use.
tiborg@chromium.org
Duration from registering VR assets component until it is ready to use.
tiborg@chromium.org
Status of the VR assets component when entering a VR mode.
tiborg@chromium.org
The component version and status of loading the VR assets. The value is
encoded as (XXX)(YYY)(SSS) where XXX is the major component version, YYY the
minor component version and SSS the status. See
//chrome/browser/vr/assets_load_status.h for possible status values.
tiborg@chromium.org
The version and update status of the VR assets component. The value is
encoded as (XXX)(YYY)(SSS) where XXX is the major version, YYY the minor
version and SSS the status. See
//chrome/browser/vr/assets_component_update_status.h for possible status
values.
tiborg@chromium.org
Network connection type when entering a VR mode.
tiborg@chromium.org
Network connection type when registering the VR component(s).
bshe@chromium.org
Number of times voice search is started in a single VR session. Recorded
when a new disjoint session has begun or when the session has ended in a
non-continuable way.
asimjour@chromium.org
We must suppress monocularly rendered ui elements in VR. This records which
ui element suppressions are encountered in practice.
vollick@chromium.org
We must exit VR mode when browsing in certain situations. This records which
situations are encountered in practice.
bshe@chromium.org
The end state of a voice search request in VR.
bshe@chromium.org
Chrome shows a prompt when the OS's record audio permission is needed for
voice search. The prompt gives user two choices: CANCEL or CONTINUE. This
records the user's selection.
ymalik@chromium.org
Whether we're auto-presenting the first time we enter WebVR mode.
billorr@chromium.org
The result of calls to VRDisplay::requestPresent(). Reported twice per
requestPresent() call, once to record the call, and once to record the
result.
ymalik@chromium.org
Whether the user had been through the FRE when Chrome is launched in VR
mode.
tiborg@chromium.org
The version of the runtime being used for VR.
billorr@chromium.org
Count of navigations while in a VR session. Logged when a new disjoint
session has begun, or when the session has ended in a non-continuable way.
billorr@chromium.org
The duration of the VR session. Logged when a new disjoint session has
begun, or when the session has ended in a non-continuable way.
ymalik@chromium.org
The duration of a single VR session initiated via a deep-linked WebVR app.
Logged when a new disjoint session has begun, or when the session has ended
in a non-continuable way.
billorr@chromium.org
Number of videos watched in a VR session. Logged when a new disjoint
session has begun, or when the session has ended in a non-continuable way.
billorr@chromium.org
The duration of a single session spent watching video in VR. Logged when a
new disjoint session has begun, or when the session has ended in a
non-continuable way.
billorr@chromium.org
The type of headset being used for VR.
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.
Deprecated 08/2016 because CertVerifier is not used for web view cert
verification.
eugenebut@chromium.org
[iOS] Reports certificate verification mismatch between SecTrust API and
CertVerifier. SecTrust API is used for making load/no-load decision and
CertVerifier is used for getting the reason of verification failure. It is
expected that mismatches will happen for those 2 approaches (e.g. SecTrust
API considers cert as good, but CertVerifier considers same cert as bad).
This metric helps to understand how common mismatches are.
eugenebut@chromium.org
[iOS] Reports URL matches between the return value from the WebState's
GetLastCommittedURL and GetCurrentURL methods. It is expected the origins
will be equal to confirm that GetCurrentURL can now be replaced with
GetLastCommittedURL. This will be called each time WebStateImpl::
GetCurrentURL(URLVerificationTrustLevel* trust_level) is called, which is an
old method of obtaining the url and trust level. The trust level was only
relevant with UIWebView, so this method is only called from code which has
not yet been updated since UIWebView was removed.
Deprecated as of 9/2013, replaced by
Web.CurrentOriginEqualsLastCommittedOrigin.
michaeldo@chromium.org
[iOS] Reports URL matches between the return value from the WebState's
GetLastCommittedURL and GetCurrentURL methods. It is expected the values
will be equal to confirm that GetCurrentURL can now be replaced with
GetLastCommittedURL. This will be called each time WebStateImpl::
GetCurrentURL(URLVerificationTrustLevel* trust_level) is called, which is an
old method of obtaining the url and trust level. The trust level was only
relevant with UIWebView, so this method is only called from code which has
not yet been updated since UIWebView was removed.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the available space that can be used when installing a WebAPK from
Google Play fails. The space recorded is the available space beyond the
system's minimum free space threshold, with a range between -1000 and 1000
MB. Negative values mean that there is less free space available than the
system's minimum, by the given amount.
Deprecated 2017-09. As of M64, this is no longer recorded.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the available space that can be used when installing a WebAPK from
Google Play succeeds. The space recorded is the available space beyond the
system's minimum free space threshold, with a range between -1000 and 1000
MB. Negative values mean that there is less free space available than the
system's minimum, by the given amount.
Deprecated in Chrome M69.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the available space that can be used when installing a WebAPK from
Google Play fails after freeing up cache and unimportant storage. The space
recorded is the available space beyond the system's minimum free space
threshold, with a range between -1000 and 1000 MB. Negative values mean that
there is less free space available than the system's minimum, by the given
amount.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the available space that can be used when installing a WebAPK from
Google Play fails after freeing up cache. The space recorded is the
available space beyond the system's minimum free space threshold, with a
range between -1000 and 1000 MB. Negative values mean that there is less
free space available than the system's minimum, by the given amount.
Deprecated in Chrome M69.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the available space that can be used when installing a WebAPK from
Google Play fails after freeing up unimportant storage. The space recorded
is the available space beyond the system's minimum free space threshold,
with a range between -1000 and 1000 MB. Negative values mean that there is
less free space available than the system's minimum, by the given amount.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the Chrome cache size when installing a WebAPK from Google Play
fails, with a range between 0 and 1000, rounded to the nearest 10MB.
Deprecated in Chrome M69.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Records the Chrome unimportant storage size when installing a WebAPK from
Google Play fails, with a range between 0 and 1000, rounded to the nearest
10MB.
Deprecated in Chrome M69.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the amount of time that it takes to bind to the play install service
for WebAPK installs.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the error code when installing a WebAPK from Google Play fails. See
go/webapk-install-googleplayerrorcode.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records whether installing a WebAPK from Google Play succeeded. If not,
records the reason that the install failed.
Deleted in M61.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
On web app and WebAPK installation, records whether a WebAPK could be
installed via the Google Play flow. If not, records why the WebAPK could not
be installed via the Google Play flow (and a web app was added to the
homescreen instead). Warning: This metric is recorded whenever a site is
added to the homescreeen as a web app, not just for sites with a WebAPK
compatible Web Manifest.
Deprecated 2017-08. As of M62, this is no longer recorded.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or
the add to homescreen menu item. This stat tracks whether the installation
is triggered by an app banner or by the add to homescreen menu.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
How long it takes to install a WebAPK. The time is measured from the time
that the user initiates the install to the time that the Open button is
shown in the infobar. This metric is only recorded when install succeeds.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or
the add to homescreen menu item. This stat tracks the WebAPKs installation
events, including whether the infobar is ignored, whether the infobar is
dismissed by the user before or during the installation, as well as whether
the installation was successful.
No longer recorded as of M65.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or
the add to homescreen menu item. If the installation is via an app banner,
user could either accept to install or dismiss the infobar; while via the
add to homescreen menu, the installation will start automatically. This stat
tracks the ways that user accepts to install a WebAPK.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the amount of time which has elapsed from the "install infobar
showing" to the "install request being sent to Google Play".
This time includes the time that it takes to request the WebAPK token and
the time that it takes to compute the hashes for the launcher icon and the
badge icon.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
Whether there is enough space to install a WebAPK. Recorded on each attempt
to install a WebAPK.
Deprecated 2017-08. As of M62, this is no longer recorded.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
WebAPKs are PWAs wrapped in an Android apk, installed from an app banner or
the add to homescreen menu item. If the user clicks the add to homescreen
menu, and a WebAPK has been installed before, an infobar with an open button
will show. The open button will also show on the infobar after a successful
installation. This stat tracks whether user clicks the open button on the
infobar or dismiss it.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the error codes when a WebAPK is launched with network failures.
Deprecated 2018-01. Replaced by WebApk.LaunchInterval2
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the amount of time since the user last launched the WebAPK from the
homescreen. Not recorded on first launch.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the amount of time since the user last launched the WebAPK from the
homescreen. Not recorded on first launch.
hanxi@chromium.org
ranj@chromium.org
yfriedman@chromium.org
When a WebAPK receives a notification, log whether it has permission to
display that notification.
Deprecated in Chrome M69.
hanxi@chromium.org
pkotwicz@chromium.org
When a user visits a PWA for which they have a WebAPK installed, the menu
item changes from 'Add to homescreen' to 'Open WebAPK'. This stat tracks
whether the opening of the WebAPK is successful when this menu item is
clicked.
Deprecated 2017-11. This UMA logs extra requests. Replaced by
ChromePermissionDenied2.
hanxi@chromium.org
pkotwicz@chromium.org
ranj@chromium.org
yfriedman@chromium.org
The number of Android runtime permission requests that are denied for the
WebAPK because Chrome does not have access to that permission.
hanxi@chromium.org
pkotwicz@chromium.org
ranj@chromium.org
yfriedman@chromium.org
The number of Android runtime permission requests that are denied for the
WebAPK because Chrome does not have access to that permission.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the amount of requests of Android runtime permissions which haven't
been granted to Chrome when Chrome is running in WebAPK runtime.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
The length of a WebAPK session (launch/foregrounding to backgrounding) in
milliseconds.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records WebAPK "Shell APK version" when the WebAPK is launched.
The "Shell APK version" is documented in shell_apk_version.gni
mheikal@chromium.org
yfriedman@chromium.org
Tracks the time to splashscreen hidden starting from the launch of the
WebAPK shell (rather than from the launch of Chrome). The splashscreen is
hidden after the first visually non-empty paint.
This is recorded iff: - This is a cold startup of Chrome. - Chrome has not
been sent to the background since launch. - There was no recents entry for
Chrome (android replays intents if a recents entry exists), which otherwise
adds noise/long-tail to this histogram.
mheikal@chromium.org
yfriedman@chromium.org
Tracks the time to splashscreen visible starting from the launch of the
WebAPK shell (rather than from the launch of Chrome). The splashscreen is
shown during postInflationStartup.
This is recorded iff: - This is a cold startup of Chrome. - Chrome has not
been sent to the background since launch. - There was no recents entry for
Chrome (android replays intents if a recents entry exists), which otherwise
adds noise/long-tail to this histogram.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records whether updating a WebAPK from Google Play succeeded. If not,
records the reason that the update failed.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the number of zombie "WebAPK update request" files that
the update process failed to cleanup. Recorded for all WebAPKs whenever a
WebAPK or webapp is launched.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the number of times that a WebAPK update request was queued (i.e.
waiting for the WebAPK to be backgrounded) before being sent to the server.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records the time point when a request to update a WebAPK is sent to the
WebAPK Server.
hanxi@chromium.org
pkotwicz@chromium.org
yfriedman@chromium.org
Records whether Chrome can bind to a WebAPK's "WebAPK service".
Recorded each time that Chrome attempts to bind to a WebAPK service.
dominickn@chromium.org
Records the number of milliseconds that the add to homescreen dialog
required to check installability eligibility.
calamity@chromium.org
mgiuca@chromium.org
The type of engagement (navigation, user input, etc.) which led to an
accumulation in site engagement within a PWA app window. Should be collected
for a subset of SiteEngagementService.EngagementType, which is triggered for
all browsing contexts. Recorded at the time of engagement accumulation
(e.g., when mouse is clicked).
piotrs@chromium.org
Records the display mode (as defined in the Web App Manifest spec) at the
install time of a WebApp (including WebApks).
dominickn@chromium.org
mcgreevy@chromium.org
Records the mechanism and source from which a web app installation was
triggered, regardless of whether the installation was successful.
Deprecated 2018-01 in favour of Webapp.Install.InstallEvent.
mcgreevy@chromium.org
Records the mechanism by which a web app installation was triggered,
regardless of whether the installation was successful.
dominickn@chromium.org
Records whether or not the check that a site is or isn't a Progressive Web
App (PWA) completes before the add to homescreen dialog on Android forcibly
times out and falls back to generating an icon.
dominickn@chromium.org
Records whether or not the check that a site is or isn't a Progressive Web
App (PWA) has completed when the user taps the add to homescreen menu item
on Android.
dominickn@chromium.org
Records whether or not the check that a site is or isn't a Progressive Web
App (PWA) has completed when the user opens the menu on Android.
piotrs@chromium.org
Records whether the top-level navigations in standalone Web Apps result in
presenting the web content or showing the error page.
mlamouri@chromium.org
Records the status of the splashscreen's background color (default or
custom).
mlamouri@chromium.org
Records the time during which the splashscreen was visible.
mlamouri@chromium.org
Records the signal that was used to hide the splashscreen.
mlamouri@chromium.org
Records the size of the icon used to construct the splashscreen in device
pixels (ie. real size divided by device pixel density). This is only
recording one dimension, the icon being square.
mlamouri@chromium.org
Records the origin of the icon used to construct the splashscreen.
mlamouri@chromium.org
Records the status of the splashscreen's theme color (default or custom).
rtoy@chromium.org
hongchan@chromium.org
The length (in frames) requested by createBuffer(). Recorded for every call
to createBuffer(). Probably many (tens or hundreds) per page.
rtoy@chromium.org
hongchan@chromium.org
The number of channels requested by createBuffer(). Recorded for every call
to createBuffer(). Probably many (tens or hundreds) per page.
Replaced by SampleRate384kHz in Issue 644683 on 2016/10 due to higher
supported sample rates.
rtoy@chromium.org
hongchan@chromium.org
The sample rate (in Hz) requested by createBuffer(). Recorded for every call
to createBuffer(). Probably many (tens or hundreds) per page.
rtoy@chromium.org
hongchan@chromium.org
The sample rate (in Hz) requested by createBuffer(). Recorded for every call
to createBuffer(). Probably many (tens or hundreds) per page.
Replaced by SampleRateRatio384kHz in Issue 644683 on 2016/10 due to higher
supported sample rates.
rtoy@chromium.org
hongchan@chromium.org
The ratio of the buffer sample rate from createBuffer() to the context
sample rate. This indicates if the buffer needs to be resampled. Recorded
for every call to createBuffer(). Probably many (tens or hundreds) per
page.
rtoy@chromium.org
hongchan@chromium.org
The ratio of the buffer sample rate from createBuffer() to the context
sample rate. This indicates if the buffer needs to be resampled. Recorded
for every call to createBuffer(). Probably many (tens or hundreds) per
page.
rtoy@chromium.org
hongchan@chromium.org
The hardware sample rate (in Hz) used by an AudioContext. Recorded for every
WebAudio AudioContext that is created; probably only one or two per page.
rtoy@chromium.org
hongchan@chromium.org
The maximum number of (hardware) channels available in an AudioContext.
Recorded for every WebAudio AudioContext that is created; probably only one
or two per page.
rtoy@chromium.org
hongchan@chromium.org
The callback buffer size (in audio frames) for WebAudio rendering between
the WebAudio graph and the audio device thread. This can differ from the
value recommended by the audio hardware due to internal constraints in
WebAudio. Recorded for every WebAudio AudioContext that is created.
rtoy@chromium.org
hongchan@chromium.org
The buffer size (in audio frames) for WebAudio rendering recommended by the
audio hardware. Recorded for every WebAudio AudioContext that is created.
Removed 02/2018 in Issue 764396. Information no longer needed or recorded.
rtoy@chromium.org
hongchan@chromium.org
The number of times the AudioParam value setter was called that also
conflicts with an ongoing AudioParam automation. Updated when the realtime
AudioContext is closed.
Removed 02/2018 in Issue 764396. Information no longer needed or recorded.
rtoy@chromium.org
hongchan@chromium.org
The percentage of number of calls to an AudioParam value setter that
conflicts with an ongoing AudioParam automation to the total number of calls
to the value setter. Updated once when an AudioContext is closed.
Removed 02/2018 in Issue 764396. Information no longer needed or recorded.
rtoy@chromium.org
hongchan@chromium.org
The number of times the AudioParam value setter was called per tab. Updated
when the realtime AudioContext is closed.
mlamouri@chromium.org
media-dev@chromium.org
rtoy@chromium.org
hongchan@chromium.org
The autoplay status of an AudioContext when destroyed. This include all
types of frames. In order to know the value only for main frames, the
.CrossOrigin values can be substracted.
mlamouri@chromium.org
media-dev@chromium.org
rtoy@chromium.org
hongchan@chromium.org
The autoplay status of an AudioContext when destroyed in a cross-origin
frame.
mlamouri@chromium.org
media-dev@chromium.org
rtoy@chromium.org
hongchan@chromium.org
Records how an AudioContext was unlocked (if it was). This is recorded when
the AudioContext is destroyed.
Removed in Issue 774526 on 2017/10; statistics aren't needed anymore.
rtoy@chromium.org
hongchan@chromium.org
The Q value (in 0.25 dB steps) used for a highpass BiquadFilter. Recorded
each time the value is set for a highpass filter via the .value setter or
the automation methods linearRampToValueAtTime, exponentialValueAtTime, and
setValueAtTime.
Removed in Issue 774526 on 2017/10; statistics aren't needed anymore.
rtoy@chromium.org
hongchan@chromium.org
The Q value (in 0.25 dB steps) used for a lowpass BiquadFilter. Recorded
each time the value is set for a lowpass filter via the .value setter or the
automation methods linearRampToValueAtTime, exponentialValueAtTime, and
setValueAtTime.
rtoy@chromium.org
hongchan@chromium.org
The type of the BiquadFilterNode. Recorded each time the type is set. This
recorded once (to lowpass) when a biquad filter is created and also recorded
whenever the filter type changes due to user action or programatically. It
is unlikely the type will change more than once.
rtoy@chromium.org
hongchan@chromium.org
The order of the WebAudio IIRFilterNode. The order is one less than the
number of feedback coefficients used in the denominator of the IIRFilter
transfer function. Recorded each time an IIRFilter is constructed.
rtoy@chromium.org
hongchan@chromium.org
The number of channels specified for the offline audio context. Recorded for
every offline context created. Probably only a few per page, but could be
potentially much more (thousands).
rtoy@chromium.org
hongchan@chromium.org
The length (in frames) specified for the offline audio context. Recorded for
every offline context created. Probably only a few per page, but could be
potentially much more (thousands).
Replaced by SampleRate384kHz in Issue 644683 on 2016/10 due to higher
supported sample rates.
rtoy@chromium.org
hongchan@chromium.org
The sample rate (in Hz) specified for the offline audio context. Recorded
for every offline context created. Probably only a few per page, but could
be potentially much more (thousands).
rtoy@chromium.org
hongchan@chromium.org
The sample rate (in Hz) specified for the offline audio context. Recorded
for every offline context created. Probably only a few per page, but could
be potentially much more (thousands).
rtoy@chromium.org
hongchan@chromium.org
The panning model for the PannerNode. Recorded once with the default value
at creation and once again whenver it is changed. Once changed, it is
unlikely to be changed again. If there are any PannerNodes created at all,
then there is probably one for each source (AudioBufferSourceNode,
OscillatorNode, or other source).
rtoy@chromium.org
hongchan@chromium.org
Captures if WebAudio caused glitches or not due to the FIFO underflow. It is
recorded when PushPullFIFO is destroyed. (e.g. navigating away from the
page.)
rtoy@chromium.org
hongchan@chromium.org
Percentage of FIFO underflow happened due to the the missed deadline of
WebAudio rendering engine. It is recorded when PushPullFIFO is destroyed.
(e.g. navigating away from the page.)
Deprecated 2016-09. As of M55, this is no longer recorded.
mlamouri@chromium.org
Records whether WebAudio had a user gesture requirement and whether it was
fulfilled.
eugenebut@chromium.org
[iOS] Report cache hit/miss for WKWebView cert verification. WKWebView Web
Controller has a cache of pending cert verification results to avoid extra
verifications when presenting SSL interstitial. This metric helps to
understand whether or not cache miss is possible.
eugenebut@chromium.org
[iOS] Chrome for iOS crashes because NavigationManager does not have any
navigation items and visible navigation item is dereferenced
(crbug.com/565457). The assumption is that crash occurs if pending load was
stopped for a child window. This metric will prove or disprove that
assumption.
mrefaat@chromium.org
[iOS] Measures the proportion of external URL requests that originate from a
subframe without any user interaction (e.g. an advertisement contains an
iframe directed at the App Store).
Deprecated 2017-02. This metric disproved the assumption mentioned in the
summary and it is no longer needed.
eugenebut@chromium.org
Chrome for iOS crashes in |didCommitNavigation:| if Navigation Manager is
empty. It's unclear how the app can get into this state and one assumption
is that didStartProvisionalNavigation: does not add a pending navigation.
This metric is logged when didStartProvisionalNavigation: fails to add a
pending item.
eugenebut@google.com
Whether or not WKWebView has provided a valid -certificateChain when loaded
a page over a secure connection.
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.
zmin@chromium.org
junov@chromium.org
The usage of Canvas 2D Context API. Logged when the particular API is used.
wychen@chromium.org
The time spent on collecting the statistics of the document in the main
frame. These statistics would be used as features to classify whether the
page is suitable for DOM distiller.
Warning: This metric may include reports from clients with low-resolution
clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports
will cause this metric to have an abnormal distribution. When considering
revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the
solution.
yoichio@chromium.org
Counts the number of times each document.execCommand is executed. This
doesn't count commands not supported by Blink.
yoichio@chromium.org
Counts the number of times each Editor::Command::execute is called. This
doesn't count commands not supported by Blink.
As of M57 this has been superseded by Blink.UseCounter.Features which fixes
a number of issues. See https://crbug.com/676837.
rbyers@chromium.org
Count of how many page loads use various features. The PageVisits bucket is
incremented for each page load, and the other buckets incremented at most
once per PageVisit via the WebCore::UseCounter class.
As of M57 this has been superseded by Blink.UseCounter.CSSProperties which
fixes a number of issues. See https://crbug.com/676837.
mikelawther@chromium.org
Records usage of CSS properties used on a page, either statically or
dynamically, from the time the page is initialised to when it is closed or
navigated away from. Each property is counted at most once per page per
view.
japhet@chromium.org
Records instances of child frames navigating the top frame. Includes whether
or not the navigation would have been permitted if not for our special case
for 'framebusting', the practice of ensuring a given document is never
displayed in a frame.
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.
cmumford@chromium.org
The reason that a forced-close of a backing store occurred.
jsbell@chromium.org
Number of outstanding transactions (running, blocked) in database when a new
transaction is created.
cmumford@chromium.org
Count of the results when attempting to destroy a corrupt Indexed DB backing
store.
dgrogan@chromium.org
Count total number of front end API calls of IndexedDB methods.
cmumford@chromium.org
The time that it takes to close IndexedDB's LevelDB backing store.
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.
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE.
dgrogan@chromium.org
Errno errors encountered by a single LevelDBEnv method when opening an
IndexedDB instance.
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBOpenErrors.BFE.
dgrogan@chromium.org
PlatformFileErrors encountered by a single LevelDBEnv method when opening an
IndexedDB instance.
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.
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE.
dgrogan@chromium.org
Errno errors encountered by a single LevelDBEnv method when reading an
IndexedDB instance.
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBReadErrors.BFE.
dgrogan@chromium.org
PlatformFileErrors encountered by a single LevelDBEnv method when opening an
IndexedDB instance.
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.
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE.
dgrogan@chromium.org
Errno errors encountered by a single LevelDBEnv method when writing to an
IndexedDB instance.
Deprecated 2015-05. As of M43 use WebCore.IndexedDB.LevelDBWriteErrors.BFE.
dgrogan@chromium.org
PlatformFileErrors encountered by a single LevelDBEnv method when writing to
an IndexedDB instance.
jsbell@chromium.org
The type of key (number, string, etc.) used for an index entry for a record
being newly stored or updated in an Indexed DB object store. For array keys,
the types of sub-keys are not recorded.
jsbell@chromium.org
The type of key (number, string, etc.) used for a record being newly stored
or updated in an Indexed DB object store. For array keys, the types of
sub-keys are not recorded.
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.
dmurph@chromium.org
The number of blobs being saved in an IndexedDB object store 'put'
operation. Recorded for every 'put' operation.
dmurph@chromium.org
The total size of the blobs being saved in an IndexedDB object store 'put'
operation. Recorded for every 'put' operation, except when there are no
attached blobs or a blob has an unknown size.
dmurph@chromium.org
The size of the IndexedDB key used in an IndexedDB object store 'put'
operation. Recorded for every 'put' operation.
Replaced with WebCore.IndexedDB.PutValueSize2 on 6/2017
dmurph@chromium.org
The size of the IndexedDB value used in an IndexedDB object store 'put'
operation. Recorded for every 'put' operation.
dmurph@chromium.org
The size of the IndexedDB value used in an IndexedDB object store 'put'
operation. Recorded for every 'put' operation.
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/
dmurph@chromium.org
Records if a v2 schema has blob keys in the database, which means the
database is corrupt. These databases will eventually be wiped as corrupt.
Recorded when the IndexedDB backing store for an origin is first opened,
which happens when a IndexedDB database connection is opened or when
database names are fetched. Note: The backing store stays alive for
subsequent connections, and sticks around for a couple seconds after the
last connection is closed. See WebCore.IndexedDB.SchemaV2HasBlobs.Docs for
the Docs-only version.
dmurph@chromium.org
Records if a v2 schema has blob keys in the database, which means the
database is corrupt. These databases will eventually be wiped as corrupt.
Recorded when the IndexedDB backing store for an origin is first opened,
which happens when a IndexedDB database connection is opened or when
database names are fetched. Note: The backing store stays alive for
subsequent connections, and sticks around for a couple seconds after the
last connection is closed. Only for docs.google.com. Note that these samples
will also be recorded in WebCore.IndexedDB.SchemaV2HasBlobs.
dmurph@chromium.org
Records the schema version of the IndexedDB database read from disk.
Recorded when the IndexedDB backing store for an origin is first opened,
which happens when a IndexedDB database connection is opened or when
database names are fetched. Note: The backing store stays alive for
subsequent connections, and sticks around for a couple seconds after the
last connection is closed. See WebCore.IndexedDB.SchemaVersion.Docs for the
Docs-only version.
dmurph@chromium.org
Records the schema version of the IndexedDB database read from disk.
Recorded when the IndexedDB backing store for an origin is first opened,
which happens when a IndexedDB database connection is opened or when
database names are fetched. Note: The backing store stays alive for
subsequent connections, and sticks around for a couple seconds after the
last connection is closed. Only for docs.google.com. Note that these samples
will also be recorded in WebCore.IndexedDB.SchemaVersion.
dmurph@chromium.org
Records the total size of tombstones deleted by the IndexedDB Tombstone
Sweeper. Recorded on the browser side (back end) when the sweeper has
completed scanning and it is in the 'deletion' mode. See
https://goo.gl/coKwA7.
dmurph@chromium.org
Records the time it takes for the IndexedDB Tombstone Sweeper to commit
tombstone deletions. Recorded on the browser side (back end) when the
sweeper has completed a round of sweeping and, it's in 'deletion' mode, and
it has tombstones to delete. See https://goo.gl/coKwA7.
dmurph@chromium.org
Records the time it takes for the IndexedDB Tombstone Sweeper to fully sweep
the indexes. Recorded on the browser side (back end) when the sweeper has
completed sweeping all indexes (so partial sweeps are not recorded) and it
is in 'deletion' mode. See https://goo.gl/coKwA7.
dmurph@chromium.org
Records when an error occurs during deletion of index tombstones by the
IndexedDB Tombstone Sweeper. Recorded on the browser side (back end) when
the sweeper has completed a round of sweeping and, it's in 'deletion' mode,
and it has tombstones to delete. See https://goo.gl/coKwA7.
dmurph@chromium.org
Recorded on the browser side (back end) when the IndexedDB Tombstone Sweeper
has completed scanning. Records the percentage of the indexes the scanner
fully scanned before it was stopped. To reduce the number of buckets, the
recorded value is the percentage divided by 5. See https://goo.gl/coKwA7.
dmurph@chromium.org
Records the number of tombstones deleted by the IndexedDB Tombstone Sweeper.
Recorded on the browser side (back end) when the sweeper has completed
scanning and it is in 'deletion' mode. See https://goo.gl/coKwA7.
dmurph@chromium.org
Records the number of tombstones encountered by the IndexedDB Tombstone
Sweeper. Recorded on the browser side (back end) when the sweeper has
completed scanning and it is in 'statistics' mode. See
https://goo.gl/coKwA7.
dmurph@chromium.org
Records the time it takes for the IndexedDB Tombstone Sweeper to fully scan
the indexes. Recorded on the browser side (back end) when the sweeper has
completed scanning all indexes (so partial scans are not recorded) and it is
in 'statistics' mode. See https://goo.gl/coKwA7.
dmurph@chromium.org
Recorded on the browser side (back end) when the IndexedDB Tombstone Sweeper
encounters an error while sweeping. See https://goo.gl/coKwA7.
dmurph@chromium.org
Records the total size of tombstones encountered by the IndexedDB Tombstone
Sweeper. Recorded on the browser side (back end) when the sweeper has
completed scanning and it is in the 'statistics' mode. See
https://goo.gl/coKwA7.
Replaced with WebCore.IndexedDB.Transaction.ReadOnly.SizeOnCommit2 on 6/2017
dmurph@chromium.org
The total temporary size of an IndexedDB ReadOnly Transaction. Since this is
a readonly transaction, the size should only be >0 when the transaction
is removing tombstone index keys. Recorded on transaction commit.
dmurph@chromium.org
The total temporary size of an IndexedDB ReadOnly Transaction. Since this is
a readonly transaction, the size should only be >0 when the transaction
is removing tombstone index keys. Recorded on transaction commit.
dmurph@chromium.org
The time it takes for an IndexedDB ReadOnly Transaction to commit, starting
from when it starts executing tasks (when it is scheduled). Recorded on
transaction commit.
Replaced with WebCore.IndexedDB.Transaction.ReadWrite.SizeOnCommit2 on
6/2017
dmurph@chromium.org
The total temporary size of an IndexedDB ReadWrite Transaction. This is the
memory that is temporarily stored before writing to disk. Recorded on
transaction commit.
dmurph@chromium.org
The total temporary size of an IndexedDB ReadWrite Transaction. This is the
memory that is temporarily stored before writing to disk. Recorded on
transaction commit.
dmurph@chromium.org
The time it takes for an IndexedDB ReadWrite Transaction to commit, starting
from when it starts executing tasks (when it is scheduled). Recorded on
transaction commit.
Replaced with WebCore.IndexedDB.Transaction.VersionChange.SizeOnCommit2 on
6/2017
dmurph@chromium.org
The total temporary size of an IndexedDB VersionChange Transaction. This is
the memory that is temporarily stored before writing to disk. Version change
transactions happen when creating a database or updating a current database
schema. Recorded on transaction commit.
dmurph@chromium.org
The total temporary size of an IndexedDB VersionChange Transaction. This is
the memory that is temporarily stored before writing to disk. Version change
transactions happen when creating a database or updating a current database
schema. Recorded on transaction commit.
dmurph@chromium.org
The time it takes for an IndexedDB VersionChange Transaction to commit,
starting from when it starts executing tasks (when it is scheduled). Version
change transactions happen when creating a database or updating a current
database schema. Recorded on transaction commit.
dmurph@chromium.org
Recorded on the browser side (back end) when an IndexedDB transaction is
aborted, specifically recording the reason for the abort. This can be
triggered by javascript code on the renderer, errors or force closes on the
backend, or by the transaction timeout timer.
Deprecated, preloads are issued on the main thread now, so this is less
useful.
csharrison@chromium.org
The delay between when the preload scanner discovers a resource on the
parser thread and when the preload request is issued on the main thread.
clamy@chromium.org
The resulting action (e.g. load resource, use resource from in-memory
cache...) upon a resource request.
Deprecated April 2017.
clamy@chromium.org
Number of dead resources found in the memory cache over the lifetime of the
ResourceFetcher.
Deprecated April 2017.
clamy@chromium.org
Number of resources that needed to be loaded by the ResourceFetcher over its
lifetime.
clamy@chromium.org
Whether the resource in the cache is being used by at least one client (live
resource) or not (dead resource) upon a cache hit.
This metric has been not recorded at least since 2016/01. The displayed enum
labels might be unreliable because C++ enum values of blink::Resource::Type
have been changed over time.
clamy@chromium.org
The type of the resource (e.g. image, script...) upon a cache hit.
Deprecated April 2017.
clamy@chromium.org
Number of dead resources that needed to be revalidated by the
ResourceFetcher over its lifetime.
Deprecated November 2017.
rmcilroy@chromium.org
The amount of time allotted to a requestIdleCallback callback, i.e., the
difference between the time when it is called and when its deadline expires.
rmcilroy@chromium.org
The amount of time by which a requestIdleCallback callback overran its
deadline. Callbacks which don't overrun their deadline will report an
overrun of 0.
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.
xiaochengh@chromium.org
The amount of time between consecutive spellcheck requests made by Blink,
with the exception that requests made simultaneously checking different
parts of the same editing host count as only one request.
Temporary histogram replaced by Blink.UseCounter.CSSProperties.
rbyers@chromium.org
Temporary histogram replaced by Blink.UseCounter.Features.
rbyers@chromium.org
Temporary histogram replaced by Blink.UseCounter.SVGImage.CSSProperties.
rbyers@chromium.org
Temporary histogram replaced by Blink.UseCounter.SVGImage.Features.
rbyers@chromium.org
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.
Deprecate 2017-06, as we've collected enough data to discuss. (see issue
584616).
yhirano@chromium.org
ricea@chromium.org
Count the number of changes to WebSocket.binaryType after the connection
opened, per connection. Assignments that match the existing binaryType are
not counted. This is recorded after WebSocket close, whether explicit or due
to error or navigation. It is not recorded if the render process is
destroyed before the WebSocket is closed.
Deprecated 2014-06 when we replaced the WebSocket implementation (see issue
226931).
yhirano@chromium.org
ricea@chromium.org
Count the number of WebSocket handshake for each result. Use this histogram
as a baseline for investigating feature usage counters.
yhirano@chromium.org
ricea@chromium.org
The sizes of binary WebSocket messages received, broken down by type. One
entry per message. Clamped to 100 MB.
yhirano@chromium.org
ricea@chromium.org
The sizes of binary WebSocket messages sent, broken down by type. One entry
per message. Clamped to 100 MB.
Deprecated 2014-06 when we replaced the WebSocket implementation (see issue
226931).
yhirano@chromium.org
ricea@chromium.org
Count the number of WebSockets that accepted permessage-deflate extension
for each context take over mode. Used by the old Blink-based WebSocket
implementation.
yhirano@chromium.org
ricea@chromium.org
Count the number of messages for each message type and set binary type.
yhirano@chromium.org
ricea@chromium.org
Count the number of send() method calls on WebSockets for each argument
type.
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.
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
The value of font-display @font-face descriptor. Counted only when
explicitly specified in the @font-face rule.
kenjibaheux@chromium.org
ksakamoto@chromium.org
This metrics is logged when a page that use web fonts is loaded. The value
is whether we had to wait on at least one web font and ended up showing
blank text, or not.
Deprecated 10/2017. Related field trial has finished rolling out.
toyoshim@chromium.org
kenjibaheux@chromium.org
For each WebFont load attempt, records whether User Agent Intervention was
triggered, and whether the request (would have) timed out or not. The
intervention takes adaptive behaviors to handle loading timeouts to improve
user experiences on slow networks.
Deprecated 10/2017. Related field trial has finished rolling out.
toyoshim@chromium.org
kenjibaheux@chromium.org
Like InterventionResult, this records whether User Agent Intervention was
triggered, and whether the request (would have) timed out or not. But this
version records only when data actually comes from network, not from disk or
memory cache, and is not provided in a data URL format.
Renamed to WebFont.StyleRecalcToDownloadLatency for clarity.
kenjibaheux@chromium.org
ksakamoto@chromium.org
The time from when the webfont was referenced by a calculated style for the
first time to the start of the font download.
ksakamoto@chromium.org
shaochuan@chromium.org
toyoshim@chromium.org
The load limit state when the first disk-cache-only request fails by cache
miss, if WebFonts cache-aware timeout adaptation is enabled and applicable.
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.
zea@chromium.org
Percentage of results that are present locally but are not returned by the
web history API call. Recorded every time a signed-in user visits the
chrome://history page and the results from the web history are received.
zea@chromium.org
Whether getting the OAuth token was successful for a web history query. On
visits to the chrome://history page this token is obtained and then used to
get the user's synced web history.
zea@chromium.org
HTTP Response code returned by the server when trying to fetch the OAuth
token for a web history query.
zea@chromium.org
Whether the web history API call was successful. Every time a signed-in user
visits the chrome://history page this query is executed to get the user's
synced web history. If successful, the local and remote results are merged
and shown in the history page.
zea@chromium.org
Time it took for the web history to reply. Recorded when the web history API
call triggered by visiting chrome://history receives the data, measuring how
much time it took for the server to reply.
droger@chromium.org
Histogram for the format of decoded WebP images on iOS, as Chrome re-encodes
WebP images on that platform.
hlundin@chromium.org
Captures if the estimated delay between rendered and captured audio is out
of bounds which can cause the Echo Cancellation to fail. This is logged
roughly once every 5 seconds. The values are logged in four buckets
reflecting how well the Echo Cancellation likely performs based on the
estimated delay.
grunell@chromium.org
minyue@chromium.org
The percentage of measurement periods during a capture stream's lifetime
when the echo canceler's filter is considered to have diverged at least
once. A diverged filter could mean that there was echo och ducking
experienced. The measurement period size is fixed and in the order of one
second. The first measurement period is larger, typically 2-3 seconds.
Capture streams with shorter lifetimes (i.e. no data available) are not
recorded here.
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.
hlundin@chromium.org
The AEC in WebRTC will sometimes realign the far- and near-end signal
buffers to keep in sync with delay changes in the echo path. This metric
logs each such realignment, storing the delay change in ms, when the change
is triggered by a shift in the signal based delay estimation (a.k.a
delay-agnostic).
hlundin@chromium.org
The AEC in WebRTC will sometimes realign the far- and near-end signal
buffers to keep in sync with delay changes in the echo path. This metric
logs each such realignment, storing the delay change in ms, when the change
is triggered by a shift in system reported delay.
hlundin@chromium.org
The AEC in WebRTC keeps a buffer to mimic the audio buffers in the lower
layers. This histogram logs a sudden positive jump in buffer size. Since we
detect jumps in the capture thread, only positive values are feasible. Note
that the difference in milliseconds is logged and not the actual AEC system
delay value. Sampled every time the AEC system delay changes more than 50
milliseconds.
aleloi@chromium.org
The Fixed-Digital part of the AGC protects from saturation by reducing the
level of too loud signals. This metric shows how long the level estimate
stays in the 'Identity' region. In this region no attanuating gain is
applied.
aleloi@chromium.org
The Fixed-Digital part of the AGC protects from saturation by reducing the
level of too loud signals. This metric shows how long the level estimate
stays in the 'Knee' region. In this region some attanuating gain is applied.
aleloi@chromium.org
The Fixed-Digital part of the AGC protects from saturation by reducing the
level of too loud signals. This metric shows how long the level estimate
stays in the 'Limiter' region. In this region some more attanuating gain is
applied.
aleloi@chromium.org
The Fixed-Digital part of the AGC protects from saturation by reducing the
level of too loud signals. This metric shows how long the level estimate
stays in the 'Saturation' region. In this region much attanuating gain is
applied.
hlundin@chromium.org
The automatic gain control (AGC) in WebRTC tries to adjust the microphone
gain to maintain a strong audio level, but without clipping (saturation).
The histogram will log a value every time input clipping is detected. The
value is a boolean, with "true" meaning that the gain was in fact
adjusted in response to the detected clipping, and "false" meaning
that adjustment was not allowed due to limiting boundaries in the algorithm.
hlundin@chromium.org
The automatic gain control (AGC) in WebRTC tries to adjust the microphone
gain to maintain a strong audio level, but without clipping (saturation).
The histogram will log a new value every time the AGC changes the target
level.
hlundin@chromium.org
This histogram reports the average RMS of the signal coming in to WebRTC's
Audio Processing Module, prior to any WebRTC processing. A new value is
reported every 10 seconds, and the average is over the latest interval. The
metric is negated dBFS, meaning that 0 is a full-scale signal, while 127
corresponds to -127 dBFS (very faint).
hlundin@chromium.org
This histogram reports the peak RMS of the signal coming in to WebRTC's
Audio Processing Module, prior to any WebRTC processing. A new value is
reported every 10 seconds, and the peak is the RMS of the strongest 10 ms
block over the latest interval. The metric is negated dBFS, meaning that 0
is a full-scale signal, while 127 corresponds to -127 dBFS (very faint).
peah@chromium.org
This histogram reports the average RMS of the signal in the output of
WebRTC's Audio Processing Module, after all audio WebRTC processing. A new
value is reported every 10 seconds, and the average is over the latest
interval. The metric is negated dBFS, meaning that 0 is a full-scale signal,
while 127 corresponds to -127 dBFS (very faint).
peah@chromium.org
This histogram reports the peak RMS of the signal in the output of WebRTC's
Audio Processing Module, after all WebRTC audio processing. A new value is
reported every 10 seconds, and the peak is the RMS of the strongest 10 ms
block over the latest interval. The metric is negated dBFS, meaning that 0
is a full-scale signal, while 127 corresponds to -127 dBFS (very faint).
aleloi@chromium.org
Reports the sampling rate at which audio mixing is done. Lower rates result
in faster processing, higher rates can give higher quality.
aleloi@chromium.org
Reports the number of active incoming streams in the WebRTC audio mixer. An
incoming stream is active if it is not muted. When multiple sterams are
active, adding them can result in saturation and limiting is needed.
aleloi@chromium.org
Reports the number of streams in the WebRTC audio mixer. The mixer queries
all streams for audio and preferred sampling rate. The number of streams
affects mixing decisions. Whether to mix in floating points or use a limiter
depends on the number of incoming streams.
hlundin@chromium.org
Measures the average waiting time in the buffer for each packet. The waiting
time is the time elapsed from the packet arrives until it is decoded. The
metric is calculated as the average over one minute, and is logged at the
end of each such interval. A well tuned target buffer level should lead to a
low value.
hlundin@chromium.org
Measures the duration of each packet loss concealment (a.k.a. expand) event
that is not followed by a merge operation. The outage is measured in
milliseconds, with a range between 0 and 2000 ms. This gives an indication
of how well the jitter buffer's level adaptation is working. If the chosen
target level is too low, this value will increase.
hlundin@chromium.org
Counts the number of delayed packet outage events per minute. The range is
between 0 and 100 (corresponds to more 1.6 events per second). See
WebRTC.Audio.DelayedPacketOutageEventMs for the definition of a delayed
packet outage event, and the interpretation of such events.
peah@chromium.org
This histogram logs a value indicating whether the WebRTC echo canceller
detects that there is active content in the render signal. A new value is
logged every 10 seconds and the logged value is averaged over this period.
peah@chromium.org
This histogram logs the applied render buffer delay used in the WebRTC echo
canceller. A new value is logged every 10 seconds and the logged value
constitutes the current buffer delay at the time when the value is logged.
peah@chromium.org
This histogram logs a value every time the WebRTC echo canceller has
detected saturation in the capture signal. A new value is logged every 10
seconds and the logged value indicates whether the capture signal has been
saturated during the last 10 seconds.
peah@chromium.org
This histogram logs the level of the comfort noise in the WebRTC echo
canceller in the lower 4 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs the level of the comfort noise in the WebRTC echo
canceller between 4 and 8 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs the frequency of echo path delay changes that are
detected by the delay estimator in the WebRTC echo canceller. A new value is
logged every 10 seconds and the logged value indicates how frequent delay
changes have been during the last 10 seconds.
peah@chromium.org
This histogram logs the estimated echo path delay in 64 sample blocks as
seen by the delay estimator in the WebRTC echo canceller. A new value is
logged every 10 seconds and the logged value is the estimate of the delay of
the echo path at the time when the value is logged.
gustaf@chromium.org
This histogram logs the echo return loss achieved by the WebRTC echo
canceller as described in ITU G.168. When the echo canceller is being used,
one value is logged every 10 seconds per ongoing WebRTC call.
peah@chromium.org
This histogram logs the echo return loss achieved by the WebRTC echo
canceller in the lower 4 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs the echo return loss achieved by the WebRTC echo
canceller between 4 and 8 kHz. A new value is logged every 10 seconds.
gustaf@chromium.org
This histogram logs the echo return loss enhancement achieved by the WebRTC
echo canceller as described in ITU G.168. When the echo canceller is being
used, one value is logged every 10 seconds per ongoing WebRTC call.
peah@chromium.org
This histogram logs the echo return loss enhancement achieved by the WebRTC
echo canceller in the lower 4 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs the echo return loss enhancement achieved by the WebRTC
echo canceller between 4 and 8 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs the estimated echo path delay in 64 sample blocks as
seen by the linear filter delay in the WebRTC echo canceller. The value 0
means that no delay could be estimated from the linear filter, otherwise the
logged delay corresponds to the actual delay + 1. A new value is logged
every 10 seconds and the logged value is the estimate of the filter delay at
the time when the value is logged.
peah@chromium.org
This histogram logs the number of times per minute that the WebRTC echo
canceller detects a shift in the skew between the total number of render and
capture calls. The metric is reported once per minute and the report is done
also for the case of 0 detected skew shifts have been detected. The amount
of skew shifts per minute is capped to 20. The metric is reported separately
for each render process. The metric is only reported for render processes
where the WebRTC echo canceller is active in and there is both audio being
played out and captured simultaneously. The reporting is only done when the
browser is awake.
peah@chromium.org
This histogram logs a value every time the WebRTC echo canceller deems that
echo path is possible to model using any of the the echo canceller echo path
models. A new value is logged every 10 seconds and the logged value is the
feasibility assessment at the time when the value is logged.
peah@chromium.org
This histogram logs the assessed reliability of the delay estimates produced
by the delay estimator in the WebRTC echo canceller. A new value is logged
every 10 seconds and the logged value is a meausure based on how often
during that period the delay estimate was reliable.
peah@chromium.org
This histogram logs the frequency of overruns in the render buffer of the
WebRTC echo canceller. A new value is logged every 10 seconds and the logged
value is a meausure that indicates how often overruns occurred.
peah@chromium.org
This histogram logs the frequency of underruns in the render buffer of the
WebRTC echo canceller. A new value is logged every 10 seconds and the logged
value is a meausure that indicates how often underruns occurred.
peah@chromium.org
This histogram logs the echo suppressor gain in the WebRTC echo canceller in
the lower 4 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs the echo suppressor gain in the WebRTC echo canceller
between 4 and 8 kHz. A new value is logged every 10 seconds.
peah@chromium.org
This histogram logs a value every time the WebRTC echo canceller deems that
the linear filter in the echo canceller is sufficiently well adapted to be
usable. A new value is logged every 10 seconds and the logged value is the
assessment of whether the filter is usable at the time when the value is
logged.
aleloi@chromium.org
Histogram of audio codec usage. Every sample corresponds to 5 seconds of
encoding with that codec.
hlundin@chromium.org
Measures the expand rate for an incoming WebRTC audio stream. The expand
rate is the fraction of samples that are generated through loss-concealemnt
algorithms instead of being decoded from incoming media packets. The metric
is calculated as the percent over a 10 second internval, and is logged at
the end of each such interval.
hlundin@chromium.org
Number of triggered WebRTC.Audio.AecSystemDelayJump during a call. This is
recorded when a WebRTC based call has ended. AecSystemDelayJump can be
triggered when, for example, the capture thread is stalled, which can harm
the AEC. NumOfAecSystemDelayJumps shows how often this occurs in general as
well as during a call.
hlundin@chromium.org
Number of triggered WebRTC.Audio.PlatformReportedStreamDelayJump during a
call. This is recorded when a WebRTC based call has ended.
PlatformReportedStreamDelayJump can be triggered when, for example, the
capture thread is stalled, which can harm the AEC.
NumOfPlatformReportedStreamDelayJumps shows how often this occurs in general
as well as during a call.
hlundin@chromium.org
The difference in stream delay reported to WebRTC by Chrome. Since we detect
jumps in the capture thread, only positive values are feasible. Note that
the difference in milliseconds is logged and not the actual stream delay
value. Sampled every time the stream delay changes more than 50
milliseconds.
hlundin@chromium.org
The sum of the jitter buffer delay and the sound card's buffering delay for
the receiving side. That is, the sum of the metrics
WebRTC.Audio.ReceiverDeviceDelayMs and
WebRTC.Audio.ReceiverJitterBufferDelayMs. Sampled once every 10 ms when
WebRTC audio is playing.
hlundin@chromium.org
The sound card's buffering delay for the receiving side. Sampled once every
10 ms when WebRTC audio is playing.
hlundin@chromium.org
The jitter buffer delay for the receiving side. Sampled once every 10 ms
when WebRTC audio is playing.
hlundin@chromium.org
ivoc@chromium.org
The estimated likelihood percentage of echo as detected by the residual echo
detector. The residual echo detector can be used to detect cases where the
AEC (hardware or software) is not functioning properly. The detector can be
non-causal and operates on larger timescales with more delay than the
regular AEC.
hlundin@chromium.org
Measures the audible expand rate for an incoming WebRTC audio stream. The
metric is very similar to WebRTC.Audio.ExpandRate, with the difference that
this metric only reports loss-concealement that generates audible samples.
The metric is calculated as the percent over a 10 second internval, and is
logged at the end of each such interval.
hlundin@chromium.org
The target bitrate in kbps that the audio codec should try to produce on
average. Sampled every time the rate is updated.
hlundin@chromium.org
The target jitter buffer delay for the receiving side. Sampled once every 10
ms per WebRTC receive stream when WebRTC audio is playing.
Removed from code 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Duration in milliseconds of WebRTC audio capture session.
henrika@chromium.org
Audio input channel layout in WebRTC.
No longer exists in the code as of 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Size of WebRTC audio input buffers (in audio frames).
No longer exists in the code as of 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Size of WebRTC audio input buffers (atypical values, in audio frames).
henrika@chromium.org
Audio input sample rate for WebRTC (in Hz).
henrika@chromium.org
Audio input sample rate for WebRTC (atypical values, in Hz).
Removed from code on 2014/2/25.
Please list the metric's owners. Add more owner tags as needed.
Audio output channel layout in WebRTC.
Removed from code Sep 2014.
henrika@chromium.org
Size of WebRTC audio output buffers (in audio frames).
Removed from code Sep 2014.
henrika@chromium.org
Size of WebRTC audio output buffers (atypical values, in audio frames).
henrika@chromium.org
Audio output sample rate for WebRTC (in Hz).
henrika@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.
Deprecated as of Aug 2016, replaced by
Media.Audio.Render.GetSourceDataTime.WebRTC.
henrika@chromium.org
Measures the time spent in WebRtcAudioRenderer::SourceCallback. Sampled 10
times per second.
holmer@chromium.org
The bandwidth estimate 2 seconds into a WebRTC call.
holmer@chromium.org
The number of video packets lost durig the first 2 seconds in a WebRTC call.
holmer@chromium.org
The round-trip time as measured 2 seconds into a WebRTC call.
holmer@chromium.org
The difference between the bandwidth estimate at 2 seconds and 20 seconds
into a WebRTC call, with a min at 0, which is supposed to capture the how
much the initial bandwidth estimate overshot the actual bandwidth available.
philipel@chromium.org
The bitrate that will be probed, triggered by an update to the max
configured bitrate.
philipel@chromium.org
The resulting bitrate probed, triggered by an update to the max configured
bitrate.
philipel@chromium.org
A successful probing attempt for a given bitrate, triggered by an update to
the max configured bitrate. NOTE! This is not the resulting bitrate from a
probing attempt, see WebRTC.BWE.MidCallProbing.ProbedKbps.
holmer@chromium.org
The time it takes the estimated bandwidth to reach 1000 kbps from the first
RTCP packet received. Used to measure the bandwidth ramp-up time.
holmer@chromium.org
The time it takes the estimated bandwidth to reach 2000 kbps from the first
RTCP packet received. Used to measure the bandwidth ramp-up time.
holmer@chromium.org
The time it takes the estimated bandwidth to reach 500 kbps from the first
RTCP packet received. Used to measure the bandwidth ramp-up time.
holmer@chromium.org
The bandwidth estimation used in WebRTC calls. Records whether the BWE is
running on the sender or the receiver and what BWE related RTP header
extensions are in use.
holmer@chromium.org
Average audio bitrate received during a call, counted from first packet
received until Call instance is destroyed. Only mesured for calls that are
at least 10 seconds long.
holmer@chromium.org
Average total bitrate received during a call (audio + video + RTCP), counted
from first packet received until Call instance is destroyed. Only mesured
for calls that are at least 10 seconds long.
holmer@chromium.org
Average estimated send bitrate during a call, counted from first packet sent
until Call instance is destroyed. Only mesured for calls that are at least
10 seconds long.
asapersson@chromium.org
The lifetime of a call. Recorded when a Call instance is destroyed.
holmer@chromium.org
Average pacer bitrate during a call, counted from first packet sent until
Call instance is destroyed. Only mesured for calls that are at least 10
seconds long.
holmer@chromium.org
Average RTCP bitrate received during a call, counted from first packet
received until Call instance is destroyed. Only mesured for calls that are
at least 10 seconds long.
saza@chromium.org
The amount of time between the arrival of the first and last audio RTP
packets to pass through a Call object. This is logged when the Call object
is destroyed. This is only logged if audio RTP packets are at some point in
time received, and is a way to omit temporary objects that do not send any
actual media.
saza@chromium.org
The amount of time between the arrival of the first and last video RTP
packets to pass through a Call object. This is logged when the Call object
is destroyed. This is only logged if video RTP packets are at some point in
time received, and is a way to omit temporary objects that do not send any
actual media.
saza@chromium.org
The amount of time between sending the first and the last audio RTP packets
through the audiostreams of a Call object. This is logged when the Call
object is destroyed. This is only logged if audio RTP packets are at some
point in time received, and is a way to omit temporary objects that do not
send any actual media.
holmer@chromium.org
Average video bitrate received during a call, counted from first packet
received until Call instance is destroyed. Only mesured for calls that are
at least 10 seconds long.
perkj@chromium.org
Counters on creation, opening, and a few main attributes of data channels.
perkj@chromium.org
The maximum number of retransmissions that are attempted in unreliable mode.
It is set to the value used in the configuration when a RTCDataChannel is
created.
perkj@chromium.org
The length of the time window during which transmissions and retransmissions
may occur in unreliable mode. It is set to the value used in the
configuration when a RTCDataChannel is created.
jiayl@chromium.org
Counters on creation of DesktopCaptureDevice and the first capture call.
zhihuang@chromium.org
Counters on different types of TCP socket error code. Collected when we hit
the error code when writing.
zhihuang@chromium.org
Counters on different types of UDP socket error code. Collected when we hit
the error code when writing.
guoweis@chromium.org
Counters on various types of NAT observed. This is logged once per session.
perkj@chromium.org
Number of data channels created per PeerConnection. Sample added to the
histogram when the PeerConnection is destroyed. Note that this is done
purely on the renderer side, so no sample will be generated when the
renderer process is destroyed (as in the fast shutdown path for the
renderer) before the PeerConnection is destroyed.
guoweis@chromium.org
Counters of various ICE Endpoint types. These values are logged for the
first selected candidate pair of a PeerConnection.
guoweis@chromium.org
Counters of ICE Connection states. These values are logged when the
PeerConnection gets into that state for the first time or after the ICE
restart.
zhihuang@chromium.org
Records the error whenever the Dtls handshake fails. There are only two
types of errors, incompatitable cipher suite and unknown error, for now.
honghaiz@chromium.org
Records the reasons for ICE re-gathering.
honghaiz@chromium.org
Records the transport channel states when ICE restart happens.
mallinath@chromium.org
Counters on IPv4 and IPv6 usage in PeerConnection. These values are logged
once per PeerConnection.
guoweis@chromium.org
Whether the permission to collect the local IP addresses in WebRTC has been
requested and/or granted. This is collected the first time when networks
updated event is reported or if never reported, during the destruction phase
of a call.
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.
hta@chromium.org
What key exchange protocol (DTLS or SDES) is used to establish the crypto
keys for a PeerConnection's RTP transport.
hta@chromium.org
What key exchange protocol (DTLS or SDES) is used to establish the crypto
keys for a PeerConnection's RTP transport, specified per media type.
pthatcher@chromium.org
Whether RTCP-mux is used for the PeerConnection (both the local and remote
description enable RTCP-mux). Recorded after SetLocalDescription and
SetRemoteDescription are called, once per PeerConnection.
steveanton@chromium.org
What SDP format is received in the remote offer. The value "no
tracks" means that no audio or video tracks were received. The value
"simple" means that at most one audio and at most one video track
was received. The value "complex" means that more than one audio
or more than one video track was received, and how this was signaled is
indicated ("Plan B" meaning with a=ssrc lines within the same m=
section and "Unified Plan" meaning with a separate m= section).
hta@chromium.org
What SDP semantic (Unified Plan or Plan B) was detected when completing
negotiation of a PeerConnection. This is recorded when accepting an SDP
Answer. The value "mixed" means that the accepted answer included
both types of marker in the SDP. The value "none" will happen when
the answerer sends no media.
hta@chromium.org
What SDP semantic (Unified Plan, Plan B or "use default") has been
asked for by the creator of a PeerConnection.
Deprecated on Dec 2016. This histogram is used to gauge the risk of making
the change for issue 6030. The decision has been made and this is not needed
any more.
zhihuang@chromium.org
Whether the application specified a value for RTCP-mux policy, and if so,
which value, "Require" or "Negotiate". Recorded after
parsing the configuration when creating the RTCPeerConnection.
steveanton@chromium.org
What error code is reported by libsrtp when failing to unprotect an incoming
SRTCP (secured media control) packet.
guoweis@chromium.org
Counters on the type of SRTP crypto suites used by WebRTC. This is collected
whenever the transport signals the OnCompleted event.
steveanton@chromium.org
What error code is reported by libsrtp when failing to unprotect an incoming
SRTP (secured media) packet.
guoweis@chromium.org
Counters on the type of SSL cipher suites used by WebRTC. This is collected
whenever the transport signals the OnCompleted event.
mallinath@chromium.org
Time to setup a peer to peer call with PeerConnection.
guoweis@chromium.org
Time to receive the first SignalNetworksChanged from the request to start
updating network in PeerConnection.
hta@chromium.org
Capsule history of a WebRTC PeerConnection, encoded as a sequence of bits
encapsulated in an integer. Only a few values will be deemed interesting,
but the interesting values may change over time.
perkj@chromium.org
Durations of audio tracks received over a PeerConnection. The stopwatch
starts when the track first becomes connected, and ends when it is
disconnected or very soon thereafter.
perkj@chromium.org
Durations of video tracks received over a PeerConnection. The stopwatch
starts when the track first becomes connected, and ends when it is
disconnected or very soon thereafter.
perkj@chromium.org
Sizes of messages sent over reliable data channels. The size of an
individual message is added to the histogram as a sample immediately when a
message is sent.
jiayl@chromium.org
Time for capturing one frame in screen capturing.
perkj@chromium.org
Durations of audio tracks sent over a PeerConnection. The stopwatch starts
when the track first becomes connected, and ends when it is disconnected or
very soon thereafter.
perkj@chromium.org
Durations of video tracks sent over a PeerConnection. The stopwatch starts
when the track first becomes connected, and ends when it is disconnected or
very soon thereafter.
guoweis@chromium.org
For clients using a shared source port per STUN binding request toward the
specified servers, success rate for requests which received a response with
various intervals between requests. Only the first instance of renderers
will conduct the trial and log this result. The STUN binding requests are
grouped into multiple batches and the success rate is calculated for an
individual batch.
guoweis@chromium.org
For clients using a shared source port per STUN binding request, average RTT
for requests which received a response with various intervals between
requests. Only the first instance of renderers will conduct the trial and
log this result.
guoweis@chromium.org
For clients using a shared source port per STUN binding request, success
rate for requests which received a response with various intervals between
requests. Only the first instance of renderers will conduct the trial and
log this result.
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.
Replaced by WebRTC.UserMediaRequest.Result2 in Feb 2018.
andresp@chromium.org
Counters for UserMediaRequests results such as failure reasons.
grunell@chromium.org
Counters for UserMediaRequests results such as failure reasons. The standard
specification error names are in parenthesis.
asapersson@chromium.org
The average number of adaptation changes per minute for a sent video stream.
Recorded when a stream is removed.
holmer@chromium.org
The average round-trip time of a WebRTC call in milliseconds. Recorded when
a stream is removed.
asapersson@chromium.org
The absolute value of the sync offset between a rendered video frame and the
latest played audio frame is measured per video frame. The average offset
per received video stream is recorded when a stream is removed.
sprang@chromium.org
Fraction of time the call was classified as bad because of any reason.
sprang@chromium.org
Fraction of time the call was classified as bad because of low framerate.
sprang@chromium.org
Fraction of time the call was classified as bad because of high framerate
variance.
sprang@chromium.org
Fraction of time the call was classified as bad because of high qp.
asapersson@chromium.org
Percentage of sent frames that are limited in resolution due to bandwidth
for a sent video stream. Recorded when a stream is removed.
asapersson@chromium.org
For frames that are limited in resolution due to bandwidth, the average
number of disabled resolutions is recorded for a sent video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The number of received bits per second for a received video stream. Recorded
when a stream is removed. The total number of bytes is divided by the time
the video stream exists.
asapersson@chromium.org
The number of sent bits per second for a sent video stream. Recorded when a
stream is removed. The total number of bytes is divided by the time the
video stream exists.
asapersson@chromium.org
The number of complete frames received per second for a received video
stream. Recorded when a stream is removed. The total number of frames is
divided by the time the video stream exists.
asapersson@chromium.org
Percentage of frames that are limited in resolution due to CPU for a sent
video stream. Recorded when a stream is removed.
asapersson@chromium.org
Average current delay for a received video stream. This is the actual delay
imposed on frames (where the goal is to reach the target delay (see
WebRTC.Video.TargetDelayInMs)). Recorded when a stream is removed.
asapersson@chromium.org
The average QP (quantizer value) per frame for a received VP8 video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of decoded frames per second for a received video stream.
Recorded when a stream is removed. The total number of frames is divided by
the time the video stream exists.
asapersson@chromium.org
The average decode time per frame for a received video stream. Recorded when
a stream is removed.
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.
ilnik@chromium.org
Total number of frames dropped by a capturer for a sent video stream.
Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped by an encoder's internal rate limiter for a
sent video stream. Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped because encoder queue is full for a sent
video stream. Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped by a WebRTC rate limiter (in MediaOpt) for a
sent video stream. Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped by a WebRTC on the receive side because they
are incomplete or undecodable.
asapersson@chromium.org
Percentage of duplicated packets in the jitter buffer for a received video
stream. Recorded when a stream is removed.
asapersson@chromium.org
The average QP (quantizer value) per frame for a sent video stream. Recorded
when a stream is removed.
asapersson@chromium.org
Configured video codec for a sent video stream. Recorded when a
VideoSendStream is destroyed (for streams whose lifetime is longer than 10
seconds).
asapersson@chromium.org
The average encode time per frame for a sent video stream. Recorded when a
stream is removed.
asapersson@chromium.org
The average end-to-end delay per frame for a received video stream. Recorded
when a stream is removed.
ilnik@chromium.org
The maximum end-to-end delay per frame for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The number of received FEC bits per second for a received video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent FEC bits per second for a sent video stream. Recorded
when a stream is removed. The total number of bytes is divided by the time
the video stream exists.
asapersson@chromium.org
The number of received RTCP FIR packets per minute for a sent video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent RTCP FIR packets per minute for a received video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
hbos@chromium.org
The number of |H264DecoderImpl| events, such as an initialization or
decoding error, that have occurred. At most one Init and one Error is
reported per |H264DecoderImpl| instance. This is to avoid the same event
from being reported multiple times (e.g. if there is an error you might
re-initialize or get a decode error every frame which would otherwise
pollute the data).
hbos@chromium.org
The number of |H264EncoderImpl| events, such as an initialization or
encoding error, that have occurred. At most one Init and one Error is
reported per |H264EncoderImpl| instance. This is to avoid the same event
from being reported multiple times (e.g. if there is an error you might
re-initialize or get an encode error every frame which would otherwise
pollute the data).
asapersson@chromium.org
The number of incoming frames per second for a sent video stream. Recorded
when a stream is removed. The total number of frames is divided by the time
the video stream exists.
asapersson@chromium.org
The average input height per frame (for incoming frames to video engine) for
a sent video stream. Recorded when a stream is removed.
asapersson@chromium.org
The average input width per frame (for incoming frames to video engine) for
a sent video stream. Recorded when a stream is removed.
ilnik@chromium.org
The 95th percentile of interframe delay for a received video stream.
Recorded when a stream is removed.
ilnik@chromium.org
The average interframe delay for a received video stream. Recorded when a
stream is removed.
ilnik@chromium.org
The maximum interframe delay for a received video stream. Recorded when a
stream is removed.
asapersson@chromium.org
Average jitter buffer delay for a received video stream. Recorded when a
stream is removed.
asapersson@chromium.org
Permille of frames that are key frames for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
Permille of frames that are key frames for a sent video stream. Recorded
when a stream is removed.
ilnik@chromium.org
The average duration of a freeze in video playback. Recorded then a recieve
stream is removed or content type changes.
ilnik@chromium.org
The average duration of a smooth video playback. Recorded then a recieve
stream is removed or content type changes.
asapersson@chromium.org
The number of received media payload bits per second for a received video
stream. Recorded when a stream is removed. The total number of bytes is
divided by the time the video stream exists.
asapersson@chromium.org
The number of sent media payload bits per second for a sent video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
asapersson@chromium.org
The number of received RTCP NACK packets per minute for a sent video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent RTCP NACK packets per minute for a received video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of times a video stream has been paused/resumed during a call.
Recorded when a stream is removed.
ilnik@chromium.org
The average number of resolution down-switches per minute for a receive
video stream. Recorded then a stream is removed or content type changes.
asapersson@chromium.org
Average delay (network delay (rtt/2) + jitter delay + decode time + render
delay) for a received video stream. Recorded when a stream is removed.
asapersson@chromium.org
The number of received padding bits per second for a received video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent padding bits per second for a sent video stream. Recorded
when a stream is removed. The total number of bytes is divided by the time
the video stream exists.
asapersson@chromium.org
Percentage of time that the video has been paused for a sent video stream.
Recorded when a stream is removed.
asapersson@chromium.org
The number of received RTCP PLI packets per minute for a sent video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent RTCP PLI packets per minute for a received video stream.
Recorded when a stream is removed. The total number of packets is divided by
the time the video stream exists.
asapersson@chromium.org
For frames that are downscaled in resolution due to quality, the average
number of downscales is recorded for a sent video stream. Recorded when a
stream is removed.
asapersson@chromium.org
Percentage of sent frames that are downscaled in resolution due to quality
for a sent video stream. Recorded when a stream is removed.
asapersson@chromium.org
Percentage of received FEC packets for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The average received height per frame for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
Percentage of received packets lost for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The average received width per frame for a received video stream. Recorded
when a stream is removed.
asapersson@chromium.org
The lifetime of a video receive stream. Recorded when a VideoReceiveStream
instance is destroyed.
asapersson@chromium.org
Percentage of recovered media packets from FEC packets for a received video
stream. Recorded when a stream is removed.
asapersson@chromium.org
The number of sent frames to the renderer per second for a received video
stream. Recorded when a stream is removed. The total number of frames is
divided by the time the video stream exists.
asapersson@chromium.org
The number of pixels (sqrt(width*height)) of sent frames to the renderer per
second for a received video stream. Recorded when a stream is removed. The
total number of pixels is divided by the time the video stream exists.
asapersson@chromium.org
The number of retransmitted bits per second for a received video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
asapersson@chromium.org
The number of retransmitted bits per second for a sent video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
asapersson@chromium.org
The absolute value of the difference between the estimated frequency during
RTP timestamp to NTP time conversion and the actual value (i.e. 90 kHz) is
measured per received video frame. The max offset during 40 second intervals
is stored. The average of these stored offsets per received video stream is
recorded when a stream is removed.
asapersson@chromium.org
The number of received bits over RTX per second for a received video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
asapersson@chromium.org
The number of sent bits over RTX per second for a sent video stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
sprang@chromium.org
Percentage of sent frames that are limited in resolution due to bandwidth
for a sent (screen content) video stream. Recorded when a stream is removed.
sprang@chromium.org
For frames that are limited in resolution due to bandwidth, the average
number of disabled resolutions is recorded for a sent (screen content) video
stream. Recorded when a stream is removed.
sprang@chromium.org
The number of sent bits per second for a sent screenshare stream. Recorded
when a stream is removed. The total number of bytes is divided by the time
the video stream exists.
ilnik@chromium.org
The average QP (quantizer value) per frame for a received VP8 screenshare
stream. Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped by a capturer for a sent screenshare stream.
Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped by an encoder's internal rate limiter for a
sent screenshare stream. Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped because encoder queue is full for a sent
screenshare stream. Recorded when a stream is removed.
ilnik@chromium.org
Total number of frames dropped by a WebRTC rate limiter (in MediaOpt) for a
sent screenshare stream. Recorded when a stream is removed.
sprang@chromium.org
The average encode time per frame for a sent (screen content) video stream.
Recorded when a stream is removed.
ilnik@chromium.org
The average end-to-end delay per frame for a received screenshare stream.
Recorded when a stream is removed.
ilnik@chromium.org
The maximum end-to-end delay per frame for a received screenshare stream.
Recorded when a stream is removed.
sprang@chromium.org
The number of sent FEC bits per second for a sent screenshare stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
sprang@chromium.org
The number of received RTCP FIR packets per minute for a sent screenshare
stream. Recorded when a stream is removed. The total number of packets is
divided by the time the video stream exists.
sprang@chromium.org
Ratio of sent frames to dropped frames at the encoder. The value is reported
when a stream is removed and is calculated as the total number frames sent
divided by the number of dropped frames.
sprang@chromium.org
Ratio of sent frames to number of re-encoded frames (due to target bitrate
overshoot). The value is reported when a stream is removed and is calculated
as the total number frames sent divided by the number of re-encoded frames.
asapersson@chromium.org
The number of incoming frames per second for a sent (screen content) video
stream. Recorded when a stream is removed. The total number of frames is
divided by the time the video stream exists.
sprang@chromium.org
The average input height per frame (for incoming frames to video engine) for
a sent (screen content) video stream. Recorded when a stream is removed.
sprang@chromium.org
The average input width per frame (for incoming frames to video engine) for
a sent (screen content) video stream. Recorded when a stream is removed.
ilnik@chromium.org
The 95th percentile of interframe delay for a received screenshare stream.
Recorded when a stream is removed.
ilnik@chromium.org
The average interframe delay for a received screenshare stream. Recorded
when a stream is removed.
ilnik@chromium.org
The maximum interframe delay for a received screenshare stream. Recorded
when a stream is removed.
ilnik@chromium.org
Permille of frames that are key frames for a received screenshare stream.
Recorded when a stream is removed.
sprang@chromium.org
Permille of frames that are key frames for a sent (screen content) video
stream. Recorded when a stream is removed.
sprang@chromium.org
Stats for the lower layer (TL0) of a screenshare stream in conference mode.
sprang@chromium.org
Stats for the higher layer (TL1) of a screenshare stream in conference mode.
ilnik@chromium.org
The average duration of a freeze in screenshare playback. Recorded then a
recieve stream is removed or content type changes.
ilnik@chromium.org
The average duration of a smooth video playback for screenshare stream.
Recorded then a recieve stream is removed or content type changes.
ilnik@chromium.org
The number of received media payload bits per second for a received
screenshare stream. Recorded when a stream is removed. The total number of
bytes is divided by the time the video stream exists.
sprang@chromium.org
The number of sent media payload bits per second for a sent screenshare
stream. Recorded when a stream is removed. The total number of bytes is
divided by the time the video stream exists.
sprang@chromium.org
The number of received RTCP NACK packets per minute for a sent screenshare
stream. Recorded when a stream is removed. The total number of packets is
divided by the time the video stream exists.
ilnik@chromium.org
The average number of resolution down-switches per minute for a receive
screenshare stream. Recorded then a stream is removed or content type
changes.
sprang@chromium.org
The number of sent padding bits per second for a sent screenshare stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
sprang@chromium.org
The number of received RTCP PLI packets per minute for a sent screenshare
stream. Recorded when a stream is removed. The total number of packets is
divided by the time the video stream exists.
sprang@chromium.org
For frames that are downscaled in resolution due to quality, the average
number of downscales is recorded for a sent (screen content) video stream.
Recorded when a stream is removed.
sprang@chromium.org
Percentage of sent frames that are downscaled in resolution due to quality
for a sent (screen content) video stream. Recorded when a stream is removed.
ilnik@chromium.org
The average received height per frame for a received screenshare stream.
Recorded when a stream is removed.
ilnik@chromium.org
Percentage of received packets lost for a received screenshare stream.
Recorded when a stream is removed.
ilnik@chromium.org
The average received width per frame for a received screenshare stream.
Recorded when a stream is removed.
ilnik@chromium.org
The lifetime of a screenshare receive stream. Recorded when a
VideoReceiveStream instance is destroyed.
sprang@chromium.org
The number of retransmitted bits per second for a sent screenshare stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
sprang@chromium.org
The number of sent bits over RTX per second for a sent screenshare stream.
Recorded when a stream is removed. The total number of bytes is divided by
the time the video stream exists.
sprang@chromium.org
The average delay (of average delays) of sent packets for a sent (screen
content) video stream. Recorded when a stream is removed. The delay is
measured from a frame is input to video engine until a packet is sent to the
network. For each sent packet, the average delay of all sent packets over
the last second is reported. The average of these reported delays is
recorded.
sprang@chromium.org
The average delay (of max delays) of sent packets for a sent (screen
content) video stream. Recorded when a stream is removed. The delay is
measured from a frame is input to video engine until a packet is sent to the
network. For each sent packet, the maximum delay of all sent packets over
the last second is reported. The average of these reported delays is
recorded.
asapersson@chromium.org
The number of sent frames per second for a sent (screen content) video
stream. Recorded when a stream is removed. The total number of frames is
divided by the time the video stream exists.
sprang@chromium.org
The average sent height per frame for a sent (screen content) video stream.
Recorded when a stream is removed.
sprang@chromium.org
Percentage of sent packets lost for a sent screenshare stream. Recorded when
a stream is removed.
ilnik@chromium.org
Ratio between Screenshare.SentFramesPerSecond and
Screenshare.InputFramesPerSecond in percents. Recorded when a stream is
removed. The total number of sent frames is divided by the total number of
input frames and multiplied by 100.
sprang@chromium.org
The average sent width per frame for a sent (screen content) video stream.
Recorded when a stream is removed.
ilnik@chromium.org
Percentage of time the recieve screenshare stream playbacks low quality
blocky video. Recorded then a stream is removed or content type changes.
ilnik@chromium.org
Percentage of time the recieve screenshare stream playbacks HD resolution.
Recorded then a stream is removed or content type changes.
sprang@chromium.org
Percentage of unique RTCP NACK requests that are received in response to a
sent screenshare stream. Recorded when a stream is removed.
asapersson@chromium.org
The average send delay of sent packets for a sent video stream. Recorded
when a stream is removed. The delay is measured from a packet is sent to the
transport until leaving the socket.
asapersson@chromium.org
The average delay (of average delays) of sent packets for a sent video
stream. Recorded when a stream is removed. The delay is measured from a
frame is input to video engine until a packet is sent to the network. For
each sent packet, the average delay of all sent packets over the last second
is reported. The average of these reported delays is recorded.
asapersson@chromium.org
The average delay (of max delays) of sent packets for a sent video stream.
Recorded when a stream is removed. The delay is measured from a frame is
input to video engine until a packet is sent to the network. For each sent
packet, the maximum delay of all sent packets over the last second is
reported. The average of these reported delays is recorded.
asapersson@chromium.org
The lifetime of a video send stream. Recorded when a VideoSendStream
instance is destroyed.
asapersson@chromium.org
The number of sent frames per second for a sent video stream. Recorded when
a stream is removed. The total number of frames is divided by the time the
video stream exists.
asapersson@chromium.org
The average sent height per frame for a sent video stream. Recorded when a
stream is removed.
asapersson@chromium.org
Percentage of sent packets lost for a sent video stream. Recorded when a
stream is removed.
ilnik@chromium.org
Ratio between SentFramesPerSecond and InputFramesPerSecond in percents.
Recorded when a stream is removed. The total number of sent frames is
divided by the total number of input frames and multiplied by 100.
asapersson@chromium.org
The average sent width per frame for a sent video stream. Recorded when a
stream is removed.
asapersson@chromium.org
Average target delay (jitter delay + decode time + render delay) for a
received video stream. Recorded when a stream is removed.
ilnik@chromium.org
Percentage of time the recieve video stream playbacks low quality blocky
video. Recorded then a stream is removed or content type changes.
ilnik@chromium.org
Percentage of time the recieve video stream playbacks HD resolution.
Recorded then a stream is removed or content type changes.
asapersson@chromium.org
Percentage of unique RTCP NACK requests that are received in response to a
sent video stream. Recorded when a stream is removed.
asapersson@chromium.org
Percentage of unique RTCP NACK requests that are sent in response to a
received video stream. Recorded when a stream is removed.
perkj@chromium.org
Counts occurences of if the VP8 software decoder runs out of buffers due to
that they are not returned to the buffer pool. See http://crbug/652923 and
http://crbug/542522.
perkj@chromium.org
mcasas@chromium.org
emircan@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.
mgiuca@chromium.org
Counts the number of calls to navigator.share. Includes both successful and
failed shares.
mgiuca@chromium.org
Records the outcome of calls to navigator.share. This will not count any
calls that never complete (e.g., if the page closes while the picker is
open). Therefore, DO NOT look at the raw percentages of this histogram;
instead, compare these numbers with the WebShare.ApiCount.Share total.
NOTE: At the moment, if the user cancels the picker, its recording will be
delayed, and possibly never recorded (https://crbug.com/636274), so that
will account for a discrepancy between ShareOutcome and ApiCount.Share.
estark@chromium.org
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.
Deprecated October 2016 in favor of Security.PageInfo.Action.HttpsUrl.Valid,
Security.PageInfo.Action.HttpsUrl.Dangerous, and
Security.PageInfo.Action.HttpsUrl.Downgraded.
estark@chromium.org
Tracks WebsiteSettings actions that take place on an HTTPS URL. This
completely disregards security status.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is changed using the
content settings menu.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is set to 'Allowed'
using the content settings menu.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is set to 'Ask'
using the content settings menu.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is set to 'Blocked'
using the content settings menu.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
miguelg@chromium.org
finnur@chromium.org
Count of how often a specific content type (permission) is reset to the
default value using the content settings menu.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
timloh@chromium.org
Count of how often a specific content type (permission) is changed to the
session only value using the content settings menu. This option only exists
for cookies.
sashab@chromium.org
felt@chromium.org
Count of how often a specific content type (permission) is changed using the
Origin Info dialog.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
sashab@chromium.org
felt@chromium.org
Count of how often a specific content type (permission) is set to 'Allowed'
using the Origin Info dialog.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
sashab@chromium.org
felt@chromium.org
Count of how often a specific content type (permission) is set to 'Blocked'
using the Origin Info dialog.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
Deprecated 12/2014 in Issue 433776, and replaced by
WebsiteSettings.OriginInfo.PermissionChanged.
sashab@chromium.org
Count of how often a specific content type (permission) is changed using the
Page Info UI.
Note: The values of this metric collected for Chrome 49 (early 2016) are
innacurate and should not be trusted. crbug.com/589255.
cmumford@chromium.org
The time required to try (and fail) to open a Web SQL database.
cmumford@chromium.org
The time required to successfully open a Web SQL database.
michaeln@chromium.org
Counts the number of WebSQL databases opened for secure vs insecure origins.
jackhou@chromium.org
The success or failure of all extension installs from the webstore. This
includes those initiated by sync.
joshwoodward@google.com
Webstore Widget app: the reason why the suggest apps dialog was closed.
joshwoodward@google.com
Webstore Widget app: whether the Webstore item user selected was
successfully installed or not.
joshwoodward@google.com
Webstore Widget app: whether the initialization of the dialog succeeded or
not.
joshwoodward@google.com
Webstore Widget app: time to load the widget contained in the app. Measured
between the moment window appears and the moment all the contents in the app
including the Chrome Webstore widget are ready.
dbeam@chromium.org
URLs for which Chrome creates WebUIControllers.
dschuyler@chromium.org
tbuckley@chromium.org
bettes@chromium.org
Paths within chrome://settings visited. For evaluating popularity and
priorities for chrome://settings GUI.
reillyg@chromium.org
juncai@chromium.org
Records the reason why the WebUSB device chooser was closed.
reillyg@chromium.org
juncai@chromium.org
Records the time spent initializing the WebUSB detector module.
reillyg@chromium.org
juncai@chromium.org
Records the reason why the "WebUSB device detected" notification
was dismissed.
reillyg@chromium.org
juncai@chromium.org
Records when the user revokes permission for an origin to connect to a USB
device using the WebUSB API.
Obsolete 04/04/2018 as it has been replaced by
Android.WebView.LoadDataWithBaseUrl.HistoryUrl.
jamwalla@chromium.org
Records whether the historyUrl parameter to loadDataWithBaseUrl is empty/
null, the same as the baseUrl parameter, or different from baseUrl.
tmartino@chromium.org
Records the result of promoting sign-in via the Welcome page.
tmartino@chromium.org
Records whether or not Chrome was the default browser when the user left the
Win10-specific Welcome page.
pmonette@chromium.org
tmartino@chromium.org
Emits a "true" sample when the revamped WebUI-based welcome page
is added to the startup tabs list. This means that barring an error on
startup, it was shown to the user. This histogram can only be recorded
during first-run flow, when the EnableWelcomeWin10 experiment is enabled.
pmonette@chromium.org
tmartino@chromium.org
Emits a "true" sample when the old external welcome page is added
to the startup tabs list. This means that barring an error on startup, it
was shown to the user. This histogram can only be recorded during first-run
flow, when the EnableWelcomeWin10 experiment is disabled.
pmonette@chromium.org
tmartino@chromium.org
Records whether or not the check that verifies if Chrome is pinned to the
taskbar has timed out. This check is done when the welcome page is opened in
order to determine which instructions to display to the user.
tmartino@chromium.org
Records whether or not Chrome was pinned to the taskbar when the user left
the Win10-specific Welcome page.
sahel@chromium.org
Records whether or not a GSU event with wheel source is latched to the
current scrolling element. It is false for the first GSU event of every
scrolling sequence and true for the rest of the GSU events.
zturner@chromium.org
Count of page loads in each of the 2 different environments (metro/desktop)
on Windows 8.
kuscher@chromium.org
The number of app windows open when a load completes. This includes windows
opened by an app shortcut, or apps opened in a popup. This only counts v1
apps.
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.
fdoray@chromium.org
The amount of CPU time a call to ComputeNativeWindowOcclusionStatus() takes.
stanisc@chromium.org
Time spent inside CreateThread() Windows API call creating a single thread.
grt@chromium.org
The Windows error code relating to a failed attempt to operate on a file or
a directory.
scottmg@chromium.org
The Windows version (base::win::Version) as reported by GetVersionEx(). This
is queried shortly after startup.
gab@chromium.org
The value of TimeTicks::IsHighResolution(). Reported once per browser
session, on startup.
stanisc@chromium.org
Percentage of elapsed time the high resolution timer is activated. The usage
is reported by each of Chrome processes individually (without aggregation)
and logged every 10 minutes.
scottmg@chromium.org
A boolean used to indicate when the Windows version reported by
GetVersionEx() and the Windows version reported by VerQueryValue() on
kernel32 do not match. This is queried shortly after startup.
pmonette@chromium.org
Indicates whether Chrome is pinned to the Windows taskbar for the current
user. Recorded shortly after startup.
pmonette@chromium.org
Indicates whether a connection error occured between the browser and the
shell handler process. This is usually caused by a crash in the utility
process. This is logged every time the pinned state is queried.
scottmg@chromium.org
The Windows version (base::win::Version) as reported by VeryQueryValue() on
kernel32.dll. This is queried shortly after startup.
fdoray@chromium.org
The number of Chrome browser windows in a given visibility state. This is
computed using ComputeNativeWindowOcclusionStatus() and is recorded every 10
minutes.
wfh@chromium.org
The 32-bit hash of the lower-case parent process basename (e.g.
explorer.exe) of the main Chrome executable. Reported once during startup as
part of install verification.
grt@chromium.org
The state of an item in the filesystem following an operation on it.
zturner@chromium.org
Count of browser launches from a Windows tablet pc.
Deprecated 10/2016 as this is enabled by default so provides no useful data.
wfh@chromium.org
Count of browser launches where Win32k renderer lockdown is enabled.
noms@chromium.org
The type of category clicked in the Windows Jumplist
Obsolete 07/06/2017 as we are no long recording this metric.
chengx@chromium.org
The number of jumplist icons requested to create per jumplist update. It is
recorded whenever UpdateJumpList() is called.
Obsolete 07/06/2017 as we are no long recording this metric.
chengx@chromium.org
Time spent in CreateIconFiles(). This method is called whenever there is a
jumplist update and the JumpListIcons folder is empty.
Obsolete 07/06/2016 as we are no long recording this metric.
chengx@chromium.org
Time spent in DeleteDirectoryContentAndLogRuntime().
Obsolete 04/25/2017 as we are no long recording this metric.
chengx@chromium.org
Time spent in DeleteDirectoryAndLogResults().
Obsolete 04/25/2017 as we are no long recording this metric.
chengx@chromium.org
This metric records the detailed delete result of JumpListIcons directory.
Obsolete 04/25/2017 as we are no long recording this metric.
chengx@chromium.org
This metric records the detailed delete result of JumpListIconsOld
directory.
Obsolete 12/13/2016 as we are no long recording this metric.
chengx@chromium.org
This metric is recorded when folder JumpListIcons is moved (can be rename or
copy and delete) to JumpListIconsOld. This happens when tabs are closed,
mostly visited URLs get updated, etc. There are several key steps in this
folder move operation. Before the move operation, there is another step that
JumpListIconsOld folder is deleted. The status of these steps are put
together and recorded in this metric. The failure of any of these steps is
suspected to be related to a known issue.
Obsolete 03/10/2017 as it is replaced by DetailedFolderResultsDeleteUpdated.
chengx@chromium.org
This metric is recorded when folders JumpListIcons and JumpListIconsOld get
updated. These two folders are updated when tabs are closed, mostly visited
URLs get updated, etc. These two folders are updated as follows 1)
JumpListIconsOld with its content get deleted; 2) if step 1 succeeds,
JumpListIcons is moved, 3) if any of the previous steps fails, JumpListIcons
is deleted, 4) A new JumpListIcons folder is created. The status of these 4
file operations are put together and recorded in this metric. The failure of
any of these file operations is suspected to be related to a known issue.
Obsolete 03/20/2017. New metrics named WinJumplist.DeleteStatusJumpListIcons
and WinJumplist.DeleteStatusJumpListIconsOld are used instead.
chengx@chromium.org
This metric is recorded when folders JumpListIcons and JumpListIconsOld get
updated. These two folders are updated when tabs are closed, mostly visited
URLs get updated, etc. These two folders are updated as follows 1)
JumpListIconsOld with its content get deleted; 2) if step 1 succeeds,
JumpListIcons is renamed to JumpListIconsOld, 3) if any of the previous
steps fails, JumpListIcons is deleted, 4) A new JumpListIcons folder is
created if deletion of JumpListIcons' content succeeds (only fail to delete
the directory is okay). The status of these 4 file operations are put
together and recorded in this metric. The failure of any of these file
operations is suspected to be related to a known issue.
Obsolete 04/25/2017 as we are no long recording this metric.
chengx@chromium.org
This metric records whether the folder JumpListIcons exists; and if it
does, whether it is empty or non-empty.
Obsolete 04/25/2017 as we are no long recording this metric.
chengx@chromium.org
This metric records whether the folder JumpListIconsOld exists; and if
it does, whether it is empty or non-empty.
Obsolete 12/08/2016. DetailedFolderMoveResults is used for more detailed
analysis.
chengx@chromium.org
This metric is recorded when folder JumpListIcons is moved (can be rename or
copy and delete) to JumpListIconsOld. This happens when tabs are closed,
mostly visited URLs get updated, etc. There are 3 possible steps in this
folder move operation. Before the move operation, there is another step that
JumpListIconsOld folder is deleted. The status of these steps are put
together and recorded in this metric. The failure of any of these steps is
suspected to be related to a known issue listed below.
https://bugs.chromium.org/p/chromium/issues/detail?id=179576
Obsolete 12/13/2016, as we are now recording DetailedFolderResults.
chengx@chromium.org
This metric is recorded when folders JumpListIcons and JumpListIconsOld get
updated. These two folders are updated when tabs are closed, mostly visited
URLs get updated, etc. These two folders are updated as follows 1)
JumpListIconsOld with its content get deleted; 2) JumpListIcons is moved, 3)
A new JumpListIcons folder is created. The status of these three file
operations are put together and recorded in this metric. The failure of any
of these file operations is suspected to be related to a known issue.
Obsolete 07/10/2017 as it's no longer needed.
chengx@chromium.org
The time interval between two adjacent update notifications if it's less
than 3500 ms.
Obsolete 07/23/2017 as it's no longer needed.
chengx@chromium.org
The time interval between two adjacent update notifications. A zero value
indicates the interval is greater than 3500 ms.
Obsolete 06/22/2017 as it's no longer needed.
chengx@chromium.org
Time spent in OnFaviconDataAvailable().
Obsolete 07/23/2017 as it's no longer needed.
chengx@chromium.org
The ratio of the duration spent adding the most-visited category compared to
the duration spent adding the recently-closed category, multiplied by 10.
Obsolete 06/22/2017 as it's no longer needed.
chengx@chromium.org
Time spent in StartLoadingFavicon().
Obsolete 04/20/2017 as it's no longer accurate due to the code change.
chengx@chromium.org
Time spent in UpdateJumpList(). This method is called whenever there is a
jumplist update.
Obsolete 07/26/2017 as it's no longer needed.
chengx@chromium.org
Time spent in JumpListUpdater::AddCustomCategory.
Obsolete 07/10/2017 as it's no longer needed.
chengx@chromium.org
Time spent in JumpListUpdater::AddTasks.
Obsolete 07/26/2017 as it's no longer needed.
chengx@chromium.org
Time spent in JumpListUpdater::BeginUpdate.
Obsolete 07/26/2017 as it's no longer needed.
chengx@chromium.org
Time spent in JumpListUpdater::CommitUpdate.
Removed 01/2017.
Please list the metric's owners. Add more owner tags as needed.
Incremented each time the TimeTicks field trial runs on a machine with
multiple cores, but failed to change thread affinity. Broken down by Windows
version.
Removed 01/2017.
Please list the metric's owners. Add more owner tags as needed.
The smallest non-zero delta reported by subsequent calls to
QueryPerformanceCounter.
Removed 01/2017.
Please list the metric's owners. Add more owner tags as needed.
True if the CPU's timestamp counter ticks at a constant rate regardless of
CPU frequency.
Removed 01/2017.
Please list the metric's owners. Add more owner tags as needed.
The number of times the TimeTicks field trial failed because
QueryPerformanceCounter ticked backwards. Broken down by Windows version.
Removed 01/2017.
Please list the metric's owners. Add more owner tags as needed.
The number of times the TimeTicks field trial succeeded. Broken down by
Windows version.
Removed 01/2017.
Please list the metric's owners. Add more owner tags as needed.
The number of times the TimeTicks field trial ran for comparison with
WinTimeTicks.VersionSuccess. Broken down by Windows version.
kinuko@chromium.org
Worker thread load, i.e. percentage of time spent on running tasks. This
metric is emitted at most once per kWorkerThreadLoadTrackerReportingInterval
sec per worker thread amortized. E.g. if a worker ran a single task for X
seconds and then went to idle for Y seconds before it shuts down, and
assuming the interval rate was 1 sec, we get X samples for 100% and Y
samples for 0%.
Deprecated on 2018-02.
nhiroki@chromium.org
The time taken for running a debugger task on WorkerThread.
nhiroki@chromium.org
Records the exit code of WorkerThread.
kinuko@chromium.org
The amount of time a worker thread ran for. Starts recording when a worker
scheduler for the thread is created, and stops when the scheduler is shut
down.
Deprecated on 2018-02. The sample count was overflowing. crbug.com/809672.
nhiroki@chromium.org
The time taken for running a worker task on WorkerThread.
ainslie@chromium.org
edwardjung@chromium.org
Number of times that each menu item is clicked.
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.
panicker@chromium.org
Records occurence of async XHR during page dismissal state (unload,
beforeunload, pagehide etc).
panicker@chromium.org
Records occurence of sync XHR during page dismissal state (unload,
beforeunload, pagehide etc).
billorr@chromium.org
Indicates which VR APIs are installed. Recorded shortly after startup.
offenwanger@chromium.org
The action that triggered the transition into Chrome in VR, either from 2D
or another VR app.
offenwanger@chromium.org
The action that triggered VR presentation, which is the display of web
content on a VR device.
klausw@chromium.org
Records the WebXR/WebVR render path used for presentation on presentation
start. The render path is affected by overrides and device capabilities.
hfung@chromium.org
The number of results (either query or URL) from ZeroSuggest. This is set
every time a successful response from ZeroSuggest is 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.
Original code deleted in a refactoring.
Deprecated 03/2018 with Mash AppList refactoring.
Deprecated 2016/03. The async set-as-default experiments are finished.
Deprecated as of at least 2013. Current autofill experiments rely on Finch
rather than a custom experimentation setup.
Deprecated 11/2017 with removal of Display List Canvas 2D mode.
Replaced with Blink.Canvas.ToBlob.CompleteEncodingDelay in 2017/12.
Removed in Oct 2016
Removed in Oct 2016
Removed in Oct 2016
Removed in Oct 2016
Removed in Oct 2016
Removed January 2018, as the limit is independent of the backend type.
Removed January 2018, as the limit is independent of the backend type.
Removed January 2018, as the limit is independent of the backend type.
Experiments no longer active.
Experiments no longer active.
rsleevi@chromium.org
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 01/2016. CertCacheTrial has been removed.
https://crbug.com/522312
Removed Jan 2018
These were temporary metrics intended to understand whether high/low
resolution clocks adversely impact page load metrics. After collecting a few
months of data it was determined that clock resolution doesn't adversely
impact our metrics, and that these histograms were no longer needed.
These used an old bucketing scheme that that had too many buckets and were
an inefficient usage of UMA bandwidth. They have been replaced by new
metrics of the same name with a "2" appended to them.
Estimates don't need long term monitoring.
Estimates don't need long term monitoring.
Deprecated and removed from code as of 02/2017.
Deprecated and removed from code as of 02/2017.
Deprecated and removed from code as of 07/2018.
Deprecated 9/2016.
Deprecated 04/2018.
Deprecated 09/2016.
Removed in Feb 2016.
Removed 2018/04.
tbansal@chromium.org
Replaced by version without network-type breakdown in June, 2018.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Replaced by KB version in October, 2017.
Deprecated March 2017
Deprecated as of 12/2013. Default pinned apps trial is finished.
Deprecated August 2016
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated April 2015
Deprecated October 2017
Deprecated April 2015
Deprecated October 2017
Deprecated April 2017
Deprecated as of 03/2018. We'd learned enough from this metric and it
made no sense to keep it around.
Deprecated as of 03/2018. We'd learned enough from this metric and it
made no sense to keep it around.
Deprecated as of 03/2018. We'd learned enough from this metric and it
made no sense to keep it around.
Deprecated as of 03/2018. We'd learned enough from this metric and it
made no sense to keep it around.
Deprecated as of 03/2018. We'd learned enough from this metric and it made
no sense to keep it around.
Replaced by GenerateRequest.
calamity@chromium.org
emaxx@chromium.org
igorcov@chromium.org
Deprecated as of 08/2017. Replaced with ExpectedQueueingDurationThreshold.
Deprecated and removed from code as of 05/2015.
Deprecated and removed from code as of 05/2015.
Deprecated and removed from code as of 05/2015.
Deprecated and removed from code as of 04/2018.
Deprecated as of 12/2017.
Deprecated as of 12/2016.
Deprecated as of 12/2016.
Deprecated as of 9/2013.
Deprecated as of 12/2016.
Deprecated as of 12/2016.
Deprecated 2017-9.
kmadhusu@chromium.org
vmiura@chromium.org
Deprecated as of 05/17/2017.
Deprecated as of 11/29/2016.
Deprecated by PageLoad.PaintTiming.NavigationToFirstContentfulPaint.
All relevant histograms have been marked as obsolete as of Sep 2016.
macourteau@chromium.org
Deprecated as of 7/2015.
lizeb@chromium.org
pasko@chromium.org
Removed 10/2016.
Removed 11/2016.
Removed 11/2016.
pauljensen@chromium.org
Unused as of 03/2018
Replaced with IPH_ContextualSearchWebSearch.
Replaced with IPH_ContextualSearchPromotePanelOpen.
Replaced with IPH_ContextualSearchPromoteTap.
Deprecated 2017-10.
Deprecated 2017-10.
cmumford@chromium.org
Deprecated 08/2016.
Deprecated as of September 20, 2017.
Deprecated 2013-04 in favor of LevelDBEnvRetry.
cmumford@chromium.org
Deprecated 12/2017. The low memory margin is a per-platform constant.
Removed from code as of 08/2016.
Removed from code as of 08/2016.
Deprecated and removed from code as of 05/2015.
Removed from code as of 03/2018.
Replaced by the likely named entry. It had a misleading name as it also
has the before-unload time discounted.
Deprecated as of June 2017, in favor of
ServiceWorker.ActivatedWorkerPreparationForMainFrame.Time_WorkerStartOccurred_NavigationPreloadEnabled.
Deprecated as of June 2017.
xunjieli@chromium.org
Deprecated 02/2018.
rch@chromium.org
Deprecated and removed from code as of 10/2015.
rch@chromium.org
rch@chromium.org
rch@chromium.org
rch@chromium.org
csharrison@chromium.org
tbansal@chromium.org
tbansal@chromium.org
rch@chromium.org
Hasn't been used for a while, as of 2016-07.
Hasn't been used for a while, as of 2016-07.
Not used anymore as of 2016-07.
Has never been used.
Has never been used.
Has never been used.
Deprecated October 2017 (feature enabled by default).
Deprecated as of 01/2017.
Deprecated as of 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2017.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 08/2017.
Deprecated 08/2017.
Deprecated 08/2017.
Deprecated 08/2017.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 01/2018.
Deprecated 2018-07 as the non bucketed metrics are enough for future
reference.
Deprecated 2016-05 as the OffDomainInclusionDetector was removed.
Experiments no longer active.
Deprecated in favor of PageLoadBackgrounded2.
Deprecated in favor of PaintTiming equivalent.
deprecated in favor of PageLoad.AbortTiming.Background.*
Deprecated in favor of PageLoad.Clients.AMPCache2.*.
Deprecated in favor of PageLoad.Clients.AMP.*.
Deprecated 05/2018.
Deprecated in favor of Clients.FromGoogleSearch.
Deprecated in favor of Clients.FromGoogleSearch.
Renamed to Clients.Protocol.H11
Deprecated at M53 in favor of LoadType.Reload.
Deprecated at M66. No longer recorded.
Deprecated at M66. No longer recorded.
Deprecated on June 2018 (M69) in favor of Clients.NoServiceWorker2.
Deprecated on June 2018 (M69) in favor of Clients.ServiceWorker2.
Deprecated in favor of PaintTiming equivalent.
Deprecated May 2018 (M68)
Deprecated May 2018 (M68)
Deprecated May 2018 (M68)
Deprecated in favor of
PageLoad.PaintTiming.NavigationToFirstContentfulPaint.LoadType.Reload.
Deprecated in favor of UserGesture/UserInputEvent/BrowserInitiated.
Deprecated in favor of UserGesture/UserInputEvent/BrowserInitiated.
Deprecated in favor of UserGesture/UserInputEvent/BrowserInitiated.
Deprecated as of 03/2016.
Replaced by ProtectedPasswordEntry in M62.
Renamed to PaymentMethod.
Deprecated 2/2017 for Issue 689315 which indicated they weren't being used.
Deprecated 12/2017 in Issue 781644.
Deprecated March 2018
Deprecated March 2018
Deprecated March 2018
Deprecated July 11 2017.
Deprecated August 2016
deprecated May 10 2012
Deprecated August 2016
Deprecated October 2017
Deprecated October 2017
Deprecated April 2017
Deprecated 8/2013. No longer tracked.
Deprecated 04/2018.
rch@chromium.org
Deprecated 10/2015.
Deprecated 04/2016.
rch@chromium.org
Deprecated as of 02/2018. Using suffix Gpu and Software instead.
Deprecated as of 04/2018. No longer recorded.
Deprecated as of 04/2018. No longer recorded.
Deprecated as of 04/2018. No longer recorded.
Deprecated as of June 2018. No longer recorded. This was also being
recorded when the page had a controller with no fetch event, which usually
means the service worker was not running.
Deprecated in 10/2016.
This experiment was turned down, see https://crbug.com/703188.
This experiment was turned down, see https://crbug.com/768325.
This experiment was turned down, see https://crbug.com/768325.
Deprecated September 2016. No longer recorded.
Deprecated September 2016. No longer recorded.
Deprecated September 2016. No longer recorded.
Deprecated September 2016. No longer recorded.
Deprecated September 2016. No longer recorded.
Deprecated September 2016. No longer recorded.
Deprecated 1/2016
Deprecated 4/2015.
Deprecated in 9/2016.
deprecated November 10 2012 crrev.com/167056
cthomp@chromium.org
estark@chromium.org
Deprecated as of 5/2016 because geofencing got removed.
This experiment was turned down, see https://crbug.com/616502.
This experiment was turned down, see https://crbug.com/616502.
This experiment was turned down, see https://crbug.com/616502.
This experiment was turned down, see https://crbug.com/616502.
This experiment was turned down, see https://crbug.com/616502.
Deprecated as of 07/2017. Replaced by ExistingUnreadyProcess and
ExistingReadyProcess.
Deprecated as of 07/2017. Replaced by StartWorkerExistingUnreadyProcess
and StartWorkerExistingReadyProcess.
Removed June 2018 (M69).
Deprecated as of 12/2014.
Deprecated as of 2018-8.
Deprecated as of 03/2015.
Deprecated as of 07/2014.
willchan@chromium.org
shess@chromium.org
Deprecated as of 2016-1 (http://crrev.com/372327).
Deprecated July 11 2017.
Deprecated as of 2013-07.
Removed 2018-02-06.
shess@chromium.org
Removed 2011-06-01.
Deprecated as of 10/2014.
Deprecated as of June 2017.
Deprecated as of June 2017.
Deprecated May 2018
Deprecated 11/17, no longer used.
Deprecated 11/17, no longer used.
Obsolete as of April 2017
No longer logged.
Removed 06/2017, never worked correctly.
Removed 06/2017, never worked correctly.
Deprecated 1/2018. Merged with TaskSchedulerTaskPriority into
TaskSchedulerTaskType to reduce suffixing.
Deprecated 4/2017. Units changed from milliseconds to microseconds.
Deprecated 4/2017. Units changed from milliseconds to microseconds.
Deprecated 4/2017. Units changed from milliseconds to microseconds.
Deprecated 1/2018. Merged with TaskSchedulerMayBlock into
TaskSchedulerTaskType to reduce suffixing.
Deprecated 4/2017. Units changed from milliseconds to microseconds.
Deprecated 12/2016. Pool name removed from task latency histogram name.
Deprecated 12/2016. Pool name removed from task latency histogram name.
Deprecated 12/2016. Pool name removed from task latency histogram name.
Deprecated 12/2016. Pool name removed from task latency histogram name.
Deprecated 02/2017. Pool was renamed to BackgroundBlocking.
Deprecated 02/2017. Pool was renamed to ForegroundBlocking.
Deprecated 01/2018. In favor of TaskSchedulerName suffix.
Deprecated 01/2018. In favor of TaskSchedulerName suffix.
Deprecated 01/2018. In favor of TaskSchedulerName suffix.
Deprecated 01/2018. In favor of TaskSchedulerName suffix.
Deprecated 01/2018. In favor of explicit .Browser suffix.
Deprecated 01/2018. In favor of explicit .Browser suffix.
Deprecated 01/2018. In favor of explicit .Browser suffix.
Deprecated 12/2016. Pool name removed from task latency histogram name.
Deprecated as of 11/2017 in Issue 650338. Using a DCHECK instead.
Deprecated as of 08/2015. Use Net.HttpJob.*Secure.NotQuic instead.
Deprecated as of 08/2015. Use Net.HttpJob.*Secure.Quic instead.
Deprecated 10/2016, no longer used.
Deprecated 2018/07.
Deprecated as of 08/2016.
Deprecated as of July 2017, in favor of
NewTabPage.ContentSuggestions.TimeUntilFirstShownTrigger and
NewTabPage.ContentSuggestions.TimeUntilFirstStartupTrigger.
toyoshim@chromium.org
Deprecated 10/2017. Related field trial has finished rolling out.
toyoshim@chromium.org
ilnik@chromium.org
tmartino@chromium.org
Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenBookmark
instead.
Deprecated as of 04/2017. Replaced by Bookmark Apps (CreateHostedApp).
Deprecated as of 02/2015. Use WrenchMenu.TimeToAction.OpenRecentTab
instead.