The proxy.process.https stats (only 2 stats) should also be considered when
overhauling the stats. They are really TLS or non-TLS stats and not tied to
the scheme. I recommend breaking up TLS and non-TLS metric and calling them
proxy.process.ssl. and proxy.process.non-ssl.
Another option to build a hierarchy of stats and have it be
proxy.process.encryption.http_version.scheme (e.g.
proxy.process.{ssl,non-ssl}.{http1,http2}.{http,https}). Where scheme I don’t
see being used very much or at all, so it would only be mainly encryption and
http_version. For http2 encryption would always be ssl.
Also, I would be for modernizing the stats and configuration and calling
everything tls instead of ssl.
-Bryan
> On Oct 15, 2018, at 7:23 PM, Masaori Koshiba <[email protected]> wrote:
>
> Hi all,
>
> I’d like to propose some HTTP metrics changes. Because current HTTP metrics
> doesn’t have consistent naming rules.
>
> ----
> 1. Define `proxy.process.http.*` is HTTP version general metrics.
> 2. Introduce `proxy.process.http1.*` metrics for HTTP/1.1 specific metrics.
> 3. Split general metric into version specific metrics if needed.
> ----
>
> More details are in
> - https://github.com/apache/trafficserver/issues/4415
> <https://github.com/apache/trafficserver/issues/4415>
> -
> https://docs.google.com/spreadsheets/d/1zux3OPiDNJlWALluhr8ciKypg_sYVxbG9fdmeuDD-Bo/edit?usp=sharing
>
> <https://docs.google.com/spreadsheets/d/1zux3OPiDNJlWALluhr8ciKypg_sYVxbG9fdmeuDD-Bo/edit?usp=sharing>
>
> My proposal has incompatible changes. And it requires some actions to people
> who is tracking these metrics.
> Please comment on the issue or this thread if you have any opinions.
>
> My current target of these incompatible changes are next major release
> (9.0.0).
>
> Thanks,
> Masaori
