← All runbooks in Observability
Runbook: Investigate Tempo Ingestion Failure
1 · Prerequisites
Confirm every item is in place before any state change.
- Tempo
- Receivers
- Object store
2 · Pre-checks
Read-only diagnostic commands. If any of these don't match expected output, stop and investigate further.
- · Determine which receiver is failing
3 · Procedure
Execute each step in order. Verify the expected output of a step before moving to the next.
- 1Check Tempo distributor metrics
- 2Verify OTLP receiver is up
- 3Verify network connectivity
- 4Verify object store is reachable
- 5Verify Tempo ingester is not rejecting
- 6Check Tempo limits and rate limits
4 · Verification
Confirm the procedure actually fixed the problem.
- ✓Tempo begins ingesting spans
- ✓Trace queries return data
- ✓Tempo metric panel shows ingest_rate > 0
5 · Rollback
If verification fails, undo the procedure in reverse order.
- ↶Reject rate-limits or restart Tempo
6 · Escalation
When the runbook isn't enough, contact:
- · Escalate to the platform team
Purpose
Investigate Tempo Ingestion Failure
When to use this runbook
Use this runbook when the operator needs a guided procedure to handle the situation described above.
Pre-checks
Before starting the procedure, confirm the prerequisites and pre-checks are met. The structured lists are rendered from the frontmatter by the page layout.
Procedure
Follow the steps from the frontmatter procedure steps. The page layout renders the steps as a checklist with copy-to-clipboard affordances.
Verification
After the procedure, the structured verification items from the frontmatter are rendered as a checklist.
Rollback
If the procedure fails or makes things worse, follow the structured rollback steps from the frontmatter.
Escalation
The structured escalation path is rendered from the frontmatter. Use it if the operator cannot complete the procedure safely.