Test on-call operations signals and thresholds

Instrument humane escalation path for production AI answer platform so primary engineer receiving SEV2 after hours can answer: demand, errors, latency/age, saturation. Emit fields needed by ack_minutes and pages_per_week 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-OC-554, 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 everyone paged for SEV3 noise → real SEV1 ignored 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-OC-554. 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 PagerDuty schedule ai-answer-primary. 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 humane escalation path for production AI answer platform, the human stakeholder is primary engineer receiving SEV2 after hours, and the incident id you design against is INC-OC-554. Re-state the oracle in your notes — game day: primary misses ACK → secondary owns INC-OC-554 in 15m with access grant — and keep the invariant visible: missed ACK in 15m escalates; SEV1 pages dual; handoff includes timeline + next action. Track ack_minutes and pages_per_week as the scoreboard. Surface under change control: PagerDuty schedule ai-answer-primary. If you only have forty minutes, finish the fixture for everyone paged for SEV3 noise → real SEV1 ignored 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 On-call lab. Speak aloud what primary engineer receiving SEV2 after hours would see on success versus on everyone paged for SEV3 noise → real SEV1 ignored. Write three bullet artifacts you must keep: a fixture name tied to INC-OC-554, a metric query for ack_minutes and pages_per_week, and the rollback or refuse command for PagerDuty schedule ai-answer-primary. Then extend the notes with one sentence on how missed ACK in 15m escalates; SEV1 pages dual; handoff includes timeline + next action would be violated if you skipped this page. Close by restating the oracle in your own words without looking: game day: primary misses ACK → secondary owns INC-OC-554 in 15m with access grant.