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.