Icinga 2 Integration Guide – Agentless

This guide describes how to integrate your Icinga 2 installation with PagerDuty using a simple Perl-based plugin.

Please note that you must be logged in as root to complete the installation. You might need to slightly alter these instructions depending on your exact Linux distribution and your Icinga 2 configuration.

If you are having trouble completing the installation, please contact us.

Looking for Icinga 1? Go here

In PagerDuty

  1. Go to the Services menu and select Service Directory.
  2. On the Services page:
    • If you are creating a new service for your integration, click Add New Service.
    • If you are adding your integration to an existing service, click the name of the service you want to add the integration to. Then click the Integrations tab and click the Add a New Integration hyperlink.
  3. Select your app from the Integration Type menu and enter an Integration Name.If you are creating a new service for your integration, in General Settings, enter a Name for your new service. Then, in Incident Settings, specify the Escalation Policy, Notification Urgency, and Incident Behavior for your new service.
  4. Click the Add Service or Add Integration button to save your new integration. You will be redirected to the Integrations page for your service.
  5. Copy the Integration Key for your new integration.

On Your Icinga 2 Server

    1. Install the necessary Perl dependencies. For Debian, Ubuntu, and other Debian-based distributions:
      apt-get install libwww-perl libcrypt-ssleay-perl libsys-syslog-perl

      For RHEL, Fedora, CentOS, and other Redhat-based distributions:

      yum install perl-libwww-perl perl-Crypt-SSLeay perl-Sys-Syslog
    2. For CentOS 7 users, you must also install an additional dependency:
      yum install perl-LWP-Protocol-https
    3. Download pagerduty-icinga2.cfg from github:
      wget https://raw.githubusercontent.com/mdcollins05/PagerDuty-Icinga2/master/pagerduty-icinga2.conf
    4. Open the file with your text editor (nano, vim, emacs, etc.) and enter the integration key corresponding to your Icinga 2 service into the pager field. The integration key is a 32 character string that can be found on the integration’s detail page.
    5. Move the Icinga 2 configuration file into place:
      mv pagerduty-icinga2.conf /etc/icinga2/conf.d/

Alternatively, if you’re using Icinga’s objects.d configuration:

mv pagerduty-icinga2.conf /etc/icinga2/objects.d/
  1. Add the custom attribute use_pagerduty to your configuration’s host and service configuration objects:
    vars.enable_pagerduty = true # Add this line to hosts/services that will send events to PagerDuty

    Note, the easiest way to do this is to add it to templates that are used by all of your configuration objects. For instance, on Debian-based systems, the default configuration has host objects that use the generic-host template and service objects that use the generic-service template. The templates are defined in /etc/icinga2/conf.d/templates.conf and can be modified as follows:

    template Host "generic-host" {
     max_check_attempts = 5
     check_interval = 1m
     retry_interval = 30s
     check_command = "hostalive"
     vars.enable_pagerduty = true # Add this line
    template Service "generic-service" {
     max_check_attempts = 3
     check_interval = 1m
     retry_interval = 30s
     vars.enable_pagerduty = true # Add this line
  2. If you added the custom attribute to a template in step 6, ensure that the template is used by your host and service objects. For instance, if you added it to the generic-host and generic-service templates, your objects should have one of the following lines:
      import "generic-host" # All host objects should have this line in them
      import "generic-service" # All service objects should have this line in them
  3. Download pagerduty_icinga.pl from github and copy it to /usr/local/bin:
    wget https://raw.github.com/PagerDuty/pagerduty-icinga-pl/master/pagerduty_icinga.pl
    cp pagerduty_icinga.pl /usr/local/bin
  4. Make sure the file is executable by Icinga:
    chmod 755 /usr/local/bin/pagerduty_icinga.pl
  5. Edit the Icinga user’s crontab (Please note: Icinga may run as the nagios user on some systems):
    crontab -u icinga -e
  6. Add the following line to the crontab:
    * * * * * /usr/local/bin/pagerduty_icinga.pl flush
  7. Restart Icinga 2:
    /etc/init.d/icinga2 restart


What if a Icinga event happens while my network is down?

If a PagerDuty server can’t be reached for any reason, events will be stored to an on-disk queue. The installed cron job will attempt to re-send the events at one minute interval.

Since Icinga needs my external Internet connection to send failure reports to PagerDuty, how will I receive notification if our site loses external connectivity?

You should configure an external ping check service like Pingdom to monitor your site’s external connectivity. Of course, you can use PagerDuty to forward alerts from these services.

It doesn’t seem to be working. What’s going on?

Check the Icinga log file for messages containing “pagerduty”. On most systems:

grep -i pagerduty /var/log/icinga2/icinga2.log

Another log to check is the syslog for messages containing “Icinga event”:

grep "Icinga event" /var/log/syslog

Please contact us if you’re unable to sort out the difficulty.

What sort of Icinga messages does PagerDuty understand?

PagerDuty can process PROBLEM, ACKNOWLEDGEMENT, and RECOVERY messages. All other messages, including FLAPPINGSTART and FLAPPINGSTOP, are ignored. If you’d like PagerDuty to process additional Icinga messages, please let us know!

Start Using PagerDuty Today

Try PagerDuty free for 14 days — no credit card required.