Found high autosensor overhead, might hint to time drift problem
what's the reason for this warning/exception to occur ?
Found high autosensor overhead, might hint to time drift problem, tsCounter: 655
Guess when this exception is occurring purepaths stop generating for the corresponding agents.? as in production I see that for certain agents having this exception I dont see any purepaths getting captured for it.
Please let me know if you need further details on this issue I can provide it.
Hi Prashanth,
We faced similar issue.
"------[00002d2e] info [native] Found high autosensor overhead, might hint to time drift problem, tsCounter: 637"
I am quoting the Xin Geng's response we got from Support
" Regarding the auto sensor overhead would you please uncheck auto sensor from system profile -> agent group -> agent mapping -> advanced.
Also we can see above message from agent log. And 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. Changing to auto sensor and agent timers will get active on the next agent restart."
It was helpful for us. Try out and keep posted.
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
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
