Wow, the addition of a join between my log db (which is a text ODBC driver) and the SA db would be both tricky (MS SQL linking to Text DBs has always been problematic) and slow (two DBs on 2 servers). So, this solution dies on the drawing board (at least for my situation). I also could use this for other checks besides ODBC. We have one setup that monitors the number of files in a directory. These files normally get processed by one of our integration servers, but if it gets slow or fails, then these files start to pile up. If I had the option for "and every time the result changes" I would know how the service is doing, rather than just an UP or DOWN.
Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] (mailto:[EMAIL PROTECTED]) 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com (http://www.saddlecrk.com/) -------------------------------------------------------------------------------- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jason Passow Sent: Tuesday, April 10, 2007 9:36 AM To: Servers Alive Discussion List Subject: Re: [SA-list] feature request for v7 I have been thinking about how to get a similar result. We monitor a fax queue but since we are attempting to avoid printing statements and mailing them we have had a lot of customers switch to faxed invoices. I would like to monitor if the queue is not only down but not getting better. i.e. An alert when there are more than 20 files but only if the result has not gone down since the last check. I could to use a change in V7 that would keep track of last check result in a temp file or something. I also recall other reasons for people wanting this. All of that being said I think you could accomplish the same thing since you already indicated you are using the odbc check. We are currently logging all check results to a DB and generating web pages from it. Therefore we could write a check that subtracts the most recent result form the check in question with the previous result and alert if the result is not positive (either unchanged=0, or increased=-x). You should be able to accomplish the same thing. Now Dirk I want to say that I appreciate the work you do and I don't want the fact that we can accomplish what we are looking as a reason not to change it V7. The reason being since check results are not logged to the database until the end of the cycle I would always be one cycle behind on my checking and therefore alerting. This is one of the limitations of my solution above and reason enough to CONSIDER the change for V7. (sorry everyone if I rambled I have not been sleeping much). Jason Passow Mississippi Welders Supply [EMAIL PROTECTED] ph: (507) 494-5178 fax: (507) 454-8104 "If you do everything right, nobody will realize you've done anything at all." Michael Shook wrote: That may be, but how do I set it up? If I just set another threshhold, how will I know when it is exceeded again with more errors? If this is a cascade event (where things go bad and keep going that way) how would one or two additional checks help? Then two by adding more checks, I increase the administrative over head of maintaining them. I realize that this would necessitate SA keeping "hold" of the previous result, but, then that's why it's a request for v7. Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation [EMAIL PROTECTED] 863 668 4477 (work) 863 665 1261 (fax) www.saddlecrk.com -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Viktor Sokol Sent: Monday, April 09, 2007 5:11 PM To: Servers Alive Discussion List Subject: Re: [SA-list] feature request for v7 Hello Michael, IMO will be much faster to setup additional alert(s) for each event "getting better" and "getting worse" depending on primary. Monday, April 9, 2007, 4:50:12 PM, you wrote: Can I get an alert option for "and every time the result changes"? For example I have an ODBC check that returns the number of errors in a log table for a given period of time. We have a master query that is "DOWN when there are more than 3 errors in the last twelve hours" This works a treat, but if during the 12 hours while the initial 4 errors age, I get 2 more new errors (now 6) I'd like a new alert to go out, thus I know things are getting worse. Similarly, if things start out at say, 8, then go down to 5, I'd like an alert to go out so I know things are getting better, but still down. Thanks!! -- Best regards, Viktor mailto:[EMAIL PROTECTED] To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. -------------------------------------- The information contained in this message is intended only for the use of the addressee. If the reader of this message is not the intended recipient or agent of the intended recipient, you are hereby notified that any dissemination, distribution, or copying of the message is strictly prohibited. To unsubscribe send a message with UNSUBSCRIBE as subject to salive@woodstone.nu If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
