2 min lesson
Observability & on-call
Use "Observability & on-call" to tell the cases apart, then choose a response for each one.
Step 1 of 2
The JD lists observability alongside retries and DLQs as a first-class requirement and for an EM it's where reliability stops being architecture and becomes a thing the team manages day to day.
A webhook system fails quietly. Events don't crash a page; they just don't arrive. So the only way you know the system is healthy is the instrumentation you built. Cover the three signals and make each one map to a decision.
Metrics are only half of it. Pair them with traces across the pipeline (ingest → queue → worker → endpoint) and structured logs keyed by event id, so one event is greppable end to end.
Interactive diagram. Tab through its regions; each focused region shows its detail in the panel below.
Ranked by how early each signal warns you - page on the leaders, write SLOs against the laggards.