Prometheus Alertmanager

advertise_address | string

Custom value to be passed to alertmanager at launch via the option "--cluster.advertise-address". In most cases, this is detected automatically and will not be required. However, The cluster.advertise-address flag is required if the instance doesn't have an IP address that is part of RFC 6890 with a default route. The advertise address tells the cluster how to connect back to the node. It should take the format of either "hostname:port" or "ipaddress:port". This field is templatized to accept the following vars: {private_address}, {public_address}, {port}, thus you can use e.g.: juju config alertmanager advertise_address="{public_address}:{port}"

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 config alertmanager external_url="http://{private_address}:{port}/"

extra_peers | string

Comma separated list of additional peers to be passed to alertmanager at launch via the option "--cluster.peer". E.g. "10.10.10.10:9094,10.10.10.11:9094".

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

log-level | string

Loggging level used for alertmanager. Valid values are "error", "warn", "info" and "debug".

nagios_context | string

Default: juju

A string that will be prepended to instance name to set the host name in nagios. So for instance the hostname would be something like: juju-myservice-0 If you're running multiple environments with the same services in them this allows you to differentiate between them.

nagios_servicegroups | string

Default: juju

Comma separated list of nagios servicegroups for the graphite check

pagerduty_description | string

Default: {{ .CommonLabels.cloud_name }} [{{ .Status | toUpper }}{{ if eq .Status "firing" }}:{{ .Alerts.Firing | len }}{{ end }}] {{ .CommonLabels.host }} {{ range .Alerts}}{{.Annotations.summary }} {{ end }}

Template to use for the description of an alert when sent to Pagerduty.

pagerduty_service_key | string

PagerDuty service key

pagerduty_url | string

Override default, use default from alertmanager ( global.pagerduty_url) if unset

port | int

Default: 9093

Alertmanager listening port

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

Default: 30m

If an alert has successfully been sent, wait 'repeat_interval' to resend them.

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

Default: root@localhost

SMTP from

smtp_smarthost | string

Default: localhost:25

SMTP relay

smtp_to | string

Default: root@localhost

Default email recipient for all alerts

snap_channel | string

Default: stable

If install_method is set to "snap" this option controlls channel name. Supported values are: "stable", "candidate", "beta" and "edge"

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