Hi,

I changed the clock/time of the server that is hosting MSSQL db with a functional S-TAP. A changed the clock a couple of hours ahead and I noticed that didnt recieved any logs after changingb the clock and didnt recieve any warnings under s-tap control,  everything showed green. 

When I changed the clock back and restrated the db server and then I recieved logs again. Normally you probably do not change the clock of a server but I am curious if this is a bug or what?

it looks that everything works well - time on collector is used for reporting
if you change time backward on monitoried system, for example - modify report timeframe to cover the incorrect time on your db machine using FROM, TO parameters

------------------------------
Zbigniew Szmigiero
IBM
Warsaw
------------------------------

Just realised that I had runtime parameters in the log report set to -3h to NOW. But this is good then I can test my policy for activity during none working hours.

Thanks for input!
Original Message:
Sent: Fri November 08, 2019 02:10 AM
From: Zbigniew Szmigiero
Subject: Changed db server time/clock - no logs

it looks that everything works well - time on collector is used for reporting
if you change time backward on monitoried system, for example - modify report timeframe to cover the incorrect time on your db machine using FROM, TO parameters

------------------------------
Zbigniew Szmigiero
IBM
Warsaw
------------------------------

It's possible that the logs will show up if you search for logs for the new time on the DB server. E.g. if the time on the collector is 10am and the DB server is changed to 8am, search for logs from 8am. I believe STAP logs are time-stamped with the local DB time since they are sometimes cached on a local file when connectivity to the collector is lost. This does not explain the alerts issue though, maybe there's a similar issue with the alert engine.

------------------------------
Femi Adalemo
------------------------------