-
Notifications
You must be signed in to change notification settings - Fork 41.1k
Relocate OpenTelemetryLoggingAutoConfiguration and SdkLoggerProviderBuilderCustomizer to an OpenTelemetry-specific package #44647
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
Comments
We discussed this today and we'd like to relocate them. We'd like to aim for 3.5, but if the customizer causes too much of an issue we'll push this back to 4.0.0 |
I've moved them to The moved |
Was I know that we have |
I tried mirroring the existing OpenTelemetry support for tracing. Tracing is in If we move Our usual package structure is |
I guess it comes down to whether we consider the auto-configuration to primarily be a logging-related feature or an OpenTelemetry-related feature. It feels like the latter to me. |
We discussed this today and decided to revert the change in 3.5 and deal with it in 4.0 instead. |
OpenTelemetryLoggingAutoConfiguration
andSdkLoggerProviderBuilderCustomizer
are inorg.springframework.boot.actuate.autoconfigure.logging
. I think they should be in an OpenTelemetry-specific package as none of other code inorg.springframework.boot.actuate.autoconfigure.logging
has any third-party dependencies.If we were just the auto-configuration class, we could make this change fairly easily in 3.5 however there's the customizer to consider too.
The text was updated successfully, but these errors were encountered: