This release of the collection will feature a whole set of possibilities to deploy a complete Icinga 2 environment. Before diving deep into the collection, a quick recap of all roles which were available and which are included in the current release v0.3.0. New Roles in v0.3.0 To further enhance the Icinga 2 installation process via Ansible those roles are vital for a successful deployment. The Icinga DB is the future backend of Icinga 2, this can be handled with our icingadb and icingadb_redis roles.

Today we’re announcing the general availability of Icinga DB Web v1.1.0. You can find all issues related to this release on our Roadmap. Please make sure to also check the respective upgrading section in the documentation.

Today we’re announcing the general availability of Icinga Web v2.12.0. You can find all issues related to this release on our Roadmap. Please make sure to also check the respective upgrading section in the documentation.

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.