Microsoft Defender ATP for Linux 90 plus percent during full scan

Copper Contributor

Hi Team,

 

we are in the process of testing Microsoft Defender ATP for Linux and noted High CPU spike from 4% to 90% at the start of the Scan. I opened a ticket with Support and they confirmed their is no CPU throttle for MDATP for Linux. Support recommended scan during non peak times, but as you can see below I haven't put the Linux Test Server under load yet.

I'm wondering if anyone else has deployed MDATP for Linux and what environment or other changes you made so MDATP wouldn't take all the CPU ?

Anyone else deployed MDATP for Linux and enable full Scans ?

 

Scan off normal

roger_jr_0-1614728146981.png

Full Scan at 0 Sec 91% cpu

 

roger_jr_1-1614728205909.png

Full Scan at 1 MIN 90% cpu

roger_jr_3-1614728341515.png

 

Full Scan at 5 min 92 % cpu with a 3 load

roger_jr_2-1614728240900.png

 

Thanks Roger

 

4 Replies
We had a similar problem with CPU spikes crashing Oracle DB, there should be a way to throttle for unexpected issues.
Hi Roger,

Do you still have that issue ?
What version of MDATP do you have ? You can use:
mdatp health
to get it.
I recommend opening a ticket with TAC and they can engage Engineering for needed commands to RCA:

The Load and CPU performance problems we encountered was caused by the mdatp_audisp_plugin when it ingest data from the audit logs.

There is a workaround to add exclusions so the mdatp_audisp_plugin stops ingesting data from the excluded applications. But you will need TAC guidance to properly put it in place.

This issue we saw was very inconsistent and only effected a handful of Linux Servers. In our case we could have the same Linux Servers running the same Applications and one would have the issue

and the other wouldn’t.

Per Microsoft they were looking at incorporating the fix on CY21Q4, but it might be CY22Q1.

101.29.64 - also help improve some unrelated Linux performance issues, but every issue unique, and going to Microsoft TAC is your best course of action.
Also we scheduled scans during non peak and non impacting hours of operations.