When you create a rule, monitor, or view, you must define a target for it. Operations Manager uses object types as targets. You should always target a monitor or rule to the object that most specifically describes the objects that you want to monitor. In other words, target your monitor, rule, or view at the lowest level possible.

After you target your monitor, rule, or view to an object type, you can narrow the scope of the monitoring data that is collected by using groups and overrides. Ideally, you need to create a group that contains only the objects that you want monitored by the monitor or rule.

If the group of objects that you want to monitor is not fixed, you can create a dynamic inclusion rule that identifies group members in the Create Group Wizard. To create a group that uses a dynamic inclusion rule, you should identify a common attribute for the objects that you want to monitor. Then you can build a formula, based on any attribute of an object type, that identifies this attribute in the Create Group Wizard. If no attribute is available, you can create an additional attribute by using the Create Attribute Wizard before you create the group.

For example, suppose that you have 10 Web servers and 5 of them are running a proprietary application that you want to monitor. Because the application on the Web servers is proprietary, no attribute exists that identifies this application. The following are the steps that solve this issue:

1. Create a custom attribute that is based on the entry in the registry that indicates this application is installed on a Web server.
   
   
2. Create a group whose membership is determined by your new attribute.
   
   
3. Create the monitor or rule that you want, and target it at the Web Server class.
   
   
4. Disable the monitor or rule.
   
   
5. Use overrides to enable the monitor or rule only for the group you created.
   
   

Note

By default, when you create a management pack object, disable a rule or monitor, or create an override, Operations Manager saves the setting to the Default Management Pack. As a best practice, you should create a separate management pack for each sealed management pack you want to customize, rather than saving your customized settings to the Default Management Pack. For more information, see Default Management Pack

Tasks

Other Resources