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.
We released an update for GLPI that fixes several vulnerabilities. We updated the following packages: glpi, glpi-autosetup and glpi-neteye-config to version 10.0.16_neteye1.15.3-2
We fixed a bug in Icingaweb2 module Tornado UI which prevented the UI from refreshing after a draft configuration was deleted. We updated the following packages: icingaweb2-module-tornado, icingaweb2-module-tornado-autosetup and icingaweb2-module-tornado-configurator to version 2.13.6-1
We fixed a bug in the NetEye Alyvix module related to the Multi Tenancy migration command neteye alyvix-node enable-multitenancy --all, in which we adapted the data sent by the command to the Alyvix node to comply with the latest specification Read More
We fixed a bug in Icingaweb2 module Tornado UI which made part of the testing form unreachable when multi-tenancy was enabled. We updated the following packages: icingaweb2-module-tornado, icingaweb2-module-tornado-autosetup and icingaweb2-module-tornado-configurator to version 2.13.5-1
We fixed a bug in the NetEye Alyvix module which caused some errors to be shown to administrators of Tenants which did not have access to some tenant-shared Alyvix Nodes. We updated the following packages: icingaweb2-module-alyvix and icingaweb2-module-alyvix-autosetup to version Read More