Closed
Bug 1479518
Opened 6 years ago
Closed 6 years ago
Require `products` key for new probes in Histograms.json
Categories
(Toolkit :: Telemetry, enhancement, P1)
Toolkit
Telemetry
Tracking
()
RESOLVED
FIXED
People
(Reporter: frank, Assigned: chutten)
References
Details
It's difficult to know what is usable in the mobile-metrics ping. It is worth it to require the `products` field for new pings, especially to ensure we know which ones are Firefox-specific (lots of TIME_TO_, FX_, etc. are). Whether this bug includes making a first-pass at specifying products for existing probes is up to the implementer.
Assignee | ||
Comment 1•6 years ago
|
||
I will form a proposal about how to tackle this so we can shop it around to stakeholders for input and education.
Assignee: nobody → chutten
Status: NEW → ASSIGNED
Priority: -- → P1
Reporter | ||
Comment 2•6 years ago
|
||
This may be helpful, [0] is a list of all metrics reported by GeckoView. We can get something similar for Fennec, but that has to be done in Spark. [0] https://sql.telemetry.mozilla.org/queries/57750/source
Assignee | ||
Comment 3•6 years ago
|
||
I've written up a proposal for what this'll take. Frank, what are your thoughts? Can you think of others who should give this a look-over before I pass it to fx-data-platform for general input? https://docs.google.com/document/d/1p1tBJaUnKOqGN_Yo7ySbfVdIu8c9_PCNJ1kh4zyXOyI/edit#
Flags: needinfo?(fbertsch)
Reporter | ||
Comment 4•6 years ago
|
||
Reviewed. Taking it to fx-data-platform seems like a good next step.
Flags: needinfo?(fbertsch)
Assignee | ||
Comment 6•6 years ago
|
||
Current status: seeking individual impact feedback from Firefox developers who will be the most affected by this change. :dao gave verbal acceptance of the idea in practice, but I'd like a couple of reviews of the document to point out some flaws. Then off to estimation for timeboxing, then to firefox-dev for announcing. Implementation will be a subsequent bug.
Points: --- → 2
Flags: needinfo?(chutten)
Assignee | ||
Comment 7•6 years ago
|
||
Individual Impact Feedback is done. When I asked on Slack#firefox :felipe, :johannh, and :mnoorenberghe offered to review the doc. Concerns they raised ranged from Devs resisting this new field as there's nothing in the doc explaining how they themselves benefit, to mutability of the products key after it has already been set. I have captured these in the text of the proposal so they aren't lost. I think we're ready to proceed.
Assignee | ||
Comment 8•6 years ago
|
||
With the filing of the project meta, work here's done.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•