Status: IN
OpenShift alerting operates as a multi-stage pipeline: PrometheusRules define both recording and alerting rules (evaluated at 30s default intervals), AlertRelabelConfigs modify alerts before routing (supporting Replace/Keep/Drop/HashMod/LabelMap actions), Alertmanager routes and groups alerts (with inhibit rules suppressing targets when sources fire), and silences persist across pod restarts only with persistent storage — each stage transforms or filters the alert stream.
Five base beliefs each describe a stage in the alerting pipeline; combining reveals the ordered flow where each component's output feeds the next, and failure at any stage (e.g., silences lost on restart) breaks downstream behavior
Depends on (SL): prometheusrule-supports-both-rule-types, ocp-prometheus-default-evaluation-interval-30s, ocp-alertrelabelconfig-actions, alertrelabelconfig-modifies-before-alertmanager, silences-require-persistent-storage