[receiver/jmx] Ability to discovery jmx endpoints dynamically

open-telemetry / opentelemetry-collector-contrib

Contrib repository for the OpenTelemetry Collector

https://opentelemetry.io

Apache License 2.0

2.71k stars 2.14k forks source link

[receiver/jmx] Ability to discovery jmx endpoints dynamically #31599

Open neo-waiariki-koia opened 3 months ago

neo-waiariki-koia commented 3 months ago

Component(s)

receiver/jmx

Is your feature request related to a problem? Please describe.

At the moment, the endpoint for jmx receiver has to be hardcoded. Unfortunately, for my use case, this isn't feasible. I was hoping some sort of service discovery mechanism could be implemented to find endpoints dynamically? The prometheus receiver has this and, although different, Datadog agents can facilitate similar functionality.

Describe the solution you'd like

I'd like for the ability to discover jmx endpoints dynamically within a Kubernetes cluster. This could be done by filtering pods based on fields, labels or annotations.

Describe alternatives you've considered

No response

Additional context

No response

github-actions[bot] commented 3 months ago

Pinging code owners:

receiver/jmx: @rmfitzpatrick

See Adding Labels via Comments if you do not have permissions to add labels yourself.

JaredTan95 commented 3 months ago

From your description, I think it might be more appropriate to put this requirement into otel-operator?

joerg commented 3 months ago

+1 for that feature. Currently, fetching other metrics than the built in ones requires building a custom jar file (see https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/17072) which is an unreasonable amount of overhead for just a list of metrics to gather. In my case, I need to gather metrics from the Atlassian tools (e.g. Jira https://confluence.atlassian.com/adminjiraserver/live-monitoring-using-the-jmx-interface-939707304.html) which would require me to:

write the custom groovy script
build the jar file
and then build a custom otel-collector supporting my custom target system (https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/jmxreceiver/config.go#L200).

github-actions[bot] commented 1 month ago

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

receiver/jmx: @rmfitzpatrick

See Adding Labels via Comments if you do not have permissions to add labels yourself.