[
https://issues.apache.org/jira/browse/KAFKA-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Swapnil Ghike updated KAFKA-592:
--------------------------------
Attachment: kafka-592-v1.patch
Change made to register AllTopicsProduceFailurePerSec,
AllTopicsFetchFailurePerSec, OfflinePartitionsPerSec and
UncleanLeaderElectionsPerSec in server.startup()
UnderReplicatedPartitionCount is already registered in startup with the
creation of replicaManager.
BrokerTopicStat.getBrokerAllTopicStat() also registers three other beans -
AllTopicsMessagesInPerSec, AllTopicsBytesInPerSec and AllTopicBytesOutPerSec.
But that's probably ok since these beans would be created anyways in most cases.
> Register metrics beans at kafka server startup
> -----------------------------------------------
>
> Key: KAFKA-592
> URL: https://issues.apache.org/jira/browse/KAFKA-592
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8
> Reporter: Swapnil Ghike
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: bugs
> Fix For: 0.8
>
> Attachments: kafka-592-v1.patch
>
>
> jmx beans are not registered until the corresponding part of the code
> executes. To set alerts on some of the server side beans, they need to be
> registered at server startup.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
