[AutoOps] Reuse Common Fields and Drop non-standard ones#45101
Merged
Conversation
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
0ce4577 to
87b7ee5
Compare
This drops custom fields that duplicate fields coming from Metricbeat through OTel in ECS format.
87b7ee5 to
6908b08
Compare
maramos-elastic
approved these changes
Jun 28, 2025
mergify Bot
pushed a commit
that referenced
this pull request
Jun 30, 2025
This drops custom fields that duplicate fields coming from Metricbeat through OTel in ECS format. (cherry picked from commit 9866af4)
1 task
6 tasks
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
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.
This drops custom fields that duplicate fields coming from Metricbeat through OTel in ECS format.
Proposed commit message
Deduplicate the reported fields.
Disruptive User Impact
None. This is an unreleased feature.
Author's Checklist
How to test this PR locally
Run this within the Elastic Agent via OTel and push to the dev service to ensure that fields are still properly parsed.