...
In SolarWinds NPM, go to Settings > Manage Alerts > Alert Manager.
Select Add New Alert.
Set alert properties as needed.
Provide information about the alert, including its name, severity, how frequently to evaluate the conditions, and whether to restrict access to the alert using account limitations.Set trigger conditions as needed.
The trigger action is executed when trigger conditions meet. SolarWinds NPM has a robust conditioning mechanism that allows users to build complex conditions. All fields available in the database can be used in these conditions.
Because of available variable variety and flexibility, building conditions in SolarWinds rather than Jira Service Management are highly recommended.Set a reset condition.
The reset action is executed when the condition is met.Set the time interval for the alert to monitor your network, either always enabled or restricted to a specified time.
Enter values for the trigger action and select Add Action.
With this trigger action, SolarWinds NPM posts alert data to Jira Service Management, and an alert is created in Jira Service Management. To send alert data back to Jira Service Management, set the trigger action to Send a Get or Post Request to a Web Server.Select POST method.
Paste the URL you copied while adding the integration in Jira Service Management.
Enter the variables to send to Jira Service Management in the following format:
variable1=val1&variable2=val2.
All variables sent with a Trigger action to Jira Service Management can be used in the alerts field "Create alert” action of the SolarWinds NPM Integration.Specify teams, recipients, and tags by putting them into the content. The default trigger action body can be sent from SolarWinds here.
The "alias" field in the following example becomes the SolarWinds NPM alerts alias field. To make different alias configurations, change the value of the alias field in post content. Ensure the alias configurations in "Trigger" and "Reset" are the same.Jira Service Management parses incoming data and creates robust alerts according to the incoming content. Modifying alert fields with incoming data can be done via dynamic fields.
Create alerts for any monitored object (Nodes, Volumes, Interfaces etc.) in SolarWinds NPM. Use a "Send Http Request" action to send common fields and monitored object-specific fields. In the SolarWinds NPM Integration, alert-specific fields are available as custom integration fields. It still supports dynamic fields to be sent to Jira Service Management.
Example: To include a NodeID variable in an alert in Jira Service Management – It's not one of the integration fields available, so send it from the SolarWinds NPM to dynamically use it in alert configuration. Ensure the variable name used in Jira Service Management and SolarWinds NPM is the same.
Add NodeID variable to Http Post Body by:
NodeID=${N=SwisEntity;M=NodeID}and then use it in the SolarWinds NPM integration "Create Alert Action" alert fields like in the following example of{{NodeID}}:Set the reset action. With a reset action, SolarWinds NPM posts the data that closes the corresponding alert in Jira Service Management. Configure the reset action with Send a Get or Post Request to a Web Server option. Find the default reset action body to send from SolarWinds NPM here.
Review the alert configuration and select SUBMIT.
...
SolarWinds NPM sends the body without making any escapes on data. Hence, if any variables contain any characters that need to be escaped (like &), send the data in advanced mode. Use µ#µ instead of = and §#§ instead of &. Sending the data from SolarWinds NPM to Jira Service Management in either format produces the same results in Jira Service Management. Refer to a troubleshooting version of the default content for the trigger action body and reset action. Ensure that the Body to Post text matches this to Acknowledge/Close/AddNote actions on the SolarWinds side.
...