Open biolds opened 1 year ago
This looks like you may be using ECS which is still a work in progress? Are you using Filebeat with the Suricata module? If so, can you let me know which version of Filebeat and Elastic you are using?
I'm forwarding data with the file module of filebeat (with Logstash and ES at version 7.17). I didn't do anything special or tried to enable ECS, though i see an ecs.version
key in my events.
Does your config look something like https://github.com/jasonish/evebox/wiki/Example-Filebeat-to-Logstash-Configuration?
There are many ways to get the data into Elastic that all result in slightly different schemas, so I need as much detail as possible please.
Yes, the conf is similar to this one. It seems filebeat is actually adding the ecs field, as I can see when taking the suricata json as file input, and use a file output, the ecs field is present. I think the field appeared when I switched from filebeat-oss to filebeat-free version.
Ok. This is a setup I haven't tested recently. Even though ecs
might be present, Suricata events are only converted to ecs
format when using the Filebeat Suricata module. So make sure you are not providing the --ecs
flag to EveBox unless you are using the filebeat Suricata module.
Short of that, this will likely have to wait until I can test this similar setup.
I'm not passing the --ecs
flag when running evebox, and don't have option in the yaml file to specify it.
I'm running Evebox 0.16 (Debian package install), and have noticed an error is triggered when when viewing an event. To trigger it, I go to the "Events" top menu entry, then click on an event (from my testings, it seems to trigger on all events):
It seems like it's expecting an
event
key in the suricata events, are these mandatory ?The full error stack: