7 Replies Latest reply on Mar 23, 2015 1:51 PM by LadaVarga

    Alert timestamps in database off by 4 hours

    Detroiter

      I just upgraded to 11.5 (yeah I know...) and I am seeing odd behavior in the new alert database tables.  I seems they are not using the local server time for the timestamp of when an alert occurred.  Screenshots below of a volume alert that occurred shortly before 9:30 am today (3/23)

       

      alert_time_Orion.jpg

      alert_time_database.jpg

      Both images show the same alert, but the "All Active Alerts" page in Orion seems to be automatically converting them back to the correct time.  I use many custom SQL queries to report out on alert status and time is a critical component of them.  As is stands, if an alert triggered at 11 pm tonight, my daily report of alerts triggered for today WOULD NOT show it since the database would stamp it as 3 am TOMORROW.

       

      Is this by design, if so WHY?