Open Bug 1578383 Opened 5 years ago Updated 3 years ago

Namespace all Glean metrics, to prevent duplicates

Categories

(Data Platform and Tools :: Glean: SDK, defect, P4)

defect

Tracking

(Not tracked)

People

(Reporter: mdroettboom, Unassigned)

References

Details

(Whiteboard: [telemetry:glean-rs:backlog][schema-v2])

Attachments

(1 file)

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.

Whiteboard: [telemetry:glean-rs:m?] → [telemetry:glean-rs:m8]
Assignee: nobody → mdroettboom
Attached file Mini-proposal

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.

Summary: Catch duplicate metrics at build time → Namespace all Glean metrics, to prevent duplicates
Whiteboard: [telemetry:glean-rs:m8] → [telemetry:glean-rs:m8][schema-v2]
Whiteboard: [telemetry:glean-rs:m8][schema-v2] → [telemetry:glean-rs:m10][schema-v2]

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]

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)
See Also: → 1604496
Assignee: mdroettboom → nobody
Blocks: 1598247
Priority: P3 → P4
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: