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 fixed a bug regarding missing systemd configuration files during the execution of some autosetups used for the correct configuration of Elastic Stack.
DPO verification containers were not restarted after a system reboot if running on Podman
We resolved a bug where the DPO blockchain verification containers with a restart policy Always were not successfully restarted after a host reboot if running on Podman.
Links inside Fleet Integrations redirected to a 404 page
We fixed an issue where clicking links inside some Fleet Integration dashboards redirected you to a nonexistent page instead of the actual resource.
APM – User Experience
Visual Monitoring with Alyvix
Transactions wrong status when thresholds were used
We fixed a bug in the Test Case reports view, where the transactions timeline could have shown the wrong status for single transactions in case a threshold (critical or warning) was applied.
Test Case enabling right after creation
Furthermore, we fixed an issue for which in the Test Case view it was not possible to enable a new Test Case in a session right after its creation without first refreshing the page. The operation is now possible, allowing a more seamless integration between these two actions.
We updated the following packages:
elastic-agent, elastic-agent-autosetup, elastic-agent-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, logstash, logstash-neteye-config, logstash-autosetup, logstash-neteye-config-autosetup, kibana, kibana-autosetup, kibana-neteye-config, elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack-license to version 8.14.3_neteye3.65.3-1
elastic-blockchain-proxy to version 1.3.1-1
icingaweb2-module-alyvix, icingaweb2-module-alyvix-autosetup, icingaweb2-module-alyvix-configurator to version 0.55.4-1
We have resolved an issue that prevented Elastic Agents from successfully connecting to the Fleet Server when their requests were excessively large. Additionally, we addressed a bug in the neteye update and neteye upgrade processes, which was incorrectly initiating a Read More
We fixed a bug which was causing Elastic Agents to disconnect themselves at regular intervals from Fleet. We updated the following packages: elastic-agent, elastic-agent-autosetup, elastic-agent-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, logstash, logstash-neteye-config, logstash-autosetup, logstash-neteye-config-autosetup, kibana, kibana-autosetup, kibana-neteye-config, elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, elasticsearch-xpack-license to Read More
We 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 Read More
Hello everyone! Today, I'd like to briefly discuss an improvement to the update and upgrade procedures that we've started to adopt with NetEye 4.39! What we wanted to improve One aspect that made quite an impact was that whenever the Read More
Hello everyone! Today, I’d like to share an exciting improvement we’ve made to the installation and upgrade procedures in NetEye, introducing a faster and more efficient parallel architecture! Why Modernize the Installation and Upgrade Processes? At Würth Phoenix, we strive Read More