Server status proposal

[Mike Abbott <mj...@trudge.engr.sgi.com>]

I propose to extend Apache/2.0's server status report to allow any
entity within the server to report status.  I would do this by adding a
new hook (alongside pre_config, post_read_request, and the rest) for
status reporting.  Registered functions would emit free-form HTML
directly.  Mod_status would degenerate to simply sending headers and
wrapper HTML and calling ap_run_status().  The file
src/include/mpm_status.h and all the interfaces it describes would
disappear.

This would allow any module to report any kind of status it wants, from
MPMs reporting thread and connection status to caches reporting hit
ratios and third-party modules reporting back-end database performance.

Comments?
-- 
Michael J. Abbott        mja@sgi.com        http://reality.sgi.com/mja/

Re: Server status proposal

[dean gaudet <dg...@arctic.org>]

any module can already report any status it wants, it just needs to
register itself as a handler somewhere in the urlspace... and by way of
making a convention it might as well handle /server-status/mod/module_name

-dean

On Sun, 30 Jul 2000, Mike Abbott wrote:

> I propose to extend Apache/2.0's server status report to allow any
> entity within the server to report status.  I would do this by adding a
> new hook (alongside pre_config, post_read_request, and the rest) for
> status reporting.  Registered functions would emit free-form HTML
> directly.  Mod_status would degenerate to simply sending headers and
> wrapper HTML and calling ap_run_status().  The file
> src/include/mpm_status.h and all the interfaces it describes would
> disappear.
> 
> This would allow any module to report any kind of status it wants, from
> MPMs reporting thread and connection status to caches reporting hit
> ratios and third-party modules reporting back-end database performance.
> 
> Comments?
> -- 
> Michael J. Abbott        mja@sgi.com        http://reality.sgi.com/mja/
> 

Re: Server status proposal

[Mark J Cox <ma...@awe.com>]

> Registered functions would emit free-form HTML
> directly.  

I don't like that, lots of people use mod_status for automated discovery
of stats so then things like ...?auto would not work.  They'll end up
having to screen-scrape it.

How about registered functions emit XML and the status module can return a
XML status page, or a nicely marked-up version of such in HTML.  

Mark
Mark J Cox, .......................................... www.awe.com/mark
Apache Software Foundation ..... OpenSSL Group ..... Apache Week editor