How status computation algorithms work
The following table shows the type of value that a component status computation function returns when using an available algorithm:
What a function returns when using an available algorithm
Function | Algorithm | Returns |
|---|---|---|
self_function | HIGHEST_VAL | The highest value among the severities of the direct events, after they have been automatically mapped to component status values. The mapping between the event severity and the self_status CI is done by using the BMC_SEVERITY_TO_STATUS data table. |
impact_function | HIGHEST_VAL | The highest value among the status values of the provider components |
AVERAGE | The average status of the provider components after weighting each status value, where the "weight" is the number of providers propagating this particular status divided by the total number of providers propagating a status | |
QUORUM | The computed impact status is the lowest status that is propagated by the quorum percentage of providers (ignoring relationships propagating NONE) | |
consolidate_function | HIGHEST_VAL | The higher value between the impact status and the self_status |
SELF_PREFERRED | The self_status value except when it is NONE. In this case, computed_status is set to the no_alert_status value of the status computation model (by default OK ). |