Submit a ticketCall us

Have You Auto Renewed? If not, you're missing out.
The SolarWinds Renewal Program comes with a host of benefits including the most recent product updates, 24/7 technical support, virtual instructor-led training and more. Experience all of this with the convenience of Auto Renewal, and never worry about missing any of these great benefits. Learn More.

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

Overview

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.

Environment

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

Detail

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

Tags

Classifications

Public