-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
jmx receiver autodiscover targets in kubernetes? #32965
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hey, this seems like a dupe of 31599, could I mark it as such? TL;dr is that there are extensions/observers that can, in conjunction with @ datadog, it seems they have you specify a port for autodiscovery
in the context of the docker observer/receiver_creator, you would specify redis/1:
# If this rule matches an instance of this receiver will be started.
rule: type == "port" && port == 6379
config:
# Static receiver-specific config.
password: secret
# Dynamic configuration value.
collection_interval: '`pod.annotations["collection_interval"]`' |
@hughesjj feel free to mark this as a duplicate. I am going to close this issue. |
Component(s)
receiver/jmx
Is your feature request related to a problem? Please describe.
The problem is that the endpoint has to be hardcoded: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/jmxreceiver#endpoint
datadog's jmx can autodiscovery: https://docs.datadoghq.com/containers/guide/autodiscovery-with-jmx/?tab=operator
Describe the solution you'd like
Some mechanism for autodiscovery of jmx endpoints for kubernetes.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: