When all agents get a change (at the “same time”), there will be some more CPU usage on the servers. This Causes CPU Spike on virtualization hosts.
And when all agents downloads new mp’s or config changes at the same time, this could result in write-latancy on the SAN.
We experience these issues when we update management packs, import new management packs, update groups, overrides, Run As account configuration.
-> All these changes will force the agent to download changes and then we are experiencing this problem.
Of course, we can make the most of changes in a test environment, but at some point it must be imported into production…
Therefore, I wonder if it’s possible to spread the rollout of changes so not all agents do the same operation at almost the same time.
I suppose all scom environments are different, but this is something we notice and would like to try to find a solution or reduce it in some way.
Thanks for feedback!
(4000 + VM’s on VMWare ESX-hosts and HP 3PAR SAN)
Source: Health Service
“New management pack with id xxx received” - Splunk Search
CPU Ready on Vmware hosts
Write Latency on SAN