Well I guess I could port HobbitClient to HP-UX. I will have to noodle
on that for awhile. I have tried to make it on 11i already and ran into
two issues. First I don't have err.h on my system and when I change
err.h to errno.h I get this make error which I have no clue as to why:
root at dev6:/var/tmp/hobbitclient-0.3 $gmake
bison -y -p`echo conf_parse.c|sed 's/^\([^_]\{1,\}_\).*$/\1/'`
conf_parse.y
gmake: *** [conf_parse.c] Error 141
I will make the assumption here that BB1.9e will work for my needs here
if I decide not to make the port?
This status lifetime parameter is very cool. I will add that now.
Thanks again for the info,
Tim
-----Original Message-----
From: Henrik Stoerner [mailto:user-ce4a2c883f75@xymon.invalid]
Sent: Tuesday, March 08, 2005 2:33 PM
To: user-ae9b8668bcde@xymon.invalid
Subject: Re: [hobbit] completely confused
On Tue, Mar 08, 2005 at 02:03:31PM -0600, Tim Rotunda wrote:
So just for clarification, before I start, I need to install the BB
Client for the OS level reporting to Hobbit. This is not the Hobbit
Client and if not, what is the Hobbit Client for?
The Hobbit client is a replacement for the BB client; however, it is
still a very new piece of software, and currently supports only
OpenBSD.
It is obviously annoying that Hobbit relies on the BB client to do
some of the monitoring, but things take time ...
I have had success in Hobbit enabling one of my apps and it works very
well. Only issue I see is that if the app takes a powder, Hobbit
Server
needs to alert me quickly. I am still looking for the "Time to
Purple"
parameter.
The way you control when the status goes purple is to set a lifetime
for the status when it is reported. Your application sends in a status
report that begins
status www,foo,com.mytest green ....
This gets the default lifetime of 30 minutes - meaning that it will
stay green for 30 minutes, or until a new status update arrives. If
you want it to only stay green for e.g. 10 minutes, then send this
instead:
status+10 www,foo,com.mytest green ....
The "+N" means that the status is valid for N minutes; after that it
goes purple. It is normally used to prolong the lifetime of a status
report, but you can shorten it as well.
Any help there would be great. I am going into a meeting on
Friday and will propose that we "Hobbit Enable" 10 or so of our "key"
applications. Our CEO has bought off on this and so it is just a
matter
of getting engineering to buy into it as well. This will enable our
IT
staff to respond very quickly to application failure.
Sounds great :-)
That will take care of about half of our remote monitoring needs. As
for the other half, I am still looking to deploy BB-Central, but
looking
at the scripts, it looks pretty tightly tied into BB so I am not sure
how successful I will be with that. I will begin this task after I
get
my Hobbit server reporting CPU, disk and such.
Let us know what problems you run into.
Regards,
Henrik