We renewed the Elastic Enterprise license, which was originally scheduled to expire on February 28, 2025. The new expiration date is now February 28, 2026.
If your NetEye version is older than 4.39 and you wish to utilize the Elastic Enterprise license, you will need to upgrade to at least NetEye 4.39. Alternatively, you can reach out to NetEye Support for assistance.
Fix of an unnecessary Elasticsearch restart
We’ve fixed an issue during the Elasticsearch update and upgrade procedures which, in case of the availability of a kernel update, would have caused an unnecessary restart of the service even if Elasticsearch itself was not updated.
List of updated packages
To solve the aforementioned issues, the following packages have been updated:
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.17.0_neteye3.72.11-1
Fix Kibana sysconfig migration We resolved a bug that occurred during the migration of Kibana to a multi-instance setup. The issue prevented the proper copying of custom configurations from /neteye/shared/kibana/conf/sysconfig/kibana-user-customization. As a result, these customizations were missing from the Kibana instances Read More
Fix monitoring object creation during deployment We fixed a bug that caused a monitoring object to be lost if it was created while a Diretor deployment was in progress. List of updated packages To solve the issues mentioned above, the Read More
Fix for Tornado Webhook collector We have fixed an issue where large incoming requests to the Webhook Collector could cause the system to become unresponsive over time. List of updated packages To solve the aforementioned issues, the following packages have Read More
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" Read More
Fix for Previously, database updates would fail if the GLPI DRBD resource was active on a node other than the primary, due to an inability to locate the necessary database configuration within the DRBD-managed volume. This fix ensures that GLPI Read More
