We are 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.

DevRel is short for Developer Relations. Developer Relations is exactly what it means, a marketing policy that prioritizes relationships with developers. In general society, there is a word known as PR (Public Relations); you could say DevRel is the developer version of this. Its definition is very simple. People who do DevRel often have a technical background, having worked in the industry before switching to their role, but that is not a requirement.

Although Icinga DB has been around for some time and many customers and users are already using it, there may still be some who are wondering how to upgrade/migrate to Icinga DB. This post will briefly explain the components of the Icinga DB and how to install them in a reasonable order. Note that it is assumed that all components are installed on the Icinga primary node(s) using a MySQL/MariaDB database.

We as a company build monitoring software. And we have committed to diversity. It is just logical and consequent for us to apply this principle not only to the people who do the work, but also to the work itself. To the monitoring software we build. Especially to Icinga 2 which, in a perfectly monitored environment, runs on every single machine. I.e. on every single OS powering all those machines.

Recently I came across the Maps module build and maintained by our community. The module displays host objects and annotations on openstreetmap using the JavaScript library leaflet.js. The module reads the coordinates for each host from custom variables and is able to group multiple hosts on the same location. There is already a guide on our blog that describes how you can use the module with human readable locations instead of numeric geolocations.

Today we are happy to announce that after many delays, re-writes, pushbacks and restructuring Icinga for Windows v1.11.0 is finally released! First, we would like to thank everyone for contributing feedback over the past month to track down issues and testing new integrations.

We recently announced the general availability of Icinga 2.14, which most of you might have noticed, and with that in mind, I’d like to show you how you can easily troubleshoot and eliminate some of the dependencies headaches known as the dependency cycle.

We are happy to announce the release of Icinga 2.14.0 and 2.13.8 today. Especially the 2.14.0 release comes with a lot of fixes and improvements and this blog post will highlight the most important ones. There are some breaking changes in 2.14.0, so please make sure to read the corresponding section before upgrading.

Before attending Icinga Berlin in May this year, Daniel Bodky and Markus Opolka from our partner NETWAYS developed the very first Icinga Kubernetes Helm Charts and released it in an alpha version. If you have ever wanted to deploy an entire Icinga stack in your Kubernetes cluster, now is your chance. I also want to highlight Daniel’s talk again on how Icinga can run on Kubernetes and the challenges involved.

It was a nice sunny morning, the weather really with us, for our Icinga Camp Berlin this year. When I peeked outside after helping with the setup, people were already mingling, getting ready to check in and get their first coffee to prepare for the day ahead. Bernd took the stage, welcoming everyone with genuine enthusiasm, setting the tone for what promised to be an engaging event. Surrounded by our community, I felt right at home – ready to dive into the talks and connect with new friends.