-
Notifications
You must be signed in to change notification settings - Fork 419
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
[docs] Add context to Windows integration documentation #3352
[docs] Add context to Windows integration documentation #3352
Conversation
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.
Haven't tested the build yet, but everything looks good. One small nit.
🌐 Coverage report
|
|
||
### Forwarded | ||
|
||
The Windows `forwarded` dataset provides events from the Windows | ||
`ForwardedEvents` event log. The fields will be the same as the | ||
channel specific datasets. | ||
|
||
#### Permissions | ||
|
||
This data should be available without elevated permissions. |
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.
The permissions requirements seem odd to mention because AFAIK the whole Elastic Agent is required to run as a service account which has elevated permissions.
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.
I included this because in the System integration, there are different levels of permission needed for different data streams (see this PR), but if that's not the case for the Windows integration I can remove these!
What does this PR do?
From elastic/observability-docs#1019:
This PR adds more context the Windows integration including:
For the reviewer
Checklist
changelog.yml
file.Author's Checklist
Related issues