Monitoring and Observability

If the system can fail in a way users notice, you should be able to see it before they tell you.

Context

Monitoring and observability translate system behavior into signals responders can trust. The goal is not to collect every metric. The goal is to make risky boundaries, user impact, and recovery state visible fast enough to guide action.

In a lifecycle-aware system, observability should preserve release intent. For brownfield work, make sure dashboards and alerts distinguish safe supported behavior from unsupported or coexistence-sensitive paths.

Inputs

• architecture-doc -- produced by the preceding skill in the lifecycle
• ci-cd-pipeline -- produced by the preceding skill in the lifecycle
• api-contract -- produced by the preceding skill in the lifecycle

Process

Step 1: Map User-Critical and Boundary-Critical Signals