-
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
[filebeat] Initial port of powershell winlogbeat module #40519
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
This pull request doesn't have a |
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
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.
Can you add an entry in the CODEOWNERS file for /x-pack/filebeat/module/windows ?
This pull request is now in conflicts. Could you fix it? 🙏
|
Moved to draft since we need a bit more discussion around this |
This pull request is now in conflicts. Could you fix it? 🙏
|
Proposed commit message
Convert winlogbeat powershell and powershell_operational module into a new filebeat module using the winlog input.
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
winlogbeat
in favor offilebeat
winlog
input. #40074