# KIP-714: Keep your Kafka Clusters Close, and your Kafka Clients Closer

**URL:** <https://forum.confluent.io/t/kip-714-keep-your-kafka-clusters-close-and-your-kafka-clients-closer/10953>\
**Category:** Architecture and Design\
**Created:** [25 June 2024 17:59 UTC](https://forum.confluent.io/t/kip-714-keep-your-kafka-clusters-close-and-your-kafka-clients-closer/10953 "2024-06-25T17:59:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![riferrei](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/riferrei/32/1848_2.png) [@riferrei](https://forum.confluent.io/u/riferrei)\
**Post date:** [25 June 2024 17:59 UTC](https://forum.confluent.io/t/kip-714-keep-your-kafka-clusters-close-and-your-kafka-clients-closer/10953/1 "2024-06-25T17:59:43Z")

</div>

## For many years, the only way to capture Kafka client metrics was using JMX. Starting with Kafka **3.7.0** and, thanks to the **KIP-714** , it is now possible to pull client metrics from your Kafka clusters using **OpenTelemetry**. This blog post explains how KIP-714 works, what you have to do to collect metrics, and gives you a working code to test things out.

> **[AWS Builder Center](https://builder.aws.com/content/2i3i0osdRihttgQ8AZii6F0Bv4F/kip-714-keep-your-kafka-clusters-close-and-your-kafka-clients-closer)**
>
> Connect with builders who understand your journey. Share solutions, influence AWS product development, and access useful content that accelerates your growth. Your community starts here.

— Ricardo Ferreira