[
https://issues.apache.org/jira/browse/KAFKA-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229952#comment-13229952
]
Evan Chan commented on KAFKA-266:
---------------------------------
The web console would not primarily be for monitoring -- for us anyways -- and
I agree it should not replace Ganglia etc. (Although at some shops - most
notably Google - having web routes for every single service and app is a
policy). I think the web console would be invaluable for debugging and status
though. For looking at a snapshot of the system easily.
Also, standard JMX just doesnt work in EC2, you don't know what ports need to
be opened up.
I think the metric Im most interested in -- number of messages or MB
outstanding -- is not available directly from Kafka server itself anyways.
What is the timeframe for KAFKA-203?
> 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
