Hey Sanghyeok An Thanks for the KIP. A couple of questions/considerations:
AS1- A gauge only shows the latest heartbeat. Could we discuss a cumulative counter or the gauge vs counter trade-off in the KIP? I don't think the gauge is wrong, but on its own it's hard to alert on reliably. AS2. Are the metric reader and writer threads the same? I assume they are two different threads. Could we discuss on the race conditions? Is it guaranteed that the reader sees the latest write? AS3- The name `streams-group-status` reads like a property of the whole group, but it's a per-thread metric (thread-id tag) reporting that thread's last heartbeat. Would something like `heartbeat-status` work better? AS4- We may need to list more edge cases?! For example, when a heartbeat has no status or when it fails. I mean could we list and discuss them? What should the value be (0 or 1) in each case? Thanks, Alieh On Wed, Jun 10, 2026 at 12:30 AM Sanghyeok An <[email protected]> wrote: > Hello Kafka Community, > > I would like to gently follow up on the discussion for KIP-1350, in case > anyone has had a chance to take a look. > This KIP proposes exposing Streams group heartbeat statuses as Kafka > Streams metrics, to make it easier to diagnose Streams rebalance protocol > issues without relying only on client logs. > > KIP - > > https://urldefense.com/v3/__https://cwiki.apache.org/confluence/display/KAFKA/KIP-1350*3A*Expose*Streams*Group*Heartbeat*Statuses*as*Kafka*Streams*Metrics__;JSsrKysrKysrKw!!Ayb5sqE7!uEAEaq5_dYw5iEExhfHl_jW2SEqSm3y_J7B-aBKm_otsCrnovllLW3t0MVpDt30NO5j73-tCwHgeOtxo6EM$ > > I would greatly appreciate any feedback, comments, or suggestions you may > have. > > Best regards, > Sanghyeok An. > > 2026년 6월 1일 (월) 오후 10:47, Sanghyeok An <[email protected]>님이 작성: > > > Hello Kafka Community, > > > > I would like to gently follow up on the discussion for KIP-1350, in case > > anyone has had a chance to take a look. > > This KIP proposes exposing Streams group heartbeat statuses as Kafka > > Streams metrics, to make it easier to diagnose Streams rebalance protocol > > issues without relying only on client logs. > > > > I would greatly appreciate any feedback, comments, or suggestions you may > > have. > > > > Best regards, > > Sanghyeok An. > > >
