Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > 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


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.


  • All versions of NPM and SAM


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.




Last modified