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

Update the connection tracker state machine to support tracing wrapped protocols #2095

Open
ddelnano opened this issue Jan 23, 2025 · 0 comments
Labels
area/datacollector Issues related to Stirling (datacollector)

Comments

@ddelnano
Copy link
Member

The current connection tracker model only supports tracing one protocol for the lifetime of the connection. Pixie was recently extended to support tracing TLS handshakes (#2050, #2058, etc). Due to this connection tracker model, this means users must pick tracing the TLS handshake or the inner (plaintext) application protocol. For the time being, the TLS handshake tracing is opt in, but it would be great to have Pixie be able to trace both the TLS handshake and the inner protocol.

This would permit tracing protocols that have L5-L7 layers. For example, web socket traffic starts out as HTTP, but is later upgraded to a different protocol. Or cases like finagle's thriftmux, which is Apache thrift contained inside a mux protocol session layer.

@ddelnano ddelnano added the area/datacollector Issues related to Stirling (datacollector) label Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/datacollector Issues related to Stirling (datacollector)
Projects
None yet
Development

No branches or pull requests

1 participant