The problem was that the metric names had all changed in the latest
version. Fixing the names seems to have done it.

On Thu, Aug 13, 2015 at 3:13 PM, Rajiv Kurian <ra...@signalfuse.com> wrote:

> Aah that seems like a red herring - seems like the underlying cause is
> that the MBeans I was trying to poll (through our metrics system) are no
> longer present. We use collectd JMX to get metrics from Kafka and here is
> what I see:
>
>  GenericJMXConfMBean: No MBean matched the ObjectName
> "kafka.server":type="BrokerTopicMetrics",name="My_Topic-FailedProduceRequestsPerSec"
>
> On Thu, Aug 13, 2015 at 2:27 PM, Rajiv Kurian <ra...@signalfuse.com>
> wrote:
>
>> Till recently we were on 0.8.1 and updated to 0.8.2.1
>>
>> Everything seems to work but I am no longer seeing metrics reported from
>> the broker that was updated to the new version.
>>
>> My config file has the following lines:
>>
>> kafka.metrics.polling.interval.secs=5
>> kafka.metrics.reporters=kafka.metrics.KafkaCSVMetricsReporter
>> kafka.csv.metrics.dir=/var/lib/kafka/metrics/
>> kafka.csv.metrics.reporter.enabled=false
>>
>> This was working in 0.8.1 but not in 0.8.2.1
>>
>> When the broker was started I noticed these messages in the logs:
>>
>> 2015-08-13T21:03:29.235Z WARN  [main                               ]
>> [kafka.utils.VerifiableProperties    ]: Property kafka.csv.metrics.dir is
>> not valid
>>
>> 2015-08-13T21:03:29.235Z WARN  [main                               ]
>> [kafka.utils.VerifiableProperties    ]: Property
>> kafka.csv.metrics.reporter.enabled is not valid
>>
>> 2015-08-13T21:03:29.235Z WARN  [main                               ]
>> [kafka.utils.VerifiableProperties    ]: Property
>> kafka.metrics.polling.interval.secs is not valid
>>
>> 2015-08-13T21:03:29.235Z WARN  [main                               ]
>> [kafka.utils.VerifiableProperties    ]: Property kafka.metrics.reporters is
>> not valid
>>
>>
>> Is this is a known issue? Is there a work around or any documentation on
>> what these properties are now called?
>>
>>
>> Thanks
>>
>
>

Reply via email to