Solarwinds Service Desk

From OSNEXUS Online Documentation Site
Revision as of 17:38, 15 March 2022 by Qadmin (Talk | contribs)

Jump to: navigation, search


Solarwinds Service Desk is a cloud based ITSM (IT Service Management) system for IT organizations to manage their support process and ticketing. Quantastor integrates via forward a copy of all alerts that are severity "Error", "Warning", or "Critical". Integration with PagerDuty is done via a webhook URL which must be added to the QuantaStor Alert Manager screen as a new Alert Endpoint.

Step 1 - Generate a JSON Web Token

Login to your Solarwinds Service Desk account then navigate to:

  • Setup* -> *Users & Groups* -> *Users*

Next select a user from the list then under "Actions" choose the option to generate a JSON Web Token. This will be needed in order for QuantaStor to interact with your account to generate *Incidents*.

Step 2 - Add an Integration

QuantaStor integrates with PagerDuty via the "Events API V2" so you'll need to add that integration to the service.

Step 3 - Get the Integration Key

After adding the integration click on the gear icon so that you can view the "Integration Key" which is also known as the "Routing Key" or "Routing Token". It will look something like this:

923c2db8f5384103c09fdf1a9f506162

Step 4 - Add the Endpoint to QuantaStor

Login to your QuantaStor storage grid and then select the "Alert Manager" button to bring up the dialog for adding more alert endpoints. On the second page select "PagerDuty" from the dropdown list of ITSM integrations and then input the URL endpoint.

All PagerDuty endpoints must start with this HTTPS URL as the prefix:

https://events.pagerduty.com/v2/enqueue/

Continuing the example above the full URL endpoint to put into QuantaStor will look like this with the Integration Key at the end:

https://events.pagerduty.com/v2/enqueue/923c2db8f5384103c09fdf1a9f506162

Step 5 - Apply Changes and Test

Apply your changes then use the "Generate Test Alert" button to generate a test alert to verify everything is configured correctly and alerts are making it to PagerDuty. Note that "INFO" level alerts are not sent to the ITSM modules so be sure to generate a "WARNING" or "ERROR" level alert for testing.