Administer > RTSM > RTSM Modeling > Modeling > Impact Analysis Manager > Impact Rules Definition Dialog Box

Impact Rules Definition Dialog Box

This dialog box enables you to set conditions for defining impacted query nodes, define the scope of the trigger conditions, and define the severity of the impact.

To access In the Impact Analysis Manager, click Add on the Details page of the Impacted Query Nodes dialog box.
Important information

  • In the Conditions area, set conditions for defining impacted query nodes. When this condition is met, the simulated change in the system is triggered.

    For example, you can define an Impact Analysis condition that states that the operational state of the query node is other than Normal. When the operational state of the query node instance changes and is no longer Normal, the condition is met and the simulated changes in the system are triggered.

  • In the Scope area, define how many instances of the trigger query node should fulfill the conditions for triggering the changes in the system.

    You can apply the trigger conditions to a single instance of a trigger query node, to a certain percentage of the trigger instances, or to all of them.

    For example, you can define that impact is calculated when at least 10% of the system’s nodes are down.

  • In the Severity area, define the severity of the Impact Analysis impact.
Relevant tasks Define an Impact Rule – Workflow
See also

User interface elements are described below :

UI Element (A-Z) Description
All All instances should fulfill the conditions.
Any One instance or more should fulfill the conditions.
Description A description of the Impact rule you are defining.
Fixed severity Define a fixed severity level for every system change generated. Then, select the required severity level from the list.
Function

Select Function (displayed when you selected the All and Range options in the Scope area) to define a severity level for the system changes, as a function of the severity levels of all the trigger query node instances that are included in the range. From the list, select either Average or Max.

For example, if you select Average, the severity level of the system changes is the average severity of all the trigger instances.
Operator Select the required operator. For a list of the operators you can use for defining an attribute condition, see Attribute Operator Definitions.
Range A certain percentage of all instances should fulfill the conditions. For example, if you enter a range of 50% to 100%, the changes are triggered when 50% or more of the instances meet the conditions.
Severity relative to trigger severity (%)

Select Severity relative to trigger severity (%) (displayed when you selected the Any option in the Scope area) to define a severity level for each system change that is relative (as a percentage) to the severity of the trigger event.

Enter the percentage in the box provided.
State Choose the required state. The states that appear in the list are the states that are defined in the State Manager. For details, see State Manager.
Value comparison Select the required attribute.

Send Help Center feedback