1681812 - Proposal: Glean API Frontend for Firefox Telemetry

Status: RESOLVED FIXED

(Toolkit :: Telemetry, task, P1)

Description

[Chris H-C :chutten]

Nika had a neat idea that maybe migration would be easier if we could avoid duplication of instrumentation code through clever API use.

Migration looks like it'll start with a longish period of migrated metrics needing to collect to both Glean and Telemetry while we wait for enough migration to make Glean-only analysis viable. There are a lot of benefits to deliberate migration of data collections, but none of them are served by forcing devs to write the same instrumentation twice.

Write a proposal outlining the problem and some solutions. Get feedback from Firefox, Platform, Glean SDK, and others.

Comment 1

[Chris H-C :chutten]

Attachment: Proposal Doc

Looking for feedback from some specific people:

• Alessio, for strong opinions
• Jan-Erik, for FOG insights
• Nika, for being the one who came up with the idea
• mdboom, for making the mistake of already having provided some feedback

Please specifically find things I missed, things that are just wrong or unworkable, and names to bikeshed upon.

Note that the step of "migrating the collection from Telemetry to Glean" is explicitly not in-scope. How someone determines that GC_MS is deserving of migration and how to best represent it is an opaque process we'll be getting into in far more detail in the new year (but not here).

Comment 2

[Chris H-C :chutten]

Proposal approved, now to file an implementation bug. Thanks, all!