Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > PREVIOUS variable is not displayed when an alert is simulated

PREVIOUS variable is not displayed when an alert is simulated

Table of contents

Updated December 8, 2017

Overview

In alert actions, it is possible to place the previous value of a variable into the trigger action. For instance, it is possible for the trigger action email to display the last time a node was booted prior to the instance that triggered the node reboot alert.

Environment

  • All versions of NPM and SAM

Detail

The PREVIOUS modifier of an alert variable is context sensitive. Because the data is not stored in the database, the prior value is kept for the duration of the trigger of the alert.

 

Hence, PREVIOUS variables in an alert will not resolve when the alert is simulated.

 

http://www.solarwinds.com/documentation/en/flarehelp/netflow/content/core-example-messages-using-variables-sw956.htm

 

 

 

Last modified

Tags

Classifications

Public