| commit | e3e1e8bb43998868122c9747af56622921df2bd4 | [log] [tgz] |
|---|---|---|
| author | haoyuewang <haoyuewang@google.com> | Thu Mar 23 14:41:52 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Mar 23 14:42:43 2023 -0700 |
| tree | 5c0d09ded4392309babf35037916c37794cfbc5b | |
| parent | e41eeaa344de2ab46ddea9bf82d6115f0ce27f2a [diff] |
Monitoring the QUIC version used for sessions with successful handshake. Internal context: a healthy Bonnet may only establish a new QUIC connection every a few hours (e.g. 10) while an unhealthy Bonnet experiencing 1-side black-hole can try to establish ~50 QUIC connections per hour. As a result, a small fraction of unhealthy Bonnets can potentially skew the types (IETF QUIC vs gQUIC) of QUIC sessions created at the server side. This CL adds metrics to log the types (IETF QUIC vs gQUIC) of QUIC sessions finishing handshake at the server side, which will reflect the QUIC versions used by healthy Bonnet. PiperOrigin-RevId: 518967612
QUICHE stands for QUIC, Http, Etc. It is Google‘s production-ready implementation of QUIC, HTTP/2, HTTP/3, and related protocols and tools. It powers Google’s servers, Chromium, Envoy, and other projects. It is actively developed and maintained.
There are two public QUICHE repositories. Either one may be used by embedders, as they are automatically kept in sync:
To embed QUICHE in your project, platform APIs need to be implemented and build files need to be created. Note that it is on the QUICHE team's roadmap to include default implementation for all platform APIs and to open-source build files. In the meanwhile, take a look at open source embedders like Chromium and Envoy to get started:
To contribute to QUICHE, follow instructions at CONTRIBUTING.md.
QUICHE is only supported on little-endian platforms.