Last built 1 year ago using go version go1.5.1 linux/amd64 and 178 seconds of time
WARNING: The Alertmanager is still very experimental and early in its development and design. More than any other Prometheus component, it will still undergo frequent breaking changes, including ones that will affect its architecture as a whole. While we do plan on making it mature and stable eventually, use it at your own risk for now.
Alertmanager receives alerts generated by Prometheus and takes care of the following aspects:
Note: Amazon SNS notifications depend on your Amazon credentials being configured as described here.
See config/fixtures/sample.conf.input for an example config. The full configuration schema including a documentation for all possible options can be found in config/config.proto. Alertmanager automatically reloads the configuration when it changes, so restarts are not required for configuration updates.
make ./alertmanager -config.file=/path/to/alertmanager.conf
To make Prometheus send alerts to your Alertmanager, set the
command-line flag on the server:
./prometheus -alertmanager.url=http://<alertmanager-host>:<port> <...other flags...>
Prometheus only pushes firing alerts to Alertmanager. Alertmanager expects to
receive regular pushes of firing alerts from Prometheus. Alerts which are not
refreshed for a period of
-alerts.min-refresh-period (5 minutes by
default) are expired.
Alertmanager only shows alerts which are currently firing and pushed to Alertmanager.
Alertmanager is still in an experimental state. Some of the known caveats which are going to be addressed in the future:
You can deploy the Alertmanager using the prom/alertmanager Docker image.
docker pull prom/alertmanager docker run -d -p 9093:9093 -v $PWD/alertmanager.conf:/alertmanager.conf \ prom/alertmanager -config.file=/alertmanager.conf