You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
|`otel.jmx.service.url`| - | mandatory JMX URL to connect to the remote JVM |
42
+
|`otel.jmx.target.system`| - | comma-separated list of systems to monitor, mandatory unless `otel.jmx.config` is set |
43
+
|`otel.jmx.config`| empty | comma-separated list of paths to custom YAML metrics definition, mandatory when `otel.jmx.target.system` is not set |
44
+
|`otel.jmx.username`| - | user name for JMX connection, mandatory when JMX authentication is set on target JVM with`com.sun.management.jmxremote.authenticate=true`|
45
+
|`otel.jmx.password`| - | password for JMX connection, mandatory when JMX authentication is set on target JVM with `com.sun.management.jmxremote.authenticate=true`|
46
+
|`otel.jmx.remote.registry.ssl`|`false`| connect to an SSL-protected registry when enabled on target JVM with `com.sun.management.jmxremote.registry.ssl=true`|
47
+
48
+
When both `otel.jmx.target.system` and `otel.jmx.config` configuration options are used at the same time:
49
+
50
+
-`otel.jmx.target.system` provides ready-to-use metrics and `otel.jmx.config` allows to add custom definitions.
51
+
- The metrics definitions will be the aggregation of both.
52
+
- There is no guarantee on the priority or any ability to override the definitions.
53
+
54
+
If there is a need to override existing ready-to-use metrics or to keep control on the metrics definitions, using a custom YAML definition with `otel.jmx.config` is the recommended option.
0 commit comments