In NetEye, we use Ansible to automate many different tasks in an idempotent way, ranging from the first installation of the system to updates and upgrades. Ansible already comes with many built-in useful modules to manage files, perform HTTPS requests and much more. Furthermore, various Ansible Collections have been developed by the community to address…
Read MoreFix rpmnew handling in Keycloak upgrade procedure We fixed an issue in Keycloak’s update procedure to improve the handling of an rpnew generated during the update. First installation for SIEM clusters without voting-only node We fixed an issue related with the first installation of clusters with the SIEM feature module which do not have a…
Read MoreFix Tornado Filters names and descriptions editing We fixed an issue in Tornado related to the editing of new Filters names and descriptions, which would have resulted in an error. List of updated packages To solve the issue, the following packages have been updated
Read MoreFix Elasticsearch read-only indices check We fixed an issue related to the 01002_elastic_indices_read_only_check.sh light health check, which checks if some indices are present in Elasticsearch in a read-only state. The check may have wrongly recognized as in read-only also some indices where the read_only_allow_delete or read_only properties were set to false. List of updated packages…
Read MoreIf you’re a NetEye regular, you may have downloaded the NetEye ISO at least once in your life. And if you did, you probably discovered that you had a bit of free time before the download was completed and the ISO was ready to be used. Why’s that? Because until a couple of weeks ago,…
Read MoreFix of an unnecessary Elasticsearch restart We’ve fixed an issue during the Elasticsearch update and upgrade procedures which, in case of the availability of a kernel update, would have caused an unnecessary restart of the service even if Elasticsearch itself was not updated. List of updated packages To solve the aforementioned issues, the following packages…
Read MoreWe fixed a bug which was causing Elastic Agents to disconnect themselves at regular intervals from Fleet. We updated the following packages:
Read More
Hello everyone! Today, I’d like to briefly discuss an improvement to the update and upgrade procedures that we’ve started to adopt with NetEye 4.39! What we wanted to improve One aspect that made quite an impact was that whenever the update or upgrade procedure stopped, even for legitimate reasons such as rpmnew or rpmsave files,…
Read MoreWe fixed an issue related to the upgrade path from 4.37 to 4.38, where the upgrade could have blocked at the secure install phase due to the missing retrieval of upgrade checkpoints. We updated the following packages:
Read MoreWe’ve fixed an issue related to the RPM Mirror where the sync would have failed after the one performed during the neteye rpmmirror setup command, due to a dependency change. We updated the following packages: Note: to apply the bug fix, run the neteye rpmmirror setup after updating the NetEye Master
Read MoreHello 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 More