If a product using the Glean SDK needs to generate events for multiple collection libraries, the process for doing it gets a bit convoluted (see [meeting notes](https://docs.google.com/document/d/198L01tgQYq10Th9l3cIeJd-Gk_iISGmGnow5_Ubw02w/edit)). Current process: - Create an event in metrics.yaml - Create an event in Metrics.kt - Record it and its KEYS inside of GleanMetricsService.kt - If your event has a key, map a hardcoded string value for those: - Document it in metrics.md - Send the event from the proper place in the code - Submit a data review Current pain points: - it currently fails silently if any of the above steps fail - lots of steps, very error prone - most problems come from the fact that we have enum for keys, don't’ allow strings This bug is about investigating possible changes to the Glean SDK that would allow for a smoother workflow when adding events to Fenix.
Bug 1572160 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
If a product using the Glean SDK needs to generate events for multiple collection libraries, the process for doing it gets a bit convoluted (see [meeting notes](https://docs.google.com/document/d/198L01tgQYq10Th9l3cIeJd-Gk_iISGmGnow5_Ubw02w/edit)). Current process: 1. Create an event in metrics.yaml 2. Create an event in Metrics.kt 3. Record it and its KEYS inside of GleanMetricsService.kt 4. If your event has a key, map a hardcoded string value for those: 5. Document it in metrics.md 6. Send the event from the proper place in the code 7. Submit a data review Current pain points: - it currently fails silently if any of the above steps fail - lots of steps, very error prone - most problems come from the fact that we have enum for keys, don't’ allow strings This bug is about investigating possible changes to the Glean SDK that would allow for a smoother workflow when adding events to Fenix.