Operations | Monitoring | ITSM | DevOps | Cloud

Icinga Director is a powerful tool that greatly simplifies the configuration, management, and deployment of monitoring objects in Icinga. It provides a user-friendly interface and automation features that make complex setups easier to maintain. Occasionally, though, you may unintentionally introduce a cyclic inheritance while configuring templates. A typical case occurs when a template imports another template that eventually imports the original one again.

Decorators have always been a powerful concept in Icinga Web’s form system — letting developers control how form elements are displayed without hardcoding markup everywhere. But until recently, the decorator system had its limits. The new implementation of form element decorators completely reimagines this approach, offering cleaner logic and better flexibility. In this article, we’ll explore what’s new, why it’s better, and how to use it effectively in your own forms.

Some of you might have already heard about this at OSMC, or you may have received a release notification from GitHub already: our Icinga Notifications project made a step forward and we are happy to announce that version 0.2.0 is now available for you to try out. It addresses feedback that we have received for the previous versions with the most important changes highlighted below.

Go’s os.Root feature, introduced in Go 1.24, is designed to improve filesystem security by restricting operations to a specific directory, making it much harder for attackers to exploit path traversal vulnerabilities.

“Please enter the code we just sent you.” – most people have seen this message when logging into an online service. Two-Factor Authentication (2FA) is no longer reserved for banks or enterprises. It’s now common in email, social media, and shopping accounts. The idea is simple: in addition to a password, you need a second factor so that attackers can’t break in with just one piece of information. But what methods are actually used – and how secure are they really?

As some of you might have already noticed, we recently gave our official Icinga 2 container image builds a complete overhaul. These new images are currently available only as snapshot builds but will replace the existing stable images with the next Icinga 2 v2.16.0 release. In this blog post, we’ll walk you through the key changes and improvements that come with the new images, as well as the reasons behind these changes.

When your Linux system feels sluggish, one of the first things to investigate is the CPU usage. The CPU (Central Processing Unit) is the brain of your machine, and if it’s overloaded, everything else slows down. In this guide, you’ll learn different ways to Linux check CPU usage with command-line tools, how to interpret the metrics, and why automatic monitoring with Icinga ensures long-term system stability.

Why wait for the next poll? An SNMP trap is a real-time alert sent from a device to a monitoring system, without waiting for polling. Ever had a router die silently at 3 AM while your monitoring system was still polling away every 5 minutes? Yeah… not fun. That’s where SNMP traps step in. Think of them as the push notifications of network monitoring: instant, lightweight, and sometimes misunderstood.

Modern IT environments are hybrid, distributed, and constantly growing. To keep them reliable, organizations rely on monitoring that scales, automates, and integrates seamlessly into existing workflows. We collected 24 Icinga customer stories from industries including finance, telecom, manufacturing, and public services. What unites them is the choice of Icinga as a flexible and cost-efficient alternative to proprietary monitoring tools.

Recently I was importing an Icinga configuration for testing purposes. Working with this configuration, I found that there were icon images assigned to the objects. Sadly, those didn’t display, because I didn’t have the icon set installed. So I thought of creating my own.