SolarWinds NPM Integration Guide

SolarWinds Network Performance Monitor (NPM) is a powerful network fault and availability management system that makes it easy to quickly detect, diagnose, and resolve performance issues before outages occur. SolarWinds NPM tracks response time, availability, uptime of routers and displays performance statistics in real time, and notifies users when something goes awry. PagerDuty and SolarWinds NPM work together to provide better incident alerting and easy-to-manage on-call schedules to SolarWinds’ network monitoring. PagerDuty alerts can be sent by a wide breadth of contact methods to ensure quick and reliable responses.

This guide will walk you through the process of integrating SolarWinds NPM with PagerDuty. If you are using SolarWinds NPM version 11.5 or newer, you should use this guide instead. If you run into any issues with this integration, please contact our support.

In PagerDuty:

  1. Login to your PagerDuty account, and select Services > Add New Service.Add PagerDuty Service
  2. Enter a service name and select an escalation policy.
  3. Start typing “SolarWinds” under “Integration Type” to filter your choices. Then, click the Add Service button.SolarWinds

In SolarWinds NPM:

  1. From your Solarwinds NPM server, login to your PagerDuty account.  Go to the SolarWinds NPM service that you just created and download the VB Script, Trigger Action and Reset Action files.
  2. Move the action.vbs files you have just downloaded to C:\Program Files\PagerDuty\your-service-key\action.vbs.
  3. Open the Advanced Alert Manager (Start > Programs > SolarWinds Orion > Alerting, Reporting, and Mapping > Advanced Alert Manager).
  4. Either select an existing alert or create a new alert.  If configuring a new alert, set up the Alert Name, Trigger Condition and Reset Condition fields.
  5. Go to the Trigger Actions tab.  Click on Import Actions.Import Trigger Action
  6. Select the Trigger.AlertActions file and click Open.Select Trigger Action
  7. Go to the Reset Actions tab.  Click on Import Actions.Import Reset Action
  8. Select the Reset.AlertActions file and click on Open.Select Reset Action
  9. Click on OK to save your alert.
  10. If you would like to test your alert, select it from the list and click on the Test button.Test Alert
  11. Select a node for the test, and then click on Test Alert Trigger.test_trigger_alertIt takes a moment for the test to initialize, but you will get an alert within PagerDuty.Triggered PagerDuty Incident
  12. You can now run a test to clear the alert, so click on the Clear Alert Test button and then click on the Test Alert Reset button.Test Reset AlertThe incident within PagerDuty will now resolve.Resolved PagerDuty Incident

Congratulations! You’ve now configured SolarWinds NPM to integrate with PagerDuty. Please contact with any questions or issues.


How do I setup SolarWinds NPM to use multiple PagerDuty services?

In order to tie SolarWinds NPM to multiple PagerDuty services, you will repeat all of the steps of this guide.  The only things that you will do differently are that you will create multiple services within PagerDuty, download the new actions and vbscripts for each, and use those for your alerts within SolarWinds NPM.

Can I customize the message that I receive from SolarWinds & PagerDuty?

Yes, you can customize the message that is sent to you.  If you feel comfortable editing VBScript, you can edit the action.vbs VBScript script you’ve downloaded to send different information to PagerDuty.You can modify the SolarWinds Macros passed in by loading up the Advanced Alert Manager and going to the alert you would like to edit. Go to the Trigger Actions or Resolve Actions tab, and double click on the PagerDuty action. From here you can edit the passed in Macros by altering the command line. Separate any arguments with the section sign (U+00A7) unicode symbol, like the existing arguments. This is required so that any argument can contain spaces and quotes, your arguments should not contain the section sign unicode symbol. Avoid using the file picker as this will remove all of the command line arguments.   The full list of available macros can be found here.If you would like to change how your incidents are de-duplicated, you can modify the incident_key as well, from within the action.vbs VBScript.

All Our Integration Guides