Icinga Blog

Release announcements, development news and monitoring goodies

Icinga Camp San Diego is waiting for you

I’m super excited for next week already – third time flying to the US joining community members at an Icinga Camp, this time San Diego after Portland and San Francisco.

“The Unrealized Role of Monitoring & Alerting” – Jason Hand from VictorOps takes the challenge to dive deep into metrics, alerts and learning from failures. We’ve seen such discussions at Devopsdays Amsterdam in June too and are super excited that Jason joins us in San Diego.

Screen Shot 2016-08-29 at 16.11.23Blerim is also all about metrics – monitor all the things, retrieve metrics and present them in beautiful graphs on your dashboard. Be it Graphite or InfluxDB natively integrated with Icinga 2 or the all new shiny Grafana dashboard we’ve shared on grafana.net.

Rumors do tell that Icinga Web 2 added support for sending commands using the Icinga 2 REST API. Eric will prove that in his talk about new features coming with Icinga Web 2 v2.4.

Yet you’ve been eagerly awaiting a new Icinga Director release. Tom is busy coding and improving it and will showcase the latest and greatest additions – probably firing the last git commit and then starting the talk, as always ;-)

vagrant_icinga2_dashingAnything else all around the Icinga 2 API including live demos of existing tools and a revamped Dashing interface are waiting for you in Michael’s presentation.

Last but not least we’ll also have the latest project news and future outlooks with us – Bernd will kick off the Icinga Camp as always.

Still not convinced? We’ll be sharing the venue with PuppetConf 2016 on next Tuesday. If you love automation, you’ll surely want to learn about Icinga and Puppet all week long :)

Take a peek into all talks and make sure to join us – it is free, a full day of #monitoringlove in lovely San Diego.

read more…

Icinga2 joins Chef Partner Cookbook Program

Today I am happy to announce that Icinga is now part of the Chef Cookbook Program. We were able to get certified with our Icinga2 Cookbook which can be used to install and manage either Icinga2 Core or Icingaweb2. A big shout-out goes to Virender Khatri for maintaining and developing most of this Cookbook.

chef-logoChef is a configuration management software that helps automating the installation and configuration of software on your servers. By turning infrastructure to code Chef makes it possible to abstract installation processes and configurations into Cookbooks.


The Partner Cookbook Program sets guidelines and best practices for cookbook creation and maintenance. By using cookbooks with the partner badge users can be sure that the cookbook has been reviewed and fulfils Chefs quality standards.

NSClient++ 0.5.0, REST API and Icinga 2 integration

Michael Medin released NSClient++ 0.5.0 this week. We’re of course considering to update the bundled NSClient++ installer inside the Windows package.

First things first – the NSClient++ 0.5.0 Changelog mentions breaking changes, so we’ll need to test the ITL CheckCommands still working prior to the next Icinga 2 release (follow #12733). In case you want to help test yourself – you can safely upgrade the NSClient++ application in Windows yourself and fire your Icinga 2 checks against it (just install the new 0.5.0 package).

One cool thing to note about NSClient++ 0.5.0 – it comes with its own web server which also provides a REST API. That could introduce a solution for querying metrics via REST API which require rate calculation (CPU) from a running nscp service. This could be easily integrated into a native Icinga 2 client check plugin then. Let’s just try this out on my Windows 10 VM! :-)

read more…

Timeperiod excludes/includes in Icinga 2 v2.5

You can build simple Icinga 2 setups where everything is checked and notified 24×7. If you are planning with bigger setups and multiple user groups being notified on problems, you’ll certainly get the task to filter specific time ranges or notification types. Or you’ll consider partial check times e.g. when a service is definitely not available and you don’t want your SLA reporting faked with downtimes.

One common thing is to limit the notifications sent to users to “9 to 5”. The configuration requires the following addition:

  • TimePeriod object named “9to5” (available in the example configuration in timeperiods.conf)
  • Referenced as “period” attribute in your Notification object or apply rule

Human beings don’t work 5 days a week and 52 weeks over the whole year. Vacation is needed, finding some rest without any work. And you obviously don’t want to get notified about Icinga problems during that period of time. In addition to that there are several days or hours where no-one wants to get notified except for the 24×7 support (new year’s eve, christmas, etc.).

read more…