Good afternoon,
I leave this post because in my ELK 7.6 I get the error you see below when loading the Meerkat Dashboard (the one that comes in the Stack) some idea of where the problem can go.
Thank you very much for the help!
Good afternoon,
I leave this post because in my ELK 7.6 I get the error you see below when loading the Meerkat Dashboard (the one that comes in the Stack) some idea of where the problem can go.
Thank you very much for the help!
Could you give a bit more information? Is this a new installation, did you upgrade? How did you trigger that error?
Good Morning,
First of all I apologize for the lack of information, it is a clean installation of ELK 7.4 that was updated via repository until its current version 7.6, the way to reproduce that error is as follows:
It looks like you may be running filebeat collection without having run ./filebeat setup
. That setup step creates dashboards in Kibana. If you run it now, do you see it working?
./filebeat at Suricata Server or ELK server?
From wherever you are currently running ./filebeat
Sorry but I don't quite understand it ./filebeat in Suricata does nothing to me ...
Okay, the screenshots show that you are using filebeat to send data from Suricata to Elasticsearch. To set up the Kibana dashboards, you need to run the filebeat setup
command on the command line, from the same place filebeat is installed.
The idea was to send logstash with filebeat, but I don't get it to work, I leave you with a capture of the command you mentioned and the main configuration files to see if you see the fault.
/etc/filebeat/modules.d/suricata.yml
/etc/filebeat/filebeat.yml
Thanks for your help!
For testing I have put the lines so that filebeat pulls the data to elasticsearch directly without going through logstash and I get what you see below in the capture, in any case when I launch it to logstash then it processes it to elasticsearch because indexes are created elasticsearch takes movement.
Greetings!
/etc/logstash/logstash.yml
/etc/logstash/conf.d/logstash.conf
/etc/logstash/conf.d/suricata.conf
I can't help you with your filebeat setup, but I can tell you that this is the source of the original problem you asked about. Without running filebeat setup
successfully, you will not see the dashboards that you are expecting.
For filebeat questions, please ask in https://discuss.elastic.co/c/beats/28
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
© 2020. All Rights Reserved - Elasticsearch
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.