Operations | Monitoring | ITSM | DevOps | Cloud

When working with systemd services in Linux, you might encounter situations where multiple instances of a service need to be managed dynamically. When I had to develop a solution to monitor multiple Kubernetes clusters with Icinga for Kubernetes, I ran into exactly this challenge.

The fundamentals of Icinga 2 are check plugins. They are being executed and their return value is mapped to either Host or Service objects. Everything else follows on top. These check plugins can be either from the Monitoring Plugins or custom. While their origin does not matter, they are the building blocks of an Icinga monitoring stack. If a plugin goes CRITICAL, Icinga 2 alerts the sysadmin.

Today we are happy to announce that we released Icinga for Windows v1.13.0 a couple of days ago. We have already talked about the changes coming to v1.13.0 with the beta blog-post last year in more depth, and will focus only on some core changes here.

Icinga is an open-source project, but it’s only become the product we like to use thanks to co-development, brainstorming and suggestions from the community. That’s why we created a platform in the past to facilitate the exchange of custom implementations like check plug-ins, styles, extensions and bridges to third-party systems. We’re talking about our Exchange Portal, of course.