fix(otel): remove SDK dependencies to prevent duplicate logs with Java agent#16
Merged
Conversation
…a agent When the Dash0 operator injects the OTEL Java agent, having the opentelemetry-spring-boot-starter and SDK dependencies in the application causes double instrumentation - both the embedded SDK and the agent capture and export logs, resulting in duplicates. This removes all SDK/starter dependencies and keeps only the API for manual instrumentation. The agent now handles all telemetry export exclusively.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
opentelemetry-spring-boot-starterand related SDK dependencies from all servicesopentelemetry-apifor manual instrumentation (custom spans)OpenTelemetryConfigclasses to useGlobalOpenTelemetry.get()instead of injected beansProblem
When the Dash0 operator injects the OTEL Java agent, having the
opentelemetry-spring-boot-starterand SDK dependencies embedded in the application causes double instrumentation:Both capture and export the same logs to OTLP, resulting in exact duplicate log entries in the backend.
Solution
Remove all SDK/starter dependencies and let the Dash0-injected Java agent be the sole source of telemetry export. The application retains only the API dependency for manual instrumentation like custom spans.