1931865 - Propose a means for migrating the Telemetry Environment to Glean

Status: RESOLVED FIXED

(Toolkit :: Telemetry, task, P1)

Description

[Chris H-C :chutten]

The Legacy Telemetry Environment is tricky, so we need a plan for migrating it to Glean. Heck, we also need to define what "migrating it to Glean" even means: is it an API migration like Events (bug 1863031) and Scalars (bug 1923028 and bug 1927093)? Is it a reinstrumentation and removal like PingCentre (bug 1820548) or Use Counters (bug 1877273)? Is it some bespoke and secret third thing?

(Spoiler: It'll likely be a mix of different approaches to best suit the different kinds of data found in it)

This bug is about writing a proposal that:

• Clearly defines what we mean by "migration"
• Establishes the process we intend to follow to make that happen
• Highlights any challenges we foresee

Comment 1

[Chris H-C :chutten]

A little pre-proposal spoiler: the attribution and distribution portions of the Legacy Telemetry Environment will be migrated to the cross-product mechanisms being designed in bug 1930762

Comment 2

[Chris H-C :chutten]

Attachment: Proposal: Migrating Legacy Telemetry's Environment to Glean

Ready for initial feedback

Comment 3

[Chris H-C :chutten]

Oh, right, this is now accepted.

Comment 4

[Florian Quèze [:florian]]

(In reply to Chris H-C :chutten from comment #3)

Oh, right, this is now accepted.

It would be nice to reference here the bug where the next piece of the work will happen.

Comment 5

[Chris H-C :chutten]

Thank you for the encouragement to get my bugs filed. Now we're under a meta, and the next piece of work will be bug 1943698