Today we are very happy to announce the first beta release of Icinga for Windows with with version 1.13.0.0! This new release provides a huge number of improvements and changes to the Framework as well as the default Windows Plugins, which we will talk about later on.

Over use of dictionaries in monitoring leads to complex and ugly configurations. This in turn makes monitoring complicated. Hence, it is advisable to use it, only if it is needed or in special cases. Even in these cases it is worthwhile to keep it simple. On that note, in this blogpost let me demonstrate how to clone dictionary row entries for objects from import sources to object properties in Icinga Director.

This is a guest blogpost from Dave Kempe from Sol1 At Sol1, we provide services around scaling and automating Icinga rollouts for customers. In large environments, we make heavy use of the excellent distributed monitoring features of Icinga to build redundant clusters across datacenters. Icinga uses the object types of Endpoints and Zones to designate the cluster layout, where a Zone contains Endpoints, and may have a parent Zone. Using this logic, a Zone with no parents is the top level zone.

A few weeks ago, we released the first beta version of the Icinga Notifications Web module. The Configuration tab provides the option to create schedules that can be used as recipients for notifications.

Icinga Notifications and Icinga Notifications Web just celebrated their first beta release. This post will try to help you get started by walking you through the interactive configuration, explaining both the underlying concepts and their actual effects. First, to get an understanding of what Icinga Notifications does, please read both the mentioned blog post and the introduction from the manual carefully.