Metric walls versus actionable tiles for integration teams

Observability for Integration Teams spends a full session on dashboard hygiene. The anti-pattern is familiar: thirty charts, none tied to a decision.

We constrain capstone candidates to five tiles per integration path, each answering a question that could change the next hour of work. Examples include consumer lag against an SLO, duplicate payment attempts, vendor error code ratios, and human approval queue age. Tiles without owners get deleted—even if they look pretty.

We also cover seasonal adjustments. Korean retail peaks around Chuseok and year-end sales require temporary threshold shifts documented in the runbook. Without that note, on-call engineers assume misconfiguration.

The module stops short of vendor-specific agent tuning. Bring your own exporter questions; we focus on integration-shaped signals rather than greenfield microservice defaults.