Which Class / Target for Management Servers to Run a Performance Collection Script?

OdgeUK 41 Reputation points
2021-02-09T12:52:27.473+00:00

I've created a Powershell Performance Collection Rule which I want to execute against my Management servers once a day. The script gets a count of all alerts created the previous day by using Get-SCOMAlert.

It works if I target to Windows Operating System and then override to the Windows Computer object for any one of the Management Servers (we have 4 in the Main Resource Pool and another 4 outside of the pool), but I don't like this method as it's not robust if that Management Server is down for any reason.

So I tried "All Management Server Resource Pool" and got no results. I tried "Management Server" but only seem to get two of my Management servers returning results, and they take it in turns to run the workflow, so the results I want can only be seen by looking at a composite of both results.

What can I use here that will execute against all the Management Servers, but only return one value (is this what they call 'Cookdown'?)

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,511 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. CyrAz 5,181 Reputation points
    2021-02-09T14:36:23.603+00:00

    Is there something wrong with the out of the box perf rule? (https://systemcenter.wiki/?GetElement=ManagementGroupCollectionAlertsCountRule&Type=Rule&ManagementPack=Microsoft.SystemCenter.OperationsManager.SummaryDashboard&Version=10.19.10050.0 )

    Anyway, targetting the All Management Server Resource Pool should be the way to go. That would make your rule run on a randomly selected server in the pool, not necessarily always the same; and still allow you to view the perf graph on a single object (the pool itself).

    Targeting "Management Server" should make the rule run on all management servers, all the time. So the behavior you're witnessing is not normal.

    And no, this is not related to cookdown. Two concrete examples of cookdown :

    • Use a single script running only once to provide data to multiple monitors on the same object
    • Use a single script running only once to provide data to the same monitor but for multiple objects
    • Or even a combination of both.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.