Nagios performance info for cluster?

[Fabalabs Mailing-Lists]

Hello!

I'm looking for a possibility to view the performance info of a Nagios worker process in a clustered environment. (Because otherwise I will not see the statistics of the active checks, if all my checks are passively sent to the master)

The default behaviour of the extinfo.cgi?type=4 page is to display the Nagios process performance data of the local running master server.
Is there any parameter to tell Nagios (this CGI page) to display the performance data of another Nagios cluster node?
(The nagiostats utility can access those data by defining the configuration file of the worker process (e.g. -c /etc/nagios-worker/nagios.cfg))


By the way, is there any documentation of all possible Nagios CGI-parameters (for example for extinfo.cgi or cmd.cgi) that are allowed?


Kind regards,
            Klaus Pesendorfer.


Klaus Pesendorfer
Research & Development
Fabalabs Software GmbH
Honauerstraße 4
A-4020 Linz
Tel.: [+43] (70) 60 61 62
Fax: [+43] (70) 60 61 62-609
E-Mail: klaus.pesendorfer at fabalabs.org
Web: http://www.fabalabs.org <http://www.fabalabs.org/> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060927/a4d90123/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- next part --------------
_______________________________________________
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