prometheus alertmanager #17
Description
The Alertmanager handles alerts sent by client applications such as the
Prometheus server. It takes care of deduplicating, grouping, and routing
them to the correct receiver integration such as email, PagerDuty,
or OpsGenie. It also takes care of silencing and inhibition of alerts.
- Tags:
- monitoring ›
Juju prometheus alertmanager charm
This charm provides the Prometheus alertmanager, part of the Prometheus monitoring system
The charm should be realted to the prometheus charm
Configuration
Common configuration options are:
- external_url
- repeat_interval
The charm supports many differnet notification mechanisms. For example
to enable email notifications set the following options:
- smtp_smarthost
- smtp_from
- smtp_to
To send notifications to PagerDuty set:
- pagerduty_service_key
For more information about supported notification methods and other
configuration options refer to the config.yaml help
Configuration
- external_url
- (string) 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. It's templatized to accept the following vars: {private_address}, {public_address}, {port}, thus you can use e.g.: juju set alertmanager external_url="http://{private_address}:{port}/"
- extra_receivers
- (string) YAML string containing a list of alertmanager 'receivers' to add
- extra_routes
- (string) YAML string containing a list of alertmanager 'routes' to add
- pagerduty_service_key
- (string) PagerDuty service key
- pagerduty_url
- (string) Override default, use default from alertmanager ( global.pagerduty_url) if unset
- port
- (int) Alertmanager listening port
- 9093
- raw_config
- (string) Alertmanager configuration in yaml format. If you set this option all options except "snap_channel", "port" and "external_url" will be ignored. This is intended for advanced use cases only, for example multiple receivers with complex routing and inhibition rules.
- repeat_interval
- (string) If an alert has successfully been sent, wait 'repeat_interval' to resend them.
- 30m
- slack_api_url
- (string) Your slack.com Webhook URL, see https://api.slack.com/incoming-webhooks (required)
- slack_channel
- (string) slack channel (required)
- smtp_from
- (string) SMTP from
- root@localhost
- smtp_smarthost
- (string) SMTP relay
- localhost:25
- smtp_to
- (string) Default email recipient for all alerts
- root@localhost
- snap_channel
- (string) If install_method is set to "snap" this option controlls channel name. Supported values are: "stable", "candidate", "beta" and "edge"
- stable
- snap_proxy
- (string) DEPRECATED. Use snap-http-proxy and snap-https-proxy model configuration settings. HTTP/HTTPS web proxy for Snappy to use when accessing the snap store.
- snap_proxy_url
- (string) DEPRECATED. Use snap-store-proxy model configuration setting. The address of a Snap Store Proxy to use for snaps e.g. http://snap-proxy.example.com
- snapd_refresh
- (string) How often snapd handles updates for installed snaps. The default (an empty string) is 4x per day. Set to "max" to check once per month based on the charm deployment date. You may also set a custom string as described in the 'refresh.timer' section here: https://forum.snapcraft.io/t/system-options/87
- webhook_url
- (string) Your webhook url