Commercial Support Clients: Clients with support contracts can get escalated support assistance by visiting Nagios Answer Hub. These forums are for community support services. Although we at Nagios try our best to help out on the forums here, we always give priority support to our support clients.

Re: [Nagios-users] RE: [Nagios-devel] MSQL Tables and log files mis-match in data types, any ideas

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.

Re: [Nagios-users] RE: [Nagios-devel] MSQL Tables and log files mis-match in data types, any ideas

Postby Guest » Fri Mar 29, 2002 1:06 am

Ethan Galstad (nagios) writes:
> I've updated the "upcoming" page (http://www.nagios.org/upcoming.php)
> to reflect a bit of what I was thinking. Dumping data into a DB
> would be handled by an external daemon of some kind.

So, would this be some kind of API that all CGIs and the core would
share, but would be completely abstract ? I'm thinking about some
normalized set of functions to put/get the data (get_host_info(),
update_host_info(), ...), which could very well be implemented on
the back-end as DB, DBM, flat file, ...

A comment on "Apache Module For Faster CGIs?" at

You say:

"The reason for the major slowdown is the fact that the CGIs re-parse
all the configuration files every time they're hit. This is very
expensive CPU-wise when you've got a large number of hosts/services
in your configuration."

And you suggest as a possible solution:

"I'm not exactly sure what to do about this, but one solution might be to
write an Apache module that caches the config information (and possibly
the status information) in memory, refreshing it at set intervals (say
15 seconds or so, only when needed). The CGIs would then read the
cached config/status data from the module rather than parsing the raw
config files and status data all themselves."

I read you right, each CGI would talk with a "mod_nagios" every
time they were called, and get the cooked configuration passed to them.

The approach is the right one (pre process the config info), but
I don't know if making it Apache specific is the best way -- possibly
another way would be to use a persistent handler for the whole hierarchy


_ _ |_ || regnauld@catpipe.net catpipe Systems ApS |
(_(_||_ || *BSD solutions, consulting, development |
|| Tlf.: +45 7021 0050 http://www.catpipe.net/ |

This post was automatically imported from historical nagios-devel mailing list archives
Original poster: regnauld@catpipe.net

Return to Open Source Nagios Projects

Who is online

Users browsing this forum: No registered users and 27 guests