The post How to Monitor Windows with Icinga appeared first on Icinga.

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. What Is Icinga Notifications, Anyway? Before we dive in, a quick primer. Icinga Notifications is a dedicated component that sits alongside your existing Icinga 2 setup and takes over the entire notification lifecycle. Rather than relying on Icinga 2’s built-in (and somewhat limited) notification system, Icinga Notifications receives state change events from your monitored infrastructure, decides whether to open an incident, and then routes alerts to the right people through the right channels: email, Rocket.Chat, webhooks, and more. The web frontend, Icinga Notifications Web, is where all the configuration lives: contacts, contact groups, escalation rules, schedules, and channel setup. Critically for us, it also exposes a REST API that lets you manage contacts and contact groups programmatically, which is exactly the hook we […]

The post Syncing LDAP Users & Groups with the Icinga Notifications Web API appeared first on Icinga.

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: messed up an interactive rebase accidentally ran git reset –hard merged the wrong branch rebased onto the wrong base You could dig through git reflog for 10 minutes. Or you could press Git’s hidden undo button: ORIG_HEAD.   What is the Git HEAD Before we look at special HEADs, we first need to understand what HEAD actually is. The HEAD is a special pointer that tells Git where you currently are in the repository. Most of the time, HEAD points to the current branch, and that branch points to the latest commit on it. When you make a new commit, the branch moves forward and HEAD moves with it. HEAD → current branch → latest commit In short: HEAD = the commit you’re currently working on. If you check out a specific commit instead of a branch, HEAD points directly to that commit – this is called a detached HEAD.   My old recovery strategy Whenever I messed up a rebase, my rescue plan always started the same way: git reflog The output could look like […]

The post How to undo Git reset hard? appeared first on Icinga.

The post Icinga Partnering in Action: The Shadow-Soft Success Story appeared first on Icinga.

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. Database Schema Upgrade Columns storing large strings for example custom variables are upgraded to MEDIUMTEXT in MYSQL Changes are made to support Dependency Redundancy Groups UI Enhancements This update resolves the below issues in UI: The applied groups displayed for hosts that was not in the restriction Incorrect displayed associated templates for the Host Choices Inherited “disabled” services not crossed out Cyclic inheritance causes UI to crash Clicking Groups repeatedly (x2) leads to “Page not found” Users with Director restrictions unable to create hosts unless you manually specify the host group Indexing of the stripped filter chain And provides the below improvements in UI: Support for ‘Dependency Redundancy Groups’ Show an indicator if there is an active deployment is running Kickstart Improvements With this release, the Icinga Director can now correctly remove the zones and endpoints while running Kickstart. CLI Improvements It is now possible to check the health of individual sync rules, import sources, and director jobs by name. Moreover, you could also delete individual sync rule or import […]

The post Icinga Director v1.11.6 Release appeared first on Icinga.

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.   What are Namespaces? If you’ve worked with programming languages like C++ or C#, you might be familiar with the concept of namespaces. In Icinga 2, namespaces serve a similar purpose. They allow you to group related functions or/and variables together, preventing naming conflicts. Think of DSL namespaces as containers that encapsulate your functions and variables. You can find them everywhere in Icinga 2 DSL, even if you don’t explicitly define them. I even dare to say that you’re already using them in your daily Icinga 2 work, ehm, ehm, I mean, without even realizing it! If you did realize it, kudos to you buddy 👏. For those who haven’t, don’t worry, you’ll get the hang of it in no time. Icinga 2 has numerous built-in namespaces like System, Icinga, Types etc. that are exposed to you in the DSL. Did you ever wonder how Icinga 2 knows where to find the Host or Service object types? That’s right, it’s because […]

The post Understanding Namespaces in Icinga 2 DSL appeared first on Icinga.

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. Moving an Icinga 2 master to a new machine requires careful preparation, especially in a master-to-master setup. This guide walks you through the process step by step, ensuring a smooth migration without service interruption.   Prepare the New Master Before starting the migration, prepare your new server by installing Icinga 2 with the desired version. Verify that the installation works as expected, including network connectivity to your database server and both existing master nodes. Once you verified everything is working, ensure that Icinga 2 is stopped on the new server. You will start Icinga 2 once all the data from the existing server is copied. It’s best to migrate one master at a time. Start with the master that holds the Certificate Authority (CA). You can identify the CA master by checking for files […]

The post How to Migrate an Icinga 2 Master in a High Availability Setup appeared first on Icinga.

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!   Security Update Let’s first get the elephant out of the room: The previously released security update for Icinga for Windows is of course also part of v1.14.0. If you haven’t seen the security release yet or were unable to update until now, you can upgrade directly to v1.14.0 to fix the issue.   Stability Improvements and Bugfixes With the new version v1.14.0, we have fixed plenty of issues, starting from smaller issues with check execution to larger issues targeting installation failures or metric over time not collecting data. You can have a look on all the changes on the public Framework changelog and the plugins changelog.   Hashing Algorithm Starting with Icinga for Windows v1.14.0, we fully got rid of MD5, which we previously used to determine if the binary of the Icinga for Windows service has the intended signature. We have now moved to SHA256 for this case. This not only improves reliability but also ensures that […]

The post Releasing Icinga for Windows v1.14.0 – We have been cooking! appeared first on Icinga.

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. That’s why I’m happy to introduce the first release of the Contacts / Contact Groups REST API in Icinga Notifications Web: a small, focused API that helps you keep “who gets notified” consistent, automated, and version-controlled. Whether you want to sync from an HR system, a CMDB, an IdP, or just a Git repo with YAML and a CI job, this API is meant to be the glue.   What this API is (and isn’t) This REST API is designed specifically for notification configuration: Manage contacts (create, read, update, delete) Manage contact groups (create, read, update, delete) Read available notification channels (read-only; discovery) OpenAPI specification included (so you can generate clients and stop hand-writing curl in your sleep) It’s not trying to be a “do everything” endpoint for the whole notifications universe—just the core primitives you need for automation: contacts and groups.   Use cases: why you’ll care There are several practical scenarios where […]

The post Sync Your Users Into Icinga Notifications: Introducing the Contacts/Groups API appeared first on Icinga.

Toady, we are releasing multiple new versions of Icinga 2 and Icinga for Windows, all of them fixing a file permission issue present in all installations on Windows. Impact The following paths were created without setting proper permissions, allowing all local users to read their contents: C:\ProgramData\icinga2\var created and used by Icinga 2. It contains the endpoint certificate and corresponding private key, synced configuration, and persisted state information. This was assigned CVE-2026-24413. C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate created and used by Icinga for Windows. It contains a certificate bundle including a private key. This was assigned CVE-2026-24414. In case your Windows installation uses non-standard paths, these folders may exist at different locations. Patches The following fixed versions were released: Icinga 2: v2.15.2, v2.14.8, and v2.13.14 Icinga for Windows: v1.13.4, v1.12.4, and v1.11.2 The permissions of an existing Icinga 2 agent installation managed by Icinga for Windows will automatically be fixed by these new versions of Icinga for Windows without needing to update the Icinga 2 agent itself. Additional Changes in Icinga 2 All three new releases of Icinga 2 also update the bundled OpenSSL version to 3.0.19, though based on our assessment, none of the fixed vulnerabilities there affects Icinga. Icinga 2 v2.15.2 […]

The post Releasing Icinga 2 v2.15.2, v2.14.8, v2.13.14 and Icinga for Windows v1.13.4, v1.12.4, v1.11.2 appeared first on Icinga.

Introduction 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. For this, we will take a look at the check_prometheus plugin developed and maintained by NETWAYS. Installation For using check_prometheus with Icinga, two parts are needed: the check binary itself as well as a CheckCommand definition making the command known to Icinga. A check_prometheus binary can be obtained multiple ways, pick the method that best fits your needs: The GitHub Releases of check_prometheus include pre-built binaries for different operating systems and architectures. Download and install the desired file to an appropriate location, for example /usr/lib/nagios/plugins/check_prometheus. NETWAYS provides software repositories for various deb- and rpm-based Linux distributions from which their check plugins can be installed. check_prometheus is provided in the package netways-plugins-prometheus. If a […]

The post Integrating Prometheus Metrics into Icinga Using check_prometheus appeared first on Icinga.