Node.js Observability Readiness

When to use

Invoke when a scaffolded Node.js 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, config, logging client, or error tiers (use nodejs-service-scaffold), auth or OWASP review (use nodejs-auth-and-security-review), queue or event integration (use nodejs-queue-and-event-integration), or backpressure/circuit-breaker/load-test gating (use nodejs-performance-and-resilience).

Inputs

Required:

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

Optional: