Filebeat and Modules when ES Down

Whenever I use modules like syslog or nginx, I can't get filebeat to start, if elasticsearch isn't up and running. I get:

" CRIT Exiting: Error creating ES client: Couldn't connect to any of the configured Elasticsearch host"

Is there a way to force it to start and keep trying to connect, like it would if I wasn't using modules? Or if I had logstash as my output (in which case, I'd only receive a warning). I can't count on the ES server always being up, when every client comes up.

1 Like

This topic was automatically closed after 21 days. New replies are no longer allowed.