Closed Bug 1497800 Opened 7 years ago Closed 7 years ago

Implement a generic metric registry parser

Categories

(Toolkit :: Telemetry, enhancement, P1)

enhancement
Points:
3

Tracking

()

RESOLVED FIXED
Tracking Status
firefox64 --- affected

People

(Reporter: Dexter, Assigned: mdroettboom)

References

Details

(Whiteboard: [telemetry:mobilesdk:m1])

Attachments

(2 files)

This bug is about designing and implementing a generic YAML metric registry parser for the mobile SDK. The same generic parser could be eventually used on desktop as well. On Firefox for Desktop, we have a few different parsers (histograms, events, scalars, use counters) that all share the same features: they parse JSON or YAML files, look for specific metric properties, check for valid values, abstract the read data as Python object and then transform these objects to some language constructs (C++ on Desktop). The Mobile SDK supports many different metric types. We should aim for a design that: - allows to read one or more YAML file (even if only one file is used in early development, on mobile); - allows to define the supported types and the expected values for the metric specific properties; - allows to define how the extracted data is transformed into the final language (Kotlin for the mobile SDK);
Assignee: nobody → mdroettboom
Blocks: 1491345
Priority: -- → P1
Points: --- → 3
Blocks: 1497802
Blocks: 1497804
Blocks: 1497816
Whiteboard: [telemetry:mobilesdk:m1]
Blocks: 1497878
Attached file GitHub Pull Request
The first pass of the implementation has been reviewed and merged. The repository URL is: https://github.com/mozilla/glean_parser Coming next: - PyPI deployment - Usage docs
Blocks: 1501312
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: