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.
I’m glad to announce new minor/patch releases for two Icinga Web modules. We tagged the Icinga Director v1.3.1 on Friday, the Business Process module v2.1.0 followed yesterday.
We’re happy to announce another minor release for Icinga 2. This release only addresses a single bug which can cause Icinga to crash when it’s trying to remove configuration files for objects which were deleted (such as comments and downtimes for hosts and services which don’t exist anymore).
Packages for Icinga 2.6.2 for the officially supported distributions should be available shortly.
We have just released another minor update for Icinga 2. Version 2.6.1 addresses a number of issues we identified in 2.6.0 and is also at the same time the first release after our recent migration to GitHub.
Two of the fixes in this version are for crash bugs which affect reloading Icinga and passing unusually large amounts of command arguments or environment variables to child processes. There are also some documentation changes and a few other smaller bug fixes. Unlike with previous minor releases we decided not to include any ITL changes this time.
An exhaustive list of all tickets solved in 2.6.1 can be found on GitHub. Packages for 2.6.1 should become available shortly.
There’s also a recently-released new version of Icinga Web 2 (2.4.1) which introduces fixes for a few minor problems our users have reported.
Want to visualize part of your IT infrastructure in a hierarchical way? Do you know the Business Impact of single services? What would happen in case you power down a specific server? Would it have any influence on your most important services? If yes, which applications would have been affected? This is what the Icinga Business Process module has been built for. (more…)
It’s been a while since we started developing the new Puppet module. After many hours of development it’s finally here: Icinga 2 Puppet Module v1.0 (more…)