Enable new Glean App `ads.backend`
Categories
(Data Platform and Tools Graveyard :: Glean Platform, task)
Tracking
(Not tracked)
People
(Reporter: gleonard, Assigned: akomar)
References
(Depends on 1 open bug)
Details
Attachments
(1 file)
%23 To be filled by the requester
Application ID*: ads.backend
Application Canonical Name: Mozilla Ads Backend Service
Description: Mozilla Ads Backend Service
Data-review response link: https://bugzilla.mozilla.org/show_bug.cgi?id=1900898
Repository URL: https://github.com/mozilla-services/mars-telemetry
Locations of metrics.yaml files (can be many):
- telemetry/glean/metrics.yaml
Locations of pings.yaml files (can be many):
- No pings.yaml file needed since this is server side Glean
Dependencies**:
- glean-server
Retention Days***: 400
%23%23 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).
%23%23 Need additional help%3F
If you need new dependencies, please file new bugs for them, separately from this one. For any questions, ask in the %23glean channel.
%23 To be filled by the Glean team
Application friendly name: my_app_name
| Reporter | ||
Comment 1•2 years ago
|
||
Is there an update on when this application can be added to probe-scraper?
Comment 2•1 year ago
|
||
(In reply to Glenda Leonard from comment #1)
Is there an update on when this application can be added to probe-scraper?
There is an ongoing discussion about this, and it bubbled up to Mark Reid to unblock. Will keep this ticket posted.
| Assignee | ||
Comment 3•1 year ago
|
||
While data review part is discussed, another issue here is that this service's repo is private. Probe scraper does not support ingesting metrics metadata from private repositories. Since there is some time pressure and we do not want to block on this too long, as a temporary solution we should create a new public repository with a mirror of metrics.yaml and use it in probe-scraper config.
In parallel we will work on adding support for scraping private repositories (https://mozilla-hub.atlassian.net/browse/DO-1706). When this is done we will switch probe-scraper to use the private repo and delete the temporary, public one.
| Reporter | ||
Comment 4•1 year ago
|
||
Once a timeline is known for the work please update the Jira task. This metrics.yaml file does expose information our ad partners.
| Reporter | ||
Comment 5•1 year ago
|
||
I've updated the above request to reference the new public repository
Repository URL: https://github.com/mozilla-services/mars-telemetry
Also note that the blocking data review request has been approved.
https://bugzilla.mozilla.org/show_bug.cgi?id=1900898
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 6•1 year ago
|
||
Probe-scraper PR: https://github.com/mozilla/probe-scraper/pull/774
Glenda: can you add probe-scraper GitHub action to the public repository? See https://mozilla.github.io/glean/book/user/adding-glean-to-your-project/enable-data-ingestion.html#validate-and-publish-metrics
| Reporter | ||
Comment 7•1 year ago
•
|
||
Added.
https://github.com/mozilla-services/mars-telemetry/actions
The first run failed which I'm assuming is due to probe-scraper not yet knowing about the repo.
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Comment 8•1 year ago
|
||
I merged probe-scraper PR.
ni? myself to check back table deployment.
Comment 9•1 year ago
|
||
| Reporter | ||
Comment 10•1 year ago
•
|
||
(In reply to Arkadiusz Komarzewski [:akomar] from comment #8)
I merged probe-scraper PR.
ni? myself to check back table deployment.
I checked and the tables do exist in both moz-fx-data-shar-nonprod-efed and moz-fx-data-shared-prod .
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Description
•