We fixed the following 4 bugs related to upgrade procedure to ELK 8.
Firstly, we fixed an issue with a script used to set the correct number of replicas for single-node installations, which was throwing an error in case a certain system index, already having the correct setting, was being affected by the procedure.
Moreover, we fixed issues related to waiting for the Elasticsearch cluster status to be back to green, which would have failed in case the first node was being upgraded and a new primary shard was being allocated on it, with the related replica not being able to be allocated on any node having a lower Elasticsearch version.
Furthermore, we ensured that Elasticsearch is not being restarted unnecessarily during updates.
Lastly, we fixed an issue in the script used to generate the additional Beats templates for El Proxy, which was failing for Winlogbeat, after ELK 8, due to the configuration of a mapping for an undeclared analyzer.
Updated packages
For NetEye 4.31 we updated the following packages:
apm-server,apm-server-autosetup,apm-server-neteye-config,elastic-agent,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.8.2_neteye3.49.2-1
Davide Sbetti
Hi! I'm Davide and I'm a Software Developer with the R&D Team in the "IT System & Service Management Solutions" group here at Würth IT Italy. IT has been a passion for me ever since I was a child, and so the direction of my studies was...never in any doubt! Lately, my interests have focused in particular on data science techniques and the training of machine learning models.
Author
Latest posts by Davide Sbetti
30. 03. 2026
APM, Log Management, Log-SIEM, NetEye
Sending OTel Data to Elasticsearch: Tenant Segregation through OAuth