[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [hobbit] single alert for a host going puprle
- To: hobbit (at) hswn.dk
- Subject: Re: [hobbit] single alert for a host going puprle
- From: "Hezki Englander" <me2unix (at) gmail.com>
- Date: Tue, 13 Nov 2007 19:01:19 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=ymAchcyrBEK8EcFPPDs9eLcure6AShCQWbKH546de+4=; b=t1GvN1FKzPuU28aSNa588QRCbmy9ixxtn3bIeXTdcBO+ymI9aMBB5JyNcu/D+hfdSwK60SrAySckSN3mGD3d2CxGKXnTJ2lr1dVMxMKyIjvZP/65Bc06F2xsP4PasgcazxcBwQGu+210SkticJKZbOvKCrmfCtmxgDzeNN2qxhc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=nu83e044pH4nYDNHEv35j6X4RW4FPSiavVOCFaZ41mmam2ERoY2YQzK+CWpcoIOib6QuboMnuG7C2+AVA2Bsrv2UHygGUry7DSJvokOuWCok+ZzengaA5J4AuINoEE5dUpSBAa3lEMgMONkH250dF3VZdSSx9howPMzW9/rK8hs=
- References: <46ac0d930711130654q2778abf8ycc7cde00e5be534 (at) mail.gmail.com> <961092e10711130824qde48148i76dfc466b4c092b3 (at) mail.gmail.com> <4739D100.4000001 (at) steria.com> <961092e10711130848s31583280y4831229989064cb1 (at) mail.gmail.com>
Thanks but I'm not asking about how to avoid having purple dots at all.
When you are monitoring a large amounts of clients, it is quite likely to
have a client not reporting once in a while.
This is why I am asking for a solution to reduce the amount of notifications
per host in case of everything from it is getting purple.
On 11/13/07, Josh Luthman <josh (at) imaginenetworksllc.com> wrote:
>
> Well your first problem there can't really be avoided unless the person
> modifying the firewall rules is more on top of their game.
>
> The second issue you can easily have it start up when entering runlevel 3
> (what a lot of people use out there, remainder of them being 5) but doing an
> ln -s /etc/init.d/hobbit /etc/rc3.d/S82hobbit
>
> I have never seen Hobbit crash, but I have only been using it for upwards
> of a month or two. Still, a crashed hobbit won't disallow ICMP echoes.
>
> Josh
>
> On 11/13/07, Frédéric Mangeant <frederic.mangeant (at) steria.com> wrote:
> >
> > Josh Luthman a écrit :
> > > Let me understand your situation. You have one host, IE:
> > >
> > > 1.2.3.4 <http://1.2.3.4> mybroken.host.com <http://mybroken.host.com>
> > > # ssh dns pop3 smtp http://mybrokenhost.com < http://mybrokenhost.com>
> > >
> > > Now after some time you have ssh and dns going down, but the box is
> > > still green on conn/ping? Logically, there are two problems - bad
> > > bind and bad opensshd, so two alerts is a wise choice.
> > >
> > > If you are saying with the example above that every test goes down
> > > because it is offline, in my case at least, it only gives me one alert
> > > - bad conn, the rest are tagged with "depend" essentially and don't
> > > alert you. Is this not the case for you?
> >
> >
> > Hi
> >
> > there are various situations where a host responds to ping but does not
> > send any status to hobbitd :
> > - firewall rule modified, so no connection from a server to the hobbitd
> > daemon allowed
> > - Hobbit client not run automatically after system restart
> > - Hobbit client stopped, hung, etc.
> >
> > --
> >
> > Frédéric Mangeant
> >
> > Steria EDC Sophia Antipolis
> >
> >
> >
> >
> > To unsubscribe from the hobbit list, send an e-mail to
> > hobbit-unsubscribe (at) hswn.dk
> >
> >
> >
>
>
> --
> Josh Luthman
> Office: 937-552-2340
> Direct: 937-552-2343
> 1100 Wayne St
> Suite 1337
> Troy, OH 45373
>
> Those who don't understand UNIX are condemned to reinvent it, poorly.
> --- Henry Spencer
>