Welcome to version 4.33 of our NetEye v4 Unified Monitoring Solution.
With this release, NetEye welcomes Winter with a spectacular view of St. Jakob Church. It is located in Ortisei (or St. Ulrich in German), a small village in Val Gardena (Gröden in German) perfect to stroll about in, discover new things, and fall in love with the winter season. When the first snowflakes fall it looks magical: sparkling white mountains, Christmas Markets, and thousands of lights …
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 the 8.9 version.
To discover the changes and improvements that RHEL 8.9 introduces, please refer to the official release notes.
We are glad to announce a significant enhancement in the Cluster Installation process.
With NetEye 4.33, we have streamlined the installation procedure, making it remarkably more efficient and, even more important, easier for our users, all thanks to our integration with Ansible.
You can learn more on our updated NetEye User Guide.
In order to give the possibility to grant access to the report list to all those people who should only consult the reports, we updated the Icingaweb2 Module Reporting, which brings with it a new set of permissions.
It is now possible to configure a NetEye role with read-only permission. A user belonging to this kind of role will be able to see the report list, open one of them, and download a copy of it.
Tornado’s capabilities have increased with the ability to handle events that arrive via SMS.
The SMS collector, introduced in this release, allows the power of Tornado to be leveraged to set the status of Icinga 2 services, for example, based on SMS received.
The EventHandler is officially deprecated and will be completely removed with NetEye 4.34. We strongly suggest migrating to the new Tornado SMS collector as soon as possible. For more info about the migration take a look at the NetEye User Guide.
With this release, we added the possibility to format any timestamp received by Tornado to a human-readable format.
The new modifier accepts a timezone, recognizes automatically whether the timestamp is in seconds, milli-, micro-, or nanoseconds and formats it into the standard RFC3339 representation (for example
In our ongoing efforts to improve the user experience of using Tornado, this release focuses also on improving the expansion of processing tree nodes.
The visualization of the event flow has also been improved by making it more understandable how and what rules interact with the test event during their configuration.
As a part of the Tornado Guide improvement process, a new section with the primary configuration was added. Before you start section contains general guidelines on the steps required to be taken prior to creating configuration with a Processing Tree, e.g. tuning your infrastructure, or configuring multitenancy roles.
Additionally, the Tornado Configuration in the NetEye Guide was reorganized in order to provide a clearer understanding of the Processing Tree functionality and the sequence of actions to be taken when creating or editing a Tornado configuration.
To allow SIEM users to get the latest features and bugfixes brought by Elastic, NetEye 4.33 upgrades the component of the Elastic Stack from version
8.8.2 to version
8.10.2. Please note that the new Elastic version also brings important security fixes.
For the full set of improvements and bug fixes, please refer instead to the official release notes of Elasticsearch, Kibana, Logstash, and Beats.
Until NetEye 4.32, the Elastic Agent was available in preview in the extras repos and its configuration and management were completely delegated to customers.
However, NetEye 4.33 brings the Elastic Agent inside the official Elastic Stack available out-of-the-box in the product. In particular, this is configured to collect logs from all NetEye nodes and to expose the Fleet functionality, useful also to managing external Elastic Agents from a central platform.
For more information about how the Elastic Agent is configured in NetEye and how to handle the upgrade for existing installations, please have a look at our Elastic Agent configuration User Guide section and at our upgrade guide.
With the integration of the Elastic Agent, NetEye 4.33 dismisses the legacy standalone APM Server, exploiting the new integration with the Elastic Agent.
Moreover, the APM integration comes pre-configured also to collect APM data from external sources, to fully exploit its potential. To discover more about this topic and how to migrate from the legacy APM Server, please consult our upgrade guide and APM configuration User Guide.