Why it’s best practice NOT to target a Rule/Monitor at a group

If I shouldn’t target groups, why are they listed when I select a target for a rule?

Groups are classes just like any other.  They’re singleton classes where the class and the instance are one and the same, but they are classes nonetheless which is why they show up in the list with all other classes.   There are really very few circumstances where you will target a rule at a group though.  

What happens if I do target a group?

You can apply a rule/monitor directly to a group, but it will execute against the group object itself.  OpsMgr will not enumerate members of the group and apply the rule to each.  Any rules targeted at groups will actually operate on the Root Management Server since groups have no host and unhosted objects are managed by the RMS. 

 In what circumstances would I target a group for a rule/monitor?

 To the specific question of how to get a particular rule/monitor to a subset of components, you have two basic options.  Let’s say for example, you have a particular subset of web sites that you need a particular rule to apply.  You could target that rule at the IIS 2003 Web Site class for example, but that would apply the rule to all instances of that class.  It would probably apply to sites that you didn’t want.

 Option 1 would be to create a new class and target the rule at the class.  In the case of an IIS site, this would mean that you would need to go to the Authoring Console or raw XML and create a new class and discovery.  That’s a more advanced solution that most customers will do and probably overkill anyway. 

 Option 2 is to create a rule target at the whole class and disable it.  Create a group with the sites you want and create an override for that group to enable your rule.  This might sound like a workaround, but it’s a completely valid solution.

This entry was posted in Monitors and Rules and tagged , , , , , , , , , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s