RMST-302: Create a derived dataset for Remote Settings uptake telemetry#9085
Merged
BenWu merged 14 commits intomozilla:mainfrom Mar 31, 2026
Merged
RMST-302: Create a derived dataset for Remote Settings uptake telemetry#9085BenWu merged 14 commits intomozilla:mainfrom
BenWu merged 14 commits intomozilla:mainfrom
Conversation
chutten
previously requested changes
Mar 26, 2026
alexcottner
reviewed
Mar 26, 2026
Contributor
Author
|
For reference, this is the kind of queries that we'll run down the line in telescope (source) SELECT
PARSE_TIMESTAMP('%s', CAST(UNIX_SECONDS(submission_timestamp) - MOD(UNIX_SECONDS(submission_timestamp), 600) AS STRING)) AS period,
CASE WHEN extra_status = 'success' THEN 'success' ELSE 'error' END AS status,
COUNT(DISTINCT client_id) AS n_client_id,
COUNT(DISTINCT IF(normalized_channel IN ('release', 'esr'), client_id, NULL)) * 100 AS n_client_id_release,
COUNT(DISTINCT IF(normalized_channel = 'nightly', client_id, NULL)) AS n_client_id_nightly,
COUNT(DISTINCT IF(normalized_channel NOT IN ('release', 'esr', 'nightly'), client_id, NULL)) AS n_client_id_other
FROM
`moz-fx-data-shared-prod.monitoring_derived.remote_settings_uptake_live_v1`
WHERE submission_timestamp > TIMESTAMP_SUB(CURRENT_TIMESTAMP(), INTERVAL 3 HOUR)
AND extra_status NOT IN ('up_to_date', 'network_error', 'offline_error', 'shutdown_error')
GROUP BY period, status |
chutten
reviewed
Mar 26, 2026
Contributor
chutten
left a comment
There was a problem hiding this comment.
Overall, I like it. I have some outstanding questions for folks more expert than me, so I'll reach out on Slack#data-help for their attention.
BenWu
reviewed
Mar 26, 2026
…_uptake_live_v1/metadata.yaml Co-authored-by: Chris H-C <chutten@users.noreply.github.com>
…_uptake_live_v1/view.sql Co-authored-by: Ben Wu <12437227+BenWu@users.noreply.github.com>
…_uptake_live_v1/view.sql Co-authored-by: Chris H-C <chutten@users.noreply.github.com>
BenWu
reviewed
Mar 27, 2026
Co-authored-by: Ben Wu <12437227+BenWu@users.noreply.github.com>
BenWu
approved these changes
Mar 31, 2026
Contributor
BenWu
left a comment
There was a problem hiding this comment.
LGTM, just trying to get it through CI
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
We are migrating our client uptake telemetry away from the legacy stack.
We want
telescopeto be able to read uptake telemetry like it did insql/moz-fx-data-shared-prod/telemetry_derived/events_live/metadata.yamlAnd ideally we would like to query live data in Grafana to be able to correlate the data publication in our servers with client behaviour.
According to my current understanding and navigation within the data eng constellation, this PR would be the way to go.
Related Tickets & Documents
Reviewer, please follow this checklist