Unable to setup metrics

[adamelmohamad]

Issue submitter TODO list

• [X] I've looked up my issue in FAQ
• [X] I've searched for an already existing issues here
• [X] I've tried running master-labeled docker image and the issue still persists there
• [X] I'm running a supported version of the application which is listed here

Describe the bug (actual behavior)

I'm unable to setup JMX metrics for my cluster

Expected behavior

No response

Your installation details

A docker container running the 'provectus/kafka-ui' image is deployed using AWS CDK. Esentially, an ECS service is being used to run the kafka-ui. Environment variables are as follows. Of course, the cluster and bootstrap server names have been replaced by dummy values in the example below. Kafka-UI is working fine apart from this metrics issue:

        KAFKA_CLUSTERS_0_NAME: 'cluster-0',
        KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS: 'server-1, server-2',
        KAFKA_CLUSTERS_0_READONLY: 'true',
        KAFKA_CLUSTERS_0_METRICS_PORT: '11001',
        KAFKA_CLUSTERS_0_PROPERTIES_SECURITY_PROTOCOL: 'SASL_SSL',
        KAFKA_CLUSTERS_0_PROPERTIES_SASL_MECHANISM: 'SCRAM-SHA-512',
        KAFKA_CLUSTERS_0_PROPERTIES_SASL_JAAS_CONFIG: `org.apache.kafka.common.security.scram.ScramLoginModule required username="user" password="pass";`,
        DYNAMIC_CONFIG_ENABLED: 'true',

Steps to reproduce

• Configure JMX in kafka broker
• Start kafka-ui with metrics

Screenshots

No response

Logs

0 metrics collected for service:jmx:rmi:///jndi/rmi://cluster-0/jmxrmi at com.provectus.kafka.ui.service.metrics.JmxMetricsRetriever.withJmxConnector(JmxMetricsRetriever.java:79)at com.provectus.kafka.ui.service.metrics.JmxMetricsRetriever.retrieveSync(JmxMetricsRetriever.java:66) at com.provectus.kafka.ui.service.metrics.JmxMetricsRetriever.lambda$retrieve$0(JmxMetricsRetriever.java:52)

Additional context

No response

[github-actions[bot]]

Hello there adamelmohamad! 👋

Thank you and congratulations 🎉 for opening your very first issue in this project! 💖

In case you want to claim this issue, please comment down below! We will try to get back to you as soon as we can. 👀