[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [hobbit] Highlights of the 4.3.0 version
- To: hobbit (at) hswn.dk
- Subject: RE: [hobbit] Highlights of the 4.3.0 version
- From: "Kern, Thomas" <Thomas.Kern (at) hq.doe.gov>
- Date: Fri, 3 Aug 2007 11:31:28 -0400
- References: <200708030831.29685.bgmilne (at) staff.telkomsa.net> <483387BD5310504F95897573FF3E350D04C23A4A (at) dpex.dpcorp.internal> <6C2B32F89382AF42875672B6F5BEB682038E8FD8 (at) MERCMBX07.na.sas.com>
- Thread-index: AcfVmExhwts47R8IQ8KHawajThfqHwAQ5N/wAAFS7nAAAHcfcA==
- Thread-topic: [hobbit] Highlights of the 4.3.0 version
When a monitoring system detects something wrong, the only actions I
want the monitor to perform is to get the admin (or the admin's boss)
moving to diagnose and fix the problem.
And I am the admin that I am most concerned with. I don't understand
most of the errors well enough to automate a recovery process.
/Thomas Kern
/301-903-2211
> -----Original Message-----
> From: Galen Johnson [mailto:Galen.Johnson (at) sas.com]
> Sent: Friday, August 03, 2007 11:18 AM
> To: hobbit (at) hswn.dk
> Subject: RE: [hobbit] Highlights of the 4.3.0 version
>
> DOn't forget...this is the model that Tivoli and HP Openview, and many
> other commercial monitoring solutions provide and sell as a feature.
> From my experience as a sys admin, I've alwys found that automatically
> restarting a service if it goes down to be "a bad thing"(TM).
>
> In many solutions, logs get overwritten upon a restart that would be
> integral to the real resolution and prevention.
>
> =G=