Alertmanager Routing Flow

Alertmanager Routing Flow A workflow diagram generated by Archify. 01 / Routing tree · matcher evaluation 02 / Receivers Alert received · enters root route · Routing tree · matcher evaluation Alert received enters root route severity=critical? · match · Routing tree · matcher evaluation severity=critical? match service=foo|bar? · match_re · Routing tree · matcher evaluation service=foo|bar? match_re owner=team-a? · child route · match · Routing tree · matcher evaluation owner=team-a? child route · match critical-receiver · group_wait 10s · Receivers critical-receiver group_wait 10s default-receiver · root route default · Receivers default-receiver root route default team-a · child route receiver · Receivers team-a child route receiver service-team · parent route receiver · Receivers service-team parent route receiver match no match no match match no match match Legend Alert entry Matcher decision Receiver

Example route config on this page

  • • Root route: receiver default-receiver, group_wait 30s, group_interval 5m, repeat_interval 4h
  • • Critical route: match severity=critical, group_wait shortened to 10s
  • • Service route: match_re ^(foo|bar)$ → service-team, nested owner=team-a → team-a