Skip to content

logging both http- and quic-level events #21

@kazuho

Description

@kazuho

At the moment, the command is capable of only logging either of the two at once. This prevents us from doing cross-layer analysis, e.g, looking into what HTTP response is sent on a particular QUIC STREAM frame.

I think we should simply log all the events regardless of the layer (e.g., provider in terms of USDT).

When emitting events from multiple providers to JSON, the event names can be prefixed by their prefixes (e.g., receive event of quicly provider becomes quicly_receive). Doing so would align the output to that generated by https://github.com/h2o/quicly/blob/master/misc/probe2trace.pl.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions