>
> >
> > Many of the "Monitoring" reports don't work well at volume, I've been
> > asking users to only use "Unhandled" reports. You may get better
> > response in Mozilla, but 'status.cgi' can kill Internet Explorer
> > because of how it's loading everything in one large list.
>
> This is a browser rendering issue, nothing to do with the nagios' speed
> at reading and parsing its status file. To get the html to display
> status for all 3800 of my services takes under 1.5 seconds --
>
In my case it is not the browser issue. The problem is that status,cgi does
not return data rather than the data it generates is so big.
And status.cgi hog cpu time at the monitoring host (not the desktop viewing
using a browser)
I guess there are something wrong with status.cgi and even the
extinfo.cgitake considerable amount of cpu as well
Thanks
--
Steve Kieu
Mob: (+64) 021 250 6437
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Nagios-users mailing list
Nagios-users@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
