Icinga supports a variety of third-party tools and plugins. In this article, we’ll review five powerful integrations to supercharge your Icinga deployment.
If you’re at all familiar with monitoring tools, there’s a good chance that you’ve worked with Icinga, a popular open-source solution for monitoring networks, servers and applications. Icinga was initially created as a fork of the Nagios system monitoring application in order to fix some long-standing issues, but has since blossomed into a viable project of its own.
Icinga has received rave reviews from open-source advocates for its flexibility, speed and simplicity. In particular, one of the major advantages of Icinga is its support for a variety of third-party configuration management systems and other tools, available through a straightforward integration process. Here’s a look at five ways that you can leverage the power of integrations to supercharge your Icinga deployment.
1. Chef Icinga Integration
Chef is a popular Ruby-based configuration management solution used by many experienced IT teams to assist with installing and configuring software on a server.
Integration of Icinga and Chef is carried out through a Chef cookbook–the basic unit of configuring nodes on a Chef infrastructure. The cookbook can be used to install and manage either Icinga2 Core or Icinga Web 2 (the web application). It currently works with Icinga 2.2.x and all later versions and requires Chef 11.x or above. In addition, the cookbook can be used for both master and agent nodes and has support for multiple platforms.
Benefits of Chef Integration
Chef is well-known in the DevOps world for its idea of “infrastructure as code,” using Chef recipes to describe how machines should be set up and configured. By integrating Icinga with Chef, managing even hundreds of thousands of servers is a straightforward process by abstracting rules for installation and configuration into cookbooks.
2. Puppet Icinga Integration
Puppet, like Chef, is a popular Ruby-based tool popular for configuration management, although its original purpose was strictly for DevOps. Users can describe system resources in a domain-specific language similar to Ruby.
In order to generate Icinga configuration with Puppet, you first need to make a big decision: will you use Puppet to generate static configuration files for the Icinga master, or will Puppet communicate directly and dynamically with the Icinga Core REST API? If you’ve already invested a lot of time and effort into manually configuring Icinga connections, the first option is probably the better choice.
Benefits of Puppet Integration
Puppet and Icinga can be used to create a powerful symbiotic relationship: Puppet can be used to create most of your Icinga monitoring configuration, while Icinga can monitor your Puppet infrastructure. By setting up the integration ahead of time, you can add new Puppet hosts automatically into your Icinga monitoring system.
3. Elastic Icinga Integration
Previously known as the ELK stack, the Elastic stack is a combination of the tools Elasticsearch, Logsearch, and Kibana into a single powerful solution for data searching, logging and analysis.
Integrating Icinga and Elastic is a relatively simple process by using Beats, lightweight Elastic software that collects data on a server and sends it to the Elastic stack. In particular, Icingabeat is a Beat that collects data from the Icinga API generated by events such as user notifications or downtime.
Benefits of Elastic Integration
By connecting Elastic and Icinga, you can more easily process and visualize data generated during Icinga operations. The data you collect is stored within Elasticsearch and can be displayed visually within the Kibana web interface.
4. PagerDuty Icinga Integration
PagerDuty is an incident resolution platform that collects system alerts and alarms and sends out a signal if it decides that the situation requires human attention.
Accomplishing Icinga integration with PagerDuty can be done with a straightforward Perl-based plugin. Since much of the Nagios code base remains in Icinga, the integration uses PagerDuty’s built-in support for Nagios.
Benefits of PagerDuty Integration
PagerDuty is able to process PROBLEM, ACKNOWLEDGEMENT and RECOVERY messages from Icinga and distribute them to a wider audience via emails, phone calls and SMS messages. If you already use PagerDuty for other applications, integrating it with Icinga should be a no-brainer.
5. Lunovia Icinga Integration
Lunovia is a chatbot plugin that adds the power of instant messaging to your application monitoring solutions.
Like PagerDuty, integration between Icinga and Lunovia is accomplished via an easy and seamless plugin installation, based on the underlying Nagios code base.
Benefits of Lunovia Integration
IT managers and administrators can use Lunovia to be automatically alerted via platforms including Skype for Business and Telegram Messenger. What’s more, they can ask simple queries of the bot in order to get more information about the situation, as well as escalate the event to another user.
Although Icinga has plenty of power all on its own, its utility increases exponentially when used in combination with the third-party tools that you already know and love. Even better, Icinga integrations aren’t limited to the five tools listed here. You can also sync up with popular products like Ansible, Vagrant, Graylog, Graphite and more, making it even easier to incorporate Icinga within your existing network infrastructure.
Need help integrating Icinga with other tools and plugins? Learn more about our Icinga services, support and training