-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Provide more control over the OTel SpanProcessors #35560
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
Labels
Milestone
Comments
MetricExporter
in default SpanProcessor
Just to clarify: You mean |
I implemented two changes:
|
That's all I need :) Thank you! |
Thanks for the feedback and glad that this solves your problem! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
SpringBootVersion
: 3.0.6I was hoping to configure
MetricExporter
in defaultSpanProcessor
provided inOpenTelemetryAutoConfiguration
OpenTelemetry code: https://github.com/open-telemetry/opentelemetry-java/blob/0bad3c982ad05f54461e241f8a402536c6f9d4b9/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/export/BatchSpanProcessor.java#L187-L219
Current workaround:
Create
@Primary
SpanProcessor
bean and redeclareSdkTracerProvider
(using customSpanProcessor
bean). One downside is that 2 SpanProcessor beans are created with dandling default one.If possible I would like to have a simple way to overwrite
SpanProcessor
beanIn PR discussion: #35558
The text was updated successfully, but these errors were encountered: