An alerting system is a human-made notification infrastructure that maps monitored conditions to prioritized signals routed to responsible operators. Its parameters are: (1) alert rules that define thresholds or anomaly-detection criteria for triggering, (2) notification channels (pager, email, chat, voice) that carry the signal, (3) escalation policies that escalate unacknowledged alerts through an on-call hierarchy, and (4) runbook integration that links each alert to prescribed remediation steps. Persistence: maintained by SRE/operations teams, encoded in monitoring platforms (Prometheus Alertmanager, PagerDuty, Opsgenie), and sustained through organizational practice. [formal: alerting | substrate: behavior | horizon: a moment | explicit: yes | epoch: 0.01]
Accepted ontology entry
alerting
An alerting system is a human-made notification infrastructure that maps monitored conditions to prioritized signals routed to responsible operators. Its parameters are: (1) alert rules that define thresholds or anomaly-detection criteria…
Definition
Why it is in scope
A human-made notification system that translates monitored signals into actionable alerts for operators — designed to draw attention to conditions requiring intervention, through structured channels (pagers, dashboards, on-call rotation), prioritized by severity, and governed by runbook procedures.
Names and aliases
- alertingen · CANONICAL
Relations from this entry
- cms7wyk72004ph6s8d82lhwqlSERVES →
Alerting systems are built and maintained for the sake of reliability — they detect anomalies early so failures can be prevented or mitigated before they cascade. Law 8d: for whose sake? The alerting system exists to further reliability.
- cmsj2z6ab01vvnobp417k0ifiSERVES →
Alerting serves incident-command: its designed purpose is to notify responders so incident-command can begin coordination. The signal from alerting triggers and feeds the command practice. Law 8d: servant (alerting) → master (incident-command).
Relations to this entry
- cmsj4xv33023knobp4j0vqjki← SERVES
An alert-threshold is configured for the sake of alerting: its purpose is defining the level at which a signal becomes an actionable alert. The servant (threshold) points at the master (alerting).
Record identity
- Created
- Aug 7, 2026, 2:56 PM UTC
- Content hash
- 20cd3dce5f739e450a34d03e50ceac01dfb9ad1c55e20671251d8bd5f22c3f8d