alertmanager/doc/alertmanager-mixin
Björn Rabenstein ce108378d4
Fix and improve AlertmanagerClusterFailedToSendAlerts (#2437)
The alert was just looking at the minimum across integrations. So a
complete failure of one integration would be masked by a still worknig
other integration. With this fix, the `integration` label is retained
(as it was already expected by the `description`), and thus any
failing integration will trigger the alert.

In addition, an `alertmanagerCriticalIntegrationsRegEx` is provided
that allows to mark integrations as critical. Integrations that are
not used to deliver critical alerts, or those that are just there for
auditing and logging purposes can now be configured to only trigger a
warning alert if they fail.

Signed-off-by: beorn7 <beorn@grafana.com>
2020-12-23 15:15:38 +01:00
..
alerts.jsonnet Beginnings of an Alertmanager mixin. (#1629) 2020-12-03 15:57:42 +01:00
alerts.libsonnet Fix and improve AlertmanagerClusterFailedToSendAlerts (#2437) 2020-12-23 15:15:38 +01:00
config.libsonnet Fix and improve AlertmanagerClusterFailedToSendAlerts (#2437) 2020-12-23 15:15:38 +01:00
go.mod Beginnings of an Alertmanager mixin. (#1629) 2020-12-03 15:57:42 +01:00
Makefile Beginnings of an Alertmanager mixin. (#1629) 2020-12-03 15:57:42 +01:00
mixin.libsonnet Beginnings of an Alertmanager mixin. (#1629) 2020-12-03 15:57:42 +01:00
README.md Beginnings of an Alertmanager mixin. (#1629) 2020-12-03 15:57:42 +01:00

Alertmanager Mixin

The Alertmanager Mixin is a set of configurable, reusable, and extensible alerts (and eventually dashboards) for Alertmanager.

The alerts are designed to monitor a cluster of Alertmanager instances. To make them work as expected, the Prometheus server the alerts are evaluated on has to scrape all Alertmanager instances of the cluster, even if those instances are distributed over different locations. All Alertmanager instances in the same Alertmanager cluster must have the same job label. In turn, if monitoring multiple different Alertmanager clusters, instances from different clusters must have a different job label.

The most basic use of the Alertmanager Mixin is to create a YAML file with the alerts from it. To do so, you need to have jsonnetfmt and mixtool installed. If you have a working Go development environment, it's easiest to run the following:

$ go get github.com/monitoring-mixins/mixtool/cmd/mixtool
$ go get github.com/google/go-jsonnet/cmd/jsonnetfmt

Edit config.libsonnet to match your environment and then build alertmanager_alerts.yaml with the alerts by running:

$ make build

For instructions on more advanced uses of mixins, see https://github.com/monitoring-mixins/docs.