mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-11-30 16:22:00 +00:00
cb92d64d4d
Check if a user is a Mozilla employee by checking their Bugzilla groups, or checking if their VCS email ends with "@mozilla.com". When a user is setting up a new build environment, telemetry will be automatically enabled for them if they are an employee. If they're not an employee, they'll be asked if they want to opt in. Differential Revision: https://phabricator.services.mozilla.com/D106315
50 lines
1.8 KiB
ReStructuredText
50 lines
1.8 KiB
ReStructuredText
.. _buildtelemetry:
|
|
|
|
===============
|
|
Build Telemetry
|
|
===============
|
|
|
|
The build system (specifically, all the build tooling hooked
|
|
up to ``./mach``) has been configured to collect metrics data
|
|
points and errors for various build system actions. This data
|
|
helps drive team planning for the build team and ensure that
|
|
resources are applied to build processes that need them most.
|
|
You can adjust your telemetry settings by editing your
|
|
``~/.mozbuild/machrc`` file.
|
|
|
|
Glean Telemetry
|
|
===============
|
|
|
|
Mozbuild reports data using `Glean <https://mozilla.github.io/glean/>`_ via
|
|
:ref:`mach_telemetry`. The metrics collected are documented :ref:`here<metrics>`.
|
|
|
|
Error Reporting
|
|
===============
|
|
|
|
``./mach`` uses `Sentry <https://sentry.io/welcome/>`_
|
|
to automatically report errors to `our issue-tracking dashboard
|
|
<https://sentry.prod.mozaws.net/operations/mach/>`_.
|
|
|
|
Information captured
|
|
++++++++++++++++++++
|
|
|
|
Sentry automatically collects useful information surrounding
|
|
the error to help the build team discover what caused the
|
|
issue and how to reproduce it. This information includes:
|
|
|
|
* Environmental information, such as the computer name, timestamp, Python runtime and Python module versions
|
|
* Process arguments
|
|
* The stack trace of the error, including contextual information:
|
|
|
|
* The data contained in the exception
|
|
* Functions and their respective source file names, line numbers
|
|
* Variables in each frame
|
|
* `Sentry "Breadcrumbs" <https://docs.sentry.io/platforms/python/default-integrations/>`_,
|
|
which are important events that have happened which help contextualize the error, such as:
|
|
|
|
* An HTTP request has occurred
|
|
* A subprocess has been spawned
|
|
* Logging has occurred
|
|
|
|
Note that file paths may be captured, which include absolute paths (potentially including usernames).
|