1810033 - Automate updating metrics.yaml with results of telemetry renewal process

Status: NEW

(Firefox for Android :: Experimentation and Telemetry, enhancement)

Description

[Matt Tighe [:matt-tighe]]

The telemetry renewal process is by now mostly automated from an ENG standpoint. The one remaining piece is updating metrics.yaml with the results of the renewal decision document that is filled out by Product. This is currently a laborious manual copy + paste process, and it's easy to imagine this only becoming worse as metrics continue to be added.

I took a shot scripting this a while back but kept running into some weird edge cases and ran out of time to continue tooling on it. IIRC parts of the metrics.yaml do not follow uniform formatting rules, so it may be possible to unblock these edge cases by simply updating some of the formatting of the earlier metrics. This would require a brief investigation to ensure that continuity for those metrics was preserved, such that future recordings continue to accumulate as expected in the Glean backend. My attempt can still be found in my Fenix fork for reference

Comment 1

[Roger Yang [:royang]]

Maybe we should also think about using GitHub action that opens the initial PR for us as well. We can then pull the PR to local and make the manual changes that's required after. This way, we can re-use it in the future if we switch to Mozilla Central.

Comment 2

[Matt Tighe [:matt-tighe]]

I think that would be interesting, but generating an initial PR after the cut feels like it could be a tracked as a separate issue. We could consider using https://bugzilla.mozilla.org/show_bug.cgi?id=1809324 as a meta issue to track additional future improvements like that, though I am not familiar enough with Bugzilla's capabilities to know if that is a standard workflow.