Skip to main content

Integrating Nagios with Faddom

Available from v2026.2

Written by Egor Marachev

Faddom's events integration with Nagios lets you send host and service notifications from Nagios directly into Faddom, so infrastructure events surface alongside your topology data. This article covers the setup for both Nagios Core and Nagios XI.

Nagios Core

Prerequisites

Before you begin, make sure you have the following:

  • Administrator access to Faddom

  • Shell access to the Nagios Core server

  • Permission to edit Nagios Core configuration files

  • A Faddom API access token

  • curl installed on the Nagios Core server

  • Network access from the Nagios Core server to the Faddom WebServices endpoint

Setting up the integration

Follow the steps below to connect Nagios Core to Faddom.

Step by step:

  1. In Faddom, go to Settings and select Events Integrations. Click Add Integration.

  2. In the modal, enter a unique name (such as "Nagios Events"), select Nagios as the type, and click Apply.

  3. In the integration details panel, switch Nagios Edition to Core.

  4. Choose an unused Nagios User Macro number for the Faddom access token, for example 101. Faddom generates faddom_nagios.cfg using that macro (for example, $USER101$). Download faddom_nagios.cfg.

    Note: If you change the User Macro number in Faddom later, download the updated faddom_nagios.cfg and replace the existing file on your Nagios Core server.

  5. Copy the file to the Nagios Core objects directory and set the correct ownership:

    sudo cp faddom_nagios.cfg /usr/local/nagios/etc/objects/faddom_nagios.cfg sudo chown nagios:nagios /usr/local/nagios/etc/objects/faddom_nagios.cfg

    The file defines faddom-notify-host, faddom-notify-service, and faddom-contact. Don't paste the API token into this file. It belongs in resource.cfg.

  6. Open /usr/local/nagios/etc/resource.cfg and add your Faddom API token using the macro number from step 4:

    $USER101$=<FADDOM_API_TOKEN>

  7. Open /usr/local/nagios/etc/nagios.cfg and add the following two lines if they don't already exist:

    cfg_file=/usr/local/nagios/etc/objects/faddom_nagios.cfg enable_environment_macros=1

  8. Add faddom-contact to each host or service definition that should send notifications to Faddom. If a host or service already belongs to a contact group, add faddom-contact to that group instead. This avoids editing each object individually.

    Host example:

    define host {     host_name   example-host     ...     contacts    faddom-contact }

    Service example:

    define service {     host_name            example-host     service_description  DNS Resolution     ...     contacts             faddom-contact }

    Note: The downloaded config file defines the Faddom commands and contact, but it doesn't automatically attach that contact to every monitored host or service. Only add faddom-contact to the hosts and services you want Faddom to receive events from.

  9. The default notification options included in faddom-contact cover standard problem and recovery events:

Type

Options

Host

d (Down), u (Unreachable), r (Recovery)

Service

c (Critical), w (Warning), u (Unknown), r (Recovery)

To also receive flapping notifications, add f to the notification_options in both the host or service definition and the faddom-contact definition.

  1. Validate the configuration, then restart Nagios Core:

    sudo /usr/local/nagios/bin/nagios -v /usr/local/nagios/etc/nagios.cfg sudo systemctl restart nagios

Troubleshooting

If events don't appear in Faddom, work through the following checks:

  • Confirm that faddom_nagios.cfg is referenced in nagios.cfg via cfg_file=

  • Confirm that your token macro (such as $USER101$) is set in resource.cfg

  • Confirm that the Nagios Core server can reach the Faddom endpoint using curl

  • Confirm that faddom-contact is attached to the host or service that triggered the notification

  • Check the Nagios Core log for notification entries

  • Re-run the validation command after any configuration change

Nagios XI

Prerequisites

Before you begin, make sure you have the following:

  • Administrator access to Faddom

  • Administrator access to Nagios XI

  • A Faddom API access token

  • Hosts and services already monitored in Nagios XI

Setting up the integration

Follow the steps below to connect Nagios XI to Faddom.

Step by step:

  1. In Faddom, go to Settings and select Events Integrations. Click Add Integration.

  2. In the modal, enter a unique name (such as "Nagios Events"), select Nagios as the type, and click Apply.

  3. In the integration details panel, switch Nagios Edition to XI.

  4. Choose an unused Nagios User Macro number for the Faddom access token, for example 101. Faddom generates the notification commands using that macro. Use Copy next to the host and service notification commands. You'll need them in step 7.

    Note: If you change the User Macro number in Faddom later, copy the updated notification commands and replace them in Nagios XI CCM.

  5. In Nagios XI, open CCM > User Macros. Set the macro variable you chose (such as $USER101$) to your Faddom API token. Click Update and restart Nagios Core if prompted.

  6. In Nagios XI, open CCM > CCM Admin > Core Configs > General [nagios.cfg], set enable_environment_macros=1, and click Save Changes.

  1. In Nagios XI, open CCM > Commands > Add New and create both notification commands using the values copied from Faddom in step 4:

Field

Host command

Service command

Command Name

faddom-notify-host

faddom-notify-service

Command Line

paste from Faddom

paste from Faddom

Command Type

misc command

misc command

Active

checked

checked

Click Save after each.

[Image: Screenshot of the Nagios XI Command Management screen with the faddom-notify-host command configured.]

  1. In Nagios XI, open CCM > Contacts > Add New. On Common Settings, configure:

    • Contact Username: faddom-contact

    • Alias: Faddom Notifications

    • Email Address: any valid placeholder (such as faddom@example.local)

    • Active: checked

  2. Open Alert Settings on the same contact and configure:

Setting

Value

Host Notifications Enabled

On

Host Notifications Timeperiod

24x7 (or your preferred period)

Host Notification options

Down, Unreachable, Up

Manage Host Notification Commands

faddom-notify-host

Service Notifications Enabled

On

Service Notifications Timeperiod

24x7 (or your preferred period)

Service Notification options

Warning, Unknown, Critical, Ok

Manage Service Notification Commands

faddom-notify-service

Click Save.

  1. For each host that should send notifications to Faddom, open CCM > Hosts, edit the host, and open Alert Settings. Click Manage Contacts, add faddom-contact, set the notification options to Down, Unreachable, and Recovery, and enable notifications. Click Save. If you're assigning the contact to many hosts, Nagios XI's Bulk Modifications Tool can apply this to multiple hosts at once instead of editing them one by one.

  2. For each service that should send notifications to Faddom, open CCM > Services, edit the service, and open Alert Settings. Click Manage Contacts, add faddom-contact, set the notification options to Warning, Critical, Unknown, and Recovery, and enable notifications. Click Save.

  3. Click Apply Configuration in Nagios XI. Once Nagios Core restarts, trigger a test notification to confirm events appear in Faddom.

If you experience any issues or need assistance, contact support@faddom.com.

Related Articles
Did this answer your question?