BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//sf26-agenda//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VEVENT
UID:SESS-169@sf26-agenda
DTSTAMP:20261020T151709Z
DTSTART:20261105T173000Z
DTEND:20261105T181500Z
SUMMARY:Wireshark for Kafka: Catch Your Client's Anti-Patterns on the Wire
LOCATION:Room 2006
DESCRIPTION:Stephane Derosiaux\n\nYou call producer.send() or consumer.poll
 (). On the wire\, that one line is never a simple request: a handshake\, a
  metadata fetch\, version negotiation\, then a Produce or a Fetch\, plus t
 he group coordination\, heartbeats\, and offset commits behind a consumer.
  All negotiated across protocol versions (Kafka is strict about backward a
 nd forward compatibility). Your logs don't show this. Kafka UIs show only 
 the records. How do you see the protocol exchange itself? You don't. That'
 s where the worst bugs hide: a full handshake on every record\, an OffsetC
 ommit after every message\, a consumer-group rebalance storm\, a producer 
 still talking to a stale leader. To see it\, we put a protocol tap between
  client and brokers\, no SDK instrumentation\, no code change\, and decode
  the frames live. It works the same whatever client speaks them (Java\, Go
 \, Python\, librdkafka\, Kafka Streams\, Flink\, etc.)\, because the proto
 col is the contract. The demo uses Kapture UI (open-source) to filter the 
 protocol stream\, flag the anti-patterns as they appear\, and fix your cli
 ents. By attending this session\, your contact information may be shared w
 ith the sponsor for relevant follow up for this event only.
URL:https://sf26.rmoff.net/s/wireshark-for-kafka-catch-your-clients-anti-pa
 tterns-on-the-169
END:VEVENT
END:VCALENDAR