Open Bug 1432328 Opened 7 years ago Updated 3 years ago

Consolidate the documentation mechanism for telemetry

Categories

(Firefox :: New Tab Page, enhancement, P3)

enhancement

Tracking

()

Tracking Status
firefox59 --- wontfix
firefox60 --- wontfix

People

(Reporter: Mardak, Unassigned)

References

Details

From https://github.com/mozilla/activity-stream/issues/3616 The goal is to have a single source of truth for all the telemetry probes in AS. Currently, AS has at least 3 sources regarding telemetry, doc/data_events.js&data_dictionary.js, test/schemas/pings.js, and the comments in the code base, respectively. Keeping them up-to-date and in sync is getting harder over time, and discrepancy will inadvertently sneak in as we're adding more probes to AS. Some notes, findings, and caveats regarding certain metrics are also important, and should be recorded together with other documents. Unfortunately, they are mostly scattered in the source code comments or Github issues. @dmose has mentioned some tools (joi-browser&sphinxjs) that might enable us to simplify this process, e.g. generating documents from Joi schema. We both believe that it's worth checking them out to see if they already meet our needs. @dmose Feel free to add your thoughts here if I'm missing anything here :)
Severity: normal → enhancement
Priority: -- → P3
Component: Activity Streams: Newtab → New Tab Page
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.