Measurement Labels

Use measurement labels to differentiate independent streams.

Measurements labels provide a way to collect additional metadata alongside each measurement.

Primary Labels are used to differentiate multiple, independent data streams for a given meter, while general Labels are used to store additional metadata that could be used to segregate usage data in different ways.

Primary Labels

The Primary Labels of a meter are used to differentiate between Independent Streams of data. When multiple Primary Labels are provided for a meter, each combination of values represents a separate stream.

These labels can be used to associate each measurement with a customer, as well as any other segments that you may use to categorize measurements. For example, if a service offers multiple deployment environments that are aggregated separately, you can use a Primary Label to represent each of these dimensions:

customer_id
This is a unique value that identifies each customer.
deployment
Identifies the deployment environment that is the source of each measurement. This could be a value such as staging or production.

Then, when Octane receives a measurement, the set of Primary Label key-value pairs included with the measurement will be used to uniquely identify each independent data stream.

🚧

Primary Labels are required on measurements

If a meter specifies Primary Labels, those labels must be present on any measurements sent for that meter. If a measurement is missing a Primary Label, it can't be associated with a stream of measurements and is considered invalid. If a measurement is marked invalid, you will receive alerts through our Slack integration, or a support associate will contact you directly.


Did this page help you?