Slicing Dimensions
Here we provide definitions and information about our standard slicing dimensions.
Note: the canonical, maintained dimension definitions now live as [dimensions.*] TOML blocks in the metric-hub repository (see definitions/*.toml and opmon/*.toml), consumed programmatically by OpMon and Looker; Jetstream uses a parallel [segments.*] mechanism (not dimensions) for segmenting experiment populations. This page remains a stub template and does not reflect current practice.
In OpMon, a project's [project.population.dimensions] list of slugs (in opmon/<project>.toml) is matched by slug against the [dimensions.*] blocks defined in definitions/<platform>.toml (or locally overridden in the project file) to build per-project dashboard filters. Looker does not consume the [dimensions] section directly; filterable fields there come from data source columns (see below).
Table of contents with links to dimensions.
Dimensions can also be defined or overridden at the project level: an OpMon project config (opmon/<project>.toml) may declare its own local [dimensions.*] blocks, or reference platform-level dimensions from definitions/<platform>.toml by slug in project.population.dimensions.
{{Dimension Name}}
TL;DR: two sentence max.
- Overview:
- What segmentation do we want to capture
- Calculation:
- Definitions of what user has to do to qualify
- Definitions of what telemetry must be sent to qualify.
- At least one working definition
- Link to the dimension's
[dimensions.*]TOML block (data source andselect_expression) in metric-hub; note that a data source can also expose all of its columns as dimensions automatically viacolumns_as_dimensions = trueon its[data_sources.*]block - Possibly an API-linked graph from STMO
- Common Issues: Failures and Gotchas
- Resources
- Similar dimensions