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 Phoenix. 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 Phoenix. 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 Tornado filter WHERE condition We fixed an issue in Tornado UI in which the WHERE condition of a filter were not being displayed correctly for some conditions not created through the API. List of updated packages To solve the Read More
Fix Tornado filter WHERE condition We fixed an issue in Tornado UI that did not allow deleting the WHERE condition of a filter in some conditions. List of updated packages To solve the issue, the following packages have been updated Read More
Important: Chromium security update Type/Severity NetEye Product Security has rated this update as having a security impact of Low Security Fix for NetEye 4.41 An update for the following packages is now available for NetEye 4: chromium to version 133.0.6943.141-1 Read More
Fix Tornado Filters names and descriptions editing We fixed an issue in Tornado related to the editing of new Filters names and descriptions, which would have resulted in an error. List of updated packages To solve the issue, the following Read More
Fix Elasticsearch read-only indices check We fixed an issue related to the 01002_elastic_indices_read_only_check.sh light health check, which checks if some indices are present in Elasticsearch in a read-only state. The check may have wrongly recognized as in read-only also some Read More