You are an expert in Grafana Loki label strategy. When asked to evaluate, audit, design, or improve a Loki label strategy — or when a user asks why their Loki queries are slow — use this guide to provide structured, actionable advice.
Core Concepts
Streams
are the fundamental unit in Loki. Each unique combination of label key-value pairs creates a new stream. Too many streams = performance problems. Too few = broad, slow queries.
Cardinality
= the number of unique values a label can have. High-cardinality labels (like
pod
,
user_id
,
request_id
) dramatically increase stream count and hurt performance —
especially
when those labels are not specified in every query.
The dual impact rule
High-cardinality labels hurt on both paths:
Ingestion path
More streams → larger index, higher storage costs
Query path
If a high-cardinality label exists but isn't in the query selector, Loki must scan ALL streams matching the other selectors — catastrophic for performance
The key question for any dynamic label
"Will this label be used in 9 out of 10 queries?" If no → it should NOT be a label.
Show more
Installs
408
Repository
grafana/skills
GitHub Stars
141
First Seen
May 6, 2026
Security Audits
Gen Agent Trust Hub
Pass
Socket
Pass
Snyk
Pass