Files
mtusi2026lab6/docs/runbooks/time-to-ready.md
T

772 B

Time to ready

SLO: 95% of attachments that reach ready do so within 10 seconds of durable acceptance. The series is messenger_attachment_time_to_ready_seconds, a histogram in seconds. AttachmentReadyLatencyHigh uses histogram_quantile(0.95, ...) over 15 minutes and pages after 2 minutes above 10 seconds.

This SLO does not see jobs that never finish. Pair it with queue age.

  1. If p95 is high and queue age is low, open a worker trace and compare s3.put, s3.get, and db.transaction.
  2. A retry span with attempt > 1 and event retry means the first attempt was transient. The successful attempt should still contain S3 and the ready update.
  3. If p95 is quiet but users wait, read queue age. The worker is likely stopped or stuck before completion.