Cherry-pick #7051 to 6.3: Add host.name in the events #7068
Conversation
This file contains 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
As a solution for elastic#7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050. (cherry picked from commit 15d9539)
|
jenkins test this again |
leweafan
pushed a commit
to leweafan/beats
that referenced
this pull request
Apr 28, 2023
…#7068) * Add host.name in the events (elastic#7051) As a solution for elastic#7050, we're adding a `host.name` field to all events. This is duplicate information from `beat.name`, but is used to avoid the mapping conflict and to slowly introduce the "host as an object" approach. To remove the duplication, you can remove `beat.name` like this: processors: - drop_fields.fields: ["beat.name"] Closes elastic#7050. (cherry picked from commit 1889f9c) * changelog cleanup
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.
Cherry-pick of PR #7051 to 6.3 branch. Original message:
As a solution for #7050, we're adding a
host.namefield toall events. This is duplicate information from
beat.name,but is used to avoid the mapping conflict and to slowly
introduce the "host as an object" approach.
To remove the duplication, you can remove
beat.namelike this:Closes #7050.