-
Notifications
You must be signed in to change notification settings - Fork 444
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
winlog: improve documentation for obtaining channel names #5689
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
🌐 Coverage report
|
log channels by running `Get-EventLog *` in PowerShell. Custom ingest | ||
pipelines may be added by setting one up in | ||
[Ingest Node Pipelines](/app/management/ingest/ingest_pipelines/). | ||
The custom Windows event log package allows you to ingest events from any [Windows event log](https://docs.microsoft.com/en-us/windows/win32/wes/windows-event-log) channel. |
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.
Just a quick question on that, should be documented as well that accepted channel names can contain spaces as well?
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.
Is that not well understood?
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.
Package winlog - 1.12.4 containing this change is available at https://epr.elastic.co/search?package=winlog |
What does this PR do?
Improves documentation for obtaining channel names.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Screenshots