Test runbooks signals and thresholds

Instrument executable queue-backlog runbook for embedding ingestion pipeline so secondary on-call clearing ingest.lag_minutes > 45 can answer: demand, errors, latency/age, saturation. Emit fields needed by drill_completion_minutes and lag_minutes with bounded labels. Sample successful high-volume traces; keep errors and rollout transitions denser within policy.

Define at least one alert that would fire for INC-INGEST-9021, with a for/pending window that survives deploy blips. Missing scrape or missing revision labels must not look like health. Include a trace/log example id format you will actually search.

Add a unit/integration check that metrics increment on the happy path and on the runbook says 'restart something' without naming deployment or verifying lag branch. Store machine-readable output in CI artifacts when practical.

Cardinality discipline: tenant and revision are usually enough; raw question text is not a label. Exemplars or trace links beat screenshots alone when debugging INC-INGEST-9021. Define who owns alert fatigue review. If you export to a vendor, record retention and access. Synthetic probes should use non-sensitive fixtures and still exercise ingest worker + queue metrics. Practice the query you will type at 2am once, while calm.

Document the exact PromQL or log query in the runbook stub for this service. Verify histograms have buckets around your SLO target. Add a canary synthetic check that exercises the oracle path every few minutes in staging. Confirm that PII redaction happens before export. Track build/version as a label on the golden signals. Delete noisy debug logs before they become accidental product dependencies. In this chapter the product is executable queue-backlog runbook for embedding ingestion pipeline, the human stakeholder is secondary on-call clearing ingest.lag_minutes > 45, and the incident id you design against is INC-INGEST-9021. Re-state the oracle in your notes — drill INC-INGEST-9021: lag 60→5 minutes in ≤ 25m following runbook v1.4 — and keep the invariant visible: every command is copy-pasteable; mutating steps need change ticket; verify after each step. Track drill_completion_minutes and lag_minutes as the scoreboard. Surface under change control: ingest worker + queue metrics. If you only have forty minutes, finish the fixture for runbook says 'restart something' without naming deployment or verifying lag before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.

Set a timer for twelve minutes and attempt only the observability concerns for Runbook lab. Speak aloud what secondary on-call clearing ingest.lag_minutes > 45 would see on success versus on runbook says 'restart something' without naming deployment or verifying lag. Write three bullet artifacts you must keep: a fixture name tied to INC-INGEST-9021, a metric query for drill_completion_minutes and lag_minutes, and the rollback or refuse command for ingest worker + queue metrics. Then extend the notes with one sentence on how every command is copy-pasteable; mutating steps need change ticket; verify after each step would be violated if you skipped this page. Close by restating the oracle in your own words without looking: drill INC-INGEST-9021: lag 60→5 minutes in ≤ 25m following runbook v1.4.