JMX expired topic metircs

2020-03-19 Thread 张祥
Hi, I notice that there are jmx metrics for deleted topics when using java code and jmxterm. Has anyone also run into this ? If yes, what is the reason behind this and how can I filter expired metrics ? Thanks.

Re: I'm trying to connect to a kafka broker running in AWS EKS (from outside the EKS cluster).

2020-03-19 Thread Dan Hill
I'll prefix this with I'm new to AWS. I'm used to Google's stack. I also noticed the helm instructions mention kops (so I'm not sure if this works with EKS). @Pirow - Kafka - I'm having

Re: Kafka Streams - partition assignment for the input topic

2020-03-19 Thread Guozhang Wang
Hi Stephen, We've deprecated the partition-grouper API due to its drawbacks in upgrading compatibility (consider if you want to change the num.partitions while evolving your application), and instead we're working on KIP-221 for the same purpose of your use case:

kafka-configs SCRAM passwords and square brackets

2020-03-19 Thread Pedro Magalhães
Hi all, I wanted to enable SCRAM-SHA-512 mechanism for a kafka cluster but I'm having an issue on trying to setup the password for one of the existing users. The problem is that the password contains a square bracket `[` and it seems impossible to escape it for the kafka-configs.sh tool. What I'm

Re: Kafka JMX monitoring

2020-03-19 Thread George
I would re-iterate Prometheus, it allows for node_collector that also gives you OS metrics, + the JMX integration that tells you how the Java servers are doing + the topic depth modules. All going into prometheus, all visualised nicely as one pane of glass via Grafana. and well if you doing

Re: Kafka JMX monitoring

2020-03-19 Thread Sachin Mittal
How about jmxterm. https://cwiki.apache.org/confluence/display/KAFKA/jmxterm+quickstart I have found this very helpful. On Thu, Mar 19, 2020 at 3:51 PM Gioacchino Vino wrote: > Hi, > > > I would like to share my experience with you. > > Even if I found out that prometheus is the a simple and

Re: Kafka JMX monitoring

2020-03-19 Thread Gioacchino Vino
Hi, I would like to share my experience with you. Even if I found out that prometheus is the a simple and fast solution, since I'm using InfluxDB (and Telegraf) in my project, I'm using the chain: Jolokia -> Telegraf -> InfluxDB -> Grafana Some useful links: https://jolokia.org/

Re: I'm trying to connect to a kafka broker running in AWS EKS (from outside the EKS cluster).

2020-03-19 Thread Robin Moffatt
You need to make sure you've configured your listeners & advertised listeners correctly. This should help: https://rmoff.net/2018/08/02/kafka-listeners-explained/ -- Robin Moffatt | Senior Developer Advocate | ro...@confluent.io | @rmoff On Thu, 19 Mar 2020 at 01:49, Dan Hill wrote: >

Re: Kafka JMX monitoring

2020-03-19 Thread sunil chaudhari
If you are not aware of Grafana and Prometheus then... You can enable JMx_PORT on kafka broker. Install and run kafka manager. https://github.com/lemastero/kafka-manager There you can see metrics on kafka manager UI. But yes, grafana-prometheus is Better one. On Thu, 19 Mar 2020 at 12:25 PM,

Re: Kafka JMX monitoring

2020-03-19 Thread George
How about using JMP -> Prometheus integration. Then you can visualise using Grafana and you can use the Prometheus alert / notification framework also. G On Thu, Mar 19, 2020 at 8:55 AM 张祥 wrote: > Hi, > > I want to know what the best practice to collect Kafka JMX metrics is. I > haven't

Kafka JMX monitoring

2020-03-19 Thread 张祥
Hi, I want to know what the best practice to collect Kafka JMX metrics is. I haven't found a decent way to collect and parse JMX in Java (because it is too much) and I learn that there are tools like tools like jmxtrans to do this. I wonder if there is more. Thanks. Regards.

RE: I'm trying to connect to a kafka broker running in AWS EKS (from outside the EKS cluster).

2020-03-19 Thread Pirow Engelbrecht
Hi Dan, For Kafka: * Make sure that your listeners and advertised listener configuration is set up correctly for external connectivity, incl. your Kafka protocols For Kubernetes: * How are you exposing the Kafka port? Your port number seems low for Kubernetes, typically external