Book Image

The DevOps 2.2 Toolkit

By : Viktor Farcic
Book Image

The DevOps 2.2 Toolkit

By: Viktor Farcic

Overview of this book

Building on The DevOps 2.0 Toolkit and The DevOps 2.1 Toolkit: Docker Swarm, Viktor Farcic brings his latest exploration of the Docker technology as he records his journey to explore two new programs, self-adaptive and self-healing systems within Docker. The DevOps 2.2 Toolkit: Self-Sufficient Docker Clusters is the latest book in Viktor Farcic’s series that helps you build a full DevOps Toolkit. This book in the series looks at Docker, the tool designed to make it easier in the creation and running of applications using containers. In this latest entry, Viktor combines theory with a hands-on approach to guide you through the process of creating self-adaptive and self-healing systems. Within this book, Viktor will cover a wide-range of emerging topics, including what exactly self-adaptive and self-healing systems are, how to choose a solution for metrics storage and query, the creation of cluster-wide alerts and what a successful self-sufficient system blueprint looks like. Work with Viktor and dive into the creation of self-adaptive and self-healing systems within Docker.
Table of Contents (18 chapters)

Integrating Alertmanager with Jenkins

At the moment, we are running Alertmanager configured in the previous chapter. It creates a Slack notification on all alerts. Let's try to change it so that alerts trigger a remote invocation of the Jenkins job service-scale.

Since Alertmanager configuration is stored as a Docker secret and they are immutable (we cannot update them), we need to remove the service and the secret and create them again.

docker service rm monitor_alert-manager

docker secret rm alert_manager_config

Let us define a Slack config that will send build requests to the service-scale job. The command that creates the service with the configuration is as follows.

echo "route:
group_by: [service]
repeat_interval: 1h
receiver: 'jenkins-go-demo_main'

receivers:
- name: 'jenkins-go-demo_main'
webhook_configs:
- send_resolved: false
...