Since we want one glean metrics definition for all of necko, we will ultimately migrate the existing metrics to this one.
Differential Revision: https://phabricator.services.mozilla.com/D156231
It doesn't actually collect anything new, but by collecting it all in one place
we should make analysis easier.
Can be shut off by setting `browser.newtabpage.ping.enabled` to `false`.
Differential Revision: https://phabricator.services.mozilla.com/D146224
It doesn't actually collect anything new, but by collecting it all in one place
we should make analysis easier.
Can be shut off by setting `browser.newtabpage.ping.enabled` to `false`.
Differential Revision: https://phabricator.services.mozilla.com/D146224
Based on our experience with Firefox for Android, annotating Glean metrics
with issue tracker component information can provide valuable context to
anyone searching for metrics.
This adds a new set of tags corresponding to the components in the
tree, annotates the existing Glean metrics. Finally, it also adds a new
mach command called `update-glean-tags` to update the tags files based
on build metadata.
Differential Revision: https://phabricator.services.mozilla.com/D134332
Based on our experience with Firefox for Android, annotating Glean metrics
with issue tracker component information can provide valuable context to
anyone searching for metrics.
This adds a new set of tags corresponding to the components in the
tree, annotates the existing Glean metrics. Finally, it also adds a new
mach command called `update-glean-tags` to update the tags files based
on build metadata.
Differential Revision: https://phabricator.services.mozilla.com/D134332
This does a few things:
1) It registers a few basic health metrics and a new Glean custom ping.
2) It arranges to mirror the default profile's
`datareporting.healthreport.uploadEnabled` preference to the
temporary background task profile. This requires not setting that
pref for every background task. This is not risky because the
Telemetry mechanism is completely disabled in background tasks at
this time.
3) It initializes Firefox-on-Glean.
4) It uses the Glean APIs to submit the Glean custom ping.
Differential Revision: https://phabricator.services.mozilla.com/D111022
This does a few things:
1) It registers a few basic health metrics and a new Glean custom ping.
2) It arranges to mirror the default profile's
`datareporting.healthreport.uploadEnabled` preference to the
temporary background task profile. This requires not setting that
pref for every background task. This is not risky because the
Telemetry mechanism is completely disabled in background tasks at
this time.
3) It initializes Firefox-on-Glean.
4) It uses the Glean APIs to submit the Glean custom ping.
Differential Revision: https://phabricator.services.mozilla.com/D111022
Covers adding the new JS global `GleanPings` for JS, the new structs for C++ at
mozilla::glean_pings, ping-id and string-table-index codegen, the usual
boilerplate for JS and C++ stuff, and tests.
Unresolved:
* What happens if we call this on a non-parent process?
(This isn't a supported mode of operation)
Differential Revision: https://phabricator.services.mozilla.com/D98671
Allow-list all Python code in tree for use with the black linter, and re-format all code in-tree accordingly.
To produce this patch I did all of the following:
1. Make changes to tools/lint/black.yml to remove include: stanza and update list of source extensions.
2. Run ./mach lint --linter black --fix
3. Make some ad-hoc manual updates to python/mozbuild/mozbuild/test/configure/test_configure.py -- it has some hard-coded line numbers that the reformat breaks.
4. Make some ad-hoc manual updates to `testing/marionette/client/setup.py`, `testing/marionette/harness/setup.py`, and `testing/firefox-ui/harness/setup.py`, which have hard-coded regexes that break after the reformat.
5. Add a set of exclusions to black.yml. These will be deleted in a follow-up bug (1672023).
# ignore-this-changeset
Differential Revision: https://phabricator.services.mozilla.com/D94045
