MonOps
The whole lifecycle
Stage 0309:46:04 · policy

L1 to L3 without a second vendor

Five minutes without an acknowledgement and it finds someone else. No second product required.

Most monitoring tools stop at sending a notification. Whether a human saw it is somebody else’s problem, which is why on-call routing is usually a separate purchase with its own bill and its own integration to maintain.

Here it is the same state machine. If nobody acknowledges within the timeout, the policy climbs a level and routes to the next rotation. Five minutes per level, three levels, then it stops — because an escalation policy that eventually pages everyone is one people learn to ignore.

The ceiling matters more than the speed. L3 is deliberately not "everyone": it is high enough to reach someone awake and low enough that reaching L3 still means something when it happens.

Defaults at this stage

timeout per level
300s
ceiling
L3

All six stages, on every plan with agents.

Detection through post-mortem in one system. No second vendor for paging.

Deploy an agent