-
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
Winlogbeat: Experimental API wrong message extraction with invalid events #19338
Comments
Pinging @elastic/siem (Team:SIEM) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
Hi! We're labeling this issue as |
Hi! We're labeling this issue as |
Pinging @elastic/sec-windows-platform (Team:Security-Windows Platform) |
I have an event with holding two data attributes, one is a string, the other is binary. The binary type currently isn't supported ( See also: #19337 )
Having the default api enabled, the event I receive looks like the one referenced in Issue 19337:
Using the experimental API, one can see that the
message
field is still wrong, even though that was part of a parseable data field from the event data (I have many events of the same type on my system, so I pick a possibly different one here compared to the above one with a different API, but makes the point still clear):Looks like,
message
lacks some kind of template extraction logic here...The text was updated successfully, but these errors were encountered: