feat(windows-agent): Add Windows Event Logger support #764
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This changes the default logging method from file logging to using the Windows Event Logger. File logging is still available through the use of the new
--file-log-enabled
flag (and its accompanying--event-log-enabled
flag, which is enabled by default).You can view logs on Windows 11 by searching for the
Event Viewer
application and creating a Custom View for all event levels of the "Application" logs.The
eventlog
support from Golang doesn't seem to include a debug function, so all debug logs are rerouted as info-level logs in the event viewer. In addition, there are event IDs which essentially go unused in this use case (0
) as I believe they're mostly OS-specific event types and would be hard to utilize through the logging methods we're currently using.UDENG-2323