Nagios Log analyzer?

[Robert Drake]

Andreas Ericsson(ae at op5.se)@2004-12-03 00:01:57 +0100:
> 
> Nopes, but they will be ported sometime not too soon to php. Most likely 
> with a lot of modifications. I think I've got some status-parsing 
> routines for PHP if you're interested.
> 

Not quite the same question, but along similar lines. 

I'm about to start pulling my nagios.log into a SQL db, right now just
by pulling the logs, but later through the hooks they're adding in
nagios 2.

My nagios server doesn't have php installed so I was contemplating
writing perl frontends.  But, everyone talks about php so I may just use
it depending on how much I feel like writing the frontend.  

What I'd like to know is what's everyones current status on these
things.  I'm trying to avoid duplicating effort so I'd like to know what
everyone things about these things.

  SQL schema.  Event logs are pretty easy to represent (flat table) but
  it makes things easier if everyone represents them the same way.

  Generic calls for "backend" in the php/perl cgi's.  (So people can use
  the nagios flat file if they want, or postgres or mysql just by
  dropping in the needed stuff)

I guess those are my two big things.  I'm gung-ho to start working on it
because I think some of it would be fun and simple, but I'd rather not
finish something only to find out it's incompatible with everyone elses
stuff, and someone already has what I needed and I just didn't know
about it :)

Thanks,
Robert  

    



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null