Time drift problem
Hi,
in Server log our customer found this line:
2014-10-16 10:52:13 [2de833f4] info [native] Found high autosensor overhead, might hint to time drift problem, tsCounter: 729
Could this refer to an incorrect Timer being used? Or is that possibly a network issue? Has anyone seen this before?
Should I open a case with Support for this?
Best,
Jiri
please do so. I tried to get an answer but wasnt lucky so far
Jiri,
If you hear/heard back please update us here ... TY.
Thanks,
Rich
Hi,
yes, it was resolved with Support. It is due to virtual environment, you need to change the timer/clock (in Advanced options on the agent level).
Best,
Jiri
Hi,
Did you guys find anything else on this "Time Drift" problem? I got an Incident Alert for Timed Out Purepaths due to this same same issuefound in the Logs: "Found high autosensor overhead, might hint to time drift problem".
I checked the Agent's Time and it appears correct.
This is what I got from Support, it helped me to resolve the problem:
The autosensor overhead measurement is to verify how long it takes getting a thread dump of all threads with sensors on it. So if it measures high overhead, it is reducing the interval to not cause overhead issues and additionally slow down a maybe already busy server.
This measurement can be unreliable in case the application server is virtualized and the VM is moved to different physical CPU cores by the hypervisor. Then the timers are most likely jumping ahead or back in time and if so, we might also detect "high overhead" even if there is no problem. 'Low-Res System Clock' should always work, but you can also try others. The change gets active on the next agent restart.
If that does not help, I would suggest opening a Support case.
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
September 2017
Announcing Dynatrace's Community Member of the Month for September 2017, Tarun A.! Click here to read more! 
