Releasing the Icinga Output for Logstash v1.1.0

A couple of months ago we introduced the Icinga Output Plugin for Logstash. Today we’re happy to announce v1.1.0. This release includes functionality to dynamically create objects in Icinga 2 and set their state based on incoming events.

With the first release of the Icinga Output Plugin you could run several actions through the Icinga 2 API. Setting the state of a host or service, add comments, set downtimes and many more that we described in an earlier blogpost. (more…)

Monitoring Windows Clients with Icinga 2 and local NSClient++ checks

Recently I wrote about the changes in NSClient++ 0.5.0 and its REST API capabilities. Icinga 2 bundles the NSClient++ installer and additional check commands in the “nscp-local” namespace for your convenience for a while already now.

The documentation highlights a short example for querying performance counters with the Icinga 2 client as command endpoint and local NSClient++ check plugin calls.

While testing the 0.5.0 integration I’ve also taken the steps of adding service checks for every available check command we have added so far to the Icinga 2 template library. I thought sharing this with you will hopefully generate feedback for documentation updates – how you are currently using NSClient++ in combination with the Icinga 2 client?

(more…)

Icinga 2 and AlertOps – a perfect match

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. (more…)

Automated Monitoring – Icinga meets Foreman

foreman logoAutomated monitoring configuration has many facilities. Some use configuration management software such as Puppet or Chef to deploy their host and service definitions. Others use the Director to import hosts from an existing CMDB and users from Active Directory. Independent from the technique that you use, I am sure we all agree that automated monitoring configuration is a huge benefit.

Today I am pleased to tell you about a new mechanism that came up recently to automate host creation in Icinga. The Foreman is a complete lifecycle management tool for physical and virtual servers. Servers can be installed classically via PXE or by using a cloud provider like Azure or DigitalOcean. You can also easily spawn Docker containers. The Foreman integrates configuration management tools such as Puppet, Chef or Ansible to set up and configure software after the installation. The list of available plugins is endless. (more…)