Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion src/cookbooks/crash_pings.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,5 +33,5 @@ GROUP BY normalized_os,
[`STMO#67927`](https://sql.telemetry.mozilla.org/queries/67927/)

These are just initial examples. You can query across all the fields in
a telemetry crash ping, which provides useful information about the crashes themselves. You can view a summary of the available fields in the STMO schema browser, referring to [the documentation on the Firefox crash ping](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/crash-ping.html)
a telemetry crash ping, which provides useful information about the crashes themselves. You can view a summary of the available fields in the STMO schema browser, referring to [the documentation on the Firefox crash ping](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/obsolete/crash-ping.html)
for more information where necessary.
4 changes: 2 additions & 2 deletions src/datasets/obsolete/crash_summary/reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ group by gfx_compositor
## Sampling

`CrashSummary` contains one record for every
[crash ping](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/crash-ping.html)
[crash ping](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/obsolete/crash-ping.html)
submitted by Firefox.

## Scheduling
Expand Down Expand Up @@ -68,6 +68,6 @@ root
```

For more detail on where these fields come from in the
[raw data](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/crash-ping.html),
[raw data](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/obsolete/crash-ping.html),
please look at the case classes
[in the `CrashSummaryView` code](https://github.com/mozilla/telemetry-batch-view/blob/master/GRAVEYARD.md#crash-summary).
2 changes: 1 addition & 1 deletion src/datasets/obsolete/sync_summary/intro.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
_Note: some of the information in this chapter is a duplication of the info found on [this](https://wiki.mozilla.org/CloudServices/Sync/ReDash) wiki page. You can also find more detailed information about the data contained in the sync ping [here](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/sync-ping.html)_
_Note: some of the information in this chapter is a duplication of the info found on [this](https://wiki.mozilla.org/CloudServices/Sync/ReDash) wiki page. You can also find more detailed information about the data contained in the sync ping [here](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/obsolete/sync-ping.html)_

`sync_summary` and `sync_flat_summary` are the primary datasets that track the health of sync. `sync_flat_summary` is derived from `sync_summary` by unpacking/exploding the `engines` field of the latter, so they ultimately contain the same data (see below).

Expand Down
2 changes: 1 addition & 1 deletion src/datasets/obsolete/sync_summary/reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Starting with Fenix, however, sync telemetry will start to be sent through [glea

## What's an engine?

Firefox syncs many different types of browser data and (generally speaking) each one of these data types are synced by their own engine. When the app triggers a "sync" each engine makes their own determination of what needs to be synced (if anything). Many syncs can happen in a day (dozens or more on desktop, usually less on mobile). Telemetry about each sync is logged, and each [sync ping](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/sync-ping.html) (sent once a day, and whenever the user logs in or out of sync) contains information about multiple syncs. The scala code responsible for creating the `sync_summary` dataset unpacks each sync ping into one row per sync. The resulting `engines` field is an array of "engine records": data about how each engine performed during that sync. `sync_flat_summary` further unpacking/exploding the `engines` field and creates a dataset that is one row per engine record.
Firefox syncs many different types of browser data and (generally speaking) each one of these data types are synced by their own engine. When the app triggers a "sync" each engine makes their own determination of what needs to be synced (if anything). Many syncs can happen in a day (dozens or more on desktop, usually less on mobile). Telemetry about each sync is logged, and each [sync ping](https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/obsolete/sync-ping.html) (sent once a day, and whenever the user logs in or out of sync) contains information about multiple syncs. The scala code responsible for creating the `sync_summary` dataset unpacks each sync ping into one row per sync. The resulting `engines` field is an array of "engine records": data about how each engine performed during that sync. `sync_flat_summary` further unpacking/exploding the `engines` field and creates a dataset that is one row per engine record.

Existing engines (`engine_name` in `sync_flat_summary`) are listed below with brief descriptions in cases where their name isn't transparent.

Expand Down
4 changes: 2 additions & 2 deletions src/datasets/pings.md
Original file line number Diff line number Diff line change
Expand Up @@ -176,13 +176,13 @@ To augment our data collection, see [Collecting New Data][addprobe] and the
[event_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/event-ping.html
[update_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/update-ping.html
[new_profile_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/new-profile-ping.html
[crash_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/crash-ping.html
[crash_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/obsolete/crash-ping.html
[deletion_request_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/data/deletion-request-ping.html
[optout_ping]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/obsolete/optout-ping.html
[crash_annotations]: https://searchfox.org/mozilla-central/source/toolkit/crashreporter/CrashAnnotations.yaml
[common_ping_data]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/common-ping.html
[main_reasons]: https://sql.telemetry.mozilla.org/queries/3434
[stack_traces]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/data/crash-ping.html#stack-traces
[stack_traces]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/obsolete/crash-ping.html#stack-traces
[preferences]: https://firefox-source-docs.mozilla.org/toolkit/components/telemetry/telemetry/internals/preferences.html
[stmo]: https://sql.telemetry.mozilla.org/
[dataset]: https://mozilla.github.io/python_moztelemetry/api.html#module-moztelemetry.dataset
Expand Down
Loading