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
Copy file name to clipboardExpand all lines: javaagent/sdk-config.yaml
+64Lines changed: 64 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -39,12 +39,67 @@ meter_provider:
39
39
aggregation:
40
40
drop:
41
41
42
+
# Configure otel java agent instrumentation. A standard translation process applied to convert the flat system properties / env var configuration scheme from https://opentelemetry.io/docs/zero-code/java/agent/ to the structured scheme used by declarative configuration:
43
+
#
44
+
# - Only properties starting with "otel.instrumentation." are resolved
45
+
# - Strip the "otel.instrumentation." prefix.
46
+
# - Split the remaining property string on "." character to break into segments
47
+
# - Starting at .instrumentation.java, follow N-1 segments to resolve the leaf node to read the property from
48
+
# - Read segment N from the resolved leaf node
49
+
#
50
+
# For example, the property "otel.instrumentation.common.default-enabled" is resolved by reading: .instrumentation.java.common.default-enabled
51
+
#
52
+
# Some system properties / env vars cannot be configured via declarative configuration, normally because they are resolved in the application lifecycle before declarative configuration is available. The set of unsupported properties includes:
53
+
# - otel.javaagent.enabled
54
+
# - otel.javaagent.configuration-file
55
+
# - otel.javaagent.extensions
56
+
# - otel.javaagent.logging
57
+
# - otel.resource.providers.[provider].enabled
58
+
# TODO: add automation to keep this in sync with system property / env var documentation: https://opentelemetry.io/docs/zero-code/java/agent/
0 commit comments