Class OtlpTracingAutoConfiguration
java.lang.Object
org.springframework.boot.actuate.autoconfigure.tracing.otlp.OtlpTracingAutoConfiguration
@AutoConfiguration
@ConditionalOnClass({io.micrometer.tracing.otel.bridge.OtelTracer.class,io.opentelemetry.sdk.trace.SdkTracerProvider.class,io.opentelemetry.api.OpenTelemetry.class,io.opentelemetry.exporter.otlp.http.trace.OtlpHttpSpanExporter.class})
@EnableConfigurationProperties(OtlpTracingProperties.class)
@Import({org.springframework.boot.actuate.autoconfigure.tracing.otlp.OtlpTracingConfigurations.ConnectionDetails.class,org.springframework.boot.actuate.autoconfigure.tracing.otlp.OtlpTracingConfigurations.Exporters.class})
public class OtlpTracingAutoConfiguration
extends Object
Auto-configuration
for exporting traces with OTLP.
Brave does not support OTLP, so we only configure it for OpenTelemetry. OTLP defines
three transports that are supported: gRPC (/protobuf), HTTP/protobuf, HTTP/JSON. From
these transports HTTP/JSON is not supported by the OTel Java SDK, and it seems there
are no plans supporting it in the future, see: opentelemetry-java#3651.
Because this class configures components from the OTel SDK, it can't support HTTP/JSON.
By default, we auto-configure HTTP/protobuf. If you want to use gRPC, you need to set
management.otlp.tracing.transport=grpc
. If you define a
OtlpHttpSpanExporter
or OtlpGrpcSpanExporter
, this auto-configuration
will back off.- Since:
- 3.4.0
- Author:
- Jonatan Ivanov, Moritz Halbritter, EddĂș MelĂ©ndez
-
Constructor Summary
-
Method Summary
-
Constructor Details
-
OtlpTracingAutoConfiguration
public OtlpTracingAutoConfiguration()
-