We 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 of Elasticsearch nodes was improved to ensure each Elasticsearch node joins the cluster before moving to the restart of the next node, hence complying with the official guidelines of Elastic.
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.15.2_neteye3.66.3-1
Software Developer - IT System & Service Management Solutions at Würth Phoenix
Tags: Bug Fixes, NetEye Updates