Nagios XI

How it works

When a problem meets a specified threshold in Nagios XI, it sends a JSON-formatted webhook to xMatters. A Nagios trigger in xMatters parses the webhook and initiates a flow. The webhook includes essential alert data you can use to enrich notifications to users or when building automated tasks.

Install the workflow

The following instructions describe how to install the workflow through the xMatters one-click installation process.

Go to the Workflow Templates page and click the NagiosXI tile.
On the Set up the Workflow tab, give the workflow a name that identifies its purpose (this must be unique in your instance), add an optional description, and set the default incident type (if applicable). Any built-in Initiate Incident steps in the workflow will automatically be set to the selected incident type.
- You can edit these later, if needed.
Click Next to set up the connection.
Choose the authentication method. A trigger URL is generated based on the selected authentication method..
Copy the trigger URL — you’ll use this to configure the webhook in NagiosXI.
- The trigger URL includes the recipients parameter, which specifies who should be notified. By default, this parameter is set to notify you (the logged in user), but you can set it to target any user or group you want.
Send a test signal to the trigger URL to test the connection.
Click Open Workflow to view and customize the workflow, or Close to return to the Workflows page.

Configure Nagios XI to send requests to the trigger URL

The following instructions describe how to configure Nagios XI to send signals to your triggers.

Nagios Host Notifications

To have Nagios XI send host notifications to the flow trigger, you need to configure a webhook and set it to use the trigger URL.

In Nagios XI go to Configure, and then select Core Config Manager.
Select Commands from the left-hand sidebar.
Click + Add New to add a command.

On the Command Management page fill in the fields with information about the host:

Command Name: notify_xmatters_host

Command Line: Paste the configuration information into the command line based on your preferred authentication type.

URL Authentication: Replace the <URL_FROM_XMATTERS> with the URL you copied from the Nagios Host Notifications trigger.

Copy

curl -X POST -H "Content-Type: application/json" -d ' { "OBJECTTYPE": "HOST", "CONTACTGROUPNAME": "$HOSTDISPLAYNAME$", "HOSTDISPLAYNAME": "$HOSTDISPLAYNAME$", "HOSTNAME": "$HOSTNAME$", "HOSTOUTPUT": "$HOSTOUTPUT$", "HOSTSTATE": "$HOSTSTATE$", "LASTHOSTSTATECHANGE": "$LASTHOSTSTATECHANGE$", "NOTIFICATIONAUTHOR": "$NOTIFICATIONAUTHOR$", "NOTIFICATIONCOMMENT": "$NOTIFICATIONCOMMENT$", "NOTIFICATIONTYPE": "$NOTIFICATIONTYPE$", "SHORTDATETIME": "$SHORTDATETIME$" } ' "<URL_FROM_XMATTERS>"

Basic Authentication: Replace <URL_FROM_XMATTERS> with the URL you copied from the trigger, and username:password with the username and password of the authenticating xMatters user.

Copy

curl -X POST -u username:password -H "Content-Type: application/json" -d ' { "OBJECTTYPE": "HOST", "CONTACTGROUPNAME": "$HOSTDISPLAYNAME$", "HOSTDISPLAYNAME": "$HOSTDISPLAYNAME$", "HOSTNAME": "$HOSTNAME$", "HOSTOUTPUT": "$HOSTOUTPUT$", "HOSTSTATE": "$HOSTSTATE$", "LASTHOSTSTATECHANGE": "$LASTHOSTSTATECHANGE$", "NOTIFICATIONAUTHOR": "$NOTIFICATIONAUTHOR$", "NOTIFICATIONCOMMENT": "$NOTIFICATIONCOMMENT$", "NOTIFICATIONTYPE": "$NOTIFICATIONTYPE$", "SHORTDATETIME": "$SHORTDATETIME$" } '  "<URL_FROM_XMATTERS>"

Command Type: misc command

Add the target names of any recipients you want to notify when the alert fires to the end of the URL.
- For URL authentication, use an ampersand to attach recipients. For example, if you want to notify Emma Pearson and the on-call members in the group responsible for the Antares service, you'd add &recipients=epearson,antares to the URL.
- For other authentication types, use a question mark to attach recipients. For example, if you want to notify Barry Gull and the on-call members in the group responsible for the Cassiopeia service, you'd add ?recipients=bgull,cassiopeia to the URL.
- You must URL-encode any special characters or spaces in the target names.
Click Save.

Now that the host is configured, create a contact to connect the configurations.

Select Contacts from the left-hand sidebar.
Click + Add New to add a new contact.
Give the contact a unique and easy to find name. For example, xMatters.
Go to the Alert Settings tab and set the Manage Host Notification Commands to notify_xmatters_host
Click Save.
Add the xMatters contact to any host definitions that will send alerts to xMatters.

You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use. To test the webhook:

View a host or service you've configured to contact xMatters.
Select the Advanced tab, and then select Send custom notification.
Select Forced, add a comment, then click Submit.
If you do not receive the notification in xMatters, check the Nagios Event Log to ensure the notification was sent.

Nagios Service Notifications

To have Nagios XI send service notifications to the flow trigger, you need to configure a webhook and set it to use the trigger URL.

In Nagios XI, go to Configure, and then select Core Config Manager.
Select Commands from the left-hand sidebar.
Click + Add New to add a command.

On the Command Management page, fill in the following information about the service:

Command Name: notify_xmatters_service

Command Line: Paste the configuration information into the command line based on your preferred authentication type.

URL Authentication: Replace the <URL_FROM_XMATTERS> with the URL you copied from the Nagios Service Notifications trigger.

Copy

curl -X POST -H "Content-Type: application/json" -d ' { "OBJECTTYPE": "SERVICE", "HOSTNAME": "$HOSTNAME$", "CONTACTGROUPNAME": "$SERVICEDISPLAYNAME$", "LASTSERVICESTATECHANGE": "$LASTSERVICESTATECHANGE$", "NOTIFICATIONAUTHOR": "$NOTIFICATIONAUTHOR$", "NOTIFICATIONCOMMENT": "$NOTIFICATIONCOMMENT$", "NOTIFICATIONTYPE": "$NOTIFICATIONTYPE$", "SERVICEDESC": "$SERVICEDESC$", "SERVICEOUTPUT": "$SERVICEOUTPUT$", "SERVICESTATE": "$SERVICESTATE$", "SHORTDATETIME": "$SHORTDATETIME$" } ' "<URL_FROM_XMATTERS>"

Basic Authentication: Replace <URL_FROM_XMATTERS> with the URL you copied from the trigger, and username:password with the username and password of the authenticating xMatters user.

Copy

curl -X POST -u username:password -H "Content-Type: application/json" -d ' { "OBJECTTYPE": "SERVICE", "HOSTNAME": "$HOSTNAME$", "CONTACTGROUPNAME": "$SERVICEDISPLAYNAME$", "LASTSERVICESTATECHANGE": "$LASTSERVICESTATECHANGE$", "NOTIFICATIONAUTHOR": "$NOTIFICATIONAUTHOR$", "NOTIFICATIONCOMMENT": "$NOTIFICATIONCOMMENT$", "NOTIFICATIONTYPE": "$NOTIFICATIONTYPE$", "SERVICEDESC": "$SERVICEDESC$", "SERVICEOUTPUT": "$SERVICEOUTPUT$", "SERVICESTATE": "$SERVICESTATE$", "SHORTDATETIME": "$SHORTDATETIME$" } ' "<URL_FROM_XMATTERS>"

Command Type: misc command

Add the target names of any recipients you want to notify when the alert fires to the end of the URL.
- For URL authentication, use an ampersand to attach recipients. For example, if you want to notify Emma Pearson and the on-call members in the group responsible for the Antares service, you'd add &recipients=epearson,antares to the URL.
- For other authentication types, use a question mark to attach recipients. For example, if you want to notify Barry Gull and the on-call members in the group responsible for the Cassiopeia service, you'd add ?recipients=bgull,cassiopeia to the URL.
- You must URL-encode any special characters or spaces in the target names.
Click Save.

Now that the service is configured, create a contact to connect the configurations.

Select Contacts from the left-hand sidebar.
Click + Add New to add a new contact.
Give the contact a unique and easy to find name. For example, xMatters.
Go to the Alert Settings tab and set the Manage Service Notification Commands to notify_xmatters_service.
Click Save.
Add the xMatters contact to any service definitions that will send alerts to xMatters.

You're ready to use the webhook to trigger automated flows, including steps such as sending alerts and initiating incidents, though we always recommend testing before putting things into use. To test the webhook:

View a service you've configured to contact xMatters.
Select the Advanced tab and select Send custom notification.
Add a comment, then click Submit.
If you do not receive the notification in xMatters, check the Nagios Event Log to ensure the notification was sent.

Set recipients in the trigger URL

The trigger expects the recipients in the trigger URL. When you copy the URL from xMatters, it includes the recipients parameter: recipients=<yourname>. Of course, you don’t want to receive all the alerts.

To change the recipients for alerts from this webhook, swap out your name for the people or groups you want to target.

For URL authentication, use an ampersand to attach recipients. For example, if you want to notify Emma Pearson and the on-call members in the group responsible for the Antares service, you'd add &recipients=epearson,antares to the URL.
For other authentication types, use a question mark to attach recipients. For example, if you want to notify Barry Gull and the on-call members in the group responsible for the Cassiopeia service, you'd add ?recipients=bgull,cassiopeia to the URL.

Remember to URL-encode any special characters, including spaces, in your group names.

We recommend using groups so you can take advantage of the xMatters group features — rotations, escalations, and absences — to reach the right on-call people to jump on an issue.

How to use the workflow

When a condition you've set fires, it sends a signal to xMatters, which creates an alert and notifies the individual or the on-call members of the people or groups you set as recipients in the webhook URL. When the trigger receives a signal saying the issue is resolved, it automatically terminates related alerts in xMatters.

The person responding to the notification has the following response options:

Acknowledge: Acknowledges the notifications and stops escalations.
Escalate: Immediately escalates the alert to the next on-call resolver in a targeted group.
Close: Ends the xMatters alert and stops notifying all targeted recipients.
Initiate Incident: Initiates an incident in xMatters.

Next Steps

Now that you've installed the workflow, you can use it as-is, or customize it to suit your needs better. Here are some examples of things you can add to the workflow to customize it:

Use Slack, Zoom, and Microsoft Teams steps to add collaboration channels to the flow.
Update the message sent to resolvers to include the information most relevant to your team.
Use the Nagios trigger to build your own custom flows.