Hello!

On Tue, Apr 13, 2010 at 10:12:12AM +0800, Weibin Yao wrote:

> Maxim Dounin at 2010-4-13 2:25 wrote:
> >Hello!
> >
> >On Mon, Apr 12, 2010 at 10:18:33PM +0530, Arvind Jayaprakash wrote:
> >
> >>This module provides a handler called upstream_status that can be used
> >>as follows:
> >>
> >>location /foo {
> >> upstream_status;
> >>}
> >>
> >>
> >>It reports all the upstream blocks configured for this server. For
> >>upstreams managed using the round robin (default upstream), it lists all
> >>the backends configured in a block and indicates the current status
> >>(up/down)
> >>
> >>http://github.com/anomalizer/ngx_upstream_status
> >>
> >>
> >>Improvements are welcome.
> >
> >Most important improvement is to document that it actually shows
> >configuration and status of upstreams in one particular worker
> >process which status request happened to hit.
> >
> The only method of showing all the status is using the shared
> memory, but is it worth of that?

I'm not suggesting to re-implement how upstreams are stored in
nginx. I'm suggesting to document what this particular module
shows.

Maxim Dounin

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx