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 Elastic Stack
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
ntopng Visual Monitoring with Alyvix Elastic Stack IT Operations (Command Orchestrator) Asset Management Service Level Management Cyber Threat Intelligence - SATAYO 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

Elastic APM

Elastic APM Architecture

The key component of Elastic APM is the APM Server, which receives performance data from applications, converts the data into Elasticsearch documents and saves these documents in Elasticsearch.

Applications can send performance data to the APM Server, hosted in the Elastic Agent, via the APM Agents. Some NetEye applications, like Tornado, can already send performance data to the APM Server, while other applications need first to be integrated with the APM Agents.

APM Configuration

The APM functionality is already configured to work out-of-the-box in NetEye installations if all the listed requirements are satisfied. The APM Server is exposed through Nginx using the certificate and key located at /neteye/shared/nginx/conf/certs/apm-server-external.crt.pem and /neteye/shared/nginx/conf/certs/private/apm-server-external.key.

The certificate and key are automatically generated upon NetEye first installation procedure, however it is recommended to install a new trusted certificate as soon as possible.

Warning

Please take note that in order to allow the correct communication between Elastic Agents and the APM Server, the full chain of certificates should be included in the certificate file.

Moreover, the cryptographic settings applied to the SSL connections replicate the settings applied at a system level, which may be changed as described in the official RHEL documentation.

Since APM Server is running as an Elastic Agent integration, this procedure can be followed in order to customize the APM Server configuration as part of the Elastic Agent configuration settings.

Collecting APM Data

In order to collect APM Data, the following two components are required:

  • An APM Agent, that will measure APM data and traces from a specific target. If additional APM Agents are required, the official Elastic guide about APM Agents can be followed.

  • An APM Server, in charge of collecting the APM Data from the related Agents.

The APM Server installation varies depending on the target tenant from which APM data are collected. The following sections will explain the configuration of the two main scenarios of collecting APM data:

From the Master Tenant

By default, NetEye comes with a preconfigured APM Server running in the Operatives nodes and collecting NetEye Master related APM data. The default implementation works out-of-the-box without the need for any additional configuration, assigning the collected data to the master namespace.

Then, to collect APM data from the Master Tenant using additional APM Agents, simply configure the APM Agent on your target application and set as output the FQDN of your NetEye Master.

Please also notice that the NetEye APM Server integration by default requires API key authentication from the agents. To create and set the API key in your APM agent you can refer to Create an API key in the APM app.

From other Tenants

In order to collect APM data from other tenants, a NetEye Satellite is required. Since NetEye currently does not officially support this scenario, you can follow the guidelines listed in the section dedicated to the Elastic Agent Configuration on Satellites in order to collect APM data from a specific tenant. The linked guide will explain how to configure an Elastic Agent, installed on the NetEye Satellite, on which an APM Server integration can be added in order to fulfill this requirement.

To configure a secure connection for the APM data transmission, the creation of an API key for the APM Agent authentication is strongly suggested. You can configure a dedicated API Key through the user interface of Kibana.

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