User Guide Functional Overview Requirements Architecture System Installation NetEye Additional Components Installation Setup The neteye Command Director NetEye Self Monitoring Tornado Business Service Monitoring IT Operation Analytics - Telemetry Geo Maps NagVis Audit Log Shutdown Manager Reporting ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO NetEye.Cloud Strategy Monitoring SOC System Administrator SOC Attacker Centric Cyber Threat Intelligence - SATAYO NetEye Update & Upgrade Backup and Restore How To NetEye Extension Packs Troubleshooting Security Policy Glossary
module icon NetEye Extension Packs
Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.48
NetEye Update & Upgrade Backup and Restore How To NetEye Extension Packs Troubleshooting Security Policy Glossary Introduction to NetEye Monitoring Business Service Monitoring IT Operation Analytics Visualization Network Visibility Log Management & Security Orchestrated Datacenter Shutdown Application Performance Monitoring User Experience Service Management Service Level Management & Reporting Requirements for a Node Cluster Requirements and Best Practices NetEye Satellite Requirements TCP and UDP Ports Requirements Additional Software Installation Introduction Single Node Cluster NetEye Master Master-Satellite Architecture Underlying Operating System Acquiring NetEye ISO Image Installing ISO Image Single Nodes and Satellites Cluster Nodes Configuration of Tenants Satellite Nodes Only Nodes behind a Proxy Additional NetEye Components Satellites Nodes only Verify if a module is running correctly Accessing the New Module Cluster Satellite Security Backup and Restore Identity and Access Management External Identity Providers Configure federated LDAP/AD Emergency Reset of Keycloak Configuration Advanced Configuration Roles Single Page Application in NetEye Module Permissions and Single Sign On Within NetEye Importing User Federation Groups inside another Group Importing OIDC IdP Groups inside another Group Resources Tuning Advanced Topics Basic Concepts & Usage Advanced Topics Monitoring Environment Templates Monitored Objects Import Monitored Objects Data Fields Deployment Icinga 2 Agents Configuration Baskets Dashboard Monitoring Status Icinga2 Features VMD Permissions Notifications Jobs API Configuring Icinga Monitoring Retention Policy NetEye Self Monitoring Concepts Collecting Events Add a Filter Node WHERE Conditions Iterating over Event fields Retrieving Payload of an Event Extract Variables Create a Rule Tornado Actions Test your Configuration Export and Import Configuration Example Under the hood Development Retry Strategy Configuration Thread Pool Configuration API Reference Configure a new Business Process Create your first Business Process Node Importing Processes Operators The ITOA Module Configuring User Permissions Telegraf Metrics in NetEye Telegraf Configuration Telegraf on Monitored Hosts Visualizing Dashboards Customizing Grafana The NetEye Geo Map Visualizer Map Viewer Configuring Geo Maps NagVis Audit Log Overview Shutdown Manager user Shutdown Manager GUI Shutdown Commands Advanced Topics Overview User Role Management Cube Use Cases ntopng and NetEye Integration Permissions Retention Advanced Topics Overview User Roles Nodes RDP Client Building Tools Editor: Interface Overview Editor: Script Building Editor: Managing Scripts Designer: Interface Overview Designer: Interface Options Designer: Component Tree Selector: Interface Overview Test Case Management Dashboard Use Cases Overview Architecture Authorization Kibana Elasticsearch Cluster Elasticsearch Configuration Replicas on a Single Node Elasticsearch Performance tuning Overview Enabling El Proxy Sending custom logs to El Proxy Configuration files Commands Elasticsearch Templates and Retentions El Proxy DLQ Blockchain Verification Handling Blockchain Corruptions El Proxy Metrics El Proxy Security El Proxy REST Endpoints Agents Logstash Rsyslog Elastic APM Elastic RUM Elastic XDR Overview Authorization in the Command Orchestrator Module Configuring CLI Commands Executing Commands Overview Permissions Installation Single Tenancy Multitenancy Communication through a Satellite Asset collection methods Display asset information in monitoring host page Overview Customers Availability Event Adjustment Outages Resource Advanced Topics Introduction The Intelligence We Produce Mitre Attack Coverage Getting Started Settings SATAYO Items Intelligence Requirements Managed Service Request Form FAQ Changelog SATAYO Community NetEye.Cloud as a SaaS solution Accessing NetEye.Cloud Monitoring with NetEye.Cloud Monitoring Environment Business Service Monitoring VMD SOC System Administrator (AdS) Access to NetEye and Elastic Elastic Dashboards Elastic Discover Elastic Alerts Elastic Rules Introduction to SOC Attacker Centric Service Description NetEye SIEM About SATAYO Threat Intelligence and Security Operations How SATAYO works MITRE ATT&CK Coverage SATAYO Findings SaaS & Managed Mode Before you start Update Procedure Single Node Upgrade from 4.47 to 4.48 Cluster Upgrade from 4.47 to 4.48 Satellite Upgrade from 4.47 to 4.48 DPO machine Upgrade from 4.47 to 4.48 Create a mirror of the RPM repository Sprint Releases Feature Troubleshooting Backup and Restore Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration NetEye Cluster on Microsoft Azure NetEye Cluster on AWS Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.48 Setup Configure swappiness Restarting Stopped Services Enable stack traces in web UI How to access standard logs Director does not deploy when services assigned to a host have the same name How to enable/disable debug logging Activate Debug Logging for Tornado Modules/Services do not start Sync Rule fails when trying to recreate Icinga object How to disable InfluxDB query logging Managing an Elasticsearch Cluster with a Full Disk Some logs are not indexed in Elasticsearch Elasticsearch is not functioning properly Reporting: Error when opening a report Debugging Logstash file input filter Bugfix Policy Reporting Vulnerabilities Glossary

Upgrade to NetEye 4.48

With NetEye 4.48 IDO will be officially removed from your NetEye without further ado.

This obviously has some impact on NetEye Extension Packs as well: nep-common and nep-monitoring-core make use of Icinga IDO in different ways, so if you have them installed on your NetEye you should do some cleanup before actually upgrading the system to version 4.48.

Do I have to do something before upgrading?

If you’re reading this, you’ll most likely have to. To be really sure, you have to check if NEP is installed on your NetEye and if you’re using either nep-common or nep-monitoring-core. You can use nep-setup list to see the list of installed NEPs: If the command exists and one or both NEPs are reported in the output, you will in fact have a few things to do.

How to fix nep-common

Note

This is not blocking for the upgrade procedure, you can fix it after the upgrade.

NEP nep-common provides a Grafana data source that can be used by dashboards to get data from the Icinga IDO Database. This data source is stored in Main Org., is of type mysql and is named mysql-icinga. This data source poses no harm to anything, but after upgrading NetEye to 4.48, the underlying database will no longer be updated. So all dashboards using this data source will stop displaying updated data.

You’ll have to take corrective actions after the Upgrade:

  • Upgrade NEP to the latest release of NetEye 4.48; this will provide a new Grafana data source that allows access to the IcingaDB DB (its name is icingadb-mysql)

  • Update all dashboards to use this new data source; remember that the DB schema is completely different, so you’ll also have to update all SQL statements

  • Drop the data source icinga-mysql

This procedure cannot be automated, but you can take advantage of some AI tools to get some help in translating the SQL queries to the new schema.

How to fix nep-monitoring-core

Warning

If not done, neteye upgrade will not be allowed to run.

NEP nep-monitoring-core actually monitors the status of the IDO connection. This configuration is no longer present on NEP for NetEye 4.48, but it’s still used on NEP for NetEye 4.47. Again removal cannot be managed automatically, so you need to remove these items by yourself.

You have to:

  1. Remove the Service Object that monitors IDO status

  2. Remove the Service Template that monitors IDO status

  3. Optionally, remove the Data Fields and Data Lists related to IDO Settings

  4. Make sure to not update nep-monitoring-core before installing the latest version of NEP for NetEye 4.48

Everything has to be done in the NetEye Web UI, so make sure you are logged in with Administrative Privileges.

Remove the Service Object that monitors IDO status

  1. Go to Director and look for the Service Set nx-ss-neteye-icinga-instance-master-state

  2. Go to the Services tab and look for the Service Icinga IDO Performance

  3. Open the service, then delete it

Remove the Service Template that monitors IDO status

  1. Go to Director and look for Service Template nx-st-agent-icinga-ido-performance

  2. Ensure that this Service Template is not in use

    • If it is in use, follow the references and delete all services using it

  3. Open the Service Template, then delete it

Further remaining steps

Now, you can check the integrity of your configuration by committing it with a Deploy. If everything is all right, Deploy should succeed. Now, you can proceed with the upgrade procedure. Make sure to run all Prerequisite Checks to ensure the safety of the whole procedure.

After the Upgrade is completed, as usual, update NEP RPM and then use nep-setup to update all required NEPs.

Blog Online Demo Training
Contact Us
© 2026, Würth IT Italy s.r.l.
VAT ID 01054690217
Privacy Cookies