I believe Dirk prices SA very fairly and the purchase of multiple copies should not be problematic for all but the smallest installations. The free version is always available for up to 10 checks. That's what I've used to monitor my main SA system for a while now.
-Kevin -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Hay Sent: Friday, February 18, 2005 11:05 AM To: 'salive@woodstone.nu' Subject: RE: [SA-list] Major product checks missing? If this is a code re-write scenario than I wonder if there is a compromise to having a 2nd copy on the same network, different box running additional checks and having the additional benifit of 'watching the watcher' and letting us know if the SA service is down on the other system. Maybe a reduced cost for additional copies on the same company. This could have the added benefit of being able to decentralize your monitoring. I believe the idea was brought up earlier about lowering the cost for subsequent licenses and I think we'd be down for that as a solution. Steve -----Original Message----- From: Kevin Stone [mailto:[EMAIL PROTECTED] Sent: February 18, 2005 8:02 AM To: salive@woodstone.nu Subject: RE: [SA-list] Major product checks missing? I am also at ~1500 checks and could add 3-500 more. Every couple of months I ping Dirk about threads and parallel checks. My understanding is a complete rewrite of the check code with a set of new tools would be required. I don't know how many of the SA community are or could be in the 1000+ check range and if it would be worth the development cost. That, of course, is Dirk's decision. To mitigate the cycle times I've done many of the same things. Lower priority checks happen less often, I've lowered the timeout on pings, reduced the number of web pages generated etc. I also made a change in the registry to lower the "PerItemCycle" value. This made a huge difference on my system. SA works extremely well in our environment despite our pushing it beyond its normal scope. A comment was made to me the other day that my monitoring system(based on SA, Kiwi tools, and PHP) is much easier to use and more informative than the corporate Concord system. That's a testimony to the usefulness built into SA. -Kevin _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Hoermann Sent: Thursday, February 17, 2005 4:18 AM To: salive@woodstone.nu Subject: RE: [SA-list] Major product checks missing? I concur, although let me share my "workaround" to the long amount of time for a check cycle to complete I have been using Servers alive since version 2, and over the past 5 years my hostfile has grown to around 2000 checks in total across 10 sites, with wan speed dictating that some service, disk space and count file checks taking up to 5 seconds per check. (you do the math) I've since grown a brain and paired down my entries to around 1450, removing stupid checks like terminal services, leaving bare essential, production / workflow affecting checks. Recently I went through and thought of how I could decrease the cycle time. All of my disk space checks I have chose now to do every 20 cycles. Service checks against things like server scan service form trend I run every 20. Service checks which are annoying to us if not running, although don't affect the user community, eg: exchange sa, I've reduced to one check every 50 cycles. Mail queues and information store checks, sure I still run every cycle, since if these aren't running, my support guys are gonna start getting phone calls. My scope was if a check fails, and I wouldn't get a call from users about it straight away, I now only check it every 5 cycles. By going through all of my entries I got my cycle time down from 20-25 mins to around 5-6 mins. Sure, the first cycle is going to take some time if the checks are set to start on first cycle, but the return is worth the bit of time of configuration. My 2 â cents worth Peter Please note that Internet email is not always private, secure or reliable. The sender accepts no liability for any damages caused by any virus inadvertently transmitted with this email. Any opinion expressed in this email is solely that of the author, unless clearly indicated otherwise. This email, and any attachments, may contain confidential and/or proprietary information that is intended only for use by the addressee. If you are not the intended recipient, any use, dissemination, forwarding, printing, or copying of this email is strictly prohibited. If you received this email in error, please delete the email and advise the sender of the delivery error. To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
