13. 01. 2022
Alessandro Valentini
Bug Fixes, Log-SIEM, NetEye
Bugfixes for NetEye 4.21, 4.20, 4.19: Elasticsearch License Renewal
The current Elasticsearch license bundled with NetEye will expire this January 31st. To continue enjoy all the SIEM functionalities you must update to the new license. An automatic update has been released for the most recent NetEye version. Older NetEye releases however, can be updated manually.
In the case the health-check light/01004_elastic_license_check.sh is preventing you to update your Neteye Installation you can run the following command: neteye update --skip-tags check_health. All other health-check must be successful to ensure a safe update.
For NetEye 4.21 we updated the following packages:
- elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, apm-server, apm-server-autosetup, apm-server-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config to version 7.15.0_neteye3.35.6-1
For NetEye 4.20 we updated the following packages:
- elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, apm-server, apm-server-autosetup, apm-server-neteye-config, kibana, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config to version 7.12.1_neteye3.32.9-1
For NetEye 4.19 we updated the following packages:
- elasticsearch, elasticsearch-autosetup, elasticsearch-neteye-config, filebeat, filebeat-autosetup, filebeat-neteye-config, kibana-autosetup, kibana-neteye-config, logstash, logstash-autosetup, logstash-neteye-config to version 7.12.1_neteye3.30.4-1
For NetEye 4.18 and older you can update your license manually via Kibana: Stack Management \ License Management \ Update License and upload the new license.
Another option is to update the license via command line:
- Download the new license in a file, for example:
/neteye/local/elasticsearch/license/elastic-license-2022.json - Load the new license:
/usr/share/neteye/elasticsearch/scripts/es_curl.sh -X PUT https://elasticsearch.neteyelocal:9200/_license -d @/neteye/local/elasticsearch/license/elastic-license-2022.json -H "Content-Type: application/json" - Verify correct license installation by checking expiry_date:
/usr/share/neteye/elasticsearch/scripts/es_curl.sh https://elasticsearch.neteyelocal:9200/_license | jq
To obtain the new license please contact our Service and Support Team.
Latest posts by Alessandro Valentini
See All
Related Content
Tags: Bug Fixes, NetEye Updates
04. 03. 2026
Bug Fixes, NetEye
Important: Lampo security update Type/Severity NetEye Product Security has rated this update as having a medium security impact. Topic An update for the lampod packages is now available for NetEye 4. Security Fix for NetEye 4.46 1.1.3-1 Summary The vulnerability is about sensitive
Read More
04. 03. 2026
Bug Fixes, NetEye
Important: Elastic Stack security update Type/Severity NetEye Product Security has rated this update as having a Medium security impact. Topic An update for the Kibana package is now available for NetEye 4. Security Fix for NetEye 4.46 9.2.6_neteye3.90.8-1 CVEs CVE-2026-26934CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVE-2026-26935CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVE-2026-26936CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H CVE-2026-26937CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Read More
02. 03. 2026
Bug Fixes, NetEye
Error during generation of SLA reports We have fixed a bug that was causing an error during the generation of SLA reports. List of updated packages To solve the issue mentioned above, the following packages have been updated for NetEye
Read More
19. 02. 2026
Bug Fixes, NetEye
Fix NagVis navigation using IcingaDB Web URLs When clicking on a host or service from a NagVis map, you were redirected to the legacy Monitoring module. The links have been updated to correctly point to the IcingaDB Web module. List
Read More
11. 02. 2026
Bug Fixes, NetEye
Fixing Misplaced Plugin Output in Icinga Web Interface When plugin output contained HTML content (like links), it was incorrectly displayed near the service name instead of in the Plugin Output section. The plugin output section now correctly renders all content.
Read More