Bug Fixes for NetEye 4.19
We fixed a bug that caused the yum groups “neteye” and “neteye-tools” to not being marked as installed on some NetEye instances. For NetEye 4.19 we updated the following packages: neteye-setup to version 1.75.1-1
Read More
Blog Entries
El Proxy – Error Handling
Beginning with NetEye 4.17, the NetEye Log Management module has been able to rely on the new Real Time Log Signing architecture, which aims to overcome some weaknesses in the previous Log Management implementation based on rsyslog. One of the core components of the new architecture is the new El Proxy daemon, whose tasks are…
Read MoreBug Fixes for NetEye 4.17
We fixed a bug in the Log Manager for which it was not possible to verify Elasticsearch blockchains containing more than 10,000 documents. For NetEye 4.17 we updated the following packages: elastic-blockchain-proxy and elastic-blockchain-proxy-autosetup to version 0.8.1-1
Read MoreLog Management – Real Time Log Signing
Meeting the highest security standards is an absolute priority in NetEye. For this reason, in the continuous process of improving security in NetEye 4, we brought an important architectural improvement in the Log Manager module in the NetEye 4.17 release. The new architecture takes the name of Real Time Log Signing and its main focus…
Read MoreBug Fixes for NetEye 4.16
We set the retention of the Icinga2 downtime history to infinite, so that downtimes are never deleted from the Icinga2 IDO. For NetEye 4.16 we updated the following packages: icinga2 to version 2.11.6_neteye1.22.5-1
Read MoreBug Fixes for NetEye 4.15
We fixed a problem for which dashboards were not rendered correctly and dashboards columns were truncated on some browsers if the content was too long. For NetEye 4.15 we updated: icingaweb2, icingaweb2-vendor-zf1, icingaweb2-vendor-JShrink, icingacli, icingaweb2-vendor-lessphp, icingaweb2-vendor-HTMLPurifier, php-Icinga, icingaweb2-autosetup, icingaweb2-vendor-dompdf, icingaweb2-common, icingaweb2-vendor-Parsedown to version 2.8.2_neteye1.80.3-1
Read MoreThe New Command Orchestrator Feature Module
One of the features introduced in the 4.15 NetEye release is the Command Orchestrator. The aim of this newly introduced feature module is to allow limited-access NetEye users to execute predefined commands on hosts, without needing full access to the targeted device. Within the Command Orchestrator, the NetEye administrator defines which commands can be executed,…
Read MoreVMD – Tornado Integration
We introduced an interesting new feature into NetEye starting in version 4.13 that permits integrating vSphereDB with Tornado. By being able to process vSphereDB Events and Alarms with Tornado rules and actions, you can for example use vSphereDB to dynamically monitor Virtual Machines and Hosts. Architecture Finding a way to send Alarms and Events stored…
Read MoreBug Fixes for NetEye 4.14
We fixed a bug for which notifications of new available NetEye releases were appearing ahead of time in the NetEye GUI. For NetEye 4.14 we updated: icingaweb2-module-update and icingaweb2-module-update-autosetup to version 1.9.1-1
Read MoreBug Fixes for NetEye 4.15
We fixed a bug for which notifications of new available NetEye releases were appearing ahead of time in the NetEye GUI. For NetEye 4.15 we updated: icingaweb2-module-update and icingaweb2-module-update-autosetup to version 1.9.1-1
Read MoreBug Fixes for NetEye 4.14
We fixed a bug related to the SLM module, where a user not having access to the Monitoring module could generate a report containing hosts and services from the Monitoring For NetEye 4.14 we updated: icingaweb2-module-neteye to version 1.73.2-1
Read MoreBug Fixes for NetEye 4.14
We fixed a bug for which the Reporting scheduling service icinga-reporting.service was unable to send report after facing errors in the connection with MariaDB. For NetEye 4.14 we updated: icingaweb2-module-reporting and icingaweb2-module-reporting-autosetup package to version 0.9.1_neteye0.5.3-2
Read MoreNetEye Communication over NATS
In a previous post we talked about how in NetEye we migrated all the Tornado communications from direct TCP to NATS. Since then, we’ve extensively and successfully adopted NATS as a communication channel for many of the components present in NetEye. As often happens when approaching new technologies, the initial straightforward approach did not turn…
Read MoreBug Fixes for NetEye 4.13
We fixed an issue in the Tornado GUI, for which it was possible to create and deploy a Filter with a space in the name from the GUI, which would cause Tornado to fail to restart. For NetEye 4.13 we updated: tornado, tornado-autosetup, tornado-common, tornado-neteye-config, tornado-rsyslog-collector-logmanager to version 0.39.8-1 icingaweb2-module-tornado, icingaweb2-module-tornado-autosetup to version 0.22.3-1
Read MoreBug Fixes for NetEye 4.13
We fixed an issue in the neteye_secure_install, causing the configuration of a wrong password for the pkcs12 bundle of the NATS client used by the Tornado Icinga2 Collector. For NetEye 4.13 we updated: tornado, tornado-autosetup, tornado-common, tornado-neteye-config, tornado-rsyslog-collector-logmanager to version 0.39.7-2
Read More