In this bugfix, we fixed a problem for which, on single node installation, setting the correct replica number for all Elasticsearch indices could lead to an error related to system indices and the permissions needed to change their settings. Updated packages We updated to version 8.10.2_neteye3.57.4-1 the following packages:
Read MoreIn this bug fix we fixed a problem that could have occurred during the upgrade phase to NetEye 4.33. More specifically, we expanded compatibility with older versions of some Elastic Agent integrations when loading them into the preconfigured NetEye policies. Updated packages We updated to version 8.10.2_neteye3.57.3-1 the following packages:
Read MoreWe have released a fix for a problem in the Tornado UI, that didn’t allow to pass multiple arguments to the script action in a rule. Updated packages We updated to version 2.4.1-1 the following packages:
Read MoreWe 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…
Read MoreWe have released a fix for a problem related to RedHat subscriptions. Updated packages We updated the following packages:
Read MoreWe fixed a bug where the deployment of the Icinga director would not clean up old stages, filling up the file system over multiple deploys. Updated packages For NetEye 4.32 we updated the following packages:
Read MoreWe added an automatic procedure that correctly upgrades the DB schema for Icinga2. Updated packages For NetEye 4.32 we updated the following packages:
Read MoreIn the Tornado GUI, we fixed the behavior of the “Group Match IDX” input of the regex extractor. Updated packages For NetEye 4.32 we updated the following packages:
Read MoreWe have fixed the following bugs in the Tornado GUI: Updated packages For NetEye 4.32 we updated the following packages:
Read MoreWe fixed a bug in the El Proxy for which in case of NetEye node failure (e.g. loss of power), the El Proxy service may lose the content of the file containing the blockchain key. In this case El Proxy would fail to sign new logs upon restart. Updated packages For NetEye 4.32 we updated…
Read MoreWe fixed a bug in the NetEye in which El Proxy would use an empty string as previous hash when, upon restart, it could not find the last signed log in Elasticsearch, resulting in a blockchain corruption. Updated packages For NetEye 4.31 we updated the following packages:
Read MoreWe updated GLPI to 10.0.10. This new version introduces a lot of security fixes. The update is strongly recommended. Furthermore we fixed a bug for which the InfluxDB secure install script could have failed to run some queries due to a numeric database name. Updated packages For NetEye 4.31 we updated the following packages:
Read MoreWe fixed a bug in the NetEye upgrade that regards the update of the Elastic Stack packages in cluster environments. The bug occurred in case of encountered errors and resulted in the procedure finishing the steps instead of instantly aborting the operations. Now is possible to update the nodes of the NetEye cluster without hesitations….
Read MoreWe fixed a bug for which the generic El Proxy composable index templates in Elasticsearch, so those not matching a particular Beat, did not include the ECS mappings and this could have led to wrongly indexed data. After the fix, the templates include by default the ECS 8.0.0 mappings. Updated packages For NetEye 4.31 we…
Read MoreWe fixed a bug in the NetEye Upgrade Manager that caused the procedure to possibly use the wrong repository metadata when understanding which NetEye *-configurator packages need to be installed to support the upgrade and update procedures. Updated packages For NetEye 4.31 we updated the following packages:
Read More