Using Collector to Run SQL Query....
We have a custom datapoint we built that runs a basic "select top 1" command to get application exceptions (which the app stores in SQL) from a remote sql server.
It appears that LM can only ...
Forum Discussion
This is great feedback....thank you both. Let me take this back to the team and see if we can use any of these ideas.
Mike: to your comments in your 2nd and 3rd paragraphs: we initially assumed these errors would be in a $log file somwhere, and we could just monitor that. But as it turns out, this application only logs these exceptions in SQL (from what we have found so far). These are 1 time events, and the log itself is fairly inactive/only throws events when there are exceptions (failed login, failed ETL job, etc.). To that point, we had an automated process fail because SMTP was not working upstream. So the ability to send data blob out through SMTP did not work. And our secondary stages for this ETL process depend on an automated mailbox task, etc. So we did not know there was an issue until $business told us...which is not good. Ideally, when the app throws this exception in SQL logs we are alerted. We will have to manually check why an exception was thrown and then check further...but it's better than nothing. In meantime, I am working w/ devs to find out if there's another point in the process we can detect failures. But it's very tricky to do dead man switches in email....
