Closed
Bug 1398873
Opened 8 years ago
Closed 5 years ago
[meta] Establish a probe info service
Categories
(Data Platform and Tools :: General, enhancement, P3)
Data Platform and Tools
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: gfritzsche, Unassigned)
References
Details
(Keywords: meta, Whiteboard: [measurement:client:tracking])
We repeatedly come up with the need for a service or dataset that provides us with:
- a view of all probes (histograms, scalars, events) of a Firefox release
- a historical view of the above, covering at least major versions (future goal: build ids / revisions)
- a single place to store this and hide the implementation details of scraping & parsing Histograms.json/Scalars.yaml/...
Reporter | ||
Comment 1•8 years ago
|
||
probe-scraper delivers a first part of that, pulling the scraping and parsing together in one place:
https://github.com/mozilla/probe-scraper
Reporter | ||
Comment 2•8 years ago
|
||
There is also potential overlap with buildhub:
https://github.com/mozilla-services/buildhub/
Could this data fit in there?
Updated•8 years ago
|
Priority: -- → P3
Comment 3•7 years ago
|
||
The prototype from comment 1 above has been extended quite a bit and is already very useful:
https://georgf.github.io/fx-data-explorer/index.html
Georg, do you think we can close this bug?
Flags: needinfo?(gfritzsche)
Reporter | ||
Comment 4•7 years ago
|
||
I don't think we have a reliable solution in place yet for the pipeline to use.
I scheduled a meeting this week to talk through what this will take and will follow up from there.
Flags: needinfo?(gfritzsche)
Comment 5•5 years ago
|
||
We now have a reliable solution, used internally by the mozilla-schema-generator among others.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•