dkuzmin@google.com cros-oac@google.com Recorded when user enters their account on license packged device during enrollment process. fsandrade@chromium.org src/chrome/browser/ash/authpolicy/OWNERS The way device is joined to the Active Directory domain. This will be recorded during successful enterprise enrollment and domain join. igorcov@chromium.org vsavu@google.com Consistency between TPM lock state and absence/presence of install attributes at boot. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Duration of the bucket download part of the auto-enrollment protocol. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2021-12-26 until 2022-07-15. vsavu@google.com igorcov@chromium.org chromeos-commercial-remote-management@google.com Count the number of timeouts and successes for AutoEnrollmentController. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Duration of the hash dance to determine enrollment state of the device. Only recorded if the hash dance finished successfully. {EnterpriseAutoEnrollmentType} sergiyb@google.com mpolzer@google.com chromeos-commercial-remote-management@google.com Duration of the private set membership request to determine enrollment state of the device. Only recorded if it finished successfully. The histogram was expired (not recording data) from 2022-04-10 until 2022-07-15. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Total duration time of the auto-enrollment protocol. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2022-01-09 until 2022-07-15. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Device management server request status for auto-enrollment PSM requests. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2021-10-31 until 2021-11-09. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Network error code (if applicable) for auto-enrollment PSM requests. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2021-10-31 until 2021-11-09. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com All possible PSM protocol results after it has executed successfully or terminated due to an error or timeout. This request is used to determine the initial enrollment state of the device. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2021-10-31 until 2021-11-09. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Network error code (if applicable) for auto-enrollment requests. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2021-12-19 until 2022-07-15. sergiyb@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com URL fetcher status for auto-enrollment requests. {EnterpriseAutoEnrollmentType} The histogram was expired (not recording data) from 2021-12-12 until 2022-07-15. gujen@google.com goanuj@google.com Recorded when a signed-in user is automatically signed out of the browser due to the BrowserSignin policy being set to 0 (sign-in disabled) by their organization. The sample is always recorded as true. Warning: This histogram was expired from 2021-06-30 to 2022-11-30; data may be missing. gujen@google.com goanuj@google.com Recorded when a user is in the process of signing in to the browser, but is interrupted due to the BrowserSignin policy being set to 0 (sign-in disabled) by their organization. The sample is always recorded as true. Warning: This histogram was expired from 2021-06-30 to 2022-11-30; data may be missing. alexwchen@chromium.org cbe-eng@google.com Histogram for counting the BrowserSignin policy. This metric is recorded every 24 hours and at startup along with the full set of the enterprise policy rules that are in use. anthonyvd@chromium.org cbe-eng@google.com Events for counting CBCM policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. anthonyvd@chromium.org cbe-eng@google.com Events measuring effectiveness of refreshing CBCM policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. zmin@chromium.org src/chrome/browser/enterprise/reporting/OWNERS Recorded when real time report enter the queue. It indicates whether the report is pushed to the queue successfully or not. anthonyvd@chromium.org cbe-eng@google.com Events for counting status of executed CBCM remote commands. The metric includes only signed CBCM remote commands. Reports a final status of finished remote command (e.g. success, failure or termination). anthonyvd@chromium.org cbe-eng@google.com Events for counting received CBCM remote commands. The metric includes signed CBCM remote commands, both valid and invalid. Valid remote command is counted by its type. Invalid remote command is counted by a reason why it is considered invalid (e.g. unknown type or duplication). anthonyvd@chromium.org cbe-eng@google.com Events for counting CBCM remote commands invalidations received with and without payloads. Invalidations indicate that there is a remote command to execute. Payloads provide context about the remote commands update, but may be absent if dropped by the invalidation service. zmin@chromium.org hur.ims@navercorp.com src/chrome/browser/enterprise/reporting/OWNERS Recorded once each time the extension request prompt dialog is accepted or aborted. zmin@chromium.org src/chrome/browser/enterprise/reporting/OWNERS Recorded when cloud extension request pending list is updated. Note that when multiple requests are added or removed together, there will be only one event recorded. zmin@chromium.org igorruvinov@chromium.org Records the enrollment token location when the token is loaded. zmin@chromium.org pastarmovj@chromium.org The proto size of the basic Chrome browser cloud management reporting request. When a report is separated into multiple requests, all of them contain the basic request. zmin@chromium.org pastarmovj@chromium.org The number of request for one Chrome browser cloud management report. A report is separated into multiple requests when it's too large. zmin@chromium.org pastarmovj@chromium.org The proto size of each Chrome browser cloud management reporting request. It includes the requests which are more than 5MB and discarded. zmin@chromium.org pastarmovj@chromium.org The upload result for each cloud reporting request. Note that there may be multiple requests per report. Also, one request may creates multiple data point due to retry. grt@chromium.org src/chrome/browser/enterprise/reporting/OWNERS The trigger detected by the ReportScheduler responsible that led to an attempt to upload an enterprise report. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting device local account policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. As opposed to current histogram, Enterprise.DevicePolicyInvalidations2 counts only events of device policy invalidations. asumaneev@google.com chromeos-commercial-remote-management@google.com Events measuring effectiveness of refreshing device local account policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. As opposed to current histogram, Enterprise.DevicePolicyRefresh3 counts only events of refreshing device policies. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting device policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. As opposed to current histogram, Enterprise.DeviceLocalAccountPolicyInvalidations2 counts only events of device local account policy invalidations. asumaneev@google.com chromeos-commercial-remote-management@google.com Events measuring effectiveness of refreshing device policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. As opposed to current histogram, Enterprise.DeviceLocalAccountPolicyRefresh3 counts only events of refreshing device local account policies. macinashutosh@google.com chromeos-commercial-crd@google.com Reports the creation of FrameSinkDesktopCapturer class object macinashutosh@google.com chromeos-commercial-crd@google.com Reports the destruction of FrameSinkDesktopCapturer class object macinashutosh@google.com chromeos-commercial-crd@google.com Reports success/failure when a session is attempted. macinashutosh@google.com chromeos-commercial-crd@google.com Reports the user type for the attempted session only when the result is EnterpriseCrdSessionResultCode::SUCCESS. macinashutosh@google.com chromeos-commercial-crd@google.com Reports success/failure when a session is attempted for the {Enterprise_CrdSessionType} and {Enterprise_UserSessionType} macinashutosh@google.com chromeos-commercial-crd@google.com Reports duration of a successful session completed for the {Enterprise_CrdSessionType} and {Enterprise_UserSessionType} asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting status of executed device remote commands. The metric includes only signed device remote commands. Reports a final status of finished remote command (e.g. success, failure or termination). {Enterprise_RemoteCommandType} iremuguz@google.com chromeos-commercial-supportability@google.com Reports the failure reason of the FETCH_SUPPORT_PACKET remote command. It will be recorded by DeviceCommandFetchSupportPacketJob class when the command execution has completed with failure. It will indicate in which stage of execution had the failure (e.g. wrong command payload, error when exporting the generated support packet or enqueueing the LogUploadEvent to ReportQueue). asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting received device remote commands. The metric includes signed device remote commands, both valid and invalid. Valid remote command is counted by its type. Invalid remote command is counted by a reason why it is considered invalid (e.g. unknown type or duplication). asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting device remote commands invalidations received with and without payloads. Invalidations indicate that there is a remote command to execute. Payloads provide context about the remote commands update, but may be absent if dropped by the invalidation service. Metric is similar to Enterprise.DevicePolicyInvalidations2. Device local account scope does not exist for remote commands so there is no metric for remote commands similar to Enterprise.DeviceLocalAccountPolicyInvalidations2. rbock@google.com chromeos-commercial-remote-management@google.com managed-devices@google.com Recorded every time policy file is missing or corrupted on Chrome OS. Should be compared to Enterprise.DeviceSettings.UpdatedStatus as happens only if status is STORE_NO_POLICY and device being not managed. rbock@google.com chromeos-commercial-remote-management@google.com managed-devices@google.com Recorded every time as DeviceSettingsProvider updates its current state. Used to compare rate of Enterprise.DeviceSettings.MissingPolicyMitigated event. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures an error that occured while trying to get signals from the CrowdStrike agent. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the actual error whenever a {Signal} signal collection request failed with a {ErrorType} error. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the number of items as part of the {Signal} signal collection response. Recorded when the collection request was received. This histogram applies only to parameterized signals. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the number of items collected in a {Signal} signal collection response. Recorded only when the collection request was successful and the signal value represents a collection. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the signal collection latency for the {Signal} signal. Recorded only when the collection {Outcome}. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the number of delta between requested and returned items as part of the {Signal} signal collection response. Recorded when the collection request was completed. This histogram applies only to parameterized signals. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded whenever a device signal collection request {Variant} for a particular signal. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded whenever a permission evaluation has been assessed for a particular user for whom device signals were requested. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Various steps recorded when a device goes through the device trust connector attestation flow with a partner website. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Latency of a {Variant} attestation step in the overarching Device Trust connector's attestation flow. This measures the amount of time required to generate and return a response to the given challenge, which is effectively the last step in the overall attestation flow. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Result of the attestation step in the overarching Device Trust connector's attestation flow. Logged whenever the attestation step finishes, success or failure, and right before the throttled request resumes. lmasopust@google.com rodmartin@google.com cbe-device-trust-eng@google.com Recorded when a device starts the device trust attestation flow with a partner website. This captures the enrollment status of the device where the attestation flow is happening. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded when a Device Trust handshake was completed between the browser and a server. This captures either the success or specific failure of the overall flow. hmare@google.com cbe-device-trust-eng@google.com Policy levels enabled for the Device Trust connector during the DTC inline flow process. The inline flow can occur during a user navigation, and the policy level determines the content of the attestation services' challenge response. seblalancette@google.com cbe-device-trust-eng@google.com Recorded when a key loading attempt was made with an enum value representing either a successful attempt, or different possible errors. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded every time a Device Trust {Variant} key is successfully used to sign a payload. Measures the signing latency in milliseconds. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Recorded every time a Device Trust signing key is successfully loaded from persistence. This captures what trust level this key has, which in turn gives insights into how it was created (e.g. via a TPM or not). hmare@google.com rogerta@chromium.org seblalancette@chromium.org Recorded every time a Device Trust signing key is successfully loaded from persistence. This captures what algorithm this key was generated with. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Recorded every time the browser attempted to {Variant} a Device Trust signing key. This captures the result from this process. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded when the browser received a failed response when triggering a Device Trust key rotation command. The browser will then attempt to categorize the failure using the given enum. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded when the browser failed to trigger a Device Trust key rotation command through the updater for an unknown reason. This will capture the unknown HRESULT returned via the COM APIs. seblalancette@chromium.org cbe-device-trust-eng@google.com Recorded when the browser received a failed response when triggering a Device Trust key rotation command. The browser will then attempt to categorize the failure using the given enum. seblalancette@chromium.org hmare@google.com cbe-device-trust-eng@google.com Recorded when a failed OSStatus code is returned from a Keychain Services API for the {KeyType} keypair during a {Operation} operation. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Recorded when a device attempts to issue an API that interacts with the Secure Enclave signing key in the {KeyType} key storage. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Captures any terminal failures that occur in the Device Trust management service binary during the execution of a command (e.g. key rotation). lmasopust@google.com rodmartin@google.com cbe-device-trust-eng@google.com Recorded when a device starts the device trust attestation flow with a partner website. This captures if the attestation flow was triggered inside of a session or on the login screen. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Captures any terminal failures that occur during the process of creating, storing, and loading a Device Trust signing key pair during a key rotation. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Recorded when a device attempts to rotate its device trust signing key. Chrome will retry a fixed number of times until the operation either succeeds or fails. A value of 1 means the rotation worked on the first try. hmare@google.com rogerta@chromium.org seblalancette@chromium.org Recorded when a device attempts to rotate its device trust signing key. {Nonce} hmare@google.com rogerta@chromium.org seblalancette@chromium.org HTTP status code of the key upload request recorded when a device attempts to rotate its device trust signing key. {Nonce} hmare@google.com rogerta@chromium.org seblalancette@chromium.org Latency recorded when the {Variant} decorator(s) finish collecting their signals. Captures the amount of time required to collect the signals under this scope. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures any client-side errors that caused a key synchronization flow to fail. seblalancette@chromium.org cbe-device-trust-eng@google.com HTTP status code of the key upload request recorded when a device issues a key synchronization request. accorsi@google.com chromeos-dlp@google.com Number of non-expired file events stored in the DlpFilesController::EventStorage. It is recorded each time an entry is added or updated. poromov@chromium.org chromeos-dlp@google.com Recorded when capture mode initialization was blocked by Data Leak Prevention. aidazolic@chromium.org chromeos-dlp@google.com Recorded when the user is warned by Data Leak Prevention before capture mode initialization. poromov@chromium.org chromeos-dlp@google.com Result of Data Leak Prevention evaluation for a data read from the clipboard. aidazolic@chromium.org chromeos-dlp@google.com Number of items stored in the DlpConfidentialContentsCache. It is recorded each time a new entry is cached. poromov@chromium.org chromeos-dlp@google.com Recorded when DataTransferController is initialized, meaning that all clipboard and drag-n-drop operations will be affected by Data Leak Prevention checks. poromov@google.com chromeos-dlp@google.com Time difference between current and the latest sent Data Leak Prevention reporting events for data transfers for which sources and destinations are the same. poromov@chromium.org chromeos-dlp@google.com Recorded when non-empty Data Leak Prevention policy is present and due to that Data Leak Prevention infrastructure is initialized on the client. poromov@chromium.org chromeos-dlp@google.com Result of Data Leak Prevention evaluation for a drag-n-drop operation. accorsi@google.com chromeos-dlp@google.com Recorded when an error occurs during adaptor usage in the Data Leak Prevention daemon. accorsi@google.com chromeos-dlp@google.com Recorded when an error occurs while performing initialization operations in the Data Leak Prevention daemon. accorsi@google.com chromeos-dlp@google.com Recorded when an error occurs during fanotify usage in the Data Leak Prevention daemon. accorsi@google.com chromeos-dlp@google.com Recorded when an error occurs while performing database operations in the Data Leak Prevention daemon. accorsi@google.com chromeos-dlp@google.com Record whether an error occurs during the Data Leak Prevention files policy setup. accorsi@google.com chromeos-dlp@google.com Record whether a Data Leak Prevention event is not reported because of report queue setup issues. accorsi@google.com chromeos-dlp@google.com Record whether the kernel supports fanotify mark filesystem. accorsi@google.com chromeos-dlp@google.com Record whether the kernel supports fanotify delete events. accorsi@google.com chromeos-dlp@google.com Records when a file action is blocked because of Data Leak Prevention policy Files restriction. Identifies which file action was blocked. ayaelattar@google.com chromeos-dlp@google.com Records which file action blocked by Data Leak Prevention policy is reviewed. accorsi@google.com chromeos-dlp@google.com Records when a file action is warned because of Data Leak Prevention policy Files restriction. Identifies which file action was warned. accorsi@google.com chromeos-dlp@google.com Records which file action was warned because of Data Leak Prevention policy restrictions and proceeded by the user. ayaelattar@google.com chromeos-dlp@google.com Records which file action warning by Data Leak Prevention policy was reviewed. ayaelattar@google.com chromeos-dlp@google.com Records which file action was warned because of Data Leak Prevention policy and the warning timed out. aidazolic@google.com chromeos-dlp@google.com Records True when opening the Files App to show a Data Leak Prevention dialog times out, and False when it successfully opens. ayaelattar@google.com chromeos-dlp@google.com Records the number of files blocked by Data Leak Prevention policy per file action. poromov@chromium.org chromeos-dlp@google.com Recorded when Data Leak Prevention policy contains Files restrictions and DLP Files daemon is started because of that. ayaelattar@google.com chromeos-dlp@google.com Records the number of files warned by Data Leak Prevention policy per file action. poromov@chromium.org chromeos-dlp@google.com Result of Data Leak Prevention evaluation for printing. aidazolic@chromium.org chromeos-dlp@google.com Recorded when there is a "warn" level Data Leak Prevention evaluation for printing. aidazolic@chromium.org chromeos-dlp@google.com Recorded when the user proceeded with (True) or canceled (False) the action after a Data Leak Prevention warning for printing. aidazolic@chromium.org chromeos-dlp@google.com Recorded when there is a "warn" level Data Leak Prevention evaluation for a screen share, but it is caused by the content that the user was already warned about and decided to proceed, so no new warning is shown and printing is silently allowed. poromov@chromium.org chromeos-dlp@google.com Recorded when privacy screen was enforced by Data Leak Prevention. poromov@chromium.org chromeos-dlp@google.com Recorded when Data Leak Prevention event with "block" level was reported. Identifies which restriction was blocked and reported. poromov@chromium.org chromeos-dlp@google.com Result of enqueueing Data Leak Prevention event to the reporting queue. poromov@chromium.org chromeos-dlp@google.com Recorded when Data Leak Prevention event with "report" level was reported. Identifies which restriction was reported. poromov@chromium.org chromeos-dlp@google.com Recorded when Data Leak Prevention event with "warn" level was reported. Identifies which restriction was reported. poromov@chromium.org chromeos-dlp@google.com Recorded when Data Leak Prevention event with "warn" level was reported after a user proceeded with a restricted action. Identifies which restriction was reported. poromov@chromium.org chromeos-dlp@google.com Records which types of restrictions are present in Data Leak Prevention policy. accorsi@google.com chromeos-dlp@google.com Time difference between the current and the latest sent Data Leak Prevention file events for which inodes and destinations are the same. poromov@chromium.org chromeos-dlp@google.com Result of Data Leak Prevention evaluation for a screen share. poromov@chromium.org chromeos-dlp@google.com Recorded when screen share was paused (True) or resumed (False) by Data Leak Prevention. aidazolic@chromium.org chromeos-dlp@google.com Recorded when there is a "warn" level Data Leak Prevention evaluation for a screen share. aidazolic@chromium.org chromeos-dlp@google.com Recorded when the user proceeded with (True) or canceled (False) the action after a Data Leak Prevention warning for a screen share. aidazolic@chromium.org chromeos-dlp@google.com Recorded when there is a "warn" level Data Leak Prevention evaluation for a screen share, but it is caused by the content that the user was already warned about and decided to proceed, so no new warning is shown and the screen share is silently allowed. poromov@chromium.org chromeos-dlp@google.com Result of Data Leak Prevention evaluation for taking a screenshot or a video capture. aidazolic@chromium.org chromeos-dlp@google.com Recorded when there is a "warn" level Data Leak Prevention evaluation for taking a screenshot or a video capture. aidazolic@chromium.org chromeos-dlp@google.com Recorded when the user proceeded with (True) or canceled (False) the action after a Data Leak Prevention warning shown at the capture mode initialization or before taking a screenshot or a video capture. aidazolic@chromium.org chromeos-dlp@google.com Recorded when there is a "warn" level Data Leak Prevention evaluation for initiating capture mode, or taking a screenshot or a video capture, but it is caused by the content that the user was already warned about and decided to proceed, so no new warning is shown and the screen share is silently allowed. poromov@chromium.org chromeos-dlp@google.com Recorded when video capture was interrupted by Data Leak Prevention. rbock@google.com chromeos-commercial-remote-management@google.com managed-devices@google.com Number of retries the client did to execute a DeviceManagementServer request. It's recorded after the request has been completed, either successfully after 0 or more retries, with a failure (too many retries or non-retriable error) or with a server error. {EnterpriseDMServerRequest} rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org rbock@google.com zmin@chromium.org igorcov@chromium.org chromeos-commercial-remote-management@google.com Whether loading of device policy from file on an enterprise-enrolled (checked against install_attributes.pb) Chrome OS device yields an enterprise policy. Filled once during session startup, after first successful device policy read. igorcov@chromium.org chromeos-commercial-remote-management@google.com Whether loading of device policies from file on an enterprise-enrolled (checked against install_attributes.pb) Chrome OS device yields a PolicyData message with a DMToken. Filled once during session startup, after first successful device policy read. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to device enrollment on new installs of Chrome OS devices. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to attestation-based enrollment (Zero-Touch) of Chrome OS devices. Warning: this histogram was expired from 2021-12-05 to 2022-02-01. Data may be missing. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to forced re-enrollment (FRE) of Chrome OS devices. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to attestation-based re-enrollment (Auto RE) of Chrome OS devices. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to forced initial enrollment of Chrome OS devices during the first startup of a device. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to attestation-based initial enrollment (Zero-Touch) of Chrome OS devices during the first startup of a device. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to manual fallback from attestation-based initial enrollment (Zero-Touch) of Chrome OS devices during the first startup of a device. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to manual fallback from attestation-based re-enrollment (Auto RE) of Chrome OS devices. Warning: this histogram was expired from 2021-12-05 to 2022-02-01. Data may be missing. andreydav@google.com rodmartin@google.com chromeos-commercial-identity@google.com Recorded when we fetch the value of enrollment nudge policy. Tracks the value of the policy or the absence of it in the server response. andreydav@google.com rodmartin@google.com chromeos-commercial-identity@google.com Tracks user actions on the enrollment nudge pop-up on the Gaia screen. Recorded when user clicks on one of the buttons there. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Events related to Chrome OS enterprise enrollment recovery. Note that this only covers cases in which prior to recovery, UMA stats are enabled by policy. crisguerrero@chromium.org mpolzer@google.com chromeos-commercial-remote-management@google.com Events related to attestation based re-enrollment after enterprise rollback. Events are recorded during enrollment after rollback and types are listed in the MetricEnrollment enum. crisguerrero@chromium.org mpolzer@google.com chromeos-commercial-remote-management@google.com Events related to manual re-enrollment after enterprise rollback. This is used when attestation based enrollment fails. Events are recorded during enrollment after rollback and types are listed in the MetricEnrollment enum. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Elapsed time from *after* GAIA login until enrollment was cancelled. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Elapsed time from *after* GAIA login until enrollment failed. asumaneev@google.com sergiyb@chromium.org chromeos-commercial-remote-management@google.com Elapsed time from *after* GAIA login until enrollment succeeded. anthonyvd@chromium.org chrome-enterprise-team-core@google.com Events for counting CBCM policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. Subset of "Enterprise.CBCMPolicyInvalidations". Gets recorded only when FCMInvalidationService is used as InvalidationService. anthonyvd@chromium.org chrome-enterprise-team-core@google.com Events measuring effectiveness of refreshing CBCM policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. Subset of "Enterprise.CBCMPolicyRefresh". Gets recorded only when FCMInvalidationService is used as InvalidationService. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting device local account policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. Subset of "Enterprise.DeviceLocalAccountPolicyInvalidations2". Gets recorded only when FCMInvalidationService is used as InvalidationService. As opposed to current histogram, Enterprise.FCMInvalidationService.DevicePolicyInvalidations2 counts only events of device policy invalidations. asumaneev@google.com chromeos-commercial-remote-management@google.com Events measuring effectiveness of refreshing device local account policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. Subset of "Enterprise.DeviceLocalAccountPolicyRefresh3". Gets recorded only when FCMInvalidationService is used as InvalidationService. As opposed to current histogram, Enterprise.FCMInvalidationService.DevicePolicyRefresh3 counts only events of refreshing device policies. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting device policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. Subset of "Enterprise.DevicePolicyInvalidations2". Gets recorded only when FCMInvalidationService is used as InvalidationService. As opposed to current histogram, Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyInvalidations2 counts only events of device local account policy invalidations. asumaneev@google.com chromeos-commercial-remote-management@google.com Events measuring effectiveness of refreshing device policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. Subset of "Enterprise.DevicePolicyRefresh3". Gets recorded only when FCMInvalidationService is used as InvalidationService. As opposed to current histogram, Enterprise.FCMInvalidationService.DeviceLocalAccountPolicyRefresh3 counts only events of refreshing device local account policies. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting user policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. Subset of "Enterprise.PolicyInvalidations". Gets recorded only when FCMInvalidationService is used as InvalidationService. asumaneev@google.com chromeos-commercial-remote-management@google.com Tracks the result of registration for policy invalidations. It will fail when duplicate invalidation names are used for different policies due to http://b/119860379. Subset of "Enterprise.PolicyInvalidationsRegistrationResult". Gets recorded only when FCMInvalidationService is used as InvalidationService. asumaneev@google.com chromeos-commercial-remote-management@google.com Events measuring effectiveness of refreshing user policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. Subset of "Enterprise.PolicyRefresh2". Gets recorded only when FCMInvalidationService is used as InvalidationService. emaxx@chromium.org igorcov@chromium.org vsavu@google.com chromeos-commercial-remote-management@google.com Chrome OS only. Result of checking if device policy files are valid when reading the device policy data. mpetrisor@chromium.org imprivata-eng@google.com ChromeOS only. Records if cleanup handler succeeded. mpetrisor@chromium.org imprivata-eng@google.com ChromeOS only. Records the duration the cleanup handler took. igorruvinov@chromium.org zmin@chromium.org Records whether browser unenrollment via DMToken deletion completed succcessfully after attempting to delete the token. rogerta@chromium.org zmin@chromium.org Time since the enrollment request was made until an error is returned from the server. zmin@chromium.org rogerta@chromium.org Time since the enrollment request was made until a successful enrollment response is returned from the server. zmin@chromium.org rogerta@chromium.org The result of machine level user cloud policy enrollment. zmin@chromium.org rogerta@chromium.org Records whether the machine level user cloud policy enrollment dialog is shown to the user and the action they took. zmin@chromium.org rogerta@chromium.org The length of time the machine level user cloud policy enrollment dialog was visible to the user. zmin@chromium.org domfc@chromium.org Records whether a browser unenrollment was completed succcessfully by writing an invalid DMToken to storage or not. mpetrisor@chromium.org imprivata-eng@google.com Records whether the managed screensaver is enabled. Recorded for managed devices when the sign-in screen is displayed, on every user login, and every time the ScreensaverLockScreenEnabled or DeviceScreensaverLoginScreenEnabled policy is updated. mpetrisor@chromium.org imprivata-eng@google.com Among users with managed screensaver enabled, records the length of each session for Slideshow. The metric is emitted when an ambient mode session ends. mpetrisor@chromium.org imprivata-eng@google.com Records the count of images downloaded in cache to display in the managed screensaver. Recorded every time the policy list changes and images are deleted from the cache or downloaded to the cache. mpetrisor@chromium.org imprivata-eng@google.com Records the result after attempting to download an image for the managed screensaver. Emitted on every image download operation. mpetrisor@chromium.org imprivata-eng@google.com Records the amount of time it takes for the managed screensaver to start. This includes tasks such as getting the list of downloaded images, checking that the list has a minimal amount of images, decoding them, etc. Note this measurement does not include the lock screen inactivity timeout. The metric would be emitted when the first two images are loaded succcessfully. domfc@chromium.org webprotect-team@google.com Records the size (in bytes) of data that might have been scanned by the OnBulkDataEntry Enterprise Connector. Is is logged once per user action that would trigger this Connector. mnissler@chromium.org Result of the OpenNetworkConfiguration policy validation. domfc@chromium.org dpr-eng@google.com Records the type of printing the user attempted that triggered content analysis. Is is logged once per user action that would trigger this Connector. igorruvinov@chromium.org zmin@chromium.org The number of proof-of-possession cookies retrieved from the platform to authenticate the user to their IdP/STS. Recorded once per successful fetch. igorruvinov@chromium.org zmin@chromium.org The HRESULT returned by either CoCreateInstance or GetCookieInfoForUri when trying to fetch proof-of-possession cookies from the platform to authenticate the user to their IdP/STS. igorruvinov@chromium.org zmin@chromium.org The elapsed time for a fetch of proof-of-possession cookies from the platform to authenticate the user to their IdP/STS to {Result}. Recorded once per fetch. vsavu@google.com asumaneev@google.com chromeos-commercial-remote-management@google.com A set of enterprise policy rules that are in use. This is recorded every 24 hours and at startup, if the last recording was earlier than a day before. zmin@chromium.org igorruvinov@chromium.org chromeos-commercial-remote-management@google.com Record summary of sources of all policies. It's recorded ever 24 hours and at startup. This does not include user cloud policy and some speicial policy sources like enterprise_default. zmin@chromium.org qiutanw@google.com chromeos-commercial-remote-management@google.com A set of {PolicyLevel} enterprise policy rules that are in use. This is recorded for each {PolicyLevel} policy every 24 hours and at startup, if the last recording was earlier than a day before. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting user policy invalidations received with and without payloads. Invalidations indicate that a policy has been updated and should be refreshed. Payloads provide context about the policy update, but may be absent if dropped by the invalidation service. asumaneev@google.com chromeos-commercial-remote-management@google.com Tracks the result of registration for policy invalidations. It will fail when duplicate invalidation names are used for different policies due to http://b/119860379. mnissler@chromium.org Time since startup of the cloud policy code until the policy invalidation service first reported its online status. mnissler@chromium.org Load status from the policy loaders which pull policy settings from the underlying platform, such as Windows Group Policy. asumaneev@google.com chromeos-commercial-remote-management@google.com Events measuring effectiveness of refreshing user policy when invalidations are received from a service. For each refresh, indicates whether the policy changed, and whether the policy was invalidated at the time of the refresh. zmin@chromium.org src/components/policy/OWNERS The total number of time {ButtonType} button has been clicked for each time chrome://policy page is opened. Recorded once the page is closed. Export To JSON button is not available on iOS. Note that we won't be able to collect the data if the page is not closed normally. For example, browser is crash or shutdown by OS which often happens on mobile platforms. rbock@google.com igorcov@chromium.org chromeos-commercial-remote-management@google.com Time since last device policy fetch. Emitted when policies are loaded. zmin@chromium.org pastarmovj@chromium.org Time since last machine level user policy fetch.. Emitted when policies are loaded. rbock@google.com igorcov@chromium.org chromeos-commercial-remote-management@google.com Time since last user policy fetch. Emitted when policies are loaded. poromov@chromium.org chromeos-commercial-remote-management@google.com Tracking the results of policy user verification. hmare@google.com cbe-device-trust-eng@google.com Recorded in the event of failures during the profile identifier generation action. hmare@google.com cbe-device-trust-eng@google.com Records whether the profile identifier generation action was successful or not. ydago@chromium.org zmin@chromium.org The Http statuses returned by the server when trying to get the ManagedAccounsSigninRestriction policy value for individual dasher accounts. This is recorded after trying to the the policy value, when the status is available. ydago@chromium.org zmin@chromium.org The network errors that happen when trying to get the ManagedAccounsSigninRestriction policy value for individual dasher accounts. This is recorded every time after trying to the the policy value. bfranz@chromium.org chromeos-kiosk-eng@google.com A public session starts when a user signs in using the policy configured public account. It stops when the user signs out. Session length is the duration between the start and stop events. It is recorded during signing out and reported on the next chrome run. This metric tracks the recorded session length rounded down to the nearest 10-minute bucket and capped at 24 hours. rogerta@chromium.org Number of retries the client did to execute a real-time reporting upload request. It's recorded after the request has been completed, either successfully after 0 or more retries, with a failure (too many retries or non-retriable error) or with a server error. bfranz@chromium.org chromeos-kiosk-eng@google.com A regular user session starts when a user signs in using his/her user account. It stops when the user signs out. Session length is the duration between the start and stop events. It is recorded during signing out and reported on the next chrome run. This metric tracks the recorded session length on an enrolled device rouned down to the nearest 10-minute bucket and capped at 24 hours. asumaneev@google.com chromeos-commercial-remote-management@google.com Tracks whether remote commands invalidator registered for corresponding invalidations. In case of success the invalidator is able to receive incoming invalidations. Metric is similar to Enterprise.PolicyInvalidationsRegistrationResult. xanth@google.com alshawwa@chromium.org domfc@chromium.org Failures to upload reporting events to the reporting server bucketed by event type. xanth@google.com alshawwa@chromium.org domfc@chromium.org Reporting events successfully uploaded to the reporting server bucketed by event type. rodmartin@google.com chromeos-commercial-identity@google.com Latency of a SecondaryGoogleAccountUsage policy fetch request. This measures the amount of time required to fetch the policy value of SecondaryGoogleAccountUsage from the Secure Connect API. This is recorded when a user account is added as a secondary account (in-session). rodmartin@google.com chromeos-commercial-identity@google.com Tracks the result of UserCloudSigninRestrictionPolicyFetcher::GetSecondaryGoogleAccountUsage. This is recorded when a user account is added as a secondary account (in-session). sergiyb@google.com chromeos-commercial-remote-management@google.com Captures state of device identifiers during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks whether embargo date has passed during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Captures situations when state determination is enabled. sergiyb@chromium.org chromeos-commercial-remote-management@google.com Network error code for unified state determination kill switch config requests. sergiyb@chromium.org chromeos-commercial-remote-management@google.com Number of tries for fetching unified state determination kill switch config. sergiyb@google.com chromeos-commercial-remote-management@google.com Captures situations when state determination takes place on Flex devices. sergiyb@google.com chromeos-commercial-remote-management@google.com Captures ownership state of device during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks whether PSM has reported that state is available during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks whether state keys were retrieved during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks whether state request returned state during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks the duration of the {Step} as part of state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks whether system clock was synchronized during state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks the total duration of state determination. sergiyb@google.com chromeos-commercial-remote-management@google.com Tracks the total duration of state determination when it results in {State} state. sergiyb@chromium.org chromeos-commercial-remote-management@google.com Device management server request status for {RequestType} requests to Device Management server. sergiyb@chromium.org chromeos-commercial-remote-management@google.com Network error code for {RequestType} requests to Device Management server. ayaelattar@chromium.org poromov@chromium.org Shows which system features are set to be disabled by SystemFeaturesDisableList policy. Recorded when the policy preference is updated with a new system feature. No-op updates aren't counted. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the actual error whenever parsing of {Signal} from WMI results failed. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the actual error whenever collection of {Signal} from WMI failed with a query error. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the actual error whenever parsing of AntiVirus info from WSC results failed. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the actual error whenever collection of AntiVirus info from WSC failed with a query error. seblalancette@chromium.org cbe-device-trust-eng@google.com Captures the response parsing error rate whenever collecting {Signal}. emaxx@chromium.org pmarko@chromium.org Duration of the initial policy load operation (including reading from cache or fetching over network, parsing and validating) during {ProfileType} session startup. emaxx@chromium.org pmarko@chromium.org Duration between when the construction of the policy stack for a user profile starts and when its initialization gets untrottled. Only reported on ChromeOS Ash, only for managed users who are primary users in the given session. The values are capped at around 5 seconds, and timeouts are reported as this upper boundary value as well. vincb@google.com ftirelo@chromium.org Records the number of user policies that are active when using a managed account. Recorded once during the profile's browsing session on the first policy update after signing in with a managed account. agawronska@chromium.org michaelpg@chromium.org Failure reason for OAuth token fetch for child user. igorcov@chromium.org asumaneev@google.com chromeos-commercial-remote-management@google.com Service error during OAuth2 access token fetch. There is a gap in data as the histogram was expired from 2022-03-01 till 2023-02-09. hendrich@chromium.org rbock@google.com chromeos-commercial-remote-management@google.com managed-devices@google.com Re-registration results after failed policy fetch. asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting status of executed user remote commands. The metric includes only signed user remote commands. Reports a final status of finished remote command (e.g. success, failure or termination). {Enterprise_RemoteCommandType} asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting received user remote commands. The metric includes signed user remote commands, both valid and invalid. Valid remote command is counted by its type. Invalid remote command is counted by a reason why it is considered invalid (e.g. unknown type or duplication). asumaneev@google.com chromeos-commercial-remote-management@google.com Events for counting user remote commands invalidations received with and without payloads. Invalidations indicate that there is a remote command to execute. Payloads provide context about the remote commands update, but may be absent if dropped by the invalidation service. Metric is similar to Enterprise.PolicyInvalidations. xiyuan@chromium.org sduraisamy@chromium.org Tracks the sign-in events on an enrolled device. lmasopust@google.com rodmartin@chromium.org cbe-device-trust-eng@google.com Recorded when building a response for a challenge from Verified Access server for remote attestation during SAML authentication. This captures if Device Trust is configured alongside Verified Access for the current endpoint or not. vsavu@google.com igorcov@chromium.org chromeos-commercial-remote-management@google.com The result of Chrome reading the VPD cache on Chrome OS. igorcov@chromium.org tnagel@chromium.org chromeos-commercial-remote-management@google.com The status code (exit code or signal) from sanity check of RW_VPD read and matching the contents with data from dump_vpd_log (Chrome OS). There is a gap in data as the histogram was expired from 2020-07-05 till 2023-02-09. igorcov@chromium.org tnagel@chromium.org chromeos-commercial-remote-management@google.com The status code (exit code or signal) from VPD update operation (Chrome OS). igorruvinov@chromium.org ydago@chromium.org pastarmovj@chromium.org rogerta@chromium.org zmin@chromium.org Time elapsed for checking the Azure AD join status. This is only recorded once during the first successful join status check. ydago@chromium.org pastarmovj@chromium.org rogerta@chromium.org Whether the machine is part of an AD domain. This check is performed once at start-up on Windows. olsen@chromium.org chromeos-commercial-remote-management@google.com A set of policy rules that failed validation due to unparsable JSON, or JSON that did not match the schema. This validation happens on start-up and when the policy has changed. The histogram was expired (not recording data) from 2020-06-18 until 2021-03-15 and from 2021-07-01 to 2022-10-23. pastarmovj@chromium.org ydago@chromium.org A set of policy rules that were ignored due to integrity violations while parsing the policy data which happens on start-up and when the policy has changed. pastarmovj@chromium.org zmin@chomium.org The number of disabled policy entries on Windows due to integrity violations while parsing the policy data which happens on start-up and when the policy has changed. pastarmovj@chromium.org rogerta@chromium.org zmin@chromium.org Whether the machine is joined to an AD domain. This check is performed once at start-up on Windows. pastarmovj@chromium.org rogerta@chromium.org zmin@chromium.org Whether the machine is considered an enterprise user. An enterprise user is either in a domain, either local or cloud via AAD. This check is performed once at start-up on Windows. twellington@google.com tedchcoc@chromium.org On Android (OS version Lollipop+): Whether the device has a "device owner" app installed. This check is performed once on application start-up. igorruvinov@chromium.org ydago@chromium.org pastarmovj@chromium.org rogerta@chromium.org zmin@chromium.org Whether the machine is joined to an Azure AD domain or the user has added one or more work/school accounts to their login session. This check is performed once at start-up on Windows. zmin@chromium.org pastarmovj@chromium.org rogerta@chromium.org Whether the full machine name is the same as the short one, identifying a local machine. This check is performed once at start-up on Windows. zmin@chromium.org pastarmovj@chromium.org rogerta@chromium.org Whether the currently logged in user is a local user or not, based on its SAM compatible user name and machine name. This check is performed once at start-up on Windows. zmin@chromium.org rogerta@chromium.org pastarmovj@chromium.org On Windows: Whether the machine is managed via MDM. On macOS: Whether Chrome found a file of managed policies to follow. On Android (OS version Lollipop+): Whether the device has a profile owner app. This check is performed once on application start-up. pastarmovj@chromium.org rogerta@chromium.org zmin@chromium.org Whether the machine is managed or part of an enterprise. This includes devices that are either in a domain or managed via MDM. This check is performed once at start-up on Windows. pastarmovj@chromium.org zmin@chromium.org On the Mac: Whether the current user has an enterprise identity in Open Directory. This check is performed once at start-up. pastarmovj@chromium.org zmin@chromium.org On the Mac: Whether the machine is joined to a domain. This check is performed once at start-up. pastarmovj@chromium.org zmin@chromium.org On the Mac: Whether the machine is managed via MDM, with data obtained via a new method (profiles) that is only available in 10.13.4 or later. This check is performed once at start-up. pastarmovj@chromium.org zmin@chromium.org On the Mac: Whether the machine is managed via MDM, with data obtained via an old method (system_profiler). This check is performed once at start-up. ydago@chromium.org pastarmovj@chromium.org The rough Windows suite we are running on. This check is performed once at start-up on Windows. The histogram was removed in 108 and reinstated in 111.