Removed in M98. Removed in M98. Removed in M98. Removed in M98. Removed in M84. Removed in M84. bzielinski@google.com cros-edu-eng@google.com The result of adding a cast sink to the media router sink list via the AccessCodeCastSinkService when discovering it using an access code. Recorded after the cast sink is added. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The result of adding a cast sink to the media router sink list via the AccessCodeCastSinkService when the device was remembered due to device policy. Recorded after the cast sink is added. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The selected cast mode when a cast session is successfully started (ResultCode::OK) after a user enters an access code. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The duration in seconds an access code device will stay in the list of cast devices. Recorded on successful creation of a cast session to an access code device. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The count of cast devices which have been successfully remembered via the access code cast sink service. Recorded when the browser starts, and any time the network changes. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The count of times that a local cast mirroring session is frozen, or paused, during its duration. Recorded at the end of a cast mirroring session. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The amount of time in milliseconds that a local cast mirroring session is frozen, or paused, until it is resumed or ended. Recorded when the session is resumed, or when the session ends. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The amount of time in milliseconds that it takes to connect to a new device. It is the combination of connecting to our server, validating the access code, constructing a cast device, opening a channel to that device, and then waiting for success. It is only recorded if the request was successful; not recorded for non-local routes. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The discovery type of the associated sink and the cast media source for an access code route. Recorded when at the start of a local access code route. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The amount of time in milliseconds that a route to an access code device lasts. Recorded at the end of a local access code route; not recorded for non-local routes. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The amount of time in milliseconds that it takes to connect to a saved device. It is a combination of the time to request a mirroring route + waiting for a success. It is only recorded if the request was successful; not recorded for non-local routes. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The amount of time in milliseconds for the user to input an access code after the UI is enabled for a cast attempt. Recorded when the user presses enter or the submit button after typing an access code. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The count of ACCESS_CODE_NOT_FOUND errors received while the AccessCodeCastDialog is open, correlating to the number of times a user typed an incorrect access code. Recorded after the dialog is closed. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The amount of time in milliseconds that the dialog is loading while attempting to cast to a new device via access code. Recorded after a cast attempt completes, and does not depend on whether the attempt was successful or ended in error. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The reason why the Access Code Cast dialog closed. Recorded when the Access Code Cast dialog closes. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The length of time for the AccessCodeCast dialog to finish loading after instantiation. Recorded after the UI creates a page handler object. Logged only on desktop platforms. bzielinski@google.com cros-edu-eng@google.com The location from which the AccessCodeCast dialog is opened. Recorded after the dialog opens. Only logged on desktop platforms. ahmedmoussa@google.com takumif@chromium.org openscreen-eng@google.com This metric is recorded once per AccessCodeCast tab mirroring session. It records the number of times the tab switcher UI was shown and not used, compared to the number of times it was shown and actually used to switch tabs. This would make it possible to compute the % of users who cast a tab who then switch which tab is being cast. Recorded once at the end of a tab mirroring casting session. ahmedmoussa@google.com takumif@chromium.org openscreen-eng@google.com This metric is recorded once per AccessCodeCast tab mirroring session. It records the number of times the tab switcher UI was used to switch the source tab. siggi@chromium.org Status of the initialization to collect stability debug files. Logged once, during the initialization of the stability debug file collection. siggi@chromium.org Number of files found during stability file collection. Logged each time the stability file collection proceeds (at most once per launch). siggi@chromium.org Status for the collection of a stability debug file. Logged each time a debug file collection attempt is made. siggi@chromium.org Status for the analysis of the system session state. Logged each time a debug file is collected. siggi@chromium.org Time spent collecting stability debug information. Logged each time a collection is performed. siggi@chromium.org Status of the minidump writing. Logged each time a writing a minidump is attempted. pauljensen@chromium.org privacy-sandbox-dev@chromium.org True if the trusted bidding signals specified a per-interest-group priorityVector whose sparse dot product with the browser generated prioritySignals was negative, indicating the generateBid() should not be invoked. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org True if the browser can reuse an existing context when calling generateBid() whose corresponding interest group has the executionMode set to group-by-origin. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org For each request made for a DirectFromSellerSignals bundle subresource, records whether the request was made to the network service, or whether the request was elided due to either loading from the DirectFromSellerSignalsRequester cache, or coalescing with an exiting request for the same subresource URL. Reported at each DirectFromSellerSignalsRequester request. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. mmenke@chromium.org morlovich@chromium.org The final state of the InterestGroupAuctionReporter when it's destroyed. Currently the lifetime of an InterestGroupAuctionReporter is scoped to the frame that runs an auction, so when that frame is destroyed, any work the Reporter has yet to do is aborted. This histogram serves to indicate how far along a destroyed Reporter is, to help understand the priority of extending an InterestGroupAuctionReporter's lifetime beyond that of the source frame. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The outcome of the first 6 auctions reported as bits, tracked per-page, reported at page unload (if at least 1 auction completed). A 1 indicates auction success, 0 indicates auction failure. The most significant bit corresponds to the least recent auction. An extra leading 1 is prepended -- this allows reporting metrics when fewer than 6 auctions occurred during the page's lifetime. Therefore, the max value is 0b1111111 (7 bits, represents 6 successful auctions), and the min value is 0b10 (represents a page that had 1 failed auction), and every value in between is valid. Not updated for auctions skipped due to enforcing the auction limit, see NumAuctionsSkippedDueToAuctionLimit. Also, not updated if runAdAuction() fails before the auction worklets run. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to initialize the context and arguments, and evaluate generateBid() once. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org For every interest group that participates in an auction, the time duration since the last join or update of that interest group. This metric only measures {Type}. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to start a FLEDGE auction and complete loading the interest groups that should participate in the auction; only recorded when at least one interest group was loaded. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to start a FLEDGE auction and complete loading the interest groups that should participate in the auction; only recorded when no interest groups were loaded. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The number of auctions (runAdAuction() calls) per-page, from page load to unload, reported at unload (if at least 1 auction completed). Not updated for auctions skipped due to enforcing the auction limit, see NumAuctionsSkippedDueToAuctionLimit. Also, not updated if runAdAuction() fails before the auction worklets run. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The number of auctions (runAdAuction() calls) per-page, from page load to unload, reported at unload (if at least 1 auction completed) that were skipped due to hitting the auction limit. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. mmenke@chromium.org morlovich@chromium.org The number of a user's interest groups taking part in a FLEDGE auction. This is the number of interest groups matching the auction configuration, not the number whose scripts are successfully loaded or that make bids. Recorded after all matching interest groups have been retrieved from storage at the start of an auction. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. mmenke@chromium.org morlovich@chromium.org The number of owner origins with interest groups taking part in a FLEDGE auction. This is not the number of owners listed by the auction's configuration, but rather only the subset of them that have interest groups the user currently belongs to. Recorded after all interest groups participating in an auction have been retrieved from storage at the start of an auction. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. mmenke@chromium.org morlovich@chromium.org The number of sellers participating in a FLEDGE auction with a non-zero number of bidders, including both the top-level seller and sellers in component auctions. A bidder is defined as an interest group owned by one of the owners participating in an auction, or, for the top-level auction, a component auction with such interest groups. Double-counts sellers that participate in multiple component auctions. Only recorded if an auction has at least one interest group participating (could be in the top-level auction, or in any component auction). See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to decrypt, decompress, and parse a the Response from a FLEDGE server-based auction (using the Bidding and Auction API). Only the times for responses that are successful decoded are recorded. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The percentage of auctions (runAdAuction() calls) per-page that succeed, from page load to unload, reported at unload (if at least 1 auction completed), rounded down to the nearest percent. Not updated for auctions skipped due to enforcing the auction limit, see NumAuctionsSkippedDueToAuctionLimit. Also, not updated if runAdAuction() fails before the auction worklets run. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to launch a process to execute FLEDGE worklets. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to initialize the context and arguments, and evaluate scoreAd() once. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The duration between runAdAuction() calls, collected on a per-page basis, reported on each auction. Not updated for auctions skipped due to enforcing the auction limit, see NumAuctionsSkippedDueToAuctionLimit. Also, not updated if runAdAuction() fails before the auction worklets run. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org The amount of time spent constructing the Bidding and Auction data blob produced in response to the getInterestGroupAdAuctionData() call to the Bidding and Auction API. This time includes loading interest groups from the database, fetching the Bidding and Auction server key (if not cached), serializing and compressing the interest group data and encryting the message. Only the times for blobs that are constructed successfully are recorded. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org The unencrypted size of Bidding and Auction data blob produced in response to the getInterestGroupAdAuctionData() call to the Bidding and Auction API. Only the sizes of blobs that are constructed successfully are recorded. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org For each time a JavaScript enum of {Type} is provided during {When}, records whether or not the enum was in the deprecated "camelCase" form. (The correct form is the "words-separated-by-dashes" form). Unknown enum values are ignored and not reported. Reported at each enum usage during {When}. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. pauljensen@chromium.org privacy-sandbox-dev@chromium.org Time required to download {Type} requests, reported upon receving a response. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The number of bytes sent for {Type} requests, reported upon each request. This is just the size of the request URL; it doesn't include the size of the HTTP headers or the word "GET". See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org The number of bytes received for {Type} requests, reported upon receving a response. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. caraitto@chromium.org pauljensen@chromium.org privacy-sandbox-dev@chromium.org Time required to find a matching directFromSignalsSignalsHeaderAdSlot, reported upon completion of the search. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. mmenke@chromium.org morlovich@chromium.org privacy-sandbox-dev@chromium.org True if the trustedBiddingSignals fetched for use in a FLEDGE auction was received in the deprecated format. Recorded whenever there's a network fetch for trustedBiddingSignals, and they're successfully decoded. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to run a Bidding and Auction Services auction. This includes all of the time from the call to `navigator.getInterestGroupAdAuctionData()` to the completion of the `navigator.runAdAuction()` call. This metric is only recorded if there was a winning bid. See https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md for the latest version of the Protected Audience Bidding & Auction Services explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org The length of time it took to run a Bidding and Auction Services auction. This includes all of the time from the call to `navigator.getInterestGroupAdAuctionData()` to the completion of the `navigator.runAdAuction()` call. This metric is only recorded if there was *no* winning bid. See https://github.com/WICG/turtledove/blob/main/FLEDGE_browser_bidding_and_auction_API.md for the latest version of the Protected Audience Bidding & Auction Services explainer. mmenke@chromium.org morlovich@chromium.org The length of time it took to run a {AuctionType} auction that was aborted. This only happens on frame destruction. Recorded when the frame is destroyed. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org mmenke@chromium.org morlovich@chromium.org The length of time it took to run a {AuctionType} auction that had a winning bid. Recorded on auction complete. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org mmenke@chromium.org morlovich@chromium.org The length of time it took to run a {AuctionType} auction that completed successfully without a winner either due to no bidders making a bid, or the seller script rejecting all bidders. Not recoded when there are no bidders, or when an auction fails due to the seller worklet failing to load. Recorded on auction complete. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org behamilton@google.com morlovich@chromium.org Recorded at the end of a {AuctionType} auction when there is a non-k-anonymous winner. True when the non-k-anonymous winner is k-anonymous. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org mmenke@chromium.org morlovich@chromium.org The final result type of running a {AuctionType} auction. Recorded on auction completion/cancellation. See https://github.com/WICG/turtledove/blob/main/FLEDGE.md for the latest version of the FLEDGE explainer. behamilton@google.com pauljensen@chromium.org privacy-sandbox-dev@chromium.org Expired and removed 10/2022. johnidel@chromium.org dalecurtis@chromium.org Duration in milliseconds of HTML5 media (when known). Only recorded for media within ad subframes. This is recorded every time the duration changes for a video, and can be recorded multiple times for a single video (the overall duration may not be known when loading starts). Because the duration will generally increase as more video gets buffered, this histogram may skew low. johnidel@chromium.org jkarlin@chromium.org Load type of HTML5 media in ad subframes such as URL, MediaSource and MediaStream. Removed 11/2020. johnidel@chromium.org jkarlin@chromium.org For a given resource fetched from the disk cache or blink memory cache, logs the encoded body length of the resource, even if the resource request was canceled or incomplete. Recorded when the resource request is complete, or when the page is destroyed/navigated for incomplete resources. The sum of samples across a page load may differ substatially from the true sum due to per-sample rounding. These are not intended to be compared to page level histograms. Removed 04/2020. tbansal@chromium.org True if the target link of the anchor element has the same host as the root document. Recorded only on default search engine pages. Removed 04/2020. tbansal@chromium.org ryansturm@chromium.org src/chrome/browser/navigation_predictor/OWNERS True if the target link of the anchor element has the same host as the root document. Recorded only on pages whose URL do not match the default search engine. Removed 04/2020. chelu@chromium.org tbansal@chromium.org True if the target link of the anchor element has the same host as the root document. Removed 04/2020. chelu@chromium.org tbansal@chromium.org The number of anchor element metrics sent to the browser process on a page load. Anchor elements having the same href are merged and counted as 1. This histogram is recorded when the webpage is loaded. khushalsagar@chromium.org graphics-dev@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). Warning: this histogram was expired from 2020-04-24 to 2022-04-29; data may be missing. majidvp@chromium.org animations-dev@chromium.org The time it takes the WorkletMutatorDispatcher to complete an asynchronous mutation request of animation worklet. The measured time is the total elapsed time from when a request is queued until the results are received. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. majidvp@chromium.org animations-dev@chromium.org The time it takes the WorkletMutatorDispatcher to dispatch to and mutate all animation worklet mutators synchronously. This includes the time that it takes each AnimationWorkletGlobalScope to produce its output (which includes V8 script execution) and also any queuing cost associated with posting mutation tasks and receiving responses. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Whether DnsConfigService::OnConfigChange actually corresponded to a change in DnsConfig. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Duration of time between calls to DnsConfigService::InvalidateConfig. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Duration of time spent parsing DnsConfig. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Counts of results of parsing DnsConfig in DnsConfigServicePosix. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Counts of results of parsing DnsConfig in DnsConfigServiceWin. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Whether DnsHosts were parsed successfully. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Whether DnsConfigService::OnHostsChange actually corresponded to a change in DnsHosts. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Duration of time between calls to DnsConfigService::InvalidateHosts. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Duration of time spent parsing DnsHosts. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Counts of results of parsing DnsHosts in DnsConfigServiceWin. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Count of servers in DnsConfig. Recorded on every new DnsSession, which is created on DNS change. Removed 2021-01. pauljensen@chromium.org mef@chromium.org Duration of time since the last empty config result to the time a non-change OnConfigChange is received. Removed 2021-01. ericorth@chromium.org src/net/OWNERS Duration of time since the last empty config result to the time a non-change OnHostsChange is received. Removed 2021-01. ericorth@chromium.org src/net/OWNERS The result of DnsConfigService watch. Counts STARTED on every initialization and FAILED_* on any failure. jbauman@chromium.org Whether the browser compositor uses GPU or the software renderer. Removed in M97 as it was expired and it was not not updated on omnibox reverts, which led to incorrect counts. AutocompleteActionPredictor.NoStatePrefetchStatus is the new alternative. tbansal@chromium.org Every time we calculate the confidence for a URL to determine if it should be prerendered, we track the URL and confidence calculated. When an Omnibox navigation happens, if we calculated a confidence for that URL, a count is incremented for the confidence that was calculated. This histogram is then a histogram of counts that relates the number of correctly predicted URLs to a confidence value. By comparing that number to the AutocompleteActionPredictor.NavigationCount and Prerender.OmniboxNavigationsUsedPrerenderCount histograms, it's possible to determine the effect of changing the confidence threshold on the accuracy of prerendering prediction. tbansal@chromium.org chrome-omnibox-team@google.com jdonnelly@chromium.org Trackes the number of times something is added, removed, or deleted from the AutocompleteActionPredictor backing database. tbansal@chromium.org chrome-omnibox-team@google.com jdonnelly@chromium.org A boolean that indicates if the autocomplete suggestion under consideration by the AutocompleteActionPredictor was found in the database. This gives an upper bound on the fraction of suggestions it is possible to calculate a confidence for, and thus an upper bound on the fraction of suggestions that can be prerendered. tbansal@chromium.org The number of navigations triggered by the Omnibox and seen by the AutocompleteActionPredictor. This triggers when the Omnibox is showing Autocomplete results to the user and they select one with the mouse or by pressing enter. spelchat@chromium.org chrome-brapp-loading@google.com Records the status of no state prefetches started by the omnibox action predictor. In particular, this records whether they were used or not. Removed in M101. Use Prerender.Experimental.PredictionStatus.DirectUrlInput instead. asamidoi@chromium.org chrome-prerendering@google.com Records the status of prerender started by the omnibox action predictor. In particular, this records whether they were used or not. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.CacheEntryAge. robertogden@chromium.org tbansal@chromium.org How old a cached probe result was when it was used, in hours. Removed in M98. robertogden@chromium.org tbansal@chromium.org Records the completion status of a probe retry after an externally reported failure. Removed in M98. robertogden@chromium.org tbansal@chromium.org Records the completion status of a probe when it completes each attempt. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.FinalState. robertogden@chromium.org tbansal@chromium.org Records the end state of a probe just before it goes inactive. This happens when the prober succeeds, fails and has no more retries, or the delegate stops probing. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.GenerateCacheKey. spelchat@chromium.org curranmax@chromium.org Records the amount of time spent generating a cache key for the availability prober. In particular, this tracks how much getNetworkOperator calls might be slowing down this method. See crbug.com/1266018 for more details. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.NetError. robertogden@chromium.org tbansal@chromium.org Records the net error of a completed or timed out probe. Note that if a HTTP response does not occur within the probe's TTL, when a sample will also be added to the ERR_TIMED_OUT bucket. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.NumAttemptsBeforeSuccess. robertogden@chromium.org tbansal@chromium.org Records the number of attempts that are made to achieve a successful probe result. Only recorded on success. This metric is 1-based so if a probe succeeds the first time, a sample of 1 will be recorded. Removed in M98. robertogden@chromium.org tbansal@chromium.org Records the HTTP response code of a completed probe, when a HTTP response is received. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.TimeUntilFailure. robertogden@chromium.org tbansal@chromium.org Records the amount of time spent working on a single probe attempt to get to a failed state. Recorded every time a probe fails. Removed in M98. The corresponding histogram for canary checks is PrefetchProxy.CanaryChecker.TimeUntilSuccess. robertogden@chromium.org tbansal@chromium.org Records the amount of time spent working on a single probe attempt to get to a successful state. Recorded every time a probe succeeds. Removed in M88 as it's no longer needed. phillis@chromium.org cmumford@chromium.org The result from updating the app badge on macOS. Removed 2021-08-11. https://crbug.com/1165237 timvolodine@chromium.org device-dev@chromium.org Number of batteries reported by the UPower service on Linux at the start of the Battery Status API. Removed 2021-08-11. https://crbug.com/1165237 timvolodine@chromium.org Number of internal batteries reported by MacOS at the start of the Battery Status API. Removed 2021-08-11. https://crbug.com/1165237 timvolodine@chromium.org Number of batteries reported by Windows at the start of the Battery Status API. Removed 2021-09-02 due to being unused in the codebase. timvolodine@chromium.org src/services/device/OWNERS Whether the Battery Status API was successfully started up on Android. shaktisahu@chromium.org Records the size of the uncompressed commit messages received by Blimp compositor. shaktisahu@chromium.org Records whether connection attempt to the Blimp engine was successful. shaktisahu@chromium.org Records whether Blimp is supported. shaktisahu@chromium.org Records whenever a Blimp tab toggles visibility. mcchou@chromium.org chromeos-bt-platform-sw-core@google.com 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. apusaka@chromium.org chromeos-bt-platform-sw-core@google.com This is specific to Chrome OS. Records the number of active advertisement monitors every couple of minutes. This helps us to gauge the additional power requirement for the advertisement monitor feature. apusaka@chromium.org chromeos-bt-platform-sw-core@google.com This is specific to Chrome OS. Records the number of advertisement packet received in the user space while the advertisement monitor is done using {Filter} filtering. This helps us to gauge the additional power requirement for the advertisement monitor feature. apusaka@chromium.org chromeos-bt-platform-sw-core@google.com This is specific to Chrome OS. Records the outcome of {Operation} operation of advertisement monitor when {Filter} filtering is used. This helps us to verify the correctness of this feature as well as to point out possible regression. sonnysasaka@chromium.org chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com This is specific to Chrome OS. Records the number of existing advertisements when registering for a new advertisement. This helps us better understand the common amount of advertisments used and the registration failures due to the limited number of advertisement slots. mmandlik@google.com chromeos-bt-platform-sw-core@google.com Records the outcome of bluetooth profile connection request to a remote device. This helps to understand the percentage of successful profile connections against failures and the causes of failures. mmandlik@google.com chromeos-bt-platform-sw-core@google.com Records the outcome of bluetooth profile probing while pairing with a remote device. This helps to understand the percentage of successful profile probing against failures and the causes of failures. mcchou@chromium.org chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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 chromeos-bt-platform-sw-core@google.com 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. alemate@chromium.org briannorris@chromium.org rsorokin@chromium.org cros-oac@google.com Time from chrome binary exec to login UI ready on Chrome OS. This is recorded from the platform side after receiving "login-ui-visible" event on the platform side in the send-boot-metrics.conf script. Warning: this histogram was expired from M83 to M105; data may be missing. briannorris@chromium.org ctshao@google.com alemate@chromium.org baseos-perf@google.com Time from power on to kernel start (Chrome OS). Warning: this histogram was expired from M83 to M105; data may be missing. briannorris@chromium.org ctshao@google.com alemate@chromium.org baseos-perf@google.com Time from kernel start to system code being called (Chrome OS). Warning: this histogram was expired from M83 to M105; data may be missing. rsorokin@chromium.org antrim@chromium.org alemate@chromium.org cros-oac@chromium.org Time from the moment sign in authentication is started until the first user session UI elements become ready to use. (Chrome OS). briannorris@chromium.org ctshao@google.com alemate@chromium.org baseos-perf@google.com Time from system code being called to starting Chrome (Chrome OS). Warning: this histogram was expired from M83 to M105; data may be missing. alemate@chromium.org briannorris@chromium.org rsorokin@chromium.org cros-oac@google.com Time from power on to login UI ready on Chrome OS. This is recorded from the platform side after receiving "login-ui-visible" event on the platform side in the send-boot-metrics.conf script. Warning: this histogram was expired from 2022-04-03 to M105; data may be missing. eustas@chromium.org Compressed/Decompressed size ratio. eustas@chromium.org Error code observed after failing to decode a Brotli-compressed response stream from the network. Recorded for each layer of Brotli compression, as indicated using Content-Encoding header values, part of an HTTP response where a decoding error occurs. Warning: this histogram was expired from M85 to M110; data may be missing. eustas@chromium.org The final state of the BrotliFilter. Recorded during the decoding process as bytes are consumed from a Brotli-compressed response stream. Warning: this histogram was expired from M81 to M110; data may be missing. eustas@chromium.org Maximum amount of memory allocated to decode a Brotli-compressed response stream from the network. Recorded during the process of allocating memory to decode a Brotli-compressed response stream. Warning: this histogram was expired from M77 to M110; data may be missing. Retired in M93, replaced by Canvas.TextMetrics.SetFont2 which has a wider range. yiyix@chromium.org fserb@chromium.org Time spent in microseconds to perform calls to SetFont in Canvas for Canvas2d. It's measured each time SetFont is called. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. Retired in M94. yiyix@chromium.org fserb@chromium.org Time spent in microseconds to perform calls to SetFont in Canvas for Canvas2d. It's measured each time SetFont is called. This differs from Canvas.TextMetrics.SetFont in that it uses buckets up to ten seconds rather than ten milliseconds (due to a change in the underlying histogramming function called). Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. ryanchung@google.com Records the result of the Cast certificate verification on the Cast sender. mfoltz@chromium.org media-dev-uma@chromium.org Records any flags observed on the Cast channel used to launch a Cast session. A single channel may have multiple flags, and each flag is logged as a separate count. 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. No longer collected as of 2022-01. takumif@chromium.org mfoltz@chromium.org openscreen-eng@google.com Records the media type of every video being cast. Removed September 2020 as it's no longer being collected. 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 as of 2021/02 as it's not been collected for a while due to refactoring. tguilbert@google.com media-dev-uma@chromium.org Records the type of the remote playback device selected by the user. This will be recorded when the user has chosen the device from the media route chooser dialog. Deprecated as of 2021/02 as it's not been collected for a while due to refactoring. tguilbert@google.com media-dev-uma@chromium.org Record each interaction with the fullscreen remote playback controls in cases when the corresponding media element on the page was present. Deprecated as of 2021/02 as it's not been collected for a while due to refactoring. tguilbert@google.com media-dev-uma@chromium.org Record each interaction with the fullscreen remote playback controls in cases when the corresponding media element on the page was not present. Deprecated as of 2021/02 as it's not been collected for a while due to refactoring. tguilbert@google.com media-dev-uma@chromium.org Indicates whether the corresponding media element on the page was present when the fullscreen remote playback controls were shown. muyaoxu@google.com openscreen-eng@google.com Records the location when users interact with the RemotePlayback API on Clank. Please note, this metric does not show whether a session is started or stopped and does not include RemotePlayback sessions initiated through the Cast SDK. Deprecated as of 2021/02 as it's not been collected for a while due to refactoring. A new metrics, "Cast.Sender.Clank.SessionTimeWithoutMediaElementPercentage" now collects the same data but at a different location. tguilbert@google.com media-dev-uma@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. Deprecated as of 2021/02 as it's not been collected for a while due to refactoring. tguilbert@google.com media-dev-uma@chromium.org Records the result of resolving the video URL for cast, including checking its CORS header. fiorito@google.com mfoltz@chromium.org openscreen-eng@google.com Indicates whether initialization of a video encode accelerator for Cast sender was successful. Warning: this histogram was expired from 2021-10-17 to 2022-12-15; data may be missing. Please list the metric's owners. Add more owner tags as needed. cast-analytics@google.com The latency between when a Cast V2 connection is established and the first message is received on that connection. "Unknown" is the peer type, which is not known at this point in the CastV2 connection establishment. Naming conforms to the CastV2 sender-side histogram naming convention "CastV2.[action].[name].[peer_type]". Please list the metric's owners. Add more owner tags as needed. cast-analytics@google.com On accepting a Cast V2 transport socket connection, if an error is encountered, the error code is logged here. "Unknown" is the peer type, which is not known at this point in the CastV2 connection establishment. "SslHandshake.Error" is the name of the action. Naming conforms to the CastV2 sender-side histogram naming convention "CastV2.[action].[name].[peer_type]". Please list the metric's owners. Add more owner tags as needed. cast-analytics@google.com The time taken to do the handshake during Cast V2 transport socket creation. "Unknown" is the peer type, which is not known at this point in the CastV2 connection establishment. Naming conforms to the CastV2 sender-side histogram naming convention "CastV2.[action].[name].[peer_type]". rsleevi@chromium.org Information about the certificate algorithms and sizes in use on the web, to examine compliance with the CA/Browser Forum requirements and security best practice. This histogram considers the notBefore as the issuance date, for purposes of what requirements apply. wfh@chromium.org chrome-stability-core@google.com Recorded when a crash occurs in a Utility process. On crash, the exit code will indicate the exception code of the crash. wfh@chromium.org chrome-stability-core@google.com Count of child utility process crashes, bucketed by the hash of their process name. The process name is typically the service name of the mojo service. Recorded when a Utility process crashes. wfh@chromium.org chrome-stability-core@google.com Count of child process crashes grouped by process type. wfh@chromium.org Count of child process abnormal channel disconnects that are not classified and reported because we took the exit code too early. Grouped by process type. wfh@chromium.org chrome-stability-core@google.com Count of child process kills 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. wfh@chromium.org chrome-stability-core@google.com A platform-specific error code returned from the attempt to launch a Utility process. Recorded when a Utility process fails to launch. wfh@chromium.org chrome-stability-core@google.com Count of child utility process launch failures, bucketed by the hash of their process name. The process name is typically the service name of the mojo service. Recorded when a Utility process fails to launch. wfh@chromium.org chrome-stability-core@google.com An extended Windows error code returned from GetLastError when failing to launch a utility process. Recorded when a Utility process fails to launch on Windows. olivierli@chromium.org fdoray@chromium.org The time elapsed between the creation and destruction of a utility process. Recorded when the process is recorded as destroyed in PerformanceManager. Replaced by ChromiumAndroidLinker.BrowserLoadTime2 in 2021-07. rsesek@chromium.org The amount of time it took to load the native libraries in the browser process. pasko@chromium.org agrieve@chromium.org The ModernLinker loads the native library twice: once with android_dlopen_ext, and if the first one does not fail, also invokes System.loadLibrary(). This histogram reflects the time to load the native library when {LoadKind}. Failed load does not record a sample. Failing the first load would also avoid recording the histogram for the second load. See a description of RELRO sharing here: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/android_native_libraries.md#RELRO-Sharing pasko@chromium.org agrieve@chromium.org Same as ModernLinkerDetailedLoadTime.*, but additionally split by process background state as known to cgroups. Reflects load time when the app {BackgroundState}. When {LoadKind}. lizeb@chromium.org pasko@chromium.org Recorded when RELRO is replaced with a shared memory region, in all processes consuming RELRO. Indicates whether the shared RELRO was available synchronously right after the native library was loaded. ModernLinker only. lizeb@chromium.org pasko@chromium.org Recorded when the native library is loaded by the Chromium linker, and an attempt to spawn a shared RELRO region is made. Indicates whether the attempt was a success. If the number of samples from "ChromiumAndroidLinker.RelroAvailableImmediately" where the availability was not immediate is large compared to the counts of successful RELRO spawns, it would indicate potential startup performance improvements when starting child process(es) during early browser startup phases. ModernLinker only. Upgraded to ChromiumAndroidLinker.RelroSharingStatus2 around 2021-10. lizeb@chromium.org pasko@chromium.org Recorded when RELRO is replaced with a shared memory region, in all processes consuming RELRO. Indicates whether the replacement was a success. ModernLinker only. lizeb@chromium.org pasko@chromium.org Recorded when RELRO is replaced with a shared memory region, in all processes consuming RELRO. Indicates whether the replacement was a success. ModernLinker only. See a description of RELRO sharing here: https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/android_native_libraries.md#RELRO-Sharing Warning: this histogram was expired from 2022-12-04 to 2023-09-07; data may be missing. Replaced by ChromiumAndroidLinker.ChildLoadTime2 in 2021-07. rsesek@chromium.org The amount of time it took to load the native libraries in the renderer process. Removed in June 2023. pasko@chromium.org lizeb@chromium.org The amount of time to find the memory address reservation intended for WebView. This search is sometimes initiated as an early stage of loading the native library. A sample is discarded if the attempt to load the native library fails. Measured when running in {ProcessType} process. Only for {SearchStatus} searches. For a more detailed description of each suffix process type suffix (Browser, Child, Zygote) see description of the ChromiumAndroidLinker.*LoadTime2. pasko@chromium.org rsesek@chromium.org The amount of time it took to load the native libraries in {ProcessType}. In order to explain the nature of the uploaded samples for this histogram it is necessary to define a few core properties of the running processes. On Android 10 (=Q) a new feature was introduced and became used in Chrome: App Zygotes. An App Zygote (AZ) is a process pre-created by the system to allow faster initialization of isolated processes (IP) for a specific app. When AZ is created it runs the app-specific "preload" function once, and becomes idle, after that no work can be performed in the AZ other than getting forked. Whenever an app requests the Android Framework (AF) to provide an isolated process, the AF notifies the AZ to fork itself into a new process, which later will be provided to the app. An AZ created for one app (package) cannot be used for another app. The purpose of the AZ in Chrome is to load the native library - it avoids loading the same library in each isolated process separately. Capabilities of the AZ are very restricted. It runs in the same sandbox constraints as an isolated process, while also not having the ability to communicate with any other process on the system. Only after forking from the AZ the inherited process becomes able to communicate to the rest of Chrome. Beyond isolated processes, Chrome can request processes with more privileges: privileged processes (PP). In this case those processes will be forked from another zygote. There are several types of those zygotes, we will refer to them as Other Zygote (OZ) for simplicity. The decisions whether to start an isolated process through an AZ, and when to start a new AZ are made dynamically and depends on a few factors. The suffixes of this histogram, as described below, correspond to distinct execution scenarios: Suffix "Browser": the native library is loaded in the main app process Suffix "Zygote": OZ forks into AZ, AZ loads the native library, AZ forks into IP Suffix "Child": OZ forks into PP, PP loads the native library Suffix "Child": OZ forks into IP, IP loads the native library Suffix "Child": OZ forks into AZ, AZ fails to load the native library, AZ forks into IP, IP loads the native library (this scenario should happen rarely). After library loading happens in the AZ, the recorded histogram value (for simplicity) gets copied to each child process forked from this AZ process and uploaded "as if" it is a unique sample from this child process. This leads to a discrepancy in sample counts. In early 2021-10 it had about 7% extra uploaded samples in "ChromiumAndroidLinker.ZygoteLoadTime2". pasko@chromium.org agrieve@chromium.org The amount of CPU time (thread time) it took to load the native libraries in {ProcessType}. For a more detailed description of each suffix process type suffix (Browser, Child, Zygote) see description of the ChromiumAndroidLinker.*LoadTime2. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org Recorded every time a Chromoting connection enters a new state. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The duration of sessions that were closed, normally by a user-initiated action. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The duration of sessions that failed to connect. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The time taken to authenticate as part of a Chromoting connection request. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The time taken to connect to a remote-host, after a request has been authenticated. Removed in M98, metrics haven't been collected since ~mid 2019. joedow@chromium.org lambroslambrou@chromium.org Input event delivery latency from the browser to the plugin. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The bandwidth of non-empty packets in Chromoting remote sessions, updated every time a video packet is processed and logged every 1s. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The time to capture a video frame on the host, returned as part of a video packet. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org Amount of time wasted on IPC and threading overhead when capturing a video frame. Removed in M98, metrics haven't been collected since ~mid 2019. joedow@chromium.org lambroslambrou@chromium.org The time from when an input event is received to when the next frame is captured. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The time to decode a video packet on the client. Removed in M98, metrics haven't been collected since ~mid 2019. joedow@chromium.org lambroslambrou@chromium.org The time to encode a video packet on the host, returned as part of a video packet. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org Delay before a newly captured frame is passed to the encoder. Removed in M98, metrics haven't been collected since ~mid 2019. joedow@chromium.org lambroslambrou@chromium.org The frame-rate of non-empty packets in Chromoting remote sessions, updated every time a video packet is processed and logged every 1s. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org Estimated network roundtrip latency calculated by subtracting total processing time on host and client from the total roundtrip time. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The packets/sec, including empty packets, in Chromoting remote sessions, updated every time a video packet is processed and logged every 1s. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The time to paint a decoded video packet on the client. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org The time from an input being sent from the client to a response being received by the client after it is processed by the host. Removed in M98, metrics haven't been collected since ~mid 2019. jamiewalch@chromium.org Delay before an encoded video packet is written to the send buffer. victortan@chromium.org miketaylr@chromium.org Emitted on two related events: First, when an request that is eligable to be restarted receives an ACCEPT_CH HTTP2/HTTP3 frame via a TLS connection with the relevent ALPS setting. Next, if that frame causes that request to be restarted. victortan@chromium.org miketaylr@chromium.org Count of requests restarted because of the Critical-CH response header. miketaylr@chromium.org potassium-katabolism@google.com The latency (in microseconds) to fetch the client hints for a given origin from the Accept-CH cache for {OperationType}. Removed December 2021 as accept-ch-lifetime was retired. yoavweiss@chromium.org tbansal@chromium.org mkwst@chromium.org aarontag@chromium.org Duration for which the origin requested the client hints to be persisted. Collected on the renderer side. Collected while navigation responses are being processed. miketaylr@chromium.org potassium-katabolism@google.com The latency (in milliseconds) to store the client hints for a given origin in the Accept-CH cache. victortan@chromium.org potassium-katabolism@google.com Count of events when the client hints needs to be persisted to the disk by the browser. Collected while navigation responses are being processed. victortan@chromium.org potassium-katabolism@google.com Count of client hints that need to be persisted to the disk. Recorded by the renderer. Collected while navigation responses are being processed. curranmax@chromium.org This records whether or not the device scale factor was exactly 1.0 or not when sending either of the viewport height or viewport width client hint. There was a bug (see crbug.com/1394231) where the device scale factor was being applied twice to the viewport values. This histogram can be used to estimate the impact of that bug. hazems@chromium.org src/android_webview/OWNERS src/components/component_updater/android/OWNERS Records {Component} component loading success, or the failure reason if the component loading fails using the EmbeddedComponentLoader. Note that success here just means that the component has been fetched successfully from the components provider service. However, this doesn't neccessary mean that the component will be then loaded successfully in the system by its respective ComponentLoaderPolicy implementation. sorin@chromium.org src/components/component_updater/OWNERS 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. sorin@chromium.org src/components/component_updater/OWNERS The result of an install or an update check. sorin@chromium.org src/components/component_updater/OWNERS The result of an install or an update check. sorin@chromium.org src/components/component_updater/OWNERS Time to complete an Install or an Update component update call. chrisha@chromium.org The number of confirmed bad modules found during module enumeration. chrisha@chromium.org The length of time it takes to enumerate the loaded modules in the browser process. chrisha@chromium.org The length of time it takes to enumerate the shell extensions. chrisha@chromium.org The length of time it takes to enumerate the Winsock LSP modules. chrisha@chromium.org The cumulative length of time it takes to inspect all modules on disk, extracting their certificates and version information. This work is actually spread out over a much longer period of time so as not to impact the user. chrisha@chromium.org The cumulative length of time it takes to enumerate and inspect all modules. This work is actually spread out over a much longer period of time so as not to impact the user. chrisha@chromium.org The number of suspected bad modules found during module enumeration. ebeach@google.com Connectivity Diagnostics App: WiFi signal strength recorded during NIC_SIGNAL_STRENGTH test. The "Strength" property of a WiFi signal is a partially-reversible function that linearly maps the RSSI range -120dBm to -20dBm to Strength values from 0 to 100. ebeach@google.com Resolution latency seen by the Connectivity Diagnostics. Resolver latency is computed by using the chrome.dns API to query three randomly generated Google hostnames (*-ccd-testing-v4.metric.gstatic.com). The random hostnames guarantees that there will be no caching of DNS hostnames. The time taken from issuing the DNS request to receiving a response is clocked in JavaScript and the arithmetic mean of the three times is used as the resolver latency. Removed in M98 as the Context menu implementation changed. michaeldo@chromium.org src/ios/web/OWNERS Logs true when the system touches are cancelled in order to show the Context Menu instead of performing a default system action. Only logged on iOS. Removed in M98 as the context menu implementation changed. michaeldo@chromium.org src/ios/web/OWNERS Logged when DOM element details are not yet available when the user completes a long press. Also logs if the context menu was shown once the element details became available or if the display was cancelled. This ensures that all context menu gestures are eventually processed. Only logged on iOS. Removed in M98 as the ContextMenu implementation changed. michaeldo@chromium.org src/ios/web/OWNERS Logged when the Context Menu will be displayed. Also logs if the element for the last touch was found in the main frame or a iframe. Only logged on iOS. Replaced by Mobile.ContextMenu.CopyImage mrsuyi@chromium.org gambard@chromium.org Logged when the copying image from context menu is invoked and relevant events happen during the copying image procedure. Replaced by Mobile.ContextMenu.GetImageDataByJsResult mrsuyi@chromium.org gambard@chromium.org Result of getting image data by JavaScript for CopyImage, SaveImage and SearchByImage from iOS context menu. Recorded when the JavaScript returns, or fails for timeout. Replaced by Mobile.ContextMenu.LensSupportStatus hujasonx@google.com lens-in-bling-team@google.com Whether or not Lens is supported, and if not, the reason why. Recorded only if the feature is enabled when the long-press context menu is shown for an image. Replaced by Mobile.ContextMenu.LensWebUploadStatus hujasonx@google.com lens-in-bling-team@google.com The status of the upload of image data to Lens. Recorded only when the Lens feature is triggered via the context menu entry from an image long-press. Replaced by Mobile.ContextMenu.LensWebUploadTime hujasonx@google.com lens-in-bling-team@google.com Logs the time it takes to upload image data to the Lens Web servers. Recorded only when the Lens feature is triggered via the context menu entry from an image long-press. benwgold@google.com lens-chrome@google.com Whether the user supports the Lens intent and if not, the reason why. Recorded only if the feature is enabled when the long-press context menu is shown for an image. Removed in M103 qinmin@chromium.org Type of the url when user saves the content through the save link context menu. avi@chromium.org mpearson@chromium.org chrome-analysis-team@google.com {Type} The option that the user selected from a context menu on Android. This is logged on Android only; check out ContextMenu.SelectedOptionIOS for iOS, and ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is invoked on mixed content, only one of the submetrics receives the log; read the code to determine which one. This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. avi@chromium.org mpearson@chromium.org The option that the user selected from a context menu on desktop. This is logged on desktop only; check out ContextMenu.SelectedOptionIOS for iOS, and ContextMenu.SelectedOptionAndroid for Android. Note that if a menu is invoked on mixed content, only one of the submetrics receives the log; read the code to determine which one. Replaced by Mobile.ContextMenu.WebImage.Actions, Mobile.ContextMenu.WebImageLink.Actions and Mobile.ContextMenu.WebLink.Actions in M98 avi@chromium.org mpearson@chromium.org chrome-analysis-team@google.com The option that the user selected from a context menu on iOS. This is logged on iOS only; check out ContextMenu.SelectedOptionAndroid for Android, and ContextMenu.SelectedOptionDesktop for desktop. Note that if a menu is invoked on mixed content, only one of the submetrics receives the log; read the code to determine which one. This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. mpearson@chromium.org twellington@chromium.org clank-app-team@google.com {Type} Recorded when a context menu is shown, sliced by whether a web contents was present. (It generally should be; indeed, this code path should not be followed when it is absent. For instance, invoking a context menu from the new tab page or from the sad tab page will not cause an emission to this histogram.) Note that this refers to link context menus, not the cut-copy-paste context menus that can appear during long presses on text on a web page or long presses in the omnibox. This is an Android-only metric; compare with RenderViewContextMenu.Shown and RenderViewContextMenu.Used on desktop. Removed in M88. twellington@chromium.org clank-app-team@google.com Logged when the callback to fetch the thumbnail returns a result: Success (bitmap data received) or Failure (null bitmap). Android only. jeffreycohen@chromium.org chrome-shared-highlighting@google.com Records how long it takes to press on "Share" from the time context menu is shown. Android only. twellington@chromium.org clank-app-team@google.com The time it takes for the user to abandon the context menu after it's shown by pressing back or touching outside the menu. This is only logged if the menu is abandoned. See ContextMenu.TimeToTakeAction.SelectedItem for the cases where it is closed as a result of user interaction with the menu. Android only. twellington@chromium.org clank-app-team@google.com The time it takes for the user to select an item. This is only logged if the menu is closed as a result of the user clicking a menu item or a DirectShare button. See ContextMenu.TimeToTakeAction.Abandoned for the cases where it is abandoned by the user. Android only. yyushkina@chromium.org Number of times the emoji item in the views text services context menu is used. Removed in M98 as the context menu implementation changed. michaeldo@chromium.org src/ios/web/OWNERS Logs true when the context menu gesture recognizer fully recognizes a long press, but is still waiting on the DOM element details before the context menu can be shown. Only logged on iOS. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures the number of aggregation keys provided in attribution source registration headers. Recorded once for each source registration header when parsed from the attributionsrc response. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures how often aggregatable reports are assembled successfully or failed and why. Recorded once for each aggregatable report processed by the aggregation service on each send attempt. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures how often aggregatable reports are stored successfully or rejected and why. Recorded once for each trigger event processed by the attribution storage layer. `kNotRegistered` will be logged if the source or trigger doesn't declare aggregatable data. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures the percentage of aggregation keys dropped per trigger. Recorded when creating the aggregatable histogram. Not recorded if no aggregation keys were declared. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the "extra" non-scheduled time it took to send a particular aggregatable attribution report. This is primarily due to a report's scheduled report time taking place while the browser is closed or there is network issue. Recorded when an aggregatable report is to be assembled. tquintanilla@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the "extra" non-scheduled time it took to confirm the aggregatable attribution report was sent. This is primarily due to a report's scheduled report time taking place while the browser is closed or there is network issue. Recorded when an aggregatable report is successfully sent. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures the percentage of aggregatable trigger data filtered per trigger. Recorded when creating the aggregatable histogram. Not recorded if no trigger data was declared. This is effectively how many trigger side dimensions the reporter declared, but were not used for histogram generation. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures the number of aggregatable histogram contributions per report. Recorded when creating the aggregatable histogram. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Upon storing an Aggregatable Report at `creation_time`, it is scheduled with a `reporting_delay` to send at time `report_time` and is pending until then. If the browser closes or the device goes offline, and until it re-opens or re-connects, we are unable to send reports. On such events, for each pending reports, we record two {TimeSpan}s: [1] TimeSinceCreation: The time elapsed since the report was created (creation_time - now). [2] TimeUntilReportTime: The time remaining for the report to be sent (report_time - now). The metrics will enable us to quantify the extent to which reducing `reporting_delay` would increase the number of reports sent before an unavailability event. [Limitation] To limit memory usage, a maximum of 50 pending reports timings are handled. Past this number, reports are dropped (until reports get sent or an unavailability event occurs). Given that the most recent reports can be dropped, we can expect the `TimeSinceCreation` to be biased down slightly and `TimeUntilReportTime` to be biased up slightly. We expect this situation to be infrequent given the 10-60 minutes reporting window. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the high level request status of an aggregatable report. Recorded once per aggregatable report. For aggregatable report that has been retried, only the last retry will be counted. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the time difference from when the report was intended to be sent, and the actual report time. This is different from Conversions.AggregatableReport.ExtraReportDelay because it uses the send attempt report time, rather than initial report time assigned by the API. Accounts for any delays in Chrome scheduling the report. Recorded when an aggregatabl report is to be assembled. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the time between a trigger and its assembly. This is emitted whenever an aggregatable report is to be assembled by the aggregation service. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the time between a trigger and its reporting. This is emitted only when an aggregatable report is sent succeessfully to the reporting endpoint, and not emitted for debug reports. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures how often attribution OS registrations were successfully registered with Android or failed and why. Only recorded on Android when the AttributionReportingCrossAppWeb feature is enabled. Recorded for each OS registration processed by the Java attribution OS-level manager. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the status of the attributionsrc requests. Recorded when the request started and finished. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records whether web or OS-level attribution is supported on the device. Only recorded on Android when the AttributionReportingCrossAppWeb feature is enabled. Recorded once per browser session when the browser starts up. johnidel@chromium.org csharrison@chromium.org Records the time it takes to clear conversion data. Logged any time site data is cleared in Chrome. tquintanilla@chromium.org apaseltiner@chromium.org measurement-api-dev+metrics@google.com Measures how often event-level triggers are stored successfully or rejected and why. Recorded once for each conversion event processed by the attribution storage layer. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Error info for sending a debug attribution report, recorded for each sent aggregatable report. The HTTP response code is recorded if there is no net error code for the request, or the net error code indicates there was a response code failure. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Error info for sending a debug attribution report, recorded for each sent event-level report. The HTTP response code is recorded if there is no net error code for the request, or the net error code indicates there was a response code failure. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records whether a particular aggregatable debug attribution report was successful. Emitted for all aggregatable debug attribution reports that retry. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records whether a particular event-level debug attribution report was successful. Emitted for all event-level debug attribution reports that retry. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the high-level request status of an aggregatable debug attribution report. Recorded for every debug aggregatable attribution report sent. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the high-level request status of an event-level debug attribution report. Recorded for every debug event-level attribution report sent. anthonygarant@chromium.org measurement-api-dev+metrics@google.com When registering an attribution data host, its registration will be deferred if it can register triggers and there are pending navigation-source registrations from the page that navigated to that page. Receivers are deferred until the pending navigation-source registrations complete or a timeout is reached. When processing a deferred attribution data host registration, this metric records if it's due to a timeout. csharrison@chromium.org measurement-api-dev+metrics@google.com For every successfully parsed attribution source that is also allowed by browser policy, records the result of the time-based destination limit, which governs whether a source can proceed to the storage layer. apaseltiner@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures how often sources and triggers are allowed to be enqueued for processing in the attribution manager. If the queue reaches a maximum size, additional sources and triggers are dropped. Events are enqueued while waiting for a previous debug-cookie check to complete. apaseltiner@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures how often OS sources and triggers are allowed to be enqueued for processing in the attribution manager. If the queue reaches a maximum size, additional OS sources and triggers are dropped. Events are enqueued while waiting for a previous debug-cookie check to complete. Only recorded on Android. apaseltiner@chromium.org johnidel@chromium.org csharrison@chromium.org Records the "extra" non-scheduled time it took to send a particular conversion report. This is primarily due to a report's scheduled report time taking place while the browser is closed. Recorded when a conversion report is to be sent. tquintanilla@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the "extra" non-scheduled time it took to confirm the particular attribution report was sent. This is primarily due to a report's scheduled report time taking place while the browser is closed. Recorded when an attribution report is successfully sent. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures filter sizes in source and trigger registrations. This includes filter data in source, top-level trigger, event-level and aggregatable trigger data. Recorded once for each filter data when parsed from the attributionsrc response. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the time it took to go througth JNI to invoke Android API to get measurement status. Only recorded on Android when the AttributionReportingCrossAppWeb feature is enabled. Recorded once per browser session when the browser starts up. Only recorded if base::ThreadTicks is suppported. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Error info for sending an attribution report, recorded for each sent aggregatable report. The HTTP response code is recorded if there is no net error code for the request, or the net error code indicates there was a response code failure. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Error info for sending an attribution report, recorded for each sent event-level report. The HTTP response code is recorded if there is no net error code for the request, or the net error code indicates there was a response code failure. johnidel@chromium.org csharrison@chromium.org Measures how often impressions are ignored because the initiator frame is dead by the time the navigation reaches the browser. johnidel@chromium.org csharrison@chromium.org linnan@chromium.org Records the number of impressions deleted per clearing operation. csharrison@chromium.org measurement-api-dev+metrics@google.com Measures the number of failures via the proposed insecure tainting mechanism, where a redirect chain will be considered "tainted" when it encounters its first insecure redirect, causing any subsequent registrations to fail even if they are secure. This metric attempts to measure the breakage. It is emitted on the completion of any main frame navigation which had at least one secure response register ARA headers. It counts how many failed registrations that navigation would have observed with tainting enabled. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records status for navigation data hosts. A single navigation data host may emit two status, one when the navigation started and the data host was registered, and one when the navigation finished or failed. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures how often attribution OS registrations were successfully registered with Android or failed and why. Only recorded on Android when the AttributionReportingCrossAppWeb feature is enabled. Recorded for each OS registration processed by the attribution manager layer. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Records the delay between a data host registration being deferred by the AttributionDataHostManagerImpl and it being processed. Only recorded for data host that are deferred rather than processed immediately or dropped. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Records the status of a data host registraton. Its status is influenced by trigger buffering. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures the number of sources or triggers registered per redirect chain. Recorded when the corresponding resource client finishes. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records whether a particular aggregatable attribution report was successful. Emitted for all conversion aggregatable reports which retry. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records whether a particular event-level attribution report was successful. Emitted for all attribution event-level reports which retry. johnidel@chromium.org tquintanilla@chromium.org measurement-api-dev+metrics@google.com Records the number of aggregatable attribution reports deleted per clearing operation. johnidel@chromium.org csharrison@chromium.org linnan@chromium.org Records the number of event-level attribution reports deleted per clearing operation. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the high level request status of a conversion report. Recorded once per conversion report. For conversion report that has been retried, only the last retry will be counted. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the high level request status of an attribution report. Recorded for every aggregatable attribution report sent. For attribution report that has been retried, every retry will be counted. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the high level request status of an attribution report. Recorded for every event-level attribution report sent. For attribution report that has been retried, every retry will be counted. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Records the top_frame origin status when an attempting to complete a trigger verification. In the attribution context, the origin represents the destination origin which is required to complete the verification operation. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Time taken to execute various parts of a Trigger Verification operation: [1] GetKeyCommitment = time taken to retrieve the issuer's key commitment. [2] InitializeCryptographer = time taken to initialize the BoringSSL cryptographer with the issuer's keys. [3] BlindMessage = time taken by the cryptographer to blind the message. [4] Issuer = time from the end of the outbound BlindMessage half to the beginning of the inbound UnblindSignature half. [5] UnblindSignature = time taken to unblind the blind signature received from the issuer. [6] Total = GetKeyCommitment + InitializeCryptographer + BlindMessage + UnblindSignature (only recorded for operations that see issuer's responses) Each part of the operation can be a Failure or a Success. e.g. if we are unable to retrieve key commitment for an issuer, it is a failure. The metrics are recorded when the verification operation finish. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Records the status of the initial part of a verification operation which attempts to retrieve verification headers to be added to a trigger registration request. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Records the status of the second part of a verification operation which processes the private state issuer's signature to generate a verification token. Metric no longer relevant/needed considering null reports generation. anthonygarant@chromium.org measurement-api-dev+metrics@google.com Records whether an aggregatable report is sent with a verification token or not. Only recorded for reports if the Report Verification feature is enabled. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the time difference from when the report was intended to be sent, and the actual report time. This is different from Conversions.ExtraReportDelay2 because it uses the send attempt report time, rather than initial report time assigned by the API. Accounts for any delays in Chrome scheduling the report. Recorded when an event-level report is to be sent. tquintanilla@chromium.org linnan@chromium.org measurement-api-dev+metrics@google.com Measures how often verbose debug reports are sent and the corresponding report type. Recorded when the verbose debug report is created. As there may be more than one report type per report, multiple entries may be logged for a report. tquintanilla@chromium.org linnan@chromium.org measurement-api-dev+metrics@google.com Measures how often source registration parsing failed and why. Recorded only when parsing failed; not recorded when parsing succeeded. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com When the storage database is initialized upon the API's first use, count and sort in descending order the number of sources per source origin. The metric records the count at the {Position} position. Only recorded if initialization is successful. tquintanilla@chromium.org anthonygarant@chromium.org measurement-api-dev+metrics@google.com Measures how often sources are stored successfully or rejected and why. Recorded once for each source event processed by the attribution storage layer. johnidel@chromium.org csharrison@chromium.org Records the time it took to do perform a clear operation on the database when supplied an origin filter. Recorded when the conversion database finishes performing a clear operation. Note that filters may vary in size and computation complexity, skewing this metric aribtrarily. johnidel@chromium.org csharrison@chromium.org Records the time it took to initialize a new conversions database from scratch. Recorded when the conversion database finishes initialization. Only recorded on platforms with base::ThreadTicks support. johnidel@chromium.org csharrison@chromium.org Records the time it took to migrate a preexisting conversions database to the latest schema. Recorded when the conversion database finishes initialization. Only recorded on platforms with base::ThreadTicks support. tquintanilla@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com When the storage database is initialized upon the API's first use, records the file size of the database in KB. Only recorded if initialization is successful. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com When the storage database is initialized upon the API's first use, records the file size of the database in bytes divided by the number of sources in storage. Only recorded if initialization is successful. tquintanilla@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the file size of the storage database in KB when the max sources per origin limit is reached. Emitted whenever a source fails to be stored due to this limit. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the file size of the storage database in bytes divided by the number of sources in storage. Reported when the max sources per origin limit is reached. Emitted whenever a source fails to be stored due to this limit. johnidel@chromium.org csharrison@chromium.org Records initialisation statuses of ConversionStorageSql. Note: currently ConversionStorageSql is initialised lazily. johnidel@chromium.org csharrison@chromium.org Records the time between a conversion and its reporting. This is emitted whenever a conversion report is sent. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the time between a trigger and its reporting. This is emitted only when an event-level report is sent successfully to the reporting endpoint, and not emitted for debug reports. tquintanilla@chromium.org linnan@chromium.org measurement-api-dev+metrics@google.com Measures how often trigger registration parsing failed and why. Recorded only when parsing failed; not recorded when parsing succeeded. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Measures the number of values in a filter. This includes filter data in source, top-level trigger, event-level and aggregatable trigger data. Recorded once for each filter in the filter data when parsed from the attributionsrc response. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Error info for sending a verbose debug report, recorded for each sent verbose debug report. The net error code is recorded if the HTTP response code is unavailable. anthonygarant@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Per the spec, {RegistrationType} filtering keys prefixed with "_" should only be used for specified features, e.g., lookback window. Before enforcing this, we use this metric to measure the number of {RegistrationType}s that would be affected by the change. Recorded for {RegistrationType} registrations which can otherwise be parsed successfully. linnan@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the network connection type in the event that the report failed to be sent due to network issues. Recorded for each report sending attempt that failed. tquintanilla@chromium.org johnidel@chromium.org measurement-api-dev+metrics@google.com Records the number of retries before a report is successfully sent or records 'Failed' if report delivery fails after reaching the max number of retries (2). wychen@chromium.org The cache hit status of metadata extraction for AppIndexing. wfh@chromium.org chrome-stability-core@google.com The exit codes for crashed extension processes. Note: Due to https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. wfh@chromium.org chrome-stability-core@google.com The exit codes for crashed renderer processes. Note: Due to https://crbug.com/805754, the enum labels are off by 1 for M56 and earlier. smaier@chromium.org crashpad-dev@chromium.org The reason that an ANR upload was skipped. jperaza@chromium.org crashpad-dev@chromium.org The reason that a crash report entered the upload pending state. jperaza@chromium.org crashpad-dev@chromium.org The size of a crash report minidump on disk when captured. jperaza@chromium.org crashpad-dev@chromium.org Logs whether a crash uploaded succeeded or failed. jperaza@chromium.org crashpad-dev@chromium.org The reason that a crash report upload was skipped. jperaza@chromium.org crashpad-dev@chromium.org The outcome of execution of the Crashpad exception handler. mark@chromium.org crashpad-dev@chromium.org The exception code encountered in a crash on Mac OS X. jperaza@chromium.org crashpad-dev@chromium.org The exception code encountered in a crash on Windows. jperaza@chromium.org crashpad-dev@chromium.org A count of the number of exceptions handled by Crashpad with two buckets for starting and finishing. mark@chromium.org crashpad-dev@chromium.org The exception code encountered for a crash of the crash handler process on Mac OS X. jperaza@chromium.org crashpad-dev@chromium.org The exception code encountered for a crash of the crash handler process on Windows. Kept as a diagnostic metric. jperaza@chromium.org crashpad-dev@chromium.org Handler start/crash/exit events. justincohen@chromium.org crashpad-dev@chromium.org Records key id when id has an invalid sizein an intermediate dump. justincohen@chromium.org crashpad-dev@chromium.org Records key id when id is missing in an intermediate dump. Removed 11/2022. justincohen@chromium.org olivierrobin@chromium.org Reports the Foundation error code of an attempt to upload a breakpad crash report. "NSNoError" if the upload was successful. As of 2020-12, we've decided on a timeout and no longer need this metric. mutexlox@chromium.org iby@chromium.org cros-telemetry@google.com The amount of time crash_sender takes to run when invoked directly on Chrome OS, without counting time spent sleeping (e.g. for hold_off_time). Used to make an informed decision about a timeout. As of 2020-12, we've decided on a timeout and no longer need this metric. mutexlox@chromium.org iby@chromium.org cros-telemetry@google.com The amount of time crash_sender takes to run when invoked directly on Chrome OS. Used to make an informed decision about a timeout. Removed 05/2022. spelchat@chromium.org chrome-brapp-loading@chromium.org Time that the UI thread is blocked on loading the Android Data Saver setting from the OS. pmonette@chromium.org grt@chromium.org The HRESULT from ActivateApplication when opening the Win10+ settings page fails. pmonette@chromium.org robliao@chromium.org Possible user interactions with the default browser info bar. Removed in Chrome 78. gab@chromium.org Results of interaction with set-as-default dialog in Win8+ first run flow. pmonette@chromium.org The outcome of an attempt to set Chrome as the user's default browser. gab@chromium.org pmonette@chromium.org Whether Chrome was the default browser when it started up. Only logged correctly on Windows and Mac. Logged incorrectly on other platforms. On Linux, this histogram is no longer logged as of 2021/10/18 due to browser test hangs. See crbug.com/1216328. For ChromeOS, no histogram is necessary because Chrome is always the default browser. For Android, see Mobile.DefaultBrowser.State. For iOS, in the future Chrome will be allowed to be the default browser. How that will be logged is to be decided at the time of writing this description. pmonette@chromium.org When changing the default browser on Windows 10, records whether the browser chooser is successfully invoked when opening the settings page. This histogram is only recorded when the Win10AcceleratedDefaultBrowserFlow experiment is enabled. pmonette@chromium.org The outcome of an attempt to set Chrome as the user's default client for a protocol. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The currently active app or window. Sampled during demo sessions and reported while the user remains active. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Records apps that have been launched by a user using the device during Demo mode. The sample is recorded when each app is launched. For any given app id, the metric is recorded only once per Demo Session. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The source of app launches in demo mode, either the shelf, the app list, or the highlights app. llin@google.com xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The timestamp (i.e. milliseconds from the beginning of the Attract Loop video) at which the user broke the Demo Mode Attract Loop. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The duration the user spent interacting with the demo session, measured from the first user activity to the last user activity. This metric rounds the duration to the nearest second and uses exponential bucketing capped at 1 hour. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Records whether a window associated with GMSCore has been created during the demo session. llin@google.com xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The duration a user spent on a given details page of the Highlights App. Only is recorded for Highlights App versions with the UI concept of a "details" page. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The first interaction (button clicks) after entering the Highlights app. The metric will be emitted once the user clicks on a button in Hightlights app, e.g. pillar page button or the home button on the home page. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com The time duration a user stays in each page of the Highlights app, e.g. the home page, each pillar page. The metric will be emitted when the user enters another page or exits the Highlights app. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Tracks whether the idle logout warning was canceled or proceeded to logout. Note: the count of "shown" includes both cases, so the count of "shown and proceeded" is equal to "shown" minus "canceled". llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Tracks the reason for removal of pre-install demo resources. To support offline demo mode, factory Chrome OS devices will have a set of offline enabled demo mode apps pre-installed. These resources are removed once they are not needed anymore. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Tracks the result of requests to remove pre-installed demo resources. To support offline demo mode, factory Chrome OS devices will have a set of offline enabled demo mode apps pre-installed. These resources are removed once they are not needed anymore. This will record only requests that attempted deleting pre-installed resources from disk. Requests that fail early will be ignored. For example, a request will fail early if the device is in demo mode, or the resources have already been removed. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com A demo session starts when a user signs in using the policy-configured public account. It stops when the user signs out, either manually or after an idle timeout. Session length is the duration between the start and stop events. It is recorded during signing out and reported on the next chrome run. This metric tracks the recorded session length rounded down to the nearest minute and is capped at 2 hours. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com This records the time taken to download the demo mode resources when demo mode is setup for the first time. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com This records the time taken to enterprise-enroll the device when demo mode is setup for the first time. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com When demo mode is setup for the first time, it must download the demo mode resources and enterprise-enroll the device. This records the time taken for these two steps to complete. (See DemoMode.Setup.DownloadDuration and DemoMode.Setup.EnrollDuration) llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Records the number of times an operator has encountered an error during the loading screen and been required to retry setup. This is only recorded after setup completes successfully. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Records how many unique apps have been launched by a user using the device during Demo mode. The sample is recorded when the DemoMode session closes. llin@chromium.org xiqiruan@chromium.org yilkal@chromium.org cros-demo-mode-eng@google.com Records how many times the user clicks mouse and presses screen in the demo session. During one demo session, if a mouse click or screen press happens, increment this metric by one. glenrob@chromium.org greengrape@google.com Record how often each permission check (e.g. permissions policy, transient activation, user dialog, hostname resolving to non-public address, rate limiting, CORS, enterprise policy) cause Permission Denied failures. Recorded when the permission is denied. bartfab@chromium.org greengrape@google.com How often tcp socket opening finishes with a network failure. bartfab@chromium.org greengrape@google.com How often tcp server socket opening finishes with a network failure. bartfab@chromium.org greengrape@google.com How often udp socket opening finishes with a network failure. zentaro@chromium.org cros-peripherals@google.com 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. jshargo@chromium.org oshima@chromium.org chromeos-gfx-compositor@google.com The way in which mirroring is implemented, either in hardware or software. This is emitted once when mirroring is enabled through API call, or the display configuration changes ( e.g. adding or removing a display) when mirror mode is on. zentaro@chromium.org cros-peripherals@google.com The types of mirror mode in which the displays connected to the device are in. This is emitted once when the normal or mixed mirror mode is enabled through API call, or the display configuration changes ( e.g. adding or removing a display) when mirror mode is on. zentaro@chromium.org cros-peripherals@google.com The mode in which the connected displays to the device are in. This is emitted once when displays are added or removed, or when the user changes the mode by e.g. enabling mirror or unified modes. zentaro@chromium.org cros-peripherals@google.com The number of displays connected to the device when Unified Desktop mode is on. This is emitted when Unified Desktop mode is turned on, or the displays are added or removed while in Unified Mode. zentaro@chromium.org cros-peripherals@google.com Records whether or not the display configuration was successfully updated. Emitted when the update-display-configuration task finishes, successfully or not. Warning: this histogram was expired from M102 to M117; data may be missing. 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). panicker@chromium.org chikamune@chromium.org Records result of invoking beforeunload handler, that determines whether to show the dialog. Warning: this histogram was expired from M77 to M108; data may be missing. Removed in M90. 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. Removed in M90. hajimehoshi@chromium.org keishi@chromium.org Records documents that survives some GCs after the document is shut down. sullivan@chromium.org chikamune@chromium.org Milliseconds spent in beforeunload dialog. Does not include time to process beforeunload event in JavaScript. Recorded immediately after closing dialog, upon user confirmation to navigate away from the page. Warning: this histogram was expired from 2020-09-05 to M108; data may be missing. bmgordon@chromium.org project-bolton@google.com Chrome OS document scan metric that tracks which SANE backend (effectively a scanner driver) was used when a scan failed. rishabhagr@google.com project-bolton@google.com Chrome OS document scan metric that tracks the stage at which the scan failed. rishabhagr@google.com project-bolton@google.com Chrome OS document scan metric that tracks the reason of a scan failure. bmgordon@chromium.org project-bolton@google.com Chrome OS document scan metric that tracks which SANE backend (effectively a scanner driver) that a user requested to use for a scan. bmgordon@chromium.org project-bolton@google.com Chrome OS document scan metric that tracks which SANE backend (effectively a scanner driver) was used when a scan succeeded. Removed in M89. grt@chromium.org The number of items within the Cache directory that could not be moved aside following a downgrade. 0 indicates that the target directory could not be created. Removed in M89. grt@chromium.org Indicates whether or not moving a user's cache dir following a downgrade succeeded or failed. Removed in M89. grt@chromium.org ydago@chromium.org The number of items within from an invalid snapshot directory that could not be moved. 0 indicates that the target directory could not be created. Removed in M89. grt@chromium.org ydago@chromium.org Indicates whether or not moving an invalid snapshot directory succeeded or failed. Removed in M89. grt@chromium.org ydago@chromium.org Indicates whether or not cleaning up after a snapshot restoration failure succeeded or failed. Removed in M89. grt@chromium.org ydago@chromium.org The number of items within from a snapshot directory that could not be restored following a downgrade. grt@chromium.org ydago@chromium.org Indicates whether or not restoring a snapshot of the user data dir succeeded or failed. Removed in M100. grt@chromium.org ydago@chromium.org The number of items within the user data directory that could not be snapshotted following an upgrade. grt@chromium.org ydago@chromium.org Indicates the id of an item that failed to be copied when taking a user data snapshot. The metrics does not cover the data from 12/12/2021 to 03/29/2022. Removed in M89. grt@chromium.org ydago@chromium.org The number of items within an existing snapshot directory that could not be moved aside before replacing it with a newer snapshot. Removed in M89. grt@chromium.org ydago@chromium.org Indicates whether or not moving a user data snapshot dir before replacing it with a newer snapshot succeeded or failed. Removed in M89. grt@chromium.org ydago@chromium.org Indicates whether or not creating a profile directory while creating a user data snapshot succeeded or failed. Removed in M100. grt@chromium.org ydago@chromium.org Indicates whether or not creating a snapshot of the user data dir succeeded or failed. Deprecated as of M96 grt@chromium.org ydago@chromium.org The number of items within User Data that could not be moved aside following a downgrade. Deprecated as of M96 grt@chromium.org ydago@chromium.org Indicates whether or not moving a user's User Data dir following a downgrade succeeded or failed. simmonsjosh@google.com src/ui/file_manager/OWNERS 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. simmonsjosh@google.com src/ui/file_manager/OWNERS Tracks whether the push notification request is registered correctly for Drive. Recorded when the push notification manager is initialized. Removed 2022-02 as this feature never launched. simmonsjosh@google.com src/ui/file_manager/OWNERS 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. mcasas@chromium.org chromeos-gfx-video@google.com Number of bits per channel described by a parsed EDID blob. This UMA is recorded whenever the color space is extracted from an EDID blob. Warning: this histogram was expired from 2022-01-03 to 2023-05-17; data may be missing. mcasas@chromium.org chromeos-gfx-video@google.com Whether an EDID blob was detected. This UMA is recorded whenever we attempt to parse the EDID from a display. Warning: this histogram was expired from 2022-01-03 to 2023-05-17; data may be missing. mcasas@chromium.org chromeos-gfx-video@google.com Whether a EDID blob contained an HDR transfer function (e.g. SMPT SE2084 or HLG). This UMA is recorded whenever the color space is extracted from an EDID blob. Warning: this histogram was expired from 2022-01-03 to 2023-05-17; data may be missing. andrescj@chromium.org mcasas@chromium.org sashamcintosh@chromium.org chromeos-gfx@google.com When attempting to get the color space from an EDID blob, whether the sanity checks passed (and if not, which check failed). This UMA is recorded whenever the color space is extracted from an EDID blob. Expired in January 2022, and revived in June 2023 (M117). Data collected between those dates may be incomplete. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com This metric tracks the time it takes from the phone becoming connected to the Chromebook and sending the PhoneStatusSnapshot proto until the phone sends over the entire apps list via the AppListUpdate proto. Emitted after the app stream launcher loads the app list. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com This metric logs where the Eche app was launched from. The metric is emmited when the eche app is launched. crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com The duration of time the phone is in the state connected to eche signaling service, and becomes disconnected. crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com Measures Eche connection success rate. This is recorded at the end of each connection attempt whether it fails or succeeds and the failure bucket is broken down to more specific segments in Eche.Connection.Result.FailureReason jonmann@chromium.org chromeos-cross-device-eng@google.com The reason for which the connection attempt to the phone has failed. This is a breakdown of the failure bucket of Eche.Connection.Result and is recorded at the time a connection attempt fails. crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com The duration of time the phone is in the state connecting to eche signaling service, and becomes connected. jonmann@chromium.org chromeos-cross-device-eng@google.com Indicates the feature state of the Exo feature. This metric is emitted to at the creation of the user session (when the user logs in), when any multi-device feature state changes, and every 30 minutes. jonmann@google.com nayebi@google.com chromeos-cross-device-eng@google.com Failure reason emitted by EcheSignaler on background connect attempt failures. jonmann@google.com nayebi@google.com chromeos-cross-device-eng@google.com Emitted on success or failure of a background network connection attempt. Triggered when Phone Hub first connects, and on each bubble opened event. Deprecated as of 11/2022. Replaced with Eche.AppStream.LaunchAttempt crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com Events logged after the user interacts with a PhoneHub notification by clicking it to launch app streaming window. crisrael@google.com exo-core-eng@google.com samchiu@google.com Events logged the user action in the Eche onboarding. Recorded when users start Eche onboarding and grant the permission that onboarding needs. crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com Events logged in the Eche stream state. Records when a stream is started and initialized after the user interacts with a PhoneHub notification or the recent app by clicking it to launch the app streaming window. crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com Events logged the root cause of Eche connection failure. Records when signaling timeout on EcheSignaler or the tablet mode check on EcheTray. crisrael@google.com exo-core-eng@google.com chromeos-cross-device-eng@google.com Records the elapsed time from when the stream is initializing to when the stream is closed before the stream doesn't started. Fires during the process of closing Eche streaming when the stream doesn't start. It is not sent on a successful connection attempt. pushi@google.com jonmann@google.com chromeos-cross-device-eng@google.com Events logged in the Eche stream state. Records when a stream is initialized and started after the user clicks on an app from full app list (Launcher) to launch the app streaming window. pushi@google.com jonmann@google.com chromeos-cross-device-eng@google.com Events logged in the Eche stream state. Records when a stream is initialized and started after the user clicks on a PhoneHub notification to launch the app streaming window. pushi@google.com jonmann@google.com chromeos-cross-device-eng@google.com Events logged the root cause of Eche connection failure when triggered from a notification and failed in last network connection check. Records when signaling timeout on EcheSignaler or the tablet mode check on EcheTray. Separate from Eche.StreamEvent.ConnectionFail. pushi@google.com jonmann@google.com chromeos-cross-device-eng@google.com Records the success rate of app streaming when triggered from notificaiton and failed in last network connection check. Recorded when the stream is initialized in EcheTray or when it starts in EcheStreamStatusChangeHandler. Separate from Eche.StreamEvent. pushi@google.com jonmann@google.com chromeos-cross-device-eng@google.com Events logged in the Eche stream state. Records when a stream is initialized and started after the user clicks on an app from recent app list to launch the app streaming window. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com This metric tracks the number of unique apps the user attempts to launch an app stream. Emitted when the app stream is launched and the app has not been launched in the current session. Deprecated as of 05/2021 donnd@chromium.org jinsukkim@chromium.org Records the reason that the BottomSheet-based Ephemeral Tab panel was closed. Recorded when the UX is hidden. Implemented for Android. Deprecated as of 05/2021 donnd@chromium.org jinsukkim@chromium.org Records the reason that the Ephemeral Tab panel was closed. Recorded when the UX is hidden. Implemented for Android. Deprecated as of 12/2021 donnd@chromium.org jinsukkim@chromium.org Records whether the user fully opened the Ephemeral Tab panel when it was shown. Recorded when the UX is hidden. Implemented for Android. Deprecated as of 12/2021 donnd@chromium.org jinsukkim@chromium.org Records whether the user opened the Ephemeral Tab panel beyond peeking state. Recorded when the UX is hidden. Implemented for Android. Deprecated as of 12/2021 donnd@chromium.org jinsukkim@chromium.org Records the duration in milliseconds that the Ephemeral Tab was left open. Recorded when the UX is hidden. Implemented for Android. Deprecated as of 12/2021 donnd@chromium.org jinsukkim@chromium.org Records the duration in milliseconds that the Ephemeral Tab was peeking. Recorded when the UX is hidden. Implemented for Android. dewittj@chromium.org petewil@chromium.org chrome-analysis-team@google.com The number of times the user clicked on a site in a category with the selected type on the Explore Sites page. This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. dimich@chromium.org 0-based index of a category tile on NTP which was clicked by the user. Indices are assigned by counting category tiles left-to-right, top-to-bottom as they appear on NTP. Recorded on click. dewittj@chromium.org Counts when the explore sites store is opened or closed. freedjm@chromium.org chrome-explore-team@google.com Tracks the result of image decoding for the favicons. dimich@chromium.org Number of unique hosts visited by the user during the last 30 days. Reported at most once a week for all users on Android only, with a 5 second delay after startup. This is different from History.MonthlyHostCount which is reported for a percentage of startups, to avoid bias toward more active users. chili@chromium.org dewittj@chromium.org Recorded every time a user navigates out of the explore sites page and comes back to it within 30 seconds on the same tab. This is used to measure accidental clicks, where we expect users who navigate to the wrong page will navigate back to the ExploreSites page immediately afterward. dimich@chromium.org freedjm@chromium.org Reported each time from the result callback of the ExploreSitesFetcher. Values include Success and several failure codes. 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. Removed in 06/2021. victorvianna@google.com jkrcal@chromium.org Records whether an icon already existed in the thumbnail DB when downloading an on-demand one. On-demand icons are the ones added to local cache without the user visiting the corresponding page. Removed in M88. mastiz@chromium.org Records the number of large icons that were fetched from the local cache (e.g. during NTP impression), where the URL (of the page or the icon) matches a hardcoded blacklist. Suspicious mismatches are reported as errors. jkrcal@chromium.org mastiz@chromium.org Records the size (concretely the width) in pixel of the favicon downloaded from Google favicon server (size 0 denotes that download has failed). jkrcal@chromium.org mastiz@chromium.org Records the size (concretely the width) in pixel of the favicon that is used to generate a fallback style in the case when large enough favicon is not available (size 0 denotes that no favicon is available at all). longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records whether users allow Google to contact them about the issues. Fires when feedback report is being sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record the length of description in the textbox. Fires when the feedback report is being sent. xiangdongkong@google.com cros-feedback-app@google.com Records the elapsed time from the start of fetching Debugd logs via the GetBigFeedbackLogs dbus method to when the data has been retrieved. Fires during the process of sending a feedback report on Chrome OS, or when the user previews the system logs from the feedback app on Chrome OS. GetBigFeedbackLogs is the dbus method used. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records a summary of the actions the user took before exiting the app. Fires when user closes the feedback app, case includes: User quits on search page after clicking some help contents; User quits on search page without clicking some help contents; User closes on search page because no help content is shown(Offline or Search is down); User closes on share data page after clicking help content; User closes on share data page without clicking help content; User submits feedback after clicking the help content; User submits feedback without clicking the help content. xiangdongkong@google.com cros-feedback-app@google.com Records the number of logs with empty data retrieved from debugd for feedback reports. Fires during the process of sending a feedback report on Chrome OS, or when the user previews the system logs from the feedback app on Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the number of logs with not available data retrieved from debugd for feedback reports. Fires during the process of sending a feedback report on Chrome OS, or when the user previews the system logs from the feedback app on Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the number of logs with data not empty or not available retrieved from debugd for feedback reports. Fires during the process of sending a feedback report on Chrome OS, or when the user previews the system logs from the feedback app on Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the success status of fetching the feedback logs via debus method GetBigFeedbackLogs. Fires during the process of sending a feedback report on Chrome OS, or when the user previews the system logs from the feedback app on Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the different results of fetching the feedback logs via debus method GetFeedbackLogsV2. Fires during the process of sending a feedback report on Chrome OS, or when the user previews the system logs from the feedback app on Chrome OS. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record the outcome of checking help contents. Fires when user leaves the search page by clicking continue or by clicking x on top right to close the app. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records the number of help content results returned in each search. Fires when user clicks and views the help content on search page. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records whether the email is included when the feedback report is submitted. Fires when user's feedback report is being sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records whether attached file is included when the feedback report is submitted. Fires when user's feedback report is being sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records whether the screenshot is included when the feedback report is submitted. Fires when a user's feedback report is successfully sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records whether the system and information is included when the feedback report is submitted. Fires when a user's feedback report is being sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records whether the page url is included when the feedback report is submitted. Fires when user's feedback report is being sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records the duration that the Feedback App is open. Emitted when the app is closed. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records the first action that the users take after sending feedback. Fires on the first action taken on post submit page after the user has sent the feedback. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Records the duration that the Feedback App is open on {FeedbackAppPage} page. Fires when the user closes the app or starts new report after feedback report has been sent. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record number of times the user viewed the help content. Fires when user clicks help content on search page. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record number of times the user viewed the attached image. Fires when user clicks the thumbnail and views the larger image. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record number of times the user viewed the metrics. Fires when user clicks metrics link and views metrics. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record number of times the user viewed the screenshot. Fires when user clicks the thumbnail on and views the larger screenshot. longbowei@google.com xiangdongkong@google.com cros-feedback-app@google.com Record number of times the user viewed the system and app information. Fires when system and app info link is clicked. xiangdongkong@google.com fernandex@google.com cros-feedback-app@google.com Records the elapsed time from the start of fetching system information to when the data has been retrieved. Fires during the process of sending a feedback report on Chrome (Desktop + Android) or Chrome OS. xiangdongkong@google.com fernandex@google.com cros-feedback-app@google.com Records the elapsed time from when the feedback app window is opened to when the backend receives the send report request submitted by a user. Fires during the process of sending a feedback report on Chrome (Desktop + Android) or Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the elapsed time from when the backend receives the send report request submitted by a user to when it starts to send confirmation back to the frontend. Fires during the process of sending a feedback report on Chrome or Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the elapsed time from when the backend receives the send report request submitted by a user and the report has been added to the send queue. Fires during the process of sending a feedback report on Chrome or Chrome OS. weili@chromium.org robliao@chromium.org Records how user interacts with Happiness Tracking Surveys (HaTS) bubble prompt which is shown for a subset of users. Each time when the bubble is shown, there should be one and only one enum type is recorded. sauski@google.com msramek@chromium.org Records the first reason why the Happiness Tracking Surveys (HaTS) bubble was or was not shown. While the request to show may not meet multiple criteria, the first criterion is reported here. nikj@google.com dpchromeos-core-eng@google.com Records how many times PIIs are redacted by the Client side log redaction tool. cschlosser@chromium.org dpchromeos-core-eng@google.com The redaction tool can be used to redact potential PII on the client side before logs and other data is sent to servers. This histogram is recorded when attempting to verify if a matched string is a credit card. Since we don't have guaranteed context for credit cards in our logs, unlike e.g. shill log format, we have to do apply some heuristic. There are several steps where the validation could detect a false positive and we want to measure how effective these mechanisms are. cschlosser@chromium.org dpchromeos-core-eng@google.com Records how many milliseconds elapsed while redacting the input text by the redaction_tool. This metric is recorded after each redaction (JS error or feedback report). This metric should be a rough control so we aren't running a very long time in the background after a report. cschlosser@chromium.org dpchromeos-core-eng@google.com Records how many milliseconds elapsed while redacting the logs of a crash inside ChromeOS's crash_reporter. This metric is recorded for each crash that has text logs that need redaction, at the time the crash happens. This metric should be a rough control so we aren't running a very long time after a crash and the user has to wait for the frozen screen to disappear. xiangdongkong@google.com cros-feedback-app@google.com Records whether the user is online when the feedback report was submitted. xiangdongkong@google.com cros-feedback-app@google.com Records the feedback report sending states to help track the success rate of feedback report offline submission. afakhry@chromium.org cros-telemetry@google.com Records the source that requested showing the feedback app. skrakowi@google.com chrome-counter-abuse-alerts@google.com Records the associated feature area when the Trust and Safety sentiment service detects that the user has performed a trigger action. This is recorded before the associated probability check and will be used to verify the infrastructure of newly integrated feature areas. We will remove this histogram once we verify the implementation. sauski@google.com chrome-hats-eng@google.com Records the associated feature area when the Trust and Safety Sentiment service requests a survey be shown from the HaTS service. sauski@google.com chrome-hats-eng@google.com Records the associated feature area when the Trust and Safety sentiment service detects that the user has performed a trigger action. This is recorded after the associated probability check. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request is either aborted, failed to load, or succeed to load in browser. mych@chromium.org chrome-bfcache@google.com Recorded true every time a new Fetch keepalive request is created by a browser. It does NOT equal to the total number of JavaScript Fetch keepalive call, as the latter can be immediately rejected with various JavaScript exceptions. This number should be compared with `FetchKeepAlive.Renderer.Total`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a FetchLater request loading is finished in browser. A finished loading can be either suceeded or failed. This number may be <= `FetchKeepAlive.Browser.Total.Started`, as a request may be dropped for other undocumented reasons like browser killed or crashes. Also, this number is ~= `kLoadingSuceeded` + `kLoadingFailed` in `FetchKeepAlive.Browser.Metrics`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request loader in browser has received a response. This number should be compared with `FetchKeepAlive.Renderer.Total.ReceivedResponse`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request loader in browser has received a redirect. This number should be compared with `FetchKeepAlive.Renderer.Total.Redirected`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a created Fetch keepalive request is started in the browser. This number should be the same as `FetchKeepAlive.Browser.Total`, but logging to figure out if any differneces exist. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request is either aborted or dropped in renderer. mych@chromium.org chrome-bfcache@google.com Recorded true every time a new FetchLater request is created by a renderer. It does NOT equal to the total number of JavaScript FetchLater API call, as the latter can be immediately rejected with various JavaScript exceptions. This metric is recorded to compare whether different behavior happens between renderer and browser. This number should be compared with `FetchKeepAlive.Browser.Total`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request loading is finished in a renderer process. A finished loading can be either suceeded or failed. This number may be <= `FetchKeepAlive.Renderer.Total.Started`, as a request may be dropped for other undocumented reasons like browser killed or crashes. Also, this number is <= `FetchKeepAlive.Browser.Total.Finished`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request loader in a renderer has received a response. This number should be compared with `FetchKeepAlive.Renderer.Total.ReceivedResponse`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a Fetch keepalive request loader in a renderer has received a redirect. This number should be compared with `FetchKeepAlive.Browser.Total.Redirected`. mych@chromium.org chrome-bfcache@google.com Recorded once every time a created Fetch keepalive request is started in a renderer process. This number may be <= `FetchKeepAlive.Renderer.Total`, as a created request may not be started at all. mych@chromium.org chrome-bfcache@google.com Records once every time a scheduled FetchLater request is either aborted or started in browser. mych@chromium.org chrome-bfcache@google.com Records true every time a new FetchLater request is scheduled by a browser. It does NOT equal to the total number of JavaScript FetchLater API call, as the latter can be immediately rejected with various JavaScript exceptions. This number should be compared with `FetchLater.Renderer.Total`, and it may be >= the sum of `FetchLater.Browser.Metrics`, as a request may be dropped for other undocumented reasons like browser killed or crashes. mych@chromium.org chrome-bfcache@google.com Records once every time a scheduled FetchLater request is started in browser. This number should be the sum of enum values "kStarted*" in `FetchLater.Browser.Metrics`. mych@chromium.org chrome-bfcache@google.com Records once every time a scheduled FetchLater request is either aborted or activated in renderer. mych@chromium.org chrome-bfcache@google.com Records true every time a new FetchLater request is scheduled by a renderer. It does NOT equal to the total number of JavaScript FetchLater API call, as the latter can be immediately rejected with various JavaScript exceptions. This metric is recorded to compare whether different behavior happens between renderer and browser. This number should be compared with `FetchLater.Browser.Total`, and it should be equal to the sum of `FetchLater.Renderer.Metrics`. shuuran@google.com kaustubhag@google.com Records initialization status of First-Party Sets database. Recorded when the database is lazily initialised when the first operation is encountered. shuuran@google.com kaustubhag@google.com Measures the outcome of site data clearing. Recorded when First-Party Sets initialization triggers site data clearing for a given browser context. shuuran@google.com kaustubhag@google.com Measures the length of time between when a navigation was deferred and then resumed due to timeout or First-Party Sets is ready. Recorded when a deferred navigation is resumed. shuuran@google.com kaustubhag@google.com Measures the deferred navigations that are resumed due to timeout. Recorded when a deferred navigation is resumed. ghendel@chromium.org pkl@chromium.org Track whether Firebase is enabled or not at app startup. jlebel@chromium.org olivierrobin@chromium.org Counts the number of times First Run experience was triggered by another application launching Chrome. This metric measures the effectiveness of Smart App Banner promotions on installation of Chrome. johntlee@chromium.org dpapad@chromium.org Records when a user interacted with the Google Apps new user experience. We record both accept and reject but are not recording when a user ignored the prompt completely. Users can ignore this prompt by closing the tab or navigating away, we record when the prompt is shown. Warning: this histogram was expired from M76 to M100; data may be missing. johntlee@chromium.org dpapad@chromium.org Records what Google apps were selected as part of the Google Apps New User Experience. Histogram is only recorded when a user accepts the prompt to add Google Apps. Warning: this histogram was expired from M76 to M100; data may be missing. scottchen@chromium.org Records when a user interacted with the landing page of the onboarding process. We record that the page was seen and what action the user took. johntlee@chromium.org dpapad@chromium.org Records when a user interacts with the NTP Backgrounds new user experience. We record the number of times the page is seen, how they interacted with the page (i.e. interacted with the options and buttons), and through what method they leave the page (i.e, confirm, cancel, neither). The new user experience should only be shown once to new profiles. johntlee@chromium.org dpapad@chromium.org Records the time taken to load a NTP background image for preview. This is recorded when a user clicks on a background to preview and the full-size version of the background finishes loading. johntlee@chromium.org dpapad@chromium.org Records when a user interacted with the set default page of the onboarding process. We record that the page was seen and what action the user took. johntlee@chromium.org dpapad@chromium.org Records when a user interacted with the sign in interstitial of the onboarding process. We record that the page was seen and what action the user took. Warning: this histogram was expired from M76 to M100; data may be missing. jlebel@chromium.org chrome-signin-team@google.com Records the result of an attempt to create the first run sentinel file. On iOS, file system errors are detailed further by the FirstRun.Sentinel.CreatedFileError histogram. jlebel@chromium.org chrome-signin-team@google.com File error when the sentinel file was not written. jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Result of the sign in flow during first run on iOS. tinazwang@chromium.org bling-get-started@google.com When Chrome is opened for the first time, the first run (onboarding) UI will be shown. Metircs will be recorded in different first run stages such as when first run experience is started, and when first run experience is completed. justincohen@chromium.org olivierrobin@chromium.org WARNING: The list of actions used to identify new tasks hasn't been attentively updated for several years (as of 2017). Some actions that should likely be considered new tasks are probably missing. Take this histogram with a grain of salt. Was expired for M85, M86. The amount of time (in seconds) that the app was in the background before the user started it justincohen@chromium.org olivierrobin@chromium.org WARNING: The list of actions used to identify new tasks hasn't been attentively updated for several years (as of 2017). Some actions that should likely be considered new tasks are probably missing. Take this histogram with a grain of salt. Was expired for M77-M86. On handsets, the type of the first user action performed after the app was started or unbackgrounded. justincohen@chromium.org olivierrobin@chromium.org WARNING: The list of actions used to identify new tasks hasn't been attentively updated for several years (as of 2017). Some actions that should likely be considered new tasks are probably missing. Take this histogram with a grain of salt. Was expired for M82-M86. On tablets, the type of the first user action performed after the app was started or unbackgrounded. drott@chromium.org etienneb@chromium.org Time to retrieve the fallback fonts on the system when not found in cache. drott@chromium.org etienneb@chromium.org The amount of font returned for a given font family. drott@chromium.org etienneb@chromium.org Time to retrieve the fallback fonts on the system. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org The number of duplicate fonts returned by system APIs. This is recorded when fonts are enumerated to be returned to script as a result of a call to the Font Access API. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org Records the number of font families observed by the font enumeration cache as part of the Font Access API. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org Records errors returned when obtaining the list of system fonts from DirectWrite's GetSystemFontCollection. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org Records the most frequent failure to obtain metadata for a font family when enumerating fonts as part of the Font Access API. Recorded in FontEnumerationCacheWin when all fonts have been enumerated. Values are Windows HRESULT error codes, and also includes custom values specific to this implementation. Removed in M86 in favor of Fonts.AccessAPI.EnumerationCache.DuplicateFontCount. oyiptong@chromium.org storage-dev@chromium.org The number of duplicate fonts returned by fontconfig. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org The number of fonts returned by fontconfig. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org The number of fonts whose name table entries could not be read. Removed in M95 oyiptong@chromium.org storage-dev@chromium.org Time spent enumerating fonts. Removed in M88. msalama@chromium.org msarda@chromium.org Tracks revoke actions taken by the account reconcilior to force Dice migration. To enforce consistency, the reconcilior may invalidate the primary account or revoke one or more secondary account tokens, if no equivalent valid gaia cookie exist for those accounts. droger@chromium.org msarda@chromium.org Reports the network error code for requests to the ListAccounts Gaia endpoint. msarda@chromium.org droger@chromium.org chrome-signin-team@google.com URLFetcher response codes for OAuth2AccessToken. Positive values are HTTP status codes, negative values are network error codes. Recorded on responses to OAuth access token requests. msarda@chromium.org droger@chromium.org chrome-signin-team@google.com Records the result of the Oauth2 access token request when a response is received from the LSO server except in net failure cases. In error cases, it records the error code in the response body. mattreynolds@chromium.org deviceapi-team@google.com Records an integer value that can be used to identify a connected gamepad device. The value is constructed from the 16-bit vendor ID in the high-order bytes and the 16-bit product ID in the low-order bytes, then cast to a 32-bit signed integer. The GamepadVendorProduct enum lists IDs for several popular gamepads but is incomplete. To identify a device not included in the enum, convert back to the vendor/product IDs and look up the human-friendly product name in go/gamepad-ids. This histogram records a new entry when a device with a vendor and product ID matching a known gaming input device is detected during Gamepad API enumeration. mattreynolds@chromium.org deviceapi-team@google.com Records an enumeration value identifying the active data fetcher when a fetcher enumerates a device that is not on the list of known gamepads, but is recognized as a gamepad by the fetcher. Please list the metric's owners. Add more owner tags as needed. Result of the authentication for Drive. jinsukkim@chromium.org clank-app-team@google.com Gesture navigation type. It can be either Chrome's own gesture UI that supports back and forward navigation or OS-provided default system gesture navigation that supports only back action on both left and right edge. This is recorded on Chrome startup at the feature component initialization. ckitagawa@chromium.org meiliang@chromium.org This histogram records the frame rate of the transition animation between Tab and Grid Tab Switcher. ckitagawa@chromium.org meiliang@chromium.org This histogram records the maximum interval between rendered frames during the transition animation between Tab and Grid Tab Switcher. Expired 2021-02-14 replaced superceded by Android.GridTabSwitcher.ThumbnailFetchingResult. yusufo@chromium.org wychen@chromium.org This histogram records the result of thumbnail fetching in the Grid Tab Switcher. zhiyuancai@chromium.org wychen@chromium.org ayman@chromium.org Records why the {MessageType} is disabled in GridTabSwitcher and will no longer be shown to users. Recorded when the message is disabled. Implemented for Android. zmo@chromium.org graphics-dev@chromium.org Records the system hardware concurrency collected in the info collection GPU process, once per UMA ping. For most systems, it is equivalent to the number of CPU cores. sashamcintosh@chromium.org chromeos-gfx@chromium.org The number of displays present right after the user has attached or detached a new display. Excludes mirrored displays, but includes sleeping displays. sashamcintosh@chromium.org chromeos-gfx@chromium.org The number of displays present at start up. Excludes mirrored displays, but includes sleeping displays. cassew@google.com media-dev-uma@chromium.org Whether a given display device supports HDR (such that the CSS media query `dynamic-range: high` would resolve as true). Recorded upon browser startup (for every connected display), upon display device connection (for the newly connected display), and upon any change to the color space metric (for the affected display). zmo@chromium.org graphics-dev@chromium.org Records a rough estimation of the system total disk space collected in the info collection GPU process, once per UMA ping. Removed in M96. rsorokin@chromium.org cros-oac@google.com Which HID were detected when user pressed Continue on OOBE dialog. This metric is specific to Chrome OS. Removed in M96. rsorokin@chromium.org cros-oac@google.com Whether HID detection dialog was shown on OOBE. Logged on screen show or on screen skip respectively. This metric is specific to Chrome OS. Removed in M97. rsorokin@chromium.org alemate@chromium.org cros-oac@google.com Records number of times the dialog was shown by the time OOBE is completed. This metric is specific to Chrome OS. Removed in Nov 2022. alancutter@chromium.org src/chrome/browser/ui/page_action/OWNERS Counts which content setting buttons in the hosted app frame are pressed by the user. chingkang@chromium.org cros-hwsec-userland-eng+uma@google.com The duration of preparation for enrollment in attestation. chingkang@chromium.org cros-hwsec-userland-eng+uma@google.com The result of attestation-related operations on the Chrome OS side. kojii@chromium.org layout-dev@chromium.org The time it takes to open a hyphenation dictionary. kojii@chromium.org layout-dev@chromium.org The time it takes to open a hyphenation dictionary file. gcomanici@chromium.org The size of the history on Auto Import from IE. This measure is only logged on a succesfull Auto Import. robliao@chromium.org gab@chromium.org The importer used on first run Auto Import. Warning: This histogram was expired from 2018-09 to 2023-07; data may be missing. robliao@chromium.org gab@chromium.org The importer used on import from the bookmarks file API. Warning: This histogram was expired from M77 to M117; data may be missing. robliao@chromium.org gab@chromium.org The importer used on import from the chrome://settings/importData UI. Warning: This histogram was expired from 2018-09 to 2023-07; data may be missing. brucedawson@chromium.org grt@chromium.org The number of retries needed to successfully move the temporary file to its final location. Zero means that ReplaceFile worked the first time. Ten means that it never succeeded. battre@chromium.org gab@chromium.org CPU time used in the foreground thread (usually UI thread) to serialize the data to be written into an important file (e.g. serialize JSON string for preferences). For users of ImportantFileWriter that leverage background serialization (e.g. bookmarks), it excludes the time spent on the background thread, and only logs the time spent on the foreground thread. wylieb@chromium.org chrome-collections@google.com CPU time used in the background thread to write serialized data into an important file. Recorded when the file is written. roagarwal@chromium.org chrome-incognito@google.com Records the action taken by the user on the Incognito clear browsing data dialog. Removed in http://crrev.com/747875. robliao@chromium.org The thread used to initialize the Windows parental controls. Removed in http://crrev.com/747875. 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. peter@chromium.org Status code of the outcome of DeleteToken request. jianli@chromium.org Length of time taken to complete the GetToken request successfully. If the request is retried multiple times, the length of time is counted for the last successful retry. peter@chromium.org platform-capabilities@chromium.org Net error code from an Instance ID GetToken attempt. Recorded when URL loading completes. Deprecated as of 11/2020 peter@chromium.org knollr@chromium.org The number of options provided to the GetToken request. Recorded when the request has been received by the InstanceID instance. peter@chromium.org rushans@chromium.org Status code of the outcome of GetToken request. Warning: this histogram was expired from 2023-08-06 to 2023-09-22; data may be missing. peter@chromium.org rushans@chromium.org treib@chromium.org Status code of the outcome of GetToken request for FCM invalidations (subtype was "com.google.chrome.fcm.invalidations"). peter@chromium.org rushans@chromium.org treib@chromium.org Status code of the outcome of GetToken request for Sync invalidations (subtype was "com.google.chrome.sync.invalidations"). 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. Removed 2020 November. avi@chromium.org For onbeforeunload dialogs, the user's choice between staying on the page and leaving it. asvitkine@chromium.org ntfschr@chromium.org Logs which Chrome flags from about:flags were active on start up. Android WebView supports flags differently than most platforms, see https://chromium.googlesource.com/chromium/src/+/HEAD/android_webview/docs/developer-ui.md for details. calamity@chromium.org davidbienvenu@chromium.org grt@chromium.org The different ways Chrome is launched. This replaces Launch.Modes. Emitted once at startup, when the user launches Chrome to browse the web or launch a Web App. It is not recorded if Chrome is launched in other ways: by the installer, after an update, after a flag change, after an OS update, to install/uninstall/list apps, or in background mode. calamity@chromium.org grt@chromium.org The different ways Chrome is launched. This metric is gradually being replaced with an improved version. See tracking bug http://crbug.com/1366137 Warnings about this version of this metric. 1. If user starts Chrome while Chrome is already running, this reports incorrect data. See http://crbug.com/1067205 2. On ChromeOS, if a user session-restores multiple profiles, each profile records this metric. See http://crbug.com/1356222 3. When the profile picker is shown on startup (which can only happen on Windows, Mac, and Linux), this metric is not recorded. See http://crbug.com/1380458 Removed in M86. 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. Removed in M86. 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. Removed in M86. 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. Removed in M86. 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. Removed in M86. 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. Removed in M86. 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. Removed in M89. skobes@chromium.org Records the number of times ScrollAnchor adjusts the scroll offset. Removed in M89. 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. Removed in M89. 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. Removed in M93. 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. Replaced with Lens.ImageClassification.ClassificationTime.SuccessOnQueryResultMs as of 12/2020. yusuyoutube@google.com benwgold@google.com Logged the end to end latency of the Lens image classifcation call when the user completes a long press on an image. Only logged on Android. yusuyoutube@google.com benwgold@google.com Logged the time between the start of the Lens image classifcation call to the early termination before the call completes. Only logged on Android. yusuyoutube@google.com benwgold@google.com Logged the end to end latency of the Lens image classifcation call when the user completes a long press on an image. Only logged on Android. yusuyoutube@google.com benwgold@google.com Logged the result state of the Lens image classifcation call when the user completes a long press on an image. Only logged on Android. yusuyoutube@google.com benwgold@google.com Logged the error code when there is a Lens SDK error occurred within the classification session. The error code is an integer constant defined by the SDK. Only logged on Android. See http://b/170422682 for more details. yusuyoutube@google.com benwgold@google.com fgorski@chromium.org wylieb@chromium.org lens-chrome@google.com Whether the user supports the camera assisted search with Google Lens and if not, the reason why. Recorded only if the feature is enabled when the omnibox or the new tab page is loaded. benwgold@chromium.org yusuyoutube@google.com lens-chrome@google.com Whether the user supports the camera assisted search with Google Lens and if not, the reason why. Recorded only when the Lens button is tapped on the Quick Action Search Widget. Note: Gap between 04/22 - 08/23. chengx@chromium.org This metric records the LoadLibraryExW and LoadLibraryW Windows API call results, which are used in native_library_win.cc. lizeb@chromium.org Percentage of the native library code pages resident in memory. Recorded immediately before the library prefetching kicks in, only on Android. thestig@chromium.org thomasanderson@chromium.org The Debian version number (eg. 8: Jessie, 9: Stretch). Logged once on startup if Linux.Distro3 is Debian. thestig@chromium.org thomasanderson@chromium.org The Fedora version number (eg. 27, 28) Logged once on startup if Linux.Distro3 is Fedora. thestig@chromium.org thomasanderson@chromium.org The Linux Mint version number (eg. 20, 20.1) Logged once on startup if Linux.Distro3 is Mint. thestig@chromium.org thomasanderson@chromium.org The openSUSE Leap version number, logged as 1000*major + minor (eg. 15001 = 15.1). Logged once on startup if Linux.Distro3 is openSUSE Leap. thestig@chromium.org thomasanderson@chromium.org The Ubuntu version number, logged as 1000*year + month (eg. 16004 = 16.04 Xenial). Logged once on startup if Linux.Distro3 is Ubuntu. thestig@chromium.org thomasanderson@chromium.org The Linux distro used. Logged on each start up. thestig@chromium.org thomasanderson@chromium.org The version of glibc used. (Linux only) Logged on each start up. kylechar@chromium.org mpdenton@chromium.org The time taken for localtime_r() call to proxied from a sandboxed process to the browser and a response returned back in microseconds. This histogram is only recorded on Linux, where all users have high-resolution clocks. mpdenton@google.com src/sandbox/linux/OWNERS The Linux sandbox status. This describes what sandboxing features are enabled (such as the suid/namespace sandboxes, various namespaces, seccomp bpf, ...). Emitted once at startup. thomasanderson@chromium.org thestig@chromium.org The default system theme. Logged once on startup. thomasanderson@chromium.org thestig@chromium.org The per-profile system theme. Logged once for each profile on startup, and whenever the system theme changes. fangzhoug@chromium.org adunaev@igalia.com graphics-dev@chromium.org The Linux Wayland base shell protocol used actually. Logged in each session when the browser creates the first shell surface. fangzhoug@chromium.org adunaev@igalia.com graphics-dev@chromium.org The Linux Wayland shell protocol(s) available. Logged in each session when the compositor announces a Wayland protocol extension that provides the desktop shell functionality (i.e., turns abstract surfaces into windows that can be positioned, moved, resized, etc., depending on the particular shell). pkotwicz@chromium.org thomasanderson@chromium.org The window manager used. (Linux only) Logged on each start up. sophiechang@chromium.org tbansal@chromium.org spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload The status of when the optimization hints were received by the Loading Predictor. This will be recorded on navigations for which predictions from the Optimization Guide were received. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload 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. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload 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. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload When the loading predictor has origins in the local database for a given navigation to preconnect and preresolve, the count of predicted origins. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload 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}. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload 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}. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload 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. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload 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. spelchat@chromium.org chrome-brapp-loading@chromium.org Internals>Preload The percentage of hosts that were preresolved and requested by a page load to the total number of hosts that were preresolved for a page load. Logged after the preconnect manager completes all jobs attached to the page load. tbansal@chromium.org Original Blink priority of the request that belongs to an iframe. Recorded for every request fetched via Blink, but only when the experiment to lower the priority of iframes is enabled. tbansal@chromium.org Original Blink priority of the request that belongs to the main frame. Recorded for every request fetched via Blink, but only when the experiment to lower the priority of iframes is enabled. nasims@google.com dimich@chromium.org Whether the user successfully shared via a native sharing extension after selecting it from the File > Share menu. False can indicate failure or user-initiated cancellation. mek@chromium.org src/base/mac/OWNERS The result of calls to base::mac::LaunchApplication, logged once for every invocation of that method. Removed 2021 November. avi@chromium.org mark@chromium.org Native macOS apps can claim regions of the URL space for themselves, and so on every navigation, Chromium calls the SFUniversalLink API to determine if the URL being navigated to requires special handling. The SFUniversalLink API is usually instantaneous, but for some machines it's very slow. This metric logs the amount of time that it the SFUniversalLink API took to run, if over 100ms. This metric is logged once per run of Chrome, because if that API call ever takes longer than 100ms, it is disabled and never used again in that run of Chrome. mgiuca@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. phillis@chromium.org desktop-pwas-team@chromium.org Tracks the result of parsing id field in the Manifest. akhouderchah@chromium.org benchan@chromium.org The result (e.g. success or the type of failure) of a modem interface switch operation performed by mist on Chrome OS. carlosil@chromium.org The net error or HTTP response code of a mixed content resource request that was autoupgraded to HTTPS. This histogram was expired from M80 to M108. carlosil@chromium.org Whether or not an autoupgrade mixed content request was for a resource we know to be an ad. This histogram was expired from M80 to M108. carlosil@chromium.org estark@chromium.org Logs the type of each resource request that is autoupgraded to HTTPS and fails to load. This histogram was expired from M80 to M108. Warning: an unexpected reorder happened in Apr 2021 (https://crrev.com/c/2798954). Please do not trust older reports. carlosil@chromium.org estark@chromium.org Logs the type of each resource request that was autoupgraded to HTTPS and resulted in a response. This histogram was expired from M80 to M108. Warning: an unexpected reorder happened in Apr 2021 (https://crrev.com/c/2798954). Please do not trust older reports. carlosil@chromium.org estark@chromium.org Logs the type of each resource request that is autoupgraded to HTTPS. This is logged when the request is started. This histogram was expired from M80 to M108. Warning: an unexpected reorder happened in Apr 2021 (https://crrev.com/c/2798954). Please do not trust older reports. carlosil@chromium.org The status of a mixed content resource request that was autoupgraded to HTTPS. This histogram was expired from M80 to M108. Removed in M87. grt@chromium.org Logged when the relocations in a module are not ordered causing the module verification to abort. amistry@chromium.org bgeffon@chromium.org rockot@google.com Measures the time taken to fully write a channel message to the underlying channel. amistry@chromium.org bgeffon@chromium.org rockot@google.com The size of a message written to a channel. amistry@chromium.org bgeffon@chromium.org rockot@google.com Tracks whether or not a message is written directly to a channel or queued. amistry@chromium.org bgeffon@chromium.org rockot@google.com The number queued messages waiting to be written, measured when a channel flush is attempted. amanvr@chromium.org carlscab@chromium.org woa-performance@google.com Records the number of received Mojo IPCs, split per process. Emitted each time a mojo IPC is received. amanvr@chromium.org carlscab@chromium.org woa-performance@google.com Records the number of sent Mojo IPCs, split per process. Emitted each time a mojo IPC is sent. siggi@chromium.org rockot@chromium.org The maximal unread message quota used for the lifetime of a Connector. This is sampled for a configurable percentage of Connectors only when the feature MojoRecordUnreadMessageCount is enabled. By default 1% of Connectors are sampled, as there's some overhead involved in enabling the unread message quota on a MessagePipe. See //mojo/public/cpp/bindings/lib/connector.cc. rsesek@chromium.org chrome-mojo@google.com Emitted any time a Mojo string is deserialized and is not valid UTF-8. zentaro@chromium.org cros-peripherals@google.com Tracks mouse sensitivity setting changes by the user. This replaces the old Mouse.Sensitivity.Changed metric. Only reported on Chrome OS. dpad@google.com cros-peripherals@google.com Tracks mouse sensitivity setting on startup. This replaces the old Mouse.Sensitivity.Started metric. Only reported on Chrome OS. Expired from 2022-12-04 to M113. May be missing some data. khorimoto@chromium.org zentaro@chromium.org Whether mouse scroll acceleration is enabled. Only reported on Chrome OS. zentaro@chromium.org cros-peripherals@google.com Mouse scroll sensitivity value. Only reported on Chrome OS. Warning: this histogram was expired from 2020-12-01 to M105; data may be missing. pasko@chromium.org yfriedman@chromium.org The time it takes to spawn the first child subprocess (including sandbox init). pasko@chromium.org yfriedman@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. Please list the metric's owners. Add more owner tags as needed. TBD Removed in M98. Replaced by Browser.Tabs.TotalSwitchDuration.* jbauman@chromium.org Time from tab switch requested to tab appearing on screen (Aura and Mac only). skuhne@chromium.org Count the number of times each UI path is taken for switching the active account in a Chrome OS multiprofile session. UI paths include the system tray and the keyboard shortcut. skuhne@chromium.org antrim@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. Warning: this histogram was expired from 2022-04-10 till 2023-07-10. simmonsjosh@google.com src/chrome/browser/ash/smb_client/OWNERS The method used to authenticate to a share. This is called on each attempted mount. simmonsjosh@google.com src/chrome/browser/ash/smb_client/OWNERS The result of the GetShares operation for Native SMB File Share. This is recorded after the D-Bus call to GetShares returns. simmonsjosh@google.com src/chrome/browser/ash/smb_client/OWNERS The number of active mounts that a user has. This is recorded after a share has been successfully mounted. simmonsjosh@google.com src/chrome/browser/ash/smb_client/OWNERS The result of the mount operation for Native SMB File Share. This is recorded after the D-Bus call to Mount returns. Removed in M87. No longer used with smbfs. zentaro@chromium.org The number of entries read when calling ReadDirectory. This is recorded after the D-Bus call to ReadDirectory returns. Removed in M87. No longer used with smbfs. zentaro@chromium.org The duration of ReadDirectory call to SmbProvider in milliseconds. This is recorded after the D-Bus call returns. Removed in M94. simmonsjosh@google.com src/chrome/browser/ash/smb_client/OWNERS The result of the Remount operation during startup. This is recorded after the D-Bus call to Remount returns. Deprecated in 10/2021 because the location permission protected API is required to get this information and this isn't a must-have histogram. tbansal@chromium.org bengr@google.com The MCC (mobile country code) and MNC (mobile network code) of the network operator when a new metrics log is created or when the network connection is changed. A value of zero means a non-mobile network or the operator code is unknown. tbansal@chromium.org bengr@chromium.org Number of times the network quality prefs were read by the network quality estimator. tbansal@chromium.org bengr@chromium.org Count of the number of network IDs in the prefs read by the network quality estimator. tbansal@chromium.org bengr@chromium.org Number of times the network quality prefs were written by the network quality estimator. tbansal@chromium.org bengr@chromium.org Number of RTT observations indexed by the source of the observation. Recorded by the network quality estimator every time a new observation is made or synthesized. bengr@chromium.org tbansal@chromium.org Rough estimate of the round trip time at the URLRequest layer. Recorded by the network quality estimator every time the effective connection type is computed. anastasiian@chromium.org sinhak@chromium.org Outcome of Chrome OS GAIA cookie session restore process. anastasiian@chromium.org sinhak@chromium.org How long it takes for the session restore to fail. anastasiian@chromium.org sinhak@chromium.org How long it takes for the session restore to finish successfully. Retired in M99. davidbienvenu@chromium.org fdoray@chromium.org Incremented each time a mouse event is handled by a window that is marked as occluded. This number should be 0 or very close to 0. It should be much less than the number of times a window is mark occluded - WindowOcclusionChanged.Occluded. Retired in M93, replaced by OffscreenCanvas.TextMetrics.SetFont2 which has a wider range. yiyix@chromium.org fserb@chromium.org Time spent in microseconds to perform call SetFont in canvas for OffscreenCanvas. It's measured each time SetFont is called. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. Retired in M94. yiyix@chromium.org fserb@chromium.org Time spent in microseconds to perform call SetFont in canvas for OffscreenCanvas. It's measured each time SetFont is called. This differs from OffscreenCanvas.TextMetrics.SetFont in that it uses buckets up to ten seconds rather than ten milliseconds (due to a change in the underlying histogramming function called). Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. pbirk@chromium.org src/components/origin_trials/OWNERS Reports whether the presence of a Critical-Origin-Trial header caused a network request restart due to the origin trial not being enabled. The Critical-Origin-Trial header is only processed for navigation requests (loading either a main- or sub-frame) using a safe HTTP verb (per section 4.2.1 of RFC 7231). On those requests, this metric will be emitted if the Critical-Origin-Trial header is present on the response, to report the decision made by the CriticalOriginTrialThrottle. The request may still be restarted due to other throttles, even if this metric reported "false". pbirk@chromium.org src/components/origin_trials/OWNERS Reports status of LevelDB initialization for persistent origin trials. This is emitted on the Init callback during browser startup, and should not be false. A high rate of "false" would indicate a problem with the shared LevelDB database. pbirk@chromium.org src/components/origin_trials/OWNERS Counts the number of origins in the LevelDb database at time of load during browser startup. This metric is for reporting only, and expected to get worse if you are in the process of launching a persistent origin trial. pbirk@chromium.org src/components/origin_trials/OWNERS Reports status of LevelDB load for persistent origin trials. This is emitted on the Load callback during browser startup, and should not be false. A high rate of "false" would indicate a problem with the shared LevelDB database. pbirk@chromium.org src/components/origin_trials/OWNERS Measures the time to load the data from LevelDb during startup in wall clock time. This metric is for reporting only, and expected to get worse if you are in the process of launching a persistent origin trial. pbirk@chromium.org src/components/origin_trials/OWNERS Counts the number of lookups for origins arriving to the LevelDbPersistenceProvider before the database was loaded from disk. Any such lookup would not have seen the persisted value. Since the database is loaded asynchronously, it is possible for the browser to start using the PersistentOriginTrial component before it is fully loaded. Due to this, it is expected to see this metric at 1, possibly 2. Large numbers can be caused by a browser restart with a lot of saved tabs being loaded at the same time. pbirk@chromium.org src/components/origin_trials/OWNERS Counts the number of origins added to the LevelDbPersistenceProvider before the persited origins have loaded from disk. This number represents the number of page loads for pages enrolled in persistent origin trials where the trial was either not activated or the request had to restart due to the presence of the Persistent-Origin-Trial header. pbirk@chromium.org src/components/origin_trials/OWNERS Reports the number of partitions a persistent origin trial token has been stored against. The purpose of the metric is to uncover memory footprint issues from storing site partitions, and to help decide if an eviction strategy needs to be put in place. This metric is recorded once for every stored origin trial token on browser startup. pbirk@chromium.org src/components/origin_trials/OWNERS Records whether a stored partition token has its own origins eTLD+1 as one of the partitions. This is being recorded to determine if space can be saved by making the first-party partition a special case. This metric is recorded on browser startup when the persisted tokens are loaded from the database. chasej@chromium.org iclelland@chromium.org feature-control@chromium.org Counts the results of token validation checks to enable experimental features. The result for each token validation check is counted once per token per execution context (e.g. page, worker). wfh@chromium.org nparker@chromium.org The result code of the application-bound Decrypt operation. This is logged once during browser startup on a background thread for system-level installs on Windows only. wfh@chromium.org nparker@chromium.org The GetLastError code for a failed application-bound Decrypt operation. This is logged once during browser startup on a background thread for system-level installs on Windows only, if the call to Decrypt failed. wfh@chromium.org nparker@chromium.org The amount of time, in ms, that it takes to perform an application-bound Decrypt call. This is logged once during browser startup on a background thread for system-level installs on Windows only. wfh@chromium.org nparker@chromium.org The result code of the application-bound Encrypt operation. This is logged once during browser startup on a background thread for system-level installs on Windows only, for a client that is initializing a new local state or a previously failing client. wfh@chromium.org nparker@chromium.org The GetLastError code for a failed application-bound Encrypt operation. This is logged once during browser startup on a background thread for system-level installs on Windows only, if the call to Encrypt failed, for a client that is initializing a new local state or a previously failing client. wfh@chromium.org nparker@chromium.org The amount of time, in ms, that it takes to perform an application-bound Encrypt call. This is logged once during browser startup on a background thread for system-level installs on Windows only, for a client that is initializing a new local state or a previously failing client. cfroussios@chromium.org mamir@chromium.org The backend selected for this user and whether it was initialised successfully. cfroussios@chromium.org thestig@chromium.org True, iff the data was not decryptable with the stored encryption key, but was decryptable with a key generated from an empty string. This is emitted every time OSCrypt attempts to decrypt a value. wfh@chromium.org nparker@chromium.org Whether or not the DPAPI Decrypt call to decrypt the OSCrypt key succeeeded. This is logged once during browser startup on Windows. wfh@chromium.org nparker@chromium.org The amount of time, in ms, that it takes to perform a DPAPI Decrypt call. This is logged once during browser startup on Windows. wfh@chromium.org nparker@chromium.org Whether or not the DPAPI Encrypt call to encrypt the OSCrypt key succeeeded. This is logged once during browser startup on Windows, if there is no stored key and a new one has to be generated. This data will therefore be biased towards newer clients. See OSCrypt.Win.Decrypt.Result which contains unbiased data. wfh@chromium.org nparker@chromium.org The amount of time, in ms, that it takes to perform a DPAPI Encrypt call. This is logged once during browser startup on Windows, if there is no stored key and a new one has to be generated. This data will therefore be biased towards newer clients. See OSCrypt.Win.Decrypt.Time which contains unbiased data. wfh@chromium.org forshaw@chromium.org The Windows GetLastError after a failure from calling into DPAPI to decrypt the master key for the os_crypt library on Windows. This is recorded during the OSCrypt::Init each time the decryption fails. mark@chromium.org Events seen by the OSX NSException swizzle. spqchan@chromium.org This event is recorded each time a user triggers fullscreen for a browser window. It indicates if the fullscreen is triggered for the browser or the tab content. erikchen@chromium.org This event is recorded each time a user triggers fullscreen for a browser window. It indicates the mechanism (immersive vs. AppKit) and the type of AppKit Fullscreen (Presentation Mode vs. Canonical Fullscreen). erikchen@chromium.org This event is recorded each time a user triggers fullscreen for a browser window. It indicates the screen in which the window was fullscreened, and the number of screens available. erikchen@chromium.org This event is recorded each time a Handoff is received by Chrome on OSX. The enumeration indicates the source of the Handoff. Removed 11/2020. avi@chromium.org mark@chromium.org The instances of other copies of Google Chrome on the user's Mac. Logged once on startup, and only for Chrome Beta and Chrome Dev. Will be used to determine if/how home directory migration will be done for side-by-side. Removed July 2021, superceded by Mac.FileMenuNativeShare. lgrey@chromium.org Whether the user successfully shared via a native sharing extension after selecting it from the File > Share menu. False can indicate failure or user-initiated cancellation. This is obsolete; the same data is currently being collected as Mac.FileMenuNativeShare. erikchen@chromium.org The configuration of the setting "Screens Have Separate Spaces" available in OSX 10.9+. erikchen@chromium.org Whether an attempt to load the system hotkeys on a Mac was successful. napper@chromium.org robsc@chromium.org When a stylus is touched to screen, the number of palms on the device at that time. robsc@chromium.org The count of the number of held events cancelled when we decide to finally cancel a stroke. Only reported if events have been held, and will be positive. Events are only held from PalmDetectionFilter. robsc@chromium.org The count of the number of held events released at once for a stroke when we decide to release. Only reported if events have been held, and will be positive. Events are only held from PalmDetectionFilter. jiwan@chromium.org robsc@chromium.org The count of the number of detected palm touches. Reported when a new palm touch is detected by either the firmware or the software palm detection. Consecutive palm touch events will be considered as the same palm touch. jiwan@chromium.org robsc@chromium.org Whether a repeated touch is detected soon after palm rejection. Reported when users repeated a touch action within 2 seconds after we rejected the first action as palm. This only emits true when we detect a repeated touch but never emits false. jiwan@chromium.org robsc@chromium.org The count of the number of stylus sessions. A stylus session is a series of stylus events with no more than 5 seconds between them. Reported when a stylus session is concluded. jiwan@chromium.org robsc@chromium.org The length of stylus sessions. A stylus session is a series of stylus events with no more than 5 seconds between them. Reported when a stylus session is concluded. jiwan@chromium.org robsc@chromium.org The time between a stylus touch and the first finger touch after it. The finger touch may or may not be detected as a palm. If the first touch after a stylus touch is another stylus touch (i.e. no finger touch between them), record a maximum time (10 seconds) instead. Reported when first new touch is reported after a stylus touch finishes. jiwan@chromium.org robsc@chromium.org The time between a stylus touch and the last finger touch before it. The finger touch may or may not still be on the touchscreen, and may or may not be detected as a palm. Reported when a stylus touch is started on the touchscreen. jiwan@chromium.org robsc@chromium.org The count of the number of touch sessions. A touch session is a series of touch events with no more than 5 seconds between them. Reported when a touch session is concluded. jiwan@chromium.org robsc@chromium.org The length of touch sessions. A touch session is a series of touch events with no more than 5 seconds between them. Reported when a touch session is concluded. jiwan@chromium.org robsc@chromium.org The type of the first finger touch within 500ms before a stylus touch. It could be finger, palm or none (no touch within 500ms). Reported when a stylus touch is started on the touchscreen. jiwan@chromium.org robsc@chromium.org The type of the last finger touch within 500ms before a stylus touch. It could be finger, palm or none (no touch within 500ms). Reported when first new touch is reported after a stylus touch finishes. ahassani@chromium.org chromeos-core-services@google.com The number of currently connected HTTP clients. This is reported every time a HTTP client connects. ahassani@chromium.org chromeos-core-services@google.com Number of megabytes (1,000,000 bytes) served from the device (via HTTP) where the client disconnects prematurely. This is reported every time a file is served and the client disconnects before receiving all data. ahassani@chromium.org chromeos-core-services@google.com The number of files available via p2p. This is reported every time a file is added or removed to the /var/cache/p2p directory. sophiechang@chromium.org chrome-journeys@google.com Internals>OptimizationGuide Records the result of requests to the Optimization Guide Salient Images backend. Recorded for each request to Optimization Guide, so the total count of this UMA should match that bucket count in PageImageService.Backend. tommycli@chromium.org chrome-journeys@google.com UI>Browser>Journeys Records the result of requests to the Suggest backend. Recorded for each request to Suggest, so the total count of this UMA should match that bucket count in PageImageService.Backend. tommycli@chromium.org chrome-journeys@google.com UI>Browser>Journeys Records the backend chosen for the request. For requests with no valid backend, this is still recorded as the "No Valid Backend" bucket. Only recorded for requests that have passed the URL consent gate. tommycli@chromium.org chrome-journeys@google.com UI>Browser>Journeys Records the result of the URL consent check after timeout has expired. Recorded for each request which was enqueued by the time when timeout happened. tommycli@chromium.org chrome-journeys@google.com UI>Browser>Journeys Recorded on each URL consent check request. This metric is used to compare numbers with consent check result in PageImageService.ConsentStatus. tommycli@chromium.org chrome-journeys@google.com UI>Browser>Journeys Records the result of the URL consent check for this request. The number of consent check requests is recorded in PageImageService.ConsentStatusRequestCount. Note that only success and failure are captured if the "old" unified consent throttle is used. pdr@chromium.org paint-dev@chromium.org Records the reason that a commit was triggered, to enable research into which event (non-same-origin, FCP, timeout, etc) led to the first commit. pdr@chromium.org paint-dev@chromium.org Records whether or not input arrived before the first paint. bttk@chromium.org wychen@chromium.org The time spent on loading partner bookmarks, from kickOffReading() to bookmarkModelLoaded() callback. mych@chromium.org pending-beacon-experiment@chromium.org Warning: this histogram was expired from M113 to M115; data may be missing. The type of PendingBeacon-related action that the browser has performed. This is only recorded when the PendingBeacon API is called to create, send, or cancel a beacon. See https://chromium.googlesource.com/chromium/src/+/main/docs/experiments/pending-beacon.md and https://crrev.com/c/4028260 for more details. mych@chromium.org pending-beacon-experiment@chromium.org Warning: this histogram was expired from M113 to M115; data may be missing. The type of batch PendingBeacon-related action that the browser has performed. A batch action means the browser is about to batch process all queued pending beacon requests at once. See https://chromium.googlesource.com/chromium/src/+/main/docs/experiments/pending-beacon.md and https://crrev.com/c/4028260 for more details. jbauman@chromium.org True if a non-flash Pepper Graphics3D context has a share group. fabiansommer@chromium.org dschuff@chromium.org The number of out-of-process plugin processes that have loaded a particular PPB interface version. raymes@chromium.org rsleevi@chromium.org Whether a Pepper TCP connect attempt comes from a plugin in a secure or an insecure origin. raymes@chromium.org rsleevi@chromium.org Whether a Pepper UDP bind attempt comes from a plugin in a secure or an insecure origin. nator@chromium.org rayankans@chromium.org Records the number of `periodicsync` events which were fired in a batch. A batch is defined as the set of `periodicsync` events dispatched at the same time by the BackgroundSyncManager. Periodic syncs usually run in a batch. nator@chromium.org rayankans@chromium.org Records whether the fired `periodicsync` events upon completion orginated from a background wakeup task or the foreground. nator@chromium.org rayankans@chromium.org Time taken to execute a batch of periodicsync events. A batch is defined as the set of `periodicsync` events dispatched at the same time by the BackgroundSyncManager. Periodic syncs often run in a batch. fbeaufort@chromium.org media-dev-uma@chromium.org Records Picture-in-Picture window control buttons pressed by user (basically everything except user tap gestures). fbeaufort@chromium.org media-dev-uma@chromium.org Records Picture-in-Picture window control user tap gestures. Replaced by PLT.iOS.BrowserInitiatedPageLoadTime2 as of M92, in order to use more granular buckets above 10 seconds. djean@chromium.org ajuma@chromium.org Page load time for Browser-initiated navigations. Browser-initiated navigations include all navigations initiated by interacting with Chrome's UI elements, except for back/forward navigations. Specifically, typing a URL into the omnibox, tapping the reload button, loading a bookmark, and loading a page from the reading list (including when offline) are all considered browser-initiated. Additionally, background loads for prerendering and reading-list offline sync are also browser-initiated, as is a reload triggered by switching to a tab whose WKWebView renderer process was killed by the OS. This is recorded for successful main-frame navigations (that is, navigations that don't result in the browser displaying an error page). The recorded value measures the time from the navigation request being sent to the renderer process until all frames have fired their load events. For background loads, the same interval is measured while the page loads and fires load events in the background; the metric is not recorded again if the background-loaed page is later displayed in the foreground. Page loads that require network fetches will be slower than those where all necessary resources are already present in WebKit's HTTP cache. Reload navigations where all cached resources are up-to-date are particularly fast, since they don't require any rendering updates either. It is possible for a user to interact with a page before all load events have been fired, so the recorded value should not be interpreted as the time before the page becomes interactive. Most things that affect user-perceived page load time on iOS are within WebKit, not within Chromium/Chrome code. To assess whether a change in this metric is caused by a WebKit change, split by OS version. WebKit changes always come with an OS version change. Obviously, aside from WebKit and Chromium changes, this metric can move due to exogenous factors such as changes in what type of web page people are looking at or changes in the implementation of popular websites. Any navigation that is not considered browser-initiated is considered to be renderer-initiated (see PLT.iOS.RendererInitiatedPageLoadTime). djean@chromium.org ajuma@chromium.org Page load time for Browser-initiated navigations. Browser-initiated navigations include all navigations initiated by interacting with Chrome's UI elements, except for back/forward navigations. Specifically, typing a URL into the omnibox, tapping the reload button, loading a bookmark, and loading a page from the reading list (including when offline) are all considered browser-initiated. Additionally, background loads for prerendering and reading-list offline sync are also browser-initiated, as is a reload triggered by switching to a tab whose WKWebView renderer process was killed by the OS. This is recorded for successful main-frame navigations (that is, navigations that don't result in the browser displaying an error page). The recorded value measures the time from the navigation request being sent to the renderer process until all frames have fired their load events. For background loads, the same interval is measured while the page loads and fires load events in the background; the metric is not recorded again if the background-loaed page is later displayed in the foreground. Page loads that require network fetches will be slower than those where all necessary resources are already present in WebKit's HTTP cache. Reload navigations where all cached resources are up-to-date are particularly fast, since they don't require any rendering updates either. It is possible for a user to interact with a page before all load events have been fired, so the recorded value should not be interpreted as the time before the page becomes interactive. Most things that affect user-perceived page load time on iOS are within WebKit, not within Chromium/Chrome code. To assess whether a change in this metric is caused by a WebKit change, split by OS version. WebKit changes always come with an OS version change. Obviously, aside from WebKit and Chromium changes, this metric can move due to exogenous factors such as changes in what type of web page people are looking at or changes in the implementation of popular websites. Any navigation that is not considered browser-initiated is considered to be renderer-initiated (see PLT.iOS.RendererInitiatedPageLoadTime2). Replaced by PLT.iOS.RendererInitiatedPageLoadTime2 as of M92, in order to use more granular buckets above 10 seconds. djean@chromium.org ajuma@chromium.org Page load time for Renderer-initiated navigations. Renderer-initiated navigations are all main-frame navigations that are not considered to be browser-initiated (see PLT.iOS.BrowserInitiatedPageLoadTime). Specificially, tapping on links within web content, navigations triggered by JavaScript, navigations for restoring tabs on launch, and back/forward navigations are all considered to be renderer-initiated. This is recorded for successful main-frame navigations (that is, navigations that don't result in the browser displaying an error page). However, this is not recorded when WebKit handles a back/forward navigation using its page cache (that is, when the DOM representation of the destination is still loaded in memory from a recent visit), since we don't get the full set of WebKit navigation callbacks for such navigations. The recorded value measures the time from the browser process being notified that the navigation has started, to all frames having fired their load events. The time that the browser process is notified that the navigation has started is usually just after a network request is sent, but can be later for back/forward navigations on sites that use pushState to generate history entries; in the latter case, the navigation may be almost finished by the time the browser finds out about it. As such, depending on the cause of the navigation, different things are measured. Some types will be very fast (e.g., pushState/replaceState) and others (such as tapping on links) will be slower. Furthermore, navigations that require network fetches will be slower than those where all necessary resources are already present in WebKit's HTTP cache. It is possible for a user to interact with a page before all load events have been fired, so the recorded value should not be interpreted as the time before the page becomes interactive. Most things that affect user-perceived page load time on iOS are within WebKit, not within Chromium/Chrome code. To assess whether a change in this metric is caused by a WebKit change, split by OS version. WebKit changes always come with an OS version change. Obviously, aside from WebKit and Chromium changes, this metric can move due to exogenous factors such as changes in what type of web page people are looking at or changes in the implementation of popular websites. djean@chromium.org ajuma@chromium.org Page load time for Renderer-initiated navigations. Renderer-initiated navigations are all main-frame navigations that are not considered to be browser-initiated (see PLT.iOS.BrowserInitiatedPageLoadTime). Specificially, tapping on links within web content, navigations triggered by JavaScript, navigations for restoring tabs on launch, and back/forward navigations are all considered to be renderer-initiated. This is recorded for successful main-frame navigations (that is, navigations that don't result in the browser displaying an error page). However, this is not recorded when WebKit handles a back/forward navigation using its page cache (that is, when the DOM representation of the destination is still loaded in memory from a recent visit), since we don't get the full set of WebKit navigation callbacks for such navigations. The recorded value measures the time from the browser process being notified that the navigation has started, to all frames having fired their load events. The time that the browser process is notified that the navigation has started is usually just after a network request is sent, but can be later for back/forward navigations on sites that use pushState to generate history entries; in the latter case, the navigation may be almost finished by the time the browser finds out about it. As such, depending on the cause of the navigation, different things are measured. Some types will be very fast (e.g., pushState/replaceState) and others (such as tapping on links) will be slower. Furthermore, navigations that require network fetches will be slower than those where all necessary resources are already present in WebKit's HTTP cache. It is possible for a user to interact with a page before all load events have been fired, so the recorded value should not be interpreted as the time before the page becomes interactive. Most things that affect user-perceived page load time on iOS are within WebKit, not within Chromium/Chrome code. To assess whether a change in this metric is caused by a WebKit change, split by OS version. WebKit changes always come with an OS version change. Obviously, aside from WebKit and Chromium changes, this metric can move due to exogenous factors such as changes in what type of web page people are looking at or changes in the implementation of popular websites. Please list the metric's owners. Add more owner tags as needed. This time is based on the NavigationTiming spec and is a more accurate version of PLT.RequestToStart. Start: requestStart. Request: navigationStart. Please list the metric's owners. Add more owner tags as needed. This time is based on the NavigationTiming spec and is a more accurate version of PLT.StartToCommit. Start: requestStart. Commit: responseStart. Please list the metric's owners. Add more owner tags as needed. This time is based on the NavigationTiming spec and is a more accurate version of PLT.StartToFinish. Start: requestStart. Finish: loadEventEnd. Please list the metric's owners. Add more owner tags as needed. Time from "request" to "start." "Request"== time when user requested document. "Start"== time when renderer requested load of document, after any unload of last document. dpad@google.com cros-peripherals@google.com Acceleration setting for pointing sticks (typically TrackPoints, the miniature red joysticks found in some laptop keyboards). Only reported on Chrome OS. Expired from 2021-04-01 to M113. May be missing some data. dpad@google.com cros-peripherals@google.com Sensitivity value for pointing sticks (typically TrackPoints, the miniature red joysticks found in some laptop keyboards). Only reported on Chrome OS. Expired from 2021-04-01 to M113. May be missing some data. dpad@google.com cros-peripherals@google.com Setting for the primary button of pointing sticks (typically TrackPoints, the miniature red joysticks found in some laptop keyboards). Only reported on Chrome OS. Expired from 2021-04-01 to M113. May be missing some data. Removed 2022-09. ksakamoto@chromium.org webpackage-dev@chromium.org The body size of each prefetched signed exchanges in PrefetchedSignedExchangeCache which is attached to a frame. Recorded when the frame is deleted or is navigated to different document. Removed 2022-09. ksakamoto@chromium.org webpackage-dev@chromium.org The total body size of prefetched signed exchanges in PrefetchedSignedExchangeCache which is attached to a frame. This metric is recorded when the frame is deleted or is navigated to different document. This is not recorded when there is no prefetched signed exchanges. ksakamoto@chromium.org webpackage-dev@chromium.org The number of prefetched signed exchanges in PrefetchedSignedExchangeCache which is attached to a frame. This metric is recorded when the frame is deleted or is navigated to different document. This is not recorded when there is no prefetched signed exchanges. Removed 2022-09. ksakamotoro@chromium.org webpackage-dev@chromium.org The total headers size of prefetched signed exchanges including outer response headers and inner response headers in PrefetchedSignedExchangeCache which is attached to a frame. This metric is recorded when the frame is deleted or is navigated to different document. This is not recorded when there is no prefetched signed exchanges. csharp@chromium.org Enumeration of errors that happened when reading Preferences files. Obsoleted 02/2021. sophiechang@chromium.org mcrouse@chromium.org tbansal@chromium.org Blocked previews due to Cache-Control:no-transform directive. Not even logged by code. Obsolete in 09/2020. ryansturm@chromium.org The actual data used for a page load using a preview optimization. Not even logged by code. Obsolete in 09/2020. 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. Not even logged by code. Obsolete in 09/2020. 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. Obsolete as of 09/2020. 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. Obsolete as of 09/2020. 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. Obsoleted 02/2021. tbansal@chromium.org dougarnett@chromium.org Records true when a URL matches the regex of denylist. Recorded at the time of navigation commit. Obsoleted 02/2021. tbansal@chromium.org dougarnett@chromium.org Records true when a redirect loop is detected when defer all script is in use. Recorded at the time of navigation commit. Obsoleted 02/2021. ryansturm@chromium.org When evaluating whether to show a user a preview, the preview might be disallowed for various reasons. If the preview is disallowed, then this reports the reason for disallowing it. If the preview is allowed, then this generally reports "Previews Allowed". It may instead report "Previews Allowed without server rule check" for a preview that expects to check server rules but they are not enabled. Recorded throughout navigation at the beginning of each navigation, after each redirect, and during commit. Obsoleted 02/2021. robertogden@chromium.org src/chrome/browser/data_saver/OWNERS User interactions with the HTTPS Server Previews notification InfoBar. Obsoleted 02/2021. robertogden@chromium.org User interactions with the Previews Android Omnibox UI. Obsoleted 02/2021. sophiechang@chromium.org mcrouse@chromium.org Whether the user chose to reload the original page when shown a preview. Not even logged by code. Obsolete in 09/2020. ryansturm@chromium.org The estimated content length of a page load using a preview optimization. Obsoleted 02/2021. robertogden@chromium.org Records why the page load ended on a given preview type. Obsolete as of 11/2020. dougarnett@chromium.org mcrouse@chromium.org tbansal@chromium.org Records the effective connection type of a navigation that triggers a preview. This is captured at commit time but uses the effective connection type from the beginning of the navigation. forshaw@chromium.org wfh@chromium.org Errors returned while launching sandboxed process on Windows. For decoding error code please refer to http://goo.gl/fJJiAv. wfh@chromium.org forshaw@chromium.org Errors returned while launching lowbox enabled sandboxed process on Windows. For decoding error code please refer to http://goo.gl/fJJiAv. Warning: this histogram expired in M87, and was revived in M103; data may be missing. ajgo@chromium.org src/sandbox/policy/win/OWNERS Duration of StartSandboxedProcess() including the time Windows spends starting the suspended process. Emitted on a successful launch of a sandboxed process on Windows. Only emitted where a high-resolution timer is available (see Windows.HasHighResolutionTimeTicks). Code removed 2021/06. 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. peter@chromium.org knollr@chromium.org When a Service Worker receives a push message, this records whether the overall operation was successful, or otherwise the type of error encountered. peter@chromium.org knollr@chromium.org When a webpage asks for details about its current push messaging registration, this records whether the request is successful, or otherwise the type of error encountered. This histogram was expired between 2022-06-26 and 2023-08-04. peter@chromium.org rayankans@chromium.org knollr@chromium.org When a Service Worker receives a pushsubscriptionchange event, this records whether the overall operation was successful, or otherwise the type of error encountered. peter@chromium.org knollr@chromium.org When a webpage registers for push messaging, this records whether the request is successful, or otherwise the type of error encountered. This histogram was expired between 2022-06-26 and 2023-08-04. peter@chromium.org knollr@chromium.org When a message arrives for a lazy subscription and Chrome isn't in the foreground, it is persisted on disk until next time Chrome is in the foreground. This histogram measures the time spent in reading and replaying persisted messages when Chrome goes to the foreground. peter@chromium.org knollr@chromium.org When unregistering a website from push messaging, this records the reason why it is being unregistered. peter@chromium.org knollr@chromium.org When unregistering a website from push messaging, this records whether the request is successful, or otherwise the type of error encountered. This histogram was expired between 2022-06-26 and 2023-08-04. mastiz@chromium.org mmrashad@google.com treib@chromium.org When an entry is added or replaced in the reading list, records in which storage this happened. corising@chromium.org chrome-desktop-ui-sea@google.com The state of the bookmark bar recorded {Frequency} a user adds to the reading list. (Desktop only). gambard@chromium.org bling-team@google.com The action chosen by the user after displaying the reading list context menu. gambard@chromium.org bling-team@google.com Number of tries before the download of the entry is successful. gambard@chromium.org bling-team@google.com Final status of the download of a reading list entry. gambard@chromium.org bling-team@google.com Time since the first read of the reading list entry getting deleted. 0 if it has never been read. mastiz@chromium.org mmrashad@google.com treib@chromium.org When a reading list entry is marked as read, records in which storage this happened. gambard@chromium.org bling-team@google.com Whether the displayed version is the offline one. gambard@chromium.org bling-team@google.com Time since the creation of the read reading list entry getting deleted. thegreenfrog@chromium.org olivierrobin@google.com Time since the creation of the read reading list entry being read for the first time. gambard@chromium.org bling-team@google.com Number of read entries in reading list. No longer recorded as of 2023-05. corising@chromium.org chrome-desktop-ui-sea@google.com Records whether the reading list and bookmarks sync states match on startup when not in Incognito or guest mode (Desktop only). gambard@chromium.org bling-team@google.com Time since the creation of the unread reading list entry getting deleted. gambard@chromium.org bling-team@google.com Number of unread entries in reading list. corising@chromium.org chrome-desktop-ui-sea@google.com Records the time taken to load the Read Later WebUI and render (at least) the initial list of entries. This is roughly equivalent to 'time to first meaningful paint' for the Read Later UI. corising@chromium.org chrome-desktop-ui-sea@google.com The amount of time between the RenderFrameHost StartProvisionalLoad event and the RenderFrameHost DocumentOnLoadCompleted event for the Read Later WebUI page. corising@chromium.org chrome-desktop-ui-sea@google.com The amount of time between the RenderFrameHost StartProvisionalLoad and DidFinishDocumentLoad events for the Read Later WebUI page. Deprecated as of 2021/02. Metric is no longer needed. corising@chromium.org chrome-desktop-ui-sea@google.com The time taken for the WebUI in the renderer to receive the full list of entries for the current user profile. This is measured as the time from when the data was first requested by the WebUI to when the data was received by the WebUI. corising@chromium.org chrome-desktop-ui-sea@google.com Records the amount of time between when a reading list bubble is opened and when it is closed. It does so by recording the difference in time between when the the hosting WebUIBubbleDialogView's Widget is first created and when the widget is destroyed. This is logged on Desktop only. corising@chromium.org mastiz@chromium.org mmrashad@google.com treib@chromium.org chrome-desktop-ui-sea@google.com The number of {ReadStatus} items in the reading list {StorageState}. Recorded {RecordedAt}. robertshield@chromium.org Log each stage of a recovery component event. Removed January 2021. tby@chromium.org charleszhao@chromium.org Records situations that can occur during the configuration and initialization of a RecurrenceRanker. Removed January 2021. tby@chromium.org charleszhao@chromium.org Whether the conversion of a JSON config for a RecurrenceRanker succeeded for failed. Removed January 2021. tby@chromium.org charleszhao@chromium.org Reports the result of a save or load of a RecurrenceRanker model. Removed January 2021. tby@chromium.org charleszhao@chromium.org Reports when the functions of a RecurrenceRanker model are used. awillia@chromium.org miketaylr@chromium.org victortan@chromium.org Count of requests restarted or the reason why not restarted when reducing accept-language HTTP header. awillia@chromium.org miketaylr@chromium.org victortan@chromium.org The latency (in milliseconds) to clear the reduce accept language for a given origin in the language negotiation cache. This histogram is recorded when clearing persisted value from PrefService. awillia@chromium.org miketaylr@chromium.org victortan@chromium.org The latency (in microseconds) to fetch the reduce accept language for a given origin in the language negotiation cache. This histogram is recorded when fetching persisted value from PrefService. Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. awillia@chromium.org miketaylr@chromium.org victortan@chromium.org The latency (in milliseconds) to store the reduced accept language header value for a given origin in the language negotiation cache. This histogram is recorded when navigation responses are being processed. awillia@chromium.org miketaylr@chromium.org victortan@chromium.org Count of reduce accept language that need to be persisted to the disk. Recorded by the renderer. This histogram is recorded when navigation responses are being processed. Removed in M90. ayaelattar@chromium.org grt@chromium.org The result of an attempt to show a relaunch notification dialog. Removed in January 2022. engedy@chromium.org For each load in a frame, records the number of interface requests to RenderFrame::GetRemoteInterfaces that arrived to the RenderFrameHostImpl after the RFHI had already committed the next cross-document navigation. This means that |document_scoped_interface_provider_binding_| was already unbound at the time from the interface connection that had been used to service RenderFrame::GetRemoteInterface for the previous load, so those interface requests are dropped. This histogram measures how often, if at all, that happens in practice. ccameron@chromium.org etienneb@chromium.org Time retrieve the fallback fonts on the system used for RenderTextHarfBuzz::ShapeRuns. This metric is known to be quite slow on bad cases. ccameron@chromium.org etienneb@chromium.org Time retrieve the preferred fallback font on the system used for RenderTextHarfBuzz::ShapeRuns. Fallback font is determined based on the input text and locale. ccameron@chromium.org etienneb@chromium.org This metric records the fallback font mechanism required to complete the shaping of a text. ccameron@chromium.org etienneb@chromium.org Time to perform RenderTextHarfBuzz::ShapeRuns with retrieved the fallback fonts. This metric is known to be quite slow on bad cases. gabolvr@google.com droger@chromium.org Count the clicks and displays of renderer view context menu item Open Link as Profile, as well as Open Link in Incognito Window for comparison. If Open Link as Profile is a submenu, it is counted as displayed even if the submenu is not open, and only counted one time regardless the amount of items in the submenu. avi@chromium.org edwardjung@chromium.org mpearson@chromium.org Count of renderer view context menu items shown. avi@chromium.org mpearson@chromium.org chrome-analysis-team@google.com Count of renderer view context menu items (Only commands now) used. The user action RenderViewContextMenu.Used.IDC_CONTENT_CONTEXT_SEARCHWEBFOR is also logged in case that IDC_CONTENT_CONTEXT_SEARCHWEBFOR is logged to this histogram. This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. wfh@chromium.org src/net/reporting/OWNERS The exact database error encountered when initializing the Reporting and NEL database, if initialization fails catastrophically. This is recorded if the database initialization fails catastrophically when the DB initialization attempt is made, which typically occurs upon the first network request after startup. Catastrophic errors are defined in sql::IsErrorCatastrophic. yhirano@chromium.org src/net/reporting/OWNERS The number of NEL policies loaded from the store. This is recorded when the NetworkErrorLoggingService requests a load from the backing store, which typically happens upon the first network request after startup. yhirano@chromium.org src/net/reporting/OWNERS The number of NEL policies loaded from the store. This is recorded when the NetworkErrorLoggingService requests a load from the backing store, which typically happens upon the first network request after startup. yhirano@chromium.org src/net/reporting/OWNERS The number of Reporting endpoint groups loaded from the store. This is recorded when the ReportingCache requests a load from the backing store, which happens upon receipt of the first Report-To header or queued report after startup. yhirano@chromium.org src/net/reporting/OWNERS The number of Reporting endpoints loaded from the store. This is recorded when the ReportingCache requests a load from the backing store, which happens upon receipt of the first Report-To header or queued report after startup. yhirano@chromium.org src/net/reporting/OWNERS The time (ms) taken to initialize the Reporting and NEL DB. This is recorded when the DB is initialized, which typically occurs upon the first network request after startup. wfh@chromium.org src/net/reporting/OWNERS The result of calling ::GetLastError() if initializing the Reporting and NEL database fails catastrophically. This is recorded, on Windows only, if the database initialization fails when the DB initialization attempt is made, which typically occurs upon the first network request after startup. Catastrophic errors are defined in sql::IsErrorCatastrophic. merkulova@chromium.org Records the number of times the factory reset dialog was shown. Grouped by the viewtype. tbansal@chromium.org Records if the loading of a resource was blocked because the resource URL matched the resource loading hints. Recorded every time a resource load is requested. tbansal@chromium.org Records the resource load priority of a resource when its loading is not blocked due to the resource loading hints. Recorded every time a resource load is requested, and the load is not blocked due to the resource loading hints. tbansal@chromium.org Records the resource load priority of a resource when its loading is blocked due to the resource loading hints. Recorded every time a resource load is requested and the resource load is blocked because the resource URL matched the resource loading hints. tbansal@chromium.org dougarnett@chromium.org Records if the resource patterns were available at the time of page commit if the committed previews type was RESOURCE_LOADING_HINTS and the navigation was redirected. This is a subset of the ResourcePatternsAvailableAtCommit histogram. Obsoleted M85. tbansal@chromium.org Records how long after the start of a delayable resource request, a non-delayable resource request arrived. This is the duration of time that the delayable request should have been queued for so as to avoid any network contetion with later-arriving non-delayable requests. Obsoleted M89. tbansal@chromium.org dougarnett@chromium.org The duration of time between the end of a non-delayable resource request to the start of the next non-delayable resource request. Recorded at the start of all non-delayable requests that are preceeded by at least one completed non-delayable request in the same resource scheduler client. Recorded only when a non-delayable request is NOT in-flight. tbansal@chromium.org dougarnett@chromium.org The duration of time between the start of a non-delayable resource request to the start of the next non-delayable resource request. Recorded at the start of all non-delayable requests that are preceeded by at least one started non-delayable request in the same resource scheduler client. Recorded only when a delayable request is in-flight. tbansal@chromium.org dougarnett@chromium.org Within a request's lifetime, the peak observed queueing delay tells whether the request was affected by the network congestion. Records the maximum network queueing delay when the given request was in-flight. This is emitted when the request is completed. tbansal@chromium.org The amount of time the ResourceScheduler queued a request. Recorded in separate histograms based on the request loading priority at the time the request was dequeued. Removed Feb 2022. eseckler@chromium.org khokhlov@chromium.org skyostil@chromium.org Records the duration of the period when some low-priority requests were throttled due to weak radio signal. Only supported on Android. wzang@chromium.org Record if updating |should_send_rlz_ping| in RW_VPD is successful within the maximum retry counts. mpolzer@google.com crisguerrero@chromium.org chromeos-commercial-remote-management@google.com The result when attempting to restore data during a ChromeOS rollback. mpolzer@google.com crisguerrero@chromium.org chromeos-commercial-remote-management@google.com The result when attempting to save data during a ChromeOS rollback. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Records results of SafeBrowsing download url check. Warning: this histogram was expired from M78 to M91. Data may be missing. This metric is used to populate a dashboard on go/crsb-site. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com The time it takes for SafeBrowsing to check a download url. Warning: this histogram was expired from M78 to M91. Data may be missing. vakh@google.com Response or error codes from the SafeBrowsing service. Logged after a GetHash request finishes to capture the response code or error code for that call. Split out from SB2.GetHashErrorResponseOrErrorCode in M49. felt@chromium.org The time between when we show the SafeBrowsing phishing interstitial and the user navigating away by for example, closing the tab, clicking the browser back button or typing another URL in the address bar. felt@chromium.org The time between when we show the SafeBrowsing phishing interstitial and the user expanding the "see more info" section of the page. (Only applies to field trial version 2 of the interstitial.) felt@chromium.org The time between when we show the SafeBrowsing phishing interstitial and the user clicking on the learn more link. felt@chromium.org The time between when we show the SafeBrowsing phishing interstitial and the user clicking on the proceed link. felt@chromium.org The time between when we show the SafeBrowsing phishing interstitial and the user clicking on the report error link. felt@chromium.org The time between when we show the SafeBrowsing phishing interstitial and the user clicking on the big green back button. vakh@chromium.org chrome-counter-abuse-alerts@google.com Count of how many URLs were actually checked vs skipped via RemoteSafeBrowsingDatabaseManager because the scheme is not supported by Safe Browsing. Incremented each time a resource load is initiated. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Count of how many URLs were actually checked by {CheckType} vs skipped via RemoteSafeBrowsingDatabaseManager because the scheme is not supported by Safe Browsing. Incremented each time a resource load is initiated. Different check types are not directly comparable because hash real time checks have applied pre-filtering before this histogram is logged while hash database checks haven't. vakh@chromium.org csharrison@chromium.org chrome-counter-abuse-alerts@google.com The microseconds between sending the Safe Browsing API call and receiving the response. Logged in java code and does not include any thread hops or extra work. Note that this does include task queue time to respond to the IPC (and that queue time is often non-trivial). Warning: This metric may include reports from clients with low-resolution clocks (i.e. on Windows, ref. |TimeTicks::IsHighResolution()|). Such reports will cause this metric to have an abnormal distribution. When considering revising this histogram, see UMA_HISTOGRAM_CUSTOM_MICROSECONDS_TIMES for the solution. vakh@chromium.org chrome-counter-abuse-alerts@google.com Latency of URL-classification API calls from Chrome via RemoteSafeBrowsingDatabaseManager, logged per-request. This includes the time to go through JNI, check the URL, and return the result and includes several thread hops betwetween IO and UI threads. The resource-load will not necessarily be delayed this much (see SB2.Delay for that). vakh@chromium.org chrome-counter-abuse-alerts@google.com The status code provided by GmsCore if it is unable to respond to a URL check request due to incorrect initialization, not being ready, etc. Logged on each URL check that hits the internal error condition. The total number of these should add up to the INTERNAL_ERROR reports under SB2.RemoteCall.Result. vakh@chromium.org chrome-counter-abuse-alerts@google.com Result of URL-classification API calls from Chrome via RemoteSafetyNetApiHandler. Logged after each URL is judged safe/not-safe, or hits a deadline. The INTERNAL_ERROR cases are further classified under SB2.RemoteCall.InternalErrorStatusCode. Removed from code Jul 2021. vakh@chromium.org chrome-counter-abuse-alerts@google.com The threat sub-type annotated for URLs classified as PHA via remote calls through RemoteSafeBrowsingApiHandler. "PHA" classifications generate "malware" interstitials. Removed from code Jul 2021. vakh@chromium.org chrome-counter-abuse-alerts@google.com The threat sub-type annotated returned for URLs classified as social engineering via remote calls through RemoteSafeBrowsingApiHandler. "Social engineering" classifications generate "phishing" interstitials. xinghuilu@chromium.org chrome-counter-abuse-alerts@google.com Request destinations of resources that were inspected by Safe Browsing in the SafeBrowsingResourceThrottle. kDocument is for a main resource request in a main frame or a Portal. Subframe requests are a combination of kIframe and kFrame. Removed from code in M94. Replaced with SB2.RequestDestination. vakh@chromium.org chrome-counter-abuse-alerts@google.com Resource types of resources that were inspected by Safe Browsing in the SafeBrowsingResourceThrottle. Starting M89, this metric is derived from network::mojom::RequestDestination. kPrefetch, kFavicon, kXhr, kPing, kNavigationPreloadMainFrame, and kNavigationPreloadSubFrame are all mapped to kSubResource. Removed 10-2021 due to lack of use. drubery@chromium.org chrome-counter-abuse-alerts@google.com The time it takes for the TwoPhaseUploader to complete. This is logged on every upload. vakh@chromium.org chrome-counter-abuse-alerts@google.com The type of incident discarded by the safe browsing incident reporting service as a result of profile or service destruction. vakh@chromium.org chrome-counter-abuse-alerts@google.com The type of incident given to the safe browsing incident reporting service but dropped as a result of not participating in safe browsing. caitkp@google.com The elapsed time to collect environmental data for a safe browsing incident report. caitkp@google.com The elapsed time to find the most recent binary download from all loaded profiles when creating a safe browsing incident report. vakh@chromium.org chrome-counter-abuse-alerts@google.com The type of incident included in an incident report by the safe browsing incident reporting service. caitkp@google.com The elapsed time between two successive incidents collated into the same incident report by the safe browsing incident reporting service. vakh@chromium.org chrome-counter-abuse-alerts@google.com The type of incident pruned by the safe browsing incident reporting service as a result of not having a matching binary download. vakh@chromium.org chrome-counter-abuse-alerts@google.com The type of incident pruned from a report in the safe browsing incident reporting service as a result of having previously been reported. vakh@chromium.org chrome-counter-abuse-alerts@google.com The type of incident received by the safe browsing incident reporting service. vakh@chromium.org chrome-counter-abuse-alerts@google.com The size, in bytes, of a safe browsing incident report. caitkp@google.com The result of an attempted report upload by the safe browsing incident reporting service. caitkp@google.com The elapsed time to verify the binary integrity of chrome.exe. caitkp@google.com The elapsed time to verify the binary integrity of chrome.dll. caitkp@google.com The elapsed time to verify the binary integrity of chrome_child.dll. caitkp@google.com The elapsed time to verify the binary integrity of chrome_elf.dll. Removed 09-2022 due to lack of use and historical stability. drubery@chromium.org chrome-counter-abuse-alerts@google.com Measures the total duration (including delay due to retries) of a failed upload request. This is recorded after the last retry on every failed upload. Warning: This histogram was expired in M91 and restored in M92. Data may be missing in M91. Removed 09-2022 due to lack of use and historical stability. drubery@chromium.org chrome-counter-abuse-alerts@google.com The HTTP response code or net error from each upload attempt. This is recorded once for each network request made as part of an upload, i.e. if an upload fails the first time, but a retry succeeds, this metric is recorded twice. Warning: This histogram was expired in M91 and restored in M92. Data may be missing in M91. Removed 09-2022 due to lack of use and historical stability. drubery@chromium.org chrome-counter-abuse-alerts@google.com Counts how many retries were needed to complete the upload request. This is emitted for every successful upload. Warning: This histogram was expired in M91 and restored in M92. Data may be missing in M91. Removed 09-2022 due to lack of use and historical stability. drubery@chromium.org chrome-counter-abuse-alerts@google.com Measures the total duration (including delay due to retries) of a successful upload request. This is recorded for every successful upload. Warning: This histogram was expired in M91 and restored in M92. Data may be missing in M91. Removed 09-2022 due to lack of use and historical stability. drubery@chromium.org chrome-counter-abuse-alerts@google.com The size of the upload request body. This is a combination of the upload data and metadata. This is recorded once for each upload, regardless of whether it was successful. Warning: This histogram was expired in M91 and restored in M92. Data may be missing in M91. Removed 09-2022 due to lack of use and historical stability. drubery@chromium.org chrome-counter-abuse-alerts@google.com Whether the overall upload request succeeded or not. This is recorded once for an upload request, regardless of how many retries were needed to complete the upload. Warning: This histogram was expired in M91 and restored in M92. Data may be missing in M91. antrim@chromium.org rsorokin@chromium.org cros-oac@google.com What type of authentication was attempted when the user failed to unlock the lock screen. antrim@chromium.org rsorokin@chromium.org cros-oac@google.com The time spent for authentication in case of a failure. antrim@chromium.org rsorokin@chromium.org cros-oac@google.com What type of authentication was attempted when the user successfully unlocked the lock screen. antrim@chromium.org rsorokin@chromium.org cros-oac@google.com The time spent for authentication in case of a success. antrim@chromium.org rsorokin@chromium.org cros-oac@google.com The time spent before the screen locker is ready. charleszhao@chromium.org chromeos-platform-power@google.com The duration for the screen to be in locked/unlocked state. Recorded inside ScreenlockMonitor, when the screen lock state changes. jeffreycohen@chromium.org src/components/send_tab_to_self/OWNERS UI>Browser>Sharing Records user flow for SendTabToSelf feature. Because each bucket represents a different aspect of the flow, it's important to look at "bucket count", not "bucket proportion". On iOS this was not recorded between M85 and M90, inclusive (see crbug.com/1204944). This expired 2022/10 and got revived 2023/07, some data will be missing. alemate@chromium.org Records result of fetching and parsing OEM customization manifest. See ServicesCustomizationDocument class for more info. Used only on Chrome OS. hanxi@chromium.org yfriedman@chromium.org hnakashima@chromium.org mheikal@chromium.org Histogram of how Chrome is launched, either in ServiceManager only mode or as full browser, as well as either cold start or warm start. See go/servicification_startup_metrics for more details. hanxi@chromium.org yfriedman@chromium.org hnakashima@chromium.org mheikal@chromium.org Histogram of how Chrome is launched, either in ServiceManager only mode or as full browser, as well as either cold start or warm start. See go/servicification_startup_metrics for more details. The UMA data is cached in the SharedPreference compared with Servicification.Startup2, which might lose some data when Chrome is running in the ServiceManager only mode. forshaw@chromium.org True if the the installer successfully added AppContainer ACEs to the application directory during installation and updating. etiennep@chromium.org grt@chromium.org The cumulative disk usage in MB during install or uninstall attempt, recorded right after the install/uninstall attempt on windows only. Removed in M94. grt@chromium.org src/chrome/installer/OWNERS Hit following a successful install or update when the legacy "app launcher" Clients key is deleted from the registry. Removed in M94. grt@chromium.org src/chrome/installer/OWNERS Hit following a successful install or update when the legacy "binaries" Clients key is deleted from the registry. Removed in M94. grt@chromium.org src/chrome/installer/OWNERS Hit following a successful install or update when the COM registration for the legacy "IExecuteCommand" implementation class key is deleted from the registry. Removed in M94. grt@chromium.org src/chrome/installer/OWNERS Hit following a successful install or update when the legacy "install-extension" app command is deleted from the registry. zmin@chromium.org grt@chromium.org Record the status of unpacking the contents of a 7z file. huangs@chromium.org The peak page file usage by setup.exe in KB during install or uninstall attempt. huangs@chromium.org The peak working set size of setup.exe in KB during install or uninstall attempt. Removed in M100 (expired a long time ago). waffles@chromium.org Hit following a successful install or update when the legacy profile count keys / values are deleted from the registry. grt@chromium.org ydago@chromium.org The final exit-result of the entire run of setup.exe on Windows. Expired on 10/2020. dcheng@chromium.org rsesek@chromium.org Tracks whether an attempt to map shared memory was blocked due to too much shared memory already being mapped into the address space. mpearson@chromium.org The number of entries in shortcuts backend's database when initialized, which happens during profile load. etienneb@chromium.org gab@chromium.org Time duration for shutdown initiated by the browser exit menu command. The duration covers from the shutdown trigger to the deletion of the BrowserImpl. Note: Android does not have shutdown metrics. etienneb@chromium.org gab@chromium.org Time duration for shutdown initiated by an end session (user logs off, shuts down or reboots without explicitly exiting).The duration covers from the shutdown trigger to the deletion of the BrowserImpl. Note: Android does not have shutdown metrics. etienneb@chromium.org gab@chromium.org Time for shutdown for a not valid exit. This situation happen when a chrome process is already running and the process is terminated after the process singleton rendez-vous. The duration covers from the shutdown trigger to the deletion of the BrowserImpl. Note: Android does not have shutdown metrics. etienneb@chromium.org gab@chromium.org Time duration for clean shutdown that are not catched by other not initiated by the users. The duration covers from the shutdown trigger to the deletion of the BrowserImpl. Note: Android does not have shutdown metrics. etienneb@chromium.org gab@chromium.org The action type that triggered a browser shutdown. The metric is emitted just after BrowserImpl deletion. Note: Android does not have shutdown metrics. In M-108, the detection of shutdown due to early exit paths changed and these shutdowns will be moved from the NotValid bucket to the Other bucket. etienneb@chromium.org gab@chromium.org Time for shutdown for a silent exit. The duration covers from the shutdown trigger to the deletion of the BrowserImpl. Note: Android does not have shutdown metrics. etienneb@chromium.org gab@chromium.org Time for shutdown initiated by the last browser window being closed. The duration covers from the shutdown trigger to the deletion of the BrowserImpl. Note: Android does not have shutdown metrics. ksakamoto@chromium.org webpackage-dev@chromium.org Records if the fetched Signed Exchange certchain was served from HTTP cache or not. ksakamoto@chromium.org webpackage-dev@chromium.org Reports the result of Signed Exchange cert verification, including success. ksakamoto@chromium.org webpackage-dev@chromium.org Reports the result of Signed Exchange CT verification, including success. ksakamoto@chromium.org webpackage-dev@chromium.org Records true when a fallback redirect of Signed Exchange has failed with ERR_TO_MANY_REDIRECTS. Total count of SignedExchange.LoadResult2 should be used as a baseline of this histogram. ksakamoto@chromium.org webpackage-dev@chromium.org Records the result of loading a resource from Signed HTTP Exchange. Emitted each time a response is handled as Signed Exchange. ksakamoto@chromium.org webpackage-dev@chromium.org The status of OCSP response in Signed Exchange certificates. Reported each time Signed Exchange's OCSP check is performed. ksakamoto@chromium.org webpackage-dev@chromium.org Reports the revocation status of OCSP response in Signed Exchange certificates. Emitted when Signed Exchange's OCSP check is performed, but only when an up-to-date OCSP response was stapled. ksakamoto@chromium.org webpackage-dev@chromium.org Records if the prefetched Signed Exchange was properly formatted and passed verification steps. Reported for each completed SignedExchange prefetch. ksakamoto@chromium.org webpackage-dev@chromium.org Recorded when Signed Exchange signature was expired. Records the time delta between current time and signature's "expires" value. ksakamoto@chromium.org webpackage-dev@chromium.org Recorded when Signed Exchange signature was not yet valid. Records the time delta between current time and signature's "date" value. ksakamoto@chromium.org webpackage-dev@chromium.org Reports the result of Signed Exchange signature verification, including success. ksakamoto@chromium.org webpackage-dev@chromium.org The amount of time elapsed to fetch certificate chain from certUrl, for which the fetch has failed. ksakamoto@chromium.org webpackage-dev@chromium.org The amount of time elapsed to fetch certificate chain from certUrl, for which the fetch has succeeded. ksakamoto@chromium.org webpackage-dev@chromium.org The amount of time that elapsed during SignedExchangeSignatureVerifier::Verify. ksakamoto@chromium.org webpackage-dev@chromium.org Number of seconds until the Signed Exchange's expiration time. Recorded when Signed Exchange signature verification is performed, and emitted only for Signed Exchanges within the validity period. awillia@chromium.org loading-dev@chromium.org The behaviour of site isolated javascript code cache recorded for each cache transaction. It records if the request was serviced and if serviced how it was serviced for ex: hit, miss, update. Warning: this histogram was expired from 2022-07-24 to 2023-04-03; data may be missing. yhirano@chromium.org loading-dev@chromium.org The amount of time spent to fetch a code cache. Recorded only for a JS code cache, and recorded only when a non-empty code cache is found. yhirano@chromium.org loading-dev@chromium.org Represents whether fetching from the code cache succeeded. Recorded when the code cache result gets available. yhirano@chromium.org loading-dev@chromium.org The amount of time that could be saved if we had a memory-backed code cache. Recorded when the code cache result gets available. yhirano@chromium.org loading-dev@chromium.org Represents whether fetching from the memory-backed code cache would succeed. Recorded when the code cache result gets available. yhirano@chromium.org loading-dev@chromium.org Represents the (hypothetical) size of the memory-backed code cache. Recorded for every 5 minutes. temao@chromium.org tluk@chromium.org The behaviour of site isolated WebUI JS code cache recorded for each cache transaction. It records if the request was serviced and if serviced how it was serviced for ex: hit, miss, update. awillia@chromium.org loading-dev@chromium.org The behaviour of site isolated web assembly code cache recorded for each cache transaction during WASM compilation. It records if the request was serviced and if serviced how it was serviced for ex: hit, miss, update. Warning: this histogram was expired from 2020-04-19 to 2023-04-03; data may be missing. Removed in Oct 2020. ericrk@chromium.org The scale factor of any images drawn by Skia. Removed in Oct 2020. ericrk@chromium.org Whether a call to drawBitmap(Rect) or drawImage(Rect) used the tiled or non-tiled rasterization path. Removed in Oct 2020. ericrk@chromium.org The count of images drawn by Skia with a given filter quality. Removed in Oct 2020. ericrk@chromium.org The path taken by Skia when it attempts to lock a texture for use. egdaniel@google.com bsalomon@google.com The number of Skia render passes sent to the GPU during a GrContext::submit call. The max value that is sent here is 100 so anything in the 100 bucket actually includes render pass counts of 100+. Though we don't expect to be reaching 100 render passes often. This is collected each time we submit to the GPU in Skia. egdaniel@google.com bsalomon@google.com The total amount of memory that the GrVkMemoryAllocator used by Skia's Vulkan backend has allocated. This is GPU memory for VkImages and VkBuffers. Note that the allocator may be shared with other users outside of Skia and this amount includes their uses as well. This is collected each time we request an allocation from Skia. egdaniel@google.com bsalomon@google.com The percent of allocated memory that is in use by the GrVkMemoryAllocator used by Skia's Vulkan backend. This is GPU memory for VkImages and VkBuffers. Note that the allocator may be shared with other users outside of Skia and this includes their allocations as well. This is collected each time we request an allocation from Skia. pavely@chromium.org src/chrome/browser/ui/messages/OWNERS Records the identifier of a snackbar every time one is shown. ianwen@chromium.org Records how users interact with the special locale promotion dialog. Removed 2021/10: This histogram was added as part of an investigation that has been completed. timvolodine@chromium.org chrome-language@google.com 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. Warning: for chrome versions 78-88 this histogram was listed as expired, so for that period the data might be missing or incomplete. Removed 2021/10: This histogram was added as part of an investigation that has been completed. timvolodine@chromium.org chrome-language@google.com 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. basiaz@google.com chrome-language@google.com The length of text checked via async checking. Warning: this histogram was expired from M83 to M107; data may be missing. basiaz@google.com chrome-language@google.com The length of text checked by spellCheck. No replacement suggestions were requested. Warning: this histogram was expired from M83 to M107; data may be missing. basiaz@google.com chrome-language@google.com The length of text checked by spellCheck. Replacement suggestions were requested. Warning: this histogram was expired from M83 to M107; data may be missing. basiaz@google.com chrome-language@google.com The number of words checked within a session. Warning: this histogram was expired from M83 to M107; data may be missing. basiaz@google.com chrome-language@google.com The average number of words checked per hour. Sampled every 30 minutes. Warning: this histogram was expired from M83 to M107; data may be missing. Logged on profile open, including for profiles that do not use this setting (such as "system" profiles) and for profiles that do not allow the profile-owner to to configure this setting (such as "guest" profiles). When logged in such cases, reported the default value. Replaced in M-114 with the histogram SpellCheck.Enabled2, which is similar yet only emitted for regular profiles. basiaz@google.com chrome-language@google.com The number of sessions that started with spellchecking enabled. Warning: this histogram was expired from M83 to M107; data may be missing. basiaz@google.com chrome-language@google.com The number of sessions that started with spellchecking enabled. Recorded only for regular profiles. (Not recorded on guest profiles for example.) basiaz@google.com chrome-language@google.com The number of misspelled words within a session. Warning: this histogram was expired from M83 to M107; data may be missing. Removed 2021/01: the relevant code path isn't used anymore. gujen@google.com chrome-language@google.com The percentage of misspelled words within checked words. basiaz@google.com chrome-language@google.com The number of misspelled-but-replaced words within a session. Warning: this histogram was expired from M83 to M107; data may be missing. Removed 2021/01: the relevant code path isn't used anymore. gujen@google.com chrome-language@google.com The percentage of replaced words within misspelled words. basiaz@google.com chrome-language@google.com The number of occurrences that shows spelling suggestion within a session. This is incremented and logged when a context menu with spelling suggestions is shown for a misspelled word. Warning: this histogram was expired from M83 to M107; data may be missing. Logged on profile open, including for profiles that do not use this setting (such as "system" profiles) and for profiles that do not allow the profile-owner to to configure this setting (such as "guest" profiles). When logged in such cases, reported the default value. Replaced in M-114 with the histogram SpellCheck.SpellingService.Enabled2, which is similar yet only emitted for regular profiles. groby@chromium.org chrome-language@google.com Whether the user has opted in to asking Google for spelling suggestions. Recorded both when spelling is initialized and when the preference is changed. groby@chromium.org chrome-language@google.com Whether the user has opted in to asking Google for spelling suggestions. Recorded only for regular profiles. (Not recorded on guest profiles for example.) Recorded both when spelling is initialized and when the preference is changed. yyushkina@google.com gujen@google.com chrome-language@google.com The elapsed time, in ms, between the moment the SimpleURLLoader starts downloading the request and the moment the SimpleURLLoader callback is invoked after the request finishes, whether an error or a success. yyushkina@google.com gujen@google.com chrome-language@google.com The HTTP code of Spelling service responses. yyushkina@google.com gujen@google.com chrome-language@google.com Describes the results returned by the Spelling service by assigning them to one of three high-level buckets: request/service error, success with no suggestions, and success with spelling suggestions. gujen@google.com chrome-language@google.com The percentage of replacement executions within suggestion occurrences. Logged on profile open, including for profiles that do not use this setting (such as "system" profiles) and for profiles that do not allow the profile-owner to to configure this setting (such as "guest" profiles). When logged in such cases, reported the default value. Replaced in M-114 with the histogram Spellcheck.Windows.ChromeLocalesSupport2.*, which are similar yet only emitted for regular profiles. gujen@google.com chrome-language@google.com Counts how many languages are added to Chrome by the user but are not supported for spell check (today Chrome only supports a hard-coded list of locales for spell check). This is a measure of the potential impact of adding support for non-Hunspell locales in the spell check settings. This also helps answer the following question: should the Chrome spell check settings raise awareness of Windows language packs and / or link to documentation describing how to install a Windows language pack? This is recorded once during spell check initialization, and then once each time the user changes their Chrome languages. gujen@google.com chrome-language@google.com Counts how many languages are added to Chrome by the user but are not supported for spell check (today Chrome only supports a hard-coded list of locales for spell check). Recorded only for regular profiles. (Not recorded on guest profiles for example.) This is a measure of the potential impact of adding support for non-Hunspell locales in the spell check settings. This also helps answer the following question: should the Chrome spell check settings raise awareness of Windows language packs and / or link to documentation describing how to install a Windows language pack? This is recorded once during spell check initialization, and then once each time the user changes their Chrome languages. Logged on profile open, including for profiles that do not use this setting (such as "system" profiles) and for profiles that do not allow the profile-owner to to configure this setting (such as "guest" profiles). When logged in such cases, reported the default value. Replaced in M-114 with the histogram Spellcheck.Windows.SpellcheckLocalesSupport2.*, which are similar yet only emitted for regular profiles. gujen@google.com chrome-language@google.com Of all the currently enabled spell check languages, counts how many are supported by the different spell checkers (Hunspell and the Windows OS). This helps measure the impact and reach of the native spell checker integration. This is recorded once during spell check initialization, and then once each time the user changes their enabled spell check languages. gujen@google.com chrome-language@google.com Of all the currently enabled spell check languages, counts how many are supported by the different spell checkers (Hunspell and the Windows OS). Recorded only for regular profiles. (Not recorded on guest profiles for example.) This helps measure the impact and reach of the native spell checker integration. This is recorded once during spell check initialization, and then once each time the user changes their enabled spell check languages. gujen@google.com chrome-language@google.com Measures the time it takes to perform one spell check end to end. The start time is taken just before invoking Hunspell or the native spell checker (via Mojo), and the end time is taken just before invoking the Blink spell check callback. This is recorded every time a spell check is performed. gujen@google.com chrome-language@google.com Measures the time it takes to generate spelling suggestions when a user right clicks a misspelled word. The start time is taken just before invoking Hunspell for the suggestions, and the end time is taken just after the final suggestion list is constructed. This is recorded every time the user opens the context menu on a misspelled word, but only if the suggestions hadn't been pre-generated (which happens when all spell check locales are supported by the OS spell checker). 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. Removed in M98 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. Expired in M77, code removed in M98 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. Expired in M77, code removed in M98 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. amanvr@chromium.org carlscab@chromium.org woa-performance@google.com The histogram is being used to track the number of messages (content::mojom::FrameHost::SubresourceResponseStarted IPCs) resulting in no-op (i.e. returning without doing anything) but requiring an IPC vs messages which revoke exceptions after seeing a good certificate when calling SSLManager::DidStartResourceResponse() from RenderFrameHostImpl::SubresourceResponseStarted(). We are not interested in calls to SSLManager::DidStartResourceResponse() from ReadyToCommitNavigation since they don't involve mojo messages. From local benchmarks, we observe this request causes significant IPC chatter, and this histogram will help us understand it better. Expired in 02/2020. Code removed in M98. estark@chromium.org Keeps track of various insecure content events, such as loading an HTTP script from an HTTPS page. carlosil@chromium.org estark@chromium.org Tracks when mixed content is loaded from a "non-webby" URL, e.g. an external protocol. The security of such URLs is unknown, but they are exempt from mixed content UI treatment because they don't usually return data to the browser. This histogram tracks how often such content is loaded so that we can decide whether to block such resources unless an enterprise policy is enabled. jlebel@chromium.org chrome-signin-team@google.com Number of accounts available for Single Sign On with the current device, recorded at the time the SSO Promo is shown. jlebel@chromium.org chrome-signin-team@google.com Action the user takes when the Single Sign On promotion is shown. jlebel@chromium.org chrome-signin-team@google.com Number of times the promotion has been seen on the current device. futhark@chromium.org Microseconds spent in StyleEngine::InvalidateStyle. Only samples from high resolution timers are recorded. futhark@chromium.org Microseconds spent in RebuildLayoutTree called from Document::UpdateStyle. futhark@chromium.org Microseconds spent in RecalcStyle called from Document::UpdateStyle. ksakamoto@chromium.org webpackage-dev@chromium.org The net error code recorded when request for a subresource web bundle was failed. horo@chromium.org webpackage-dev@chromium.org The value of content length header of a subresource web bundle, or zero if the content-length header is missing. horo@chromium.org webpackage-dev@chromium.org The result of loading subresource web bundles. horo@chromium.org webpackage-dev@chromium.org The max memory usage per renderer process for subresource web bundles which are kept in the network process's memory. Recorded when all the subresource web bundles for the renderer process are released. hayato@chromium.org webpackage-dev@chromium.org The counts of Web Bundles origin types requested by Subresource Loading with Web Bundles. Recorded when a script element whose type is webbundle is inserted into a document. horo@chromium.org webpackage-dev@chromium.org The received data size of a subresource web bundle. Recorded when received all the body of the subresource web bundle. ksakamoto@chromium.org webpackage-dev@chromium.org The number of resources contained in a web bundle. Recorded when bundle metadata is received and parsed successfully. 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. Removed some time before 10/2020. siggi@chromium.org Number of URLs present in the Suggestions local blacklist when the Suggestions service is created. mathp@chromium.org The counts of response states (such as empty or invalid) encountered by SuggestionsService when attempting to fetch suggestions from the server. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org Drag an app window from top in tablet mode will result in different window states. Logged when the app drag ended to record the window end state. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The number of the action that drag an app window from top in tablet mode. Logged when the TabletModeController is destructed, which means the user session is ended. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The number of the action that drag an app window from top in tablet mode when splitview is active. Logged when the TabletModeController is destructed, which means the user session is ended. minch@chromium.org omrilio@chromium.org The number of each volume adjust type in tablet mode. Logged when starts volume adjust while in tablet mode. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The number of the action that drag a tab of the browser window in tablet mode. Logged when the TabletModeController is destructed, which means the user session is ended. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The type of a tab drag done in tablet mode. Logged when start to drag a tab of the browser window in tablet mode. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The number of the action that drag a tab of the browser window in tablet mode when splitview is active. Logged when the TabletModeController is destructed, which means the user session is ended. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The type of the window (app window or tab strip) drag end event in tablet mode. Logged when the window drag in tablet mode ended. The corresponding feature was removed. minch@chromium.org omrilio@chromium.org The number of windows in overview when dragging a window from top in tablet mode. Logged when start the window drag and overview has been opened behind. pmonette@chromium.org kristianm@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. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@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. This histogram was expired between 2019-12-31 and M114. pmonette@chromium.org kristianm@chromium.org Records whether an equivalent driver letter path was found for a device path. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org Records the number of modules that were blocked from loading into the browser process by the third-party DLL blocking feature. This is recorded every 5 minutes. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org Records whether or not Chrome is still blocking third-party DLLs. This is a bit that turns to false when the in-process printing is invoked. Recorded every 5 minutes. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org Records the number of unique modules that were blocked from loading into the browser process by the third-party DLL blocking feature. This is recorded every 5 minutes. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@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. This histogram was expired between M77 and M114. pmonette@chromium.org kristianm@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. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@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. This histogram was expired between 2019-12-31 and M114. pmonette@chromium.org kristianm@chromium.org The total number of signed modules loaded (or potentially loaded) into the browser process. Measured shortly after startup. Windows only. This histogram was expired between 2019-12-31 and M114. pmonette@chromium.org kristianm@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. This histogram was expired between 2019-12-31 and M114. pmonette@chromium.org kristianm@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. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org The total number of modules loaded (or potentially loaded) into the browser process. Measured shortly after startup. Windows only. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org The total number of unsigned modules loaded (or potentially loaded) into the browser process. Measured shortly after startup. Windows only. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org The number of registered shell extensions found on the user's machine. This is emitted shortly after startup when the shell extensions enumeration is done. Doesn't count duplicates. This histogram was expired between M85 and M114. pmonette@chromium.org kristianm@chromium.org Records whether or not a loaded third party module could be uninstalled using the Windows Apps & Features page. This histogram was expired between M85 and M114. Removed 01/2021. dfried@chromium.org pbos@chromium.org While taking a screenshot of the current tab for use as a thumbnail, the time it took to copy the tab's contents into a bitmap. carlosk@chromium.org skym@chromium.org The time it takes to detect whether a thumbnail requires a gradient overlay. This is run when thumbnails are downloaded for content suggestions, as they load and the result is cached for future use. It is Android specific. carlosk@chromium.org skym@chromium.org Whether a thumbnail used for a suggestions image requires a gradient to be overlaid to not fade into the background. It applies to the thumbnails used for content suggestions and is Android specific. Removed 01/2021. dfried@chromium.org pbos@chromium.org While taking a screenshot of the current tab for use as a thumbnail, the time it took to post-process the captured bitmap. Removed Sept 2021 due to lack of use. pdr@chromium.org vmpstr@chromium.org Measures whether the tile manager exceeded the hard GPU memory budget (OOMed). Recorded each time the tile manager assigns GPU memory to tiles. alemate@chromium.org michaelpg@chromium.org Events in TimeZoneRequest. alemate@chromium.org michaelpg@chromium.org Http response codes in TimeZoneRequest. alemate@chromium.org michaelpg@chromium.org The time elapsed between the sending of the first API request and the time the final (failed) response was recorded. Includes all retries. alemate@chromium.org michaelpg@chromium.org The time elapsed between the sending of the first API request and the time the final (successfull) response was recorded. Includes all retries. alemate@chromium.org michaelpg@chromium.org Result of TimeZoneRequest. alemate@chromium.org michaelpg@chromium.org Number of retries until the final response was recorded. elainechien@chromium.org robliao@chromium.org Chrome Labs features user-facing experiments through a button in the toolbar. This metric tracks which experiment (also called lab in the context of Chrome Labs) a user selects {State} for. This histogram is emitted to when {State} is selected in the combobox of the ChromeLabs dialog. 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. jhawkins@chromium.org Tracks touchpad device state. gavinwill@chromium.org cros-peripherals@chromium.org Tracks touchpad haptic click sensitivity setting changes by the user. Only reported on Chrome OS. gavinwill@chromium.org cros-peripherals@chromium.org Tracks touchpad haptic click sensitivity setting on startup. Only reported on Chrome OS. gavinwill@chromium.org cros-peripherals@chromium.org Tracks touchpad haptic feedback setting changes by the user. Only reported on Chrome OS. gavinwill@chromium.org cros-peripherals@chromium.org Tracks touchpad haptic feedback setting on startup. Only reported on Chrome OS. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad natural scroll setting changes by the user. Only reported on Chrome OS. Warning: this histogram was expired from 2022-06-15 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad natural scroll setting on startup. Only reported on Chrome OS. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad sensitivity setting changes by the user. This replaces the old Touchpad.Sensitivity.Changed metric. Only reported on Chrome OS. Warning: this histogram was expired from 2022-06-15 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad sensitivity setting on startup. This replaces the old Touchpad.Sensitivity.Started metric. Only reported on Chrome OS. Warning: this histogram was expired from 2022-06-15 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Whether touchpad scroll acceleration is enabled. Only reported on Chrome OS. Warning: this histogram was expired from 2020-12-01 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Touchpad scroll sensitivity value. Only reported on Chrome OS. Warning: this histogram was expired from 2020-12-01 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad TapDragging setting changes by the user. Only reported on Chrome OS. Warning: this histogram was expired from 2022-06-15 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad TapDragging setting on startup. Only reported on Chrome OS. Warning: this histogram was expired from 2022-06-15 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad TapToClick setting changes by the user. Only reported on Chrome OS. Warning: this histogram was expired from 2022-06-15 to M105; data may be missing. zentaro@chromium.org cros-peripherals@google.com Tracks touchpad TapToClick setting changes by the user. Only reported on Chrome OS. girard@chromium.org input-dev@chromium.org Recorded when a touch event excludes an active touch (a touch-id/dwId that previously generated a TOUCHEVENTF_DOWN, and has not since generated a TOUCHEVENTF_UP). Chromium generates a simulated event to maintain consistency/correctness. Only recorded on Windows. Warning: This histogram was expired after M95, and resurrected in M108. This workaround will be removed once usage drops off. See https://crbug.com/811273 for details. flackr@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. etiennep@chromium.org tracing@chromium.org chrometto-team@google.com The size, in kilobytes, of a compressed trace ready to be uploaded. Values can range from 1KB to 100MB. ssid@chromium.org Reason why background tracing finalization was not allowed. Also see "Tracing.Background.ScenarioState" metric, which records the total number of times finalization was allowed and not allowed. oksamyt@chromium.org tracing@chromium.org chrometto-team@google.com The size, in kilobytes, of a finalized trace ready to be uploaded. Values can range from 1KB to 100MB. This replaces Tracing.Background.FinalizingTraceSizeInKB, which had a minimum of 1MB and was not precise enough for WebView traces. 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) oksamyt@chromium.org tracing@chromium.org chrometto-team@google.com The size, in kilobytes, of a trace about to be uploaded. Values can range from 1KB to 100MB. eseckler@chromium.org tracing@chromium.org Records success or failure of creating the shared buffer in ProducerClient::InitSharedMemoryIfNeeded() 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. davidbienvenu@chromium.org robliao@chromium.org Records the time spent in UpdateAllDisplaysAndNotify. Only logged on Windows. malaykeshav@chromium.org Records the time spent in uncompressing a gzipped animation file. msarda@chromium.org droger@chromium.org State of the user settings for making searches and browsing better, recorded each time a regular profile is loaded (this histogram is not recoded for system profiles, guest profiles, off-the-record profiles or irregular ChromeOS profiles). Deprecated as of 2023/01 in favor of UnifiedConsent.MakeSearchesAndBrowsingBetter.OnProfileLoad as histogram UnifiedConsent.MakeSearchesAndBrowsingBetter.OnStartup was also recorded for all profiles, including system, guest and other irregular ChromeOS profiles. msarda@chromium.org droger@chromium.org State of the user settings for making searches and browsing better, recorded each time a profile was loaded. Note: Starting with CL https://crrev.com/c/3913924 (M109), this histogram was no longer recorded for System, Guest and other irregular profiles on desktop and ChromeOS. droger@chromium.org msarda@chromium.org All *off* sync data types are recorded when the user confirmed the sync setup after going through the advanced opt-in flow. emshack@chromium.org pbos@chromium.org Measures the days elapsed from an update being visible to the browser and the browser being restarted or quit. Warning: this histogram expired after M87, and was re-added in M92; data may be missing. emshack@chromium.org pbos@chromium.org Measures the hours elapsed from an update being visible to the browser and the browser being restarted or quit. spqchan@chromium.org Tracks the upgrade notification stage. This is recorded with every UMA log. Removed in M90. grt@chromium.org ydago@chromium.org Records the type of poll that first detected an installed version change. Note that a browser that is running while multiple updates are applied will only record this metric once. mpolzer@google.com crisguerrero@chromium.org chromeos-commercial-remote-management@google.com Tracks what is the reason we're doing a rollback instead of an update (going to a more stable channel or admin-initiated enterprise rollback). We're showing different notifications depending on the reason. Sent when the device finished installing the rollback image, shows the notification and is waiting for reboot. This metric is specific to ChromeOS. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from M77 to M96 some data may be missing. satorux@chromium.org hashimoto@chromium.org The system uptime on Chrome OS when the dbus-daemon process crashes, resulting in a reboot. Warning: this histogram was expired from M85 to M118 some data may be missing. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from M85 to M96 some data may be missing. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from 09/2020 to M96 some data may be missing. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from M77 to M96 some data may be missing. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from M77 to M96 some data may be missing. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from M77 to M96 some data may be missing. alemate@chromium.org cros-oac@google.com xiyuan@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. Warning: this histogram was expired from M77 to M96 some data may be missing. Removed in M100. wanderview@chromium.org dcheng@chromium.org Measures whether DoSimpleHost() in url_canon_host.cc escaped any characters in the ASCII table. This is recorded every time a URL hostname is successfully parsed. Removed in M100. wanderview@chromium.org dcheng@chromium.org This histogram records which ASCII characters are escaped in DoSimpleHost(). Each escaped character is recorded separately, but only once for any invocation of DoSimpleHost(). This can potentially be recorded every time a URL hostname is parsed, but only if parsing escaped at least one character. hayato@chromium.org src/url/OWNERS Measures whether DoPartialPathInternal() in url_canon_path unescaped any percent-encoded characters. The measurement is not specific to any particular use case. For example, this is recored to parse the following URL: new URL("https://example.com/%61") This can potentially be recorded every time a URL path is parsed, but only if unescaping at least one percent-encoded character. Eventually, we will add other metrics for each use case to better understand the usage. hayato@chromium.org src/url/OWNERS This metrics is recorded each time when KRUL.SetProtocol is called on a special scheme URL. The value is whether a new scheme is a non-special scheme or not. The measurement is not specific to any particular use case. For example, this is recorded in the following: const url = new URL("https://example.com/"); url.protocol = "non-special"; See https://crbug.com/1416018 for details. pnoland@chromium.org fgorski@chromium.org Android: count of Usage Stats events. Recorded as these events occur; e.g. when a domain is associated with a token, or a site is suspended. jasontt@chromium.org assistive-eng@google.com Distribution of the device images that users changed (Chrome OS). The statistic is recorded each time the user changes their device image to a different one in Settings. This metric expired in March 2022 and was revived in M105. Data between these times is incomplete. This metric supersedes `UserImage.Changed` due to a change in enum values. achuith@chromium.org alemate@chromium.org jasontt@chromium.org assistive-eng@google.com cros-oac@google.com Distribution of the default images that existing users log in with (Chrome OS). One sample is taken each time the user logs in. This metric supersedes UserImage.LoggedIn2 due to a change in enum values. Special value 0 (Camera image) of ChromeOSUserImageId2 is never recorded in this histogram. Warning: this histogram was expired from 2022-03-30 to 2022-08-01; data may be missing. achuith@chromium.org The time it took to download user's profile picture. achuith@chromium.org antrim@chromium.org cros-lurs@google.com The number of users of different types that log in to the system (Chrome OS). alemate@chromium.org antrim@chromium.org cros-lurs@google.com The time between one regular user logging out and a different regular user logging in (Chrome OS). Delays above thirty minutes or which span system reboots or non-regular-user logins are not reported. atwilson@chromium.org Whether the profile_ever_initialized() user attribute migration has completed for the current user. alemate@chromium.org michaelpg@chromium.org rsorokin@chromium.org cros-oac@google.com This is logged when new user type reported by Gaia is different from the old one (for existing user). Removed 01/2021. rsorokin@chromium.org cros-oac@google.com The result of restoring account id on Chrome restart after crash on Chrome OS. binlu@google.com Records instances of navigator.vibrate. Includes whether or not it comes with a user gesture, same-origin subframe or cross-origin subframe. wychen@chromium.org dtrainor@chromium.org The interval between ViewResourceAdapter#getBitmap calls. oka@chromium.org An integer representing a state transition from x to y in the form of x * 1000 + y. If the transition is not expected, the value is negated. For example an expected transition from SHOWING (= 2) to SHOWN (= 1) is denoted as 2001, and an unexpected transition from SHOWING to SHOWING is denoted as -2002. See KeyboardControllerState for the correspondence between the number and the enum. Deprecated as of 2023/04 as the Assistant integration project has been calcelled basiaz@google.com chrome-language@google.com Android: The action performed by Assistant upon being invoked during a voice search initiated via the {Source}, such as transcription of a voice search query or translation of the current page. This is recorded after an Assistant intent has completed successfully. Deprecated as of 2023/04 as the Assistant integration project has been calcelled basiaz@google.com chrome-language@google.com Android: Whether Translate extras were successfully attached to an Assistant intent. This is recorded just before the intent is sent to Assistant, and is only recorded if the Translate extras are enabled. basiaz@google.com chrome-language@google.com Android: The events related to granting or denying audio permission for system level transcription (as opposite to Assistant). Will be logged {Timing}. basiaz@google.com chrome-language@google.com Android: The source of a dismissed voice search, such as omnibox or NTP. This is recorded after the dismissed intent returns to Chrome. basiaz@google.com chrome-language@google.com Android: The target of a dismissed voice search, such as the system transcription dialog or Assistant. This is recorded after the dismissed intent returns to Chrome. basiaz@google.com chrome-language@google.com Android: The source of a failed voice search, such as omnibox or NTP. This is recorded after any intent failure, which could occur before an intent is sent (if the send fails) or after the intent returns unsuccessfully. It will only be recorded once. basiaz@google.com chrome-language@google.com Android: The target of a failed voice search, such as the system transcription dialog or Assistant. This is recorded after any intent failure, which could occur before an intent is sent (if the send fails) or after the intent returns unsuccessfully. It will only be recorded once. basiaz@google.com chrome-language@google.com Android: The source of a successful voice search, such as omnibox or NTP. This is recorded immediately after the successful intent returns to Chrome. basiaz@google.com chrome-language@google.com Android: The target of a successful voice search, such as the system transcription dialog or Assistant. This is recorded immediately after the successful intent returns to Chrome. muyuanli@chromium.org Counts the number of requests to retrieve voice interaction context when no user interaction is initiated. basiaz@google.com chrome-language@google.com Records the time it takes between the user clicking the mic and chrome receiving the transcribed voice query. This is recorded after an Assistant intent has completed successfully. basiaz@google.com chrome-language@google.com Records the time it takes between the user clicking the mic and chrome receiving the transcribed voice query. This is recorded after an Assistant intent has completed successfully. This histogram is limited to intents sent to {Target}. See VoiceInteraction.QueryDuration.Android for the total count across all targets. basiaz@google.com chrome-language@google.com Records the time it takes between the user clicking the mic and chrome receiving the intent response for {Action} actions. This is recorded after an Assistant intent has completed successfully. These per-action variants are recorded only when non-transcription actions are enabled. See VoiceInteraction.QueryDuration.Android for the total count that includes clients with non-transcription actions disabled. basiaz@google.com chrome-language@google.com Android: The source of a voice search start event, such as omnibox or NTP. This is recorded immediately before the voice transcription intent is sent. basiaz@google.com chrome-language@google.com Android: The target of a voice search start event, such as the system transcription dialog or Assistant. This is recorded immediately before the voice transcription intent is sent. basiaz@google.com chrome-language@google.com Android: The source of an incoming result that doesn't align with an outgoing request from Chrome. This is recorded when the extraneous intent response is received. basiaz@google.com chrome-language@google.com Android: The target of an intent result that doesn't align with an outgoing request from Chrome. This is recorded when the extraneous intent response is received. muyuanli@chromium.org Records the time between user interaction and the actual request arrival. basiaz@google.com chrome-language@google.com Android: Records the confidence value of a successful voice search as a percentage. This is recorded when the voice intent returns successfully. basiaz@google.com chrome-language@google.com Android: Records the confidence value of a successful voice search as a percentage, limited to intents sent to {Target}. This is recorded when the voice intent returns successfully. basiaz@google.com chrome-language@google.com Android: Records whether the voice search produced results. This is recorded when the voice intent returns successfully. basiaz@google.com chrome-language@google.com Android: Records whether the voice search produced results, limited to intents sent to {Target}. This is recorded when the voice intent returns successfully. cduvall@chromium.org jam@chromium.org Measures the time it takes to call all observers of the WebContents observer method {Method}. Logged every time the method is called. benwgold@chromium.org mdjones@chromium.org Records the number of milliseconds that it takes for a web context fetch to complete. Recorded when the javascript execution completes. To start will be used for Google Lens image queries to track time to retrieve page context, but may extend to other features over time. Removed 2021-11, since the WebKit bug whose occurrences were being tracked by this metric no longer reprodcues on iOS 13+. ajuma@chromium.org gambard@chromium.org [iOS] Records the action take when the backForwardList of the WebView is out of sync with the URL exposed by the WebView when starting a new provisional navigation. The URLs can get out of sync because of a bugs in WebKit. This is only recorded when the URLs are out of sync. ajuma@chromium.org gambard@chromium.org [iOS] Report cache hit/miss for WKWebView cert verification. CRWWKNavigationHandler has a cache of pending cert verification results to avoid extra verifications when presenting SSL interstitial. This metric helps to understand how often this cache miss happens. mrefaat@chromium.org [iOS] Measures the proportion of external URL requests that originate from a subframe without any user interaction (e.g. an advertisement contains an iframe directed at the App Store). battre@chromium.org asully@chromium.org Records the success or failure of various database operations in autofill::AutofillWebDataBackendImpl. battre@chromium.org asully@chromium.org If a migration to a new WebDatabase schema fails, this histogram records the target version to which the migration failed. battre@chromium.org asully@chromium.org Records whether WebDatabase::Init succeeds or otherwise a failure reason. battre@chromium.org fleimgruber@google.com If a migration to a new WebDatabase schema succeeds, this histogram records the target version to which the migration failed. 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. xiaochengh@chromium.org chrome-rendering-core@google.com Recorded when render-blocking web font preloads have reached the maximum blocking time, and therefore, turned into non-render-blocking. Records the number of web font preloads that are still pending. This is a diagnostic metric for feature RenderBlockingFonts. 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. Removed 2021-03 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. Removed in M91. ksakamoto@chromium.org toyoshim@chromium.org The load limit state when the first disk-cache-only request fails by cache miss, if WebFonts cache-aware timeout adaptation is enabled and applicable. hajimehoshi@chromium.org kenjibaheux@chromium.org kouhei@chromium.org ksakamoto@chromium.org Whether a locallly installed font is actually used when @font-face had local sources. No longer recorded in M89. droger@chromium.org Histogram for the format of decoded WebP images on iOS, as Chrome re-encodes WebP images on that platform. mgiuca@chromium.org Counts the number of calls to navigator.share. Includes both successful and failed shares. mgiuca@chromium.org Records the outcome of calls to navigator.share. This will not count any calls that never complete (e.g., if the page closes while the picker is open). Therefore, DO NOT look at the raw percentages of this histogram; instead, compare these numbers with the WebShare.ApiCount.Share total. NOTE: At the moment, if the user cancels the picker, its recording will be delayed, and possibly never recorded (https://crbug.com/636274), so that will account for a discrepancy between ShareOutcome and ApiCount.Share. jackhou@chromium.org The success or failure of all extension installs from the webstore. This includes those initiated by sync. dpapad@chromium.org chrome-webui@google.com URLs for which Chrome creates WebUIControllers. dschuyler@chromium.org tbuckley@chromium.org bettes@chromium.org Paths within chrome://settings visited. For evaluating popularity and priorities for chrome://settings GUI. Note that this metric used to include paths that were part of OS settings, but starting with M-81, this metric only records browser settings paths. dpapad@chromium.org etienneb@chromium.org tluk@chromium.org The elapsed time for URL requests made through the WebUIURLLoaderFactory. The reported duration is the time spent in the browser process from the reception of the mojo request up to the content delivery through mojo call. temao@chromium.org tluk@chromium.org True if WebUICodeCache feature is enabled. This counts the number of times generated WebUICodeCache JS code cache is instantiated. collinbaker@chromium.org tluk@chromium.org The WebUI tab strip is a more touch-friendly tab strip used in place of Chrome's native tab strip in some cases. It can be opened and closed. This records how a user closed it. johntlee@chromium.org dpapad@chromium.org The WebUI tab strip is a more touch-friendly tab strip used in place of Chrome's native tab strip in some cases. This records how a user closed a tab within the WebUI tab strip. yuhengh@chromium.org tluk@chromium.org romanarora@chromium.org The amount of time between the RenderFrameHost StartProvisionalLoad event and the RenderFrameHost DocumentOnLoadCompleted event for the WebUI tab strip page. This happens once when a browser window with WebUI tab strip enabled is created. WebUITabStrip.LoadDocumentTime should be smaller or equal to WebUITabStrip.LoadCoimpletedTime. yuhengh@chromium.org tluk@chromium.org romanarora@chromium.org The amount of time between the RenderFrameHost StartProvisionalLoad and DidFinishDocumentLoad events for the WebUI tab strip page. This happens once when a browser window with WebUI tab strip enabled is created. WebUITabStrip.LoadDocumentTime should be smaller or equal to WebUITabStrip.LoadCoimpletedTime. collinbaker@chromium.org tluk@chromium.org The WebUI tab strip is a more touch-friendly tab strip used in place of Chrome's native tab strip in some cases. It can be opened and closed. This records how a user opened it. collinbaker@chromium.org tluk@chromium.org The WebUI tab strip is a more touch-friendly tab strip used in place of Chrome's native tab strip in some cases. It can be opened and closed. This records how long it was open when closing. robliao@chromium.org johntlee@chromium.org WebUI Tabstrip: Time from activating a tab from WebUI to receiving an activation notification in WebUI. robliao@chromium.org johntlee@chromium.org WebUI Tabstrip: Time needed to create all of the tab elements at launch. robliao@chromium.org johntlee@chromium.org WebUI Tabstrip: Time from requesting the tab data to receiving the data. reillyg@chromium.org Records the reason why the WebUSB device chooser was closed. reillyg@chromium.org Records the reason why the "WebUSB device detected" notification was dismissed. reillyg@chromium.org Records when the user revokes permission for an origin to connect to a USB device using the WebUSB API. Renamed in M99. Please see "Android.WebView.ApiCall" going forward, which has the same logging behavior. ntfschr@chromium.org src/android_webview/OWNERS Records calls to WebView APIs in WebViewChromium. tmartino@chromium.org msarda@chromium.org droger@chromium.org chrome-signin-team@google.com Records the result of promoting sign-in via the Welcome page. tmartino@chromium.org Records whether or not Chrome was the default browser when the user left the Win10-specific Welcome page. pmonette@chromium.org tmartino@chromium.org Emits a "true" sample when the revamped WebUI-based welcome page is added to the startup tabs list. This means that barring an error on startup, it was shown to the user. This histogram can only be recorded during first-run flow, when the EnableWelcomeWin10 experiment is enabled. pmonette@chromium.org tmartino@chromium.org Emits a "true" sample when the old external welcome page is added to the startup tabs list. This means that barring an error on startup, it was shown to the user. This histogram can only be recorded during first-run flow, when the EnableWelcomeWin10 experiment is disabled. pmonette@chromium.org tmartino@chromium.org Records whether or not the check that verifies if Chrome is pinned to the taskbar has timed out. This check is done when the welcome page is opened in order to determine which instructions to display to the user. tmartino@chromium.org Records whether or not Chrome was pinned to the taskbar when the user left the Win10-specific Welcome page. rbpotter@chromium.org mahmadi@chromium.org Records load events for the What's New page when a load event occurs. This tracks how many times loading remote content is attempted, and whether it succeeds, fails and results in an error page, fails and redirects to the New Tab Page, fails and doesn't open the tab (for preloading), or fails and closes the tab. Load is attempted when the page is first opened or on first startup after updating to a new milestone. Success or failure will occur when the network request completes. Desktop only. rbpotter@chromium.org mahmadi@chromium.org Records the net error or HTTP response code of the network request for the remote content for the iframe in the What's New page. This request is triggered when the What's New page is opened. Desktop only. rbpotter@chromium.org mahmadi@chromium.org Records whether the What's New page should try to show, whether it is overridden (e.g. by welcome) and whether the user is ineligible (e.g. due to being in incognito mode). Recorded when startup tabs are being determined at initialization. Desktop only. flackr@chromium.org input-dev@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. Retired in M99. davidbienvenu@chromium.org fdoray@chromium.org A top level window's occlusion state. Recorded each time the state changes. noms@chromium.org The type of category clicked in the Windows Jumplist nhiroki@chromium.org chrome-worker@google.com Records the exit code of WorkerThread. ainslie@chromium.org edwardjung@chromium.org Number of times that each menu item is clicked. rpop@chromium.org The number of times each tab or window restore option in the Recent Tabs submenu is clicked. ainslie@chromium.org edwardjung@chromium.org The time a user takes to select a menu item after opening the menu. kkimlabs@chromium.org Time difference between touch down and touch up on Android wrench button. Removed July 2021 as enough data was collected. huangdarwin@chromium.org src/ui/base/clipboard/OWNERS Counts how often the X11 server fails to register an atom. Recorded when ::XInternAtom fails (returns None). Failure rates will inform whether we implement error handling. https://crbug.com/1000919 panicker@chromium.org Records occurence of async XHR during page dismissal state (unload, beforeunload, pagehide etc). panicker@chromium.org Records occurence of sync XHR during page dismissal state (unload, beforeunload, pagehide etc). kdillon@chromium.org panicker@chromium.org Records occurence of sync XHR requests during page dismissal state (unload, beforeunload, pagehide etc) that were forbidden.