[ 
https://issues.apache.org/jira/browse/KAFKA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229233#comment-13229233
 ] 

Eric Hauser commented on KAFKA-266:
-----------------------------------

I would like to see a simple monitoring console as something that is embedded 
within the brokers themselves (ActiveMQ does something similar).  It should 
have minimal dependencies (jetty, servlets, and Javascript sound appropriate).  
The simple HTTP interface should allow for quick checking to see if:

1) Brokers are up
2) Topic are being written to
3) Topics are being consumed

While most of this data is available via JMX already, HTTP is a preferable 
alternative.  An external application that provides comprehensive management, 
audit solution seems to make sense as well.
                
> Kafka web console design
> ------------------------
>
>                 Key: KAFKA-266
>                 URL: https://issues.apache.org/jira/browse/KAFKA-266
>             Project: Kafka
>          Issue Type: New Feature
>          Components: contrib
>            Reporter: Evan Chan
>   Original Estimate: 672h
>  Remaining Estimate: 672h
>
> This issue is created to track a community-contributed Kafka Web UI.
> Here is an initial list of goals:
> - Be able to easily see which brokers are up
> - Be able to see lists of topics, connected producers, consumer groups, 
> connected consumers
> - Be able to see, for each consumer/partition, its offset, and more 
> importantly, # of bytes unconsumed (== largest offset for partition - current 
> offset)
> - (Wish list) have a graphical view of the offsets
> - (Wish list) be able to clean up consumer state, such as stale claimed 
> partitions
> List of challenges/questions:
> - Which framework?  Play! for Scala?
> - Is all the data available from JMX and ZK?  Hopefully, watching the files 
> on the filesystem can be avoided....
> - How to handle large numbers of topics, partitions, consumers, etc. 
> efficiently

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to