Open theodiefenthal opened 4 years ago
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 just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
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: https://github.com/elastic/beats/issues/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...