Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > LastTimeUp variable will be an hour off in alerts

LastTimeUp variable will be an hour off in alerts

Table of contents

Updated 9-1-2016


Alerts using LastTimeUp variable may be off by an hour. The LastTimeUp variable is internally converted to local time. Alerting expects all values in UTC. Unfortunately, there is not a workaround for the time difference.


  • NPM 11.5 and later
  • SAM 6.2.X and later
  • Orion 2015.1 and later


When using the LastTimeUp property in alerts, be ware the value will be an hour off in notification emails. The variable converts to the local system time through the Orion Platform. Alerting expects all time values in UTC. This causes the values to report an hour off.




Last modified
10:11, 1 Sep 2016