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 Visual Monitoring with Alyvix
Overview User Roles Nodes Test Cases Dashboard Use Cases
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

Overview

Alyvix monitoring system within NetEye is not included in the NetEye Core, and is to be additionally installed as a Feature Module.

In order to start using Alyvix within NetEye, follow the procedure described in Additional NetEye Components.

After the Alyvix Feature Module has been installed, it is possible to configure an Alyvix node in NetEye to be able to monitor and configure it from the NetEye UI in just a few steps that you will find below.

Alyvix Service is available under its own product license. You can find out more on how to obtain Alyvix license in its installation guide.

Alyvix is a synthetic monitoring system based on computer vision which synthesizes real users without being hardwired to application engines.

NetEye integration with Alyvix allows currently the monitoring of Alyvix nodes, with planned support for scheduling test cases, assigning test cases to sessions on different Alyvix machines, and more.

More information about Alyvix is available on the official website and in the official documentation.

Architecture of Alyvix Nodes

This section provides information about the supported Alyvix node types. As explained below, currently NetEye supports four different types of node:

The main differences between them reside in the adopted Tenancy configuration and the way they communicate with the NetEye Master. There are two types of communication involved: HTTPS and NATS. NetEye communicates with the Alyvix Service via API calls through the HTTPS communication channels, while NATS serves as a communication channel to send the performance metrics from the Alyvix nodes to the NetEye Master. The choice of using one rather than the other boils down to your infrastructure and purpose of the node.

Multitenant - Tenant Specific

This node is meant to be used in Multitenant environments where the Alyvix node is completely dedicated to and managed by a specific tenant. In this case, the NetEye Master and the Alyvix node can be set up on different networks.

This Alyvix node is dedicated to only one Tenant and hence the communication between the Alyvix node and the NetEye Master will flow through a Satellite of that Tenant. This architecture forces the Alyvix node to run sessions belonging to one specific Tenant, meaning that all the sessions running on a node will be related to one Tenant.

Please note that, to associate a Multitenant - Tenant Specific Alyvix node to a tenant, this must be specified in the Host configuration in the Icinga Director.

The configuration of an Alyvix Multitenant - Tenant specific in the Director

Note

This node is currently not fully supported, meaning that the API/HTTP communication is still direct between the NetEye Master and the Alyvix node

Communication between the Alyvix node and the |ne| Master through Satellites

Fig. 142 Communication between the Alyvix node and the NetEye Master through Satellites

Multitenant - Tenant Shared

This node is meant to be used in Multitenant environments the Alyvix node serves multiple Tenants. This Alyvix node can run sessions belonging to different Tenants and is managed by the admin of the NetEye Master. For this reason, the NetEye Master and the Alyvix node must be set up on the same network.

In this case, the NetEye Master will communicate directly with the Alyvix node without the need of Satellites. For this reason, all the sessions running on the node must be configured to be related to one specific Tenant from the available ones.

Direct communication between the Alyvix node and the |ne| Master

Fig. 143 Direct communication between the Alyvix node and the NetEye Master

Single Tenant - Via Satellite

This node is equivalent to the Multitenant - Tenant Specific node but for single Tenant environments. Note that in single Tenant environments the only Tenant available is always the Master Tenant.

Note

This node is currently not fully supported, meaning that the API/HTTP communication is still direct between the NetEye Master and the Alyvix nodes

Single Tenant - Direct to Master

This node is equivalent to the Multitenant - Tenant Shared node but for single Tenant environments. Note that in single Tenant environments the only Tenant available is always the Master Tenant.

Roles

The following roles are currently supported in the NetEye Alyvix integration. For more information about how to configure IcingaWeb2 roles to match the one described below, please consult the User Roles section.

Super Admin

A user having the Super Admin role is considered as an administrator of each configured Alyvix node and hence has their full control, with all capabilities.

Tenant Admin

A user having the Tenant Admin role is considered as an administrator of one (or more) NetEye Tenants, associated to his role.

As an administrator of a tenant, the user has administrative access on all the Multitenant - Tenant Specific nodes associated with that tenant.

On Multitenant - Tenant Shared nodes, the Tenant Admin has control over objects specific to the tenants under their administration. This includes editing their tenants’ Sessions, creating Test Cases, adding and editing their tags and monitoring their results. However, they do not have authority to manage global configurations of the node, such as creating new Sessions or managing the license.

Tenant Viewer

A user with Tenant Viewer role is granted read-only access to one or more NetEye Tenants associated with their role.

Within the Multitenant - Tenant Specific nodes, the Tenant Viewer can observe activities and data pertinent to their assigned tenants.

Optionally, the Tenant Viewer can be limited to viewing a specific subset of the Alyvix Test Cases of the Tenant. This restriction is based on the tags assigned to their role, acting as filters. Consequently, the Tenant Viewer gains visibility solely into the Test Cases linked with the designated tags. This filtering functionality is exclusive to the Tenant Viewer role and can be set up by following the steps outlined in the Tenant Viewer Configuration section.

On Multitenant - Tenant Shared nodes, similar to a Tenant Admin user, the Tenant Viewer can view tenant-specific objects, including Sessions and Test Cases, and monitor their outcomes. However, they do not have permissions to observe global characteristics such as configurations, available sessions or licenses.

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