Component(s)

receiver/jmx

Describe the issue you're reporting

Requiring the Collector to run Java is problematic, especially since the Collector is commonly deployed as a Docker image and none of the official images ship a Java runtime, resulting in a broken user experience. Managing a standalone Java process is better handled through traditional mechanisms, not via Collector-managed subprocesses.

More broadly, the Collector should not run subprocesses at all; the jmxreceiver is an exception that sets an undesirable precedent, even with its checksum-based restrictions. This issue is closely tied to the lack of Java tooling in distributed Collector images.

Context: #34825 (comment)

• Change component stability to deprecated
• Remove the component from distributions by June 2026
• Remove the code for this component by July 2026

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}