We improved the upgrade and update procedure related to the Elastic Agent, fixing an issue for which external Elastic Agents would disconnect from Fleet if they were connecting through a hostname different from NetEyes’s FQDN.
Moreover, we solve potential problems during the upgrade that would have occurred in case of already present outdated integrations or in case of a large number of policies.
Manual required steps
If you have not already upgraded to NetEye 4.33
You are good to go, the upgrade procedure will take care of all the required steps.
If you have already upgraded to NetEye 4.33
To ensure a clean and compliant environment please apply the following procedure before performing the update:
Access Fleet from Kibana’s menu and remove the previously created policies NetEye Operative Nodes and NetEye Single Purpose Nodes. Please note that if there are Elastic Agents associated to them, these need to be unenrolled. Do not worry, they will be enrolled back automatically by the update procedure! To un-enroll the agents, please apply the following procedure:
Access Fleet from Kibana’s menu
Select all the agents enrolled in one of the previously mentioned policies
Click on Actions -> Unenroll X agents -> Remove agent immediately -> Unenroll
Always from Fleet, access the Settings and remove all NetEye related outputs and Fleet Hosts. Please note that if they are marked as default they cannot be removed, so we advise to create a new item, marking that as default and delete then the one belonging to NetEye.
At this point, it is possible to update the packages, following the standard NetEye Update procedure.
Please note that these steps are required only for this particular update, due to necessary changes in some objects ID, while future updates and upgrades would not be impacted by this in any mean.
Updated packages
For NetEye 4.33 we updated the following packages:
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
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.
Fix contract list option wrongly disabled in SLM reports We fixed a bug affecting the SLM reporting in NetEye 4.45. The issue occurred during the modification of a report, when one of the contracts in the list could not be Read More
Bug Fix We updated the version of GLPI in order to fix some relevant vulnerabilities. List of updated packages The following packages have been updated for NetEye 4.45: glpi, glpi-autosetup, glpi-configurator, glpi-neteye-config to version 10.0.22_neteye1.17.5-1.
Bug Fix in Tornado Module We solved an issue in Tornado's rule configuration where the action_name field in director actions was being cleared after saving and deploying. When users created a rule with a director action and filled in both Read More
Important: Elastic Stack security update Type/Severity NetEye Product Security has rated this update as having a High security impact. Topic An update for the elastic-stack packages (elasticsearch, kibana, filebeat, logstash and elastic-agent) is now available for NetEye 4. Security Fix for NetEye 4.45 Read More
Elastic Enterprise license renewal Previously, the Elastic Enterprise license was scheduled to expire on February 28, 2026.With this update, the Elastic Enterprise license has been renewed and will now expire on December 31, 2026. In the case the health-check light/01004_elastic_license_check.sh is preventing Read More