Bug Fixes for NetEye 4.32
In 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 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 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.30 we updated the following packages:
Read MoreWe fixed a bug in El Proxy that caused the verification result sent to the Monitoring to be filled with logs and difficult to read. Now a simplified report with only important information is sent by El Proxy to the Monitoring. Updated packages For NetEye 4.31 we updated the following packages: To correctly apply the…
Read MoreWe fixed a bug in the Alyvix IcingaWeb2 module for which a missing requirement could led to an error if a certain package was not installed. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed a bug in the Alyvix IcingaWeb2 module for which a missing requirement could led to an error if a certain package was not installed. Updated packages For NetEye 4.31 we updated the following packages:
Read MoreWe fixed the following 4 bugs related to upgrade procedure to ELK 8. Firstly, we fixed an issue with a script used to set the correct number of replicas for single-node installations, which was throwing an error in case a certain system index, already having the correct setting, was being affected by the procedure. Moreover,…
Read MoreWe fixed a bug in a check pre-upgrade related to the upgrade to Elastic Stack 8 which did not identify correctly the cases in which a single critical system index needs migration. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed the following 4 bugs related to El Proxy. The first bug was that there was large RAM consumption during the verification in case the verified blockchain contained a large number of corruptions. With the fix, the list of found corruptions, which caused the problem, is now exported in a .ndjson.gz file, for easier…
Read More