# Metrics for producers

**URL:** <https://forum.confluent.io/t/metrics-for-producers/7204>\
**Category:** Confluent Cloud\
**Created:** [10 February 2023 09:44 UTC](https://forum.confluent.io/t/metrics-for-producers/7204 "2023-02-10T09:44:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![trevorwebster](https://avatars.discourse-cdn.com/v4/letter/t/d78d45/32.png) [@trevorwebster](https://forum.confluent.io/u/trevorwebster)\
**Post date:** [10 February 2023 09:44 UTC](https://forum.confluent.io/t/metrics-for-producers/7204/1 "2023-02-10T09:44:41Z")

</div>

Good day ,

Im looking to find out if there is a metric I can pull to get the details of the producers into the confluent cluster and see if one might drop off. I have multiple producers feeding into a single cluster and need a way to monitor this if one drops off.

Thanks

Trevor

---

<div class="post-metadata">

**Author:** ![trevorwebster](https://avatars.discourse-cdn.com/v4/letter/t/d78d45/32.png) [@trevorwebster](https://forum.confluent.io/u/trevorwebster)\
**Post date:** [9 March 2023 08:53 UTC](https://forum.confluent.io/t/metrics-for-producers/7204/2 "2023-03-09T08:53:51Z")

</div>

Anyone know of a metric ?? Bump!

---

<div class="post-metadata">

**Author:** ![kuro](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.confluent.io/kuro/32/1809_2.png) [@kuro](https://forum.confluent.io/u/kuro)\
**Post date:** [13 March 2023 22:52 UTC](https://forum.confluent.io/t/metrics-for-producers/7204/3 "2023-03-13T22:52:43Z")

</div>

As far as I know, there is nothing that lets you know the status of a producer outside of the actual client-side producer application. Confluent Cloud only has information about the server side metrics, for example records being produced inside a topic or the consumer lag.

One option you can consider is to monitor the throughput of your topics using the [metrics API](https://docs.confluent.io/cloud/current/monitoring/metrics-api.html#query-for-bytes-received-from-producers-per-minute-grouped-by-topic), and try to identify possible errors regarding production rates with this information. There is also an “active\_connection\_count” metric that can be useful too.

Hope it helps.