emaamari@google.com cros-lurs@google.com cros-oac@google.com Chrome OS histogram that keeps track of cases where the user_allowlist policy is not present, forcing us to use the user_whitelist policy instead. We emit false to this histogram when user_allowlist is present. We emit true when user_allowlist is not present and user_whitelist is present and used as fallback. These checks happen during login policies decoding, which occurs every time device settings are loaded or stored. Warning: this histogram was expired from 2023-03-19 to 2024-04-24; data may be missing. hidehiko@chromium.org junis@google.com cros-oac@google.com Tracks the browser process shutdown time from when SIGTERM is sent to the browser process to when the browser process group exits (or gets killed by SIGABRT). iscsi@google.com cros-lurs@google.com Tracks the result of the cryptohome recovery and the failure reason for passwordless users. Recorded when the recovery attempt finished. yunkez@google.com cros-lurs@google.com Records the time taken for the Cryptohome recovery when it {Result}. yunkez@google.com cros-lurs@google.com Tracks the result of the cryptohome recovery and the failure reason. Recorded when the recovery attempt finished. antrim@chromium.org cros-lurs@google.com A set of chrome flags that triggered browser restart on Chrome OS after user sign in. Chrome needs to be restarted if the device owner set of flags is different from the user flags. Which means that there is a flag difference which led to this restart. This difference is reported by this metric. igorcov@chromium.org chromeos-commercial-remote-management@chromium.org Reports the device ownership, the state of the device policy and the state of the owner key. Logged only for the devices that have ownership taken as per install attributes. Is logged at every device policy load. antrim@chromium.org cros-lurs@google.com Chrome OS login failure reason. antrim@chromium.org cros-lurs@google.com Report the type of user login and the number of it on a device. It is triggered when a login is successful emaamari@google.com src/chromeos/ash/components/policy/OWNERS Chrome OS histogram that keeps track of cases where devices have an invalid combination of allow_new_users and user_allowlist policies. This is emitted during the decoding of login policies. Warning: this histogram was expired from 2024-02-25 to 2025-03-14; data may be missing. sinhak@chromium.org cros-lurs@google.com Boolean histogram that indicates if token handle is in sync with the user's current refresh token - i.e. if token handle checks are performed for token handles that actually belong to the user's current refresh token. If this is not the case, it can result in users getting unnecessary logout notifications. This histogram is logged once at the start of a user's session. emaamari@google.com cros-lurs@google.com Boolean histogram that indicates if token handle is in sync with the user's current refresh token - i.e. if token handle checks are performed for token handles that actually belong to the user's current refresh token. If this is not the case, it can result in users getting unnecessary logout notifications. This histogram is logged once at the start of a user's session. This histogram replaces the Login.IsTokenHandleInSyncWithRefreshToken histogram after launching the UseTokenHandleStore ash feature, which changes the way we manage token handles. Warning: this histogram was expired from 2025-12-31 to 2026-03-19; data may be missing. mslus@chromium.org chromeos-commercial-identity@google.com Records whether a new user's priority prefs sync timed out. mslus@chromium.org chromeos-commercial-identity@google.com Time spent waiting for priority preferences to sync after new user sign in. The operation will time out after 10s. mslus@chromium.org chromeos-commercial-identity@google.com Records the number of users the login screen was initialized with. It is emitted on processing the user list before displaying the screen. The count includes all Regular, Child and Active Directory users. mslus@chromium.org chromeos-commercial-identity@google.com Records offline login attempts with user pods hidden on the login screen. Warning: this histogram was expired from 2023-12-24 to 2025-03-14; data may be missing. yigu@chromium.org tbansal@chromium.org web-identity-eng@google.com Type of login detected for a page load based on different heuristics. Recorded once per page load. antrim@chromium.org cros-lurs@google.com Tracks the reason why a user was sent through the GAIA re-auth flow which caused the local password change. antrim@chromium.org cros-lurs@google.com Tracks the reason why a user was sent through the GAIA re-auth flow which did not cause the local password change. antrim@chromium.org achuith@chromium.org cros-lurs@google.com Time from first display of the login prompt until the user completes signing in. khmel@chromium.org antrim@chromium.org cros-lurs@google.com Time from first display of the login prompt until the existing user completes signing in. yunkez@google.com cros-lurs@google.com Records the fetch duration of the reauth request token from the recovery service when it {Result}. This is recorded on the GAIA reauth screen when Cryptohome recovery is deemed to be needed in high probablity. Warning: this histogram was expired from 2022-06-02 to 2022-08-18 and from 2025-12-28 to 2026-03-19; data may be missing. iby@chromium.org Tracks whether a ChromeOS user was logged out because Chrome repeatedly crashed. sergiyb@chromium.org chromeos-commercial-remote-management@chromium.org Result of a state key generation operation. Warning: this histogram was expired from 2019-10-29 (M78) to 2023-02-09 (M110); data may be missing. Starting in 2023-08-22 (M116), the value MISSING_IDENTIFIERS is no longer reported. Instead we report MISSING_MACHINE_SERIAL_NUMBER or MISSING_DISK_SERIAL_NUMBER when only one of the identifiers is missing, or MISSING_ALL_IDENTIFIERS when all are missing. achuith@chromium.org antrim@chromium.org cros-lurs@google.com Chrome OS login success reason. hidehiko@chromium.org junis@google.com Tracks whether switches were mapped to feature flags in session_manager for compatibility. session_manager does this and emits UMA samples when encountering old device settings files that still contain feature configuration in command line switch representation. This data will inform the decision when to remove this compatibility code. antrim@chromium.org cros-lurs@google.com Time between sending a request to, and receiving a reply from, GAIA token endpoint to validate TokenInfo. Warning: this histogram was expired from 2024-09-22 to 2025-03-14; data may be missing. antrim@chromium.org cros-lurs@google.com Time between sending a request to, and receiving a reply from, GAIA token endpoint to obtain TokenInfo. Warning: this histogram was expired from 2021-04-01 to 2023-12-05, data may be missing.