Cherry-pick #18159 to 7.x: Add a disable_host option to Filebeat inputs #18188
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
botelastic
bot
added
the
needs_team
This adds a configuration option `publisher_pipeline.disable_host` to disable the addition of `host.name` in events. By default Filebeat adds `host.name` to all events and we want to be able to disable this for data sources that do not originate on the host (like cloud logs). Relates elastic#13920 (cherry picked from commit 6ea21a9)
andrewkroh
force-pushed
the
backport_18159_7.x
branch
from
d91d360 to
7abf29c
Compare
💔 Build Failed
Expand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
Looks like the PR needs rebase due to CHANGELOG conflict, though. |
andrewkroh
added
Team:SIEM
and removed
needs_team
|
Pinging @elastic/siem (Team:SIEM) |
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 #18159 to 7.x branch. Original message:
What does this PR do?
This adds a configuration option
publisher_pipeline.disable_hostto disable the additionof
host.namein events. By default Filebeat addshost.nameto all events and we wantto be able to disable this for data sources that do not originate on the host (like cloud logs).
Relates #13920
Why is it important?
ECS host.* fields should be populated with details about the host on which the event happened, or from which the measurement was taken. For some data sources Filebeat does not know that actual host and it should not use its own host name in these events. This gives a way to turn this off.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
Run Filebeat and verify that the output does not have host.name.
Use cases
This will be used by several modules: