We’re proud of our many customers and users around the globe that trust Icinga for critical IT infrastructure monitoring. That’s why we’re now showcasing some of these enterprises with their Success stories. It’s stories from companies or organizations just like yours, of any size and different kinds of industries. Some of them are our long-standing customers, others have just recently profited from migrating from another solution to Icinga.

We recently released the beta version of our Notification Web Module, which includes a cool feature that is not yet known to everyone. We named it Desktop Notifications (Browser Push Notifications). With this feature enabled, your browser can send you instant notifications based on your configured event rules—provided you’re logged into Icinga Web.

One of the advantages of the new Icinga Notifications is that it is more loosely coupled to Icinga 2. This is made possible by the concept of sources, each of which is a possible provider of events for Icinga Notifications to act upon. While the most prominent source would be of the “Icinga” type, there is also the “Other” option, which opens up a huge field of different providers via a simple HTTP-based API.

Whether you’re new to Icinga or a seasoned user who thinks they’ve seen it all, some of these resources could surprise you with a few tricks. Let’s dive into the resources that’ll have you saying, “Why didn’t I think of this sooner?” Or send this to someone you would like to rope into the Icinga universe.

If you’re looking for a comprehensive guide to getting started with Icinga, you’re in the right place. Whether you’re new to Icinga or a seasoned user who thinks they’ve seen it all, some of these resources could surprise you with a few tricks. Let’s dive into the resources that’ll have you saying, “Why didn’t I think of this sooner?” Or send this to someone you would like to rope into the Icinga universe.

First of all, if you own a domain, the following text is for you. In production you obviously want to reduce outages. And an outage of a DNS domain as such takes down all services under that domain, no matter whether your LAMP components are all up and running. At least from users’ perspective. As usually, roughly speaking, monitoring has to “play end user” to properly discover failures end-to-end. At best you have an Icinga satellite (e.g.

We at Icinga / NETWAYS (yes, that’s the order) held an internal event recently. It’s name was Knowledge Days and I got to to talk about how I review code. Now, I will share my knowledge with you! Though, this is specifically how I personally perform reviews. This is by no means the definitive way of doing it! Find your own, I can only share my experience. So without further ado…

You want to monitor your infrastructure? Monitoring is essential to ensure system stability, security and optimal performance. Without proper monitoring, small issues can quickly escalate into major problems and affect productivity and service availability. While there is no fixed checklist for infrastructure monitoring and it depends on your setup, there are some key areas that are worth considering when building your own monitoring strategy that fits the needs of your own environment.

In a previous article, Julian provided a comprehensive overview of the characteristics and functionality of Incidents in Icinga Notifications. In today’s blog, I will explain the concept of Incident muting and its underlying mechanisms.

Automating the monitoring process for a huge amount of servers, virtual machines, applications, services, private and public clouds is a main driver for users when they decide to use Icinga. In fact, monitoring large environments is not a new demand for us at all. We experienced this challenge in tandem with many corporations for many years.