← Back to guidesGuide

Troubleshoot Loki ingest limits and label policies before tenant rate limits drop logs

A practical runbook to separate bad labels, real tenant limits, and log-drop symptoms without blindly increasing quotas first.

Learn how to investigate Loki drops caused by label policies, rate limits, and excessive streams, then clean volatile labels and validate that critical searches still work.

Created: June 20, 2026

Published: June 20, 2026

Estimated time40 min

LevelAdvanced

Before you startRead access to Grafana/Loki or Logs Drilldown

PlatformsLinux

WhatsApp X LinkedIn

Linux

Diagnose from a Linux workstation using logcli, curl, promtool, and kubectl against Loki on Kubernetes.

logclikubectljqoptional promtool

List recent labels

logcli labels --since=15m --addr http://loki-gateway

Count series for a namespace

logcli series '{namespace="payments"}' --since=15m | jq length

Inspect drops by reason

promtool query instant http://prometheus:9090 'sum by (reason)(rate(loki_discarded_samples_total[5m]))'

Also available inDiagnosticar límites de ingestión y políticas de labels en Loki antes de perder logs

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.