May 2019
Intermediate to advanced
442 pages
11h 36m
English
Alertmanager is configured through a single configuration file, and can reload it at runtime without restarting the same way Prometheus does: either sending a SIGHUP to the process or sending an HTTP POST request to the /-/reload endpoint. Such as Prometheus, a malformed configuration will not be applied – an error message will be logged and the alertmanager_config_last_reload_successful metric that's found in its /metrics endpoint will be set to 0.
The configuration file is divided into five top-level sections: global, route, inhibit_rules, receivers, and templates. In the following sections, we'll be exploring each one of them.
Read now
Unlock full access