Icinga 2 is a feature “monster”. You can do so much more with it than just “check” and “notify”. Forward your performance data into metric systems such as Graphite or InfluxDB, add the IDO database backend for beautiful dashboards in Icinga Web 2 or connect to the REST API and have Dashing present the latest stats in your office.
After all, Icinga 2 runs as an application on your server and will suffer from outages, full disks, load and memory issues and what not. It shouldn’t happen but what if?
We’ve celebrated eight years Icinga in May – hooray!
Currently we are working on Icinga 2 v2.7 to be released in June. This will include certain enhancements for performance and metrics. I’m writing a blog post soon. We are also pushing resources into Icinga Exchange and our new backend. Many things cooking under the hood, and soon to be shared with insights.
One of them is new build infrastructure which has been released this week. Built with Jenkins and Puppet and developed in the open. All involved scripts, modules and a Vagrant test environment can be found on GitHub. You’ll also recognise a new theme on packages.icinga.com :)
Icinga 2 can generate its own alerts when a host or service has reached a certain state (hosts: UP, DOWN, or UNREACHABLE, services: OK, WARNING, CRITICAL, or UNKNOWN). With the right configuration the monitoring software sends out emails, text or instant messages, etc. to users or user groups. (Check out our documentation to learn more about Notification objects.) As soon as you want to organise notifications for more than a few people or several teams with different on-call duties, things can become a bit uncomfortable in Icinga 2. read 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. read more…