[jira] [Updated] (KAFKA-4819) Expose states of active tasks to public API
[ https://issues.apache.org/jira/browse/KAFKA-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4819: --- Description: https://cwiki.apache.org/confluence/display/KAFKA/KIP+130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API (was: In Kafka 0.10.1.0 the toString method of KafkaStreams class has been implemented mainly to ease topologies debugging. Also, the streams Metrics has been exposed to public API. But currently theres is no way to monitor kstreams tasks states, assignments or consumed offsets. I propose to expose the states of active tasks to the public API KafkaStreams. For instance, an application can expose a REST API to get the global state of a kstreams topology.) > Expose states of active tasks to public API > --- > > Key: KAFKA-4819 > URL: https://issues.apache.org/jira/browse/KAFKA-4819 > Project: Kafka > Issue Type: New Feature > Components: streams >Affects Versions: 0.10.2.0 >Reporter: Florian Hussonnois >Assignee: Florian Hussonnois >Priority: Minor > Labels: kip > > https://cwiki.apache.org/confluence/display/KAFKA/KIP+130%3A+Expose+states+of+active+tasks+to+KafkaStreams+public+API -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4819) Expose states of active tasks to public API
[ https://issues.apache.org/jira/browse/KAFKA-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4819: --- Labels: kip (was: needs-kip) > Expose states of active tasks to public API > --- > > Key: KAFKA-4819 > URL: https://issues.apache.org/jira/browse/KAFKA-4819 > Project: Kafka > Issue Type: New Feature > Components: streams >Affects Versions: 0.10.2.0 >Reporter: Florian Hussonnois >Assignee: Florian Hussonnois >Priority: Minor > Labels: kip > > In Kafka 0.10.1.0 the toString method of KafkaStreams class has been > implemented mainly to ease topologies debugging. Also, the streams Metrics > has been exposed to public API. > But currently theres is no way to monitor kstreams tasks states, assignments > or consumed offsets. > I propose to expose the states of active tasks to the public API KafkaStreams. > For instance, an application can expose a REST API to get the global state of > a kstreams topology. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (KAFKA-4819) Expose states of active tasks to public API
[ https://issues.apache.org/jira/browse/KAFKA-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax updated KAFKA-4819: --- Labels: needs-kip (was: ) > Expose states of active tasks to public API > --- > > Key: KAFKA-4819 > URL: https://issues.apache.org/jira/browse/KAFKA-4819 > Project: Kafka > Issue Type: New Feature > Components: streams >Affects Versions: 0.10.2.0 >Reporter: Florian Hussonnois >Priority: Minor > Labels: needs-kip > > In Kafka 0.10.1.0 the toString method of KafkaStreams class has been > implemented mainly to ease topologies debugging. Also, the streams Metrics > has been exposed to public API. > But currently theres is no way to monitor kstreams tasks states, assignments > or consumed offsets. > I propose to expose the states of active tasks to the public API KafkaStreams. > For instance, an application can expose a REST API to get the global state of > a kstreams topology. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
