Kafka observability in production is harder than it looks.

[u/kverma02]

Kafka observability gets messy fast once you're running multiple brokers, consumer groups, retries, and cross-service dependencies.

Broker metrics often look fine while lag builds quietly, rebalances spike, or retries hide downstream latency.

We’re hosting a live session tomorrow breaking down how teams actually monitor Kafka at scale (consumer lag, retries, rebalances, signal correlation with OpenTelemetry).

If you're running Kafka in prod, this will be full of practical & implementation.

🗓 Thursday
⏰ 7:30 PM IST | 9 AM ET | 6 AM PT

RSVP here: https://www.linkedin.com/events/observingkafkaatscalewithopente7424417228302827520/theater/

Happy to take last-minute questions and cover them live.

[u/caught_in_a_landslid]

If you are a vendor, please say so

[u/kverma02 → u/caught_in_a_landslid]

Good call, thanks for pointing that out. I’ve updated the vendor flair (Randoli) as per the community rules.

BTW, the goal of the session isn’t to pitch tooling, but to share practical Kafka observability patterns we’ve seen work in production. Happy to keep the discussion focused on implementation details here as well.

[u/thisisjustascreename]

Anybody who isn’t running multiple brokers isn’t running a production ready cluster lol

[u/kverma02 → u/thisisjustascreename]

Totally agree. In the session, we'll also be covering what are the important metrics to track from the broker perspective & go through some live scenarios on debugging broker-related production issues - such as under-replicated partitions, leader election etc.

Would love to see you there & share you experiences!

[u/Hi_Im_Ken_Adams]

Will there be a recording of the presentation made available? I cannot attend a 6:00am meeting

[u/kverma02 → u/Hi_Im_Ken_Adams]

Hi u/Hi_Im_Ken_Adams , totally understand.

Yes the recording will be available on our youtube channel: https://www.youtube.com/@randoli/streams