# time interval defined in the time_intervals section.
# otherwise acts normally (including ending the route-matching process # When a route is muted it will not send any notifications, but # Additionally, the root node cannot have any mute times. # mute time interval defined in the mute_time_intervals section. # How long to wait before sending a notification again if it has already # are added to a group of alerts for which an initial notification has # How long to wait before sending a notification about new alerts that # more initial alerts for the same group. Allows to wait for an inhibiting alert to arrive or collect # How long to initially wait to send a notification for a group # A list of matchers that an alert has to fulfill to match the node. # A set of regex-matchers an alert has to fulfill to match the node. # A set of equality matchers an alert has to fulfill to match the node. # Whether an alert should continue matching subsequent sibling nodes. # a very low alert volume or your upstream notification system performs This is unlikely to be what you want, unless you have # This effectively disables aggregation entirely, passing through all # To aggregate by all possible labels use the special value '.' as the sole label name, for example: # multiple alerts coming in for cluster=A and alertname=LatencyHigh would # The labels by which incoming alerts are grouped together. None exist), the alert is handled based on the configuration parameters of the If an alert does not match any children of a node (no matching child nodes, or If continue is true on a matching node, theĪlert will continue matching against subsequent siblings. If continue is set to false, it stopsĪfter the first matching child. Its optionalĬonfiguration parameters are inherited from its parent node if not set.Įvery alert enters the routing tree at the configured top-level route, which # A list of time intervals for muting/activating routes.Ī route block defines a node in a routing tree and its children. # A list of mute time intervals for muting routes. # The last component may use a wildcard matcher, e.g. # Files from which custom notification template definitions are read. # This has no impact on alerts from Prometheus, as they always include EndsAt. # not include EndsAt, after this time passes it can declare the alert as resolved if it has not been updated. # ResolveTimeout is the default value used by alertmanager if the alert does # The API URL to use for Slack notifications. # Note that Go does not support unencrypted connections to remote SMTP endpoints. If empty, Alertmanager doesn't authenticate to the SMTP server. # SMTP Auth using CRAM-MD5, LOGIN and PLAIN. # The default hostname to identify to the SMTP server. # Port number usually is 25, or 587 for SMTP over TLS (sometimes referred to as STARTTLS). # The default SMTP smarthost used for sending emails, including port number. They also serve as defaults for other configuration The global configuration specifies parameters that are valid in all otherĬonfiguration contexts. The other placeholders are specified separately.
#WECHAT VERIFICATION SAME REGION PASSWORD#
: a regular string that is a secret, such as a password.: a boolean that can take the values true or false.: a valid path in the current working directory.: a string matching the regular expression *.Generic placeholders are defined as follows: To specify which configuration file to load, use the -config.file flag./alertmanager -config.file=alertmanager.ymlīrackets indicate that a parameter is optional. Sending a HTTP POST request to the /-/reload endpoint. Is not well-formed, the changes will not be applied and an error is logged.Ī configuration reload is triggered by sending a SIGHUP to the process or To view all available command-line flags, run alertmanager -h.Īlertmanager can reload its configuration at runtime. While the command-line flags configure immutable system parameters, theĬonfiguration file defines inhibition rules, notification routing and Command-line flags and a configuration file.
0 kommentar(er)
