# Server Status?

**URL:** <https://www.ruby-forum.com/t/server-status/245603>\
**Category:** NGINX\
**Created:** [June 20, 2013, 2:48pm UTC](https://www.ruby-forum.com/t/server-status/245603 "2013-06-20T14:48:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sadaf\_N](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/858c86/32.png) [@Sadaf\_N](https://www.ruby-forum.com/u/Sadaf_N)\
**Post date:** [June 20, 2013, 2:48pm UTC](https://www.ruby-forum.com/t/server-status/245603/1 "2013-06-20T14:48:49Z")

</div>

Hi Nginx Team,

I used nginx for a few years and until now, i used to deploy it for  
static  
content. Right now, i 'd like to deploy it for dynamic content using  
php-fpm. It works fine and performances are good.

But according to me and my team (and many other admins as far as i can  
see), something important is really missing to push it in production.  
This  
is the “extended status” (i mean something like the apache  
server-status)

There is a 3rd party module that is supposed to do that but it is buggy  
and  
nginx core has to be patched.

So my question is: Do you think that nginx dev team could do something  
in  
that way? i think it will be a much better improvment than getting stuff  
like SPDY or other experimental things.

Best regards,

Julien

---

<div class="post-metadata">

**Author:** ![Julien\_Decrouy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/c67d28/32.png) [@Julien\_Decrouy](https://www.ruby-forum.com/u/Julien_Decrouy)\
**Post date:** [June 20, 2013, 4:15pm UTC](https://www.ruby-forum.com/t/server-status/245603/2 "2013-06-20T16:15:54Z")

</div>

> But according to me and my team (and many other admins as far as i can  
> see), something important is really missing to push it in production. This  
> is the “extended status” (i mean something like the apache server-status)

What are the “important” things in the “extended status” that you miss  
for  
the production use?

Combined with the php-fpm own status ( pm.status\_path ) you can get  
pretty  
much all the vital metrics the only exception being the list of current  
active request URLs and even then the problematic ones can be logged  
with  
the php-fpm’s slow log (request\_slowlog\_timeout).

> So my question is: Do you think that nginx dev team could do something in  
> that way? i think it will be a much better improvment than getting stuff  
> like SPDY or other experimental things.

So to answer your question - while the dev team of nginx could probably  
work  
on more visually appealing status page (as far as I know it’s on TODO  
list  
and you can always speed up theese things by either contributing the  
code  
yourself or using the nginx commercial support ([nginx.com](http://nginx.com))) these  
“experimental things” are what have made nginx one of the fastest and  
feature richest webserver.

rr

rr

---

<div class="post-metadata">

**Author:** ![Julien\_Decrouy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/c67d28/32.png) [@Julien\_Decrouy](https://www.ruby-forum.com/u/Julien_Decrouy)\
**Post date:** [June 20, 2013, 5:58pm UTC](https://www.ruby-forum.com/t/server-status/245603/3 "2013-06-20T17:58:45Z")

</div>

Thanks for the feed back Reinis

I agree that the extended module (  
[http://wiki.nginx.org/Extended\_status\_module](http://wiki.nginx.org/Extended_status_module)) is doing things right but  
it  
is no more supported with nginx 1.3 or later and i think that patching  
nginx core is not a good thing.

This way, the php-fpm status is a good alternative but we miss some  
metrics  
like the client ip,Vhost (i can get it with the script path but i won’t  
get  
it if it’s an alias), the status (reading, writting…) and as you said  
the list of current active request URLs. This is pretty important to  
debug  
and apache serverstatus helped us several times so it will be great to  
have  
the same on nginx.

Finally, i know that many admins (friends) don’t use nginx for dynamic  
content because of this miss and getting it will be a way to gain some  
more  
percentage points of market share.

I will be interested to contribute but i haven’t found anything about a  
TODO list, do you have a link or something like this please?

regards

2013/6/20 Reinis R. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)

---

<div class="post-metadata">

**Author:** ![Julien\_Decrouy](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/c67d28/32.png) [@Julien\_Decrouy](https://www.ruby-forum.com/u/Julien_Decrouy)\
**Post date:** [June 20, 2013, 7:27pm UTC](https://www.ruby-forum.com/t/server-status/245603/4 "2013-06-20T19:27:02Z")

</div>

Me too, I am looking forward for this extension for 1.4.x

current branch which is not working for recent versions:

> **[GitHub - zealot83/ngx\_http\_extended\_status\_module](https://github.com/zealot83/ngx_http_extended_status_module)**
>
> Contribute to zealot83/ngx\_http\_extended\_status\_module development by creating an account on GitHub.

it would be greatly appreciated if one of geeks to do it

Regards

============================================