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.
On the other hand, integrations and cool new ideas are floating in our community channels. My personal highlight this time: A Macbook Pro touchbar status from Icinga, true #monitoringlove shared by noledge.
This month we’d like to welcome our newest Icinga partner: T1 Solutions. The Icinga-as-a-Service NWS platform hosted by our partner NETWAYS now features Icinga 2.9 master and satellites, try it out! Our partner Axxeo shared their insights on deploying Icinga 2 configuration with Ansible (German blog post).
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).
Thanks to the quality feedback from community members and contributors, we’ve analysed and fixed the problem last week. Next to that, Dirk has updated the SELinux policy to allow Systemd notifies, and another fix deals with init script sourcing on non-posix systems.
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. read more…
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.
v2.9.0 contains many bugfixes and improvements requested by Icinga partners and their customers. Our community members have also been reporting and testing quite a bit, especially the nasty bugs with memory leaks on REST API requests are fully resolved.