Fixes for Elastic Stack
Improved wait for cluster status during updates / upgrades
When restarting the Elasticsearch cluster during the NetEye update / upgrade procedure, is it possible let the restart procedure going even if the cluster has a “yellow” status. The check on the cluster status has been improved to allow at least the “yellow” status if the user specified it.
Resolving Elasticsearch Nodes Attempting to Join a New Cluster
During updates or upgrades, certain conditions may cause some Elasticsearch nodes to attempt to form a new cluster, resulting in nodes restart failures. This issue has been addressed by configuring the cluster.initial_master_nodes setting only during the initial bootstrap of the Elasticsearch cluster. Once the cluster is successfully established, this setting is permanently removed.
Addition of EnvironmentFile Directive in elastic-agent.service file
We have now made it possible to configure environment variables for the elastic-agent.service running on NetEye nodes. You can now configure environment variables by creating an environment file under /neteye/local/elastic-agent/conf/sysconfig/elastic-agent-user-customization.
List of updated packages
To solve the aforementioned issues, the following packages have been updated for NetEye 4.43:
elastic-agent,elastic-agent-autosetup,elastic-agent-neteye-config,elastic-stack-configurator,elasticsearch,elasticsearch-autosetup,elasticsearch-neteye-config,elasticsearch-xpack-license,filebeat,filebeat-autosetup,filebeat-neteye-config,kibana,kibana-autosetup,kibana-neteye-config,logstash,logstash-autosetup,logstash-neteye-config,logstash-neteye-config-autosetupto version8.18.3_neteye3.81.4-1
Emil Fazzi
Software Developer, R&D Team in the "IT System & Service Management Solutions" group at Würth Phoenix.
Author
