Counting different bandwidth cases

roederharpo · 2017-11-01T19:58:49+00:00

Hi all!found in the ngx.timer.at() description that it can not work with cosocket based operations:So suppose when i work with websocket i can not share ws i...

Counting different bandwidth cases

roederharpo

Hello! I am using the latest openresty release and am very happy with the project.

I have an inquiry about feature support / potential implementation of a feature.

I have an openresty service configured as a reverse proxy for some servers.

I wish to accurately record the bandwidth that is being used. There are 4 types

of bandwidth that I am interested in. Bandwidth from the browser to the proxy,

from the proxy to the browser, from the site server to the proxy, and from the proxy

to the site server.

NGINX provides a variable to find the data between the proxy and browser. This can be

found with "$bytes_sent". There are 3 more variables that NGINX defines that do not

appear to be included with openresty. These variables are "$upstream_bytes_received",

and "$bytes_received". Both of these are marked as part of the "1.11.4" release of NGINX.

Is there a planned date when these features will be available? Do they currently exist

in development? If so should I build master and run that for the features I want?

If anyone has comments on alternative ways for me to get the statistics I want without

some external byte count monitor program I am all ears! I quickly also have a side

question. Do you know if these variables count compressed or uncompressed bytes?

I get the impression that they count bytes that actually go over the wire and not the

uncompressed version but I am not sure.

Thanks!

zchao1995

Hello! I am using the latest openresty release and am very happy with the project.
I have an inquiry about feature support / potential implementation of a feature.
I have an openresty service configured as a reverse proxy for some servers.
I wish to accurately record the bandwidth that is being used. There are 4 types
of bandwidth that I am interested in. Bandwidth from the browser to the proxy,
from the proxy to the browser, from the site server to the proxy, and from the proxy
to the site server.
NGINX provides a variable to find the data between the proxy and browser. This can be
found with "$bytes_sent". There are 3 more variables that NGINX defines that do not
appear to be included with openresty. These variables are "$upstream_bytes_received",
and "$bytes_received". Both of these are marked as part of the "1.11.4" release of NGINX.
Is there a planned date when these features will be available? Do they currently exist
in development? If so should I build master and run that for the features I want?

As far as i know, the OpenResty official team is migrating their nginx core form version 1.11.2 to version 1.13.6.

If anyone has comments on alternative ways for me to get the statistics I want without
some external byte count monitor program I am all ears! I quickly also have a side
question. Do you know if these variables count compressed or uncompressed bytes?
I get the impression that they count bytes that actually go over the wire and not the
uncompressed version but I am not sure.

$bytes_sent is calculated later than the gzip body filter, so if the content is decompressed, the $bytes_sent is the one decompressed.

$upstream_bytes_received is calculated whenever nginx upstream module gets data, it is the one backend sent to nginx

$bytes_received is a variable supported by stream module.

Thanks!

jonathan

The current github master is using 1.13.5 (september commit) and looks like there is an rc being tested.

i would just try using the master.