-
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
[Winlogbeat] Skip add_host_metadata for forwarded event logs #18153
[Winlogbeat] Skip add_host_metadata for forwarded event logs #18153
Conversation
587b765
to
1eab800
Compare
Pinging @elastic/siem (Team:SIEM) |
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
bd5428b
to
14beac3
Compare
Update config examples to use the "forwarded" tag to skip adding host metadata. Also disable host.name being added by libbeat. This field was overwritten by the winlog.computer_name so it didn't serve any purpose to have libbeat set it. Relates elastic#13920
14beac3
to
5ff2233
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Update config examples to use the "forwarded" tag to skip adding host metadata. Also disable host.name being added by libbeat. This field was overwritten by the winlog.computer_name so it didn't serve any purpose to have libbeat set it. Relates elastic#13920 (cherry picked from commit f80f82c)
What does this PR do?
Update config examples to use the "forwarded" tag to skip adding host metadata.
Also disable host.name being added by libbeat. This field was overwritten by
the winlog.computer_name so it didn't serve any purpose to have libbeat set it.
Relates #13920
Why is it important?
Having
host.*
fields populated with data from the system on which the event occurred is important for interpreting and reacting to the data.Checklist
- [ ] I have made corresponding changes to the documentationCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Relates #13920
Use cases
When reading from
ForwardedEvents
in a Windows Event Collector (WEC) setup you don't want the WEC machine using it's own host metadata in forwarded events. This solves that problem.