From 6182e368aa64c40138802d440cb574d9ce7c9e68 Mon Sep 17 00:00:00 2001 From: Arkadiusz Komarzewski Date: Thu, 26 Sep 2024 17:09:55 +0200 Subject: [PATCH 1/2] DENG-2407 Update Mozilla Accounts docs --- .spelling | 1 + src/datasets/fxa.md | 12 +++++++++++- 2 files changed, 12 insertions(+), 1 deletion(-) diff --git a/.spelling b/.spelling index a6fba7cb6..cad74cb70 100644 --- a/.spelling +++ b/.spelling @@ -144,6 +144,7 @@ fivetran-discussion Fivetran_Prod footgun frac +frontend funnelcake GCP GCP-GCR diff --git a/src/datasets/fxa.md b/src/datasets/fxa.md index 13913805d..fc67c4442 100644 --- a/src/datasets/fxa.md +++ b/src/datasets/fxa.md @@ -45,7 +45,17 @@ The [FxA oauth server](https://github.com/mozilla/fxa/pull/3176) logs metrics ev ## Metrics Taxonomies -In 2023 we integrated Glean with Mozilla Accounts and Event Metrics are now available for the [server-side](https://dictionary.telemetry.mozilla.org/apps/accounts_backend) and [client-side](https://dictionary.telemetry.mozilla.org/apps/accounts_frontend). +### Glean + +In 2023, we integrated Glean with Mozilla Accounts and Event Metrics are now available for both the server-side and client-side. + +To explore available metrics, visit [Glean Dictionary](https://dictionary.telemetry.mozilla.org/) and browse the [`accounts_backend`](https://dictionary.telemetry.mozilla.org/apps/accounts_backend) and [`accounts_frontend`](https://dictionary.telemetry.mozilla.org/apps/accounts_frontend) applications. + +All events are sent in `events` ping. The most effective way to query them is to use the `events_stream` tables in BigQuery: [`accounts_frontend.events_stream`]() and [`accounts_backend.events_stream`](). `events_stream` tables are accessible in Looker. Because they have extra properties packaged as a JSON structure, when these are needed it is best to use the `events unnested` explores. + +The Accounts frontend is instrumented with [automatic Glean website events](https://mozilla.github.io/glean.js/automatic_instrumentation/page_load_events/). Data collected this way can be explored on the [Website Sessions dashboard](https://mozilla.cloud.looker.com/dashboards/websites::website_sessions?App+ID=accounts%5E_frontend&Submission+Date=7+day&Country+Name=&External+Referrer=&App+Channel=&UA+-+Browser=&Traffic+Source=) in Looker. To dig deeper you can write a query to analyze properties of these events: [`element_click`](https://sql.telemetry.mozilla.org/queries/102469/source) and [`page_load`](https://sql.telemetry.mozilla.org/queries/102470/source). + +### Legacy There are two additional legacy event types described below: From 597ab089ab8dd116d86497ba50dc925836b76fcd Mon Sep 17 00:00:00 2001 From: Arkadiusz Komarzewski Date: Thu, 26 Sep 2024 20:52:52 +0200 Subject: [PATCH 2/2] Correct event_counts explore name --- src/datasets/fxa.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/datasets/fxa.md b/src/datasets/fxa.md index fc67c4442..e9cb67c33 100644 --- a/src/datasets/fxa.md +++ b/src/datasets/fxa.md @@ -51,7 +51,7 @@ In 2023, we integrated Glean with Mozilla Accounts and Event Metrics are now ava To explore available metrics, visit [Glean Dictionary](https://dictionary.telemetry.mozilla.org/) and browse the [`accounts_backend`](https://dictionary.telemetry.mozilla.org/apps/accounts_backend) and [`accounts_frontend`](https://dictionary.telemetry.mozilla.org/apps/accounts_frontend) applications. -All events are sent in `events` ping. The most effective way to query them is to use the `events_stream` tables in BigQuery: [`accounts_frontend.events_stream`]() and [`accounts_backend.events_stream`](). `events_stream` tables are accessible in Looker. Because they have extra properties packaged as a JSON structure, when these are needed it is best to use the `events unnested` explores. +All events are sent in `events` ping. The most effective way to query them is to use the `events_stream` tables in BigQuery: [`accounts_frontend.events_stream`]() and [`accounts_backend.events_stream`](). They are accessible in Looker via `Events Stream Table` explores. Because they have extra properties packaged as a JSON structure, when these are needed it is best to use the `Event Counts` explores. The Accounts frontend is instrumented with [automatic Glean website events](https://mozilla.github.io/glean.js/automatic_instrumentation/page_load_events/). Data collected this way can be explored on the [Website Sessions dashboard](https://mozilla.cloud.looker.com/dashboards/websites::website_sessions?App+ID=accounts%5E_frontend&Submission+Date=7+day&Country+Name=&External+Referrer=&App+Channel=&UA+-+Browser=&Traffic+Source=) in Looker. To dig deeper you can write a query to analyze properties of these events: [`element_click`](https://sql.telemetry.mozilla.org/queries/102469/source) and [`page_load`](https://sql.telemetry.mozilla.org/queries/102470/source).