Exclude specific alerts from SQL SERVER ERROR LOG ENTRY alerts
We have certain tools (mainly infosec related) that generate a lot of entries in the SQL server error log as part of their normal operation creating a lot of alerts. The only way to identify these and thereby determine that they are 'expected' is to go into each alert individually and mark it as read. The ability to ignore certain errors based on error number, severity or message would add a lot of value to this feature.
Anonymous
shared this idea
-
Tim
commented
This is really needed, every time we fail-over we get a couple hundred alerts that we would like to filter out.
-
Ash.Tickett
commented
Definantly very useful feature needed. We have a box that runs AlienVault which scans the network (including SQL Server) which causes a number of packet alerts. Would be useful if we can exclude the IP of the box that AlienVault runs on to avoid the huge number of alerts.
-
David Tawater
commented
Redgate SQL Monitor already has this functionality with Long Running Query Alerts. Can we also have this with the SQL Server Error Log Entry as well?
-
Roland Strauss, MCSE
commented
We monitor SQL Server with PRTG and a failover always creates this error. At least this should be an informational message
-
Chris Fox
commented
I have the same issue as Art, and it would be nice to be able to source-filter these alerts.
Thanks,
Chris F -
kerstin
commented
Would it be possible to have an exclusion like in long running queries?
Exclude entries matching the following regular expressions:
-
Art
commented
I would also like to see this feature. If an exclusion could be made related to the IP address of the machine causing the log entry, that would be one way to handle it. We have a program that scans our network and sql instances for vulnerabilities and every time it does this it throws up a bunch of sql error log entries at severity 20. I would like some way to exclude those from alerting me, without changing the severity level settings on the alert to something higher.