Technical detail ยท Service Resilience: Operating Context and Control Map
Record the evidence for an incident
The data model behind the policy should preserve enough context to explain an incident. Store request id, command id, idempotency key, dependency name, deadline budget, attempt number, timeout reason, breaker state, pool rejection, fallback type, device id, tenant id, trace id, and final user-visible response. OpenTelemetry spans can connect the caller, dependency, queue, and fallback path; Prometheus counters can track rates; logs can carry the command id needed for support to reconcile a physical action.