You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@kafka.apache.org by Jose Manuel Vega Monroy <jo...@williamhill.com> on 2019/06/24 14:57:35 UTC

Kafka 2.1.1 migration - JMX metrics problem

Hi there,

Recently we rolling upgraded our internal brokers from version 0.11.0.1 to version 2.1.1 in different envs, with the next definition of JMX metrics for Introscope Wily:

JMX|kafka.server|Fetch:queue-size,\
JMX|kafka.server|Fetch|*:byte-rate,\
JMX|kafka.server|Fetch|*:throttle-time,\
JMX|kafka.server|Produce:queue-size,\
JMX|kafka.server|Produce|*:byte-rate,\
JMX|kafka.server|Produce|*:throttle-time,\

However, somehow even defining client.id and group.id in our consumer/producer app conf, looking like Wily is taken the apps metrics by the username we are defining in sasl.jaas.config for security protocol SASL_PLAINTEXT, instead of client.id like used to be before migration.

Any idea why this is happening?

Thanks

[https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180]<http://www.williamhill.com/>
[https://www.williamhillplc.com/content/signature/senet.gif?width=180]<http://www.whenthefunstops.co.uk/>
Jose Manuel Vega Monroy
Java Developer / Software Developer Engineer in Test
Direct: +0035 0 2008038 (Ext. 8038)
Email: jose.monroy@williamhill.com<ma...@williamhill.com>
William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA

Re: Kafka 2.1.1 migration - JMX metrics problem

Posted by Jose Manuel Vega Monroy <jo...@williamhill.com>.
Hi there,

We found it was related to quotas definition, having defined clients and users ones with default value at the same time.

Thanks

[https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180]<http://www.williamhill.com/>
[https://www.williamhillplc.com/content/signature/senet.gif?width=180]<http://www.whenthefunstops.co.uk/>
Jose Manuel Vega Monroy
Java Developer / Software Developer Engineer in Test
Direct: +0035 0 2008038 (Ext. 8038)
Email: jose.monroy@williamhill.com<ma...@williamhill.com>
William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA




From: Jose Manuel Vega Monroy <jo...@williamhill.com>
Date: Monday, 24 June 2019 at 16:55
To: "users@kafka.apache.org" <us...@kafka.apache.org>
Cc: Luca Segafredo <Lu...@williamhill.com>, Andreea Nicula <an...@williamhill.com>, Laur Aliste <la...@williamhill.com>, Pedro Da Costa <Pe...@williamhill.com>, Cezary Gajdzinski <Ce...@williamhill.com>, Paul Johnson <pa...@williamhill.com>
Subject: Kafka 2.1.1 migration - JMX metrics problem

Hi there,

Recently we rolling upgraded our internal brokers from version 0.11.0.1 to version 2.1.1 in different envs, with the next definition of JMX metrics for Introscope Wily:

JMX|kafka.server|Fetch:queue-size,\
JMX|kafka.server|Fetch|*:byte-rate,\
JMX|kafka.server|Fetch|*:throttle-time,\
JMX|kafka.server|Produce:queue-size,\
JMX|kafka.server|Produce|*:byte-rate,\
JMX|kafka.server|Produce|*:throttle-time,\

However, somehow even defining client.id and group.id in our consumer/producer app conf, looking like Wily is taken the apps metrics by the username we are defining in sasl.jaas.config for security protocol SASL_PLAINTEXT, instead of client.id like used to be before migration.

Any idea why this is happening?

Thanks

[https://www.williamhillplc.com/content/signature/WHlogo.gif?width=180]<http://www.williamhill.com/>
[https://www.williamhillplc.com/content/signature/senet.gif?width=180]<http://www.whenthefunstops.co.uk/>
Jose Manuel Vega Monroy
Java Developer / Software Developer Engineer in Test
Direct: +0035 0 2008038 (Ext. 8038)
Email: jose.monroy@williamhill.com<ma...@williamhill.com>
William Hill | 6/1 Waterport Place | Gibraltar | GX11 1AA