Hello everyone! As you may remember, a topic I like to discuss a lot on this blog is the Proof of Concept (POC) about how we could enhance search within our online NetEye User Guide. Well, we’re happy to share with you how we’ve further developed the POC, specifically the process outlined in the first…
Read MoreSIEM – Log Management We have resolved an issue in the update and upgrade process for the Elastic Stack. Previously, if the Enrollment Token for our Elastic Agent was manually revoked, the procedure could encounter an error when attempting to regenerate it. Alyvix We fixed a bug affecting cloned Alyvix dashboards for performance graphs. Previously,…
Read MoreWe have resolved an issue that could have led to the failure of the installation process during initial setups. This problem arose from a temporary absence of an entry in the /etc/hosts file, which in turn hindered the startup of nginx. We updated the following packages:
Read MoreHey everyone! We played around a bit last time with our radar data to build a model that we could train outside Elasticsearch, loading it through Eland and then applying it using an ingest pipeline. But since our data is in the form of vectors, could we actually exploit Elasticsearch vector database functionality and perform…
Read MoreWe resolved a bug in the nginx configuration for our clickhouse integration. This fix guarantees that queries will no longer be directed to the voting-only node in cluster environments, preventing potential errors. We updated the following packages:
Read MoreWe fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade. This enhancement guarantees proper pcs resource management throughout this phase. We updated the following packages:
Read MoreWe fixed a bug in the neteye update procedure. In particular, this now handles properly the update of pacemaker and corosync, as done already by the neteye upgrade, to ensure a correct handling of the resources during this phase. We updated the following packages:
Read MoreHey everyone! As you may remember, we took a look in the past at how it’s possible to use a model (trained directly in Elasticsearch) to perform some real time classification by using an ingest pipeline. But… what if we wanted to use our own externally trained model? Well the good news is that, under…
Read MoreA bug in the NetEye Alyvix integration has been resolved. This bug was associated with certain secure attributes that were absent from the cookie responsible for storing the Alyvix JWT token. We updated the following packages:
Read MoreWe 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 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 More