Skip to main content
RunBook Academy

← All break/fix scenarios in Observability

intermediateloki-ingestion~25 min

Break/Fix: Loki Ingestion Spike

Reported symptoms

  • Loki ingest rate has spiked 20x

Evidence

  • · A new debug-level stream was enabled
Diagnosis and resolutionclick to reveal

Root cause

Code change enabled debug logging.

Remediation

1. Identify the stream. 2. Revert log level. 3. Validate.

Verification

Ingest returns to baseline.

Prevention

Log rate alerts

Scenario

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

  • Loki ingest rate has spiked 20x

Available evidence:

  • A new debug-level stream was enabled

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. Identify the stream. 2. Revert log level. 3. Validate.

Verification

Ingest returns to baseline.

Rollback

Revert

Prevention

Log rate alerts