mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-23 10:15:41 +00:00
ede2c0b68a
Before this commit, we used event telemetry to record timing and counts for the different steps of a bookmark merge (fetching the local tree, new local contents, remote tree, and new remote contents; merging; applying; fetching outgoing records; and notifying observers). This has several limitations. We need to store all numbers as strings, include a "flow ID" to tag events from the same merge, and collect failure reasons twice. We also can't correlate these events to the existing engine telemetry, meaning we can't see other stats for that engine, or for the entire sync. Finally, we need to run separate queries on these events for analysis, instead of extending our existing engine dashboards. This approach also feels like an abuse of event telemetry, so this commit adds a "steps" field for each engine in the Sync ping. Each step has a name, time taken, and additional named counts, like the number of items in the tree, or merged structure stats. Currently, only the `buffered-bookmarks` engine records these steps. Differential Revision: https://phabricator.services.mozilla.com/D33411 --HG-- extra : moz-landing-system : lando |
||
---|---|---|
.. | ||
app | ||
build_scripts | ||
core | ||
docs | ||
geckoview | ||
hybrid-content | ||
other | ||
pings | ||
pingsender | ||
tests | ||
components.conf | ||
datareporting-prefs.js | ||
Events.yaml | ||
healthreport-prefs.js | ||
histogram-whitelists.json | ||
Histograms.json | ||
Makefile.in | ||
moz.build | ||
Processes.yaml | ||
Scalars.yaml | ||
telemetry-constants.mozbuild | ||
TelemetryOriginEnums.h | ||
TelemetryStartup.jsm |