sanghyeok An created KAFKA-20596:
------------------------------------
Summary: Consider exposing broker-reported Streams group heartbeat
status via metrics
Key: KAFKA-20596
URL: https://issues.apache.org/jira/browse/KAFKA-20596
Project: Kafka
Issue Type: Improvement
Reporter: sanghyeok An
Assignee: sanghyeok An
Kafka Streams currently exposes stream thread state through client metrics, but
some broker-reported Streams group status information is only available through
logs or internal client state.
With the Streams Rebalance Protocol, the broker reports group status
information to the client through StreamsGroupHeartbeatResponse.Status. This
can include conditions such as missing source topics, missing internal topics,
incorrectly partitioned topics, delayed assignment, stale topology, or
application shutdown requested by another member. The client already consumes
this information internally, for example when determining whether the Streams
group is ready to process records.
This ticket proposes considering whether Kafka Streams should expose the
broker-reported Streams group heartbeat status through metrics. The goal is to
make this protocol-level status easier to observe through monitoring systems
without requiring users to inspect logs first.
The metric should represent broker-reported Streams group heartbeat status, not
a general explanation for every stream thread state. It should also avoid
exposing StatusDetail as metric data because it may contain topic names or
variable error text.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
