Left idea of filebeat to send logs and working with logstash-forwarder. It's working. Thanks steffens for help.
Hold on. As you moved to logstash-forwarded, now you changed architecture. Does this mean you're still having elasticsearch running in developer/testing mode? Does this mean logstash (also running in the JVM) running on the same host as Elasticsearch?
The bootstrap checks in Elasticsearch check some common system parameters, to guarantee the service running stable. By working around these checks you might end up with an unstable system you should not use in production. Plus, you're stealing additional resources from Elasticsearch by having yet another process running on the host.
filebeat is originally a fork from logstash-forwarder. It also contains a many bug-fixes. Filebeat can also send to logstash. logstash-forwarder is not maintained or supported anymore. Using logstash-forwarded is not adviced.
Elasticsearch, kibana and logstash are configured in same server , only filebeat i was using to send logs from different server. so for now i have just replaced filebeat with logstash-forwarder and logs are forwarding. But it is sending logs for single instance only while i have configured it to send for multiple instances.
I agree it is not recommended but still filebeat was not able to send logs to server, also same configuration exists in logstash-forwarder through which it was working smoothly without any issue
You used filebeat to send to elasticsearch, right? You can configure filebeat to send to logstash, just as logstash-forwarder does.
Yes steffens, I have already tried to send logs to logstash from filebeat as well, Again i was getting connection-refused error.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.