How to monitor the SQL Server Errorlog

Hi all,

I'm not sure if this is possible within SolarWinds, but is there a way that I could setup an alert to monitor for events within the SQL Server Errorlog?

I'd like to monitor for all kinds of errors eventually, but just as a trail run, I'd like to be alerted when a login failure event is written to the log.

I've been looking at doing this with the custom SQL Alert advanced setting but I keep hitting deadends.

Any help or recommendations would be greatly appreciated.

Thanks

Find more posts tagged with

sql

Events

Alerting

errorlog

monitoring

Accepted answers

All comments

weiss4m0n

Monitoring and Alerting/Paging based on Severity messages and or SQL errorlog message text (and being able to exclude based on message text) is such a basic DBA monitoring requirement but I also have been unable to find out how to do this with SAM. Anyone?

hallstev5

I ran into the same problem trying to monitor the SQL Error Log using default SAM templates. I composed a PowerShell script that monitors the SQL Error Log.

Uses the SQL Error Log Path as an argument for the script
I have it searching the SQL Error Log for specific conditions (in my case severity greater than 19)
The script alerts based on if a condition was found and the message is the condition that was found
The script maintains its position in the Error Log
- using xml file to store file location on the server that is running the script
It is set to run as a remote script
Writes the results of the script to a custom windows event log for troubleshooting purposes

Let me know if this is something that would be of interest and I can share it.

jameslindsay

Please do.

hallstev5

I have attached the a copy of the script that to the response. If you have any question about what it does or how it does it, please let me know. I hope this helps or is at least a starting point to get you guys going with monitoring the SQL Error Log. There is one thing that may fail with the script that i haven't fixed. If the path to the SQL Error log has a space in it, then you may have to hard code the path in the script instead of passing it. Just something i haven't gotten back to yet.

Check-SQLErrorLog.ps1