Alertmanager Integration

Lightbend Console can integrate with Prometheus Alertmanager for routing alerts that it generates. Alertmanager is able to route alerts to many different integration points, including Slack, PagerDuty, and others. It can also route based on severity and workload.

For more details on Alertmanager and other alert integration, see:

Note

Console does not provide Alertmanager. Suggested options for installing Alertmanager are the Prometheus Helm Chart and the CoreOS Prometheus Operator.

Configuring

The Helm chart provides a parameter alertManagers for specifying the URLs of your Alertmanager deployments. Add it to your values.yml file:

alertManagers: my-alertmanager-svc:9093
./lbc.py install --namespace=lightbend --version=1.2.5 -- --values=values.yml

Multiple AlertManagers

Prometheus documentation describes how to set up a high-availability cluster of Alertmanagers. Internally, Alertmanager cluster takes care of deduplicating, silencing, and triggering configured behaviours just as if running a single instance. To use such a cluster, you need to provide addresses for all its instances:

alertManagers: my-alertmanager1:9093,my-alertmanager2:9093
./lbc.py install --namespace=lightbend --version=1.2.5 -- --values=values.yml

Example Alertmanager

To get going quickly, you can use the resource files available in the Kubernetes cluster addon repository:

kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/master/cluster/addons/prometheus/alertmanager-configmap.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/master/cluster/addons/prometheus/alertmanager-pvc.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/master/cluster/addons/prometheus/alertmanager-deployment.yaml
kubectl apply -f https://raw.githubusercontent.com/kubernetes/kubernetes/master/cluster/addons/prometheus/alertmanager-svc.yaml

Then configure Console to point to it:

# values.yml
alertManagers: alertmanager.kube-system
./lbc.py install --namespace=lightbend --version=1.2.5 -- --values=values.yml

We don’t recommend this for a production set-up, but it can be useful for testing.