Add new metrics to measure throughput in QBONE.

Historically, QBONE relies on metrics exported by the GFE and QUIC to measure throughput in bytes and packets:

* `/gfe/gfe2/http/bytes_in` for throughput in bytes to prod.
* `/gfe/gfe2/http/bytes_out` for throughput in bytes from prod.
* `/gfe/gfe2/spdy4_over_quic/packets_quic_read` for throughput in packets to prod.
* `/gfe/gfe2/spdy4_over_quic/connection_packet_writer_total_packets_sent` for throughput in packets from prod.

The initial motivation for this CL was to add a `traffic_class` dimension to the above methods, but as that involved modified non-QBONE code I decided to implement new QBONE-specific metrics. Each of the metrics in this CL have two dimensions:

* `direction`: TO_PROD or FROM_PROD
* `traffic_class`: A string that represents the traffic class of the packets.

A follow up CL will change the dashboard to use these metrics instead of the old ones once this is fully rolled out.

PiperOrigin-RevId: 620055645
5 files changed
tree: 46ffd38541abf18c9d593ca0a56717602f4091d6
  1. build/
  2. depstool/
  3. quiche/
  4. .bazelrc
  5. .bazelversion
  6. BUILD.bazel
  11. WORKSPACE.bazel


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

QUICHE is only supported on little-endian platforms.