web socket connection time

[Philip Walenta]

Igor,

Not sure if this will help, but I gather several metrics from the front end
to make a determination how long back end responses take.

Here's a snippet from my log format that might help:

"upstream_server":"$upstream_addr", "req_total_time":"$request_time",
"req_upstream_time":"$upstream_response_time",
"upstream_conn_time":"$upstream_connect_time",
"upstream_header_time":"$upstream_header_time"

You can find all the variables here:

http://nginx.org/en/docs/varindex.html

On Mon, Nov 21, 2016 at 5:09 AM, Igor Karymov <ingham.k at gmail.com> wrote:

> Hello. I'm using Nginx as WebSocket proxy and trying to set up the metric
> that will show me how quick gateway can establish new connections.
> Unfortunately, looks like when I parse logs I have only "response_time"
> that in the case of WebSockets  will be better to call "connection time".
> Any ideas how can I get time between GET request and 101 response?
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20161121/35c89ba2/attachment.html>