SIEM – 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 MoreWe have implemented a verification step in the neteye install, update, and upgrade processes to verify Kibana’s connectivity to the fleet integration endpoint when the NetEye instance operates behind a proxy without direct Internet access. Additionally, we have revised our User Guide to provide detailed instructions on configuring this aspect. Moreover, the rolling restart process…
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 MoreCore Neteye install, update, upgrade procedures individual service logs weren’t saved in the correct format We resolved a small issue where logs from parallel install or configurator playbooks were wrongly manipulated resulting in a different format from what they were supposed to be saved. SIEM – Log Management Elastic Stack missing systemd configuration files We…
Read MoreWe fixed a procmail misconfiguration that was occurring after the upgrade. 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 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 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 under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read MoreWe fixed a bug that under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read MoreWe fixed a bug that under certain conditions caused notifications of a state change to be lost during the execution of a deployment and at the same time Tornado would perform an action to set a check result. We updated the following packages:
Read More