Operations | Monitoring | ITSM | DevOps | Cloud

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.

If you want to get started with Icinga but don’t have a data center lying around, no worries. Icinga is a lightweight monitoring tool that works for both large infrastructures and small home labs. When I first explored Icinga during my first year as an apprentice, it was also my first real contact with monitoring tools. After completing the Icinga Fundamentals training, I wanted to experiment with hosts and services, but what should I monitor?

Icinga is designed to be a highly dynamic monitoring software that can monitor your setup, regardless of its architecture. While most setups are hierarchical and fit well into the master, satellites, and agents scheme with different zones, it is sometimes impractical or impossible to create one large Icinga 2 cluster. Imagine that you are responsible for only some hosts within another organization.

If you’ve ever muted your phone during a maintenance window, only to miss a real outage an hour later, you’re not alone. Sysadmins on Reddit and beyond often describe feeling like they’re drowning in alerts: So many notifications that the important ones lose their meaning. This is alert fatigue, sometimes called notification fatigue or incident noise, and it’s one of the most common challenges in modern, growing IT operations.