That's fantastic :chutten, thank you! In terms of _where_ to collect it, our primary use case is cross referencing metrics collected in [toolkit/components/translations/metrics.yaml](https://searchfox.org/mozilla-central/source/toolkit/components/translations/metrics.yaml) with CPU info based on the unique user ID. Right now, that looks like this: ```sql FROM firefox_desktop.events_stream AS fes LEFT JOIN telemetry.clients_daily AS cls ON fes.legacy_telemetry_client_id = cls.client_id AND DATE(fes.submission_timestamp) = cls.submission_date ``` Where I am using values such as `cls.cpu_model`, `cls.cpu_cores`, `cls.cpu_speed_mhz` etc. All of these are null on Android. My hope is to achieve something like this: ```sql FROM firefox_desktop.events_stream AS fes LEFT JOIN {NEW_GLEAN_METRICS} AS cls ON fes.client_id = cls.client_id AND DATE(fes.submission_timestamp) = cls.submission_date ``` Where I can cross reference our Translations event data with CPU info on both platforms.
Bug 1945253 Comment 3 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
That's fantastic :chutten, thank you! In terms of _where_ to collect it, our primary use case is cross referencing metrics collected in [toolkit/components/translations/metrics.yaml](https://searchfox.org/mozilla-central/source/toolkit/components/translations/metrics.yaml) with CPU info based on the unique `client_id` value. Right now, that looks like this: ```sql FROM firefox_desktop.events_stream AS fes LEFT JOIN telemetry.clients_daily AS cls ON fes.legacy_telemetry_client_id = cls.client_id AND DATE(fes.submission_timestamp) = cls.submission_date ``` Where I am using values such as `cls.cpu_model`, `cls.cpu_cores`, `cls.cpu_speed_mhz` etc. All of these are null on Android. My hope is to achieve something like this: ```sql FROM firefox_desktop.events_stream AS fes LEFT JOIN {NEW_GLEAN_METRICS} AS cls ON fes.client_id = cls.client_id AND DATE(fes.submission_timestamp) = cls.submission_date ``` Where I can cross reference our Translations event data with CPU info on both platforms.
That's fantastic :chutten, thank you! In terms of _where_ to collect it, our primary use case is cross referencing metrics collected in [toolkit/components/translations/metrics.yaml](https://searchfox.org/mozilla-central/source/toolkit/components/translations/metrics.yaml) with CPU info based on the unique `client_id` value. Right now, that looks like this: ```sql FROM firefox_desktop.events_stream AS fes LEFT JOIN telemetry.clients_daily AS cls ON fes.legacy_telemetry_client_id = cls.client_id AND DATE(fes.submission_timestamp) = cls.submission_date ``` Where I am using values such as `cls.cpu_model`, `cls.cpu_cores`, `cls.cpu_speed_mhz` etc. All of these are null on Android. My hope is to achieve something like this: ```sql FROM firefox_desktop.events_stream AS fes LEFT JOIN {NEW_GLEAN_METRICS} AS ngm ON fes.client_id = ngm.client_id AND DATE(fes.submission_timestamp) = ngm.submission_date ``` Where I can cross reference our Translations event data with CPU info on both platforms.