1prometheus-alertmanager(1) 0.23.0 prometheus-alertmanager(1)
2
3
4
6 prometheus-alertmanager - The Prometheus alert manager
7
9 prometheus-alertmanager [<flags>]
10
11
14 -h, --help
15 Show context-sensitive help (also try --help-long and --help-
16 man).
17
18 --config.file="/etc/prometheus/alertmanager.yml"
19 Alertmanager configuration file name.
20
21 --storage.path="/var/lib/prometheus/alertmanager/"
22 Base path for data storage.
23
24 --data.retention=120h
25 How long to keep data for.
26
27 --alerts.gc-interval=30m
28 Interval between alert GC.
29
30 --web.config.file=""
31 [EXPERIMENTAL] Path to configuration file that can enable TLS or
32 authentication.
33
34 --web.external-url=WEB.EXTERNAL-URL
35 The URL under which Alertmanager is externally reachable (for
36 example, if Alertmanager is served via a reverse proxy). Used
37 for generating relative and absolute links back to Alertmanager
38 itself. If the URL has a path portion, it will be used to prefix
39 all HTTP endpoints served by Alertmanager. If omitted, relevant
40 URL components will be derived automatically.
41
42 --web.route-prefix=WEB.ROUTE-PREFIX
43 Prefix for the internal routes of web endpoints. Defaults to
44 path of --web.external-url.
45
46 --web.listen-address=":9093"
47 Address to listen on for the web interface and API.
48
49 --web.get-concurrency=0
50 Maximum number of GET requests processed concurrently. If nega‐
51 tive or zero, the limit is GOMAXPROC or 8, whichever is larger.
52
53 --web.timeout=0
54 Timeout for HTTP requests. If negative or zero, no timeout is
55 set.
56
57 --cluster.listen-address="0.0.0.0:9094"
58 Listen address for cluster. Set to empty string to disable HA
59 mode.
60
61 --cluster.advertise-address=CLUSTER.ADVERTISE-ADDRESS
62 Explicit address to advertise in cluster.
63
64 --cluster.peer=CLUSTER.PEER
65 Initial peers (may be repeated).
66
67 --cluster.peer-timeout=15s
68 Time to wait between peers to send notifications.
69
70 --cluster.gossip-interval=200ms
71 Interval between sending gossip messages. By lowering this value
72 (more frequent) gossip messages are propagated across the clus‐
73 ter more quickly at the expense of increased bandwidth.
74
75 --cluster.pushpull-interval=1m0s
76 Interval for gossip state syncs. Setting this interval lower
77 (more frequent) will increase convergence speeds across larger
78 clusters at the expense of increased bandwidth usage.
79
80 --cluster.tcp-timeout=10s
81 Timeout for establishing a stream connection with a remote node
82 for a full state sync, and for stream read and write operations.
83
84 --cluster.probe-timeout=500ms
85 Timeout to wait for an ack from a probed node before assuming it
86 is unhealthy. This should be set to 99-percentile of RTT (round-
87 trip time) on your network.
88
89 --cluster.probe-interval=1s
90 Interval between random node probes. Setting this lower (more
91 frequent) will cause the cluster to detect failed nodes more
92 quickly at the expense of increased bandwidth usage.
93
94 --cluster.settle-timeout=1m0s
95 Maximum time to wait for cluster connections to settle before
96 evaluating notifications.
97
98 --cluster.reconnect-interval=10s
99 Interval between attempting to reconnect to lost peers.
100
101 --cluster.reconnect-timeout=6h0m0s
102 Length of time to attempt to reconnect to a lost peer.
103
104 --log.level=info
105 Only log messages with the given severity or above. One of: [de‐
106 bug, info, warn, error]
107
108 --log.format=logfmt
109 Output format of log messages. One of: [logfmt, json]
110
111 --version
112 Show application version.
113
114
115
116version alertmanager, prometheus-alertmanager(1)