Jump to: navigation, search

Alert Metrics

The following Table lists alert metrics.

Name Internal Name Description Source Type
Action Taken AlertActionTaken
Business Priority 1 Alerts AlertB1
Business Priority 2 Alerts AlertB2
Cause AlertCause
Duration ViolationDuration If the alert is inactive, use the start time minus the real end time. If the alert is active, use the start time minus the current time. The format is hh:mm:ss. Calculated
End Date AlertEndDate The date when the alert expired.
End Time AlertEndTime The time when the alert expired.
Max Violation The highest or lowest value of the violation Calculated
Start Date AlertStartDate For an alert, the start date is when the alert actually started, even if that is before the time period in the user's filter.

For a key action report, display the Key Action Date from the Action Management page.

Start Time AlertStartTime From the carousel; the time when the alert was triggered (hh:mm:ss).

For a key action report, display the Key Action Time from the Action Management page.

Success Rating AlertSuccessRating The value from the Success Rating drop-down list on the Alert Management page.

(3, 2, 1, 0, -1, -2, or -3) If multiple key actions exist show the highest success rating of all of the key actions.

Success Time AlertSuccessTime The violation end time and date minus the key action start time and date, where the key action has a success rating greater than 0 (equal to 1 or 2 ).

The format is hh:mm:ss.

Calculated
Technical Priority 1 Alerts AlertT1 An alert row displays T1 or dashes.
Technical Priority 2 Alerts AlertT2 An alert row displays T2 or dashes.
Threshold This column displays the acceptable value used to calculate the max violation. In WA, the acceptable value is a range so use the closest acceptable value. For example, if the acceptable range is 20-30 and the max violation is 40, display 30.
Value at Max Violation The worst metric value used to calculate the max violation.
This page was last edited on March 27, 2015, at 15:02.
Comments or questions about this documentation? Contact us for support!