[
https://issues.apache.org/jira/browse/KAFKA-12239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chia-Ping Tsai reassigned KAFKA-12239:
--------------------------------------
Assignee: Gérald Quintana
> Unclear warning message in JmxReporter, when getting missing JMX attribute
> --------------------------------------------------------------------------
>
> Key: KAFKA-12239
> URL: https://issues.apache.org/jira/browse/KAFKA-12239
> Project: Kafka
> Issue Type: Improvement
> Components: clients
> Affects Versions: 2.4.1
> Reporter: Gérald Quintana
> Assignee: Gérald Quintana
> Priority: Major
>
> When collecting bulk metrics, this warning message in logs is unhelpful, it
> is impossible to determine which MBean is missing this attribute and fix the
> metric collector:
>
> {noformat}
> [2021-01-26T15:43:41,078][WARN ][org.apache.kafka.common.metrics.JmxReporter]
> Error getting JMX attribute 'records-lag-max'
> javax.management.AttributeNotFoundException: Could not find attribute
> records-lag-max
> at
> org.apache.kafka.common.metrics.JmxReporter$KafkaMbean.getAttribute(JmxReporter.java:192)
> ~[?:?]
> at
> org.apache.kafka.common.metrics.JmxReporter$KafkaMbean.getAttributes(JmxReporter.java:200)
> ~[?:?]
> at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:709)
> ~[?:1.8.0_202]
> {noformat}
> Il would be very useful, to have the MBean object name in the error message.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
