I'm new to this discussion webpage but have been using the ELK stack for a fair amount of time now, and this page been a great help for me.
I was recently looking into the full config yml file for Filebeat and didn't see a specific config to shut down the Filebeat service itself, if it can't connect to ES or LS after few tries or if been trying for a long time.
The reason for my question is that we are trying to make certain beats a part of a platform load; and in some networks we may have no connection back to our cluster. Our concern is whether there will be any networking issues/flooding by constantly trying to connect to logstash…etc.
I just would like to know if there is already something to handle such thing or do I need to script something to take care of that. I know there is
filebeat.shutdown_timeout, but not sure if applies to my scenario.
I appreciate your response and thank you in advance.