Monitoring

Back in 2016 I wrote a Checkmk notification script that sends messages via a Telegram Bot. Only a few years later I got around and turned it into a real Checkmk package.

After switching to Checkmk 1.6 some months ago, all I had for notifications was email. During my christmas vacation I got notifications via Telegram set up again. As part of the setup I also brought the old code into shape and finally packaged it as a real Checkmk package to make installation easier.

I once installed Checkmk into an existing Nagios installation, back then by using a plain source package. This also meant I had to take care of installing and configuring all dependencies like Apache, Nagios and PNP4Nagios. Keeping this setup working was quite tedious over the last two upgrades (1.2.4 to 1.2.6 and finally 1.2.6p16) so I decided to switch to the official Checkmk CRE packages instead. For now I switched to the rather outdated 1.2.6p16 packages to concentrate on migrating my configuration first.

After a self-inflicted downtime of my server that also happens to handle my email I decided that it’s time to have monitoring notifications delivered out-of-band instead of foolishly trying to send them via the most important resource I monitor.

Since I recently started using Telegram I decided to give it a try for monitoring notifications.

Please note that normal Telegram message contents are unencrypted so they can possibly be read on the Telegram server side!