[
https://issues.apache.org/jira/browse/TS-4136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15244291#comment-15244291
]
Susan Hinrichs commented on TS-4136:
------------------------------------
This is fixed for HTTP1 and HTTP2 with the application of TS-3612. The
maintenance of the proxy.process.http.current_client_connections and
proxy.process.http.total_client_connections counters is moved from the
Transaction processing to the Http1ClientSession and Http2ClientSession classes.
SPDY is unchanged, so if spdy is enabled, you will need to look at the spdy
connection count and spdy stream counts to update the
proxy.process.http.current_client_connections and
proxy.process.http.total_client_connections counters.
I
> incoming http connection stats should be correct regardless of the HTTP
> version
> -------------------------------------------------------------------------------
>
> Key: TS-4136
> URL: https://issues.apache.org/jira/browse/TS-4136
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, HTTP/2
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 6.2.0
>
>
> proxy.process.http.current_client_connections and
> proxy.process.http.total_client_connections are inaccurate once you
> introduction SPDY and HTTP2. The connections counts will be incremented once
> per stream, not once per connection.
> You can use the spdy and http2 specific counts to fix up the number, but we
> should go ahead and fix this directly. Once ts-3612 is present, the HTTP1.1
> session protocol is separated out of the HTTP state machine making the fix
> relatively straight forward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
