Hi Jason - can you describe how you verify that the metrics are not coming through to the metrics registry? Looking at the metrics code it seems that the mbeans are only registered by the yammer jmx reporter only after being added to the metrics registry.
Thanks, Joel On Tue, Jan 27, 2015 at 02:20:38AM -0500, Jason Rosenberg wrote: > I can confirm that the per topic metrics are not coming through to the > yammer metrics registry. I do see them in jmx (via jconsole), but the > MetricsRegistry does not have them. > All the other metrics are coming through that appear in jmx. > > This is with single node instance running locally. > > Jason > > > > On Mon, Jan 26, 2015 at 8:30 PM, Manikumar Reddy <ku...@nmsworks.co.in> > wrote: > > > If you are using multi-node cluster, then metrics may be reported from > > other servers. > > pl check all the servers in the cluster. > > > > On Tue, Jan 27, 2015 at 4:12 AM, 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. > > > > >
