We’ve come a long way with our new release Icinga 2 v2.5. After the 2.4 release in NovemberÂ we’veÂ focussed onÂ fixing many of the remaining bugs. 2.5 isn’t just a feature release – it includesÂ all the bugfixes from the past months.
A big thank you to Simon Murray & DataCentred for contributing the new InfluxDB feature! Dive into the documentation details or just try it out yourself. We’ve also added a new Vagrant box “icinga2x-influxdb” just for Icinga 2, InfluxDB and Grafana 🙂
Don’t want to be notified during the holidays? Add an on-call exclusion for a specific time period? We’re really happy that Philipp Dallig contributed the long awaitedÂ time period exclusion and inclusion feature to Icinga 2. You’ll also find updated examples for specific time ranges in the documentation.
The IDO database feature now supports an incremental config dump. FutureÂ restarts only update what really changedÂ instead of a full config dump.Â This tremendously decreases the database reconnect time on restart making it 10 times (!) faster than before. We’ve tested this with large scale customer environments (Example with 60k services, 2000 clients, 60k dependencies running in an HA cluster).
2.4.10 [2016-08-17 13:06:03 +0200] information/IdoMysqlConnection: Finished reconnecting to MySQL IDO database in 320.08 second(s). 2.5.0 [2016-08-17 14:31:17 +0200] information/IdoMysqlConnection: Finished reconnecting to MySQL IDO database in 29.4937 second(s).
There are two new endpoints added which allow you to fetch global variables (/v1/variables) as well as defined template names (/v1/templates). Notification state and type filters can now be specified as string values (e.g. “OK”).
There’s also a new API action /v1/actions/generate-ticket which allows you to fetch the ticket required for client setups with CSR auto-signing. That way your automated setups will work like a breeze – make sure to check the updated documentation bits too.
We’ve fixed a bug where one faulty client would cause other clients to disconnect. While analysing clusterÂ stability issues we’ve also added more detailed log messages. There is a known issue with messages routing for zones with more than two endpoints – we recommendÂ to only have two endpoints in a zone for now.
Uwe EbelÂ contributed the API/Cluster configuration attributes forÂ the accept cipher listÂ as well as the minimum TLS version – thanks a lot!
We weren’t happy with the documentation chapters explaining how the cluster works and how the Icinga 2 client has to be installed. It was complicated and our community channels were literally flooded with questions. We’ve taken the hard road and purged away the old content.
You’ll now find two new chapters inside the documentation:
- Service Monitoring – a good starting point for plugin integration and more examples based on the numerous CheckCommand definitions (thanks everyone for contributing!).
- Distributed Monitoring with Master, Satellites and Clients – from roles to zones to setup to configuration modes (“top down” and “bottom up”) to scenarios. All doneÂ with real-world examples and newly added images helping you getting your distributed environment going.
The distributed monitoring chapter also explains how to automate your client setup in a Docker client by example. We’ve also made sure to add best practices and advanced hints which we learned from you, our community 🙂
More Release Highlights
- Debian and RHEL packages for vim/nano syntax highlighting.
- DateTime typeÂ for formatting timestamps in the configuration DSL.
- Performance improvementsÂ for config validation.
- Many bugfixes for check execution, notifications, downtimes, etc.
When upgrading your distributed environment ensure to upgrade your master and satellite instances to v2.5 first. Clients using v2.4.x mayÂ still work,Â but should be upgraded as well.
AnÂ IDO database schema update is required (2.5.0.sql). The categories attribute requires the array notation (deprecation warning is logged).
The icinga2.conf file includes plugins-contrib, manubulon, nscp, windows-plugin by default on new installations. This helps deploying checks even more easy but may collide with your own CheckCommands synced in global zones.
Update Icinga 2
Prior to upgrading your production environment you should test the new release in your staging environment as always. Make sure to read the full Changelog.
Note: There was a release critical bug in 2.5.0 so we decided to go for a fixed 2.5.1 release.
Note, 2nd: The notification bug was not fully fixed. Go for 2.5.3 including this fix and one for group members in DB IDO.
Updated packages are available soon.
Special thanks to all contributors and testers making Icinga 2 v2.5 great! Simon, Philipp, Uwe, Rune, Tobias, Blerim, Bernd, Eric, Markus, Hannes, Dirk, Matthias, Emanuel … you know who you are 🙂