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 run into any issues with this integration, please contact our support.
Congratulations! You’ve now configured SolarWinds NPM to integrate with PagerDuty. Please contact firstname.lastname@example.org with any questions or issues.
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.
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.