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?
> And, uhm, number of allocs you use to produce simple answer is
> really outstanding. ;)
>
> Maxim Dounin
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
>


--
Weibin Yao


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