← All runbooks in Observability
Runbook: Investigate Loki Ingestion Failure
1 · Prerequisites
Confirm every item is in place before any state change.
- Loki
- Object store
- Collector (Alloy / OTEL Collector)
2 · Pre-checks
Read-only diagnostic commands. If any of these don't match expected output, stop and investigate further.
- · Verify the service is logging
- · Verify the collector is running
3 · Procedure
Execute each step in order. Verify the expected output of a step before moving to the next.
- 1Check collector logs
- 2Verify collector configuration
- 3Check the scrape / path configuration against the service
- 4Verify network connectivity collector to Loki
- 5Check loki_canary or test query
- 6Check object store availability
- 7Verify Loki limits_config does not reject the stream
4 · Verification
Confirm the procedure actually fixed the problem.
- ✓Logs appear in Loki
- ✓loki_canary continues to log
- ✓The service stream is present in Loki
5 · Rollback
If verification fails, undo the procedure in reverse order.
- ↶Revert configuration changes
6 · Escalation
When the runbook isn't enough, contact:
- · Escalate to the platform team
Purpose
Investigate Loki 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.