Hands-On Infrastructure Monitoring with Prometheus

route

This is ostensibly the most important configuration section of Alertmanager. In this section, we will define how to group alerts based on their labels (group_by), how long to wait for new alerts before sending additional notifications (group_interval), and how long to repeat them (repeat_interval), but most importantly, which receivers should be triggered for each alert batch (receiver). Since each route can have its own child routes, this forms a routing tree. The top-level route can't have any matching rules as it works like a catch-all for any alert that doesn't match any of its sub-routes. Each setting, except continue, made on a route is carried over to its child routes in a cascading fashion. Although the default behavior is to ...