Enable new Glean App `mdn-yari`
Categories
(Data Platform and Tools Graveyard :: Glean Platform, task, P1)
Tracking
(Not tracked)
People
(Reporter: gsleigh, Assigned: Dexter)
Details
Attachments
(1 file)
To be filled by the requester
Application ID*: mdn-yari
Application Canonical Name: https://developer.mozilla.org/
Description: Mozilla Developer Network (MDN) Web docs
Data-review response link: https://github.com/mdn/yari/pull/6813#issuecomment-1203705308
Repository URL: https://github.com/mdn/yari
Locations of metrics.yaml files (can be many):
- client/src/telemetry/metrics.yaml
Locations of pings.yaml files (can be many):
- client/src/telemetry/pings.yaml
Dependencies**:
- glean-js
Retention Days***: 180
(Optional) To be filled by the requester
Does the product require end-to-end encryption in the pipeline? Yes | No
If answered yes to the above, who should be granted access to the data?
No
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 180. 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.
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Updated•3 years ago
|
| Assignee | ||
Comment 1•3 years ago
•
|
||
Hey Guy, I'll start creating the PR and I'll merge it once the data-review response link is provided. Please note that the YAML files can't be found at client/src/telemetry/*.yaml on the main branch. Does the integration still need to happen?
Kindly ping me back once that happens and let me know if there's anything I can help with!
Hey Alessio
https://github.com/mdn/yari/pull/6813#issuecomment-1203705308
The data request is in the above link along with the initial PR for integration. It's a work in progress currently. We also need to figure out where our opt-in/out cookie gets set as we are currently unable to re-use the one from www.mozilla.org.
| Assignee | ||
Comment 3•3 years ago
|
||
Hey Travis, would you kindly take care of adding this to repositories.yaml once Guy is ready?
Comment 4•3 years ago
|
||
Sure, I'd be happy to help. Just ni? me when you are ready, and know that it usually takes about 24 hours for it to be enabled.
Comment 5•3 years ago
|
||
Once I finish the requested data-review for this collection, I will proceed with adding the application to the ingestion pipeline. If you have any questions, please do not hesitate to ask.
Travis
Comment 6•3 years ago
|
||
Comment 7•3 years ago
|
||
Still waiting on the underlying PR to mdn-yari repo to add the metrics.yaml file to land before I can land the probe-scraper changes.
Comment 8•3 years ago
|
||
PR adding mdn-yari to the probe-scraper ingestion landed
Updated•11 months ago
|
Description
•