1879155 - Enable new Glean App `moso-mastodon-android`

Status: RESOLVED FIXED

(Data Platform and Tools Graveyard :: Glean Platform, task)

Description

[Kirill Demtchouk]

To be filled by the requester

Application ID*: moso-mastodon-android
Application Canonical Name: Mozilla Social Android App
Description: Android client for Mozilla Social
Data-review response link: https://docs.google.com/document/d/17vK3r7Sihb_S4-_8oKNoAraWeb_QiomC3UL-2W7PHgY/edit?usp=sharing
Repository URL: https://github.com/MozillaSocial/mozilla-social-android
Locations of metrics.yaml files (can be many):

• /blob/main/core/analytics/metrics.yaml

Locations of pings.yaml files (can be many):

• NA (no custom pings were defined, uses default events ping)

Dependencies**:

• glean-core

Retention Days***: 37 months

(Optional) To be filled by the requester

Does the product require end-to-end encryption in the pipeline? No
If answered yes to the above, who should be granted access to the data?

Notes and guidelines

* This is the identifier used to initialize Glean (or the id used on the store on Android and Apple devices).

** Dependencies can be found in the Glean repositories. Each dependency must be listed explicitly. For example, the default Glean probes will only be included if glean itself is a dependency.

*** Number of days that raw data will be retained. A good default is 400. We can change this later to accommodate longer retention periods, though we cannot recover data that is past the retention period (for example, we cannot recover data that is 200 days old if your retention period is 180 days).

Need additional help?

If you need new dependencies, please file new bugs for them, separately from this one. For any questions, ask in the #glean channel.

To be filled by the Glean team

Application friendly name: my_app_name

The following are only required for products requiring encryption:

Document namespace: my-app-name

Please NI Operations on this bug to request the creation of encryption keys and an analysis project.

Comment 1

[Arkadiusz Komarzewski [:akomar]]

:dexter I'm not sure if moso-mastodon-android is the right application id here. I don't see it the codebase. How do I confirm it's the right one?

Comment 2

[Arkadiusz Komarzewski [:akomar]]

Probe scraper PR: https://github.com/mozilla/probe-scraper/pull/685 (application id needs to be confirmed).

Comment 3

[Alessio Placitelli [:Dexter]]

(In reply to Arkadiusz Komarzewski [:akomar] from comment #1)

:dexter I'm not sure if moso-mastodon-android is the right application id here. I don't see it the codebase. How do I confirm it's the right one?

Kirill, what's the Google App id of the app? Where can we find it in the codebase?

Comment 4

[Arkadiusz Komarzewski [:akomar]]

I checked Play Console and it looks like it's org.mozilla.social.nightly. I have updated the probe-scraper PR.

Kirill: I filed a PR to add Glean workflow in moso-android repository: https://github.com/MozillaSocial/mozilla-social-android/pull/455

Comment 5

[Kirill Demtchouk]

Thank you!

Devota confirmed the current Google app ID is org.mozilla.social.nightly, which we will likely change to org.mozilla.social for the official app store listing (i.e. the non-nightly listing). Does that mean we'll need to provision a separate Glean app for the non-nightly build?

Comment 6

[Alessio Placitelli [:Dexter]]

(In reply to Kirill Demtchouk from comment #5)

Thank you!

Devota confirmed the current Google app ID is org.mozilla.social.nightly, which we will likely change to org.mozilla.social for the official app store listing (i.e. the non-nightly listing). Does that mean we'll need to provision a separate Glean app for the non-nightly build?

Yes. Google Play treats "channels" as different products and assigns them different app ids. We can treat this the same way we treat Fenix: if you keep both channels, we'll provision both and then have them appear as "one product" (we have this capability). If you want to migrate the "Nightly" channel to the different channel, I believe we did this too with Fenix.

So, the question really becomes, what is your plan?

Comment 7

[Kirill Demtchouk]

Good question :) When they appear as "one product", how does that work?

Is the Glean app_id different in the data, but the two app IDs would show up under one entry in the Glean dictionary and/or send their data to the same destination BigQuery datasets?

Comment 8

[Arkadiusz Komarzewski [:akomar]]

(In reply to Kirill Demtchouk from comment #7)

Is the Glean app_id different in the data, but the two app IDs would show up under one entry in the Glean dictionary

Yes. Compare probe-scraper configuration for Fenix and Fenix entry in Glean Dictionary.

and/or send their data to the same destination BigQuery datasets?

Raw data goes to different datasets. There is another app-level dataset provisioned automatically with views that unify data from all channels.

Comment 9

[Arkadiusz Komarzewski [:akomar]]

Probe-scraper PR has been merged. NI? myself to check the generated artifacts tomorrow.

Comment 10

[Kirill Demtchouk]

Thanks for the details! It's good to know that Glean supports both flows (migrating one channel to the other channel vs. combining both channels as the same "product").

Do we have to make this decision now? Or can we wait until it comes time to release the production build in the Google App store?

Comment 11

[Arkadiusz Komarzewski [:akomar]]

(In reply to Kirill Demtchouk from comment #10)

Thanks for the details! It's good to know that Glean supports both flows (migrating one channel to the other channel vs. combining both channels as the same "product").

Do we have to make this decision now? Or can we wait until it comes time to release the production build in the Google App store?

We can decide later. Probably the best way to go will be to use another channel, similar to other applications.

Probe scraper run was successful, BigQuery tables and views were created (mozdata.org_mozilla_social_nightly).
Glean Dictionary entry was created: https://dictionary.telemetry.mozilla.org/apps/moso_mastodon_android

I'll keep the bug open to validate Looker assets.

Comment 12

[Arkadiusz Komarzewski [:akomar]]

It looks like Mastodon Android client has been canceled and repository was archived. I have filed a PR to deprecate it in probe-scraper: https://github.com/mozilla/probe-scraper/pull/694