SolarWinds Network Performance Monitor Alerts

1. In the Orion Web Console, go to Settings > All Settings > Alerts & Reports > Manage Alerts.
   

   

   
   
2. Choose whether to create a new alert or use an existing one: 
   • To create a new alert click Add New Alert.
   • To use an existing alert, select the check box next to the alert name and click Edit Alert.
     

     

     
     
3. On the Properties tab of the Edit Alert window, click Enabled (On/Off) to enable the alert.
   

   

4. Click Next to continue to the next page of configuration options. For this trigger configuration, the next tab you need is Trigger Actions.
5. On the Trigger Actions tab, click Add Action.
   

   

6. From the list of actions, select Send a GET or POST Request to a Web Server, then click Configure Action.
   

   

7. On the Configure Action window, fill in the following fields: 
   • Name of action: e.g., Triggered Action
   • URL: paste the trigger URL you copied from Flow Designer. 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.
     • You must URL-encode any special characters or spaces in the target names.
   • Select Use HTTP/S POST.
   • Body to POST: Overwrite the default payload with the configuration payload you copied from the SolarWinds NPM Alerts trigger in Flow Designer:
     
   • ContentType: Application/JSON

   

8. Click Add Action.
9. On the Reset Actions tab, click Add Action.
10. From the list, select Send a GET or POST Request to a Web Server.
11. Fill in the following fields:
    • Name of action: e.g., Triggered Action
    • URL: paste the trigger URL you copied from Flow Designer. 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.
    • Select Use HTTP/S POST.
    • Body to POST: Overwrite the default payload with the linked Configuration Payload for the Reset Action in step 12:.
      
    • ContentType: Application/JSON
      
12. On the Summary tab, review your changes and click Submit.
    

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.

Configuration Payload for the Reset Action in step 12:

{
"NodeID" : "${N=SwisEntity;M=NodeID}",
"DisplayName" : "${N=SwisEntity;M=DisplayName}",
"Status" : "${N=SwisEntity;M=Status;F=Status}",
"StatusDescription" : "${N=SwisEntity;M=StatusDescription}",
"PolledStatus" : "${N=SwisEntity;M=PolledStatus}",
"Category" : "${N=SwisEntity;M=Category}",
"Alert" : {
"AlertAction" : "Reset",
"AlertDefID" : "${N=Alerting;M=AlertDefID}",
"AlertActiveID" : "${N=Alerting;M=AlertActiveID}",
"AlertMessage" : "${N=Alerting;M=AlertMessage}",
"AlertName" : "${N=Alerting;M=AlertName}",
"Severity" : "${N=Alerting;M=Severity}",
"AlertTriggerTime" : "${N=Alerting;M=AlertTriggerTime;F=DateTime}",
"AcknowledgeLink" : "${N=Alerting;M=AcknowledgeLink;F=OriginalValue}",
"AlertDetailsUrl" : "${N=Alerting;M=AlertDetailsUrl}"
}
}

The trigger has the following outputs you can use as inputs to steps further along the flow.