[9.2] (backport #10588) [otel] Add back elastictrace processor#10609
Merged
[9.2] (backport #10588) [otel] Add back elastictrace processor#10609
Conversation
* [otel] Add back elastictrace processor * bump elasticapm processor version This version adds a public function used by the elastictrace processor * Create 1760538256-add_back_elastictrace_processor.yaml * Update go.mod * Update go.sum * Update notice files * Update readme and testdata files * Update deprecated-components.yaml (cherry picked from commit 7a4b56c)
Contributor
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
cmacknz
approved these changes
Oct 15, 2025
Contributor
⏳ Build in-progress, with failures
Failed CI StepsHistory
cc @gregkalapos |
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
4 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.
What does this PR do?
This PR adds back the
elastictraceprocessor to the EDOT collector and bumps the version to v0.12.0.This version is marked as deprecated (in favor of the
elasticapmprocessor) and just wraps theelasticapmprocessor itself.Why is it important?
This way, we don't break users. The
elastictraceprocessor is marked as a core component and we don't want to just remove it. Therefore, we'll keep one around for existing users, so they can gradually move to theelasticapmprocessor.Checklist
./changelog/fragmentsusing the changelog toolI have added an integration test or an E2E testDisruptive User Impact
How to test this PR locally
Related issues
Questions to ask yourself
This is an automatic backport of pull request #10588 done by [Mergify](https://mergify.com).