In my experience, I have to agree. Hobbit is for monitoring so the
information that x is down gets to people who can properly diagnose what
is going on, not take generic actions. If generic actions were
something that were required for X to function properly, it should be a
feature of that software.
Hobbit CAN do some scripting based on alerts, but even that might be a
bit more than a systems administrator wants to hinder himself with.
Tod Hansmann
Network Engineer
-----Original Message-----
From: Buchan Milne [mailto:user-9b139aff4dec@xymon.invalid]
Sent: Friday, August 03, 2007 12:31 AM
To: user-ae9b8668bcde@xymon.invalid
Cc: Hubbard, Greg L
Subject: Re: [hobbit] Highlights of the 4.3.0 version
On Tuesday 24 July 2007 22:55:02 Hubbard, Greg L wrote:
Wonder if there is any way to tell a client what it's status is so it
can be autonomous? What I mean is this: suppose there was a way for
the Hobbit client to tell the server that service X was now in state
Y,
and a client-side module could then activate response Z on its own?
I don't like band-aids like this.
"restart because it's down" prevents the real impact of problems being
seen,
and provides less motivation for fixing things properly. Instead, you
sit
with frequent short outages (which may avoid the attention of managers,
production managers) which have end-user impact.
I like even less using a monitoring system to do this ...
Regards,
Buchan