Update for Fenix release

[tdsmith]

This needs more work, probably, but this is the ~minimal edit to avoid pointing people at the Nightly table for now.

aside: I love editing pipe tables by hand; it's great

[wlach]

This needs more work, probably, but this is the ~minimal edit to avoid pointing people at the Nightly table for now.

This is good, thank you, have one suggestion re: iOS, which now uses Glean.

aside: I love editing pipe tables by hand; it's great

It's still a little painful, but don't worry too much about making sure that things align perfectly, as prettier now takes care of that for you! You can just run prettier (or better yet, get your editor to run it via format-on-save) https://github.com/mozilla/data-docs#markdown-formatting

Note that we re-run prettier on a weekly basis so no need to worry (too much) about making sure that any individual PR is formatted.

[wlach]

Suggested change

	| Firefox iOS | `Fennec` | iOS | |
	| Firefox iOS | `Fennec` | iOS | Uses Glean (see below) |

[wlach]

Do any of the above use Glean?

[travis79]

Uses Glean:

Firefox for Fire TV
Firefox for Echo Show
Lockwise Android (going away?)
Lockwise iOS (also going away?)
Firefox Reality for Android

Planning on integrating with Glean very soon:

Focus Android
Focus iOS
Klar? (discussion of whether or not to instrument Klar is in the works)

[jklukas]

For completeness, there is also Reference Browser for Android that sends Glean telemetry.

Fire TV, Echo Show, Firefox Reality, and Firefox for iOS all send both core pings and Glean telemetry, and KPI reporting still relies on the core pings.

[jklukas]

We now have a canonical UDF for "prettifying" app names, including a table of transformations in the docs. See https://mozilla.github.io/bigquery-etl/mozfun/norm/#product_info-udf

I think that table should probably be the source of truth documentation, since it's used to generate the UDF logic and is guaranteed to stay up to date. We should link to that table from these docs, and make sure our terminology is consistent between the two.

That said, the product_info table is currently mostly focused on making sure we have all the bases covered for mobile telemetry that feeds into KPIs. Currently, Fenix is the only app for which baseline pings are the source of truth we use for KPIs. We should definitely transition KPI reporting for Firefox iOS to baseline pings, but that has not happened yet.

So, I think it would be good for the docs here to list Glean apps for the time being, but defer to https://mozilla.github.io/bigquery-etl/mozfun/norm/#product_info-udf for naming. Then we should set a goal for January to fully codify in UDF form the mapping for Glean apps, and move to Glean as source of truth for KPIs wherever possible.

[tdsmith]

@jklukas do you know how to assign these datasets to release channels?

  org_mozilla_ios_fennec                 
  org_mozilla_ios_firefox                
  org_mozilla_ios_firefoxbeta

[tdsmith]

^ please disregard; Frank reminded me that the probe-info service can shed some light on these https://probeinfo.telemetry.mozilla.org/glean/repositories

[jklukas]

I think the info here on legacy event pings is incorrect. It's my understanding that events for mobile apps are sent in mobile-event and focus-event pings. The event ping is Desktop-specific.

[jklukas]

I did not realize that https://probeinfo.telemetry.mozilla.org/glean/repositories contained logical channel names! This is great! We should absolutely be using this data as source of truth for building some downstream views. I'm going to write up an issue in bigquery-etl.

Edit: see mozilla/bigquery-etl#1466