Re: [PROPOSAL] HTTP Metrics Overhaul

2018-10-17 Thread Masakazu Kitajo
> Also don’t forget that QUIC will have to get into the mix here, and long term, both H2 and QUIC on the outbound connections. Yah, and QUIC would have some versions (some features are already pushed out from the first version). This brings up one more question; Should we also think about TLS vers

Re: [PROPOSAL] HTTP Metrics Overhaul

2018-10-17 Thread Leif Hedstrom
> On Oct 17, 2018, at 10:26 AM, Bryan Call wrote: > > I didn’t think about ipv4 and ipv6. If we want to break out all the stats so > you can figure out any combination we would need to have a stat hierarchy > such as: proxy.transport.process.encryption.http_version.scheme (e.g. > proxy.pro

Re: [PROPOSAL] HTTP Metrics Overhaul

2018-10-17 Thread Bryan Call
I didn’t think about ipv4 and ipv6. If we want to break out all the stats so you can figure out any combination we would need to have a stat hierarchy such as: proxy.transport.process.encryption.http_version.scheme (e.g. proxy.process.{ipv4,ipv6}.{tls,non-tls}.{http1,http2}.{http,https}). The

Re: [PROPOSAL] HTTP Metrics Overhaul

2018-10-17 Thread Masaori Koshiba
> 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. Good point. I didn't

Re: [PROPOSAL] HTTP Metrics Overhaul

2018-10-16 Thread Susan Hinrichs
I completely agree with the stats re-normalizing. I've been messed up multiple times by assuming that a http metric covers both protocols but was in fact http/1.x specific. On Tue, Oct 16, 2018 at 12:44 PM Bryan Call wrote: > The proxy.process.https stats (only 2 stats) should also be considere

Re: [PROPOSAL] HTTP Metrics Overhaul

2018-10-16 Thread Bryan Call
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 b

[PROPOSAL] HTTP Metrics Overhaul

2018-10-15 Thread Masaori Koshiba
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