Icinga 2 v2.7.1 bugfix release

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…)

Vagrant box updates: Elastic Stack, InfluxDB & Icinga Web 2 modules

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.

Monthly Snap August – v2.5, InfluxDB, Contributions

IMG_0330We 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).

Icinga 2 meets InfluxDB

When it comes to monitoring we like to send out a notification as soon as the problem occurs. What’s better than a system that reports a problem the very moment it appears, right? However, we are aware that alerting alone is not always enough. To identify the problem’s root cause it is often necessary to have more information about a service besides its availability state. To meet this claim, most of the monitoring plugins used with Icinga 2 can return performance data. Additionally, the output contains a string showing one or more performance data metrics, for example the time a host or service check took to execute, the number of bytes being transferred, or the free disk space. With the new InfluxDBWriter feature of Icinga 2.5 it’s possible to automatically store this data in an InfluxDB database – without detour. In order to achieve that, the corresponding Icinga 2 object communicates with the native InfluxDB HTTP API. (more…)