Removed input in Elastic Agent Fleet System integration
With the release of Elastic Agent Fleet version 2.0.0, the “System” integration has been updated and now removes support for a deprecated log collection input method that relied on httpjson. This input is no longer available in the latest version of the integration.
To address this change, we’ve updated the NetEye Fleet policy definition by removing the httpjson input reference from the System integration template. This fix ensures continued compatibility with the new integration behavior.
However, please be aware that if you’re running a NetEye version 4.40 or previous, the default System integration definition must be updated manually. Failing to do so before an upgrade, if the System integration has been updated to version 2.0, can break the NetEye update or upgrade process.
To prevent this issue, NetEye users with versions prior to 4.41 must manually edit the following configuration files on every NetEye node:
/neteye/local/elastic-agent/conf/fleet/templates/system_neteye_operative_nodes_integration.json.j2
/neteye/local/elastic-agent/conf/fleet/templates/system_neteye_single_purpose_nodes_integration.json.j2
Within those files, remove the section with the label system-httpjson from the System integration definition.
List of updated packages
To solve the aforementioned issues, the following packages have been updated for NetEye 4.41:
elastic-agent,elastic-agent-autosetup,elastic-agent-neteye-config,elastic-stack-configurator,elasticsearch,elasticsearch-autosetup,elasticsearch-neteye-config,elasticsearch-xpack-license,filebeat,filebeat-autosetup,filebeat-neteye-config,kibana,kibana-autosetup,kibana-neteye-config,logstash,logstash-autosetup,logstash-neteye-configto version8.17.3_neteye3.74.5-1elastic-blockchain-proxy,elastic-blockchain-proxy-autosetup,elastic-blockchain-proxy-configurator to version1.8.4-1
Emil Fazzi
Software Developer, R&D Team in the "IT System & Service Management Solutions" group at Würth Phoenix.
Author
