Standard event management policies and dynamic enrichment policies are included with the BMC ProactiveNet. 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 BMC ProactiveNet 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:
Dynamic enrichment policies that are provided out-of-the-box include:
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 type||Policy name||Description||Enabled|
|Closure||PATROL_Portal_Closure_on_OK_Events||Closes previous Portal events for the same managed object||Yes|
|Adapter_Start_Stop_Closure||Closes previous events for the same adapter instance||Yes|
|Client_Stop_Closes_Start||Client Stop events close Client Start events and then close themselves||Yes|
|Component Based Enrichment||Sample_Component_Based_Enrichment_Policy||Enriches events by filling selected event slots with the slot values of the|
|Dynamic Blackout||Dynamic_Blackout||Blacks out events that meet a specified criteria during a specified time period||No|
|Dynamic Enrichment||Location_Enrichment||Appends the location of a server to an event||No|
|Service_Contact_Enrichment||Appends 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_Translation||Replaces the text of existing PATROL event messages with messages that can be more easily understood by operators.||No|
|Intelligent Incident Service||Sample_Intelligent_Incident_Service_Policy||Sample policy for creating Intelligent Incidents for Remedy Helpdesk||No|
|Propagation||Event_Propagation_To_Remedy_Help_Desk||Propagates events to Remedy Helpdesk||No|
|Event_Reporting_Propagation||Propagates events to the Portal for event reporting||No|
|Recurrence||Apache_Login_Failed_Repeats||Handles repeating Apache Login Failed events||No|
|Patrol_Portal_DeDup_Policy||Handles repeating Portal events for the same managed object||Yes|
|Suppression||Blackout_Suppression||Suppresses Blackout events||No|
|Component Based Blackout||Component_Based_Blackout||Suppresses events that meet a specified criteria during a specified time period for specified components||No|
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.
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.