Nagios Support Forum

While I see the advantage of a delayed start, so that you can ensure one logstash is running. It raises a question in my mind though - how is your load balancer determining which service to forward packets to? Say the load balancer sends data in a round robin fashion to 1,2,3 - 1 is starting, while...

...and restart the appropriate services across the cluster in an orderly fashion. An important clarification. However this orderly fashion still leaves the cluster unresponsive for a few minutes. It really should wait for the first logstash start responding again before it restarts the next node. I...

To clarify. If I click the "Save" button in "Administration / Configuration Editor / Global Configuration". Will that write down the new configuration without restarting logstash on all nodes? If so then I will have to restart logstash on one node at a time to prevent data loss.

If I do save. Doesn't that distribute the changes on all nodes? If so then I will have to restart each logstash manually one node at a time. We have udp syslog going to this server and they are fire and forget. Some systems can't do anything else

Does Nagios Log Server support any method to manage elasticsearch.yml in a cluster?
We are looking into change discovery.zen.minimum_master_nodes for instance.

Our concern is that future upgrades might clobber these changes if we do it directly in the files.

When applying changes to our global configuration in our cluster I have noticed that all logstash instances will become unavailable. As we have a load balancer in front of the cluster this is really bad. We will loose logs. What is the supported way to apply config changes without restarting all log...