Oh, alright. I didn't know that it is so old. Well seems logic now that you used so complicated method as you didn't have export we got in the v6. Thx, I'll look through it again.
-----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Wednesday, September 26, 2007 12:21 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring Oh, don't get me wrong. What I did is EXTREMELY complicated, but I wrote it during version 4 of SA, so that was what I had to work with. I'm merely pointing out that you can roll-your-own uptime monitoring if necessary, and use what I did as a place to start. Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation 863 668 4477 (work) 863 665 1261 (fax) My time zone: UTC -0400 (Eastern Daylight Time) -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr Bohac Sent: Tuesday, September 25, 2007 4:11 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring I was there and I didn't like it. If I remember correctly most of them involve sql scripts and I'm no sql scripter. The method I'm using is much easier to implement plus you get uptime for month, year etc. Btw what's better in your method? I found it rather ... Complicated to setup and to maintain. Petr -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Michael Shook Sent: Tuesday, September 25, 2007 11:51 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring If you go to the Users Group, you'll find the rather involved method I have in place to manage uptimes. SAUG.snarkybox.com Michael D. Shook Systems Analyst - Data Integration Saddle Creek Corporation 863 668 4477 (work) 863 665 1261 (fax) My time zone: UTC -0400 (Eastern Daylight Time) -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr Bohac Sent: Tuesday, September 25, 2007 3:36 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring Ok, thanks. C'mon, the others, every manager wants to see a nice uptime charts of their servers :) -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, September 25, 2007 3:41 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring It will surely not be in the next build of SA. Maybe in a new version....we'll see how other re-act on it.... Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr Bohac Sent: Tuesday, September 25, 2007 10:16 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring Yeah, I know it's a unique key. So my question is could you implement it into next build of the SA? -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, September 25, 2007 11:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring The UID gives you the possibility to link it to the weboutput, to the other db loggings, that's the reason for having the uid. Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr Bohac Sent: Tuesday, September 25, 2007 8:40 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring Yes, description would be fine too. The UID is at least for me useless for any report. Ad to MOM: the SA is less accurate because a cycle takes ~5 mins. During that period some fast system could go to BSOD, restart and boot up without any notice. This is not case of the MOM as it have agent installed on the monitored server and update period is more frequent. Petr -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Tuesday, September 25, 2007 10:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Uptime monitoring If we include the hostname/prettyname then why not a check description? What is the use of the UID then? And in what way is the logging less accurate then what MOM does? Dirk Bulinckx. -----Original Message----- From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Petr Bohac Sent: Tuesday, September 25, 2007 8:16 AM To: Servers Alive Discussion List Subject: [SA-list] Uptime monitoring Hi all, I'd like to re-open uptime monitoring thread. I find that the output from the SA is not suifficent. I mean we get only UID which si useless unless you pair it with another db (salive statistical logging) to get hostname and prettyname. Would be possible to add these 2 fields into uptime monitoring table? That would make a lot easier showing uptime for any manager ;) I've modified pretty easy asp script http://saug.snarkybox.com/index.php?topic=14.0 and get decent results. And I think it is good for for basic monitoring of systems uptime and to present some SLA (KPIs). For the accurate uptime monitoring I'm using MOM2005 but the licencing is pretty expensive so I'd like to stick w/ the SA for most of the systems. Petr This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] 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 [email protected] 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. This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] 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 [email protected] 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. This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] 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 [email protected] 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. This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] 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 [email protected] 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. This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] 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 [email protected] 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. This e-mail including any attachment is intended only for the recipient(s) named. It may contain confidential information and should not be read, copied or otherwise used by any other person. If you are not a named recipient, please contact the sender and delete the e-mail from your system. The sender does not accept any liability for errors or omissions in the content of this message or for viruses, or any damage due to the e-mail. The recipient is advised to have appropriate virus check software. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] 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.
