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 Update & Upgrade 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.31
NetEye Update & Upgrade 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 Single Node Cluster Node Satellites Nodes only Verify if a module is running correctly Accessing the New Module Cluster Satellite Security Identity and Access Management External Identity Providers Configure federated LDAP/AD Emergency Reset of Keycloak Configuration Advanced Configuration Authorization 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 VMD Permissions Notifications Jobs API Configuring Icinga Monitoring Retention Policy NetEye Self Monitoring 3b 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 Performance Graph The NetEye Geo Map Visualizer Map Viewer Configuring Geo Maps NagVis 3b Audit Log 3b 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 Test Cases Dashboard Use Cases Overview Architecture Authorization Elasticsearch 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 Elastic APM Elastic RUM Log Manager - Deprecated 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 Getting Started SATAYO Items Settings Managed Service Mitre Attack Coverage Changelog Before you start Update Procedure Single Node Upgrade from 4.41 to 4.42 Cluster Upgrade from 4.41 to 4.42 Satellite Upgrade from 4.41 to 4.42 DPO machine Upgrade from 4.41 to 4.42 Create a mirror of the RPM repository Sprint Releases Feature Troubleshooting Tornado Networking Service Management - Incident Response IT Operation Analytics - Telemetry Identity Provider (IdP) Configuration Introduction to NEP Getting Started with NEPs Online Resources Obtaining NEP Insights Available Packages Advanced Topics Upgrade to NetEye 4.31 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 3b

Obtaining NEP

As described at Online Resources, NetEye Extension Packs can be obtained through two main channels:

  • Wuerth Phoenix’s RPM Repository neteye-contrib

  • Wuerth Phoenix’s Anonymous BitBucket Repository

Wuerth Phoenix’s RPM Repository neteye-contrib is the official channel: through it, all the Offical Stable Versions of NEP are made available via RPM package. Those RPMs will have the sole duty of making all necessary contents available for installation, allowing the End User to import only the strictly required objects. Each version of NetEye will come with its set of compatible NEPs packed inside the proper RPM. This channel is freely accessible by all Wuerth Phoenix’s Customers.

Wuerth Phoenix’s Anonymous BitBucket Repository is the development channel: through it, it is possible to get the contents of all stable versions of NEP as well as the current development release. This makes possible for everyone to get NEP freely. Also, if anyone desires it, everyone can contribute to the development of the project. Even if NEPs have NetEye as their target platform, they can be used on any system that equips the same underlying software a NetEye system.

Please note that just downloading and installing these files will not automatically deploy all NEP’s contents into NetEye: it is up to the End User to perform the import of one or more Packages by manually performing the Package Setup. This allows for a system to have the smallest footprint, enabling an easier management of the NEP-related Objects. Therefore, each NEP comes with a setup procedure that must be run by the end user before all objects become usable. Additionally, the setup procedure can be re-executed to restore all the objects to their original state.

Enable access to external repos

NetEye Extension Packs requires access to external resources to complete the setup. Without these resources, the install/update procedure for some NEPs might fail. Therefore, you must ensure your NetEye Servers have access to these websites:

  • repo.wuerth-phoenix.com

  • linux.dell.com

  • grafana.com

  • yum.centreon.com

  • yum-gpg.centreon.com

  • bitbucket.org

In case your NetEye has the SIEM Module, ensure all your NteEye Servers have access also to these websites:

Only for NetEye SIEM:

  • epr.elastic.co

  • geoip.elastic.co

  • storage.googleapis.com

Installing from RPM Repository

Installing NetEye Extension Packs from Wuerth Phoenix’s RPM Repository is fairly simple: just install the NEP RPM provided by the repository on the required NetEye Systems:

  • If you have a NetEye Single-Node deployment, install the RPM on the Single-Node NetEye

  • If you have a NetEye Cluster deployment, install the RPM on all Cluster Nodes

To install the NEP RPM, just run this line of code in a shell with root privileges:

yum -y --enablerepo=neteye-contrib install neteye-nep

After this procedure, all NEP’s related contents will be available at /usr/share/neteye/nep directory, that will become your NEP Content’s Source.

Installing from Anonymous BitBucket Repository

Warning

Use of BitBucket Repository is strongly discouraged for production environment. Production environment should be managed only via RPM from our official repositories. While contents provided by the Master Branch are still complete and stable, they should not be considered as a stable release. BitBucket Repo should be used only for testing purposes only or for preparing your own contribution to NEP Project.

Installing NetEye Extension Packs from Wuerth Phoenix’s RPM Repository is just like cloning a GitHub Repository: just clone the NEP Repository on the required NetEye Systems:

  • If you have a NetEye Single-Node deployment, clone it on the Single-Node NetEye

  • If you have a NetEye Cluster deployment, clone it on all Cluster Nodes

Before cloning, find a suitable path to where clone NEP Repository contents. For the sake of simplicity, it is possible to assume /usr/share/neteye/ as a suitable path. To clone the NEP Repository from BitBucket, just run these commands in a shell with root privileges:

mkdir -p /usr/share/neteye/nep
git clone https://bitbucket.org/siwuerthphoenix/nep.git /usr/share/neteye/nep
mkdir -p /neteye/shared/nep/data/packages
ln -s /usr/share/neteye/nep/setup/nep-setup /usr/sbin/nep-setup

After this procedure, all NEP’s related contents will be available at /usr/share/neteye/nep directory, that will become your NEP Content’s Source.

Blog Online Demo Training
Contact Us
© 2025, Wuerth Phoenix S.r.l.
VAT ID 01054690217
Privacy Cookies