We have hostgroups with 150 - 250 hosts... and since dtlog lacks the
details we need, we finally hacked a programm to analyze monhist.log
- we configured an empty alert (just alert.template), so that every
alert gets logged with the date and the failed hosts. It takes a bit
of data shuffling, but in the end you can at least get a host-based
list of downtimes which can easily be fed into some database for
further processing.
We tried to use rrdmon, but installing mon with 2.000 hostgroups
is not that funny and monitoring it via mon.cgi is just impossible.
We still need another tool to monitor the lines in shorter intervals,
right now we're doing it in 10 min intervals which is sufficient
for internal use but we'd rather need 1-2 minutes.
Uwe
-Ursprüngliche Nachricht-
Von: Andrew Ryan [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 5. Juni 2002 21:21
An: alan evetts; [EMAIL PROTECTED]
Betreff: Re: dtlogging in combination with mon.cgi
On Tuesday 04 June 2002 03:15 pm, alan evetts wrote:
It seems that mon has built in dtlogging.. and mon.cgi likes to display
this, too. which is really helpful _except_ for the part where it only
seems to display group/service downtime - not group/host/service.
Since the concept of a 'host' doesn't officially exist in mon as of yet,
this
is kind of impossible unless one does unnatural stuff with parsing the
dtlog.
I say 'unnatural' because one is reliant upon the monitors to output the
failed hostnames in the summary line (which some monitors don't do), and for
the dtlog to accurately track failing hosts, which it doesn't.
For example, if hostgroup contains hosts A,B,C, let's say host A fails. The
dtlog may record that A failed, assuming your monitor is well-behaved. If B
fails 2 minutes later, while A is still down, this doesn't get recorded in
the dtlog. If A comes back 2 minutes after B fails, and B is down for 2 more
days while A is up, the net result is that the dtlog thinks that B was never
down and A was down for 2 days.
I'd love to be able to reflect back and see precisely which server in a
hostgroup (I have up to 10 in each), and which service failed.
Me too, that's why I wrote dtquery. I suggest you give it a try. dtquery at
least makes guesses and has a nice (IMHO) query interface to boot.
http://www.nam-shub.com/files/dtquery/
Does anyone have a patch or a method for doing this?
I'd rather not use
any additional software to store the stats.. as the way the downtime log
in
mon.cgi is done is perfect for my use - just not detailed enough. I don't
want/need graphs, as if something failed once, a month ago for 5 minutes -
it'll be hard to see.. but in the way mon.cgi shows the dtlog - it is
quite
obvious.
I used the code from mon.cgi inside of dtquery to generate the same table
that you see in mon.cgi.
You don't actually need to generate the graphs with dtquery. If you don't
install the graphing programs, you get just the information it sounds like
you're looking for.
andrew
Nachricht wurde von MailSweeper gescannt.
