Welcome to version 4.5 of our NetEye v4 Unified Monitoring Solution. Following version 4.4, the new and updated features in this version focus on bug fixes, updates to CentOS and core components, and improvements to Log Manager, Lampo, Tornado and Safed.
Product: NetEye Release Number: 4.5 Release Date: March 31, 2019 Release Type: Minor Previous Release: 4.4
System Requirements: NetEye 4.4
These release notes for NetEye 4.5 describe new features and improvements compared to version 4.4. The complete change log, which includes all fixed issues, is available in the updated NetEye documentation (see the section “Starting your Upgrade” below).
Improvements
Log Manager / Safed Deployment
We have enhanced the deployment mechanism whereby configurations are sent from the Log Manager to individual, remote Safed agents. Now if you change a Safed Agent configuration, the intelligent deployment tool will notify you to update only those hosts affected by this change; you will no longer need to deploy to all hosts. Unlike in the past, hosts will need to be redeployed in Director before they will appear in the Safed Deployment panel.
Log Manager Translations
All text descriptions in the Log Manager GUI (labels, fields, menu items, etc.) have been translated from English into both Italian and German. Beginning with this release, all new modules added to NetEye 4 will include localization support for these three languages from the start.
Log Manager Integration with Audit Log
Configuration changes to the Log Manager are now recorded in the Audit Log, visible at System > Audit Log.
Tornado
Tornado has been improved so that it can now collect monitoring events from Icinga 2 and trigger actions using the Icinga 2 API (e.g. setting passive check results). Other changes include:
Rules: Tornado now treats Rules in alphanumeric order based on their file name, and thus the priority field has been deprecated.
Rule Sets: Rules are now organized as independent Rule Sets, and can be processed in parallel. This allows for better organization, and faster processing with complex setups.
Sockets: Internal and external communication in Tornado has shifted from Unix-specific domain sockets to more generalized TCP sockets.
Configuration verification: A new command allows you to check the correctness of a given configuration, without restarting Tornado.
Lampo
Now users will be notified if an error occurs while using Lampo.
Standalone Updates to the User Guide
The user guide has been updated to include the following new content:
A full description of Configuration Baskets, which were introduced in the latest version of IcingaWeb2 Director (User Guide > Director > Importing Director Configurations).
A reference guide for using NetEye’s new Search Guard tools and backup scripts that wrap many basic parameters, such as security certificates (User Guide > Log Manager > Search Guard Helper Tools).
A complete walk-through of how to configure and use the Moxa NPort 6150 in conjunction with a modem for sending SMS notifications (User Guide > Initial Configuration > SMS Gateway Connection).
To receive the upgrade, ensure that NetEye is up to date by running this command in a shell:
yum update --enablerepo=neteye
Then click on the purple notification box next to the System menu item and follow the linked documentation.
NetEye 3.17 Release Notes
Welcome to the 3.17 version of our NetEye 3 Unified Monitoring Solution, updating the availability report and monitoring check plugins.
Product: NetEye Release Number: 3.17 Release Date: March 31, 2019 Release Type: Minor Previous Release: 3.16
System Requirements: NetEye 3.16
These release notes for NetEye 3.17 describe the improvements to version 3.16, and provide information on how to upgrade. The complete change log, which includes all fixed issues, is available in the “What’s New” section of the updated NetEye documentation.
Improvements
NetEye Thruk
A link to the Info Page has been added to the Availability Report for hosts and services.
NetEye Plugins
The latest versions of check_inventory and check_mssql_health are now included.
How to Upgrade
Upgrading from NetEye 3.16 to NetEye 3.17 can be performed locally by following the documentation already provided in NetEye 3.16. This upgrade procedure will still be possible for all future NetEye 3 minor releases. The base requirement is a NetEye 3.16 installation based on CentOS 6.
Step 1:
Update the NetEye 3.16 documentation package with the following command:
Execute the upgrade procedure as described in the just-updated documentation section “What’s New in NetEye?” at the link under “NetEye Upgraded Documentation”.
Hi folks!
I began loving computer since 1994, it was still the time of windows 3.1. Immediately I learned starting DOS games from the command promt, and while typing some white text on black background I felt like some hackish dude in a hollywoodian movie.
Later during the studies at the university, I discovered the magic world of opensource, and it was love at first sight. Finally I got rid of BSOD's =)
I love everything that is connected to some network, especially in a security perspective.
My motto is:
"With motivation, nothing is impossibile. It only requires more time."
Author
Thomas Forrer
Hi folks!
I began loving computer since 1994, it was still the time of windows 3.1. Immediately I learned starting DOS games from the command promt, and while typing some white text on black background I felt like some hackish dude in a hollywoodian movie.
Later during the studies at the university, I discovered the magic world of opensource, and it was love at first sight. Finally I got rid of BSOD's =)
I love everything that is connected to some network, especially in a security perspective.
My motto is:
"With motivation, nothing is impossibile. It only requires more time."
When using Kibana in environments that require a proxy to reach external services, you might encounter issues with unrecognized SSL certificates. Specifically, if the proxy is exposed with its own certificate and acts as an SSL terminator, requests made by Read More
In a previous post we went through the configuration of Elastic Universal Profiling in NetEye, seeing how we can profile applications written in programming languages that do not compile to native code (for example Python, PHP, Perl, etc.) But what Read More
Elastic 8.16, which comes with NetEye 4.39, made Elastic Universal Profiling generally available for self-hosted installations. This means that NetEye SIEM installations will now be able to take advantage of the continuous profiling solution by Elastic. In this blog post Read More
In the first part of this series, we explored how Jira Service Management (JSM) helps streamline Incident Management, aligning with ITIL v4 best practices. Incident Management aims to restore normal service operation as quickly as possible after a disruption, ensuring Read More
Hello everyone! Today, I'd like to briefly discuss an improvement to the update and upgrade procedures that we've started to adopt with NetEye 4.39! What we wanted to improve One aspect that made quite an impact was that whenever the Read More