Closed Bug 1713380 Opened 4 years ago Closed 4 years ago

Document how to migrate individual collections from Telemetry to FOG

Categories

(Toolkit :: Telemetry, task, P1)

task

Tracking

()

RESOLVED FIXED
91 Branch
Tracking Status
firefox91 --- fixed

People

(Reporter: chutten, Assigned: chutten)

References

Details

Attachments

(1 file)

If I have a Telemetry of kind A, what Glean should I have instead? That's a complicated question to answer, but we have to try. And we'll have to try over and over again until migration is over.

So let's start with enumerating the common cases, the easy ones, and how to migrate them to Glean with FOG. List pratfalls that people familiar with Telemetry might fall into (like the new IPC restrictions, product- and process- and channel-agnosticism, etc).

We should resist the urge to try to explain anything that is too complicated to completely and unambiguously document in text. Instead, refer the reader to #glean:mozilla.org for hands-on assistance.

Be clear about missing pieces. There are a lot of metric types and behaviours we'll need that just don't yet exist. What should people do when they run across one? What should people do if they discover a new one?

Pushed by chutten@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5f349f10a6a2 Document how to migrate individual data collections from Telemetry to Glean r=mdroettboom DONTBUILD
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: