-
Notifications
You must be signed in to change notification settings - Fork 40.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add auto-configuration for OTLP span exporter #34390
Comments
Yes, I found Jaeger UI is more user friendly when displaying tracing data(e.g. Better span name and SQL displayed nicely inside span) I wish spring boot 3 (micrometer) can export trace data to Jaeger. Like what it used to do with spring cloud sleuth. |
This issue is about OTLP really, does not have too much to do with Jaeger specifically. The Jaeger collector can accept spans in the Zipkin format so you should be able to use Jaeger out of the box. Right now you can create a |
Followed @jonatan-ivanov hint and get Jaeger working. Here is a sample repo https://github.com/sivaprasadreddy/spring-boot-opentelemetry-demo However, as Jaeger is a very popular choice, having auto-configuration support would be great. |
With these changes an OTLP exporter is auto-configured if opentelemetry-exporter-otlp is on the classpath by default HTTP is used but gRPC is also available Closes spring-projectsgh-34390
With these changes an OTLP exporter is auto-configured if opentelemetry-exporter-otlp is on the classpath. By default HTTP is used but gRPC is also available. Closes spring-projectsgh-34390
With these changes an OTLP HTTP/protobuf exporter is auto-configured if opentelemetry-exporter-otlp is on the classpath. Closes spring-projectsgh-34390
With these changes an OTLP HTTP/protobuf exporter is auto-configured if opentelemetry-exporter-otlp is on the classpath. Closes spring-projectsgh-34390
Closing in favor of #34508. |
Currently, only Zipkin (
ZipkinSpanExporter
) and Wavefront (WavefrontOtelSpanExporter
) exporters are supported in auto configuration when using OpenTelemetry as the tracer.Since there are many OpenTelemetry backends that support OTLP, it would be very useful to have OTLP exporter support as well.
Actually spring-cloud-sleuth-otel has such an auto configuration.
https://github.com/spring-projects-experimental/spring-cloud-sleuth-otel/blob/main/spring-cloud-sleuth-otel-autoconfigure/src/main/java/org/springframework/cloud/sleuth/autoconfig/otel/OtelExporterConfiguration.java
The text was updated successfully, but these errors were encountered: