Environment
Redline 3.5.1 build 1011 or higher
Situation
The purpose of this document is to provide step-by-step instructions for enabling Back To Normal alerts on Redline Alerts.
Resolution
Back to Normal Alert is a feature designed to automatically manage alerts that occasionally exceed their conditions and then return to normal shortly thereafter. An example of this may be a mail queue from an email blast, or number of threads in use on an agent. Back To Normal does not rely on any other setting to function. However, if used with Self Correction Delay, Back To Normal will not solve alerts that resolved within the first loop. See the article detailing Self Correction Delay for more information.
To enable Back To Normal on an alert, open the properties of any alert from Configure | Thresholds/Recommendations.
Alternatively, this can be done using the configurealert icon on the Alerts page.
When enabled, a Back to Normal type of notification is generated through the alert system when the condition returns to normal. The alert is marked solved with "BackToNormal" as the user and it is removed from the Alerts page. This is done without any need for administrator intervention. The email address assigned to the alert will receive an email containing the string "BackToNormal" indicating the alert has been resolved. EXAMPLE: Let's assume the following alert was triggered in Redline and the email notification below was sent. Shortly thereafter another email notification was received when the condition returned to normal.
Subject: Alert: (2)-Voyager.Intrepid->poaAVAILABLE_GWCHK_THREAD should be > 2, but is 0 Date: 11-30-2011 Time: 14:18:34 Severity: Minor Error: (2)-Voyager.Intrepid->poaAVAILABLE_GWCHK_THREAD should be > 2, but is 0
Subject: Alert: (2)-Voyager.Intrepid->BackToNormal: poaAVAILABLE_GWCHK_THREAD should be > 2, but is 8 Date: 11-30-2011 Time: 14:20:33 Severity: Minor Error: (2)-Voyager.Intrepid->BackToNormal: poaAVAILABLE_GWCHK_THREAD should be > 2, but is 8
Additional Information
This article was originally published in the GWAVA knowledgebase as article ID 2027.