Return
-
Title
Can a time duration be set before the SQL Server or Windows connection failure alarms fire? -
Description
There are instances where it is clear that network glitches are causing SQL Server or Windows connection alarms to fire. To minimize the email alerts from this alarm, can duration be set for SQL Server or Windows Connection Alarms so that unless the SQL Connection exceeds a time threshold, that alarms should not fire. -
Resolution
WORKAROUND:
Currently, Spotlight has an Alarm Action condition that states “where the alarm has existed for more than n minutes.”An enhancement request will be considered for adding for a condition that does the opposite: “where the alarm has existed for less than n minutes”.This will allow end users to write an alarm rule such as:For all alarmswhere the alarm is Monitored Server - Windows Connection Failureand the alarm has existed for less than 1 minutesuppress the alarmBy extending the Alarm Actions, it is also a more generic solution with other uses.STATUS: Enhancement request number has been submitted to Development for consideration in a future release of Spotlight on SQL Server Enterprise.
-
Defect ID
SOSSE-3866 -
Additional Information
The proposal is not add a duration to the SQL Server Connection Alarms. But currently, Spotlight has an Alarm Action condition that states “where the alarm has existed for more than n minutes.” We will consider adding for a condition that does the opposite: “where the alarm has existed for less than n minutes”. This will allow end users to write an alarm rule such as: For all alarms where the alarm is Monitored Server - Windows Connection Failure and the alarm has existed for less than 1 minute suppress the alarm By extending the Alarm Actions, it is also a more generic solution with other uses.