Page tree
Skip to end of metadata
Go to start of metadata

A component-based enrichment policy enables you to enhance the event definition of an incoming event that is already associated with a component through an mc_smc_id or mc_smc_alias match. When you define the component-based policy, you assign specified slot values from a standard list of component slots (BMC_BaseElement class) to matching slots in the associated event definition. Whenever an event that matches the selection criteria is received, its definition is automatically enriched by the specified component slot values.

To create a new component-based enrichment policy

  1. From the Event Management Policies tab of the Administration View, expand the By Policy Type folder.
  2. Under the By Policy Type folder, select Component Based Enrichment Policy.
  3. Click the Add Event Policy
    button.

    A Selector Chooser dialog box is displayed.
  4. From the Selector Chooser dialog box, select the event selector that you want to use for this policy and click OK.

    The event selector controls which events are processed by the policy and, consequently, which event slots are displayed in the Event fields list.

    The Component Based Enrichment Policy Details tab is displayed in the details pane of the Administration View as shown in the following figure.

    Component Based Enrichment Policy Details tab
  5. In the Policy Name field, type a unique alphanumeric name for the event management policy. The name must contain no spaces.
  6. In the Description field, type a description of the event management policy.
  7. To enable the event management policy, select the Enabled check box. If you do not want to enable the policy at this time, you can return to this dialog box and enable the policy later.
  8. Assign a numerical value to the policy in the Execution Order box.

    The numerical value indicates the order in which policies are automatically run. Policies are run in ascending chronological order. A policy with the lowest numerical value is run first while the policy with the highest numerical value is run last. During the execution phase, policies with higher numerical values always overwrite the preceding policies with lower numerical values.

    Example

    You have defined four component-based enrichment policies and have assigned each a unique numerical value (1, 2, 3, or 4) in the Execution Order field. The policy assigned the value 1 is run first, followed in ascending numerical order by policies assigned the values 2, 3, and 4. During the execution sequence, the policy with the value 2 overwrites the policy with the value 1; the policy with value 3 overwrites the policy with value 2; and the policy with value 4 overwrites the policy with value 3.

    You should assign higher numerical values to policies that you want to run last and lower values to policies that you want to run first.

  9. In the Policy Activation Timeframes section, define the periods of time the event management policy should be active (when enabled) by performing the following actions:
    1. Select one of the following choices:
      • To make the event management policy active continuously, select Always Active.
      • To specify when the policy is active or inactive, select Define Activation Timeframes.

        The Active Timeframes and Not Active Timeframes check boxes are enabled.
    2. If you selected Define Activation Timeframes, depending on how you want to define the timeframe for your policy do one or both of the following:
      • To specify the periods of time when the policy should be active, select the Active Timeframes check box and one or more timeframes from its scrollable list. 
      • To specify the periods of time when the policy should be inactive, select the Not Active Timeframes check box and one or more timeframes from its scrollable list.

        Note

        You can select both check boxes to create active and inactive time periods. However, the inactive time period takes precedence over the active time period.

  10. In the Component Based Event Enrichment Details tab, assign the component slots to the matching event slots in the Match the Component and Event Slots section.

    Consider these guidelines before you make the assignments: 
    • The list of event slots is dynamic insofar as it depends on the base event class you chose in the selector. The list that you see always contains a subset of the CORE_EVENT class. It also contains any additional slot or slots derived from the subclass you specified as the base event class. 
    • The list of component slots is static. The component slots are derived from the BMC_BaseElement class. 
    • You can view and edit a list of excluded event and component slots in the installationDirectory\pw\server\pronto\data\ix\configurationItemPolicies\configurationItemEnrichment.slotFiltering.properties file. You can specify event and component slots to be excluded in the appropriate field: excluded.event.slots and excluded component.slots. Add or update the slots using a comma-separated list.

      After updating and saving the configurationItemEnrichment.slotFiltering.properties file, restart the TrueSight Infrastructure Management server by entering the following command:
      pw system start
    • The component slot value overwrites any current value in the matching event slot. 
    • You must match slots of similar types: STRING with STRING, INTEGER with INTEGER, BOOLEAN with BOOLEAN, and so forth.

      Note

      The table does not support the assignment of LIST or LIST OF slots.

      To make the assignment, select a slot name in the Event fields column and, using the arrow button, move it to the Assignment Table, where you match it with a slot in the Component fields column.

  11. Click OK.

    administration console saves the defined component-based enrichment policy, and it is displayed in the list of event policies for the selected event selector.