I tried to setup a disconnected architecture between production and monitoring, as I have non-connectivity between my production servers and my ELK stack (local network).
I planed to work as follow:
filebeat process relevant logs and save it (output plugin) as a file
However, I failed to configure logstatsh correctly:
using the file input plugin (tail mode) makes the process fine BUT beat logs are seen as simple logs and thus logstash puts the filebeat logs as "message" instead of considering them as it would with the beat input plugin.
Yes, you need to define the JSON codec as your file input in logstash OR use the JSON filter in your logstash configuration and target the message field as the source
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.