MonitorWare Knowledge Base

Dear Support,

Let me thank you for the wonderful support! You guys were very prompt in replying to all the queries! Well, there is always something for the customer to keep the support people busy.

My Winsyslog service displays Time 1hr late (in Date coloumn) after the daylight settings changed. The service collects all the events from remote machines, but the time displayed is 1hr late (eg. when an event is logged at 10am on remote machine, syslog collects the event and writes to database and displays in web page with time 9am). I think it is just a small seting somewhere i have missed!

Thanks and regards,

Kiran

Dear Kiran,

Thanx for the compliments

I think in the "Write to Database" Action, you might have selected UTC instead of Local Time for "DeviceReportedTime" and "ReceivedAt" fields. If you switch them to Local Time, it will sove your problem. Can you check that and let me know?

Regards
Wajih-ur-Rehman
Adiscon

Kiran,

I am not sure, but it could also be that the sender does not know of Daylight savings time (or is not configured to obey it). We often see this case, esepcially as some routers do not at all have an idea of DST. If this is the case, WinSyslog then-wrongly converts the time (because the device is sending with the wrong offset).

Unfortunately, the only cure in such cases is to adjust the device clocks. Current syslog protocol does not provide any time zone information, so we can not filter this out. The "ReceivedAt" time, however, should always be accurate.

We are also involved in IETF activity to create a better syslog protocol, so this issue will be solved over time.

Again, I don't say this is necessary the issue in your case, but I wanted to add it as it is a frequent cause (and others may also be reading this thread).

Rainer

Bingo!!! After changing from UTC to LocalTime on ReceivedAt, Syslog started populating the right time! Thanks again for the wonderful support!

regards,

Kiran