I'd still recommend Nagios to do the monitoring, far cheaper than hiring someone to do the checking 24*7. Also you'll get an instant notification of when things go bad, rather then in 2 hours time when someone checks it.
You could setup 2 instances of nagios.. get them to monitor each other and then also mirror everything that will be monitored onto each of them. You;ll get two alerts if things go bad, but that's better than none. A faq on nagios monitoring tomcat.. http://nagios.org/faqs/viewfaq.php?faq_id=310 On 5/24/07, Mark H. Wood <[EMAIL PROTECTED]> wrote:
On Thu, May 24, 2007 at 03:03:12PM +0530, Praveen Kumar wrote: > It seems this is also one type of tool. Here again we have some problem > ie we should monitor this tool too right ? > > So instead installing new tool to monitor tomcat server , is there any > feature that apache group provides to inform tomcat server status ? There is an insoluble dilemma here. If you use a separate process to monitor your server, then that process must also be monitored. Eventually you have two processes watching each other, whatever else they may be doing. If you do *not* use a separate process, then your server can only report its state transitions if it is still able to do so. A crashed process cannot tell you that it has crashed; the most you can get is that it will begin failing to tell you that it has *not* crashed. To get complete coverage can become quite elaborate. To protect against hardware failure, you need two machines monitoring each other. To protect against network or utility power failure, you need two (or more) machines monitoring each other from different sites. At some point as this scales up, it may be more sensible to just hire somebody to watch screens and check things periodically. -- Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] Typically when a software vendor says that a product is "intuitive" he means the exact opposite.
--------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
