Skip to main content
RunBook Academy

← All break/fix scenarios in Observability

advancedstorage-backend~30 min

Break/Fix: Object Storage Unavailable

Reported symptoms

  • ●Loki / Tempo cannot write

Evidence

  • · Ingest metrics show object store errors
Diagnosis and resolutionclick to reveal

Root cause

The object store is down or credentials are wrong.

Remediation

1. Verify object store. 2. Verify credentials. 3. Failover if multi-region.

Verification

Ingestion resumes.

Prevention

Multi-region failover

Scenario

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

  • Loki / Tempo cannot write

Available evidence:

  • Ingest metrics show object store errors

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. Verify object store. 2. Verify credentials. 3. Failover if multi-region.

Verification

Ingestion resumes.

Rollback

Revert

Prevention

Multi-region failover