corising@chromium.org top-chrome-desktop-ui@google.com Records the number of actions that are currently pinned to the toolbar. This is emitted every time the user pins or unpins an action to the toolbar. ntsirakis@google.com kdgwill@google.com core-devices@google.com Size of enqueued payload. Only recorded on initial enqueue attempt; skipped during retries. ntsirakis@google.com kdgwill@google.com core-devices@google.com Response from CfM logger service after enqueue attempt. ntsirakis@google.com kdgwill@google.com core-devices@google.com Number of retry attempts before we successfully enqueue a record. Should be zero for the majority of cases. ntsirakis@google.com kdgwill@google.com core-devices@google.com The current queue size, recorded after every successful enqueue. ntsirakis@google.com kdgwill@google.com core-devices@google.com Recorded during initial one-time setup steps. Any failures logged will imply that Artemis is effectively disabled. This should skew heavily towards kSetupSucceeded. ntsirakis@google.com kdgwill@google.com core-devices@google.com The time elapsed between successful enqueue attempts. ntsirakis@google.com kdgwill@google.com core-devices@google.com The delay performed before a given enqueue retry after a failure. aalsum@chromium.org chromeos-data-eng@google.com Records the stage up to which the user interacted with the HaTS Chrome OS survey. This is needed in addition to the Hats metrics data since Chrome OS relies on client side logic to roll the dice for device selection. This is recorded when the Hats pipeline ends processing, which is usually when the controller is destroyed. acondor@chromium.org clank-performance-team@google.com Records the latency of CookieAccessObserver's callbacks. Subsampled to 1/100. Not reported for clients with low-resolution clocks. lgrey@chromium.org robliao@chromium.org Whether the user's system is in dark mode, light mode, or if this choice is unavailable due to lack of system support. Updated every UMA upload. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Reflects cached events count: presents number of times a single event is received and placed in cache. Per-event count is incremented every time an event is added/replaced in the cache, and the metrics sample is recorded once the event is confirmed by the server (and thus won't be accepted for upload anymore). Expected to be 1 for the majority of the events, although small number of re-uploads is allowed. Counter for an event that has not been confirmed by the server yet will not be presented in UMA even if received and cached multiple times; since ERP guarantees delivery, this would only be a temporary state. Counter is inexact, since it may be reset in the rare cases that the uploader memory usage reaches its limit. To see how common that is, look at the histogram Browser.ERP.UploadMemoryUsagePercent. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when RecordHandlerImpl catches an error while trying to parse the configuration file that was sent from the reporting server. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when ConfigurationFileController encounters an error while trying to verify the signature and the signed message received from the reporting server. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded once each time reporting::error::DATA_LOSS is returned in the browser. There is a 1:1 relationship between the UMA values and error messages used with reporting::error::DATA_LOSS so that we can understand exactly which parts of the code are failing. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when ReportQueue::Enqueue is called to post an event or metric to ERP. It counts occurences of the reporting destination for the record enqueue that failed. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when ReportQueue::Enqueue is called to post an event or metric to ERP. It counts occurences of the reporting destination for the record enqueue that succeeded. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when ReportQueue::Enqueue is called to post an event to ERP. It counts occurrences of the call returning success or each possible error Status. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when ReportQueue::Enqueue is called to post an event to ERP. It counts occurrences of the call returning success or each possible error status for the {Destination} destination. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Reflects events upload count: presents number of times a single event is sent to the server. Per-event count is incremented every time the event is sent, and the metrics value is recorded in UMA once the event is confirmed by the server (and thus won't be sent anymore). Expected to be 1 for the majority of the events, although minor duplication is allowed. Counter for an event that has not been confirmed by the server yet will not be presented in UMA even if uploaded multiple times; since ERP guarantees delivery, this would only be a temporary state. Counter is inexact, since it may be reset in the rare cases that the uploader memory usage reaches its limit. To see how common that is, look at the histogram Browser.ERP.UploadMemoryUsagePercent. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com {Param} informed by the Missive daemon. Updated every time the Missive daemon requests uploading. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Records whether an event is filtered out by FilteredReportQueue. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when the MetricEventObserverManager enqueues an event metric. It counts occurences of the event type that was extracted from the event payload. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when {MetricCollector}::OnMetricDataCollected is triggered from samplers with no metric data to report. It counts occurences of the reporting destination configured with the collector's report queue. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when the Missive client receives a response from sending a record to the Missive daemon over dBus. There are four types of responses. OK indicates no error. SERVICE_UNAVAILABLE indicates Missive client is not connected to dBus and did not attempt to send the record. NO_RESPONSE indicates Missive client thinks it's connected to dBus and attempted to send the record over dBus but received no response from the Missive daemon. UNKNOWN indicates an unknown error occurred. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Records the result of obtaining PSR info from healthd in the metrics pipeline. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Records whether an event is accepted by ReportQueue rate limiter. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when we send an encrypted record and receive a valid response from the server (i.e. no network errors). True if the server processed the record. False if the server found some error with the record. Note that this may return False even if Browser.ERP.(Un)ManagedUploadEncryptedReport doesn't report a server error, because the server errors it refers to are for DM server requests which are not reporting specific. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when uploading records to the reporting server from a non-ChromeOS device (i.e. using the realtime reporting pipeline). Counts the number of records batched into a single upload request from a {ManagementStatus} device. Uploads containing zero records will not be included as those are just encryption key requests. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded when uploading records to the reporting server. Counts the number of records batched into a single upload request from a {ManagementStatus} device. Uploads containing zero records will not be included as those are just encryption key requests. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com The size of ERP's response payload as a JSON string when upload is successful. Updated every time when an upload succeeds AND at least one hour has passed since the last update AND 9 more uploads have succeeded since the last update. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Success or failure status of enqueuing a record to Missive after failing to enqueue at least once due to Missive unavailablity. Recorded once the enqueue succeeds or times out. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com The size of ERP's request payload as a JSON string when upload is successful. Updated every time when an upload succeeds. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Amount of time spent re-trying to enqueue a record to Missive after failing to enqueue at least once due to Missive unavailablity. Recorded once the enqueue succeeds or times out. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Recorded once each time reporting::error::UNAVAILABLE is returned in the browser. There is a 1:1 relationship between the UMA values and error messages used with reporting::error::UNAVAILABLE so that we can understand exactly which parts of the code are failing. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com The reason that an unuploaded crash is determined that it should or should not be reported in crash reporting. It is recorded every time an unuploaded crash is received from healthd. The primary purpose is to monitor how frequently old unuploaded crashes are not reported because a maximum number of saved local IDs has been reached. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Would only be true. Recorded whenever an unusual timestamp is encountered when enqueuing a record, which will be rejected. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Records memory usage by event uploader as a percent of total memory allocated for the client-side events upload handling. Metric is recorded every time a new upload request is received and stored in memory. nancylanxiao@google.com xanth@google.com domfc@google.com cbe-cep-eng@google.com Status of a completed ERP upload request from a {ManagementStatus} device. Either successful, with a failure or with a server error. Recorded when a response from the server is received. djzhang@google.com jdudder@google.com cros-reporting-team@google.com The accumulated size per hour of ERP's {Param} payload as JSON strings when upload is successful. Updated every hour. kawasin@google.com baseos-perf@google.com This metric is a specialized subset of the `Browser.MainThreadsCongestion` metric, designed to capture the metrics specifically during the first minute after a device resumes from suspend. After the main message loop starts, the calculation for Browser.MainThreadsCongestion is done on a periodic 30 second interval. Any calculations that occur within a minute of resuming will also emit this metric. Each 30 second duration is divided into 100ms intervals. This metric counts the number of these intervals that were "congested". An interval is congested if during it the UI or IO thread executes an "important" task that was queued more than 100 ms ago, or a non-important task or a native event handler that started executing more than 100 ms ago. See https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit for more details. This is supported by ChromeOS only. joenotcharles@google.com catan-team@chromium.org This metric is emitted every 30 seconds after main message loop start, when there is user activity. Each 30 second duration is divided into 100ms intervals. This metric counts the number of these intervals that were "congested". An interval is congested if during it the UI or IO thread executes an "important" task that was queued more than 100 ms ago, or a non-important task or a native event handler that started executing more than 100 ms ago. See https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit for more details. This metric is split by the estimated number of extensions that ran content scripts in the pages that were visible during the interval. It is only recorded if there were visible pages. This version is used for {NumExtensions}. vovoy@chromium.org chromeos-memory@google.com This metric is emitted every 30 seconds after main message loop start, when there is user activity. Each 30 second duration is divided into 100ms intervals. This metric counts the number of these intervals that were "congested". An interval is congested if during it the UI or IO thread executes an "important" task that was queued more than 100 ms ago, or a non-important task or a native event handler that started executing more than 100 ms ago. See https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit for more details. This metric is only recorded if the available physical memory is below a threshold based on Memory.Experimental.AvailableMemoryPercent 10 percentile. pmonette@chromium.org catan-team@chromium.org This metric is emitted every 30 seconds after main message loop start, when there is user activity. Each 30 second duration is divided into 100ms intervals. This metric counts the number of these intervals that were "congested". An interval is congested if during it the UI or IO thread executes an "important" task that was queued more than 100 ms ago, or a non-important task or a native event handler that started executing more than 100 ms ago. See https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit for more details. This metric is only recorded if Chrome is either visible, playing audio, or capturing video. etienneb@chromium.org gab@chromium.org chrome-analysis-team@google.com This metric is emitted every 30 seconds after main message loop start, when there is user activity. Each 30 second duration is divided into 100ms intervals. This metric counts the number of these intervals that were "congested". An interval is congested if during it the UI or IO thread executes an "important" task that was queued more than 100 ms ago, or a non-important task or a native event handler that started executing more than 100 ms ago. See https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit for more details. This metrics graduated from Browser.Responsiveness.JankyIntervalsPerThirtySeconds(1,2,3) and their history might be useful to understand how we got here. Suffixed phases can be useful as diagnosis metrics. This phase represents: {Phase} This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. pmonette@chromium.org catan-team@chromium.org This metric is emitted every 30 seconds after main message loop start, when there is user activity. Each 30 second duration is divided into 100ms intervals. This metric counts the number of these intervals that were "congested". An interval is congested if during it the UI or IO thread executes an "important" task that was queued more than 100 ms ago, or a non-important task or a native event handler that started executing more than 100 ms ago. See https://docs.google.com/document/d/1vDSGFvJblh7yJ3U3RVB_7qZLubyfTbQdQjuN1GoUNkc/edit for more details. This metric is split by usage scenarios (go/chrome_power_use_per_scenario). This version is recorded for {UsageScenario}. gjc@google.com chrome-loading@google.com Records memory pressure metrics when a process is killed. The UMA is recorded only on the Android platform when a process kill matching the type happens. The metric is only available on Android experiment groups under the feature kUserLevelMemoryPressureSignalMetricsOnly. Details: {ProcessType} - {MetricName} flackr@chromium.org chrome-a11y-core@google.com Whether overlay scrollbars are enabled by the operating system settings on desktop platforms (Mac, Linux, Windows, ChromeOS). Updated every UMA upload. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the size of a compressed on-disk capture for the paint preview after a proto is written to disk if compressed. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the number of frames captured by a paint preview if it succeeded. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records a boolean indicating whether a capture attempt was successful. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the total time spent capturing a paint preview of a page. This includes capture and serialization of all frames and IPC time. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records if the paint preview compositor process started correctly. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the time it took to start the paint preview compositor process. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records when a link is clicked in the paint preview player. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the time taken to from the request to start the compositor process to the first bitmap being loaded. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the the reason for exiting the compositor process for the TabbedPaintPreviewPlayer. Recorded when the compositor returns an error or disconnects. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the the reason for exiting TabbedPaintPreviewPlayer. Recorded when paint preview is removed. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records whether paint preview was drawn before the tab finished loading. Recorded when tab has finished loading. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records whether a paint preview exists. Recorded when attempting to show a preview on startup. This in conjuction with CompositorFailureReason gives the total number of failures to show a paint preview. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the number of times that the upgrade snackbar was shown in a session of TabbedPaintPreviewPlayer. Recorded when paint preview is removed. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the time taken to from actvity creation to the first bitmap being shown. Recorded on first paint preview paint event. ckitagawa@chromium.org fredmello@chromium.org chrome-fdt@google.com Records the length of the time that a session of TabbedPaintPreviewPlayer lasts. Recorded when paint preview is removed. {TabbedPaintPreviewPlayerUptime} ckitagawa@chromium.org fredmello@chromium.org Records the total disk usage by the Paint Preview Tab Service at startup of the profile keyed service. gab@chromium.org olivierli@chromium.org Similar to Browser.Responsiveness.IOJankyIntervalsPerMinute but sums janky events across all foreground threads over the monitored minute rather than considering each interval a boolean. This aims to cover a blind spot of IOJankyIntervalsPerMinute as it cannot see an improvement where we unblock 19/20 threads performing I/O. Not reported across system sleep. More details @ https://bit.ly/chrome-io-jank-metric gab@chromium.org olivierli@chromium.org This metric is emitted every minute. It reports a number between 0 and 60 which corresponds to the number of 1 second intervals during the monitored minute to which a stalled foreground thread ScopedBlockingCall(BlockingType::MAY_BLOCK) was attributed. A stalled call is first attributed to the interval in which it began, and is attributed to a number of intervals equal to the length of the call, rounded to the nearest second. (Before http://crrev.com/c/2314873, the length was truncated rather than rounded.) This aims to capture moments where the main thread is responsive but the application is not (because things aren't loading). Not reported across system sleep. More details @ https://bit.ly/chrome-io-jank-metric dljames@chromium.org top-chrome-desktop-ui@google.com Records the browser command ID (from chrome_command_ids.h) whenever a registered keyboard shortcut is pressed (excluding auto-repeat events). Note: Command IDs in chrome_command_ids.h are not strictly guaranteed to be stable version-to-version. When analyzing historical trends across multiple milestones, filter by specific Chrome milestone versions. iremuguz@google.com chromeos-commercial-supportability@google.com Reports the actions that the user takes when they use chrome://support-tool WebUI. These actions include the page navigation and data collection details. This metric is used to measure the usage rate of Support Tool features. robliao@chromium.org yuhengh@chromium.org Compositor presentation time when dragging tabs left or right to a different index. This metric is used to measure tab dragging performance. Record on the next compositor frame when the data is collected. robliao@chromium.org yuhengh@chromium.org Compositor presentation time when dragging tabs out to a new browser. This metric is used to measure tab dragging performance. Record on the next compositor frame when the data is collected. robliao@chromium.org yuhengh@chromium.org Compositor presentation time when dragging tabs. This metric is used to measure tab dragging performance. Record on the next compositor frame when the data is collected. robliao@chromium.org yuhengh@chromium.org Maxinum compositor presentation time when dragging tabs. This metric is used to measure tab dragging performance. Record after a drag and drop session is ended. joenotcharles@google.com catan-team@chromium.org Recorded when a tab is shown. Records whether both the tab switching and bfcache restore show reasons are set. This is used to understand if there is any overlap between these two events. fdoray@chromium.org joenotcharles@google.com catan-team@chromium.org Whether a frame was presented after a tab switch event. Recorded based on the destination tab state when the tab switch starts: {TabSwitchingType} fdoray@chromium.org jonross@chromium.org joenotcharles@google.com catan-team@chromium.org The time between a tab switch input event timestamp and when the tab is hidden, if no frame is presented in the meantime. Recorded based on the destination tab state when the tab switch starts: {TabSwitchingType} jonross@chromium.org joenotcharles@google.com catan-team@chromium.org chrome-ds@google.com The time between the input event timestamp and the frame presentation time on a tab switch. Recorded based on the destination tab state when the tab switch starts: {TabSwitchingType} This histogram is of special interest to the chrome-ds@. Do not change its semantics or retire it without talking to them first. noahrose@google.com src/chrome/updater/OWNERS Recorded when the user changes any of the filters on the chrome://updater history page. noahrose@google.com src/chrome/updater/OWNERS Recorded when the user clicks an install path link on the chrome://updater page. Sliced by the type of path being followed (per-system updater, per-user updater, or Chrome Enterprise Companion App). rhalavati@chromium.org chrome-privacy-core@google.com Number of open guest windows at the same time. Recorded when a new guest window is created. Please note that this metric double counts the lower numbers, meaning that if user opens three windows (without closing any in between), then buckets 1, 2, and 3 will all be incremented in turn. rhalavati@chromium.org chrome-privacy-core@google.com Number of open incognito windows at the same time. Recorded when a new incognito window is created. Please note that this metric double counts the lower numbers, meaning that if user opens three windows (without closing any in between), then buckets 1, 2, and 3 will all be incremented in turn. gjc@google.com chrome-loading@google.com Records the size of the available memory before the spare renderer creation, if a process kill happens shortly afterwards. The UMA is recorded only on the Android platform when a process kill matching the type happens within {Time} after a spare renderer creation. Details: {ProcessType} gjc@google.com chrome-loading@google.com Recorded the size of the available memory when before creating the spare renderer. The UMA is recorded only on the Android platform before the creation of a spare renderer. creis@chromium.org site-isolation-dev@chromium.org Recorded when RenderProcessHostImpl::FilterURL detects a disallowed URL sent by the renderer process and rewrites it to about:blank#blocked. See also Navigation.Renderer.BlockedForFilterURL for cases caught earlier in the renderer process, and https://crbug.com/40066983. wfh@chromium.org chrome-stability-core@google.com Count of renderer process terminations due to a code integrity failure, grouped by type. This is only reported on Windows. wfh@chromium.org chrome-stability-core@google.com Count of renderer process crashes grouped by type. wfh@chromium.org chrome-stability-core@google.com Count of renderer process kills grouped by type. oshima@chromium.org chrome-stability-core@google.com 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 chrome-stability-core@google.com The launch error codes for failed renderer process launches. In M129 we are more accurately tracking renderer process launch failures, and expect to find a significant spike in volume. wfh@chromium.org chrome-stability-core@google.com Count of renderer process launch failures grouped by type. In M129 we are more accurately tracking renderer process launch failures, and expect to find a significant spike in volume. mych@chromium.org bfcache-dev@chromium.org Recorded whenever a RenderProcessHost is cleaned up, with the reason the cleanup fails or is delayed, or kNoDelay if it succeeded quickly. The total count of this histogram should be equal to BrowserRenderProcessHost.Cleanup.Total. mych@chromium.org bfcache-dev@chromium.org Records true when an attempt is made to clean up a RenderProcessHost. wfh@chromium.org chrome-stability-core@google.com Count of renderer process crashes that we miscounted because we took the exit code too early. Grouped by type. cduvall@chromium.org swarm-team@google.com Whether the existing renderer used is alive. Recorded when RenderProcessHostImpl::GetProcessHostForSiteInstance uses an existing renderer. mych@chromium.org bfcache-dev@chromium.org Recorded on every attempt to fast-shutdown a RenderProcessHost. The value is kNoDelay on success, or the reason it couldn't take place otherwise. Warning: this histogram was expired from 2024-04-29 to 2024-12-09; data may be missing. mych@chromium.org bfcache-dev@chromium.org Records true when an attempt is made to fast shutdown a RenderProcessHost. Warning: this histogram was expired from 2024-04-29 to 2024-12-09; data may be missing. creis@chromium.org avi@chromium.org Reports false each time the Task Manager displays an unlabeled renderer process using the fallback task provider, indicating that a type of renderer process is missing a task provider, which is a bug. For comparison, this reports true when renderer processes are properly labeled by a primary task provider. These values are only reported when the Task Manager is open. This can be removed when no unlabeled cases remain, per https://crbug.com/739782. dtapuska@chromium.org chrome-loading@google.com Records the maximum number of outermost main frames that were hosted in the process. This is logged when the RenderProcessHost is destroyed. gjc@google.com chrome-loading@google.com Records the reason for there being no spare renderer present when calling SpareRenderProcessHostManagerImpl::MaybeTakeSpare. The UMA is recorded when kNoSparePresent is recorded in the UMA BrowserRenderProcessHost.SpareProcessMaybeTakeAction. gjc@google.com chrome-loading@google.com Records the detailed allocation source of the process when calling SpareRenderProcessHostManagerImpl::MaybeTakeSpare if there is no spare renderer. The UMA is recorded when the corresponding NoSpareRendererReason is recorded in the UMA BrowserRenderProcessHost.NoSparePresentReason2. gjc@google.com chrome-loading@google.com Records whether the process creation is caused by a COOP header when calling SpareRenderProcessHostManagerImpl::MaybeTakeSpare if there is no spare renderer. The UMA is recorded when NavigationRequest is recorded in the UMA BrowserRenderProcessHost.NoSpareRenderer.AllocationSource.{NoSpareRendererReason}. gjc@google.com chrome-loading@google.com Records the detailed navigation stage of the process when calling SpareRenderProcessHostManagerImpl::MaybeTakeSpare if there is no spare renderer. The UMA is recorded when NavigationRequest is recorded in the UMA BrowserRenderProcessHost.NoSpareRenderer.AllocationSource.{NoSpareRendererReason}. dtapuska@chromium.org chrome-loading@google.com Records the number of outermost main frames that were hosted in the process when it was determined no more should be placed in the process for the ProcessPerSite algorithm. This is recorded only when this limit is first crossed for each RenderProcessHost. gjc@google.com chrome-loading@google.com Records the process reuse policy when a SiteInstance reuses an existing process. Recorded when RenderProcessHostImpl::GetProcessHostForSiteInstance is called and the site instance is assigned a process by reusing an existing process. ziadyoussef@chromium.org chrome-loading@google.com Records how the main frame's SiteInstance was assigned a renderer process. Recorded when RenderProcessHostImpl::GetProcessHostForSiteInstance is called. pmonette@chromium.org catan-team@chromium.org Count of spare renderers. Recorded every 2 minutes. kerenzhu@chromium.org dayeung@chromium.org robliao@chromium.org tluk@chromium.org Records the time elapsed from the initiation of the spare process warm-up to the actual creation of the process. jam@chromium.org cduvall@chromium.org Records true if SpareRenderProcessHostManager::WarmupSpare evicted an existing spare process that had a different BrowserContext, or false if there wasn't an existing spare process. 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. gjc@google.com chrome-loading@google.com Records what happens when an attempt is made to use a spare RenderProcessHost during a navigation request. The UMA logs that either the attempt succeeded or why it failed. gjc@google.com chrome-loading@google.com Records the time elapsed from the creation of a spare renderer to the point when the browser tries to take a spare renderer. The UMA is recorded each time when the browser tries to take a spare renderer. The timer will not be reset if the spare renderer timeouts and will be recorded even if the spare renderer is no longer present. The behavior is designed to collect data about the appropriate value of the spare renderer timeout. gjc@google.com chrome-loading@google.com Categorize the BrowserRenderProcessHost.SpareProcessMaybeTakeTime by the SpareProcessMaybeTakeAction. The UMA is recorded each time when the browser try to take a spare renderer. gjc@google.com chrome-loading@google.com Records the detailed reason if the spare process cannot be taken because of RefusedByEmbedder. kerenzhu@chromium.org dayeung@chromium.org robliao@chromium.org tluk@chromium.org Records the time elapsed from the creation of the spare process to the point when the process becomes ready. This does not include the scheduled delay time (see SpareProcessDelayTime). gjc@google.com chrome-loading@google.com Records how a spare renderer process is used or destroyed. The UMA is recorded when the spare renderer is used by navigation or destroyed because of timeout or resource limit. gjc@google.com chrome-loading@google.com Records whether the process creation is caused by a COOP header in the previous successful call to SpareRenderProcessHostManagerImpl::MaybeTakeSpare when the same function is called and there is no spare renderer. The UMA is recorded when TakenByPreviousNavigation is recorded in the UMA BrowserRenderProcessHost.NoSparePresentReason2 and NavigationRequest is recorded in the UMA BrowserRenderProcessHost.SpareRendererPreviouslyTaken.Source. gjc@google.com chrome-loading@google.com Records the allocation source of the previous successful call to SpareRenderProcessHostManagerImpl::MaybeTakeSpare when the same function is called and there is no spare renderer. The UMA is recorded when TakenByPreviousNavigation is recorded in the UMA BrowserRenderProcessHost.NoSparePresentReason2. gjc@google.com chrome-loading@google.com Records the navigation stage of the previous successful call to SpareRenderProcessHostManagerImpl::MaybeTakeSpare when the same function is called and there is no spare renderer. The UMA is recorded when TakenByPreviousNavigation is recorded in the UMA BrowserRenderProcessHost.NoSparePresentReason2 and NavigationRequest is recorded in the UMA BrowserRenderProcessHost.SpareRendererPreviouslyTaken.Source. pmonette@chromium.org catan-team@chromium.org Records whether or not the spare was ready at the time it was taken. pmonette@chromium.org catan-team@chromium.org Records the time delta since the spare RenderProcessHost was created at the time it is taken. gjc@google.com chrome-loading@google.com Records whether the current process allocation is caused by a COOP header if the current allocation fails and the previous allocation takes the spare renderer in the same navigation. The UMA is recorded if both BrowserRenderProcessHost.SpareRendererPreviouslyTaken.Stage and BrowserRenderProcessHost.NoSpareRenderer.NavigationStage.{NoSpareRendererReason} are recorded and the render process allocation happens in the same navigation. gjc@google.com chrome-loading@google.com Records whether a combination of the previous and the current navigation stage if the allocation of the spare renderer fails and the previous allocation takes the spare renderer in the same navigation. The value is calculated by { 100 * PREVIOUS_STAGE + CURRENT_STAGE }. The UMA is recorded if both BrowserRenderProcessHost.SpareRendererPreviouslyTaken.Stage and BrowserRenderProcessHost.NoSpareRenderer.NavigationStage.{NoSpareRendererReason} are recorded and the render process allocation happens in the same navigation. alexmos@chromium.org creis@chromium.org wjmaclean@chromium.org Records the total number of frames at the time the subframe memory threshold is exceeded and the process is not reused. Only recorded the first time that the threshold is exceeded in code that picks a process for a particular SiteInstance. wfh@chromium.org chrome-stability-core@google.com Whether or not kernel-mode execution was recorded for a suspended renderer process. This is recorded after process creation but before process resumption. This is recorded for every sandboxed Renderer process launched on Windows only. wfh@chromium.org chrome-stability-core@google.com Whether or not user-mode execution was recorded for a suspended renderer process. This is recorded after process creation but before process resumption. This is recorded for every sandboxed Renderer process launched on Windows only. anandrv@google.com clank-performance-team@google.com Records the duration spent off-CPU by tasks running on the browser UI thread. Recorded with 0.001 probability when a task scheduled on the main thread finishes running. anandrv@google.com clank-performance-team@google.com Records the duration spent on-CPU by tasks running on the browser UI thread. Recorded with 0.001 probability when a task scheduled on the main thread finishes running. anandrv@google.com clank-performance-team@google.com Records the percentage of wall time spent on-CPU by tasks running on the browser UI thread. Recorded with 0.001 probability when a task scheduled on the main thread finishes running. peconn@chromium.org peter@chromium.org Triggered when a TrustedWebActivity is paused, recording the time since it had been resumed. peconn@chromium.org peter@chromium.org The result of Digital Asset Link verification performed when starting a Trusted Web Activity. Warning: this histogram was expired from M114 to 2024-10-10; data may be missing. peconn@chromium.org peter@chromium.org Triggered when Trusted Web Activity verification completes. Records how long it takes the device to realise it is offline and fall back to the cached result. Warning: this histogram was expired from 2024-09-15 to 2024-10-10; data may be missing. peconn@chromium.org peter@chromium.org Triggered when Trusted Web Activity verification completes. Records how long verification took when online. nicolaso@chromium.org pastarmovj@chromium.org Records which browser the Legacy Browser Support feature is configured to open (which defaults to IE). Recorded on browser startup, and when the value changes. Only measured when Legacy Browser Support is enabled via the BrowserSwitcher* policies. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Records whether the "AppData/Local/Google/BrowserSwitcher" directory was successfully created. Windows only. nicolaso@chromium.org pastarmovj@chromium.org Records whether a temp file in "AppData/Local/Google/BrowserSwitcher" the directory was successfully created. Windows only. nicolaso@chromium.org pastarmovj@chromium.org Records whether the temp file in "AppData/Local/Google/BrowserSwitcher" directory was successfully moved to its final destination ("cache.dat") after writing its contents. Windows only. nicolaso@chromium.org pastarmovj@chromium.org Whether or not Chrome was launched by the Legacy Browser Support for Edge extension's native host. This indicates an automatic Edge=>Chrome or IE=>Chrome transition. Recorded whenever Chrome is launched by any means. Only recorded on Windows. nicolaso@chromium.org pastarmovj@chromium.org On navigation and redirect, whether to switch browsers or not. Only measured when Legacy Browser Support is enabled via the BrowserSwitcher* policies. When this is true, Chrome attempts to launch an alternative browser (typically IE) with the navigation URL. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org On navigation and redirect, records how long it took to compute a decision (stay in Chrome/open in IE). Only measured when Legacy Browser Support is enabled via the BrowserSwitcher* policies. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Number of rules that come from an external greylist XML file. Measured when the sitelist is loaded during browser startup. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Number of rules that come from an external sitelist XML file. Measured when the sitelist is loaded during browser startup. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Number of rules in the BrowserSwitcherUrlGreylist policy. Measured when the policy is loaded. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Whether there is a wildcard ("*") rule in the BrowserSwitcherUrlGreylist policy. Measured when the BrowserSwitcherUrlGreylist policy gets updated. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Number of rules that come from Internet Explorer Enterprise Mode's sitelist. Measured when the sitelist is loaded during browser startup. Windows only. nicolaso@chromium.org pastarmovj@chromium.org Records whether an attempt to launch an alternate browser failed or succeeded. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Records how long it took to launch an alternate browser (regardless of whether it failed or succeeded). Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Number of rules in the BrowserSwitcherUrlList policy. Measured when the policy gets updated. Desktop Chrome only. nicolaso@chromium.org pastarmovj@chromium.org Whether there is a wildcard ("*") rule in the BrowserSwitcherUrlList policy. Measured when the BrowserSwitcherUrlList policy gets updated. Desktop Chrome only. swestphal@chromium.org rayankans@chromium.org Records the number of fingerprints in assetlinks.json for every performed Digital Asset Link validation with a valid `sha256_cert_fingerprints`-entry. musalmaan@chromium.org top-chrome-desktop-ui@google.com Records when a desktop infobar centralized under the new centralization framework triggers a specific {Action}. Each bucket in this sparse histogram corresponds to a unique InfoBarIdentifier, and the count reflects the number of times that specific infobar triggered the {Action}. Recorded once per event to track user engagement and health of migrated infobars under the centralization framework. koretadaniel@chromium.org top-chrome-desktop-ui@google.com Records how many infobars were visible at the moment a new infobar was shown. This is recorded any time a new infobar is shown. The maximum bucket for this metric is set to 10. It is less plausible to have 10 infobars at the same time, so this maximum value will help to capture all the lower buckets distinctly. koretadaniel@chromium.org top-chrome-desktop-ui@google.com Records the infobars pending queue size at a time of showing a new infobar. The maximum bucket for this metric is set to 50. koretadaniel@chromium.org top-chrome-desktop-ui@google.com Records the identifier of pending infobars that were discarded (starved) when the InfobarManager was reset or the tab was closed. koretadaniel@chromium.org top-chrome-desktop-ui@google.com Records the number of pending infobars that were discarded (starved) when the InfobarManager was reset or the tab was closed. koretadaniel@chromium.org top-chrome-desktop-ui@google.com The time elapsed between an infobar being added to the prioritization queue and it being promoted to visible status. 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. mdjones@chromium.org Records how many times a particular infobar was displayed in a hidden state due to at least one other infobar existing. If there are no existing infobars, but the user scrolls at the exact moment a new infobar is added, the infobar may be hidden, but not recorded in this metric. Reliably triggering and detecting this combination is tricky so it isn't done. Only recorded on Android. mdjones@chromium.org Records how many times a particular infobar was visible and hiding a new infobar behind it. Only recorded on Android. mdjones@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. mschillaci@google.com linyuh@google.com clank-app-team@google.com Records when the side panel has been automatically closed because the window was resized to be too small. Recorded when the user resizes the window. mschillaci@google.com linyuh@google.com clank-app-team@google.com Records when the side panel has been automatically restored because the window was resized to be big enough again. Recorded when the user resizes the window. alfredohiguera@google.com top-chrome-desktop-ui@google.com Records how long the ReadAnything side panel entry was open for (capped at 24 hours). It is recorded in SidePanelEntry::OnEntryHidden when the entry is hidden (ie. switching entries or the side panel closing). This is similar to SidePanel.ReadAnything.ShownDuration but with a longer duration cap. corising@chromium.org top-chrome-desktop-ui@google.com Records how long the {SidePanelType} was open for (capped at 1 hour) starting when the {SidePanelType} is triggered to be opened. Note this might be different than when the {SidePanelType} becomes visible due to delays for loading content. Recorded when the {SidePanelType} is closed. corising@chromium.org top-chrome-desktop-ui@google.com Logs the UI location from which the {SidePanelType} is triggered to be opened or to change the entry shown. Recorded when the {SidePanelType} is shown or the entry changed and a trigger is provided. corising@chromium.org top-chrome-desktop-ui@google.com Logs the UI location from which the {SidePanelType} is triggered to be opened. Recorded when the {SidePanelType} is shown and a trigger is provided. emshack@chromium.org top-chrome-desktop-ui@google.com Records the width of the side panel contents after the side panel was resized. emshack@chromium.org top-chrome-desktop-ui@google.com Records the width of the side panel contents as a percentage of the browser window width after the side panel was resized. corising@chromium.org top-chrome-desktop-ui@google.com Records elapsed time between animation steps for the longest step in a side panel open or close animation. OBSOLETE. See: SidePanelType.SidePanelAnimationType.TimeOfLongestAnimationStep below. corising@chromium.org top-chrome-desktop-ui@google.com Records the frames per second for the side panel animation. This is recorded after each side panel animation is completed when the side panel opens or closes. corising@chromium.org top-chrome-desktop-ui@google.com Records elapsed time between animation steps for the longest step in a side panel open or close animation. emshack@chromium.org top-chrome-desktop-ui@google.com Records the width of the side panel contents after the side panel was resized, while the {SidePanelEntry} side panel entry was displayed. emshack@chromium.org top-chrome-desktop-ui@google.com Records the width of the side panel contents as a percentage of the browser window width after the side panel was resized, while the {SidePanelEntry} side panel entry was displayed. corising@chromium.org top-chrome-desktop-ui@google.com Records how long the {SidePanelEntry} side panel entry was open for (capped at 1 hour). This is recorded in SidePanelEntry::OnEntryHidden when the entry is hidden (ie. switching entries or the side panel closing). corising@chromium.org top-chrome-desktop-ui@google.com Records how a {SidePanelType} entry is triggered to be shown. (i.e. by toolbar button, by commbobox selection). This is recorded when a new {SidePanelType} entry is triggered to be shown regardless any {SidePanelType} entry is currently open. corising@chromium.org top-chrome-desktop-ui@google.com Records elapsed time between when the {SidePanelEntry} side panel entry triggered to be shown and when it was shown.