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…)
Three years ago we’ve released v2.0.0 – today we are happy to bring you Icinga 2 v2.7.0. This release focusses on stability and performance fixes and enhancements with some new additions such as additional metrics or an NSClient++ API check plugin.
We spent the last weeks and months improving our build system, so we can ship packages better and faster.
Most of the changes are live since Friday last week, new release builds will come out with the upcoming releases. (more…)
Today we are happy to announce version 1.0 of our Icinga Output Plugin for Logstash! It allows you to process check results, send notifications and manage downtimes by calling the Icinga API directly from Logstash. Furthermore, the Icinga output plugin for Logstash can be used in a high available manner, making sure you don’t lose any data. (more…)
We just released another minor bugfix release for Icinga 2. In addition to providing a number of documentation enhancements version 2.6.3 addresses a few bugs. A list of changes can be found here.
Packages for Icinga 2 v2.6.3 for the officially supported distributions should be available shortly.
Today we are happy to announce the release of Icingabeat v1.0!
Beats are lightweight data shippers. They are based on libbeat and written in Go. You install a Beat on your server to collect various data and forward it either to Logstash or directly to Elasticsearch. For example, there is Filebeat to read log files, Metricbeat to fetch metrics from operating systems or Packetbeat to inspect network packets. Icingabeat collects data from the Icinga API. It can open a stream to receive events and simultaneously poll the current status of Icinga 2 periodically.