Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Archive > 2018September24 - Deletes > Add variables to Alert Messages in NPM 10.7

Add variables to Alert Messages in NPM 10.7

Table of contents


This article discusses how you can add variables to an alert in NPM 10.7.


NPM version 10.7


  1. Log in to the main Orion server machine.
  2. Open the Advanced Alert Manager.
    This is the interface where you can create and delete and modify alerts in detail.
  3. Select one of the alerts. 

For example: Alert me when component is down and click Edit.

  4.  Navigate to Trigger Actions tab. 
Trigger actions is where you define what action you would like the product to do if the Trigger conditions have been met.

  5.  Click Email/Page Action.
  6.  Click Edit Action.

  7.  In the smaller pop-up window for edit action, navigate to the Message tab.
This is the tab where you can adjust what you would like to be sent in the Alert Email.

  8.  Click Insert Variable.
This leads to another pop-up window with a list of variables that you can search through to choose what information you would like to be included in an email. For Example: Node.IPAddress.

  9.  Click the confirmation button, and the variable will be included in the email message.

 10.  Click OK until you are back to the list of Alerts in the Advanced Alert Manager.
Note: In your next email alert, you should now see the node IP address within the email.


There are also Reset Alert Emails. In most cases unless manually changed, the reset alert has the condition to trigger a reset action when the Trigger Condition is no longer true.

Some examples are provided below: 

  • Component is down is the trigger condition.
  • Trigger condition becomes true when a component you are monitoring goes down.
  • Trigger action is then set to send an alert email.
  • Component comes back up.
  • Then the trigger condition no longer is true, this in turn triggers the Rest Condition.
  • Reset action is then set to send a reset alert email to tell you that the component is now back up.


The Reset is found the same way the Alert Actions is found. Only instead of the Trigger Action, you navigate to the Reset Actions > Click Edit action, and navigate to the message tab.


Here are some further helpful links regarding alerts:



Last modified


This page has no custom tags.


Internal Use Only