-
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
Cherry-pick #18153 to 7.x: [Winlogbeat] Skip add_host_metadata for forwarded event logs #18183
Conversation
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)
Pinging @elastic/siem (Team:SIEM) |
💔 Build FailedExpand 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
|
Cherry-pick of PR #18153 to 7.x branch. Original message:
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.