What to do when Loki sinks from label cardinality explosion

Practical troubleshooting: symptoms, redesigning labels and ingestion pipelines without losing useful context

Actionable guide to detect and fix high-cardinality labels that degrade or crash Loki: symptoms, metrics and logs to inspect, safe Promtail/ingest changes and validation steps.

Created: April 13, 2026

Published: April 13, 2026

Estimated time60 min

LevelAdvanced

Before you startAccess to Loki metrics (/metrics) and Loki logs

PlatformsDocker / Linux

WhatsApp X LinkedIn

Linux

Diagnostics for Linux installs using systemd or packages, with examples for inspecting metrics and processes.

SSH access to the host running Loki and sudo if neededcurl and jq available for API queries

Check the loki service status

systemctl status loki -l --no-pager

Scrape Loki metrics and search for active streams

curl -s http://127.0.0.1:3100/metrics | grep loki_ingester_active_streams || true

Query API to inspect series volume for a specific label (safe example)

curl -s -G 'http://127.0.0.1:3100/loki/api/v1/query_range' --data-urlencode 'query=count_over_time({job="my-app"}[1h])' --data 'limit=100' | jq .

Also available inQué hacer cuando Loki se hunde por labels con demasiada cardinalidad

Content locked

This guide requires both steps before full content is available.

○Click “Like” on this guide.
○Share on WhatsApp, X, LinkedIn, or copy the link.

Access is automatically unlocked as soon as both steps are completed.