Fix issues in open_telemetry_javaagent and splunk_java_agent frameworks#1239
Merged
Conversation
ramonskie
approved these changes
Apr 17, 2026
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
2 participants
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.
The PR addresses certain issues in the
open_telemetry_javaagentandsplunk_java_agentframeworks. It also introduces refactoring and additional unit tests.-Dotel.service.nameis wrongly set. It is now obtained from VCAP_APPLICATION and adjusted properly.splunk-o11ywhich was anticipated in the ruby based implementation. Don't contribute splunk otel agent if not expected by having only some sort ofotelnamed service or tag. With regard to not expected splunk's otel contribution #1236