Each Policy Component is only applicable to assets that are within its target scope, or the target scope of the Monitoring Policy which contains the Policy Component.
Policy Components are configuration items which affect how SilverBack monitors selected assets.
|
|
Each Policy Component is only applicable to assets that are within its target scope, or the target scope of the Monitoring Policy which contains the Policy Component. |
Different Policy Components affect different monitoring aspects. Some affect how data is processed (Thresholds, Windows Services Monitors, Event Monitors, Remote Tasks); others affect what data to collect (Collection Fault Monitors, Event Monitors, Patch Scans, Vulnerability Scans); and others affect the presentation of information (Scheduled Reports, Scheduled Report Packages, Notification Rules).
Some Policy Components (Collection Fault Monitors, Event Monitors, Patch Scans, Remote Tasks, Scheduled Report Packages, Thresholds, Vulnerability Scans and Windows Services Monitors) can be grouped into Monitoring Policies, enabling you to apply multiple Policy Components to a common set of assets as one entity. See Understanding Monitoring Policies for more information about Monitoring Policies and Monitoring Policy Templates.
|
|
Whenever possible, start with the default Policy Components as starting points for your monitoring services. Combine these into a Monitoring Policy to ensure consistency across your organization or customers (see Understanding Management Domains). When an individual device or application requires a variation from your standard policies, use the override or block operation to deviate from the norm. |
In those instances where several devices or applications require a different service level, you can create individual Policy Components which can be applied to only those systems. In this case, Dell recommends that you block the Policy Components from their applicable devices or applications to avoid conflicts or duplicate faults from being generated. See Blocking and Overriding Policy Components on Assets for more information about blocking Policy Component from assets.
An example of when to use an individual Policy Component would be if a customer has several devices which require minimal monitoring. For example, they may only want their redundant network infrastructure monitored for major failures. In this case, you might create a set of Thresholds or Event Monitors with minimal monitoring and apply those Policy Components to a device group containing the redundant network devices.
|
|
Policy Components themselves cannot target Desktop systems. You must include them in a Monitoring Policy, then target the policy at Desktops. |
