Nginx stats

Server NGINX
1

Folks,

I’am interested in nginx stats like per return status numbers, bytes
served etc. I run nginx in a reverse proxy mode. I know parsing logs
will give that, but I wanted to know if there any module which gives
these stats. I looked in the stub module, i think these stats are not
there.

Thanks
samit

2

On Mar 29, 2012, at 3:52 PM, Samit Pal wrote:

Folks,

I’am interested in nginx stats like per return status numbers, bytes
served etc. I run nginx in a reverse proxy mode. I know parsing logs
will give that, but I wanted to know if there any module which gives
these stats. I looked in the stub module, i think these stats are not
there.

Yes, the stub one is quite limited. We’ve been working on a much better
version, which is going to appear soon.

3

One option is nginx-sflow-module. It reports counters (and
transactions) using a standard binary format over UDP - so you can have
a whole web-farm reporting to a single port on another server. No
log-file-tailing required. If you send the sFlow feed to Ganglia, for
example, it will pull out the counters and trend them. If your
transaction rate is high you can reduce the load by configuring random
sampling on the transaction logging, but the counters will still be
100% accurate.

http://code.google.com/p/nginx-sflow-module/

It works in conjunction with hsflowd, so you also get CPU, mem, I/O
stats for each server:
http://host-sflow.sourceforge.net

If anything is missing that should be counted/sampled for a
reverse-proxy scenario, please let me know. The sFlow-HTTP spec is
here:
http://sflow.org/sflow_http.txt

Neil

4

Is it out there now this module ANdrew?

Cheers!

2012/3/29 Andrew A. [email protected]

5

Still here. I’m not quite sure what you mean, though. Does the module
not compile cleanly for you, or is it missing fields that are needed
for reverse-proxy analysis?

Neil

6

Yes, the stub one is quite limited. We’ve been working on a much
better version, which is going to appear soon.

any more info on this topic yet?

Posted at Nginx Forum: