FastAPI Observability Readiness

When to use

Invoke when a scaffolded FastAPI service needs production observability: distributed tracing, RED (Rate/Errors/Duration) metrics, logs correlated to traces, and SLI/SLO definitions with burn-rate alerting before release or before an on-call rotation takes it.

Do not use for: the service shell, settings, logging client, or error tiers (use fastapi-service-scaffold), auth or OWASP review (use fastapi-auth-and-security-review), task or event integration (use fastapi-async-and-task-integration), or pool-sizing/circuit-breaker/load-test gating (use fastapi-performance-and-resilience).

Inputs

Required:

• A service with the fastapi-service-scaffold baseline (no-op telemetry seam, structlog logger, request context present).
• Approved architecture/reliability SLO targets (latency/availability objectives, error budget) — or explicit confirmation they are intentionally deferred.

Optional: