[
https://issues.apache.org/jira/browse/TS-4474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15298437#comment-15298437
]
Susan Hinrichs commented on TS-4474:
------------------------------------
I would argue that we should keep track of current connections and current
transactions. There currently is
proxy.process.http.current_client_connections and
proxy.process.http.current._client_transactions
I think they both should include both HTTP1.x and HTTP2. If we want to keep
track of the protocol stats separately, we should add stats in addition to the
general case.
BTW, it appears that we aren't decrementing the
proxy.process.http.current_client_transactions for HTTP2. Looks like it needs
a fix similar to the one you made for current_active_client_connections.
> Clarify proxy metric names
> --------------------------
>
> Key: TS-4474
> URL: https://issues.apache.org/jira/browse/TS-4474
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP, HTTP/2, Metrics
> Reporter: Masaori Koshiba
> Fix For: sometime
>
>
> After TS-3612, proxy session and proxy transaction is separated explicitly.
> But some metrics names are confusing and inconsistent.
> e.g.
> - {{proxy.process.http.current_active_client_connections}} includes number of
> active client HTTP/2 streams. But, HTTP/2 stream is a kind of transaction.
> - {{proxy.process.http.current_client_connections}} for HTTP/1.1 and HTTP/2
> but {{proxy.process.http2.current_client_sessions}} for HTTP/2
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
