SIEM – Log Management JVM Configurations We fixed some bugs related to the Elastic JVM configurations, that was duplicating log files in the default directory. The JVM configurations are now up to date and the organization of configuration files has been improved. El Proxy We fixed a bug in El Proxy related to the retry…
Read MoreEl Proxy We fixed a bug in El Proxy related to the retry strategy for sending signed logs to Elasticsearch. Previously, after a document has been rejected from the Elasticsearch ingest pipeline, all non-signed logs were deleted during the retry phase including the mandatory “timestamp” field. Our solution now ensures that all mandatory fields remain…
Read MoreGLPI logging sensitive data We fixed some bugs related to the GLPI where sensitive data were incorrectly logged during log-in and log-out procedures. Updated packages We updated the following packages:
Read MoreRPM Mirror We fixed some bugs related to the NetEye rpmmirror: Updated packages We updated the following packages: Post installation steps After installing the neteye-pulp3-mirror package you should re-run the setup of the rpmmirror ( neteye rpmmirror setup ) to make the bugfixes effective.
Read MoreRPM Mirror We fixed some bugs related to the NetEye rpmmirror: Module Audit Log We also fixed another bug in the audit log module that did not allow correct display in environments with many logs. Updated packages We updated the following packages: Post installation steps After installing the neteye-pulp3-mirror package you should re-run the setup…
Read MoreWe fixed a few bugs in Tornado: Updated packages We updated the following packages:
Read MoreWe fixed a bug in the Logrotate configuration for GLPI that prevented the logs to be compressed and archived. Updated packages 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 MoreSynopsis Important: geomap security update Type/Severity Security Advisory: High Topic An update for the package geomap is now available for NetEye 4. NetEye Product Security has rated this update as having a security impact of High. Common Vulnerability Scoring System (CVSS) base scores provide additional guidance about a vulnerability and give a detailed severity rating….
Read MoreResolved an issue in the NetEye Alyvix module where the dashboard’s loading state would persist indefinitely if no nodes were configured. Furthermore we fixed a bug where Monitoring Objects could not be created over the live-creation if its name contained the percentage symbol Updated packages We updated the following packages:
Read MoreImportant: GLPI Security Update Type/Severity Security Advisory: High Topic An update for the package glpi is now available for NetEye 4. NetEye Product Security has rated this update as having a security impact of High. Common Vulnerability Scoring System (CVSS) base scores provide additional guidance about a vulnerability, and give a detailed severity rating. Description…
Read MoreWe resolved a bug in the NetEye PDF exporting module that causes the reporting scheduler to stop working. Updated packages We updated the following packages:
Read MoreWe resolved a bug in the NetEye Satellite installation and update procedures that previously resulted in an error when the Elastic Agent package was manually installed on the Satellite. Updated packages We updated the following packages:
Read MoreWe fixed a bug in the Elasticsearch installation and update procedures for which customizations of the Elasticsearch node name, if performed, were not taken into account by the built-in procedures and would lead to a failure. Updated packages We updated the following packages:
Read More