All other "normal" fields can be filtered and indexed without any problem
Not sure if this is important but this winlog event is from Trendmicro AV system
The data you want might already be in there. For most Windows events that's where you'll find the raw data that contributes to the message. But for third-party events you sometime just get a single string. When that happens you have to parse the message with tools like dissect or grok processors.
I added to winlogbeat.yml config file but with no results. No errors on winlogbeat side. I did config to have the same amount of fields as log have but it didn't help. Also i removed condition for event.code = 500 but also without success. Is anything more which has to be configured?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.