[jira] [Commented] (KAFKA-266) Kafka web console

["James Miller (JIRA)" <ji...@apache.org>]

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

James Miller commented on KAFKA-266:
------------------------------------

Hi Folks, 
I have a admin web app that I built for this purpose, it connects to Zk and displays information about brokers, topics, and consumers. 

It really useful, especially when just getting started with Kafka, I would like to contribute it to the this project.

It is a Play App, written in Scala and depends on Playframework, Kafka, and jQuery.  Any concerns about these dependencies?

 Also, what are the preferred next steps, should I attach source or put in public github, not sure how you would like to move forward?



> Kafka web console
> -----------------
>
>                 Key: KAFKA-266
>                 URL: https://issues.apache.org/jira/browse/KAFKA-266
>             Project: Kafka
>          Issue Type: New Feature
>          Components: contrib
>            Reporter: Evan Chan
>              Labels: project
>   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 was sent by Atlassian JIRA
(v6.1.5#6160)