-
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
Make it possible to disable host metadata #17919
Make it possible to disable host metadata #17919
Conversation
This provides a way to disable the addition of host metadata without introducing a breaking change. By setting @metadata.internal.distable_host_metadata=true in an event this will disable the addition of host.name by libbeat and disable add_host_metadata if it exists in the pipeline. This can be removed in 8.0 if we disable host.name is libbeat and modify how the default configurations.
The PANW module always forwards data from another device so Filebeat should not set the host fields.
3d01296
to
04706b0
Compare
Pinging @elastic/integrations (Team:Integrations) |
One can 'disable' adding 'Host' altogether when constructing a Beat. Where would you use this changes? I'd prefer if we can do without this feature. Instead of adding some magic fields to |
💔 Build FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
I'm going to close this change. I made a smaller change to add a Filebeat input setting to disable |
What does this PR do?
This provides a way to disable the addition of host metadata without introducing a breaking change. By setting
@metadata.internal.distable_host_metadata=true
in an event this will disable the addition ofhost.name
by libbeat and disableadd_host_metadata
if it exists in the pipeline.This can be removed in 8.0 if/when we disable
host.name
is libbeat and modify the default Beat configurations.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. Some data sources only forward data and it would be incorrect to set
host.*
fields.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Relates #13920