Once upon a time (in fact it was just a month ago, but it sounds more dramatic this way) I had the opportunity to attend a webinar about Vector Search, Generative AI, and modern NLP by the Elastic Team. One of the topics that was touched on during the webinar was ELSER , Elastic’s new…
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.30 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.31 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 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 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 MoreWe 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 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 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 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 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 More