Monitoring Traefik 2 with Icinga

Unknown — Wed, 06 May 2020 12:47:00 +0000

Checking if a specific website or web application is alive and well is a classic task of monitoring software. I monitor personal web services with good old Icinga2. Last year I wrote a small Python script that runs on a Icinga2 master or satellite node that queries the Traefik API to automate the generation of Icinga2 rules. For me this was a nice and useful exercise to learn how to use REST APIs together with Python for system administration. In the process of upgrading Traefik 1.7 to 2.0</a> I also had to modify this script.

So without further ado lets jump right in. The way my script works:

It fetches the exposed Traefik Routers with their coresponding hostnames and services and creates Icinga2 apply rules</a> that use the HTTP check</a>. The script is designed to run as a nightly cronjob so that new services that should be monitored are added automatically.

Requirements
#</a> </h3> sudo -u nagios crontab -e </code></pre> Edit and insert nightly cronjob. Something like that should suffice. # Daily at 2am: Generate Icinga checks from Traefik API and restart Icinga2 service 0 2 * * * /etc/icinga2/cronjobs/traefik2_to_icinga.py > /etc/icinga2/zones.d/YOUR-ZONE/traefik_services.conf && systemctl restart icinga2 >/dev/null 2>&1 </code></pre> Note: Of course you need to print the output of traefik2_to_icinga.py</code> to a directory that is either inside your zone or in conf.d The end result should look like this: I am looking forward to any feedback or even pull-requests</a> for the small script. Source for the graphics used in the header: Background vector created by vectorpouch - www.freepik.com</a>

moritzvd.eu - Nagios

Monitoring Traefik 2 with Icinga

Requirements#</a> </h2> A working Traefik v2.x reverse proxy with it's API exposed</li>