-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a disable_host option to Filebeat inputs #18159
Add a disable_host option to Filebeat inputs #18159
Conversation
Pinging @elastic/siem (Team:SIEM) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
The change LGTM. The default filebeat configuration contains |
Yes, I'm thinking to update the example config to show how put a condition on the |
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
7fcdd77
to
2f4c846
Compare
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)
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 #13920 (cherry picked from commit 6ea21a9)
What does this PR do?
This adds a configuration option
publisher_pipeline.disable_host
to disable the additionof
host.name
in events. By default Filebeat addshost.name
to 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.asciidoc
orCHANGELOG-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: