Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better options for choosing what to trace #83

Open
kazuho opened this issue Jun 8, 2020 · 0 comments
Open

Better options for choosing what to trace #83

kazuho opened this issue Jun 8, 2020 · 0 comments

Comments

@kazuho
Copy link
Contributor

kazuho commented Jun 8, 2020

IIUC, h2o has two modes, identified by the special argument "quic." If set, it logs QUIC and HTTP events. If not, it logs HTTP events only. The limitation of the approach is that it is not capable of logging QUIC events only (therefore it cannot be used for tracing other applications using quicly). The other problem is that it does not trace TLS events.

I think that things would become clearer if there were three options to designate tracing at each layer. E.g., -H for HTTP-level tracing, -Q for QUIC level, -T for TLS-level.

@kazuho kazuho changed the title Better options for choosing what to log Better options for choosing what to trace Jun 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant