Director v1.6.0 is available
Icinga Director v1.6.0 has been released with Multi-Instance Support, Configuration Baskets and improved Health Checks. We’re excited to announce new features that will help you to work more efficiently.
Icinga Director v1.6.0 has been released with Multi-Instance Support, Configuration Baskets and improved Health Checks. We’re excited to announce new features that will help you to work more efficiently.
We are pleased to announce the first open source release of our X.509 module for Icinga. The X.509 module for Icinga keeps track of certificates as they are deployed in a network environment. It does this by scanning networks for TLS services and collects whatever certificates it finds along the way. The certificates are verified using its own trust store.
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.
With the TLS connection improvements there was also another bug with hanging TLS connections unveiled. Turns out, this has been sitting there since 2.8.2 and not only affects JSON-RPC cluster connections but also HTTP request sessions, as being used inside the Director kickstart wizard for example. Tom is working on a fix for Director 1.6 in order to support older Icinga 2 versions too.
We’re in OSMC mode in October which typically means that expectations are high, time is limited and everyone is busy preparing talks, demos, implementing new features … but also fixing things. Icinga 2.10 brings support for namespaces, improved TLS connection performance and much more. Community members tackled some bugs already, 2.10.1 is released and 2.10.2 is waiting for test feedback from the snapshot packages.
It’s been a while since the last Vagrant box update and release, so here are the highlights of the past months combined into a new shiny 2.0 release :)
The namespace support in 2.10 caused a regression with the registered global scope being evaluated for API permissions with filters. This release fixes the problem, next to a problem with Windows packages not fully starting up. There’s also a fixed oversight with not setting a default environment constant. This affects setups checking the SNI header in external load balancers.
Our friends from the Max-Planck-Institut for Marine Mikrobiologie kindly sponsored that acknowledgement notifications are now sent only to users which have been notified about a problem before – thanks a lot. Another sponsor asked for more child options for the ScheduledDowntime which are now released in 2.10.
Our first Icinga meetup in Salzburg, Austria is happening this week. Join fellow community members :) OSMC is near, just one month to go …. meet Jan-Piet on MQTT, Claudio as a first-time speaker on container monitoring, Nicolai with infrastructure visualization and Carsten with his “Einhornmagie” :-)
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.