Always use care when modifying Monitoring Policy Templates - all Monitoring Policies that reference (compose) a modified template will be automatically modified as well.
A Monitoring Policy is a combination of Policy Components which represent the types of issues for which you wish to monitor a set of customers or systems. Monitoring Policies are containers for Policy Components that have a common purpose. That purpose can be technology-based or service-based.
For example:
A Platinum Monitoring Policy could be focused on looking for all IT infrastructure issues. It might contain all Thresholds associated with Cisco routers, Web Server Event Monitors, Vulnerability scanning and Exchange Services.
A Server Monitoring Policy could specifically focus on Microsoft OS issues, and include Policy Components such as CPU Threshold, Server Health Event Monitors and core Windows Services.
A Monitoring Policy is establishes the set of rules used to determine whether your IT systems are working correctly. Therefore, part of the definition of a Monitoring Policy is identifying which assets within the IT infrastructure should be targeted. Targets can include customers (Management Domains), Groups, Devices, Applications, etc.
A Monitoring Policy Template is similar to a Monitoring Policy in that it contains Policy Components, but it cannot be applied to a set of targets. It is used to establish a standard for monitoring a specified technology. For example, Cisco PIX firewalls; another template may be applicable to monitoring Desktops.
Once this standard is established, the Monitoring Policy Template can be referenced and used by many Monitoring Policies. When the template is improved or modified, all Monitoring Policies which reference that template will be automatically updated.
|
|
Always use care when modifying Monitoring Policy Templates - all Monitoring Policies that reference (compose) a modified template will be automatically modified as well. |
Monitoring Policies can also reference Monitoring Policy Templates. Monitoring Policies can only reference Monitoring Policy Templates from within the same parent Management Domain hierarchy, as shown below:
When a Monitoring Policy references a Monitoring Policy Template, the net effect is the same as creating a Monitoring Policy with the same Policy Components as contained in the Monitoring Policy Template. Therefore, a Monitoring Policy includes all Policy Components directly contained in the Monitoring Policy, plus one copy of each Policy Component from composed Monitoring Policy Templates.
Whenever Policy Components within a Monitoring Policy Template are disabled (or Monitoring Policy Templates themselves are disabled), all corresponding Policy Components in the referencing Monitoring Policies are effectively disabled. As a result, the disabled Policy Components are not applied as part of the Monitoring Policy. If a Policy Component is duplicated in different Monitoring Policies targeting the same set of Devices, you will receive multiple faults.
A Monitoring Policy can exclude one or more Policy Components from the referenced Monitoring Policy Template. The net effect is that the excluded Policy Component(s) are not used in the final Monitoring Policy.
The following Policy Components can only stand alone, outside of a Monitoring Policy or Monitoring Policy Template:
Notification Rules
Scheduled Reports
|
|
Stand-alone Policy Components cannot target desktop devices. They must be first placed inside a Monitoring Policy, and then the Monitoring Policy can be targeted to the desktops. |
