We’ve fixed an issue where the neteye satellite config send command would stop if no SSH connection was available or enabled for a satellite. Now, the command will skip those satellites, allowing configurations to continue for reachable ones, while manual configuration transfer can be addressed later. This enhances efficiency and streamlines your deployment process. We…
Read MoreWe fixed a bug in Icingaweb2 module Geomap that prevented users from declustering pins, even when fully zoomed in. Now, pins that are clustered together can be separated and viewed clearly by clicking the cluster icon at max zoom level, enhancing the overall map usability. We updated the following packages:
Read MoreWe fixed a bug in the host and service search configuration with custom fields that generated an error if only one of the two fields was filled in. SIEM – Log Management We have resolved a bug that caused one of our custom Elasticsearch procedures to fail. This script enabled users to modify index templates…
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 MoreAssetmanagement – GLPI We fixed a bug for the GLPI single sign on, where every login through the SSO would write two line of updates for the user permissions to the user object history. SIEM – Log Management We resolved a bug in Elasticsearch that occurred when a mount (for example, an NFS share) was…
Read MoreMonitoring We have resolved an issue where icinga2 would fail to write state changes to the IDO and execute notifications during shutdown. We updated the following packages:
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 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 More