Timestamp in field "ReceivedAt" and "DeviceReportedTime" stored in the database is wrong ?

Friday, December 5th, 2003

Timestamp in field "ReceivedAt" and "DeviceReportedTime" stored in the database is wrong ?

Updated 2003-12-05 by Tamsila-Q-Siddique

The local PC-Time and other reported device time is correct but the the time stamp in "RecievedAt" and "DeviceReportedTime" field stored in the database is wrong ?

The time in field "ReceivedAt" and "DeviceReportedTime" which is stored in the Database Table (e.g. MySQL, SQL Server) isn’t actually wrong. In the database logging action (the one you had defined) the value for these fields are set to UTC by default. Because of this setting you would see a time difference in the database. For example a person living in UK, won’t even notice this because he is actually on UTC!

Please do the following if you face this situation:
1. Go into the action that you had defined for Database Logging.
2. Set the time for "ReceivedAt" and "DeviceReportedTime" to "Localtime".

Difference between ReceivedAt and DeviceReportedTime

Saturday, May 10th, 2003

Difference between ReceivedAt and DeviceReportedTime

Created 2003-05-10 by Wajih-ur-Rehman.

What is the difference between ReceivedAt and DevicedReportedTime?

I will explain you the difference by giving you two different scenarios:

Scenario 1: Using MonitorWare Agent as Event Log Monitor and Forwarding the data to another MonitorWare Agent using Syslog

In this case, the DeviceReportedTime is actually the time that is there in the Windows Event Log i.e. the time at which the message was written into the Windows Event Log. ReceivedAt time on the other hand is the time when the Syslog message is received at the Syslog Daemon, which in this case is the MonitorWare Agent.

Scenario 2: Using MonitorWare Agent as Event Log Monitor and Forwarding the data to another MonitorWare Agent using SETP

In this case, the DeviceReportedTime is once again the time that is there in the Windows Event Log i.e. the time at which the message was written into the Windows Event Log. ReceivedAt time, in this case, is the time at which the MonitorWare Agent picks up the data from the event log. Note that by design, SETP protocol doesn’t modifies the message as it is sent to the central daemon. So when the message receives at the central daemon, its ReceivedAt time stamp will not be changed. In other words, the ReceivedAt time stamp of any message would stay the same (i.e. the time when the event was read from the Windows Event Log)