Thanks, Jun. I'm pretty sure, though not 100% confident, that this has caused a change in the way that these metrics are reported to Yammer metrics (I believe that they are stomping on each other). Is that intended as well?
On Mon, Jan 26, 2015 at 4:13 PM, Jun Rao <j...@confluent.io> wrote: > Yes, we refactored the mbean names in 0.8.2.0 to make them more standard. > Those metrics are now registered under the following names. I did some > quick test and the values do get updated. > > kafka.server:type=BrokerTopicMetrics,name=BytesInPerSec > kafka.server:type=BrokerTopicMetrics,name=BytesInPerSec,topic=test > > The full list of the refactored mbean names can be found at > http://kafka.apache.org/082/documentation.html#monitoring > > Thanks, > > Jun > > > On Mon, Jan 26, 2015 at 2:42 PM, Kyle Banker <kyleban...@gmail.com> wrote: > > > I've been using a custom KafkaMetricsReporter to report Kafka broker > > metrics to Graphite. In v0.8.1.1, Kafka was reporting bytes and messages > in > > and out for all topics together and for each individual topic. > > > > After upgrading to v0.8.2.0, these metrics are no longer being reported. > > > > I'm only seeing the following: > > BrokerTopicMetrics > > - BytesInPerSec > > - BytesOutPerSec > > - BytesRejectedPerSec > > - MessagesInPerSec > > > > What's more, despite lots of successful writes to the cluster, the values > > for these remaining metrics are all zero. > > > > I saw that there was some refactoring of metric naming code. Was the > > behavior supposed to have changed? > > > > Many thanks in advance. > > >
