Alerting Architecture

Alerting Architecture An architecture diagram generated by Archify. PrometheusRule · Kubernetes rule resource · Kubernetes cluster PrometheusRule Kubernetes rule resource Prometheus Operator · Select and render config · Kubernetes cluster Prometheus Operator Select and render config Prometheus · Evaluate rules on metrics · Kubernetes cluster Prometheus Evaluate rules on metrics Alertmanager · Group, inhibit and route · Kubernetes cluster Alertmanager Group, inhibit and route Configured receivers · Slack / PagerDuty · Architecture component Configured receivers Slack / PagerDuty Selectors Rule config Alert updates Route and deliver Kubernetes cluster Legend Backend Message bus External

Operator and Prometheus

  • • The Operator selects rules by namespace/labels and renders configuration
  • • Prometheus evaluates those rules against collected metrics
  • • Firing does not prove successful external notification

Explicit delivery policy

  • • Grouping uses configured labels, not automatic root-cause discovery
  • • Inhibition must match the intended entity and scope
  • • Test continue behavior and the final fallback route

Receivers and response policy

  • • This example sends critical alerts to PagerDuty and the selected Slack route
  • • Email and other webhooks require their own integration configuration
  • • Severity and response targets are organization policy, not a built-in SLA