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.
Additionally, the Windows wizard has been updated and check_perfmon now supports non-localized performance counters. One of our customers sponsored improving mass-creation of downtimes via the REST API in HA enabled clusters, thank you.
Official packages are available on packages.icinga.com, have been pushed to Chocolatey and Raspbian will follow soon. Meanwhile check the changelog for v2.10.4.
We’ve come around several issues with Icinga 2 v2.7.0 and fixed them with this new v2.7.1 release. It also contains other bug fixes requested by Icinga partners and their customer support (Livestatus, DB IDO downtimehistory).
There also was an issue with large configuration files being synced in distributed environments. Aside from the bugfix the configuration sync logs now tell you how many bytes will be synced for better debugging low bandwidth issues. Cluster setups could also run into the problem that the “Downtime End” event was not correctly updated in the IDO database history tables. (more…)
A while back we’ve written about changes inside our Vagrant box demo environments – and many things happened ever since.
There are a couple of new Icinga Web 2 modules directly integrated into the Vagrant boxes (Director, Grafana, Cube, Globe). In terms of metrics and event collecting we’ve integrated Elastic Stack with Icingabeat and also InfluxDB with Grafana. We are happy to release v1.3.0 today.
Couldn’t have said it better – join us in San Diego!
We certainly had a great time over at Icinga Camp Belgrade too … the event archive will be online soon-ish.
We keep working together as an open source community. We’re here to listen what you say – keep it polite and encourage/motivate us to solve your problem with you as best as we can. Lean back and think how others would react if you click “send”, frustrated with an issue tab opened in your browser. Sometimes it doesn’t hurt to just close the tab or rephrase. The person on the other end (dev and/or user) will appreciate it. In the end we all are human beings with emotions, language & culture differences and offline needs (friends, family, hobbies, etc.). What we have in common – we all want to build a great Icinga monitoring product together 🙂
Bernd did a great ignite on that topic with “Working in and with Open Source Communities” at DevOpsDays Amsterdam (video starts at 17:35).