The default/recommended MID Server CPU alert/mid server issue threshold is unrealistic for a MID Server doing DiscoveryDescriptionA MID Server set up with the default values for MID Server resource threshold alerts (95% for 30 minutes) is almost guaranteed to alert for CPU usage if a Discovery schedule is run. This false alert implies there is an issue with the MID Server, but that is not the case. These mid server issues can also lead to event management self-health monitoring alerts.MID Server resource threshold alerts"mid.threshold.mean_cpu.aggregate_interval_spanNumber of 10 minute units in the interval for sampling CPU usage data. The default interval is 30 minutes (3 x 10 min.)Default: 3mid.threshold.mean_cpu.percentUsage percentage of the total CPU resources that initiates a threshold breach alert.Default: 95"Steps to Reproduce Set up a MID ServerConfigure the default properties for mid server cpu monitoringRun the in-house Discovery test suites or a Discovery schedule that would be expected to run for several hoursWorkaroundThere are many factors that may cause CPU to spike up during Discovery. Once the Discovery execution stops successfully, the resource utilization returns normal. Due to Discovery's deliberate optimization of Shazzam and other probes/patterns for maximum throughput, 100% CPU use is to be expected almost immediately, and stay that way for most of the discovery schedule. A 10k node schedule run in a single mid placed in an AWS instance of type m5.xlarge with 8 CPUs and 16 GB memory, will be expected to max out the CPU for long periods. MID Server System Requirements Discovery MID Servers at 100% CPU - Good or Bad, Why and then what? MID Server Max Threads - Worker Groups - Priority and QueuesRelated Problem: PRB1458352