[elasticapmprocessor] - do not disable AgentName and AgentVersion in ECS mode #758
Conversation
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
girodav
approved these changes
Oct 20, 2025
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.
elastic/opentelemetry-lib#229 is a prerequisite for this - until that the corresponding test fails.update: that's mergedWhen OTLP receiver (for OTel SDKs) is used and set to
ecsmode, then agent.name and version were not calculated due to these lines.agent.nameis required in Kibana -without that the APM UI throws an exceptionelastic/opentelemetry-lib#229 has more details on the complete plan - and also linking internal issue.