qlog
qlog copied to clipboard
quicwg
The IETF I-D documents for the qlog format
This would be *really* important for generating metrics. Logically, it's a congestion event, but I'm not sure if it would probably make sense to add this as a state to...
msquic has separate events that indicate if the sender was blocked/delayed/idle and due to which cause (e.g., pacing, flow control limited, cwnd limited, etc.). This is quite useful for debugging....
This is a high-level observation based on my experience of 1. adding qlog support for quic-go and 2. writing some tooling to sift through a pile of logs. When adding...
Currently, we have some events that are used both for indicating changes in the local as well as the remote endpoint. An example is parameters_set, which logs both connection params...
Currently, the parameters related events aggregate all sorts of parameters, doesn't matter where they come from. Good example is transport:parameters_set, which contains mostly data that's transported via TLS (Transport params,...
Now that this is a bit more mature, it should be added to draft-02. Via @marten-seemann: > So I would assume that would best be modeled using a `path_probed` event...
When a client receives a Version Negotiation packet indicating that there's no commonly supported version, it aborts the connection attempt. Currently, qlog doesn't allow to log this.
I recently implemented draft 2 and was very confused about the these two fields, found in some of the QuicFrame classes. 1. What does it mean when a frame has...
At the moment, it's not entirely clear how qlog is "supposed to be used". For example, it's not clear to implementers why some fields (e.g., quic version) are duplicated across...
Fixes #122. This PR contains 2 fixes: - stateless reset tokens are not tokens - `PacketHeader` already contains a `Token`, so we don't need another field on the `packet_sent` and...