Icinga 2 v2.9 introduced performance related changes inside the configuration compilation and activation order. This was to ensure a) no unwanted notifications b) use available CPU resources to speed up the overall validation process. These changes had a bad effect on configuration depending on a specific activation order, and slowed it down with many config objects of a specific type. The Icinga Director depends on get_host() being called in service objects to support specific service set overrides.

Under the hood, Icinga 2 uses many constants and reserved keywords, e.g. “Critical” or “Zone” which are respected by the config parser and compiler. This sometimes leads to errors when users accidentally override such things, or re-define their own global constants. v2.10 introduces namespaces for this purpose, and ensures that such accidents won’t happen anymore.

Our first Icinga Camp Tel Aviv happens on December 17th, 2018, the fourth edition in Berlin takes place on March 14th, 2019 again :) The first Icinga meetup in Salzburg, Austria happens on Oct 12th, 2018 – join for more #icingalove. The Berlin meetup was a great success, Carsten and Lennart joined there too. Watch their meetup group for future dates.

Building your monitoring landscape can be a hard task. The main reason for this is the sheer amount of available solutions. Even though, each of them has their own reason for existence. One challenge during the discovery phase is to find out if the tools you selected can work together. If they have integrations for each other or if they can use the same storage backend. OpenAPM aims to help you find out which parts can work together and how you may use them in combination.

One of the biggest advantages of Icinga is its capability to interact with other tools. Integrations of Icinga cover notification mechanisms, visualisations or automatic deployment. Especially our REST API allows users to easily connect with Icinga, be it for read access or the creation of new objects.The possibility to automate allows Icinga users to monitor highly dynamical infrastructure in private and public clouds.

Stability and user experience were the main goals for this release. Please read the full Changelog for all the details and the Upgrading instructions to be on the safe side. Spoiler: as always, upgrade is safe and super easy.

July brought you new releases for our monitoring core and web frameworks: Icinga 2.9 and Icinga Web 2.6. Both major versions add more awesome features to your monitoring stack. Icinga 2.9.1 was already pushed fixing a problem with non-Systemd platforms, Icinga Web 2.6.1 is coming later this week fixing a regression.

Icinga 2.9.0 provided many many bugfixes and one change has unfortunately been overseen. If you use an init system different to Systemd (e.g. Sysvinit) or the “-d/–daemonize” option in your containers, issue #6445 causes troubles. This is visible with logging, cluster connects, IDO database writing. Users reported problems on CentOS 6, SLES 11, Ubuntu 14, Debian 8, Gentoo (both with Sysvinit).

I’m happy to announce that we released Icinga Web 2.6.0 today! The new version comes with new features that give you a better overview, better auditing and of course bug fixes.

This release comes with Elasticsearch 6 support sponsored by a customer – cheers to Vienna! In addition to this feature, we’ve also taken care of unwanted unknown results on reload with command endpoint clients. Thanks for sponsoring a long lasting issue fix.