Open
Bug 1578383
Opened 5 years ago
Updated 4 years ago
Namespace all Glean metrics, to prevent duplicates
Categories
(Data Platform and Tools :: Glean: SDK, defect, P4)
Data Platform and Tools
Glean: SDK
Tracking
(Not tracked)
NEW
People
(Reporter: mdroettboom, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:backlog][schema-v2])
Attachments
(1 file)
96 bytes,
text/x-google-doc
|
Details |
1523977 added a probe scraper feature to detect duplicate metrics at probe_scraper time. It would be nice (if possible) to also catch duplicates at build time.
Updated•5 years ago
|
Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:m8]
Reporter | ||
Updated•5 years ago
|
Assignee: nobody → mdroettboom
Reporter | ||
Comment 1•5 years ago
|
||
Reporter | ||
Comment 2•5 years ago
|
||
After discussion on the mini-proposal, it was decided to solve this problem by namespacing all Glean metrics. This neatly sidesteps the problem of detecting for duplicates at build time.
Reporter | ||
Updated•5 years ago
|
Summary: Catch duplicate metrics at build time → Namespace all Glean metrics, to prevent duplicates
Reporter | ||
Updated•5 years ago
|
Whiteboard: [telemetry:glean-rs:m8] → [telemetry:glean-rs:m8][schema-v2]
Updated•5 years ago
|
Whiteboard: [telemetry:glean-rs:m8][schema-v2] → [telemetry:glean-rs:m10][schema-v2]
Comment 3•5 years ago
|
||
Hey Mike, I'm moving this to backlog. This has a [schema-v2] tag, will it happen in Q4?
Flags: needinfo?(mdroettboom)
Whiteboard: [telemetry:glean-rs:m10][schema-v2] → [telemetry:glean-rs:backlog][schema-v2]
Reporter | ||
Comment 4•5 years ago
|
||
We should talk about when we want to do a schema revision, I guess. I very much doubt it will happen in Q4 at this point.
Flags: needinfo?(mdroettboom)
Reporter | ||
Updated•4 years ago
|
Assignee: mdroettboom → nobody
Updated•4 years ago
|
Priority: P3 → P4
You need to log in
before you can comment on or make changes to this bug.
Description
•