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 intact during the retry strategy. Additionally, we enhanced the logging of El Proxy errors in the DLQ logs for easier debugging.
Upgrade Manager
We fixed a bug in the upgrade procedure related to fencing. The procedure now, whenever an update of pacemaker or corosync is present, ensures fencing is disabled to prevent possible issues when nodes are put in standby.
Furthermore, we fixed an issue related with the check of missing updates, which may have given an error in case a change of RedHat Release.
Updated packages
We updated the following packages:
elastic-blockchain-proxy, elastic-blockchain-proxy-autosetup, elastic-blockchain-proxy-configurator to version 1.2.5-1
Fix upgrade 4.45 migration error We solved an issue that affected the upgrade to NetEye 4.45. The issue occurred during the migration of the monitoring role permissions to Icinga DB, due to the order in which packages were updated. List Read More
Fix NetEye web UI exception We solved an issue that affected the NetEye web UI, when the SLM feature module is not installed, causing an exception to be thrown. List of updated packages To solve the issues mentioned above, the Read More
Fix for memory corruption in icinga2 We solved an issue that affected icinga2. If the cleanup of the http sessions in the execute-script endpoint ran during a request, the re-balance in the internal datastructure would corrupt the requests memory, resulting Read More
Fix El Proxy Kibana plugin activity We solved an issue that affected the El Proxy Kibana plugin which, in case many Fleet agent policies were associated with an integration, caused a large number of index template updates, possibly resulting in Read More
Fix support for Alyvix Nodes with older versions We solved an issue that could cause Test Cases to be not shown in the Alyvix UI if the Alyvix Nodes supported only API version 3 (i.e. Alyvix Service version <= 2.5). Read More
