This page describes the steps for adding Glean to a project. This does not include the steps for adding a new metrics or pings to an existing Glean integration. If that is what your are looking for, refer to the Adding new metrics or the Adding new pings guide.
The Glean integration checklist can help to ensure your Glean SDK-using product is meeting all of the recommended guidelines.
Products (applications or libraries) using a Glean SDK to collect telemetry must:
Integrate the Glean SDK into the build system. Since the Glean SDK does some code generation for your metrics at build time, this requires a few more steps than just adding a library.
Go through data review process for all newly collected data.
Ensure that telemetry coming from automated testing or continuous integration is either not sent to the telemetry server or tagged with the
automationtag using the
Important consideration for libraries: For libraries that are adding Glean, you will need to indicate which applications use the library as a dependency so that the library metrics get correctly indexed and added to the products that consume the library. If the library is added to a new product later, then it is necessary to file a new [bug][dataeng-bug] to add it as a dependency to that product in order for the library metrics to be collected along with the data from the new product.
Additionally, applications (but not libraries) must:
Request a data review to add Glean to your application (since it can send data out of the box).
Initialize Glean as early as possible at application startup.
Provide a way for users to turn data collection off (e.g. providing settings to control
Glean.setUploadEnabled()). The exact method used is application-specific.
Step-by-step tutorials for each supported language/platform, can be found on the specific integration guides: