[bitnami/kafka] jmx-metrics servicemonitor has wrong path

[horihel]

Name and Version

bitnami/kafka-29.3.4

What architecture are you using?

amd64

What steps will reproduce the bug?

1. install kafka with metrics.jmx.enabled=true and metrics.serviceMonitor.enabled=true
2. prometheus-operator will pick up the new service
3. target reports as DOWN in prometheus with error expected a valid start token, got "<" ("INVALID") while parsing: "<"

Are you using any custom parameters or values?

--set metrics.jmx.enabled=true --set metrics.serviceMonitor.enabled=true

What is the expected behavior?

prometheus being able to scrape metrics

What do you see instead?

expected a valid start token, got "<" ("INVALID") while parsing: "<"

Additional information

It looks like the recent upgrade to jmx-metrics 1.0 changed the path which metrics are exposed. jmx-exporter no longer exposes metrics on the root path, instead, they are exposed on /metrics

I think this can be easily solved by changing the path in the serviceMonitor to /metrics instead of /

[carrodher]

Thank you for bringing this issue to our attention. We appreciate your involvement! If you're interested in contributing a solution, we welcome you to create a pull request. The Bitnami team is excited to review your submission and offer feedback. You can find the contributing guidelines here.

Your contribution will greatly benefit the community. Feel free to reach out if you have any questions or need assistance.

[horihel]

PR is ready for review.

[carrodher]

Thank you for opening this issue and submitting the associated Pull Request. Our team will review and provide feedback. Once the PR is merged, the issue will automatically close.

Your contribution is greatly appreciated!