Welcome to version 4.28 of our NetEye v4 Unified Monitoring Solution.
In this release, NetEye welcomes winter and the new year with the typical South Tyrolean Apple Strudel.
There are myriad recipes for typical apple strudel and seemingly every family has its own delicious filling. Each cook adds his own special blend of sultanas, nuts, breadcrumbs, sugar, pine nuts “pinoli”, nuts, and spices to the apples. In the family, after being baked, it doesn’t last long because it is taken by storm. After all, what could taste better than a warm strudel accompanied by hot tea?
One of our main goals is to make NetEye 4 as safe as possible, that’s why we are continuously working hard to keep its components up to date. For this purpose, in this release, we updated RHEL to 8.7 version. RHEL 8.7 brings in a new kernel so we also took the opportunity to improve our upgrade/update process by shipping a new
neteye node reboot utility command and consolidating the user guide procedure.
To improve the stability of NetEye, we upgraded the distributed replicated storage system (DRBD) used in high-availability cluster environments from version 9.0 to 9.2.
The complete list of change logs can be found at this link.
To meet the needs of NetEye administrator users, all logins and logouts of each user are now logged. These logs containing the username and other useful information about the user such as roles and permissions can be viewed in the
System > Audit Log page.
We also added a retention policy to the audit logs, that can easily be modified over the GUI.
In order to give a more comprehensive vision of the status of NetEye and avoid potential hidden problems, a new Health Check has been added. It is now possible to monitor the status of NetEye systemd timers running the
neteye health command. The overall status is also visible from the health-check-neteyelocal service, reachable from the NetEye Monitoring module.
To identify the NetEye system globally, a NUUID (NetEye Universal Unique Identifier) will be assigned to each NetEye Node. Red Hat Subscriptions are now bound to the NUUID.
The feature was originally introduced in NetEye 4.27 and is now also available in NetEye versions 4.26, 4.25, and 4.24.
For more information on the registration of NetEye nodes and NUUID, see the official user guide.
For a better understanding of some of the main NetEye concepts and functionality, a number of diagrams were added to the Architecture part of the online User Guide.
Single Node with tenants diagram aims to illustrate the ability of a Single Node to support multitenancy, while proving data transmission to the Master being secured and authenticated.
Tornado pipeline diagram highlights the key phases of processing data by Tornado software, from data gathering by Collectors, and all the way down the processing pipeline, resulting in actions to be executed by the Tornado Engine.
Self Monitoring section has become a part of Monitoring – Detection concepts, in order to provide a complete and consistent image of NetEye’s monitoring capabilities in one place.
In order to recover the logs in case of an Elasticsearch infrastructure incident, which would prevent El Proxy from indexing the signed logs on the blockchains, the
dlq recover command was introduced. The command aims to automatically recover the logs inside the dead letter queue.
NetEye 4.28 allows to perform El Proxy verification in a more seamless way due to introducing new El Proxy container images, available on DockerHub, and the new
neteye dpo setup command. The container images allow the verification to be run on any operating system, while the
neteye dpo setup command enables the secure configuration of an external Linux machine as DPO machine directly from NetEye. Moreover, the command manages the update of the container image after NetEye updates or upgrades.
El Proxy already allowed sending the return code of the verification command to the Tornado Webhook Collector. In order for the NetEye admin to easily analyze the results of the blockchain verification, El Proxy will also send the report of the verification together with the parameters that identify the verified blockchain:
In the new version of the Alyvix module shipped with NetEye 4.28, we revamped the test case run report view to show the list of transactions in a nicely formatted timeline.
Moreover, we also improved the visualization of the performance of a single transaction inside the test case run report. The previously adopted tabular format was transformed into a real performance graph and this allows users to easily analyze the performance of a transaction with respect to the defined thresholds.
Additionally, we added a tooltip with a detailed description of a transaction’s performance metrics.
Nodes page, we added a column to the nodes table to show the Alyvix Service version together with the already present Alyvix Core version.
Additionally, the Alyvix dashboard, which provides summary metrics about the configured Alyvix installation, such as the number of nodes, test cases, and sessions, was introduced as a new NetEye 4.28 feature. Moreover, the Alyvix dashboard provides useful links to the official documentation. The dashboard is available in the main Alyvix menu.
A huge number of new features and bug fixes are included in the new Icingaweb2 module vSphereDB version 1.6. Most notably, vCenter restrictions and filters have been integrated into the UI, a history for the state changes of the monitoring rules and single objects has been added and it provides support for vSphere tags in the UI as well as multiple bug fixes and UI/UX improvements.
Please take a look at the official documentation for the full list of improvements.
This update is currently in beta and can be installed from the neteye-beta repository.