Elastic 8.16, which comes with NetEye 4.39, made Elastic Universal Profiling generally available for self-hosted installations. This means that NetEye SIEM installations will now be able to take advantage of the continuous profiling solution by Elastic. In this blogpost we’ll explain what you can achieve with continuous profiling how you can configure it in NetEye….
Read MoreWe fixed a bug which was causing the Elasticsearch upgrade procedure to fail in a race condition. In particular, after the upgrade of the Elasticsearch RPM and before the restart of the service, the running Elasticsearch service could possibly fail loading some libraries, hence breaking the upgrade procedure. We updated the following packages:
Read MoreWelcome to version 4.39 of our NetEye v4 Unified Monitoring Platform. This stunning drone panoramic photo captures the frozen beauty of Lake Carezza, nestled in Northern Italy’s winter landscape. The snowcapped mountain pass frames the serene lake, while the dense green pine forest adds depth to the scene. Cars winding along the road hint at…
Read MoreWe resolved a bug in the Elastic Agent which was causing the Elastic Agent to temporarily losing its state (namely the state.enc file) during updates. We updated the following packages:
Read MoreWe updated the Elastic Stack to version 8.15.2, which fixes some known issues present with versions 8.15.1 (the version previously used in NetEye for Elasticsearch, Kibana, Logstash and APM) and 8.15.0 (the version previously used in NetEye by Elastic Agents and Beats). For more details please refer to the official Elastic release notes. We updated…
Read MoreWe fixed a bug in nginx that was causing NetEye upgrades from version 4.36 to version 4.37 to fail with an error. We updated the following packages:
Read MoreWe resolved an issue in the neteye update and neteye upgrade commands where the process would halt if the Elasticsearch cluster took longer than 30 seconds to respond to API requests. We updated the following packages:
Read MoreAs the NetEye R&D team, we sometimes need to develop features in NetEye that require a lot of work to finish implementing. To handle the development of these features, we’re always trying to divide the work into smaller, more manageable pieces so that we can see any progress and avoid the typical pitfalls of the…
Read MoreWe fixed a bug that caused the neteye install command to not wait for resources to restart after the procedure completed. We updated the following packages:
Read MoreWe fixed a bug in the NetEye Alyvix module which caused some errors to be shown to administrators of Tenants which did not have access to some tenant-shared Alyvix Nodes. We updated the following packages:
Read MoreWe fixed a bug in the neteye update and neteye upgrade commands that was causing the NetEye default Logstash plugins to be installed from the Internet on passive cluster nodes. In particular this was causing the commands to fail in case these nodes did not have access to rubygems.org. Updated packages We updated the following…
Read MoreWe fixed a bug in the neteye update and neteye upgrade commands that was causing the NetEye default Logstash plugins to be installed from the Internet on passive cluster nodes. In particular this was causing the commands to fail in case these nodes did not have access to rubygems.org. Updated packages We updated the following…
Read MoreWe fixed a bug in the SLM module that was causing an error when trying to create a Resource Contract in case any SLM Customer had an associated role with no permissions on the analytics module. Updated packages We updated the following packages:
Read MoreWe fixed a bug in the NetEye Update and Upgrade procedures that was causing the procedure itself to stop with a timeout error in environments where the Elasticsearch APIs and/or Kibana APIs are particularly slow to respond. Updated packages We updated the following packages:
Read MoreWe fixed a bug in the NetEye Update and Upgrade procedures that was causing the procedure itself to stop with a timeout error in environments where the Elasticsearch APIs and/or Kibana APIs are particularly slow to respond. Updated packages We updated the following packages:
Read More