chadduffin@google.com cros-device-enablement@google.com Records the policy text message suppression state. This is emitted whenever the text message suppression value is changed via policy. chadduffin@google.com cros-device-enablement@google.com Records the received text message notification suppression state. This is emitted whenever a text message notification is received. chadduffin@google.com cros-device-enablement@google.com Records the user text message suppression state. This is emitted whenever the text message suppression value is changed by the user. nikhilcn@google.com cros-device-enablement@google.com Records the state of AllowApnModification policy while creating a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the APN types of an APN. This is emitted each time a user creates a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the authentication type of an APN. This is emitted each time a user creates a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the IP type of an APN. This is emitted each time a user creates a custom APN. nikhilcn@google.com cros-device-enablement@google.com Deprecated. Records the result of an attempt to create a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the result of an attempt to create a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records shill errors of an attempt to create a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the APN types of an APN. This is emitted each time a user creates an exclusively enabled custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the authentication type of an APN. This is emitted each time a user creates an exclusively enabled custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the IP type of an APN. This is emitted each time a user creates an exclusively enabled custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the result of an attempt to create an exclusively enabled custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the number of APNs saved for a cellular network every time a cellular network successfully connects. nikhilcn@google.com cros-device-enablement@google.com Records the number of {CustomApnState} APNs saved for a cellular network every time a cellular network successfully connects. nikhilcn@google.com cros-device-enablement@google.com Records the APN types of an APN before modification. This is emitted each time a user disables a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the result of an attempt to disable a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the APN types of an APN before modification. This is emitted each time a user enable a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the result of an attempt to enable a custom APN. nikhilcn@chromium.org cros-device-enablement@google.com Tracks the state of AllowApnModification policy at login. hsuregan@google.com nikhilcn@google.com cros-device-enablement@google.com Records the type of migration that occurs for each APN that's migrated for managed devices. This metric is emitted when a managed network is migrated from the old APN UI to new APN UI. nikhilcn@google.com cros-device-enablement@google.com Records the state of AllowApnModification policy while modifying a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the APN types of an APN before modification. This is emitted each time a user modifies a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the result of an attempt to modify a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the state of AllowApnModification policy when the policy is applied on the device. nikhilcn@google.com cros-device-enablement@google.com Records the state of AllowApnModification policy while removing a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the APN types of an APN. This is emitted each time a user removes a custom APN. nikhilcn@google.com cros-device-enablement@google.com Records the result of an attempt to remove a custom APN. hsuregan@google.com nikhilcn@google.com cros-device-enablement@google.com Records the type of migration that occurs for each APN that's migrated for unmanaged devices. This metric is emitted when an unmanaged network is migrated from the old APN UI to new APN UI. hsuregan@chromium.org cros-device-enablement@google.com Tracks the type of cellular configuration failures that occur when connecting to a cellular network. nikhilcn@google.com cros-device-enablement@google.com Tracks the result of network connection attempts for cellular networks and whether they have at least one enabled custom APN or not. A success is emitted when a cellular network becomes connected from a non-connected state. When a cellular network goes from a connecting state to a disconnected state without a user initiated disconnect, a shill failure reason is emitted. chadduffin@chromium.org cros-device-enablement@google.com Records when a step in the installation of an eSIM profile is reached. Each installation attempt is expected to emit to multiple buckets, e.g. installation started and installation succeeed, and may emit to particular buckets more than once, e.g. installation retried. chadduffin@chromium.org cros-device-enablement@google.com Records the method of installation used to attempt to install an eSIM profile. This is emitted once for each initial installation attempt of the eSIM profile corresponding to a policy-defined network. chadduffin@chromium.org cros-device-enablement@google.com Records the method of installation used to attempt to install an eSIM profile. This is emitted once for each installation attempt of the eSIM profile corresponding to a policy-defined network, and is only emitted if the scan performed to find profiles matching the provided activation code finds no available profiles. chadduffin@chromium.org cros-device-enablement@google.com Records the result of an attempt to install an eSIM profile. This is emitted once for each installation attempt of the eSIM profile corresponding to a policy-defined network. The "included" variant will always be emitted to; the "filtered" variant, however, will not be emitted to when the result was due to an Hermes failure that was caused by something outside the control of ChromeOS, e.g. an invalid activation code. chadduffin@chromium.org cros-device-enablement@google.com Tracks the number of eSIM profiles discovered by SM-DS scans. This will be emitted once for each installation attempt; this means that if multiple SM-DS servers are scanned for an installation attempt the count emitted will be the total number of profiles discovered across all scanned servers. chadduffin@chromium.org cros-device-enablement@google.com Records the result of a single SM-DS scan of a single SM-DS server. The {SmdsType} token indicates the type of SM-DS server that was scanned, and the {UserErrorHandling} token indicates the result filtering used, if any. The "included" variant will always be emitted to; the "filtered" variant, however, will not be emitted to when the result was due to an Hermes failure that was caused by something outside the control of ChromeOS, e.g. an invalid activation code. chadduffin@google.com cros-device-enablement@google.com Tracks the time taken to perform a single SM-DS scan of a single SM-DS server. The {SmdsType} token indicates the type of SM-DS server that was scanned, and the {DurationType} token indicates whether this duration was for a scan that completed with a Hermes result that indicates a non-fatal error occurred. An error does not necessarily indicate that the scan failed, but does indicate that there was an issue when performing the scan, e.g., there was an issue with one of the profiles discovered. chadduffin@chromium.org cros-device-enablement@google.com Records the method of installation used to attempt to install an eSIM profile. This is emitted once for each installation attempt of an eSIM profile using the consumer UI. chadduffin@chromium.org cros-device-enablement@google.com Records the result of an attempt to install an eSIM profile. This is emitted once for each installation attempt of an eSIM profile using the consumer UI. The "included" variant will always be emitted to; the "filtered" variant, however, will not be emitted to when the to when the result was due to an Hermes failure that was caused by something outside the control of ChromeOS, e.g. an invalid activation code. hsuregan@chromium.org nikhilcn@chromium.org cros-device-enablement@google.com Records events on the notification shown when the SIM is locked and admin has restricted users from PIN locking their SIMs. These are emitted once the notification is shown and once when the user interacts with it. hsuregan@chromium.org nikhilcn@chromium.org cros-device-enablement@google.com Records the type of SIM lock affecting a cellular network when a user is notified that the cellular network is SIM locked. hsuregan@chromium.org nikhilcn@chromium.org cros-device-enablement@google.com Records the status of the SIM (Unlocked/PIN Locked/PUK Blocked) upon a change in cellular connection. This metric will be recorded upon following transitions: 1. no connection to new connection; 2. connection_1 to connection_2 hsuregan@google.com cros-device-enablement@google.com Tracks the technology type of the default network, which considers the technology type and whether the network is metered. The default network here means the first default/active non VPN network. Note that this metric is recorded whenever the default network changes or when the metered property changes. Note that if the default/active network drops and then reconnects without another network taking its place, this metric will not be emitted. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the result of setting hotspot configuration. Emitted whenever attempts to update hotspot configuration. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the hotspot allow status on the cellular-capable devices. This metric is emitted each time the allow status is updated, for example: when user connects/disconnect to a cellular network, enterprise policy applied, etc. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the hotspot allow status on the cellular-capable devices only when user logins in. This metric is emitted after a 5 minutes delay when user login which gives the user enough time to connect to their upstream cellular network. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the result of checking tethering readiness. Emitted whenever attempts to check tehtering readiness, for exmaple: when cellular network get connected or when enable hotspot. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the causes of disabled hotspot. Emitted each time the hotspot becomes disabled. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the upstream status the when hotspot is start up. Emitted each time the hotspot starts successfully. jiajunz@google.com cros-device-enablement@google.com Tracks how long the user needs to wait once the hotspot is requested to turn on until the hotspot is ready to use. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the number of whether the hotspot auto disable configuration is set for usage. Emitted each time the hotspot starts successfully. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the number of whether the hotspot extend compatibility mode is set for usage. Emitted each time the hotspot starts successfully. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the number of whether the hotspot BSSID randomization configuration is set for usage. Emitted each time the hotspot starts successfully. jiajunz@google.com cros-device-enablement@google.com Tracks how long users use hotspot per session. Emitted whenever the hotspot is torn down. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the number of the hotspot being used on a managed device or not. Emitted each time the hotspot starts successfully. jiajunz@google.com cros-device-enablement@google.com Records the number of maximum connected device count per hotspot session. Emitted whenever the hotspot session is torn down. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the result of turning on/off hotspot. Emitted whenever attempts to enabled/disabled hotspot. chadduffin@chromium.org cros-device-enablement@google.com Logs the configuration source (i.e., the user vs. policy) for VPN networks. Emitted when a VPN is configured. chadduffin@chromium.org cros-device-enablement@google.com Records the number of WiFi networks that were determined to be wrongly configured as hidden and were attempted to be removed. This metric will be emitted each time we check for wrongly configured networks which happens once at startup and each time the primary user changes. chadduffin@chromium.org cros-device-enablement@google.com Records the result of an attempt to remove a WiFi network that was determined to be wrongly configured as hidden. This metric will be emitted for each network we attempt to remove if and when we are notified of the result of our removal request; while it is safe to expect that we will be notified most of the time, we are not guaranteed to be notified. These network removals will occur once at startup and each time the primary user changes. chadduffin@chromium.org cros-device-enablement@google.com Logs whether the network in question is configured as hidden or not. Emitted when a network is newly configured. Note: This histogram was wrongly emitted for all network configurations when it should have only been emitted for new network configurations. This issue was resolved on 2023-07-19. jiajunz@google.com cros-device-enablement@google.com Emitted whenever client queries the WiFi Direct capabilities. jiajunz@google.com cros-device-enablement@google.com Tracks the duration of each Wifi P2P connection. Emits when the connection is torn down. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the result of the tag socket operation. Emitted whenever the operation is attempted. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the disconnect reason of {GroupType} P2P connection. Emitted when the {GroupType} P2P connection disconnects. jiajunz@google.com cros-device-enablement@google.com Measures and tracks the result of {Operation} operation. Emitted whenever {Operation} operation is attempted. jiajunz@google.com cros-device-enablement@google.com Tracks the result of automatic Network connection attempts. A success is emitted when a network of type {NetworkType} becomes connected from a non-connected state without user action. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of a user initiated connection attempt. Logged when a network of type {NetworkType} connection succeeds or fails. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of all Network connection attempts, it also tracks tracks non repeated connection errors. A success is emitted when a network of type {NetworkType} becomes connected from a non-connected state. When a network of type {NetworkType} goes from a connecting state to a disconnected state without a user initiated disconnect, a shill failure reason is emitted. {Filtering} is not emitted if the network has if the current error is the same as the previous error. hsuregan@chromium.org cros-device-enablement@google.com Tracks when a network of type {NetworkType} is connected and when a network of type {NetworkType} is disconnected without explicit user action. chadduffin@chromium.org cros-device-enablement@google.com Tracks the Shill error provided as the disconnection reason when a network of type {NetworkType} becomes disconnected without any user interaction. hsuregan@chromium.org cros-device-enablement@google.com Tracks the rate of success of performing the {Operation} operation on the shill associated {TechnologyType} technology type. nikhilcn@chromium.org cros-device-enablement@google.com This metric is emitted when users perform {Operation} operation on the {TechnologyType} technology. We capture all result codes returned by the platform API. ricea@chromium.org src/net/OWNERS The time elapsed between the start of a brokered TCP socket creation request and when the socket is received by the network service. This is recorded once for every brokered TCP socket that is created. The histogram is not reported on Windows machines without high resolution clocks. ricea@chromium.org src/net/OWNERS The time elapsed between the start of a brokered UDP socket creation request and when the socket is received by the network service. This is recorded once for every brokered UDP socket that is created. The histogram is not reported on Windows machines without high resolution clocks. stevenjb@chromium.org cros-network-health-team@google.com The Shill network state received by Chrome when a network is connected, or when the connection state changes, including portal state. hsuregan@chromium.org cros-device-enablement@google.com ChromeOS cellular network metric that tracks the Attach APN Toggle value when the user explicitly clicks the Save button in the 'Other' APN settings, with the intent of setting the cellular network APN properties. ujjwalpande@google.com cros-cellular-core@google.com Emitted each time Carrier Lock Manager was successfully initialized and a new configuration process was started (only when Manager is not disabled and device has cellular modem). ujjwalpande@google.com cros-cellular-core@google.com Emitted every time the error occurs during manager initialization, modem seup, OOBE stage or communication with FCM, PSM and provisioning servers. ujjwalpande@google.com cros-cellular-core@google.com Emitted each time registration or subscription to FCM topic was successful. ujjwalpande@google.com cros-cellular-core@google.com Emitted on every notification received from FCM service. ujjwalpande@google.com cros-cellular-core@google.com Emitted every time the Initialization step is triggered. Reports number of events from each trigger group. ujjwalpande@google.com cros-cellular-core@google.com Emitted when the property SimLockStatus was updated. State of LockType will tell if the modem is carrier-locked (but only if an incompatible SIM is inserted) and the internal disable flag of Carrier Lock Manager will tell whether the modem should be configured. ujjwalpande@google.com cros-cellular-core@google.com Emitted each time the modem was successfully configured. ujjwalpande@google.com cros-cellular-core@google.com Emits current number of failures every time the error counter (any cause of failure) reaches multiple of 10. It will help detect false negative (modem unlocked and config locked) failure which can happen when the modem was not properly configured. ujjwalpande@google.com cros-cellular-core@google.com Emitted each time lock configuration was downloaded from Provisioning server. ujjwalpande@google.com cros-cellular-core@google.com Emitted each time PSM service was requested about device membership. ujjwalpande@google.com cros-cellular-core@google.com Emitted when the modem was successfully locked or unlocked. It reports the cumulative number of attempts made before successful configuration. khorimoto@chromium.org cros-device-enablement@google.com Tracks the success rate of disabling an eSIM profile. Note that the result for "already disabled" is considered a success for this metric. Emitted once the operation completes. khorimoto@chromium.org cros-device-enablement@google.com Tracks the success rate of enabling an eSIM profile. Note that the result for "already enabled" is considered a success for this metric. Emitted once the operation completes. nikhilcn@chromium.org hsuregan@chromium.org cros-device-enablement@google.com This metric is emitted when user attempts to install an eSIM profile. We record all hermes response status codes that are within our control. User and Carrier related errors such as invalid qr code, malformed carrier response are omitted. This will be used to measure the success rate of installing an eSIM profile when the input is valid and external dependencies are operating without errors. Emitted once the operation completes. khorimoto@chromium.org cros-device-enablement@google.com Tracks the success rate of installing a "pending" eSIM profile found via SM-DS. SM-DS provides all profiles which a carrier has associated with a device's EID; once this occurs, the user has the chance to install one of these pending profiles via the UI. The installation process involves making a network request to the cellular carrier and downloading a profile to the device. Emitted once the operation completes. nikhilcn@chromium.org khorimoto@chromium.org cros-device-enablement@google.com Tracks the dbus result for all eSIM installation attempts. This gets logged only if we receive an unknown hermes response code. Emitted once the operation completes. khorimoto@chromium.org cros-device-enablement@google.com Tracks the success rate of installing an eSIM profile via a QR code. During this process, the user can either scan a QR code by using the device's webcam or can enter the QR code's decoded contents into a text field manually. Once this occurs, the device contacts the cellular carrier and downloads a profile to the device. Emitted once the operation completes. jiajunz@google.com cros-device-enablement@google.com Tracks how often the admin allows only managed cellular networks to connect. This metric is logged for managed, cellular-capable devices when the primary user logs in or when there is an update to the allowOnlyPolicyCellularNetworks policy. hsuregan@chromium.org jiajunz@google.com cros-device-enablement@google.com Tracks the result of all connection attempts. A success is emitted when a managed eSIM network becomes connected from a non-connected state. When a managed eSIM network goes from a connecting state to a disconnected state, a shill failure reason is emitted. jiajunz@google.com cros-device-enablement@google.com Tracks when a managed eSIM cellular network is connected and when a managed eSIM cellular network is disconnected without explicit user action. jiajunz@google.com cros-device-enablement@google.com Tracks the result of an attempt to upload euicc status to DM server. This metric provides the insights on how often ICCID/SM-DP+ get uploaded to the DM server and whether the upload operation is successful or not. Emitted once the euicc status upload operation completes. jiajunz@google.com cros-device-enablement@google.com Tracks the amount of time taken to complete reset euicc operation. jiajunz@google.com cros-device-enablement@google.com Tracks the result of an attempt to reset euicc. This process includes both an attempt to inhibit modem scans as well as a request to reset EUICC. The metric tracks failures at each step of the process. Emitted once the operation completes. jiajunz@google.com cros-device-enablement@google.com Tracks how many managed eSIM profiles are installed on the devices after a primary user login. jiajunz@google.com cros-device-enablement@google.com Tracks status of managed eSIM cellular networks on the device. The status indicates whether the device has managed or only non-managed or both types of cellular networks. This is logged for managed cellular capable devices when the primary user logs in. This allows us to track what fraction of cellular network usage are controlled by policy. jiajunz@google.com cros-device-enablement@google.com Tracks the number of times a managed eSIM cellular network is connected as the only network, or with other network or not connected at all. hsuregan@chromium.org jiajunz@google.com cros-device-enablement@google.com Tracks how long users are using a managed eSIM cellular network as the sole network for connectivity on their device. hsuregan@chromium.org cros-device-enablement@google.com Tracks the time for a profile to be fully downloaded from a provided activation code. This histogram was updated on 11/16/23 to only start counting how long it takes to install a profile until AFTER we inhibit the cellular device. hsuregan@chromium.org cros-device-enablement@google.com Tracks the time for a pending profile to be fully downloaded. hsuregan@chromium.org cros-device-enablement@google.com Tracks the rate of success of setting a profile nickname. hsuregan@chromium.org cros-device-enablement@google.com Tracks the rate of success of uninstalling a profile. nikhilcn@chromium.org cros-device-enablement@google.com Tracks the latency of call to SMDS server. This is emitted when a known or installed profile is refreshed. Call latency is calculated and emitted upon completion of the platform call. khorimoto@chromium.org cros-device-enablement@google.com Tracks the result of an attempt to request pending eSIM profiles (i.e., those found via an SM-DS scan). This process includes both an attempt to inhibit modem scans as well as a request for the profiles. The metric tracks failures at each step of the process. Emitted once the operation completes. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of the eSIM setup flow when the setup dialog closes. hsuregan@chromium.org cros-device-enablement@google.com Tracks the ESim Cellular network profile status when the primary user logs-in to the device. khorimoto@chromium.org cros-device-enablement@google.com Tracks the result of the high-level operation of uninstalling an eSIM profile. This includes several steps before and after the core step of uninstalling the profile. Emitted once the operation completes. khorimoto@chromium.org cros-device-enablement@google.com Tracks the success rate of uninstalling an eSIM profile. Emitted once the operation completes. khorimoto@chromium.org cros-device-enablement@google.com Tracks the number of times a ESim cellular network is connected as the only network, or with other network or not connected at all. khorimoto@chromium.org cros-device-enablement@google.com Tracks the result of a cellular device inhibit-uninhibit cycle. Emitted when uninhibit completes or when any step fails. hsuregan@chromium.org cros-device-enablement@google.com Tracks the rate of success of various pin operations. Note: This histogram was expired from 2022-03-01 to 2022-03-23; data may be missing. khorimoto@chromium.org cros-device-enablement@google.com Tracks the result of the high-level operation of preparing a cellular network for a connection. For eSIM networks, this involves several steps such as enabling the profile, each of which can fail or succeed. Emitted once the operation completes. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of attempting to activate a physical SIM card via an Over the Air (OTA) activation. Emitted once the operation completes. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of the physical SIM card setup flow when the setup dialog closes. hsuregan@chromium.org cros-device-enablement@google.com Tracks the PSim Cellular network activation state when the primary user logs-in to the device. khorimoto@chromium.org cros-device-enablement@google.com Tracks the number of times an PSim cellular network is connected as the only network, or with other network or not connected at all. nikhilcn@chromium.org hsuregan@chromium.org cros-device-enablement@google.com Sim PIN Lock policy is applied by enterprise administrators when they want to restrict their users from locking or changing the PIN of their SIM. This metric tracks instances where users have been able to successfully execute lock or change PIN operations on their SIM while this policy is turned on. hsuregan@chromium.org cros-device-enablement@google.com Tracks the time taken by the user to complete Cellular setup flow of a {SimType} network with result {Result}. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of all connection attempts. A success is emitted when a {SimType} network becomes connected from a non-connected state. When a {SimType} network goes from a connecting state to a disconnected state, a shill failure reason is emitted. Warning: this histogram was expired from 2022-10-01 to 2023-02-28; data may be missing. hsuregan@chromium.org cros-device-enablement@google.com Tracks the result of a user initiated connection attempt. Logged when a {SimType} connection succeeds or fails. This histogram logs failure reasons exposed by NetworkConnectionHandler. jiajunz@google.com cros-device-enablement@google.com Tracks the rate of success of disconnecting the connected unmanaged {SimType} networks when restricting cellular networks is enforced by policy. khorimoto@chromium.org cros-device-enablement@google.com Tracks when cellular {SimType} network is connected and when cellular network is disconnected without explicit user action. Note: This histogram was expired from 2022-03-01 to 2022-03-23; data may be missing. khorimoto@chromium.org cros-device-enablement@google.com Tracks the number of cellular networks that are {SimType} available to the device after a primary user logs in, {PolicyState}. hsuregan@chromium.org cros-device-enablement@google.com Tracks the amount fo time taken between when cellular device starts and finishes connecting for {SimType} networks. hsuregan@chromium.org cros-device-enablement@google.com Tracks how long users are using a {SimType} cellular network as the sole network for connectivity on their device. horo@chromium.org blink-network-stack@google.com Result of creating the Mojo data pipe used between the decoding thread and the data receiving thread for the RendererSideContentDecoding feature. Recorded whenever the renderer process receives a resource that needs to be decoded, or content decoding is intercepted for downloads initiated via navigation or for Signed Exchange (SXG) responses and when RendererSideContentDecoding feature is enabled. horo@chromium.org blink-network-stack@google.com The time taken to create the Mojo data pipe used between the decoding thread and the data receiving thread for the RendererSideContentDecoding feature. Recorded whenever the renderer process successfully creates the data pipe for a resource that needs to be decoded, or content decoding is intercepted for downloads initiated via navigation or for Signed Exchange (SXG) responses and when RendererSideContentDecoding feature is enabled. The histogram is not reported on Windows machines without high resolution clocks. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the DOH mode setting whenever it is read from or changed in Chrome and propagated to shill. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records an value corresponding to the HTTP status returned when a DNS-over-HTTPS request returns in error. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the type of plain text nameservers used whenever they are obtained from shill for a given network. jasongustaman@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records any errors that occur during DNS probes made by the service. A value will be recorded whenever the probe completes in error. jasongustaman@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records number of retries for failing probes. A value will be recorded whenever the probe completes in error. jasongustaman@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the results of the DNS probes made by the service. A value will be recorded whenever the probe completes. jasongustaman@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the results of the DNS probes made by the service. A value will be recorded whenever the probe completes. However, on error it is only recorded if it is a consistent error, meaning if it fails even after certain amount of retries. jasongustaman@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records number of retries needed until a successful probe. A value will be recorded whenever the probe completes in success. This metric does not catch consistenly failing probes. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the duration of various stages of the resolution process, including the entire time elapsed processing the query. The measurement is started when the resolver first reads the query data from the client and completes when the reply is sent. This histogram collects data for stages of the query that have resulted in some kind of failure. It's possible that for any single query, both successful and failed stages may exist. The most obvious case is when a resolution step is retried. As such, the total time elapsed will necessarily include zero or more resolution stages which are recorded in the query-type-specific version of this histogram. A "total" duration will be successful if at least one resolve stage succeeds, but will be recorded as 'failed' if they all do, or if any other stage fails. All measurements are made within the Resolver class. The "receive" time is recorded in OnDNSQuery(). This is also when the "total" time starts. The "resolve" measurements all start from the Resolve() method, and will stop either in the same method (on failure) or handler applicable to the specific client that was used: HandleAresResult() and HandleCurlResult(). The "reply" time is recorded in the ReplyDNS() method. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the duration of various stages of the resolution process, including the entire time elapsed processing the query. The measurement is started when the resolver first reads the query data from the client and completes when the reply is sent. This histogram collects data for stages of the query that have resulted in success. It's possible that for any single query, both successful and failed stages may exist. The most obvious case is when a resolution step is retried. As such, the total time elapsed will necessarily include zero or more resolution stages which are recorded in the query-type-specific version of this histogram. A "total" duration will be successful if at least one resolve stage succeeds, but will be recorded as 'failed' if they all do, or if any other stage fails. All measurements are made within the Resolver class. The "receive" time is recorded in OnDNSQuery(). This is also when the "total" time starts. The "resolve" measurements all start from the Resolve() method, and will stop either in the same method (on failure) or handler applicable to the specific client that was used: HandleAresResult() and HandleCurlResult(). The "reply" time is recorded in the ReplyDNS() method. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the number of nameserver addresses whenever they are obtained from shill for a given network. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy tracking critical process events, which are emitted when conditions arise that cause fatal or disruptive conditions to the service. This metric is used to monitor the stability of the service and provide detailed insight into failures. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records any errors that occur during DNS queries made by the service. A value will be recorded whenever the request completes in error. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the duration of a failed name resolution as part of an overall query. The measurement is started just before the client resolver (either plaintext or DoH) is run and stopped on its completion. All measurements are made within the Resolver class. The "resolve" measurements all start from the Resolve() method, and will stop either in the same method (on failure) or handler applicable to the specific client that was used: HandleAresResult() and HandleCurlResult(). garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the duration of a successful name resolution as part of an overall query. The measurement is started just before the client resolver (either plaintext or DoH) is run and stopped on its completion. All measurements are made within the Resolver class. The "resolve" measurements all start from the Resolve() method, and will stop either in the same method (on failure) or handler applicable to the specific client that was used: HandleAresResult() and HandleCurlResult(). garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the results of the DNS queries made by the service. A value will be recorded whenever the request completes. garrick@chromium.org cros-network-metrics@google.com Diagnostic metric for ChromeOS DNS proxy that records the results of the DNS queries made by the service. A value will be recorded whenever the request completes. If there are retries, only the last result will be recorded. arichiv@chromium.org zalmashni@google.com During request initialization, this metric records the source of each outgoing HTTP(S) request that had the Sec-GPC header set, categorized by the type of the request. Logged each time the Sec-GPC header is attached to an outgoing request, during request finalization. Subsampled to one out of one thousand times. nmuggli@google.com project-bolton@google.com Number of mDNS packets sent for mDNS queries in support of different services. The individual enum values indicate whether the query is an initial query or a refresh query. chuweih@google.com cros-network-metrics@google.com Percentage of time WiFi multicast packets are forwarded from ChromeOS to ARC. This depends on ARC WiFi multicast lock state and ARC doze mode state. The metric is only emitted when ARC is running and WiFi is connected. The value is recorded for a network whenever it is disconnected. jasongustaman@chromium.org cros-network-metrics@google.com Amount of WiFi multicast packets received by ChromeOS when multicast packets are forwarded to ARC and WiFi is connected. The value is recorded every 2 minutes by ChromeOS's patchpanel. The metrics are separated by multicast protocol mDNS and SSDP. jasongustaman@chromium.org cros-network-metrics@google.com Amount of WiFi multicast packets received by ChromeOS when multicast packets are not forwarded to ARC and WiFi is connected. The value is recorded every 2 minutes by ChromeOS's patchpanel. The metrics are separated by multicast protocol mDNS and SSDP. jasongustaman@chromium.org cros-network-metrics@google.com Amount of multicast packets received by ChromeOS. The value is recorded every 2 minutes by ChromeOS's patchpanel. Only multicast protocols mDNS and SSDP are included. jasongustaman@chromium.org cros-network-metrics@google.com Amount of multicast packets received by ChromeOS when at least one network of the specified technology (ethernet or WiFi) is connected. When there are multiple networks of the same technology, the sum is reported. The value is recorded every 2 minutes by ChromeOS's patchpanel. Only multicast protocols mDNS and SSDP are included. jasongustaman@chromium.org cros-network-metrics@google.com Amount of multicast packets received by ChromeOS when at least one network of the specified technology (ethernet or WiFi) is connected. When there are multiple networks of the same technology, the sum is reported. The value is recorded every 2 minutes by ChromeOS's patchpanel. The metrics are separated by multicast protocol mDNS and SSDP. stevenjb@chromium.org cros-network-health-team@google.com Number of Chrome portal detection attempts per network connection on ChromeOS. stevenjb@chromium.org cros-network-health-team@google.com The PortalState result of Chrome portal detection when completed. stevenjb@chromium.org cros-network-health-team@google.com Captive portal detection network type recorded when Chrome on ChromeOS detects a captive portal. NOTE: This metric used to be CaptivePortal.NetworkPortalDetectorType which was expired from 2021-09-27 to 2022-09-18. stevenjb@chromium.org cros-network-health-team@google.com Captive portal detection state when a notification is shown. Can be used with Network.NetworkPortalSigninMode to compare notification to signin ratio. stevenjb@chromium.org cros-network-health-team@google.com Captive portal signin display mode when a UI element requests to show the signin UI. See also NetworkPortalSigninSource. stevenjb@chromium.org cros-network-health-team@google.com Captive portal signin display source (notification, settings, etc.) when a UI element requests to show the signin UI. See also NetworkPortalSigninMode. stevenjb@chromium.org cros-network-health-team@google.com Time from showing a captive portal signin page to the network becoming online. Zero values represent a disconnect without becoming online. hugobenichi@google.com cros-device-enablement@google.com cros-network-metrics@google.com Diagnostic metric for ChromeOS patchpanel's ArcService which controls the virtual network setup for ARC++ and ARCVM. This metrics is recorded when the virtual network setup for ARC or ARCVM is created, deleted, or updated to track success and error rates of the various platform operations (network interface creation, iptables setup, etc) involved in the ARC virtual network setup. hugobenichi@google.com cros-device-enablement@google.com cros-network-metrics@google.com Diagnostic metric for the Dbus APIs implemented by ChromeOS patchpanel network service. This metrics is recorded whenever one of patchpanel DBus APIs is called and tracks success and error rates of various network platform primitives implemented by patchpanel (port forwarding APIs, firewall APIs, virtual network APIs for ARC and crosvm, etc). hugobenichi@google.com cros-network-metrics@google.com Result of creating a DownstreamNetwork tethered to an upstream network when calling the patchpanel DBus API CreateTetheredNetwork. hugobenichi@google.com cros-network-metrics@google.com DHCP server events happening for the DHCP server set up by the patchpanel DBus API CreateTetheredNetwork. stevenjb@chromium.org cros-network-health-team@google.com Captive portal time from a portal-suspected state to an online state on ChromeOS. NOTE: Prior to M110 this used a range that was too small so those results are invalid. ricea@chromium.org blink-network-stack@google.com For every failed match in network::PrefetchMatches() caused by a header in the `headers` field sent by the render process that was not in the prefetch, logs the name of the first header that was missing. Logged once per request that matched NIK and URL but failed to match due to an unexpected header. Not logged if a header value mismatch was seen first. ricea@chromium.org blink-network-stack@google.com For every failed match in network::PrefetchMatches() caused by a header in the `headers` field sent by the render process that had a different value from the same header in the prefetch, logs the name of the first header that failed to match. Logged once per request that matched NIK and URL but failed to match due to a header value mismatch. Not logged in a header missing from the prefetch was seen first. ricea@chromium.org blink-network-stack@google.com For every failed match in network::PrefetchMatches(), logs the first field that failed to match. Logged once per request that matched NIK and URL but failed to match on other fields. ricea@chromium.org blink-network-stack@google.com For every failed match in network::PrefetchMatches() caused by a header in the `headers` field of the prefetch that wasn't in the `headers` field sent by the render process, logs the name of a header that was missing. Logged for every missing header for every request that matched NIK and URL but failed to match due to a header value mismatch. Not logged if there were headers from the render process that were unexpected or had differing values. ricea@chromium.org blink-network-stack@google.com For every attempted match network::PrefetchMatches(), logs true if the ResourceRequest objects successfully matches, or false otherwise. Logged once per request that matched NIK and URL. stevenjb@chromium.org cros-network-health-team@google.com Captive portal time from a redirect-found state to an online state on ChromeOS. NOTE: Prior to M110 this used a range that was too small so those results are invalid. pmeenan@chromium.org blink-network-stack@google.com The time spent creating a brotli source stream with a dictionary. Logged when the network service receives an HTTP response compressed with Shared Brotli. Note that clients without high-resolution clocks will report 0 for very short times. pmeenan@chromium.org blink-network-stack@google.com The time spent creating a zstd source stream with a dictionary. Logged when the network service receives an HTTP response compressed with Shared Zstandard. Note that clients without high-resolution clocks will report 0 for very short times. Warning: this histogram was expired from 2025-06-08 to 2024-08-27; data may be missing. pmeenan@chromium.org blink-network-stack@google.com For each request that is for a document destination that has a shared compression dictionary available and is using the disk-based dictionary storage, records if the dictionary was available in one of the memory caches. Logged at the time a request is sent and only for those requests that were for a document destination and had a compression dictionary available. wbjacksonjr@chromium.org blink-network-stack@google.com For each request that is for a document destination that has a shared compression dictionary available and is using the disk-based dictionary storage, records if the dictionary's metadata was ready in memory at request initiation time, or if the request had to wait for the metadata to load from disk. This metric is logged only for those requests that were for a document destination and had a compression dictionary available. nidhijaju@chromium.org blink-network-stack@google.com For each shared dictionary network transaction, record the encoding type. akahuang@chromium.org cros-network-metrics@google.com ChromeOS network metric indicating if a CAPPORT status response contains the "bytes-remaining" field defined in RFC8908. This metric is only recorded once per CAPPORT session and only if the CAPPORT server started advertising "captive" as false. akahuang@chromium.org cros-network-metrics@google.com ChromeOS network metric indicating if a CAPPORT status response contains the "seconds-remaining" field defined in RFC8908. This metric is only recorded once per CAPPORT session and only if the CAPPORT server started advertising "captive" as false. akahuang@chromium.org cros-network-metrics@google.com ChromeOS network metric indicating if a CAPPORT status response contains the "venue-info-url" field defined in RFC8908. This metric is only recorded once per CAPPORT session and only if the CAPPORT server started advertising "captive" as false. akahuang@chromium.org cros-network-metrics@google.com ChromeOS network metric indicating if the maximum value advertised in CAPPORT status responses for the "seconds-remaining" field defined in RFC8908. This metric is only recorded once per CAPPORT session (the maximum value). akahuang@chromium.org cros-network-metrics@google.com ChromeOS network metric indicating the results for a CAPPORT query as defined in RFC8908. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the number of cellular network flakes. A network flake occurs when the signal strength goes below detection level for a short duration. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the total amount of time spent from the start of the first auto-connect request until when the cellular modem successfully connects to the network. NOTE: This metric was expired from 2022-01-30 to 2022-04-01. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the number of auto-connect tries that were attempted before the cellular modem successfully connected to the network. NOTE: This metric was expired from 2022-01-30 to 2022-04-01. ejcaruso@chromium.org cros-network-metrics@google.com Reports the result of Cellular connection attempts through the platform layers. This captures any success or failure as a result of a Connect call through ModemManager, or any causes of early failure in shill that prevents a connect attempt altogether. Refer to go/cros-cellular-apn-metrics for details. This metric was replaced by Network.Shill.Cellular.ConnectResult.{ApnType} in R116. danielwinkler@google.com cros-network-metrics@google.com Reports the result of Cellular connection attempts through the platform layers when using the {ApnType}. This captures any success or failure as a result of a Connect call through ModemManager, or any causes of early failure in shill that prevents a connect attempt altogether. Refer to go/cros-cellular-apn-metrics for details. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network metric that tracks the presence of a Cellular device in the system. A sample is emitted once every 3 minutes. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS cellular network metric that tracks the number of drops based on the network technology. andrewlassalle@chromium.org cros-network-metrics@google.com ChromeOS cellular network metric that tracks the entitlement check results used for hotspot. This metric is triggered every time the user tries to enable hotspot using cellular as the upstream technology. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric that tracks the length of a lease for a cellular network at the time it expired without the DHCP client being able to renew it. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network metric that tracks the types of IP configuration used for establishing cellular connections. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the result of portal detections for a cellular network. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS connection manager service errors for cellular interface. NOTE: This metric was updated in M101. Data prior to that may be missing. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network metric sampling the signal strength (0-100) of the cellular modem before it dropped from the network. rmao@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the enablement of a Cellular device in the system. A sample is emitted once every 3 minutes. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to join a cellular network and configure Layer 3 state. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to connect a cellular modem. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to disable a cellular modem. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to enable a cellular modem. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to initialize a cellular modem. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that a cellular network is online after configuring Layer 3 state. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that a cellular network is in a captive portal after configuring Layer 3 state. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that a cellular network is in a captive portal with a valid redirect URL after configuring Layer 3 state. ejcaruso@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to scan a cellular network and register a modem. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network metric that tracks Layer 3 connectivity issues diagnosed by the ConnectionDiagnostics class in Shill ran on a connected network after Shill portal detection has failed to validate the network. This metric is logged each time a ConnectionDiagnostics object completes its diagnostics actions and reports the results to its caller. olsa@google.com chromeos-commercial-networking@google.com ChromeOS network metric that tracks the EAP TLS connection events. olsa@google.com chromeos-commercial-networking@google.com ChromeOS network metric that tracks the EAP TLS connection events under the experiment SingleCaCertVerificationPhase1 if system CA certs are in use and custom cert is in use for the server authentication. olsa@google.com chromeos-commercial-networking@google.com ChromeOS network metric that tracks the EAP TLS connection events under the experiment SingleCaCertVerificationPhase2 if system CA certs are in use and custom cert is in use for the server authentication. olsa@google.com chromeos-commercial-networking@google.com ChromeOS network metric that tracks the EAP TLS connection events without experiments if system CA certs are in use and custom cert is in use for server authentication. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the presence of an Ethernet device in the system. A sample is emitted once every 3 minutes. chuweih@google.com cros-network-metrics@google.com Chrome OS metric that records the name of ethernet driver detected when an ethernet network is started. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the length of a lease for an Ethernet network at the time it expired without the DHCP client being able to renew it. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the result of portal detections for an Ethernet network. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS connection manager service errors for ethernet interface. NOTE: This metric was updated in M101. Data prior to that may be missing. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to join a wired Ethernet network and configure Layer 3 state (typically acquire a DHCP lease). NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to initialize an Ethernet device. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that an Ethernet network is online after configuring Layer 3 state. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that an Ethernet network is in a captive portal after configuring Layer 3 state. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that an Ethernet network is in a captive portal with a valid redirect URL after configuring Layer 3 state. NOTE: This metric was expired from 2021-12-01 to 2022-04-01. hugobenichi@google.com cros-network-metrics@google.com Indicates how the network advertises supports for the CAPPORT protocol (RFC8908) using RFC8908. This metric is recorded once for every network connection where CAPPORT was advertised, even if no captive portal was found with HTTP probes. This metric is a redefinition of the same portal detection metric ("Network.Shill.PortalDetector.CAPPORTAdvertised"), but with a name matching the typo existing in the platform for m121 and m122 and fixed in crrev/c/5223768, and without the shill network Technology suffix. This metric can be removed once captive portal metrics data on m121 and m121 is not needed anymore. hugobenichi@google.com cros-network-metrics@google.com Indicates if the network advertises supports for the CAPPORT protocol (RFC8908) using RFC8908. This metric is recorded once for every network connection where a captive portal was found with an HTTP redirect. This metric is a redefinition of the same portal detection metric ("Network.Shill.PortalDetector.CAPPORTAdvertised"), but with a name matching the typo existing in the platform for m121 and m122 and fixed in crrev/c/5223768, and without the shill network Technology suffix. This metric can be removed once captive portal metrics data on m121 and m121 is not needed anymore. hugobenichi@google.com cros-network-metrics@google.com Result of ChromeOS network validation CAPPORT queries aggregated over multiple queries until Internet connectivity has been validated or until disconnection. hugobenichi@google.com cros-network-metrics@google.com Result of ChromeOS network validation aggregated over multiple attempts until Internet connectivity has been validated or until disconnection. hugobenichi@chromium.org cros-network-metrics@google.com Number of network validation attempts before a physical network transitions to a non connected state, recorded when the Network transitions to the idle state and network validation could not confirm Internet access on that Network. hugobenichi@chromium.org cros-network-metrics@google.com Number of network validation attempts until a physical network transitions to online, recorded when network validation confirms Internet access for the first time on a given Network connection. hugobenichi@chromium.org cros-network-metrics@google.com Number of network validation attempts before a physical network transitions to redirect-found, recorded when network validation returns the first portal-redirect result for a given Network connection. hugobenichi@google.com cros-network-metrics@google.com Indicates how the network advertises supports for the CAPPORT protocol (RFC8908) using RFC8908. This metric is recorded once for every network connection where CAPPORT was advertised, even if no captive portal was found with HTTP probes. hugobenichi@google.com cros-network-metrics@google.com Indicates if the network advertises supports for the CAPPORT protocol (RFC8908) using RFC8908. This metric is recorded once for every network connection where a captive portal was found with an HTTP redirect. hugobenichi@google.com cros-network-metrics@google.com HTTP response code received by an HTTP probe used for network validation. Response codes received for encrypted HTTPS probes are ignored because it is assumed that HTTPS probes cannot be spoofed and always receive the expected 204 result. Possible values are HTTP response codes in the [100, 599] range or one of the three special values: 0 to indicate a bad response with an invalid response code, 1 to indicate a 302 or 307 redirect response without a Location header or with an invalid Location header which was not a URL, 2 for a 200 response without a Content-Length header or with an invalid Content-Lenght header. This metric is a redefinition of the same portal detection metric ("Network.Shill.PortalDetector.HTTPResponseCode"), but with a name matching the typo existing in the platform for m121 and m122 and fixed in crrev/c/5267618. This metric can be removed once captive portal metrics data on m121 and m121 is not needed anymore. hugobenichi@google.com cros-network-metrics@google.com Length in bytes of 200 responses received by a network validation HTTP probe during a network validation attempt. 200 responses with no content or a single byte of content are treated as 204 answers. These events are expected to be recorded only once for a given network connection (network with Internet acess). 200 responses with some actual content are treated as a suspected portal redirect and trigger the portal sign-in flow. These events are expected to be recorded multiple times until the user has signed into the portal. This metric is a redefinition of the same portal detection metric ("Network.Shill.PortalDetector.HTTPResponseContentLength"), but with a name matching the typo existing in the platform for m121 and m122 and fixed in crrev/c/5267618. This metric can be removed once captive portal metrics data on m121 and m121 is not needed anymore. hugobenichi@google.com cros-network-metrics@google.com HTTP response code received by an HTTP probe used for network validation. Response codes received for encrypted HTTPS probes are ignored because it is assumed that HTTPS probes cannot be spoofed and always receive the expected 204 result. Possible values are HTTP response codes in the [100, 599] range or one of the three special values: 0 to indicate a bad response with an invalid response code, 1 to indicate a 302 or 307 redirect response without a Location header or with an invalid Location header which was not a URL, 2 for a 200 response without a Content-Length header or with an invalid Content-Lenght header. hugobenichi@google.com cros-network-metrics@google.com Length in bytes of 200 responses received by a network validation HTTP probe during a network validation attempt. 200 responses with no content or a single byte of content are treated as 204 answers. These events are expected to be recorded only once for a given network connection (network with Internet acess). 200 responses with some actual content are treated as a suspected portal redirect and trigger the portal sign-in flow. These events are expected to be recorded multiple times until the user has signed into the portal. hugobenichi@chromium.org cros-network-metrics@google.com Initial result of network validation for a given physical Network connection, recorded once after the first network validation result. hugobenichi@chromium.org cros-network-metrics@google.com Subsequent result of network validation for a given physical Network connection, recorded after the first network validation result until Internet access is confirmed. damiendejean@chromium.org cros-network-metrics@google.com Result of terms and conditions URL detection aggregated with portal detection sampled once for every network connection. hugobenichi@google.com cros-network-metrics@google.com Total duration of a full ChromeOS portal detection attempt on a {Technology} network when this attempt either validates Internet connectivity or when detects a portal with a redirected probe. hugobenichi@google.com cros-network-metrics@google.com Duration of a single HTTP or HTTPS probe sent on a {Technology} network as part of ChromeOS platform portal detection. hugobenichi@google.com cros-network-metrics@google.com Total time it takes for ChromeOS network validation to find a captive portal redirection ("TimeToRedirect"), or to find a captive portal sign-in URL after a CAPPORT query as defined in RFC8908 ("TimeToCAPPORTUserPortalURL"), or to validate Internet access starting from the initial network connection ("TimeToInternet"), or starting from the first discovery of a captive portal redirection ("TimeToInternetAfterRedirect"), or after interacting with a CAPPORT server as defined in RFC8908 ("TimeToCAPPORTNotCaptive"), jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the MTU value provided by the upstream PPP peer for L2TP VPN connections. A sample is emitted each time the client successfully negotiates an MTU value via PPP. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric sampled on each successful VPN connection that tracks the VPN connection type. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful IKEv2 VPN connection that tracks how the client authenticates itself to the server. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful L2TP/IPsec VPN connection that tracks whether tunnel group is used. The tunnel group property needs to be set when connecting to some Cisco L2TP/IPsec VPN. taoyl@google.com cros-network-metrics@google.com ChromeOS network metric emitted on each successful OpenVPN connection that tracks the cipher algorithm negotiated with server. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric sampled on each successful VPN connection that tracks the remote authentication method. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each user login that tracks the number of the configured VPN services in shill. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to configure Layer 3 state on a VPN network (typically acquire a DHCP lease). jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that a VPN connection is online after configuring Layer 3 state. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric sampled on each successful VPN connection that tracks the user authentication method. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful WireGuard VPN connection that tracks the type of the allowed IPs set in this connection. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful WireGuard VPN connection that tracks the source of the key pair used in this connection. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful WireGuard VPN connection that tracks the number of peers used in in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each failed {VPNType} VPN connection attempt that tracks the reason of the connect failure. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each {VPNType} VPN connection end event (i.e., the VPN is no longer connected) that tracks the reason that the connection gets lost. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the encryption algorithm used by the ESP protocol in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the integrity algorithm used by the ESP protocol in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the DH group used by the IKE protocol in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the encryption algorithm used by the IKE protocol in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the integrity algorithm used by the IKE protocol in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the IP family provided in this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful split-routing {VPNType} VPN connection that tracks the length of the largest IPv4 excluded route (the route with the shortest prefix). jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the number of IPv4 excluded routes. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful split-routing {VPNType} VPN connection that tracks the length of the largest IPv4 included route (the route with the shortest prefix). jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the number of IPv4 included routes. Note that for a default route, it will always be counted as an included route, even if it is not explicitly set. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the type of routing setup for IPv4. Caveat: when we calculate whether the address space is fully covered, we will only check if there is a default route and no excluded route. If there is no /0 route but the address space is fully covered by multiple routes, it will be considered as split-routing. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful split-routing {VPNType} VPN connection that tracks the length of the largest IPv6 excluded route (the route with the shortest prefix). jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the number of IPv4 excluded routes. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful split-routing {VPNType} VPN connection that tracks the length of the largest IPv6 included route (the route with the shortest prefix). jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the number of IPv6 included routes. Note that for a default route, it will always be counted as an included route, even if it is not explicitly set. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the type of routing setup for IPv6. Caveat: when we calculate whether the address space is fully covered, we will only check if there is a default route and no excluded route. If there is no /0 route but the address space is fully covered by multiple routes, it will be considered as split-routing. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the MTU value of this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN connection that tracks the type of the DNS setup. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each time when the state of a {VPNType} VPN transits from connected to a non-connected state (reconnecting or idle), which tracks how long the VPN driver stays in the connected state of this connection. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful new {VPNType} VPN connection that tracks time duration from the VPN driver starts connecting to the VPN driver reports connected. The time used by shill and patchpanel for datapath configuration is not counted in this metrics. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each time when the state of a {VPNType} VPN transits from connecting to idle (without being connected once), which tracks the time duration from the VPN driver starts connecting to the VPN driver becomes idle. This can be expected (e.g., user cancel the connection) or unexpected (e.g., cannot reach the VPN server). jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each successful {VPNType} VPN reconnection (i.e., was connected before the reconnection restarts) that tracks time duration from the VPN driver starts reconnecting to the VPN driver reports connected. The time used by shill and patchpanel for datapath configuration is not counted in this metrics. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted on each time when the state of a {VPNType} VPN transits from reconnecting (i.e., was connected before) to idle (without being connected once), which tracks the time duration from the VPN driver starts reconnecting to the VPN driver becomes idle. This can be expected (e.g., user disconnects the connection) or unexpected (e.g., VPN server is no longer reachable). kglund@google.com cros-network-metrics@google.com ChromeOS WiFi usage metric emitted every time the WiFi adapter is enabled. It tracks if the adapter that was detected on the device is in the allowlist to be reported via structured metrics (e.g. is it in AVL?) or not. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS WiFi metric emitted every time an access point compatible with ANQP is connected. It tracks the support of the ANQP Address Type Availability field. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS WiFi metric emitted every time an access point compatible with ANQP is connected. It tracks the support of the ANQP Network Authentication Type field. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS WiFi metric emitted every time an ANQP query is done. It tracks the success or the different types of failures of a query. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS WiFi metric emitted every time an access point compatible with ANQP is connected. It tracks the support of the ANQP Venue Name field. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS WiFi metric emitted every time an access point compatible with ANQP is connected. It tracks the support of the ANQP Venue URL field. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support the 802.11k standard, sampled on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support the 802.11r standard, sampled on successful connections to an AP. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support ANQP request protocol, sampled on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support the 802.11v BSS Max Idle Period feature, sampled on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support the 802.11v BSS Transition feature, sampled on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support the 802.11v DMS feature, sampled on successful connections to an AP. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support transmit opportunity negotation, emitted on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric sampled when an AP switches channels. Shows the old frequency band and the new frequency band. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. Reason code reported when the AP disconnects a WiFi connection. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. Broad category of reason AP disconnected a WiFi connection. damiendejean@chromium.org cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support stream classification, emitted on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. Status code reported when an 802.11 association fails. Note that not all disconnects are caused by an assoc failure, and so this metric shold not be correlated with the DisconnectType metrics. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. Status code reported when an 802.11 authentication fails. Note that not all disconnects are caused by an auth failure, and so this metric should not be correlated with the DisconnectType metrics. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of wifi services available for auto-connect when auto-connect is initiated for wifi device. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of BSSes (endpoints) available for the currently connecting wifi service. yichenyu@chromium.org cros-network-metrics@google.com ChromeOS network usage metric. This is recorded when a connection failure is due to bad-passphrase and indicates whether the attempt is initated by users or not and if the service has been previously connected. rmekonnen@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the 6GHz Band support of access points that devices connect to. Results are recorded every time a device connects to an access point. kglund@google.com cros-network-metrics@google.com ChromeOS network metric recording BSS Transition Management statuses. This is recorded every time a BSS Transition Management request is received from a wireless access point. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. The channel used for each successful WiFi connection. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of Wireless Access Points that support Cisco's Adaptive FT feature, sampled on successful connections to an AP. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. Reason code reported when the client disconnects a WiFi connection. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. Broad category of reason client disconnected a WiFi connection. kglund@google.com cros-network-metrics@google.com ChromeOS Wifi Connection Quality Monitor(CQM) Notifications metric. This is emitted when any packet or beacon loss is observed for signal strength greater than -80 dBm. This metric is rate-limited such that it is never emitted more than once every 6 minutes. kglund@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the presence of a WiFi device in the system. A sample is emitted once every 3 minutes. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric that tracks the cause of an 802.11 wireless network disconnection. The disconnect types were expanded in release R129-15997.0.0. Refer to go/cros-wifi-disconnect-type for details. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric sampled on each successful 802.1x wireless connection that tracks the configured inner authentication method. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric sampled on each successful 802.1x wireless connection that tracks the configured outer authentication method. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the length of a lease for a WiFi network at the time it expired without the DHCP client being able to renew it. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the result of the fallback DNS test. The fallback DNS test is performed when portal detection failed due to DNS failure. jonmann@chromium.org tnagel@chromium.org cros-network-metrics@google.com pwg-cros@google.com ChromeOS network metric tracking whether there has ever been a successful connection for each WiFi network which is configured with a hidden SSID. The metric includes networks from system and user profile and it's recorded each time a user configuration profile is loaded, such as when a user logs in. Networks that were last connected before M-84 will show as never connected. jonmann@chromium.org tnagel@chromium.org cros-network-metrics@google.com pwg-cros@google.com ChromeOS network metric tracking the number of days since the last connection for each WiFi network configured with hidden SSID. The metric includes networks from system and user profile and it's recorded each time a user configuration profile is loaded, such as when a user logs in. tnagel@chromium.org cros-network-metrics@google.com cros-privacy-core@google.com ChromeOS network metric tracking whether WiFi networks configured with hidden SSID have ever been connected. The metric includes networks from system and user profile and it's recorded each time a user configuration profile is loaded, such as when a user logs in. tnagel@chromium.org cros-network-metrics@google.com cros-privacy-core@google.com ChromeOS network metric tracking WiFi networks configured with hidden SSID. The metric includes networks from system and user profile and it's recorded each time a user configuration profile is loaded, such as when a user logs in. The fraction of non-zero buckets should roughly correspond to the fraction of devices that are trying to connect to hidden SSIDs at any given point in time. kglund@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the Hotspot 2.0 support of access points that devices connect to. Results are recorded every time a device connects to an access point. The metric records either the HS20 version the AP supports, or that the AP does not support HS20. kglund@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the Multi-Band Operation (MBO) support of access points that devices connect to. Results are recorded every time a device connects to an access point. jiejiang@chromium.org cros-network-metrics@google.com ChromeOS metric that signals the type of failure the NeighborLinkMonitor detected on 802.11 wireless network. Recorded after the NeighborLinkMonitor detects a layer 2 connectivity failure to a neighbor. kglund@google.com cros-network-metrics@google.com ChromeOS network metric that tracks the types of IP configuration used for establishing WiFi connections. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the network problems encountered by TrafficMonitor after WiFi connection is established. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Results of a WiFi connection attempt for a WiFi network provisioned through Passpoint. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of FQDNs specified in a Passpoint profile. Recorded once per Passpoint profile successfully provisioned in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of Home Organization Identifiers specified in a Passpoint profile. Recorded once per Passpoint profile successfully provisioned in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Duration in milliseconds of a single supplicant Interworking select operation. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of Passpoint match events during a single supplicant Interworking select operation. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Match event between a Passpoint profile provisioned in shill and a Passpoint network. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Meterdness configuration of Passpoint profiles. Recorded once per Passpoint profile successfully provisioned in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Origin of a Passpoint profile successfully provisioned in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Result of a Passpoint profile provisioning operation in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Result of a Passpoint profile removal operation in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of required Home Organization Identifiers specified in a Passpoint profile. Recorded once per Passpoint profile successfully provisioned in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of Roaming Organization Identifiers specified in a Passpoint profile. Recorded once per Passpoint profile successfully provisioned in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of Passpoint profiles saved in a shill user profile. Recorded once every time a user profile is loaded in shill. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com EAP method configuration of Passpoint profiles. Recorded once per Passpoint profile successfully provisioned in shill. damiendejean@chromium.org cros-network-metrics@google.com Indicates if the network requires terms and conditions acceptance to access the network. hugobenichi@google.com cros-networking@google.com cros-network-metrics@google.com Number of savd WiFi networks provisioned through Passpoint. Recorded once every time a user profile is loaded in shill. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. The standard advertised by the AP for each successful WiFi connection. It is not necessarily the same as the standard used by the AP and STA to communicate. For example, if the AP supports 802.11ax and the STA only supports 802.11ac, this metric will report 802.11ax even though STA and AP will use 802.11ac. The metric is emitted when the device connects successfully to an AP. hugobenichi@chromium.org cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the result of portal detections for an 802.11 wireless network. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric that tracks which country the WiFi regulatory domain is set to. Recorded every time a WiFi regulatory domain change is triggered or determined initially (Shill startup). kglund@google.com cros-network-metrics@google.com ChromeOS network diagnostic metric sampling the number of 802.11 wireless networks known by the connection manager at the time a configuration profile has been loaded. A configuration profile is loaded at each system startup, and when a user logs in. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of 802.11 wireless networks configured from the system configuration profile. This metric is sampled each time a user configuration profile is loaded, such as when a user logs in. It might be surprising to have a system configuration profile metric sampled when a user configuration profile is loaded. But this ensures that we have equal numbers of samples for system and user configuration profiles. {ShillWiFiRememberedNetworkSecurityMode} kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the number of 802.11 wireless networks configured from a user configuration profile. This metric is sampled each time a user configuration profile is loaded, such as when a user logs in. {ShillWiFiRememberedNetworkSecurityMode} kglund@google.com cros-network-metrics@google.com ChromeOS network metric recording roam successes or failures. This is recorded every time a client succeeds or fails to roam from one wireless access point to another. {RoamSecurityType} kglund@google.com cros-network-metrics@google.com ChromeOS network metric recording roam time in milliseconds. This is recorded every time a successful roam from one wireless access point to another occurs. {RoamSecurityType} kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric describing, for a WiFi scan attempt, what scan method is used and whether it ends in a connection. {ProgressiveScan} kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric describing, for a WiFi scan attempt, how many milliseconds were spent waiting to talk to the kernel/drivers. kglund@google.com cros-network-metrics@google.com ChromeOS network usage metric. The security setting for each successful WiFi connection. andrzejo@google.com cros-network-metrics@google.com ChromeOS network metric for WiFi security changes. It is emitted every time a new BSSID is being added to a network, this network has already been connected before and configuration of this new BSSID causes network security to be changed in a non-trivial way - that is a downgrade or an upgrade that can cause split of an network into two services. kglund@google.com cros-network-metrics@google.com ChromeOS connection manager service errors for wifi interface. kglund@google.com cros-network-metrics@google.com ChromeOS network metric recording session length in milliseconds. This is recorded every time an uninterrupted session with a wireless access point is terminated. {RoamSecurityType} kglund@google.com druth@google.com cros-network-metrics@google.com ChromeOS metric reporting the state of the "session tag" state machine that tags {Event} structured metrics events. The state of the session tag is emitted at the same time as the {Event} structured metric event is emitted. Details at go/cros-wifi-metrics-session-tag-dd. kglund@google.com cros-network-metrics@google.com ChromeOS network metric indicating the negative of the dBm received signal strength recorded at the time of a WiFi disconnect. kglund@google.com cros-network-metrics@google.com ChromeOS network metric indicating the negative of the dBm received signal strength recorded at the time a successful WiFi connection started. kglund@google.com cros-network-metrics@google.com Number of attempts required for a WiFi device to be established with WPA supplicant (shill retries on failure). This metric is reported either on success, reporting the number of attempts performed; or after repeated failures (currently 6), we give up and report an artificial maximum (10). Thus, a value of 10 means we aborted after repeated failures. Values of 1 to 6 represent successful connections on the first to sixth try. Values of 7 to 9 (which should not occur) represent successful connections after seven or more attempts (success reports are capped at 9). billyzhao@chromium.org cros-network-metrics@google.com Time spent between network rekey attempt to connection failure. The metric timer starts when a rekey is initiated and stops once a connection failure is reported or another rekey is initiated. The metric is only reported if the timer is stopped by a connection failure within 180 seconds. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time from the resume event to the time when an 802.11 wireless network has configured its Layer 3 state. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time from the resume event to the time when an 802.11 wireless network has configured its Layer 3 state if the AP associated to after resume is the same as the one before suspend, and the AP is on the 5GHz band. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time from the resume event to the time when an 802.11 wireless network has configured its Layer 3 state if the AP associated to after resume is the same as the one before suspend, and the AP is on the 2.4GHz band. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time from the resume event to the time when an 802.11 wireless network has configured its Layer 3 state if the AP associated to after resume is the same as the one before suspend, and the AP is on the 6GHz band. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to configure Layer 3 state on an 802.11 wireless network (typically acquire a DHCP lease). kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to connect to a WiFi Basic Service Set (which consists of the access point and associated stations on a particular WiFi channel for a specific network). {ProgressiveScan} kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to initialize an 802.11 wireless device. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to join (associate plus authenticate) an 802.11 wireless network. {ProgressiveScan} kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that an 802.11 wireless network is online after configuring Layer 3 state. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that an 802.11 wireless network is in a captive portal after configuring Layer 3 state. hugobenichi@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to determine that an 802.11 wireless network is in a captive portal with a valid redirect URL after configuring Layer 3 state. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time between the beginning of a WiFi scan (if the scan includes both a progressive scan and a full scan, the TimeToScanAndConnect starts with the first scan of the series) and the completion of a successful connection. {ProgressiveScan} kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric sampling the time to scan WiFi until a connection is found. {ProgressiveScan} kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the transmit bitrate in Mbps for the wifi device when it is connected to a network. The bitrate is reported once every minute after the wifi connection is established. kglund@google.com cros-network-metrics@google.com ChromeOS network metric sampling the signal strength (0-100) of the wifi network when it becomes unreliable (experiencing multiple link failures in a short period of time). kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the reasons of failed user-initiated WiFi connection attempts. The result of the user-initiated WiFi connection attempts are being tracked by Network.Shill.WiFi.UserInitiatedConnectionResult. kglund@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the result of user-initiated WiFi connection attempts. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted after a {Technology} connection has DHCPv4 provisioned, to track the duration from shill starts DHCPv4 configuration until shill gets the DHCP configuration from the dhcpcd process. chenzikai@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the number of successful DHCPv4 Renew/Rebind events for {Technology}. The metric will be emitted once per DHCPv4 Renew/Rebind event in shill. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted after a {Technology} connection has been connected for 30 seconds, to track the IP type on this connection. Wait for 30 seconds because IPv4 and IPv6 configuration are usually provisioned at different time. Note that no metric will be emitted if the duration of the connection is shorter than 30 seconds. jiejiang@chromium.org cros-device-enablement@google.com cros-network-metrics@google.com ChromeOS network usage metric emitted after a {Technology} connection has SLAAC provisioned, to track the duration from shill requests the kernel to start SLAAC configuration until shill gets the first SLAAC address from the kernel. chenzikai@google.com cros-network-metrics@google.com ChromeOS network performance metric that tracks the DHCPv4 provision result for {Technology} due to {DHCPProvisionReason}. The metric is emitted once the provisioning is done (either succeeded or failed). sisidovski@chromium.org chrome-worker@google.com Records whether the committed response headers are consistent with the headers from the network when the service worker synthetic response is used. This is recorded in navigation, when the browser receives the response from the network, while committed the navigation with locally stored headers. khegde@google.com cros-network-health-team@google.com Chrome metric emitted to store the average daily usage of technology {Technology} in megabytes. This metric is emitted once every time the TrafficCountersHandler class resets the data usage (automatically or manually) for this network. khegde@google.com cros-network-health-team@google.com Chrome metric emitted to store the data usage of technology {Technology} when the last reset time is not available. The metric is emitted once every time the TrafficCounterHandler class resets the data usage (automatically or manually) for this network and cannot obtain the last reset time to calculate the daily average data usage. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the failure reason for all connection attempts, manual or automatic, to Wi-Fi networks which were added from Chrome Sync. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the result of all connection attempts, manual or automatic, to Wi-Fi networks which were added from Chrome Sync. crisrael@google.com jonmann@chromium.org tnagel@chromium.org cros-network-metrics@google.com cros-privacy-core@google.com ChromeOS network metric tracking the count of synced networks that were fixed after getting saved to the device when out of range and marked as hidden. See b/178089463 for more details. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the failure reason for manual connection attempts to Wi-Fi networks which were added from Chrome Sync. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the result of manual connection attempts to Wi-Fi networks which were added from Chrome Sync. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the total number of Wi-Fi networks which are stored in Chrome Sync for the active user. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the failure reason for update attempts to synced Wi-Fi networks. This includes create/modify/remove operations. Each retry is counted seperately. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the success or failure to generate a local network config. Emitted on success and failure of add/update operations. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric that tracks the result of update attempts to synced Wi-Fi networks. This includes create/modify/remove operations. failures are only recorded after all retries have been exhausted. crisrael@google.com jonmann@chromium.org chromeos-cross-device-eng@google.com ChromeOS metric logged for users who have the feature enabled but have zero networks eligible for sync. Tracks the reasons why none of the networks are eligible. averge@chromium.org mkwst@chromium.org shivanisha@chromium.org xiaochenzh@chromium.org Records the presence of parsed Connection-Allowlist and Connection-Allowlist-Report-Only headers. This is recorded when the network restrictions throttles are executed for either navigations or worker scripts, immediately before the allowlist takes effect. hiroshige@chromium.org toyoshim@chromium.org Whether method or normalized method are allowed in CORS preflight request in PreflightResult::EnsureAllowedCrossOriginMethod(), to measure the impact of https://crbug.com/1228178. Logged for preflight requests that have method checked (i.e. those without errors before EnsureAllowedCrossOriginMethod). olivier@chromium.org cduvall@chromium.org Logs the time spent in CorsURLLoaderFactory::CreateLoaderAndStart. Logged on exiting the function. Subsampled to one out of one thousand times. Note that clients without high-resolution clocks will report 0 for very short times. olivier@chromium.org cduvall@chromium.org Logs the thread time spent in CorsURLLoaderFactory::CreateLoaderAndStart. Logged on exiting the function. Subsampled to one out of one thousand times. Note that clients without high-resolution clocks will report 0 for very short times. Only recorded on clients with thread tick support. pmeenan@chromium.org src/services/network/OWNERS Recorded whenever a renderer request claims to originate from an outermost main frame while its browser-created URLLoaderFactory does not. The request value is clamped to the factory value. One known legitimate source is an initial empty document in an opener-retaining popup created by a subframe. ricea@chromium.org src/net/OWNERS The system error code after a call to MaybeGrantAccessToDataPath() failed for directory '{Directory}'. Logged during instantiation of a new NetworkContext only on failure to grant access. Only logged for non-Windows platforms. ricea@chromium.org src/net/OWNERS The system error code after a call to MaybeGrantAccessToDataPath() failed for directory '{Directory}'. Logged during instantiation of a new NetworkContext only on failure to grant access. Only logged on Windows. wfh@chromium.org mmenke@chromium.org The result of the attempt to grant the sandbox access to a network context data files, and migrate the data if a migration is requested. This is reported each time a network context instance is created on the network service, even when the sandbox is not enabled or no migration is requested. hayato@chromium.org blink-network-stack@google.com The time taken to finish a network URLLoader to complete. A network URLLoader is a URLLoader that a CorsURLLoader used internally to load an HTTP response from the underlying layer. The underlying layer serves the response from either the disk cache backend or the network. This histogram is recorded for {Source}. hayato@chromium.org blink-network-stack@google.com The time taken to finish a network URLLoader to complete. A network URLLoader is a URLLoader that a CorsURLLoader used internally to load an HTTP response from the underlying layer. The underlying layer serves the response from either the disk cache backend or the network. This histogram is recorded for requests of {Priority} priority served from {Source}. yyanagisawa@chromium.org chrome-loading@google.com Records the elapsed time for pupulating parsed headers in the network service's ParseHeaders() IPC call. Note: The metrics is reported from all clients. Some of clients may not have high resolution timer that can send metrics with microseconds precision. nafisabedin@google.com clank-performance-team@google.com Measures the amount of time the task to run CreateLoaderAndStart was queued for a {FrameType} before running. Logged every time CreateLoaderAndStart is run in PrefetchMatchingURLLoaderFactory with a valid queue time. hayato@chromium.org net-dev@chromium.org Records the number of pending tasks in {QueueName}Queue of NetworkServiceScheduler. Recorded with 0.001 probability when a task scheduled on the IO thread starts. hayato@chromium.org net-dev@chromium.org Records the queuing time (from post to start processing) of a task posted to {QueueName}Queue of NetworkServiceScheduler. Recorded with 0.001 probability when a task scheduled on the IO thread starts. hayato@chromium.org net-dev@chromium.org Records the duration spent off-CPU by tasks running on the Network Service IO thread. Recorded with 0.001 probability when a task scheduled on the IO thread finishes running. hayato@chromium.org net-dev@chromium.org Records the duration spent on-CPU by tasks running on the Network Service IO Thread. Recorded with 0.001 probability when a task scheduled on the IO thread finishes running. hayato@chromium.org net-dev@chromium.org Records the percentage of wall time spent on-CPU by tasks running on the Network Service IO Thread. Recorded with 0.001 probability when a task scheduled on the IO thread finishes running. toyoshim@chromium.org chrome-loading@google.com The size of Sec-CH-* headers in bytes. Recorded when validating renderer-initiated requests in the Network Service. This helps monitor the impact of size limits imposed to protect the IPC boundary. toyoshim@chromium.org chrome-loading@google.com The size of Sec-Speculation-Tags headers in bytes. Recorded when validating renderer-initiated requests in the Network Service. This helps monitor the impact of size limits imposed to protect the IPC boundary. ricea@chromium.org yoichio@chromium.org blink-network-stack@google.com The first reason why the chunk allocation for a request was blocked. Recorded once per request that made use of SlopBucket, when it is completed. ricea@chromium.org yoichio@chromium.org blink-network-stack@google.com The reason why slop bucket is disabled, if it has been disabled. Is not recorded when SlopBucket is disabled by feature setting. Recorded when SlopBucket is first needed, and at most once every 24 hours afterwards. Also recorded immediately if SlopBucket is disabled due to memory pressure. Warning: this histogram was expired from 2024-10-23 to 2025-06-24; data may be missing. ricea@chromium.org yoichio@chromium.org blink-network-stack@google.com The peak number of chunks allocated for a request. Recorded once per request that made use of SlopBucket, when it is completed. Warning: this histogram was expired from 2024-10-23 to 2025-06-24; data may be missing. ricea@chromium.org blink-network-stack@google.com The priority of all requests passed to SlopBucket::RequestSlopBucket() while it is enabled. By default, requests with a priority lower than MEDIUM will not receive a SlopBucket, but they are still recorded here. Recorded once per request that attempts to make use of SlopBucket, ie. it filled up its mojo pipe and SlopBucket was enabled. Warning: this histogram was expired from 2024-10-23 to 2025-06-24; data may be missing. horo@chromium.org blink-network-stack@google.com The time taken from NetworkService creation to the first CreateNetworkContext call. Recorded once per NetworkService initialization. wfh@chromium.org mmenke@chromium.org The time taken to permit the sandbox access to the cache directory during network context initialization. This is recorded each time a network context is created with a valid disk cache specified. This histogram is platform dependent so values from different platforms cannot be directly compared. On Windows, this records the amount of time taken to set the filesystem ACLs to allow the sandbox access to the cache directory. wfh@chromium.org mmenke@chromium.org The time taken to permit the sandbox access to the data directory during network context initialization. This is recorded each time a network context is created with a valid set of NetworkContextFilePaths with unsandboxed_data_path specified indicating it could be sandboxed. This histogram is platform dependent so values from different platforms cannot be directly compared. On Windows, this records the amount of time taken to set the filesystem ACLs to allow the sandbox access to the data directory. Warning: this histogram was expired from 2023-10-08 to 2024-01-02; data may be missing. pmeenan@chromium.org src/net/extras/shared_dictionary/OWNERS The time taken to permit the sandbox access to the shared dictionary directory during network context initialization. This is recorded each time a network context is created with a valid shared dictionary directory specified. This histogram is platform dependent so values from different platforms cannot be directly compared. On Windows, this records the amount of time taken to set the filesystem ACLs to allow the sandbox access to the cache directory. wfh@chromium.org mmenke@chromium.org The time taken to copy the network context data files from the unsandboxed data path to the new sandbox data path. This is recorded each time an unmigrated network context is created with a valid set of data file paths, an unsandboxed_data_path to migrate from, and trigger_migration specified. This could include several logs from the same client for the same network context if the migration fails, since this is reported each time the migration is attempted. rogerm@chromium.org asvitkine@chromium.org The uncertainty of the estimated network time, recorded when the current network time is estimated based on a previous network time synchronization. The uncertainty is calculated based on the uncertainty inherent in the previous network time update and any skew detected between the local wall and tick clocks since that update. rogerm@chromium.org asvitkine@chromium.org The uncertainty of the network time, recorded when the network time is successfully synchronized. The uncertainty is calculated based on the resolution of the time source, the latency of the query, and the resolution of the local tick clock. This is the uncertainty in the data which will later be used to estimate/calculate network time.