A glossary with explanations and background for wording used in the Glean project.
According to the dictionary the word “glean” means:
to gather information or material bit by bit
Glean is the combination of the Glean SDK, the Glean pipeline & Glean tools.
See also: Glean - product analytics & telemetry.
The general data pipeline is the infrastructure that collects, stores, and analyzes telemetry data from our products and logs from various services. See An overview of Mozilla’s Data Pipeline.
The Glean pipeline additionally consists of
The Glean SDK is the bundle of libraries with support for different platforms. The source code is available at https://github.com/mozilla/glean.
Glean provides additional tools for its usage:
Metrics are the individual things being measured using Glean. They are defined in metrics.yaml files, also known as registry files.
Glean itself provides some metrics out of the box.
A ping is an entity used to bundle related metrics. The Glean SDK provides default pings and allows for custom ping, see Glean Pings.
"To submit" means to collect & to enqueue a ping for uploading.
The Glean SDK stores locally all the metrics set by it or by its clients. Each ping has its own schedule to gather all its locally saved metrics and create a JSON payload with them. This is called "collection".
Upon successful collection, the payload is queued for upload, which may not happen immediately or at all (in case network connectivity is not available).
Unless the user has defined their own custom pings, they don’t need to worry too much about submitting pings. All the default pings have their scheduling and submission handled by the SDK.
This Week in Glean is a series of blog posts that the Glean Team at Mozilla is using to try to communicate better about our work.