mozilla / mozilla/probe-scraper
Read mozilla-central's metrics_index instead of requiring manual addition of new definitions files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 26
- Forks
- 73
- Avg merge
- 10h
- Merged PRs (30d)
- 3
Description
Presently we order Firefox on Glean consumers to manually file bugs whenever they add new metrics.yaml or pings.yaml files to metrics_index.py.
This isn't the most ergonomic way to deal with this. Could we have probe-scraper pull https://hg.mozilla.org/mozilla-central/file/tip/toolkit/components/glean/metrics_index.py and read the list of yamls from there (like mozilla-central's build does)?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading mozilla-central's toolkit/components/glean/metrics_index.py and compare its YAML list with the current probe-scraper workflow for manually added metrics.yaml and pings.yaml files. Done means probe-scraper pulls and reads that list directly, removing the need for consumers to file manual addition bugs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100