Monitoring error (SQL Server data collection) - SAVE THE ERROR LOG
When one of these occurs it is 99.999% likely that, in the middle of the night, I will NOT jump out of bed, fire up the laptop, connect to the SQL Monitor Server and look at the SQL Monitor Error Log IN THE 5 MINUTES I HAVE BEFORE THE ENTRY IS LOST! May I cite the "Description" tab in SQL Monitor: "If the alert is still Active, or it Ended within the last five minutes, you can find out more information about its cause..." So we, ANYONE THAT IS, has a mere FIVE MINUTES to react to this before "see ya!". May I respectfully say, "that's idiotic and unrealistic" - who of us is glued to our SQL Monitor Alerts like that!?
Please, put these log entries SOMEWHERE ELSE so we can actually see what triggered the Alert in the first place! Better still, put ALL associated Log Entries as collateral data with the Alert!
I had a 3-minute outage shortly after midnight over a weekend. Despite sending myself an email to my personal account, do you think I leaped up? Not having a company smart phone means I don't have text alerts. Perhaps the RG assumption is that all DBAs on Production Systems have such devices...?
So, for the dinosaurs among us, and for simply doing a good job of reporting errors of this kind for everyone, please snag the data and show it me in the Alert itself.
Completed in SQL Monitor 5.0.3
@luke: apologies for the offense caused. I believe my frustration level overspilled when neither the SQM log nor anyone at Rackspace could enlighten me as to the cause.
While Stephen 's tone is somewhat over the top, I also agree that persisting this type of monitoring error can be of great help when troubleshooting issues. Particularly the intermittent kind in the middle of the night. Even If I get paged by it It's unlikely that I'll be able to get out of bed, boot my laptop and log into my VPN within the 5 minutes that the log data is available.
Perhaps this could be added to a log with a 24 hour retention?
Thanks for suggesting how we could improve this and explaining why it's a problem. We'll certainly consider this suggestion.