.TH PROMETHEUS-ALERTMANAGER "1" "March 2024" "prometheus-alertmanager 0.27.0+ds" "Prometheus"/
.SH "NAME"
prometheus-alertmanager \- the Prometheus alert manager
.SH "SYNOPSIS"
.TP
\fBprometheus-alertmanager [<flags>]\fR

.SH "DESCRIPTION"

.SH "OPTIONS"
.TP
\fB-h, --help\fR
Show context-sensitive help (also try --help-long and --help-man).
.TP
\fB--config.file\fR
Alertmanager configuration file name.
.TP
\fB--storage.path\fR
Base path for data storage.
.TP
\fB--data.retention=120h\fR
How long to keep data for.
.TP
\fB--data.maintenance-interval=15m\fR
Interval between garbage collection and snapshotting to disk of the silences and the notification logs.
.TP
\fB--alerts.gc-interval=30m\fR
Interval between alert GC.
.TP
\fB--web.systemd-socket\fR
Use systemd socket activation listeners instead of port listeners (Linux only).
.TP
\fB--web.listen-address=:9093\fR
Addresses on which to expose metrics and web interface. Repeatable for multiple addresses.
.TP
\fB--web.config.file\fR
Path to configuration file that can enable TLS or authentication. See: https://github.com/prometheus/exporter-toolkit/blob/master/docs/web-configuration.md
.TP
\fB--web.external-url=WEB.EXTERNAL-URL\fR
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.
.TP
\fB--web.route-prefix=WEB.ROUTE-PREFIX\fR
Prefix for the internal routes of web endpoints. Defaults to path of --web.external-url.
.TP
\fB--web.get-concurrency=0\fR
Maximum number of GET requests processed concurrently. If negative or zero, the limit is GOMAXPROC or 8, whichever is larger.
.TP
\fB--web.timeout=0\fR
Timeout for HTTP requests. If negative or zero, no timeout is set.
.TP
\fB--web.ui-path\fR
Path to static UI directory.
.TP
\fB--cluster.listen-address\fR
Listen address for cluster. Set to empty string to disable HA mode.
.TP
\fB--cluster.advertise-address=CLUSTER.ADVERTISE-ADDRESS\fR
Explicit address to advertise in cluster.
.TP
\fB--cluster.peer=CLUSTER.PEER\fR
Initial peers (may be repeated).
.TP
\fB--cluster.peer-timeout=15s\fR
Time to wait between peers to send notifications.
.TP
\fB--cluster.gossip-interval=200ms\fR
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.
.TP
\fB--cluster.pushpull-interval=1m0s\fR
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.
.TP
\fB--cluster.tcp-timeout=10s\fR
Timeout for establishing a stream connection with a remote node for a full state sync, and for stream read and write operations.
.TP
\fB--cluster.probe-timeout=500ms\fR
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.
.TP
\fB--cluster.probe-interval=1s\fR
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.
.TP
\fB--cluster.settle-timeout=1m0s\fR
Maximum time to wait for cluster connections to settle before evaluating notifications.
.TP
\fB--cluster.reconnect-interval=10s\fR
Interval between attempting to reconnect to lost peers.
.TP
\fB--cluster.reconnect-timeout=6h0m0s\fR
Length of time to attempt to reconnect to a lost peer.
.TP
\fB--cluster.tls-config\fR
[EXPERIMENTAL] Path to config yaml file that can enable mutual TLS within the gossip protocol.
.TP
\fB--cluster.allow-insecure-public-advertise-address-discovery\fR
[EXPERIMENTAL] Allow alertmanager to discover and listen on a public IP address.
.TP
\fB--cluster.label\fR
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.
.TP
\fB--enable-feature\fR
Experimental features to enable. The flag can be repeated to enable multiple features. Valid options: receiver-name-in-metrics, classic-mode, utf8-strict-mode
.TP
\fB--log.level=info\fR
Only log messages with the given severity or above. One of: [debug, info, warn, error]
.TP
\fB--log.format=logfmt\fR
Output format of log messages. One of: [logfmt, json]
.TP
\fB--version\fR
Show application version.