yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com Execution time of ServiceWorkerGlobalScope.onactivate. Includes the time for waitUntil() promise to settle. yyanagisawa@chromium.org chrome-worker@google.com The result of dispatching the activate event to the worker. This is recorded to both ServiceWorker.ActivateEventStatus and whichever of ServiceWorker.ActivateEventStatus_InShutdown ServiceWorker.ActivateEventStatus_NotInShutdown is appropriate. (InShutdown means the context was null or ServiceWorkerProcessManger::Shutdown was called.) {ServiceWorker_ShutdownStatus} yyanagisawa@google.com chrome-worker@google.com True if Clients.matchAll() captures SharedWorker with blob URL. This is recorded when Clients.matchAll() is called and SharedWorker is found as a client. The entry will we added per SharedWorker entries regardless of its number. sisidovski@chromium.org chrome-worker@google.com Records whether ServiceWorkerAutoPreload is dispatched or not. This metric is recorded for the main resource. sisidovski@chromium.org chrome-worker@google.com Records the result of attempting to dispatch ServiceWorkerAutoPreload. If it was not dispatched, records the specific reason why it was blocked. This metric is recorded for the main resource. yyanagisawa@chromium.org chrome-worker@google.com The length of cached metadata of scripts which are stored to the CacheStorage by the installing service worker. yyanagisawa@chromium.org chrome-worker@google.com The total length of cached metadata of scripts which are stored to the CacheStorage by the installing service worker. yyanagisawa@chromium.org chrome-worker@google.com The counts of scripts which are stored to the CacheStorage by the installing service worker. yyanagisawa@chromium.org chrome-worker@google.com The length of scripts which are stored to the CacheStorage by the installing service worker. yyanagisawa@chromium.org chrome-worker@google.com The total length of scripts which are stored to the CacheStorage by the installing service worker. hchao@chromium.org cthomp@chromium.org chrome-secure-web-and-net@google.com How many times we need to update the address space for an extensions service worker to kLoopback. Value of histogram is what address space was saved in the service worker registration database when the registration was loaded. yyanagisawa@chromium.org chrome-worker@google.com Time spent to check ServiceWorker allowed on the context. Recorded when ServiceWorker is registered, updated, or deleted for non-ServiceWorker client. Note: The metrics is reported from all clients. Some of clients may not have high resolution timer that can send metrics with microseconds precision. sisidovski@chromium.org chrome-loading@google.com The size of `cors_exempt_header_list` passed from the browser in the ServiceWorker startup. This is recorded in `WebServiceWorkerFetchContext::Create()`, in order to ensure the fix for crbug.com/40753993 doesn't introduce any changes to the given `cors_exempt_header_list` used in the ServiceWorker. yyanagisawa@chromium.org chrome-worker@google.com When WorkerOrWorkletGlobalScope::CountUse() is called, this UMA records the current object's interface name. This UMA is for investigating crbug.com/40918057. yyanagisawa@chromium.org chrome-worker@google.com When WorkerOrWorkletGlobalScope::CountUse() is called for a dedicated worker, this UMA records the WebFeature to be recorded with the CountUse(). Metrics that does not limit to the dedicated worker caller exists as ServiceWorker.CountUse.WebFeature. This UMA is for investigating crbug.com/40918057. yyanagisawa@chromium.org chrome-worker@google.com When WorkerOrWorkletGlobalScope::CountUse() is called for a dedicated worker, this UMA records the WebFeature to be recorded with the CountUse(). This UMA is for investigating crbug.com/40918057. yyanagisawa@google.com chrome-worker@google.com Records result of destroy database operations in ServiceWorkerDatabase. yyanagisawa@google.com chrome-worker@google.com Records result of opening a database for ServiceWorkerDatabase. yyanagisawa@google.com chrome-worker@google.com Records result of read operations in ServiceWorkerDatabase. yyanagisawa@google.com chrome-worker@google.com Records result of write operations in ServiceWorkerDatabase. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com Records result of opening a disk cache for ServiceWorkerDiskCache. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com Records result of reading response from ServiceWorkerDiskCache. yyanagisawa@chromium.org chrome-worker@google.com Records result of writing response into ServiceWorkerDiskCache. This is not recorded when response has no body. Note that this is recorded on every write operation, and can there can be multiple write operations for the same response if it is large enough. chikamune@chromium.org chrome-worker@google.com Execution time of the service worker's top level script. The metric is recorded for each startup of service workers. Recorded only when the evaluation was {ResultStatus}. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken between dispatching an ExtendableMessageEvent to a Service Worker and receiving a message that it finished handling the event. Includes the time for the waitUntil() promise to settle. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken between dispatching a FetchEvent to a Service Worker and receiving a fallback-to-network reply. This histogram was expired between roughly 2021-08-01 and 2021-09-30. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken between dispatching a FetchEvent to a Service Worker and receiving a response. Includes the time for the respondWith() promise to settle. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The result of dispatching a fetch event to a Service Worker for a main resource request (i.e., a request for a navigation or a shared worker). yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time that a fetch event was queued. The start time is when the event is created on the service worker thread and added to the ServiceWorkerEventQueue. The end time is when the event is dequeued and the event handler starts to execute. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The result of dispatching a fetch event to a Service Worker for a subresource request (i.e., not a navigation or a shared worker request). sisidovski@chromium.org chrome-worker@google.com The result of the RaceNetworkRequest. RaceNetworkRequest runs a race between the network request which bypasses ServiceWorker, and the other request which goes through the fetch handler. This metric is recorded for {Resource}. sisidovski@chromium.org chrome-worker@google.com Recorded as true when the data cloning from the original response to the data pipe for the fetch handler is cancelled not to pause the data transfer for the network request. This metric is recorded per {Resource}. Recorded only when `ServiceWorkerStaticRouterRaceNetworkRequestPerformanceImprovement` is disabled, and recorded in the destructor of `ServiceWorkerRaceNetworkRequestURLLoaderClient`. sisidovski@chromium.org chrome-worker@google.com Recorded the result of data transfer from the original netowrk response to the data pipes for both the network and the fetch handler. This metric is recorded per {Resource}. Recorded only when `ServiceWorkerStaticRouterRaceNetworkRequestPerformanceImprovement` is enabled, and recorded in the destructor of `ServiceWorkerRaceNetworkRequestURLLoaderClient`. sisidovski@chromium.org chrome-worker@google.com Recorded when ServiceWorkerForwardedRaceNetworkRequestURLLoaderFactory::CreateLoaderAndStart() is called. It is recorded as false for the first call, and true for any subsequent calls. This is to measure how often this method is called multiple times, which is not expected for a legitimate renderer. This metric is recorded per {Resource}. sisidovski@chromium.org chrome-worker@google.com Recorded as true when the data cloning from the original response to the data pipe for the fetch handler is completed, but still the completion status via `ServiceWorkerRaceNetworkRequestURLLoaderClient::OnComplete()` is not invoked. This metric is recorded per {Resource}. sisidovski@chromium.org chrome-worker@google.com The result if the RaceNetworkRequest received a redirect response. RaceNetworkRequest runs a race between the network request which bypasses ServiceWorker, and the other request which goes through the fetch handler. This metric is recorded for {Resource}. yyanagisawa@chromium.org chrome-worker@google.com The reason why the service worker fetch handler has been skipped. If the fetch handler has not been skipped for any reasons, it is just recorded as not skipped instead. yyanagisawa@chromium.org chrome-worker@google.com The type of the fetch handler recorded just before dispatching the fetch handler. This represent the fetch handler type, and does not represent if the fetch handler is skipped or not. yyanagisawa@chromium.org chrome-worker@google.com Records net::Error code (as a positive integer) when a Service Worker fetch request with a race network request token fails after its matching respondWith observer has already settled/been erased. Note that this includes requests that fell back to the regular network loader (e.g. due to pipe disconnection). yyanagisawa@chromium.org chrome-worker@google.com Records net::Error code (as a positive integer) when a Service Worker fetch fails after its matching respondWith observer has already settled/been erased, specifically when the RaceNetworkRequest URLLoaderFactory (the pipe to the browser process) was actually used for the fetch. yyanagisawa@chromium.org chrome-worker@google.com Records net::Error code (as a positive integer, where 0 is net::OK for success) when any Service Worker fetch request with a race network request token completes (both during and after respondWith). Note that this includes requests that fell back to the regular network loader (e.g. due to pipe disconnection). yyanagisawa@chromium.org chrome-worker@google.com Records the loader state (e.g. race loader used, or reason for fallback) when a fetch request with a Service Worker race network request token is initiated in the Service Worker fetch handler. yyanagisawa@chromium.org chrome-worker@google.com Records the loader state when a fetch request with a Service Worker race network request token fails. yyanagisawa@chromium.org chrome-worker@google.com Records the loader state when a fetch request with a Service Worker race network request token completes successfully. yyanagisawa@chromium.org chrome-worker@google.com Records net::Error code (as a positive integer, where 0 is net::OK for success) when a Service Worker fetch request completes (both during and after respondWith), specifically when the RaceNetworkRequest URLLoaderFactory (the pipe to the browser process) was actually used for the fetch. chikamune@chromium.org chrome-worker@google.com Whether FindRegistrationForClientUrl() is called for navigation or not. This is recorded when FindRegistrationForClientUrl() function is called. chikamune@chromium.org chrome-worker@google.com Whether FindRegistrationForClientUrl() could skip calling mojo API. This is recorded only when FindRegistrationForClientUrl() is used for navigation, and when the {StorageKeyIsFirstParty}. chikamune@chromium.org chrome-worker@google.com Execution time of FindRegistrationForClientUrl until continuation is called. The metric is not recorded during startup. chikamune@chromium.org chrome-worker@google.com Whether ServiceWorkerControlleeRequestHandler::MaybeCreateLoader found a service worker registration after looking up the registration by using FindRegistrationForClientUrl. yyanagisawa@google.com chrome-worker@google.com True if Clients.match() looks up the SharedWorker client and it is a blob URL client. This will be recorded when the Clients.match() is called, and SharedWorker matches. yyanagisawa@chromium.org chrome-worker@google.com The number of clients controlled by the Chrome Extension. It has been measured when `Clients.matchAll()` is called by the Extension ServiceWorker. This is a metrics that is counted for {type}. yyanagisawa@chromium.org chrome-worker@google.com The number of network fetches performed by the install event handler. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The result of dispatching the install event to the worker. This histogram includes data for {type}. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken between dispatching an InstallEvent to a Service Worker and receiving a message that it finished handling the event. Includes the time for the waitUntil() promise to settle. This histogram includes data for {type}. sisidovski@chromium.org chrome-worker@google.com The time taken from (a) the response of the AutoPreload is received, to (b) the fetch handler execution is completed. Recorded for each navigation request (including redirects) where there is a fetch event handler, the fetch event was successfully dispatched to the service worker, and ServiceWorkerAutoPreload is enabled. This is recorded even in the case when (b) is faster than (a). In this case the value will be 0. The response is from {ServiceWorkerFetchResponseFromName} yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) renderer process sends an IPC message to notify that a resource loading request needs to be fall back to network, to (b) browser process received the IPC. Recorded when no fetch event handler provided a response to the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) renderer process sends an IPC message to notify that a promise of respondWith() is settled, to (b) browser process received the IPC message. Recorded when a fetch event handler handled the request and provided a response to the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) a fetch event is dispatched, to (b) respondWith() is settled for the fetch event, or fetch event dispatch is finished without respondWith() being called. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. The records are breakdown by FetchEventResult. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) a fetch event is dispatched, to (b) respondWith() is settled for the fetch event, or fetch event dispatch is finished without respondWith() being called. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of finding service worker registration, to (b) reading response body is completed. Recorded when a fetch event handler handled the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of finding service worker registration, to (b) browser process received the IPC. Recorded when no fetch event handler provided a response to the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of finding service worker registration, to (b) the start of a navigation request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) a resource loading request is routed to service worker path, to (b) a service worker is ready to handle the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. Please note that this histogram has accidentally changed the bucket definition from 117.0.5874.0. Previously, DEPRECATED_UMA_HISTOGRAM_MEDIUM_TIMES() was used, and it was replaced with base::UmaHistogramMediumTimes(). DEPRECATED_UMA_HISTOGRAM_MEDIUM_TIMES() starts the bucket from 10ms whereas base::UmaHistogramMediumTimes() starts the bucket from 1ms. {EmbeddedWorkerInitialStatus}{NavigationType} chikamune@chromium.org chrome-worker@google.com The initial service worker status. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {NavigationType}{FrameTreeNodeType}{BrowserStartupCompleted} This histogram was skewed between roughly 2024-05-07 and 2024-09-03. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) response headers from service worker are received, to (b) reading response body is completed. Recorded when a fetch event handler handled the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {ServiceWorkerResponseSource} {EmbeddedWorkerInitialStatus} chikamune@chromium.org chrome-worker@google.com Record true if the service worker is waiting for being warmed up. Otherwise record false. Recorded for each navigation request (including redirects) where there is a fetch event handler and service worker is a STOPPED state. chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of a navigation request, to (b) reading response body is completed. Recorded when a fetch event handler handled the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of a navigation request, to (b) browser process received the IPC. Recorded when no fetch event handler provided a response to the request. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of a navigation request, to (b) the request is forwarded to a service worker code path. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) browser process sends an IPC message to dispatch a fetch event, to (b) a renderer process received the IPC message and is about to dispatch a fetch event. Recorded for each navigation request (including redirects) where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. {EmbeddedWorkerInitialStatus} sisidovski@chromium.org chrome-worker@google.com The time taken from (a) the response of the AutoPreload is received, to (b) the fetch handler execution is completed. Recorded for each subresource request where there is a fetch event handler, the fetch event was successfully dispatched to the service worker, and ServiceWorkerAutoPreload is enabled. This is recorded even in the case when (b) is faster than (a). In this case the value will be 0. The response is from {ServiceWorkerFetchResponseFromName} yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) service worker sends a mojo message to notify that a resource loading request needs to be fall back to network, to (b) the mojo message is received on the other side of mojo endpoint (a background thread executing subresource loading). Recorded when no fetch event handler provided a response to the request. Recorded for each subresource request where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) service worker sends a mojo message to notify that a promise of respondWith() is settled, to (b) the mojo message is received on the other side of mojo endpoint (a background thread executing subresource loading). Recorded when a fetch event handler handled the request and provided a response to the request. Recorded for each subresource request where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) a subresource request is routed to the URLLoader (on a background thread) for service worker controlled loads starts handling a subresource request, to (b) a service worker is ready to handle the request. Recorded for each subresource request where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) response headers from service worker are received, to (b) reading response body is completed. Only recorded when a fetch event handler handled the request. Recorded for each subresource request where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken from (a) a fetch event is dispatched, to (b) respondWith() is settled for the fetch event, or fetch event dispatch is finished without respondWith() being called. Recorded for each subresource request where there is a fetch event handler and the fetch event was successfully dispatched to the service worker. chikamune@chromium.org chrome-worker@google.com Loading time of the service worker's top level script. The metric is recorded for each startup of service workers. Recorded only when the loading was {ResultStatus}, and the service worker scripts were {WhetherAlreadyInstalledOrNot}. yyanagisawa@chromium.org chrome-worker@google.com Records the fetch result after the fetch handler has been dispatched. This is recorded after dispatching the fetch event handler to a service worker, and it executed the handler without error (i.e. abort or timeout). yyanagisawa@chromium.org chrome-worker@google.com Records the result of validating a service worker main script request in the browser process. A "forged" result indicates that the renderer process (potentially compromised) sent a request that does not match the expected script URL, destination, or mode. yyanagisawa@chromium.org chrome-worker@google.com Records the purpose for potentially starting a service worker. This is recorded every time a running worker is required whether it needs to be started or not in the ServiceWorkerVersion::RunAfterStartWorker() method. yyanagisawa@chromium.org chrome-worker@google.com Record the current status of a service worker when we need it to be running for some purpose. If the status is STOPPED or STOPPING then the service worker will be started. This is recorded from ServiceWorkerVersion::RunAfterStartWorker(). See also ServiceWorker.MaybeStartWorker.RunningStatusByPurpose_* for the breakdown by event type. yyanagisawa@chromium.org chrome-worker@google.com Record the current status of a service worker when we need it to be running broken down by the purpose for needing a worker. If the status is STOPPED or STOPPING then the service worker will be started. This is recorded from ServiceWorkerVersion::RunAfterStartWorker(). (see ServiceWorker.MaybeStartWorker.RunningStatus for all attempts). yyanagisawa@chromium.org chrome-worker@google.com Records the result of context validation when dispatching an extendable message event to a service worker or client. Recorded every time a message is dispatched. yyanagisawa@chromium.org chrome-worker@google.com The number of fetch handlers registered in a service worker script. This metrics is recorded every time a service worker starts and only includes fetch event handlers registered at script evaluation time. chikamune@chromium.org chrome-worker@google.com Execution time of FindRegistrationForClientUrl until continuation is called. It is recorded only once on browser startup. chikamune@chromium.org chrome-worker@google.com Whether the first navigation requires checking the existence of service worker registration in DB. It is recorded only once on browser startup. yyanagisawa@chromium.org chrome-worker@google.com The type of the fetch handler type to be stored in the database for update. During the start of ServiceWorker, the fetch handler type is decided, and sent via OnStarted. If the fetch handler type is different from the fetch handler type already recognized and stored before, it will eventually be updated when it is read from the database next time. This metrics records the name of the new fetch handler detected. ServiceWorker.OnStarted.UpdatedFetchHandlerTypeBySourceType_* for the breakdown by the source fetch handler type. yyanagisawa@chromium.org chrome-worker@google.com The type of the fetch handler type to be stored in the database for update per the source fetch handler type {SourceType} (See ServiceWorker.OnStarted.UpdatedFetchHandlerType for all attenpts). During the start of ServiceWorker, the fetch handler type is decided, and sent via OnStarted. If the fetch handler type is different from the fetch handler type already recognized and stored before, it will eventually be updated when it is read from the database next time. This metrics records the name of the new fetch handler detected. yyanagisawa@chromium.org chrome-worker@google.com The URL scheme of Clients.openWindow()'s URL argument. This is recorded when the openWindow() is called. smcgruer@chromium.org perryuwang@gmail.com chrome-payments-eng@google.com Records whether a payment handler connection was disconnected due to a timeout. True indicates the disconnect was due to the 20-minute timeout firing, false indicates an external disconnect (e.g., the payment handler window was closed by the user or the payment was completed). This is recorded each time the payment_handler_connected_ flag is set to false. rouslan@chromium.org chrome-payments-eng@google.com zino@chromium.org The time taken between dispatching an PaymentRequestEvent to a Service Worker and receiving a message that it finished handling the event. Includes the time for the waitUntil() promise to settle. nator@chromium.org platform-capabilities@chromium.org The time taken between dispatching a PeriodicSyncEvent to a Service Worker and receiving a message that it finished handling the event. Includes the time for the waitUntil() promise to settle. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The number of StorageKeys that have a service worker registration. Recorded near browser startup, when the service worker storage system is initialized. yyanagisawa@chromium.org chrome-worker@google.com The initiator of a service worker registration deletion. This is recorded when a deletion is triggered. yyanagisawa@chromium.org chrome-worker@google.com The result of deleting a service worker registration. This is recorded when the deletion from the database is complete. The histogram is broken down by the initiator of the deletion. elkurin@chromium.org chrome-storage-team-tokyo@google.com Records whether the checksum of a service worker resource matches the expected checksum. This is used to detect data corruption. Recorded after a service worker resource has been read from the disk, to indicate whether the resource's checksum matches the expected checksum. yyanagisawa@chromium.org chrome-worker@google.com An error that happens in ServiceWorkerRouterEvaluator setup. For calculating an error ratio, no error case is also recorded. This metrics will be recorded per ServiceWorkerRouterEvaluator instance. sisidovski@chromium.org chrome-worker@google.com Time spent for the router evaluation to handle a request. Recorded when the service worker has associated routing info, and the browser or renderer is processing requests. Both main resource and subresource record this metric when being processed. This histogram only records metrics on machines with high-resolution clocks. sisidovski@chromium.org chrome-worker@google.com The result of the router evaluation of the ServiceWorker Static Routing API. This indicates which source type is used to get the resource. This will be recorded only when the router has matched the incoming resource. sisidovski@chromium.org chrome-worker@google.com The sum of registered router rules with the ServiceWorker Static Routing API. Recorded when the service worker, which has associated routing info, is activated. This was broken from 2024-02-07 to 2024-04-07. suzukikeita@chromium.org chrome-worker@google.com Total time spent for the router evaluation to handle a request for the subresources. Recorded when the service worker has associated routing info at the end of each page load or when the page is navigated away, the browser is closed, or on Android when the browser is backgrounded. This histogram only records metrics on machines with high-resolution clocks. yyanagisawa@chromium.org chrome-worker@google.com Whether a resource fetch initiated inside a blob script SharedWorker uses ServiceWorker. This is recorded when an URLLoader is created to fetch resources inside SharedWorker. yyanagisawa@chromium.org chrome-worker@google.com Whether a resource fetch initiated inside a SharedWorker uses ServiceWorker. This is recorded when an URLLoader is created to fetch resources inside SharedWorker. yyanagisawa@chromium.org chrome-worker@google.com Whether a SharedWorker script got via a ServiceWorker is a blob URL or not. This metrics is recorded in the main resource loader intereceptor during the script loading. chikamune@chromium.org chrome-worker@google.com Whether the navigation requires checking the existence of service worker registration by using FindRegistrationForClientUrl(). This metric is not recorded during startup. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken to start a Service Worker that has not yet installed, from process allocation to ACK of started from the renderer (which occurs after script execution). This may include script download time. The metric is not recorded if DevTools was ever attached to the Service Worker during startup. See also ServiceWorker.StartWorker.Time for installed workers. This histogram was expired between approximately Feb through Sep 2021. yyanagisawa@chromium.org chrome-worker@google.com Recorded on each successful service worker startup. ServiceWorker.StartTiming.* uses timing data from both the renderer process and browser process. This histogram describes whether the clocks are known to be accurate and consistent accross processes, and whether the actual timing data for this worker startup was consistent, i.e., TimeTicks did not go backwards. If the clocks and timing were inconsistent, ServiceWorker.StartTiming.* metrics (other than this one) are not recorded. This histogram was expired between roughly 2021-07-30 and 2021-09-31. {ServiceWorker_StartSituation2} yyanagisawa@chromium.org chrome-worker@google.com The time taken to start a service worker that is already installed, from start of the start sequence (finding a renderer) to ACK of started from the renderer (which occurs after script execution). The metric is not recorded if DevTools was ever attached to the Service Worker during startup. It does not include time, if any, waiting for the service worker to finish stopping before asking it to start, if that occurred. This histogram was expired between roughly 2021-07-30 and 2021-09-31. {ServiceWorker_StartSituation2} yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) the renderer receiving the start worker IPC message, to (b) initial JavaScript evaluation starting on the worker thread. Recorded when ServiceWorker.StartTiming.Duration is recorded. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) initial JavaScript evaluation finishing on the worker thread, to (b) the browser receiving the worker started IPC message (the final step of worker startup). Recorded when ServiceWorker.StartTiming.Duration is recorded. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) initial JavaScript evaluation starting on the worker thread, to (b) initial JavaScript evaluation finishing on the worker thread. Recorded when ServiceWorker.StartTiming.Duration is recorded. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) the browser sending the start worker IPC message, to (b) the renderer receiving the start worker IPC message. Recorded when ServiceWorker.StartTiming.Duration is recorded. chikamune@chromium.org chrome-worker@google.com The time taken from (a) the start of service worker startup, to (b) the renderer receiving the start worker IPC message. Recorded when ServiceWorker.StartTiming.Duration is recorded. This histogram was expired between roughly 2021-07-30 and 2021-09-31. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) the start of service worker startup, to (b) initial JavaScript evaluation finishing on the worker thread. Recorded when ServiceWorker.StartTiming.Duration is recorded. This histogram was expired between roughly 2021-07-30 and 2021-09-31. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) the start of service worker startup, to (b) initial JavaScript evaluation starting on the worker thread. Recorded when ServiceWorker.StartTiming.Duration is recorded. This histogram was expired between roughly 2021-07-30 and 2021-09-31. yyanagisawa@chromium.org chrome-worker@google.com The time taken from (a) the start of service worker startup, to (b) the browser sending the start worker IPC message. Recorded when ServiceWorker.StartTiming.Duration is recorded. yyanagisawa@chromium.org chrome-worker@google.com Records the difference between the legacy scope-based validation and the newer StorageKey-based validation when starting a service worker. Recorded every time IsStartWorkerAllowed is evaluated. yyanagisawa@chromium.org chrome-worker@google.com The purpose for starting up a service worker. Recorded only for installed workers. This histogram was expired between approximately Feb through Sep 2021. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The result of trying to start a Service Worker that is already installed. See also ServiceWorker.StartNewWorker.Status for new workers. See also ServiceWorker.StartWorker.StatusByPurpose_* for the breakdown by event type. yyanagisawa@chromium.org chrome-worker@google.com The result of trying to start a service worker for the event type {ServiceWorkerEventType} (see ServiceWorker.StartWorker.Status for all start attempts). Only recorded for installed workers. chikamune@chromium.org chrome-worker@google.com Records the start purpose for a service worker that timed out while starting up. Recorded only for installed workers. This histogram was expired between approximately Feb through Sep 2021. chikamune@chromium.org chrome-worker@google.com The phase the ServiceWorker was in when ServiceWorker startup timed out. This histogram was expired between approximately Feb through Sep 2021. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken to start a Service Worker that is already installed, from process allocation to ACK of started from the renderer (which occurs after script execution). The metric is not recorded if DevTools was ever attached to the Service Worker during startup. See also ServiceWorker.StartNewWorker.Time for new workers. {ServiceWorker_StartSituationDoNotUse} yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com The time taken to start a Service Worker that is already installed, from process allocation to ACK of started from the renderer (which occurs after script execution). The metric is not recorded if DevTools was ever attached to the Service Worker during startup. See also ServiceWorker.StartNewWorker.Time for new workers. {ServiceWorker_StartSituationDoNotUse} {ServiceWorkerEventType} suzukikeita@chromium.org chrome-worker@google.com Time spent to conduct cache lookup. Recorded when the service worker has associated routing info with the `cache` as the rule, and the browser or renderer is processing requests. This metric is recorded for {Resource}. This histogram only records metrics on machines with high-resolution clocks. yyanagisawa@chromium.org chrome-worker@google.com Records the cache storage error when the cache source is set by a rule for the ServiceWorker static routing API and the cache storage match call returns a status instead of a result. This metric is recorded for {Resource}. yyanagisawa@chromium.org chrome-worker@google.com Records the result of the Cross-Origin Resource Policy (CORP) check for responses from the ServiceWorker Static Routing API with source: 'cache'. This metric is recorded for {Resource}. yyanagisawa@chromium.org chrome-worker@google.com Records whether a response from the ServiceWorker Static Routing API with source: 'cache' is valid according to the Fetch spec (4.4 HTTP fetch, Step 3.5.6). If it's invalid, it is a security risk and should be blocked. yyanagisawa@chromium.org chikamune@chromium.org chrome-worker@google.com Records result of storage recovery operations in ServiceWorkerStorage. chikamune@chromium.org chrome-worker@google.com The scope count for a given StorageKey. This is recorded when ServiceWorkerStorage::FindForClientUrlInDB() function is called. chikamune@chromium.org chrome-worker@google.com Execution time of ServiceWorkerStorage::FindForClientUrlInDB which is used by FindRegistrationForClientUrl. chikamune@chromium.org chrome-worker@google.com Records successes and failures of purging a stale resource in ServiceWorkerStorage. chikamune@chromium.org chrome-worker@google.com Execution time of ServiceWorkerStorage::ReadInitialDataFromDB which reads RegisteredStorageKey from a database. chikamune@chromium.org chrome-worker@google.com The cache creation time of service worker registration key on UI thread. Includes asynchronous call, thread hopping and the time of ServiceWorker.Storage.ReadInitialDataFromDB.Time. This is only recorded on the browser startup. yyanagisawa@google.com chrome-worker@google.com Type of subresources that is controlled with a service worker, but did not handled by a service worker (i.e. did not get replied via respondWith). This metric is taken every time a subresource load finishes. See ServiceWorker.Subresource.Handled.Type for handled cases. yyanagisawa@google.com chrome-worker@google.com Type of subresources that is controlled with a service worker, and handled by a service worker (i.e. get replied via respondWith). This metric is taken every time a subresource load finishes. See ServiceWorker.Subresource.Fallbacked.Type for fallbacked cases. sisidovski@chromium.org chrome-worker@google.com Records true when OnConnectionClosed() is called and the fetch request is restarted in the ServiceWorkerSubresourceLoader. Recorded in the destructor of ServiceWorkerSubresourceLoader. This helps measure how often the connection to the service worker gets disconnected while handling a subresource fetch event. sisidovski@chromium.org chrome-worker@google.com The type of inline resource, that is blocked by Content Security Policy when the synthetic response is enabled before receiving a Content Security Policy in a meta tag. This is recorded when the inline resource is blocked by the synthetic response. sisidovski@chromium.org chrome-worker@google.com The total count of blocked resources by the synthetic response. This is recorded, once per document/page, when the synthetic response is enabled and at the time when the first Content Security Policy delivered in a meta tag is parsed. Measures the count of resources that have been blocked by Content Security Policy because of synthetic response until that point. sisidovski@chromium.org chrome-worker@google.com The type of source of scripts that is blocked by the synthetic response. This is recorded when the resource from the source is blocked by the synthetic response. sisidovski@chromium.org chrome-worker@google.com Records whether navigation request embedders (e.g. WebRequest API for extensions) handle redirect security checks. This is recorded when the network request is initiated in the browser process for the synthetic response. sisidovski@chromium.org chrome-worker@google.com Records the eligibility of the synthetic response. This is recorded when the main resource request is handled in ServiceWorker, and the page is avalable to use the synthetic response. sisidovski@chromium.org chrome-worker@google.com Records whether the search prefetch cache is found. This is recorded when the synthetic response is considered being handled, but before actually starting it. sisidovski@chromium.org chrome-worker@google.com Records whether the response headers are successfully stored to the memory. This is recorded in navigation, when the browser receives the response from the network, and there is no stored header locally yet for the synthetic response. sisidovski@chromium.org chrome-worker@google.com Records whether the shared producer pipe is valid when handling an intercepted network response. This is recorded in navigation, when the browser receives the response from the network, while committed the navigation with locally stored headers and when the network service delegation mode is enabled. If this is true, the data pipe producer handle provided to the network service is still valid. sisidovski@chromium.org chrome-worker@google.com Records whether a valid response body handle is provided from URLLoader. This is recorded in navigation, when the browser receives the response from the network, while committed the navigation with locally stored headers. If this is true, the URLLoader provided a valid response body handle. sisidovski@chromium.org chrome-worker@google.com Records the time from (a) the client receives the network response to (b) completes the response time. This is recorded in navigation, when the browser receives the response from the network, while committed the navigation with locally stored headers. sisidovski@chromium.org chrome-worker@google.com Records the reason why the browser reloads the page when a synthetic response is about to be served. This is recorded in navigation, when the browser receives the response from the network, but the browser tell the custom response to reload the page to the renderer for some fallback case e.g. header mismatch. sisidovski@chromium.org chrome-worker@google.com Records the time from (a) the loader starts a network request to (b) it receives the response. This is recorded in navigation, when the browser receives the response from the network, while committed the navigation with locally stored headers. sisidovski@google.com chrome-worker@google.com Records the MojoResult returned by WriteData() when writing the synthetic response fallback body. sisidovski@chromium.org chrome-worker@google.com The result of the checksum update operation. Each ServiceWorker resource should have a sha256 cehcksum hash string in the database, and that will be updated when there is a change in ServiceWorker scripts, or the field is empty. sisidovski@chromium.org chrome-worker@google.com Records the number of interceptors involved in the URLLoaderFactory creation for the main resource request in ServiceWorkerClient. This is recorded when a navigation request is initiated by the service worker (e.g., navigation preload, synthetic response). hchao@chromium.org cthomp@chromium.org chrome-secure-web-and-net@google.com How many times a service worker navigates a WindowClient, and the IP address space of the WindowClient's current page does not match the IP address space of the Service Worker. A value of 'true' indicates that the IP address spaces did not match. yyanagisawa@google.com chrome-worker@google.com True if the workaround for crbug.com/1342408 has been applied. Otherwise, false. The workaround is applied when the response stream call back is called. This information is used to understand if we need to continue this workaround or not. ayui@chromium.org chrome-owp-storage@google.com The time to perform a 'match' operation on a given Cache when that cache is known to be fully initialized. This includes measurements for hits, misses, and errors. ayui@chromium.org chrome-owp-storage@google.com The time to perform a 'match' operation on a given Cache when the operation was initiated from a service worker currently processing a FetchEvent with a matching request URL. This includes measurements for hits, misses, and errors. ayui@chromium.org chrome-owp-storage@google.com Histogram for the ServiceWorker Cache API. {MatchType} This histogram was temporarily disabled from M96 through early 12/2021. ayui@chromium.org chrome-owp-storage@google.com Histogram for the ServiceWorker Cache API. {ProcessOps} This histogram was temporarily disabled from M96 through early 12/2021. elkurin@chromium.org chrome-storage-team-tokyo@google.com Records the actual delayed time on completing CacheStorage APIs. The value is Time (in ms) added to run CacheStorage used for ablation study purposes. ayui@chromium.org chrome-owp-storage@google.com Histogram for the ServiceWorker Cache API. {ProcessOps} This histogram was temporarily disabled from M96 through early 12/2021. ayui@chromium.org chrome-owp-storage@google.com Records where the generic kErrorStorage value is triggered within the cache_storage code. This histogram was temporarily disabled from late 10/2021 to early 12/2021. ayui@chromium.org chrome-owp-storage@google.com The result from parsing and validating the index protobuf while calculating the list of cache_storage origins. ayui@chromium.org chrome-owp-storage@google.com The time in ms from when an operation is started until it completes. This histogram differs from the old OperationDuration in that it uses a different bucket size to measure longer values. ayui@chromium.org chrome-owp-storage@google.com The time in ms from when an operation is started until it completes. This histogram differs from the old OperationDuration in that it uses a different bucket size to measure longer values. ayui@chromium.org chrome-owp-storage@google.com The number of operations in the scheduling queue just before enqueuing a new operation. ayui@chromium.org chrome-owp-storage@google.com The time in ms from when an operation is started until it completes for the {ServiceWorkerCacheSchedulerOpClientType} instance. ayui@chromium.org chrome-owp-storage@google.com The time in ms from when an operation is started until it completes for the {ServiceWorkerCacheSchedulerOpClientType} instance. ayui@chromium.org chrome-owp-storage@google.com The number of operations in the scheduling queue just before enqueuing a new operation for the {ServiceWorkerCacheSchedulerOpClientType} instance. yyanagisawa@chromium.org chrome-worker@google.com The time in ms for setting up the devtools agent for the dedicated worker to trace the dedicated worker script fetch. yyanagisawa@chromium.org chrome-worker@google.com The time in ms from when a dedicated worker host is created inside the browser process until when the script is started to load in the browser process. yyanagisawa@chromium.org chrome-worker@google.com The time in ms for creating a DedicatedWorkerHost in the browser process. The time include all procedures that is needed for creating the DedicatedWorkerHost. yyanagisawa@chromium.org chrome-worker@google.com If PlzDedicatedWorker is enabled, DedicatedWorkerDebToolsAgent will be created and kept in the WorkerDevtoolsManager. This metric shows the number of the agent kept in the manager. The metric is recorded when the new entry is created, which correspond to timing when the Worker.BrowserProcess.DevToolsCreateTime metric is recorded. Therefore, it can be used for good understanding on how the number of entries affect the devtools agent creation time. yyanagisawa@chromium.org chrome-worker@google.com The time in ms from when a dedicated worker starts to fetch a classic script until the script starts to be evaluated. The value can only be taken for PlzDedicatedWorker. yyanagisawa@chromium.org chrome-worker@google.com The time in ms from when a worker thread initialization starts until the dedicated worker global scope is going to be made. This does not include the global scope creation time. Unfortunately, this does not measure a time from worker thread creation. It just measures from when the initialization starts. yyanagisawa@chromium.org chrome-worker@google.com The time in ms from when a dedicated worker starts until the script load started. This includes PlzDedicatedWorker to offload starting to fetch a script in the browser process. However, fetching contents are excluded from this time. yyanagisawa@chromium.org chrome-worker@google.com The time in ms from when a dedicated worker starts until the worker script fetch finished. This includes PlzDedicatedWorker to offload starting to fetch a script in the browser process. It does not include the initial evaluation of the script. yyanagisawa@chromium.org chrome-worker@google.com The time in ms from when a dedicated worker starts until the worker host creation callback is called from the browser process. This roughly means IPC turn-around time betweeen the renderer process and the browser process.