jamescook@chromium.org tbarzic@chromium.org chromeos-launcher@google.com zhangwenyu@google.com jimmyxgong@chromium.org zentaro@chromium.org cros-peripherals@google.com azeemarshad@chromium.org cros-connectivity@google.com hsuregan@chromium.org wmahon@chromium.org chromeos-tango@google.com jackshira@google.com julietlevesque@google.com chromeos-cross-device-eng@google.com rsorokin@chromium.org tomhughes@chromium.org cros-oac@google.com chromeos-fingerprint@google.com rsorokin@chromium.org cros-oac@google.com hansenmichael@google.com nearby-share-chromeos-eng@google.com hansenmichael@google.com nearby-share-chromeos-eng@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com hansberry@chromium.org chromeos-cross-device-eng@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com kenalba@google.com chromeos-tango@google.com jamescook@chromium.org tbarzic@chromium.org chromeos-launcher@google.com enlightened@chromium.org chromeos-hardening@google.com Records the number of unique processes on the system that attempted to execute a memory file descriptor. Processes are scanned for this anomaly every thirty seconds, but the metric is recorded every two hours on ChromeOS devices. If the metric is recorded successfully, the process count is reset. So the metric represents the number of anomalous processes found in a two-hour scan window or since the last successful recording event. enlightened@chromium.org chromeos-hardening@google.com Records the number of unique processes on the system that do not have the minimum sandboxing measures applied in order to avoid the forbidden intersection: https://chromium.googlesource.com/chromiumos/docs/+/HEAD/sandboxing.md#The-forbidden-intersection As a caveat, SELinux is not considered as only an enforcing domain provides meaningful coverage. Processes are scanned for this anomaly every thirty seconds, but the metric is only sent once per boot and only in the logged-in state. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records the app platform shown as the result of link intent handling. Recorded when the user makes a choice in the Intent Picker dialog, and when the result of a previous user preference is applied during a link click. chingkang@google.com cros-hwsec+umas@chromium.org Records the status of attestation flow. The value represents 6 flags in 6 rightmost bits; starting from more significant bits they mean: 1. Has proxy. 2. Is System proxy active. 3. Run the default flow. 4. The default flow succeeds. 5. Run the fallback flow. 6. The fallback flow succeeds. chingkang@google.com cros-hwsec+umas@chromium.org Records the status of `AttesttionClient::GetCertificate()` called by `AttestationFlowIntegrated`. Warning: this histogram was expired from Oct 8, 2022 to June 26, 2023; data may be missing. kamesan@chromium.org chromeos-camera-eng@google.com Records the average latency in running the detector during an Auto Framing enabled camera session. Emitted when the camera session is closed. This metric is reported on ChromeOS devices with Auto Framing enabled. kamesan@chromium.org chromeos-camera-eng@google.com Records the rate that the detector successfully detects a subject in the scene during an Auto Framing enabled camera session. Emitted when the camera session is closed. kamesan@chromium.org chromeos-camera-eng@google.com Records the number of times that Auto Framing is toggled from off to on by the user during a camera session. Emitted when the camera session is closed. kamesan@chromium.org chromeos-camera-eng@google.com Records the percentage of time that Auto Framing is turned on during a camera session. Emitted when the camera session is closed. kamesan@chromium.org chromeos-camera-eng@google.com Records errors in Auto Framing that can break camera functionality or cause frame drops. Emitted at most once for each error when the camera session is closed. kamesan@chromium.org chromeos-camera-eng@google.com Records the median of sampled zoom ratios when Auto Framing zooms in camera frames to the subject during a camera session. beckerh@chromium.org chromeos-camera-eng@google.com Records the resolution of output stream that is configured by Chrome OS camera service. beckerh@chromium.org chromeos-camera-eng@google.com Records the process time of ConfigureStreams() method in Chrome OS camera service. This metric is reported for all users and will not cause abnormal distribution since the metric is Chrome OS specified. skyostil@chromium.org chromeos-camera-eng@google.com Records the first error encountered in a camera which uses effects. This metric is emitting once every hour if the camera session exceeds an hour, and once at the end of every session. skyostil@chromium.org chromeos-camera-eng@google.com Records the number streams that required rendering effects in a camera session which uses effects. This metric is emitting once every hour if the camera session exceeds an hour, and once at the end of every session. skyostil@chromium.org chromeos-camera-eng@google.com Records the number streams in a camera session which uses effects. This metric is emitting once every hour if the camera session exceeds an hour, and once at the end of every session. skyostil@chromium.org chromeos-camera-eng@google.com Records the number of still capture shots taken in a camera session which uses effects. This metric is emitting once every hour if the camera session exceeds an hour, and once at the end of every session. jmpollock@chromium.org chromeos-camera-eng@google.com Records a user enabling a camera effect. Emitted at most once per camera effect chosen when the camera session is closed, or every hour if the session duration exceeds an hour (and then at the end of the session). jmpollock@chromium.org chromeos-camera-eng@google.com Records average wall time interval between successfully processed frames within the EffectsStreamManipulator for the different effect + stream type combinations. This metric is reported on ChromeOS devices with an effect applied that does not encounter an error during processing. It is emitted at the close of each camera session, or every hour if the session duration exceeds an hour (and then at the end of the session). jmpollock@chromium.org chromeos-camera-eng@google.com Records the wall time taken to execute the EffectsStreamManipulator ProcessCaptureResult method for the different effect + stream type combinations. Calculated as the average processing time / latency over the camera session. This metric is reported on ChromeOS devices with an effect applied that does not encounter an error during processing. It is emitted at the close of each camera session, or every hour if the session duration exceeds an hour (and then at the end of the session). skyostil@chromium.org chromeos-camera-eng@google.com Records the number of pixels in one frame of the largest stream in a camera session which uses effects. This metric is emitting once every hour if the camera session exceeds an hour, and once at the end of every session. skyostil@chromium.org chromeos-camera-eng@google.com Records the number of pixels in one frame of the smallest stream in a camera session which uses effects. This metric is emitting once every hour if the camera session exceeds an hour, and once at the end of every session. beckerh@chromium.org chromeos-camera-eng@google.com Records the type of the error which triggers the Notify() method in Chrome OS camera service. beckerh@chromium.org chromeos-camera-eng@google.com Records face auto exposure function status of the Chrome OS device. The metric is reported when the camera is detected. beckerh@chromium.org chromeos-camera-eng@google.com Records max number of detected faces of the camera session in Chrome OS camera service. The metric is reported when the camera is closed. beckerh@chromium.org chromeos-camera-eng@google.com Records the camera facing of the camera session in Chrome OS camera service. jcliang@chromium.org chromeos-camera-eng@google.com Records the average auto exposure convergence latency in frame count throughout a camera session that runs Gcam auto exposure. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the average HDR ratio throughout a camera session that runs Gcam auto exposure. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the average total exposure time (TET) throughout a camera session that runs Gcam auto exposure. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the average CPU latency in running a given type of processing throughout a HDRnet camera session. Emitted when the camera session is closed. This metric is reported on all ChromeOS devices with HDRnet enabled. jcliang@chromium.org chromeos-camera-eng@google.com Records whether there's an error that can compromise the HDRnet feature, either causing frame drops or stops the pipeline from running completely, throughout a HDRnet camera session. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the maximum number of output buffers a HDRnet stream produces (greater than 1 means there are multiple streams with the same aspect ratio) throughtout a HDRnet camera session. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the maximum size (in width * height pixels) of the HDRnet stream configured for a given output in a HDRnet camera session. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the number of concurrent HDRnet streams in a HDRnet camera session. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the number of HDRnet-rendered still capture shots taken in a HDRnet camera session. Emitted when the camera session is closed. jcliang@chromium.org chromeos-camera-eng@google.com Records the stream configuration including the number of streams, the type of streams, and if the streams are of the same aspect ratio in a HDRnet camera session. Emitted when the camera session is closed. beckerh@chromium.org chromeos-camera-eng@google.com Records the process time of the JDA (Jpeg Decode Accelerator) or JEA (Jpeg Encode Accelerator) run on Chrome OS camera service. There are suffixes that record the runner method (hardware/software), the runner type (decode/encode). This metric is reported for all users and will not cause abnormal distribution since the metric is Chrome OS specified. beckerh@chromium.org chromeos-camera-eng@google.com Records the resolution of the image that JDA/JEA process by Chrome OS camera service. The resolution represents by the total pixels contained in the image. There are suffixes that record the runner method (hardware/software), the runner type (decode/encode). dorahkim@google.com chromeos-camera-eng@google.com Records a camera's module id in a format of integer when a camera is open. If it is one of the top 20 popular camera peripherals, it records the module id and if not it records zero. dorahkim@chromium.org chromeos-camera-eng@google.com Records which client type (e.g., Chrome, Android) is opening a camera device. beckerh@chromium.org chromeos-camera-eng@google.com Records the process time of OpenDevice() method in Chrome OS camera service. This metric is reported for all users and will not cause abnormal distribution since the metric is Chrome OS specified. julianachang@google.com chromeos-camera-eng@google.com Records the average processing latency to execute the PortraitModeStreamManipulator ProcessCaptureResult method. Emitted when the camera session is closed. This metric is reported on ChromeOS devices with Portrait Mode enabled. julianachang@google.com chromeos-camera-eng@google.com Records whether there's an error that can compromise the Portrait Mode feature. Emitted at most once for each error when the camera session is closed. julianachang@google.com chromeos-camera-eng@google.com Records the number of still capture shots taken in a camera session with Portrait Mode enabled. Emitted when the camera session is closed. beckerh@chromium.org chromeos-camera-eng@google.com Records the session duration in Chrome OS camera service. miersh@google.com pmarko@chromium.org The amount of time it took the {CertProvisioningProtocolVersion} certificate provisioning worker with scope {CertProvisioningScope} to sign a CSR. Emitted after the sign is complete. miersh@google.com pmarko@chromium.org Number of times each event is reached during the {CertProvisioningProtocolVersion} certificate provisioning flow with scope {CertProvisioningScope}. miersh@google.com pmarko@chromium.org The amount of time it took the {CertProvisioningProtocolVersion} certificate provisioning worker with scope {CertProvisioningScope} to generate one key pair. Emitted after the generation is complete. miersh@google.com pmarko@chromium.org For final states (see the list in cert_provisioning::IsFinalState): number of times the {CertProvisioningProtocolVersion} certificate provisioning worker with scope {CertProvisioningScope} finished on every state. For other states: number of times the worker failed on every state. miersh@google.com pmarko@chromium.org The amount of time it took the {CertProvisioningProtocolVersion} certificate provisioning worker with scope {CertProvisioningScope} to build one Verified Access response. Emitted after the response is built. aalexand@google.com gmx@chromium.org cwp-team@google.com A count of successes and various failure modes related to collecting and processing profile data obtained via "perf events" on Chrome OS. aalexand@google.com cwp-team@google.com Record the collection status (success or failure) when the Chrome process and thread types are collected as part of the ChromeOS perf profile collection. gmx@chromium.org cwp-team@google.com Records the status of collection attempts triggered by jankiness on Chrome OS. Warning: this histogram was expired from 08/30/2020 to 03/30/2022; data may be missing. gmx@chromium.org cwp-team@google.com A count of successes and various failure modes related to the parsing of logical CPU frequencies on Chrome OS. Recorded when the browser process starts. shantuo@google.com cwp-team@google.com A count of various locations gotten from parsing a Lacros binary path. This is used to monitor any change to the Lacros path. Recorded when a Lacros binary path was found when CWP collects browser processes. shantuo@google.com cwp-team@google.com A count of successes and various failure modes related to the parsing of PSI CPU data on Chrome OS. Recorded after each perf collection. raging@google.com chromeos-memory@google.com A count of successes and various failure modes related to the parsing of PSI Memory data on Chrome OS. Recorded after each perf collection. raging@google.com chromeos-memory@google.com Reports periodic memory pressure metrics, as seen ChromeOS-wide. Metrics originally come from /proc/pressure/memory readings, expressed as a percentage with 2 decimal points (99.99%), but expressed as p*100, in an integer in the range (1-9999) meaning (00.01% to 99.99%). Underflow value 0 means "no pressure" - 0%. shantuo@google.com cwp-team@google.com A count of the various outcomes related to recording the profile data collected via "perf events" on Chrome OS. The histogram is recorded when system-wide CPU profiling finishes and the collected data is being saved to memory for later upload. aalexand@google.com gmx@chromium.org cwp-team@google.com Records the number of "perf events" reports included in an UMA upload on Chrome OS. xiangdongkong@google.com cros-feedback-app@google.com Records the total time it takes for each sub task of LogTool::GetBigFeedbackLogs to complete. Recording happens on each call to debugd's GetBigFeedbackLogs. enlightened@google.com jorgelo@google.com chromeos-security-core@google.com Records the total time it takes for each call to LogTool::{FunctionName} to complete. Recording happens on each D-Bus call to debugd. zhangwenyu@google.com ashleydp@google.com zentaro@chromium.org cros-peripherals@google.com Records the ProbeError::ErrorType returned on request for {ProbeErrorSourceStruct}. Recorded on the event a request to cros_healthd probe service returns a ProbeError. zhangwenyu@google.com ashleydp@google.com zentaro@chromium.org cros-peripherals@google.com Records error type such as no data error, not a number error and expectation not met error when receiving system information including battery info, network info and system info. All errors are recorded. zhangwenyu@google.com ashleydp@google.com gavinwill@chromium.org zentaro@chromium.org cros-peripherals@google.com Records requested initial screen when opening the Diagnostics App. zhangwenyu@google.com dpad@chromium.org michaelcheco@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the duration that the user spent in the Keyboard Tester. Emitted when the user closes the keyboard tester. zhangwenyu@google.com ashleydp@google.com gavinwill@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the duration that the Memory Routine took to complete. Emitted when the routine completes successfully. zhangwenyu@google.com ashleydp@google.com gavinwill@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the duration that the Diagnostics App is open. emitted when the app is closed. zhangwenyu@google.com ashleydp@google.com gavinwill@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the number of routines run while the Chrome OS Diagnostics App was open. Begins at zero each time the app is open and recorded each time the app is closed. zhangwenyu@google.com ashleydp@google.com gavinwill@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the duration that the Diagnostics App is open for a given page view. Emitted when the active page changes or when the app is closed. Cumulatively adds up to the total duration recorded by "ChromeOS.DiagnosticsUi.OpenDuration" or "ChromeOS.FeatureUsage.DiagnosticsUi.Usetime". zhangwenyu@google.com ashleydp@google.com gavinwill@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the result of the {RoutineType} Routine. rsorokin@chromium.org cros-oac@google.com Records device eligibility, enabled status, and success rate for the {FeatureName} feature. Different events are recorded at different times, as described in the enum labels. rsorokin@chromium.org cros-oac@google.com Records the duration of time (ms) a given {FeatureName} feature was used. jimmyxgong@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the result of installing a firmware update. Recorded once per install and the histogram is emitted either when an install is completed or when a failure state is reached. An example failure state is if we're unable to create a firmware update directory. jimmyxgong@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the total number of devices found. OnStartup is recorded when a user first logs in and OnRefresh is recorded for any subsequent request. The cases in which a subsequent request will be made are when the Firmware Update SWA is launched, when an install is completed, and when we detect that a device has been added or removed. jimmyxgong@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the total number of {Severity} firmware updates found for all of the peripherals currently connected. The histogram is emitted once we've received the list of updates (if any) for all peripherals. OnStartup is recorded when a user first logs in and OnRefresh is recorded for any subsequent request. The cases in which a subsequent request will be made are when the Firmware Update SWA is launched, when an install is completed, and when we detect that a device has been added or removed. bchikhaoui@google.com cros-oac@google.com Records the amount of time spent by user to complete GAIA login. Recorded during user sign-in when Chrome received all the signals from Gaia. rsorokin@google.com cros-3pidp@google.com Records whether or not {MessageName} was received during the {GaiaAuthFlow} authentication on the login screen. Recorded on the successful online authentication only. antrim@chromium.org cros-lurs@google.com Records events for the Gaia password flow. "Started" is recorded on each password entry on the Gaia page. "Completed" is recorded when Gaia authentication succeeds. Note: this is not recorded for SAML flows. itspeter@chromium.org stimim@chromium.org chromeos-runtime-probe@google.com Qualification status of each component types. This entry is generated by hardware_verifier.conf at boot time. itspeter@chromium.org stimim@chromium.org chromeos-runtime-probe@google.com Aggregated result of hardware verifier check. itspeter@chromium.org stimim@chromium.org chromeos-runtime-probe@google.com The amount of time it takes to finish one hardware verification run. itspeter@chromium.org stimim@chromium.org chromeos-runtime-probe@google.com The amount of time it takes to probe hardware components. aalsum@chromium.org jackshira@google.com cros-telemetry@google.com Records the responses for HaTS questions, to be analyzed against other OS metrics like performance or number of crashes. Emitted during the lifecycle of a survey and when a user answers any question on a HaTS survey. weiluanwang@google.com dennyh@google.com cros-tdm-tpe-eng@google.com Records the diagnostic results from healthd to analyze the usage and the pass rate. Emitted when a routine terminates. weiluanwang@google.com dennyh@google.com cros-tdm-tpe-eng@google.com Records the event subscription to healthd to analyze the usage. Emitted when the specific category is requested from a client. weiluanwang@google.com dennyh@google.com cros-tdm-tpe-eng@google.com Records the telemetry results from healthd to analyze the usage and error rate. Emitted when the specific category is requested from a client. chenghaoyang@chromium.org chromeos-sensors-eng@google.com Records the maximum number of concurrent sensor clients within an hour, which indicates how many apps are using sensors. Recorded once every hour. Might not be recorded for tail-end usage during a session. chenghaoyang@chromium.org chromeos-sensors-eng@google.com Records the maximum number of running observers within an hour to any sensor. It indicates how widely used the sensor samples are. Recorded once every hour. Might not be recorded for tail-end usage during a session. chenghaoyang@chromium.org chromeos-sensors-eng@google.com Records the number of opened observer within an hour, which indicates how often sensors are enabled and disabled. Recorded once every hour. Might not be recorded for tail-end usage during a session. chenghaoyang@chromium.org chromeos-sensors-eng@google.com Records the usage of the sensor within an hour with at least {Frequency} Hz. Recorded once every hour. Might not be recorded for tail-end usage during a session. wmahon@google.com chromeos-tango@google.com cros-peripherals@google.com Records the device forms (Keyboard, Mouse, Pointing Stick, etc) of {Type} devices, when they are connected. As one physical device can be multiple forms at the same time (eg. a wireless dongle that identifies as both a keyboard and mouse), multiple entries can be generated from a single physical attachment event. wmahon@google.com chromeos-tango@google.com cros-peripherals@google.com Records the connection types (Internal, Bluetooth, Usb, etc) of {Form} devices, when they are connected. As one physical device can be multiple forms at the same time (eg. a wireless dongle that identifies as both a keyboard and mouse), multiple entries can be generated from a single physical attachment event. dpad@chromium.org cros-peripherals@google.com Records a hash of a keycode + modifier keys pressed everytime a user event is repeated due to auto repeat. This also includes events which are suppressed by downstream system such as the diacritics menu or wayland. See `RecordAutoRepeatUsageMetric` in //ui/events/ash/event_rewriter_ash.cc for information on how to decode the values. dpad@google.com chromeos-tango@google.com cros-peripherals@google.com Records the classification given by ChromeOS to a given keyboard/mouse combo device. These devices could either be keyboards, mice, or devices that actually are "combo" devices that have keyboards and mice on the same physical device. wangdanny@chromium.org dpad@chromium.org cros-peripherals@google.com Records the event rewriter latency metric every time a key is pressed. This metric is reported for all users and will not cause abnormal distribution since the metric is ChromeOS specified. dpad@google.com cros-peripherals@google.com Records the number of times modifier keys are pressed before any modifier remapping takes place on {KeyboardType} keyboards. dpad@google.com cros-peripherals@google.com Records the number of times modifier keys are pressed after modifier remappings takes place on {KeyboardType} keyboards. wmahon@google.com chromeos-tango@google.com Records touchscreen usage time in {Mode}. A usage session is defined as a set of subsequent touches where each touch occurred less than {TimePeriod} after the previous. tsergeant@chromium.org chromeos-apps-foundation-team@google.com The intent picker dialog is shown (either automatically, or though a page action button) when the user navigates to a page whose URL can be handled by an installed app. This metric is recorded when the dialog is closed and records the user action which caused it to close. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records events associated with the intent picker icon in the omnibox. Recorded when the icon is shown or interacted with. Replaced by ChromeOS.Intents.LinkCapturingEvent2 in M106. vpao@google.com chromeos-apps-foundation-team@google.com Records when the link capturing entry point is shown, when a link is successfully captured and results in opening an app, and when the user changes their settings to automatically capture similar links in the future. Replaced by ChromeOS.Intents.LinkCapturingEvent2 in M106. vpao@google.com chromeos-apps-foundation-team@google.com Records when the link capturing entry point is shown for the {AppType} app type, when a link is successfully captured and results in opening a/ an {AppType} app, and when the user changes their settings to automatically capture similar links in the future. vpao@google.com chromeos-apps-foundation-team@google.com Records when the link capturing entry point is shown, when a link is successfully captured and results in opening an app, and when the user changes their settings to automatically capture similar links in the future. Replaces ChromeOS.Intents.LinkCapturingEvent, which incorrectly recorded events when the user changed settings to stay in Chrome. vpao@google.com chromeos-apps-foundation-team@google.com Records when the link capturing entry point is shown for the {AppType} app type, when a link is successfully captured and results in opening a/ an {AppType} app, and when the user changes their settings to automatically capture similar links in the future. Replaces ChromeOS.Intents.LinkCapturingEvent.{AppType}App, which incorrectly recorded events when the user changed settings to stay in Chrome. jamescook@chromium.org lacros-team@google.com Recorded as part of the metrics session data to identify the lacros-chrome browser binary. omorsi@google.com pmarko@google.com Counts the number of times the migration started as well as the number of times it succeeded and failed. It also counts the number of necessary migrations. Necessary migrations are the ones that work on migrating permissions for at least one key. Currently, some migration processes start when there are 0 keys saved in preferences. Removed in M103 omorsi@google.com pmarko@chromium.org Records the time taken to successfully migrate key permissions to chaps. erikchen@chromium.org tvignatti@igalia.com lacros-team@google.com Time to load Lacros binary. The bulk of load time may be spent in mounting Lacros browser binary through squashfs in the component manager. If the user has explicitly specified a path for the Lacros browser binary though, load time will very likely be insignificant. Recorded by ash each time the lacros binary is started. erikchen@chromium.org lacros-team@google.com The release channel of the Chrome OS system on which Lacros is running. May be different than the Lacros browser release channel. Recorded by the lacros binary shortly after startup. andreaorru@chromium.org lacros-team@google.com Time to resume the lacros binary after being prelaunched at login screen, specifically the time between when the process is resumed and the mojo connection is established between ash and lacros. Recorded by ash each time the lacros binary is resumed. erikchen@chromium.org lacros-team@google.com Time to start the lacros binary, specifically the time between when the process is launched and the mojo connection is established between ash and lacros. Recorded by ash each time the lacros binary is started. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records which feature requested a Pack from Language Packs Manager; specifically an entry is recorded each time GetPackState is called. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records which language was requested from Language Packs Manager; specifically an entry is recorded each time GetPackState is called. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records which feature requested a BasePack from Language Packs Manager; specifically an entry is recorded each time InstallBasePack is called. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records the type of error that is received from DLC Service when an installation is requested for Handwriting. No metric is emitted on success, we only record an entry in case of error. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records the type of error that is received from DLC Service when an installation is requested for TTS. No metric is emitted on success, we only record an entry in case of error. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records whether a language pack installation was successful after a language pack installation attempt, broken down by feature ID. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records whether LanguagePackManager is called with a valid locale when updating packs in OOBE. claudiomagni@chromium.org mlcui@google.com dvallet@chromium.org Records whether a language pack uninstallation was successful after a language pack uninstallation attempt. rtinkoff@google.com xiyuan@google.com Reports the time (ms) elapsed between sending of a LivenessChecker ping and receipt of the response. Recorded when LivenessChecker receives a ping response. iby@google.com xiyuan@google.com Records whether the dbus liveness pings successfully go through. True is recorded when the session manager daemon receives the pong back from chrome in time. False is recorded when it times out waiting for the pong. ahassani@chromium.org chromeos-core-services@google.com The number of seconds of uptime since the last time the Chrome OS machine-id was regenerated. This is reported every time the machine-id is regenerated except for the first time since reboot. NB: Data before M90 is incomplete. ahassani@chromium.org chromeos-core-services@google.com Measures whether the MachineIdRegen script acquires the lock. Success / Fail is recorded every time the script is invoked. This is to test if the locking is working as expected. ahassani@chromium.org chromeos-core-services@google.com The reason why the Chrome OS machine-id was regenerated. This is reported when the machine-id is re-generated. NB: Data before M90 is incomplete. leandre@chromium.org cros-status-area-eng@google.com The cause of the scroll event by the user on the message center. Only the first event after the message center opens is recorded. For example, the user opens the message center and scrolls by mouse then by key, only the mouse event is recorded. If the user closes and reopens the message center before the second event, both events are recorded. miersh@google.com pmarko@google.com chromeos-commercial-networking@google.com Records events related to the owner key generation, loading and usage. erikchen@chromium.org cros-hwsec+uma@google.com The result of a platform verification attempt for content protection on Chrome OS. Does not include browser-related failures. pawliczek@chromium.org bmgordon@chromium.org project-bolton@google.com Total CPU time of all children processes started by foomatic_shell in a single failed run. foomatic_shell is used for preparing input data for some printers. pawliczek@chromium.org bmgordon@chromium.org project-bolton@google.com Total CPU time of all children processes started by foomatic_shell in a single successful run. foomatic_shell is used for preparing input data for some printers. ashleydp@google.com gavinwill@chromium.org cros-peripherals@chromium.org Tracks the source element that triggers navigation to Printer settings from Print Management SWA. It attempts to capture the state of Print Management when a user clicks the Printer settings button. Possible states include: no active or historical print jobs and with at least one active or historical print job. cschlosser@chromium.org chromeos-privacyhub@google.com PrivacyHub is a chrome://os-settings page that allows system wide control of privacy settings. The Privacy Hub effort adds additional context to already existing notifications for microphones and cameras in case there is a physical switch on the device to disable one of these sensors. Prior there was only the notification message informing the user about the current state of the system. The notifciations now include a link to a support page where this is explained in more detail. This histogram records which sensor being disabled resulted in the notification button being clicked. zauri@google.com chromeos-privacyhub@google.com Records when the user visits the Privacy Hub page in system settings. Capturing the origin where the user navigated from. zauri@google.com chromeos-privacyhub@google.com Records when the user changes the device-wide {FeatureName} access from the {Source}. This can happen directly from the settings page "Settings">"Security and Privacy">"Privacy hub" or through notifications. michaelcheco@google.com dpad@google.com jimmyxgong@chromium.org zentaro@chromium.org cros-peripherals@google.com Records whether or not RGB keyboard is supported for the current device. Most devices will return RgbKeyboardCapabilityType::None since RGB keyboard is currently only supported on a handful of devices. We still include these samples since it'll be useful for finding real failures, i.e, RgbKeyboardCapabilityType::None is recorded for a device that supports RGB. michaelcheco@google.com dpad@google.com jimmyxgong@chromium.org zentaro@chromium.org cros-peripherals@google.com Records the source of RGB backlight change for a device. mslus@chromium.org emaxx@chromium.org Records every online login authenticated purely with GAIA or with SAML. mslus@chromium.org rsorokin@chromium.org Records how often users are guided through the SAML in-session password change flow, and how often it is completed succesfully. mslus@chromium.org mohammedabdon@chromium.org Records how often password sync token API is called. Tracks results of token verify operation and API errors. mslus@chromium.org mohammedabdon@chromium.org Records SAML provider when SAML login flow is used. mslus@chromium.org emaxx@chromium.org The number of passwords that were scraped during a Chrome OS login via SAML. This is set only when the Chrome Credentials Passing API is not used. Removed in M102 bartfab@chromium.org Whether one of the scraped passwords was successfully verified as the user's password. This is set only when the Chrome Credentials Passing API is not used. enlightened@chromium.org chromeos-security-core@google.com Records the status of the Landlock LSM on the system. Records true if Landlock is enabled, and records false if it is disabled (not configured), not supported by the kernel, or responding with an error. The state of Landlock is determined once per boot and the metric is also recorded only once per boot. enlightened@chromium.org chromeos-hardening@google.com Records the percentage of processes on the system that have the NoNewPrivs bit set in the /proc/self/status file. For more information on no_new_privs, see https://docs.kernel.org/userspace-api/no_new_privs.html No new privs process percentage for the system is sent once per boot and only when a user is logged in. enlightened@chromium.org chromeos-hardening@google.com Records the percentage of processes on the system that are not in the same PID and mount namespace as the init process. Namespace information is collected from /proc/self/ns/pid and /proc/self/ns/mnt symlinks. Non-init-namespace process percentage for the system is sent once per boot and only when a user is logged in. enlightened@chromium.org chromeos-hardening@google.com Records the percentage of processes on the system that are not running as the root user. A process is considered non-root, if its real UID listed in the /proc/self/status file is anything other than 0. Non-root process percentage for the system is sent once per boot and only when a user is logged in. enlightened@chromium.org chromeos-hardening@google.com Records the percentage of processes on the system that are covered by SecComp. A process is considered covered by SecComp if the Seccomp: line in /proc/self/status is anything other than 0. SecComp coverage for the system is sent once per boot and only when a user is logged in. enlightened@chromium.org chromeos-hardening@google.com Records the percentage of processes on the system that are not running as the root user and do not have the CAP_SYS_ADMIN capability. A process is considered non-root, if its real UID listed in the /proc/self/status file is anything other than 0. To determine if a process has CAP_SYS_ADMIN, we parse the CapEff: line in /proc/self/status file and check whether the 21st bit is set. Unprivileged process percentage for the system is sent once per boot and only when a user is logged in. rborzello@google.com cros-enterprise-security@google.com Records whether the cros bootmode for the device was successfully found for devices running the CrOS secagentd daemon. Emits either success or the failure reason. When XDR reporting is enabled it will emit once per daemon lifetime. rborzello@google.com cros-enterprise-security@google.com Records whether the bootparams file was successfully parsed for the UEFI bootmode information for devices running the CrOS secagentd daemon. Emits either success or the failure reason. When XDR reporting is enabled it will emit once per daemon lifetime. rborzello@google.com cros-enterprise-security@google.com Records the initialization status of the {Bpf} BPF used by the CrOS secagentd daemon. Emits either a success or a specific error value. When XDR reporting is enabled it will be recorded once per daemon lifetime. rborzello@google.com cros-enterprise-security@google.com Records whether the processe's information was found in the cache for the CrOS secagentd daemon. Emits either Cache Hit, Cache Miss or Cache Miss but scraped procfs successfully. It will be recorded at most 3 times per XDR event. rborzello@google.com cros-enterprise-security@google.com Records what percent full the cache is for the CrOS secagentd daemon. Emits a value 0-100 representing the percentage. It is recorded every 30 seconds. rborzello@google.com cros-enterprise-security@google.com Records whether the XDR event reporting policy was found enabled for a device. Also provides an on-check enum for baseline. All of the functionality of the CrOS secagentd daemon is gated by this enterprise policy. Note that even though the daemon regularly polls device policy for updates, it will emit exactly one on-check value and at most one enabled value during its lifetime (generally per device per boot). rborzello@google.com cros-enterprise-security@google.com Records whether the Process {EventType} Event was correctly formed for the CrOS secagentd daemon. Emits event was complete or the reason it was not. It is recorded once per XDR event. rborzello@google.com cros-enterprise-security@google.com Records what position the redacted username was found in the list of usernames for the CrOS secagentd daemon. Emits the position up to 5 (but should always be less than or equal to 2). It is recorded everytime a username is found in the commandline which should be very rare. rborzello@google.com cros-enterprise-security@google.com Records the status response of all events sent by the CrOS secagentd daemon. Emits either a success or the failure reason. It is recorded once per XDR event. rborzello@google.com cros-enterprise-security@google.com Records whether the TPM for the device was successfully found for devices running the CrOS secagentd daemon. Emits either success or the failure reason. When XDR reporting is enabled it will be recorded once per daemon lifetime. jorgelo@chromium.org chromeos-security-core@google.com Records when an event representing a deviation from the ChromeOS security posture happens. The list of writable+executable mounts is updated every thirty seconds, and only new anomalous mounts are recorded. This list is cleared every two hours so existing anomalies get recorded again after the two-hour window. Memfd execution attempts are checked every thirty seconds and new attempts are recorded. memfd_create events are only recorded once per boot. Prior to M111 memfd_create events were recorded up to ten times per boot. jorgelo@chromium.org chromeos-security-core@google.com Records the result (boolean success or failure) of attempting to report a Chrome OS system as anomalous via the crash reporting service. Reporting is only attempted if one or more anomalies are detected (see the previous histogram's description for the types of anomalies considered), *and* once per boot, even if reporting fails. So this histogram will be recorded at most once per boot, and only if a system is detected as anomalous (i.e. presents any of the tracked anomalies.) dpad@google.com cros-peripherals@google.com Records the configured modifier remapping set on {KeyboardType} keyboard for all modifiers as a hash. dpad@google.com cros-peripherals@google.com Records the number of modifier keys reset everytime the modifier remappings are reset to default on the {KeyboardType} keyboard, if the number is not zero. dpad@google.com cros-peripherals@google.com Records the number of non default modifier key remappings when the {KeyboardType} keyboard is first initialized. dpad@google.com cros-peripherals@google.com Records the configured modifier remapping for the {Modifier} key when the {KeyboardType} keyboard is updated. dpad@google.com cros-peripherals@google.com Records the configured modifier remapping for the {Modifier} key when the {KeyboardType} keyboard is first initialized. michaelcheco@google.com cros-peripherals@google.com Records the configured modifier remapping for the {Key} key when the {KeyboardType} keyboard is updated. michaelcheco@google.com cros-peripherals@google.com Records the configured modifier remapping for the {Key} key when the {KeyboardType} keyboard is first initialized. dpad@google.com cros-peripherals@google.com Records the value of the {KeyboardSetting} setting when the {KeyboardType} keyboard is updated. dpad@google.com cros-peripherals@google.com Records the value of the {KeyboardSetting} setting when the {KeyboardType} keyboard is first initialized. michaelcheco@google.com cros-peripherals@google.com Records the value of the {Key} setting for the {KeyboardType} keyboard when the setting is {State}. michaelcheco@google.com cros-peripherals@google.com Records the value of the simulate right-click setting when the {TouchpadType} touchpad is updated. michaelcheco@google.com cros-peripherals@google.com Records the value of the simulate right-click setting when the {TouchpadType} touchpad is first initialized. dpad@google.com cros-peripherals@google.com Records the value of the {TouchpadSetting} settings when the {TouchpadType} touchpad settings are updated. dpad@google.com cros-peripherals@google.com Records the value of the {TouchpadSetting} settings when the {TouchpadType} touchpad is first initialized. dpad@google.com cros-peripherals@google.com Records the value {Difference} when {TouchpadSetting} settings on {TouchpadType} touchpad are updated. dpad@google.com cros-peripherals@google.com Records the value of the {TouchpadSpeedSettings} setting when the {TouchpadType} touchpad settings are updated. dpad@google.com cros-peripherals@google.com Records the value of the {TouchpadSpeedSettings} setting when the {TouchpadType} touchpad is first initialized. dpad@google.com cros-peripherals@google.com Records if the {DeviceType} settings are set successfully. Set settings will fail if the id or the settings object is invalid. dpad@google.com cros-peripherals@google.com Records the number of times settings were updated for the first ever connected {DeviceType} within the given time period of {TimePeriod}. dpad@google.com cros-peripherals@google.com Records the number of times {DeviceType} settings were updated when they were initially taken from the user's defaults within the time period of {TimePeriod}. dpad@google.com cros-peripherals@google.com Records the number of times {DeviceType} settings were updated when the settings were taken from synced settings within the time period of {TimePeriod}. dpad@google.com cros-peripherals@google.com Records the value of the Button.CustomizableButton property when the {Peripheral} device button remapping name changes. dpad@google.com cros-peripherals@google.com Records the value of the Button.Vkey property when the {Peripheral} device button remapping name changes. To lookup the Vkey value from UMA, convert the int value to a hex, and then lookup that hex value in ui/events/keycodes/keyboard_codes_posix.h. dpad@google.com cros-peripherals@google.com Records the value of the button_remapping StaticShortcutAction property when the {Peripheral} device button_remapping is first initialized. dpad@google.com cros-peripherals@google.com Records the value of the {PeripheralSetting} settings when the {Peripheral} device settings are updated. dpad@google.com cros-peripherals@google.com Records the value of the {PeripheralSetting} settings when the {Peripheral} device is first initialized. dpad@google.com cros-peripherals@google.com Records the value of the {SensitivityType} setting when the {Peripheral} device settings are updated. The value ranges from 1 to 5. dpad@google.com cros-peripherals@google.com Records the value of the {SensitivityType} setting when the {Peripheral} device is is first initialized. The value ranges from 1 to 5. dpad@google.com cros-peripherals@google.com Records the value {Difference} when {SensitivityType} setting on {Peripheral} device is updated. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records number of {AppType} apps found for a given intent in the Sharesheet when the sharesheet is invoked. Has 100 exponential buckets. (The original histogram had 1000 linear buckets). Warning: this histogram was expired from M95 to M96; data may be missing. vpao@google.com chromeos-apps-foundation-team@google.com Records the form factor when the Copy To Clipboard option is selected from the sharesheet. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records the number of files a user is trying to share from the Sharesheet when the sharesheet is invoked. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records the form factor when the Sharesheet is invoked. tsergeant@chromium.org chromeos-apps-foundation-team@google.com If the value is true, the data being shared from the Sharesheet is a folder from Drive. Recorded when the sharesheet is invoked. tsergeant@chromium.org chromeos-apps-foundation-team@google.com If the value is true, the image preview was pressed during the current invocation. Recorded when the sharesheet closes. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records the source from which the Sharesheet is invoked. Warning: this histogram was expired from M95 to M96; data may be missing. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records each action found for a given intent when the Sharesheet is invoked. Warning: this histogram was expired from M95 to M96; data may be missing. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records user action on sharesheet invocations. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records the mime type of the content being copied at the {Location} point in the Sharesheet flow. This histogram could record multiple times in a single share in the event that the user shares data of mime types at once. However, a single share will not record the same mime type twice. E.g. sharing 2 images in one share will record the image mimetype once. mutexlox@google.com palaksh@google.com kendraketsui@google.com cros-telemetry@google.com Records the severity of crashes reported by the ChromeOS crash-reporter, broken down by the product type that reported the crash. This is recorded from the CrashCollector::FinishCrash() method - refer to it for more details. ctshao@google.com bgeffon@google.com An enum value indicates whether or not swap_management started swap successfully. The value is absl error code. ctshao@google.com bgeffon@google.com An enum value indicates whether or not swap_management stopped swap successfully. The value is absl error code. amehfooz@chromium.org cros-status-area@google.com Tracks the animation smoothness for the collapse / expand animation of the system tray. amehfooz@chromium.org cros-status-area@google.com Tracks the number of blocked notifiers in the system tray after the user blocks one or multiple notifiers. Note that this metric records the number of blocked notifiers *after* the update. amehfooz@chromium.org cros-status-area@google.com Tracks the number of blocked notifiers in the system tray when it is opened. amehfooz@chromium.org cros-status-area@google.com Records the first interaction the user has with the system tray, which can be a click/tap on the quick settings or message center bubble. Note that this interaction could be at any time after the user opens the tray (e.g. 30 seconds later before the first click). amehfooz@chromium.org cros-status-area@google.com An enum value how system tray bubble is interacted e.g. by tap (touch screen), or click (mouse, trackpad, etc.) Reported every time the region inside system tray bubble is tapped or clicked. amehfooz@chromium.org cros-status-area@google.com If the value is true, SystemTray is expanded when it's opened. Otherwise, it's closed when it's opened. khorimoto@chromium.org tjohnsonkanu@chromium.org chadduffin@chromium.org cros-connectivity@google.com This metric will record each action taken as a result of a user clicking a Network from Network list within system tray. Metric emitted each time a user clicks on a network list row. khorimoto@chromium.org tjohnsonkanu@chromium.org chadduffin@chromium.org cros-connectivity@google.com Records when different sections within the detailed network view in the system tray shown. This metric is emitted each time a user opens the system tray and each time a different network section is newly shown. khorimoto@chromium.org tjohnsonkanu@chromium.org chadduffin@chromium.org cros-connectivity@google.com Records the new value of the WiFi/Mobile toggle button in system tray. Metric emitted each time a user clicks on the enable/disable WiFi or Mobile toggle. amehfooz@chromium.org cros-status-area@google.com Records the number of notifications that are removed in a single clear all action by the user. amehfooz@chromium.org cros-status-area@google.com The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in the shelf status area whenever a pod appears/disappears. This histogram is only logged when the device is not in tablet mode, otherwise ChromeOS.SystemTray.Tablet.ShelfPodCount is logged. amehfooz@chromium.org cros-status-area@google.com The number of status area item pods (e.g. IME, Palette, Dictation, etc.) in the shelf status area whenever a pod appears/disappears. This histogram is only logged when the device is in tablet mode, otherwise ChromeOS.SystemTray.ShelfPodCount is logged. tengs@chromium.org gzadina@google.com The amount of time a user took from clicking on the button in status area, to clicking on an item in the system tray bubble. (Obsolete M90 onwards). amehfooz@chromium.org cros-status-area@google.com The amount of time a user took after opening the system tray bubble, to clicking on an item in the system tray bubble. amehfooz@chromium.org cros-status-area@google.com An enum value how system tray bubble is expanded or collapsed. It can be toggled by the button and touch gesture. pmalani@chromium.org chromeos-power@google.com This value represents the speed of the USB Type-C cable which is connected to a device. It is recorded every time a new peripheral is connected. pmalani@chromium.org chromeos-usb@google.com This value represents DisplayPort (DP) alternate mode entry success (or failure) for USB Type-C peripherals that support this alternate mode. This metric gets recorded by the Chrome OS Type-C system daemon (typecd) when a peripheral that supports DP alternate mode is connected to the systems that support this metric. wonchung@google.com chromeos-usb@google.com This value represents the location and order of a USB Type-C peripheral (partner) which is connected to a device. It is recorded every time a new peripheral is connected. pmalani@chromium.org chromeos-power@google.com This value represents the type of a USB Type-C peripheral (the Partner) which is connected to a device. It is recorded every time a new peripheral is connected. wonchung@google.com chromeos-usb@google.com This value represents the location and order of a USB Type-C power source which is connected to a device. It is recorded every time a new power source is connected. pmalani@chromium.org chromeos-power@google.com This value represents events where a USB Type-C peripheral couldn't be configured correctly, or experienced some other unexpected behaviour. It is recorded every time a new peripheral is connected. jorgelo@chromium.org tnagel@chromium.org The number of files with URL extended attributes found in the users' home directories. This is emitted once per boot. See crbug.com/919486 and crbug.com/939386 for more details. allenwebb@chromium.org jorgelo@chromium.org mnissler@chromium.org Timing and number of USB devices attached. wonchung@google.com allenwebb@chromium.org chromeos-usb@google.com Timing and number of external USB devices attached. This is emitted each time an external device is attached via USB and when user logs in with an external device attached. wonchung@google.com chromeos-usb@google.com USB device class per {USBPortType}. This is emitted each time an external device is attached via USB and when user logs in with an external device attached. wonchung@google.com chromeos-usb@google.com USB device speed per {USBPortType}. This is emitted each time an external device is attached via USB and when user logs in with an external device attached. bmalcolm@chromium.org cros-client-wa@google.com This value is reported at the start of a user session, and is a 32-bit value that reports the primary user account type and the device type (umanaged user on managed device, K12 user on an education device, etc.). The upper 16-bits represent the device type (found at http://shortn/_3iFWcdjy0P), and the lower 16-bits represent the user type (found at http://shortn/_uK3ZM4pC0a). So a nonprofit user (0x03) on an enterprise device (0x02) would be 0x00020003 or 131075. tsergeant@chromium.org chromeos-apps-foundation-team@google.com Records the overall final state of a WebAPK {InstallType} operation on ChromeOS. A WebAPK is generated and installed when a PWA which supports Web Share Target is installed in the browser, and updated when the PWA's manifest updates. jorgelo@chromium.org chromeos-security-core@google.com Records the number of writable+executable mounts on the system. The count itself is updated every 30 seconds, but this metric is reported every two hours of runtime. This metric is reported regardless of whether users are logged in or not. This metric is only reported on Chrome OS. erikchen@chromium.org bgeffon@chromium.org chromeos-memory@google.com This is a multi-dimensional metric that includes information from two existing metrics: ChromeOS.Zram.OrigDataSizeMB and ChromeOS.CWP.PSIMemPressure.Some. There are exactly 300 buckets. To interpret the bucket label, divide the bucket by 20 to get OrigDataSizeMB. The result is memory usage in gigabytes. The ranges are [0, 1), [1, 2), ..., [14, infinity). Modulus the bucket by 20 to get PSIMemPressure.Some (ranges of 0.05, 20 buckets). The metric is logged every 10 seconds. ctshao@google.com bgeffon@chromium.org chromeos-memory@google.com Records {CountMetric}. Recorded every 10s from boot to shutdown. ctshao@google.com raging@google.com bgeffon@chromium.org chromeos-memory@google.com Records the {HugePageActivityMetric} in a period of time. Recorded every 10s from boot to shutdown. Period is the time between recordings (10s). ctshao@google.com bgeffon@chromium.org chromeos-memory@google.com Records {PctMetric}. Recorded every 10s from boot to shutdown. ctshao@google.com bgeffon@chromium.org chromeos-memory@google.com Records {SizeMetric}. Recorded every 10s from boot to shutdown.