SCOM Agent CPU Utilization higher

Asoka Chang 46 Reputation points
2022-08-19T01:30:38.863+00:00

H! Guys,

SCOM agent occupies too much CPU resources, what is the reason? Is there a way to solve it?

Environment: SCOM 2019 UR3

Updated: KB5005527-AMD64-Agent hotfix, doesn't seem to work

Operations Manager
Operations Manager
A family of System Center products that provide infrastructure monitoring, help ensure the predictable performance and availability of vital applications, and offer comprehensive monitoring for datacenters and cloud, both private and public.
1,438 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Graham 176 Reputation points
    2022-08-20T10:32:23.347+00:00

    Can you narrow it down?

    1. Is it all servers? If so, have you configuered anti-virus exclusions?
      https://learn.microsoft.com/en-us/system-center/scom/plan-security-antivirus?view=sc-om-2022
    2. Just servers with a specific operating system?
    3. Just a specific management pack \ application?

    If you've done some custom rules and monitors then depending on how you've scoped them then this could be causing an issue. Or has someone done an override to run a rule \ monitor too frequently?

    And what is too much? And is it a flat line high or does in go in peaks and troughs? If it is a peak on a regular basis e.g. every 5 minutes, every 15 minutes, every hour then chances are that it is a rule or a monitor.

    1 person found this answer helpful.

  2. Andrew Blumhardt 9,676 Reputation points Microsoft Employee
    2022-08-20T20:10:59.443+00:00

    Check the agent version. I have seen high CPU when the agent is far outdated compared to the SCOM version. I have also seen the same in reverse, for example when SCOM 2012 monitors Server 2016 or higher. Also consider the workload on the agent. Are there any issues on the server causing high event volume or rapid performance fluctuations? have any new, potentially inefficient MPs, been deployed?

    1 person found this answer helpful.
    0 comments No comments