We 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 and indexes that were in a yellow state within single-node instances, an issue arising from an unmet shard replica policy. For more information, please consult our User Guide.
We updated the following packages:
icingaweb2-module-neteyeto version1.156.1-1elastic-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-licenseto version8.15.2_neteye3.66.8-1
Mattia Codato
Software Developer - IT System & Service Management Solutions at Würth Phoenix
Author
Latest posts by Mattia Codato
11. 02. 2025
Development, Events, NetEye
Podman Quadlet: Simplifying Container Management with systemd
18. 12. 2024
Automation, Development, DevOps
GitOps: Push vs Pull? Choosing the Right Approach for Production Deployments