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

Standard event management policies and dynamic enrichment policies are included with the Infrastructure Management. These policies enable you to interactively set up routine event processing quickly. 

To use out-of-the-box dynamic enrichment policies, you must enable the policy, import useful data into the sample .csv files and then import the data into the cell using the policy mechanism. For instructions to creating dynamic enrichment policies, see Creating a new dynamic enrichment event management policy.

Several event management policies are included with the product that enable you to interactively set up routine event processing quickly. Standard event management policies that are provided out-of-the-box include:

  • PATROL_Portal_Closure_on_OK_Events
  • Apache_Login_Failed_Repeats
  • Blackout_Suppression
  • Adapter_Start_Stop_Closure
  • Client_Stop_Closes_Start
  • Sample_Component_Based_Enrichment_Policy
  • Sample_Intelligent_Incident_Service_Policy
  • Event_Reporting_Propagation
  • Event_Propagation_To_Remedy_Help_Desk

Dynamic enrichment policies that are provided out-of-the-box include:

  • Location_Enrichment
  • Service_Contact_Enrichment
  • PATROL_Message_Translation
  • BPM_STATE_CHANGE
  • BPM_RSM_STATE_CHANGE
  • PATROL_EVENT

The following table lists the out-of-the-box policies and indicates whether or not each out-of-the-box policy is enabled by default.

Policy typePolicy nameDescriptionEnabled
ClosurePATROL_Portal_Closure_on_OK_EventsCloses previous Portal events for the same managed objectYes
Adapter_Start_Stop_ClosureCloses previous events for the same adapter instanceYes
Client_Stop_Closes_StartClient Stop events close Client Start events and then close themselvesYes
JSERVERCellConnectionStatusPolicy Yes
Close_Open_Alarms Yes
RATECellConnectionStatusPolicy Yes
Component Based EnrichmentSample_Component_Based_Enrichment_PolicyEnriches events by filling selected event slots with the slot values of the
component type
No
Dynamic BlackoutDynamic_BlackoutBlacks out events that meet a specified criteria during a specified time periodNo
Dynamic EnrichmentLocation_EnrichmentAppends the location of a server to an eventNo
Service_Contact_EnrichmentAppends contact information for a server administrator to an event. For example, contact information might include the name of the administrator for that server and his or her telephone number.No
PATROL_Message_TranslationReplaces the text of existing PATROL event messages with messages that can be more easily understood by operators.No
Intelligent Incident ServiceSample_Intelligent_Incident_Service_PolicySample policy for creating Intelligent Incidents for Remedy HelpdeskNo
PropagationEvent_Propagation_To_Remedy_Help_DeskPropagates events to Remedy HelpdeskNo
Event_Reporting_PropagationPropagates events to the Portal for event reportingNo
RecurrenceApache_Login_Failed_RepeatsHandles repeating Apache Login Failed eventsNo
Patrol_Portal_DeDup_PolicyHandles repeating Portal events for the same managed objectYes
SuppressionBlackout_SuppressionSuppresses Blackout eventsNo
Component Based BlackoutComponent_Based_BlackoutSuppresses events that meet a specified criteria during a specified time period for specified componentsNo

For instructions to use these out-of-the-box policies, see Creating new standard event management policies and Creating a new dynamic enrichment event management policy.

Note

The BMC Impact Integration for PATROL product can detect duplicate events and can correlate events that come from the same origin. The rules for detecting duplicated events are located in the installationDirectory/pw/server/etc/cellName/kb/rules/bii4p.mrl file. See the patrol_duplicates and the correlate alarm_and_ra definitions. You can use the new patrol_duplicates rule to delete duplicate events and the correlate alarm_and_ra rule to close a current event after a subsequent event arrives from the same origin.

BMC Impact Integration for PATROL does not provide a policy for these events.