Child pages
    • Defining general policy details

    Unsupported content

     

    This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

    Skip to end of metadata
    Go to start of metadata

    Using BMC ProactiveNet Central Monitoring Administration, you can define and manage policies to configure the BMC PATROL monitoring solutions.

    To define general policy details

    1. In the navigation pane of the Central Monitoring Administration console, click the Policies drawer.
    2. Expand one of the following policy types:
      • Monitoring—Allows you to create or edit monitoring policies
      • Blackout—Allows you to create or edit blackout policies
      • Staging—Allows you to create or edit staging policies
    3. Select one of the following policy views:
      • All
      • Global
      • Tenant
    4. Click Add , or select an existing policy and click Edit .
    5. 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.

    6. Provide the following information:

      Field

      Instructions
      NameName 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 policyIndicates 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:
      • Global—Indicates that the policy is applicable to all the BMC PATROL Agents that match policy conditions. The default value is Global.
      • No Associated Tenant—Indicates that the policy is applicable only to the BMC PATROL Agents that are not associated with any tenant and match policy conditions
      See Policies and tenants.
      PrecedencePriority 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.
    7. Click Next.

    Policies and tenants

    When Central Monitoring Administration receives a configuration request from a BMC PATROL Agent, the policies are applied in the following way: 

    • If only a global policy match the agent conditions, then configuration from the global policy applies to all the BMC PATROL Agent.
    • If a global policy and a tenant policy or a no-associated-tenant policy match the agent conditions, then configuration from both the policies apply to the BMC PATROL Agent. If a conflict arises (that is, two policies configure the same attributes), then configuration from the tenant policy applies.

    Where to go from here

    2 Comments

    1. 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.

      1. 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.