We fixed a bug in a check pre-upgrade related to the upgrade to Elastic Stack 8 for which, in case some critical system indices need to be migrated, the upgrade was prevented. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed a bug that regards Tornado Carbon. It is now possible, in the dedicated regex fields, to be assisted in the error check without incoming in an error message during the deployment phase. In addition, a bug that was causing a host’s availability to exceed 100% in SLA reports has been fixed. Updated packages…
Read MoreWe fixed a bug in NetEye Userguide clarifying the procedure to setup custom certificate on a NetEye Mirror in Change NGINX Certificates section both in NetEye 4.30 and 4.31.
Read MoreWe fixed an issue for which El Proxy, when writing logs to the DLQ due to the impossibility to index logs in Elasticsearch, would not write the original received log but a “reduced version” used in the previous retries. With the released version, the original document is now written in DLQ. Updated packages For NetEye…
Read MoreWe fixed an issue for which El Proxy was taking long to acknowledge multiple corruptions at large iterations. With the newly released version is now possible to use the acknowledge-range command to acknowledge multiple corruptions with a single command. For more information, check out the NetEye User Guide. Updated packages For NetEye 4.31 we updated…
Read MoreWe updated the Elastic Stack to the latest bugfix version 7.17.11. In particular this version fixes a problem in Kibana, which was not properly handling some particular DSL queries. For more information on the fixes provided with this version, please refer to the official Elastic Stack website. In case you have any Elasticsearch plugin installed…
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 that regards the validation of the hostname of a NetEye node. Now is possible to use names starting with upper case characters without any problem. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed a bug that regards the neteye alyvix-node setup command, which was not specifying the version of the Alyvix API to consume, thus leading to an error. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed a bug that regards the neteye upgrade/update process: since there was the risk of failures when the first node of a cluster was already in a standby status, now we implemented an additional check about this possible case. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed an issue where the check of the upgrade prerequisites was failing in case no prerequisites were found. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed several deprecations in the NetEye SIEM module, which allow NetEye installations to be compliant with the directives of Elastic Stack and to be prepared for future upgrade of the Elastic Stack. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed several bugs regarding the NetEye first installation on a cluster. It is now possible to successfully run the neteye_secure_install without worrying about possible problems and interruptions. In addition, we fixed the permissions of some configuration files. Updated packages For NetEye 4.30 we updated the following packages:
Read MoreWe fixed a bug that caused a failed authentication of Alyvix sessions having some special characters in the password, due to an inconsistent encoding. Moreover, we fixed an issue related to the installation procedure of the feature modules packages on satellites, which under some circumstances was not marking the corresponding DNF group as installed. Furthermore,…
Read MoreGeneral Authentication via request-header backend We fixed a bug that did not allow the role to be associated with a user who was part of an LDAP group when the user logged in via the request-header backend. Tornado Tornado Director retry loop We fixed a bug that triggered the Tornado Director in a retry loop…
Read More