Operations | Monitoring | ITSM | DevOps | Cloud

This is not just a version bump. Raising the PHP floor allowed us to modernize the IPL codebase in ways that were not possible before: strict type declarations throughout, and a cleaner, more predictable API surface.

A feature that used to work suddenly broke. The problem? There were 300 commits since the last time I knew it worked. Checking each commit manually would take forever. Fortunately, Git has a tool designed exactly for this situation: git bisect.

If you’re running Icinga in a mid-to-large organization, chances are your users and teams are already defined in LDAP or Active Directory. Manually re-creating contacts and contact groups in Icinga Notifications Web is tedious and error-prone, but thankfully, it doesn’t have to be that way. The Icinga Notifications Web REST API gives you everything you need to automate this synchronization. In this post, we’ll walk through how to build a reliable LDAP-to-Icinga sync using the v1 API.

You just finished a long interactive rebase. You hit enter. Your commit history looks… wrong. There is a bunch of things that could go wrong: You could dig through git reflog for 10 minutes. Or you could press Git’s hidden undo button: ORIG_HEAD.

We are happy to announce the release of Icinga Director version 1.11.6. This release addresses several important bug fixes and introduces improvements that enhance the overall stability of Icinga Director.

Last time, we explored the concept of variable scopes in Icinga 2, which help you manage and organize your DSL configurations effectively. As promised, today we’ll dive into another, how shall I say, advanced topic: Namespaces in Icinga 2.

Moving an Icinga 2 master to a new machine requires careful preparation, especially in a master-to-master high availability setup. In production environments, such migrations are often part of broader infrastructure changes, platform standardization, or long-term monitoring strategy decisions. This guide walks you through the process step by step, ensuring a smooth migration without service interruption while keeping your monitoring platform stable and consistent across the environment.

As Bernd mentioned at last year’s OSMC, the Icinga for Windows team was heavy working on v1.14.0 which was going to be released in December. Well, we are off a couple of days, but we believe the wait was worth it!

If you’ve ever onboarded a teammate at 4:57 PM on a Friday (or offboarded one at 4:58 PM… ), you know the pain: keeping notification contacts and groups up to date is work. With the Icinga Notifications REST API, you can automate that and avoid drift.

This article explains how to integrate metrics from Prometheus into Icinga checks using the check_prometheus plugin. There can be multiple reasons why this could be desired: Maybe you have different teams with their own monitoring systems, and you need to bridge the gap, or you want to perform queries that are just better expressed in Prometheus than in plain Icinga check plugins. The latter can be the case if you want to aggregate data from multiple sources or you want to take historic data into account.