Forum Discussion
Nashaat Sorial
Dec 23, 2018Copper Contributor
ATP sensor Consume most server CPU (60%)
It is observed after installing ATP sensor, on domain controller, that more than 60 % of 16 cores CPU are consumed by microsoft.tri.sensor.exe component
mesaqee
Mar 24, 2021Copper Contributor
EliOfek Well after upgrading the capacity the usage was pretty high and we were even getting the "Some network traffic could not be analyzed" alert. However, we are now unable to see the trend as the Sensor service is not starting. On trying to manually start it, we are getting the below error:
We have tried rebooting the server and re-installed the sensor, but the service is still not running. Shall we contact support to have a detailed look or you got any further suggestions?
Thanks,
Saqib
EliOfek
Microsoft
Mar 24, 2021Check the local logs of the sensor and updater to see if there is any clue to why it fails to start.
Also make sure you have the WmiApSrv service starting correctly.
If no clues, you need a support ticket to go forward...
Also make sure you have the WmiApSrv service starting correctly.
If no clues, you need a support ticket to go forward...
- EliOfekFeb 26, 2024
Microsoft
aafar Your description is too generic to spot the root cause.
This is something that would best be handled via a support ticket, as given the machine details we can track it's telemetry remotely to better understand what is happening and why.
General note: assuming this is not a standalone sensor you are talking about (in which case it's normal for it to consume all available resource), the sensor is designed to throttle it's cpu and memory consumption to make sure the server has at least 15% free cpu/memory at all times.
So while high cpu can be "by design" if traffic on the machine is high, exhaustion should not really happen unless something really bad happen and the resource manager fail to do it's job, which is unlikely. - aafarFeb 26, 2024Copper ContributorHas anyone else seen this issue? I've been experiencing high CPU usage/exhaustion due to tri.sensor and tri.sensor updater over the last week or so. I followed links in this thread but did not see anything that helps the issue.