We fixed a bug that caused the tenant drop down, in the NetEye Alyvix integration, to not display the full list of tenants in case of users who are not administrator of NetEye but have Full Module Access on the Alyvix module. We updated the following packages:
Read MoreWe 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 of Alyvix Service. Furthermore, we fixed an issue in the update procedure which was not…
Read MoreWe fixed a bug in the NetEye Alyvix module for which, in case of the superadmin, the Test Cases failing were shown duplicated in the Dashboard. Furthermore, we fixed an issue in the upgrade procedure that was causing some packages to skip their update during the upgrade procedure. We updated the following packages:
Read MoreWe fixed a bug in the NetEye IDOReports module related to its installation process and in particular with an update of its database. We updated the following packages:
Read MoreWe fixed a bug in the NetEye IDOReports module related to its installation process and in particular with an update of its database. We updated the following packages:
Read MoreWe fixed a bug in the NetEye Alyvix module where an error was thrown when the super-admin would create a Test Case in a Tenant associated with a Time Period present in a different Tenant. We updated the following packages:
Read MoreBetween the 4th and 7th of June this year, Bolzano had the opportunity to host XP 2024, the 25th edition of the premier international conference on Agile software development. The scenario was NOI Techpark and, as Würth Phoenix, we were there and had the chance to participate in the conference with two talks about SecDevOps…
Read MoreWe fixed a bug in the Elasticsearch installation and update procedures for which customizations of the Elasticsearch node name, if performed, were not taken into account by the built-in procedures and would lead to a failure. Updated packages We updated the following packages:
Read MoreWe fixed a bug in the El Proxy DPO configuration for which the verification logs were never cleaned up. With the fix, it is now possible to specify, for each blockchain, a limit for the accumulated size for the logs. By default, the value is set to 1GB. Updated packages We updated the following packages:…
Read MoreWe fixed the following issues in the integration between NetEye and Alyvix. Test Case file selection dropdown We fixed an issue in the Test Cases view for which, when switching between the Test Cases of different nodes, the wrong Test Case file name was shown in the relative dropdown menu. Hidden Nodes session workflow status…
Read MoreWe fixed the following issues in the integration between NetEye and Alyvix. Test Case file selection dropdown We fixed an issue in the Test Cases view for which, when switching between the Test Cases of different nodes, the wrong Test Case file name was shown in the relative dropdown menu. Hidden Nodes session workflow status…
Read MoreWe fixed the following issues in the integration between NetEye and Alyvix. Test Case file selection dropdown We fixed an issue in the Test Cases view for which, when switching between the Test Cases of different nodes, the wrong Test Case file name was shown in the relative dropdown menu. Hidden Nodes session workflow status…
Read MoreIn 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 More
You weren’t expecting a part three of this series, right? Well honestly, me neither. But after working together with you on the POC where we firstly crawled the NetEye Guide and applied ELSER to the resulting documents, and then we exploited its semantic search capabilities in the NetEye Guide search, we asked ourselves, what if…
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 More