Best practices for defining Intelligent Event Suppression  relationships


Before you begin defining Intelligent Event Suppression relationships, consider these best practices:

  1. Define broad rather than narrow relationships.
     Relationships are used to ascertain the potential probable causes and related events.
     Narrow relationships may inadvertently filter out potential abnormalities by forcing BMC ProactiveNet to give them lower scores. The BMC ProactiveNet recommends defining the broader relationships first. If more granular relationships are needed, you can always define additional relationships.   
  2. Think through the relationships before creating them.
     Plan the relationships well. Generally a scalable and well thought-out plan of related groups works best. Think of elements in your infrastructure in abstract groupings and create relationships based on these groupings as opposed to using the device or instance level. 
  3. BMC ProactiveNet includes default, global relationships. Take advantage of this out-of-the-box functionality. Focus on creating relationships that are specific to your infrastructure.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC ProactiveNet 9.6