Skip to main content
RunBook Academy

← All break/fix scenarios in Observability

intermediateloki-ingestion~25 min

Break/Fix: Loki Receives No Logs

Reported symptoms

  • ●Loki has no logs from a service

Evidence

  • · Loki /metrics shows ingestion 0 for the stream
Diagnosis and resolutionclick to reveal

Root cause

The pipeline has broken.

Remediation

1. Check collector logs. 2. Verify configuration. 3. Check network. 4. Fix.

Verification

Logs appear in Loki; logcli query returns expected lines.

Prevention

Test with a synthetic log entry

Scenario

You are operating a production observability platform. The following symptoms appear:

  • Loki has no logs from a service

Available evidence:

  • Loki /metrics shows ingestion 0 for the stream

Your task

Determine the cause, recover, document, and validate.

Investigation

The investigation follows the discipline taught in Part XCVIII:

  1. Form hypothesis, find evidence, test, validate.
  2. Use the available evidence above to bound the search.
  3. Reach one of the likely root causes.

Recovery procedure

(Do not reveal until you have reasoned through the problem.)

  1. Identify the failing component.
  2. Apply the remediation pathway.
  3. Validate with the verification step.
  4. Document the incident.

Remediation

  1. Check collector logs. 2. Verify configuration. 3. Check network. 4. Fix.

Verification

Logs appear in Loki; logcli query returns expected lines.

Rollback

Revert

Prevention

Test with a synthetic log entry