We have implemented a verification step in the neteye install, update, and upgrade processes to verify Kibana’s connectivity to the fleet integration endpoint when the NetEye instance operates behind a proxy without direct Internet access. Additionally, we have revised our User Guide to provide detailed instructions on configuring this aspect.
Moreover, the rolling restart process of Elasticsearch nodes was improved to ensure each Elasticsearch node joins the cluster before moving to the restart of the next node, hence complying with the official guidelines of Elastic.
We updated the following packages:
elastic-agent, elastic-agent-autosetup, elastic-agent-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, logstash, logstash-neteye-config, logstash-autosetup, logstash-neteye-config-autosetup, kibana, kibana-autosetup, kibana-neteye-config, elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack-license to version 8.15.2_neteye3.66.3-1
We fixed a bug which was causing the Elasticsearch upgrade procedure to fail in a race condition. In particular, after the upgrade of the Elasticsearch RPM and before the restart of the service, the running Elasticsearch service could possibly fail Read More
Hello everyone! Today, I'd like to briefly discuss an improvement to the update and upgrade procedures that we've started to adopt with NetEye 4.39! What we wanted to improve One aspect that made quite an impact was that whenever the Read More
Hello everyone! Today, I’d like to share an exciting improvement we’ve made to the installation and upgrade procedures in NetEye, introducing a faster and more efficient parallel architecture! Why Modernize the Installation and Upgrade Processes? At Würth Phoenix, we strive Read More
After the previous release of an Icinga2 bugfix for a race-condition during the shutdown, some issues with the connection to satellite nodes emerged. This bugfix release is a cleanup we worked on in cooperation with Icinga2 to address those issues. Read More
We fixed an issue related to the upgrade path from 4.37 to 4.38, where the upgrade could have blocked at the secure install phase due to the missing retrieval of upgrade checkpoints. We updated the following packages: neteye-upgrade-manager to version Read More