Your company here ā€” click to reach over 10,000 unique daily visitors

prometheus-alertmanager - Man Page

The Prometheus alert manager


prometheus-alertmanager [<flags>]



-h, ā€‰--help

Show context-sensitive help (also try --help-long and --help-man).


Alertmanager configuration file name.


Base path for data storage.


How long to keep data for.


Interval between garbage collection and snapshotting to disk of the silences and the notification logs.


Interval between alert GC.


Use systemd socket activation listeners instead of port listeners (Linux only).


Addresses on which to expose metrics and web interface. Repeatable for multiple addresses.


Path to configuration file that can enable TLS or authentication. See: https://github.com/prometheus/exporter-toolkit/blob/master/docs/web-configuration.md


The URL under which Alertmanager is externally reachable (for example, if Alertmanager is served via a reverse proxy). Used for generating relative and absolute links back to Alertmanager itself. If the URL has a path portion, it will be used to prefix all HTTP endpoints served by Alertmanager. If omitted, relevant URL components will be derived automatically.


Prefix for the internal routes of web endpoints. Defaults to path of --web.external-url.


Maximum number of GET requests processed concurrently. If negative or zero, the limit is GOMAXPROC or 8, whichever is larger.


Timeout for HTTP requests. If negative or zero, no timeout is set.


Listen address for cluster. Set to empty string to disable HA mode.


Explicit address to advertise in cluster.


Initial peers (may be repeated).


Time to wait between peers to send notifications.


Interval between sending gossip messages. By lowering this value (more frequent) gossip messages are propagated across the cluster more quickly at the expense of increased bandwidth.


Interval for gossip state syncs. Setting this interval lower (more frequent) will increase convergence speeds across larger clusters at the expense of increased bandwidth usage.


Timeout for establishing a stream connection with a remote node for a full state sync, and for stream read and write operations.


Timeout to wait for an ack from a probed node before assuming it is unhealthy. This should be set to 99-percentile of RTT (round-trip time) on your network.


Interval between random node probes. Setting this lower (more frequent) will cause the cluster to detect failed nodes more quickly at the expense of increased bandwidth usage.


Maximum time to wait for cluster connections to settle before evaluating notifications.


Interval between attempting to reconnect to lost peers.


Length of time to attempt to reconnect to a lost peer.


[EXPERIMENTAL] Path to config yaml file that can enable mutual TLS within the gossip protocol.


[EXPERIMENTAL] Allow alertmanager to discover and listen on a public IP address.


The cluster label is an optional string to include on each packet and stream. It uniquely identifies the cluster and prevents cross-communication issues when sending gossip messages.


Experimental features to enable. The flag can be repeated to enable multiple features. Valid options: receiver-name-in-metrics, classic-mode, utf8-strict-mode


Only log messages with the given severity or above. One of: [debug, info, warn, error]


Output format of log messages. One of: [logfmt, json]


Show application version.


alertmanager, version 0.27.0