Thanks for the replies - just to clarify: we have dtquery up & running, but it's not exactly what we're looking for. Our folks would like to run some kind of report like "show me the downtime for these 10 hosts within the last 14 days" - which should be a classical case for a database... but it's beyond my perl knowledge to use dtquery as an example for a new program to store values from dt.log in a database. And I think a better solution would be to stored the data directly via the alert. I'll have a closer look at fping.monitor, looks like it's still simple enough that even I can understand it! :-)
I'll also have to take a closer look a mrtg again (which we've got installed as well). So far we've only used it for general traffic monitoring on our routers and as far as I remember there's some build-in data compression with the graphics, so with long-time logs, the data becomes more and more fuzzy... which is fine for traffic stats, but with a database, we could re-generate precise downtime information whenever needed. Thanks again Uwe -----Urspr�ngliche Nachricht----- Von: Andrew Ryan [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 11. Januar 2002 19:58 An: Kreibaum, Uwe Cc: [EMAIL PROTECTED] Betreff: Re: logging to database and severity At 12:43 PM 1/11/02 +0100, you wrote: > I had a look at dtquery but must >admit >that it is far beyond my current perl know-how to adapt it... dtquery uses mon-generated downtime logs as its 'database'. It may not be what you want or need for your case however. The nice thing about it is that it gives you a query interface and doesn't require any extra work past enabling downtime logs and setting up dtquery initially. >Furthermore, I'm looking for a way to classify the failures reported by >fping: what you describe here is possible by modifying the fping.monitor. You could easily add a flag that calculated the # of hosts that it was passed, and only gave an error if a certain number, or percentage of those hosts, were marked as unreachable. This would be pretty simple perl. Definitely leverage the 'exit=' flag for sending out different alerts. andrew Nachricht wurde von MailSweeper gescannt.
