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.exporter=jaeger | OTEL_EXPORTER=jaeger| To select Jaeger exporter|
67
+
|otel.jaeger.endpoint| OTEL_JAEGER_ENDPOINT| The Jaeger endpoint to connect to, default is "localhost:14250", currently only gRPC is supported. |
68
+
|otel.jaeger.service.name | OTEL_JAEGER_SERVICE_NAME | The service name of this JVM instance, default is "unknown".|
69
69
70
70
#### Zipkin exporter
71
71
A simple wrapper for the Zipkin exporter of opentelemetry-java. It POSTs json in [Zipkin format](https://zipkin.io/zipkin-api/#/default/post_spans) to a specified HTTP URL.
72
72
73
-
| System property | Environment variable| Purpose|
|otel.exporter=zipkin | OTEL_EXPORTER=zipkin| To select Zipkin exporter|
76
+
| otel.zipkin.endpoint | OTEL_ZIPKIN_ENDPOINT | The Zipkin endpoint to connect to, default is "http://localhost:9411/api/v2/spans". Currently only HTTP is supported. |
77
+
| otel.zipkin.service.name | OTEL_ZIPKIN_SERVICE_NAME | The service name of this JVM instance, default is "unknown".|
78
78
79
79
#### OTLP exporter
80
80
81
81
A simple wrapper for the OTLP exporter of opentelemetry-java.
82
82
83
83
| System property | Environment variable | Purpose |
| ota.propagators | OTA_PROPAGATORS | Default is "tracecontext" (W3C). Other supported values are "b3", "b3single", "jaeger". |
108
+
If this is set to a comma-delimited list of the values, the multi-propagator will be used.
109
+
The multi-propagator will try to extract the context from incoming requests using each of the configured propagator formats (in order), stopping after the first successful context extraction.
110
+
The multi-propagator will inject the context into outgoing requests using all the configured propagator formats.
111
+
112
+
| System property | Environment variable | Purpose |
|otel.resource.attributes| OTEL_RESOURCE_ATTRIBUTES | Used to specify resource attributes in format: key1=val1,key2=val2,key3=val3 |
120
124
121
125
#### Batch span processor
122
126
@@ -154,7 +158,7 @@ The OpenTelemetry API exposes SPI [hooks](https://github.com/open-telemetry/open
154
158
for customizing its behavior, such as the `Resource` attached to spans or the `Sampler`.
155
159
156
160
Because the auto instrumentation runs in a separate classpath than the instrumented application, it is not possible for customization in the application to take advantage of this customization. In order to provide such customization, you can
157
-
provide the path to a JAR file including an SPI implementation using the system property `ota.initializer.jar`. Note that this JAR will need to shade the OpenTelemetry API in the same way as the agent does. The simplest way to do this is to use the same shading configuration as the agent from [here](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/cfade733b899a2f02cfec7033c6a1efd7c54fd8b/java-agent/java-agent.gradle#L39). In addition, you will have to specify the `io.opentelemetry.auto.shaded.io.opentelemetry.trace.spi.TraceProvider` to the name of the class that implements the SPI.
161
+
provide the path to a JAR file including an SPI implementation using the system property `otel.initializer.jar`. Note that this JAR will need to shade the OpenTelemetry API in the same way as the agent does. The simplest way to do this is to use the same shading configuration as the agent from [here](https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/cfade733b899a2f02cfec7033c6a1efd7c54fd8b/java-agent/java-agent.gradle#L39). In addition, you will have to specify the `io.opentelemetry.auto.shaded.io.opentelemetry.trace.spi.TraceProvider` to the name of the class that implements the SPI.
158
162
159
163
## Supported Java libraries and frameworks
160
164
@@ -220,8 +224,8 @@ For this reason the following instrumentations are disabled by default:
220
224
-`servlet-filter` which creates spans around Servlet Filter methods.
221
225
-`servlet-service` which creates spans around Servlet methods.
222
226
223
-
To enable them, add `ota.integration.<name>.enabled` system property:
224
-
`-Dota.integration.jdbc-datasource.enabled=true`
227
+
To enable them, add `otel.integration.<name>.enabled` system property:
228
+
`-Dotel.integration.jdbc-datasource.enabled=true`
225
229
226
230
#### Grizzly instrumentation
227
231
@@ -231,7 +235,7 @@ Servlet-based applications, you get better experience from Servlet-specific
231
235
support. As these two instrumentations conflict with each other, more generic
232
236
instrumentation for Grizzly http server is disabled by default. If needed,
233
237
you can enable it by add the following system property:
0 commit comments