Adjust impact rules for a CI

Configure impact rules to customize the impact calculation. The impact rules update the overall alert and show the impact on related CIs. When you change impact rules, the updates apply to alert severity in places such as the Event Management alerts console and dashboard.

Before you begin

Role required: evt_mgmt_admin, evt_mgmt_operator, or evt_mgmt_user

About this task

You can view and adjust the impact rules of CIs from the business service map of a service.

Procedure

  1. Open the business service map from either the Event Management dashboard or the Manual Services list.
    OptionDescription
    From the Event Management dashboard
    1. Navigate to Event Management > Dashboard.
    2. Double-click the tile of the service.
    From the Manual Services list
    1. Navigate to Event Management > Manual Services.
    2. Click View Map next to the service.
  2. On the business service map, click a CI.
  3. Below the map, click the Impact tab and then adjust the impact rules accordingly.
    Table 1. Impact Rules
    Field Description
    Name The name of the impact rule.
    • Application Cluster Member: Determines how application cluster members affect the overall impact of the cluster. For example, if a three-member cluster requires 70% Influence to set the severity for the entire cluster to Major, each member has 23% Influence (70% divided by 3). The severity of the entire cluster can only change to Major when all three members have a severity of Major.
    • CI Business Service: Determines how impact applies to parent or child entities that are part of a business service.
    • CI Impact: Applies to manual services. Determines the relationship between service members. The impact from child to parent CIs is always 100%. For example, the parent impact severity is derived from the child CI with the highest severity.
    • CI Parent in Application: Sets impact only on the parent entity.
    • Inclusion: Determines the impact on entities with a Contains relationship. This rule is read-only.
    • Infrastructure Dependencies: Determines the definition of impact propagation for CIs in infrastructure relationships.
    • Network Path: Determines how impact applies to parent or child entities that are part of a traditional network.
    • OS Cluster Member: Determines how host cluster members affect the overall cluster status based on a percentage or number of cluster members. For example, if a three-host cluster requires 50% Influence to set the severity of Major, each member has 17% Influence (50% divided by 3). The severity of the entire cluster can only change to Major when two or more cluster members have a severity of Major. The entire cluster is also considered to be down.
    • Storage Path: Determines how impact applies to parent or child entities that are part of a storage network.
    Impact On The valid type of service for this impact rule.
    • Business Service: The impact rule applies to a business service. Not available for a manual service.
    • Parent: The impact rule applies to the parent CI.
    Influence The value to allow the impact rule to set on the parent. Set a value on the parent and each child. This field works with the Influence Units field.
    Influence Units The unit of measurement to show impact on the parent. Set the highest value on the parent CI. Set lower values on each child CI. When alerts occur for several child CIs, Event Management calculates the sum of the Influence Units of each affected child. If the sum exceeds the parent Influence Units value, the parent receives the highest severity in the set. This field works with the Influence field.
    • Percent: When the percentage exceeds the Influence value, apply the impact on the parent.
    • Number: When the number exceeds the Influence value, apply the impact on the parent.
      For example, you can set the parent Influence Units to 100% and the child CIs to these values:
      • Child 1: 40%
      • Child 2: 40%
      • Child 3: 40%
      • Child 5: 70%
      When alerts for Child 3 and Child 5 have the Critical severity, the severity of the parent is set to Critical because the sum is greater than 100% (40% + 70% = 110%).
    Impact when Critical The alternative impact to use when the calculated severity is Critical. If the column to the right of Impact when Critical has a higher severity, update all right-most columns with the same or a lower severity as Impact when Critical. To make sure the topology and impact tree accurately show impact, always update each column accordingly.
    • Critical: Red (highest severity).
    • Major: Orange.
    • Minor: Yellow.
    • Warning: Blue (lowest severity).
    Impact when Major The alternative impact to use when the calculated severity is Major. If the column to the right of Impact when Major has a higher severity, update all right-most columns the same or a lower severity as Impact when Major. To make sure the topology and impact tree accurately show impact, always update each column accordingly.
    • Critical: Red (highest severity).
    • Major: Orange.
    • Minor: Yellow.
    • Warning: Blue (lowest severity).
    Impact when Minor The alternative impact to use when the calculated severity is Minor. Controls the field values to the right of this field. If the Impact when Warning column has a higher severity, use the Impact when Minor value for both fields. To make sure the topology and impact tree accurately show impact, always update each column accordingly.
    • Critical: Red (highest severity).
    • Major: Orange.
    • Minor: Yellow.
    • Warning: Blue (lowest severity).
    Impact when Warning The alternative impact to use when the calculated severity is Warning. To make sure the topology and impact tree accurately show impact, make sure that the columns to the left have higher severities.
    • Critical: Red (highest severity).
    • Major: Orange.
    • Minor: Yellow.
    • Warning: Blue (lowest severity).

What to do next

Review the changes on the impact tree. For example, if you changed a number or percentage influence for child CIs, review the impact tree updates accordingly.