Nagios 2.0 performance

[Peter McAlpine]

I've been reading this thread and appreciate all the tips everyone has
to offer, but the time it takes the cgi's to load is obviously due to 
parsing the log file for each execution... unfortunately:
*Parsing the log file each time status.cgi runs is just plain silly*

Status should be stored within nagios, and the cgi's should query
nagios (not the log file) for status. 
OR
Status should be stored in a database.
If supporting multiple databases is a problem:
-Say "too bad, only foosql is supported" (mysql runs on MsWindows btw)
-Use something like ODBC to make the database more portable.

I know you may say, "then implement this yourself", and I may do just
that... but the speed of the cgi's is something that comes up on this
list regularly, and improving the situation would be very very good.

-Peter

On Thu, Sep 09, 2004 at 06:39:37PM +0200, Andreas Ericsson wrote:
> Ben wrote:
> >Why did nagios 2 drop db support?
> >
> 
> Because it was ass to maintain when people started requesting additional 
> features and asking "Hey, Ethan. Why isn't MSSQL supported?!".
> 
> Feel free to reimplement it if you like, but make sure you make it 
> easily extendable for both features and other database systems or it 
> will most likely be dropped again.
> 
> -- 
> Andreas Ericsson                   andreas.ericsson at op5.se
> OP5 AB                             www.op5.se
> Lead Developer
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM. 
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> 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
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <https://www.monitoring-lists.org/archive/users/attachments/20040911/7259236c/attachment.sig>