Using BMC ProactiveNet Central Monitoring Administration, you can define and manage policies to configure the BMC PATROL monitoring solutions.
Select the configurations that you want to set for the policy.
Note
This page is applicable only for the monitoring policies, not for the blackout policies or staging policies.
In this procedure for creating monitoring policies, it is assumed that you have selected all the configuration options.
Provide the following information:
Field | Instructions |
---|---|
Name | Name for the policy. The policy names must be unique. In an environment with tenants, the policy names must be unique for a single tenant. It is a mandatory field. |
Description | (Optional) A brief description about the policy |
Enable policy | Indicates whether the policy is enabled or disabled. By default, the policy is disabled. If you disable a policy when you create it, the policy configurations are not applied to the BMC PATROL Agents and the child servers. If you disable any existing policy, the policy configurations are removed from the BMC PATROL Agents and the child servers, where the policy was applied. |
Tenant | (For environments with tenants) Name of the tenant who owns the policy. The other supported values are as follows:
|
Precedence | Priority of the policy. Based on the precedence number you configure, the configuration is applied on the BMC PATROL Agents and BMC ProactiveNet Child Servers. The default value is 999. The precedence number ranges from 0 to 999. A lower number indicates a higher precedence. It is a mandatory field. For precedence behavior and best practices, see Precedence best practices. |
When Central Monitoring Administration receives a configuration request from a BMC PATROL Agent, the policies are applied in the following way:
2 Comments
Daric Smith
The following isn't explicitly laid out in any of the documentation:
The Precedence also determines when a policy is applied: Lower Precedence Policies are Applied BEFORE High Precedence Policies.
This particular Best Practice information IMPLIES that, but the main documentation and this document should make it explicit.
Because of that, things like your precedence values for "Windows Basic" or other "General Monitoring Settings" should be a higher precedence (not lower). This way if you have a non-standard monitoring that is a duplicate of the "General" you would not want that configuration over-written by the "general settings" policy.
Sanjay Prahlad
Hello Daric,
Policies with higher precedence are not really applied before policies with lower precedence. All policy configuration that is sent to a particular PATROL Agent is combined and the result is then sent to the PATROL Agent. Conflict resolution and the eventual result is evaluated differently in 9.5 GA and 9.5 SP1.
More information on this page: Precedence best practices. Hope this clarifies/helps.