As a little introduction for everyone who has not heard about the cube yet: The cube module is there to show statistics grouped by the custom variables that have been set for the hosts and services. They are then displayed in up to three dimensions for a quick overview to show the relations. The most prominent change is the addition of services: While it used to be only possible to have the hosts in a cube, the module has now been extended to provide full functionality with services as well.

After our initial release of Icinga Reporting for early adopters we continued our development and are happy to release v0.9.1 today. The release includes bug fixes and some minor enhancements for the usability. I want to take this opportunity to write a post aimed at the people who are new to the whole reporting shabang – like me. This week I set out to figuring out for myself why one would need to use reporting and how to get there – and to share my new knowledge with you!

In our ongoing efforts to make it easier to automate monitoring environments we recently introduced a new module for Icinga Web 2. This module is first and foremost a platform which lets you have an overview over all the certificates you are using in your environment to prove the identity of your devices. You can take a quick glance or a very detailed look at them.

This release fixes a regression introduced with namespaces in 2.10 where advanced permission filters could result in a crash with many concurrent requests. It also fixes the problem that permission filters are sometimes not applied correctly. Thanks VSHN for sponsoring the development time!

Last week I told Blerim that Icinga came to life on 6.5.2009 … really, 10 years already? A small group of Nagios community members stood up and wanted to create more than a monitoring core with an enhanced web interface. APIs, integrations, backends, scaling, metrics, … A lot of passion and love was received from the community and actually, the Nagios ecosystem became more active again.

We are happy to announce a new bugfix release for Icinga Web 2. Official packages are available on packages.icinga.com. Community repositories might need a while to catch up. You can find issues related to this release on our Roadmap.

I’m not going to list all benefits of automating your monitoring system. If you’re here and reading this, you are most likely very aware that maintaining a large infrastructure is a big challenge. Automating the monitoring process for a huge amount of servers, virtual machines, applications, services, private and public clouds was a main driver for us when we decided to build Icinga 2. In fact, monitoring large environments is not a new demand for us at all.

We’re happy to announce that we released an early version of Icinga Reporting today! With this release we create the foundation for an overall reporting functionality for Icinga by introducing a new way to work with collected data. At the same time we are also publishing the first use case of Icinga Reporting which enables you to calculate, display and export SLA reports for your hosts and services.

This release provides fixes for the InfluxDB and Elasticsearch metric writers. If you’re using TLS connections, the latter were not closed correctly. In addition to these fixes, we’ve also backported fixes for delayed and one-time notifications. Special thanks to mdetrano for being patient and testing this one.

More than 150 monitoring maniacs found their way to the location. For another year Kalkscheune was the venue for the Icinga Camp Berlin. Among those maniacs were many well-known faces, but also surprisingly many new ones. A lot of talks and discussions and besides tasty food, you could also grab an Icinga shirt from the newest collection. As usual the event started with pretzels, coffee and a quick kick off from Icinga CEO Bernd.