I am trying the elastic cloud for the first time using 7.12 stack. I would like to send zeek logs to my elastic cloud deployment and the default method recommended is to use filebeats. I would like to stream the logs using kafka and apply zeek specific data transformations to make it ECS compliant using logstash. I would appreciate it if you can let me know what I need to do to achieve this.
The filebeat zeek module is already ecs compliant. Some of the processing is done locally and the rest is done via the ingest pipelines for the module.
Thanks for the response. Yes, I am aware of that. My requirement is to be able to replicate that pipeline using a combination of kafka and logstash without using filebeats. I have been able to configure logstash to pull zeek logs from kafka, but I don;t know how to make it ECS compliant. Because of this, I don't see data populated in the inbuilt zeek dashboards on kibana. Appreciate any more info on how to make it happen.
Yes I was just going to post the link to github. I wouldn't bother doing too much in Logstash except pulling from Kafka and perhaps doing the minor changes that filebeat is doing prior to pushing to the respective ingest pipeline. I would use those native pipelines so you don't have to reinvent the wheel.
I am a newbie to the ELK ecosystem. Just to understand what filebeats does, I followed the instructions provided by Elastic. What I see is that filebeats has created an ingest pipeline in the cloud with a whole bunch of transformations. what are the minor changes it does locally that I need to replicate in logstash? Would appreciate any pointers.
Also, if I understand correctly, what you are suggesting is to configure logstash to reuse the ingest pipeline created by filebeats. Is there any document that helps me understand how to do this. Your replies have been very informative and useful.
Take a look at ingest-convert. I believe that tool is designed to convert the pipeline.yaml from a Filebeat module into a logstash configuration. It has limitations, and if I remember correctly it has bugs.
This blog describes its introduction. Back then filebeat modules used JSON, not YAML. Someone from Elastic opened an issue saying the converter should be removed, but it has not happened yet.
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.