Reduce CPU impact for SCOMpercentageCPUTimeCounter script
The SCOMpercentageCPUTimeCounter (vbs or ps1) used by Agent processor utilization rule and monitor runs on each agent every 5 minutes (321 sec) and with a sync time set to 00:00.
This causes CPU spike on virtualization hosts.
K Justin commented
Two options for this item -
SCOM2016 UR4 addresses this with pack updates.
SCOM 2012R2 will need to disable the workflow - see Holman's blog https://blogs.technet.microsoft.com/kevinholman/2017/08/15/quicktip-disabling-workflows-to-optimize-for-large-environments/
As I needed to fix something else with the SCOM 2016 implementation of this, I went ahead and also changed this monitor to use SpreadInitializationOverInterval instead of the synctime currently in use. If you take the code it should be fast to implement.
Please remove the sync time from this. That seems like a very simple fix that can help a lot of us out.
Martin Ehrnst commented
Yep, i havent tought about it earlier, but I was investigating with a colleague from our data center department and we pin pointed it to cscrcript which let me think of scom.
We dont use this data, so it's disabled now.
Kevin Holman commented
I was shocked that this has a synch time. I gave feedback on this workflow when it first came out back in SCOM 2007R2. In general - I recommend disabling the rule and the monitor which both run this script, as it is very noisy for script failures and collects too much perf data in my opinion. That said - I agree - we should not use a default synch time on script datasources unless there is a VERY good reason, as we create resource depletion on virtual hosts when we do this.