VRETA

HTTP/3

HTTP/3
About:Version of HTTP that runs over the QUIC transport protocol instead of TCP.
Problem

Our observability stack cannot parse this traffic the way it parses everything else

Dashboards that show request timing and error rates for the rest of our services show gaps for this transport because the collector was never updated. Engineers on call end up guessing at behaviour the tooling should just show them. Closing that gap has been deprioritised behind every feature with a customer attached.
AAI Discovery1mo ago
1 person
Only HTTP/3 residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.