Grafana Mimir glossary

The terms and definitions that follow relate to Grafana Mimir and GEM.

Blocks storage

Blocks storage is the Mimir storage engine based on the Prometheus TSDB. Grafana Mimir stores blocks in object stores such as AWS S3, Google Cloud Storage (GCS), Azure blob storage, or OpenStack Object Storage (Swift). For a complete list of supported backends, refer to About the architecture

Chunk

A chunk is an object containing encoded timestamp-value pairs for one series.

Churn

Churn is the frequency at which series become idle.

A series becomes idle after it’s no longer exported by the monitored targets. Typically, series become idle after a monitored target process or node gets terminated.

Component

Grafana Mimir comprises several components. Each component provides a specific function to the system. For component specific documentation, refer to one of the following topics:

Flushing

Flushing is the operation run by ingesters to offload time series from memory and store them in the long-term storage.

Gossip

Gossip is a protocol by which components coordinate without the need for a centralized key-value store.

HA tracker

The HA tracker is a feature of the Grafana Mimir distributor. It deduplicates time series received from two or more Prometheus servers that are configured to scrape the same targets. To configure HA tracking, refer to Configuring high-availability deduplication.

Hash ring

The hash ring is a distributed data structure used by Grafana Mimir for sharding, replication, and service discovery. Components use a key-value store or gossip to share the hash ring data structure. For more information, refer to the Hash ring.

Key-value store

A key-value store is a database that associates keys with values. To understand how Grafana Mimir uses key-value stores, refer to Key-value store.

Memberlist

Memberlist manages cluster membership and member failure detection using gossip.

Org

Refer to Tenant.

Ring

Refer to Hash ring.

Sample

A sample is a single timestamped value in a time series.

Given the series node_cpu_seconds_total{instance="10.0.0.1",mode="system"} its stream of samples may look like:

# Display format: <value> @<timestamp>
11775 @1603812134
11790 @1603812149
11805 @1603812164
11819 @1603812179
11834 @1603812194

Series

A series is a single stream of samples belonging to the same metric, with the same set of label key-value pairs.

Given a single metric node_cpu_seconds_total you may have multiple series, each one uniquely identified by the combination of metric name and unique label key-value pairs:

node_cpu_seconds_total{instance="10.0.0.1",mode="system"}
node_cpu_seconds_total{instance="10.0.0.1",mode="user"}
node_cpu_seconds_total{instance="10.0.0.2",mode="system"}
node_cpu_seconds_total{instance="10.0.0.2",mode="user"}

Tenant

A tenant is the owner of a set of series written to and queried from Grafana Mimir. Grafana Mimir isolates series and alerts belonging to different tenants. To understand how Grafana Mimir authenticates tenants, refer to Authentication and authorization.

Time series

Refer to Series.

User

Refer to Tenant.

Write-ahead log (WAL)

The write-ahead Log (WAL) is an append only log stored on disk by ingesters to recover their in-memory state after the process gets restarted. For more information, refer to The write path.