jackshira@chromium.org chromeos-cross-device-eng@google.com none profile

Metrics for the ChromeOS Fast Pair implementation.

The user is shown a notification which can start the pairing process.

The pairing protocol of the discovered device.

The Fast Pair spec version the device implements.

The model ID of the discovered device.

The inquiry RSSI of the discovered device, recorded at the time of metrics emission, with a range of -128 to 127. If inquiry RSSI is unknown, we report -129.

The inquiry TxPower of the discovered device, recorded at the time of metrics emission, with a range of -128 to 127. If inquiry TxPower is unknown, we report -129.

The starting of the pairing process.

The pairing protocol being started.

The Fast Pair spec version the device implements.

The model ID of the device being paired.

The inquiry RSSI of the pairing device, recorded at the time of metrics emission, with a range of -128 to 127. If inquiry RSSI is unknown, we report -129.

The inquiry TxPower of the pairing device, recorded at the time of metrics emission, with a range of -128 to 127. If inquiry TxPower is unknown, we report -129.

The end of the pairing process.

The pairing protocol being started.

The Fast Pair spec version the device implements.

The model ID of the device being paired.

The inquiry RSSI of the paired device, recorded at the time of metrics emission, with a range of -128 to 127. If inquiry RSSI is unknown, we report -129.

The inquiry TxPower of the paired device, recorded at the time of metrics emission, with a range of -128 to 127. If inquiry TxPower is unknown, we report -129.

The pairing process failed for the provided reason.

The pairing protocol being started.

The Fast Pair spec version the device implements.

The pairing failure reason.

The model ID of the device being paired.

charleszhao@chromium.org tby@chromium.org per-project profile

Project for recording CrOSActions.

Records whenever a file is opened in the File App on ChromeOS.

The absolute path of the file.

The type of file open, defined in FileTaskObserver::OpenType.

Sequence of this action across all CrOSActionEvent.

Time in milliseconds since last CrOSActionLogging.

Records information about the launch of an item from ChromeOS launcher.

The search query associated with this launch.

Which type of search provider the launched result was created by.

The ID of the launched result result. For example, the app ID for app results, or the URL for omnibox results.

Sequence of this action across all CrOSActionEvent.

Time in milliseconds since last CrOSActionLogging.

Records when a setting is changed; only records quick settings for now.

Value of the setting after the change.

Value of the setting before the change.

Sequence of this action across all CrOSActionEvent.

The setting id (in ash::ml::UserSettingsEvent::Event::SettingId) that represents the type of the changed setting.

Enum that represents where the settings event originated from (in ash::ml::UserSettingsEvent::Event::SettingType).

Time in milliseconds since last CrOSActionLogging.

Records a tab activity of navigating to a new url.

The types of transition between pages. See more on ui::PageTransition.

Sequence of this action across all CrOSActionEvent.

Time in milliseconds since last CrOSActionLogging.

The URL of the current event.

The visibility of this url, see more on content::Visibility.

Records a tab activity of opening a new url with ctrl+click.

Sequence of this action across all CrOSActionEvent.

Time in milliseconds since last CrOSActionLogging.

The URL of the current event.

The URL that is opened from the current url.

Enum that indicates where the new tab is opened, see more on WindowOpenDisposition.

Records a tab activity of reactivating an existing tab.

Sequence of this action across all CrOSActionEvent.

Time in milliseconds since last CrOSActionLogging.

The URL of the current event.

tby@chromium.org per-project profile

See event summary.

Records information about the launch of an item (such as an app or a file) from the ChromeOS launcher. One event is recorded for every launch originating from any launcher UI component, and this is the only circumstance that records events.

App ID of the most-recently-opened app when this launch occured. This can be an app ID of a Chrome app, Arc++ app, or PWA.

The most-recently-visited domain when this launch ocurred.

The hour of launch. This is the user's local time rounded to the nearest hour, 0 to 23 inclusive.

Which type of search provider the launched result was created by. This comes from the AppListSearchResultType enum.

The relevance score of the launched result. This is a double multiplied by 1000 and cast to an int64. Results that don't have a score report 0.

The search query associated with this launch. Before hashing, the query is the empty string if there was no search query.

String length of the search query associated with this launch. If there was no query, this is zero.

The target item of this launch, eg. an app ID, filepath, or omnibox URL.

pdyson@chromium.org per-project device

Project for recording events to monitor the creation of Neutrino Devices.

Records the client id being changed to a new value. This does not include when the client id is cleared (see ClientIdCleared below).

The client id before it is changed.

The client id after it is changed.

The time since installation. Recorded as the integer floor of the log base 2 of the time duration measured in days. Negative values indicate periods shorter than one day.

The time since metrics enabled. Recorded as the integer floor of the log base 2 of the time duration measured in days. Negative values indicate periods shorter than one day.

An integer indicating the location in the code. This can be used to perform a partial stack trace to see which code was executed in the lead up to the client id being changed.

The number of days since the key was rotated.

Records when the client id is cleared.

The client id before it is changed.

The time since installation. Recorded as the integer floor of the log base 2 of the time duration measured in days. Negative values indicate periods shorter than one day.

The time since metrics enabled. Recorded as the integer floor of the log base 2 of the time duration measured in days. Negative values indicate periods shorter than one day.

Records the enrollment status, either managed or unmanaged.

The client id.

An integer indicating the location in the code. This can be used to perform a partial stack trace to see which code was executed in the lead up to the client id being changed.

Whether the device is managed. 1: Managed, 0: Unmanaged.

Whether the metrics reporting policy is managed. 1: Managed, 0: Unmanaged.

Records that execution reached a particular point in the code.

The client id.

An integer indicating the location in the code. This can be used to perform a partial stack trace to see which code was executed in the lead up to the client id being changed.

jongahn@chromium.org tby@chromium.org per-project device

Structured Metrics is a logging framework for events. This project is used for monitoring the framework itself.

Records metadata about initialization of Structured Metrics and will be recorded immediately after initialization is successful. Will be sent once per initialization during browser process initialization.

The platform for which the client is initialized on. 0: Uninitialized, 1: ASH_CHROME, 2: LACROS_CHROME.

jongahn@chromium.org per-project device

120

Project used to record a sequence of events that are related to each other.

Recorded whenever a new app is installed on Chrome OS.

Key that identifies an app.

The type of app that was installed (ie ARC, native, Crostini, etc.).

Origin from which the app was installed (ie launcher, playstore).

Reason for which the app was installed.

Recorded whenever a new app is launched on Chrome OS.

Key that identifies an app.

The type of app that was installed (ie ARC, native, Crostini, etc.).

From where the app was launched from (ie launcher, shelf).

Recorded whenever an app is uninstalled on Chrome OS.

Key that identifies an app.

The type of app that was installed (ie ARC, native, Crostini, etc.).

From where the app was uninstalled.

Recorded when a change in an app state has been detected.

Key that identifies an app.

Denotes a change in an app state. 0 - INACTIVE, 1 - ACTIVE, 2 - CLOSED.

Event collected if the launcher is opened. This is recorded when a zero- state query is initiated.

Event collected if a result iis opened in the launcher.

Score that represents how close the initial query was to the app result selected. A score of 1.0 represents an exact match.

App ID that identifies an app on the client. This will only be recorded if the user has consented into app-sync.

Name of the app that was launched. Names are UTF-16 string encoding.

Enum representing the category of app the result is. This enum should map to ash::SearchResultType.

Event recorded when the PWA Install Icon is clicked.

Boolean if the IPH (In-product help) was shown when the icon was clicked. 1 if the IPH was shown 0 otherwise.

Event recorded when the PWA confirmation dialog is shown.

Identifier of the app for which the bubble view is shown.

Event capturing the result of the app install dialog shown in the browser. This event will be captured if the install is accepted or cancelled. If a user switches to a different tab, this will result in a "cancel".

1 if accepted. 0 if cancelled. The status is considered cancelled if the bubble dialog is closed before an "Accept" status has been detected.

Identifier of the app for which the bubble view is shown.

Event recorded when a PWA is installed from the browser menu.

Identifier of the app that is being installed.

Event recorded when a web app or PWA is installed by creating a shortcut.

Identifier of the app that is being installed.

An event to signify a user is using the system.

An event to signify a user explicitly logged out of the system.

An event to signify the system has gone to sleep.

The reason the system was suspended, maps to the SuspendImminent::Reason.

Test event used for unit tests to ensure that the code-gen for the event sequence project is working properly.

Test metric1

Test event for events without metrics.

tby@chromium.org per-project profile

Project for unit testing, do not use.