I don't understand your logic. Let's test with 3 matching event_id's, one each where TargetUserName is "Administrator", "root", and "bob".
You drop "Administrator" because it is not "root". You drop "root" because it is not "Administrator", you drop "bob" because both match. It looks your logic logic drops everything.
If that doesn't help, your syntax and error messages would help.
I think it's very confusing logic, someone else on our team handles these, I tend to send it all to logstash and let it sort it out. But, I think it's something like this:
Thanks very much I will give it a shot..
why is it confusing .. don‘t get your point.. for me your config is confusing :‘)
because i want drop event 6524 when username not administrator or root..
the code you send me looks like not drop
4624, or admin , or root ..
The next thing is.. in other posts they write „winlog.eventdata.targetusername“ ..
So thats confusing for me .. also the point with the - symbol.. depends on the page dou look everyone writes different and i get only „missing key here, wrong symbol here.. and so an errors..
I think most of those errors are YAML formatting errors. I think it will help you to validate the YAML with a linter (linked above) to get valid YAML before testing in beats.
Dashes are array syntax in YAML see the array section here.
In my guess above, the and can have a '-' and it's still valid yaml, it's just a 1 element array. The "- not" and "- equals.event_data.event_id" are elements of the "and", in the doc . The "- or" is a complex conditional also with 2 elements.
YAML "equals.event_data.event_id: 4624" is the same as
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.