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 Asset Management
Overview Permissions Installation Single Tenancy Multitenancy Communication through a Satellite Asset collection methods Display asset information in monitoring host page
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

Asset collection methods

Asset collection can be performed with the help of GLPI Agent software that can be used in two different ways: agentless or agent-based. To correctly install and configure the GLPI Agent software, the following steps should be executed:

  1. Install GLPI Agent on the desired device following the official GLPI documentation. GLPI Agent can be installed on both Linux and Windows nodes that are external to the NetEye environment. For Windows installation we recommend to use the .msi package.

    Hint

    In order to execute glpi-agent and glpi-remote commands on Windows machines, be sure to operate as administrator from the GLPI-Agent folder.

  2. Find credentials for the agent: GLPI Agent has a dedicated NetEye user called neteye_glpi_agent_<tenant_name> authorized to send assets to the Master. User’s password can be found in /root/.pwd_neteye_glpi_agent_<tenant_name> and should be used for authentication when sending inventories.

    For installations with a Single Tenant the default credentials are:

    • user: neteye_glpi_agent_master

    • password can be found in /root/.pwd_neteye_glpi_agent_master.

  3. Configure the user and password credentials for the agent in the config file on the system.

  4. Choose the node where to send assets:

    • Master: GLPI Agent can send inventories directly to the Master. In that case, the Master hostname should be used as <neteye_addr>.

    • Satellite: In order to use a Satellite as a proxy to forward assets to the Master, the Satellite hostname should be selected as <neteye_addr>

After the first configuration parts has been executed, agent-based or agentless mode should be selected to start collecting assets.

Agent-based

The inventory can be performed on the node where the GLPI Agent software is installed with the following command:

Linux:

glpi-agent -f --logger=stderr \
-s https://<neteye_addr>/glpi/front/inventory.php \
--tasks inventory

Windows:

glpi-agent -f --logger=stderr ^
-s https://<neteye_addr>/glpi/front/inventory.php ^
--tasks inventory

Where <neteye_addr> is the address of the endpoint, as previously described. Once the inventory has been performed, the GLPI Agent will send it to the specified target hostname.

More information about the glpi-agent command can be found in glpi-agent.

Agentless

If no software can be installed on the devices from which assets are collected, agentless mode can be selected. A GLPI Agent server will perform the inventory on remote devices and subsequently send assets to the Master. Note that the software GLPI Agent should not be installed on remotes, but only on a separate node that will act as a server that performs the remote inventory.

Hint

We recommend to use agent-based asset collection method over agentless when applicable, since involving agents in the asset collection process proves to be a more secure solution.

../../_images/agentless-diagram.svg

Fig. 191 GLPI Agent performs inventories to the remote devices.

Windows remote configuration In order to establish a secure connection with a Windows remote WinRM with transport HTTPS should be correctly configured for a SSL connection. Detailed information can be found in the official Microsoft guide.

GLPI Agent, used as a server between remotes and NetEye, should be configured as it follows:

Linux server configuration

  1. Specify the target server: Using agentless mode, the target server should be declared before inserting the remotes. You should specify the previously defined parameters with the command:

    glpi-agent \
    --server=https://<neteye_addr>/glpi/front/inventory.php
    
  2. Extract the ID of the specified target server with the command:

    glpi-remote list targets
    
  3. Add remote devices with the following command:

    For a Linux remote machine:

    glpi-remote \
    add ssh://<remote_user>:<remote_pass>@<addr>/?mode=libssh2 \
    --target <server_id>
    

    Hint

    Make sure to have the perl library Net:SSH2 installed by executing the command perl -e "use Net:SSH2. libssh2 should also be installed on the server machine.

    For Windows remotes:

    glpi-remote \
    add winrm://<remote_user>:<remote_pass>@<addr>/?mode=ssl \
    --target <server_id>
    
    • <remote_user> and <remote_pass> are the credentials that GLPI Agent should use on remotes to perform the inventory

    • <addr> is the IP address or hostname of the remote device

    • <server_id> is the ID of the previously inserted target server that can be shown with the glpi-remote list targets command.

    Warning

    NetEye Security is granted only if mode=libssh2 and mode=ssl are used for Linux and Windows remotes respectively.

    Hint

    By exchanging ssh keys, <remote_pass> is not needed when adding the remote device.

  4. Execute the remote inventory task of the GLPI Agent to collect assets and send them to the Master:

    glpi-agent -f --logger=stderr --tasks remoteinventory \
    -s https://<neteye_addr>/glpi/front/inventory.php
    

Where <neteye_addr> is the address of the endpoint, as previously described in the Asset collection methods Once the inventory has been performed, the GLPI Agent will send it to the specified target hostname.

Windows server configuration

  1. Specify the target server: Using agentless mode, the target server should be declared before inserting the remotes. You should specify the previously defined parameters with the command:

    glpi-agent ^
    --server=https://<neteye_addr>/glpi/front/inventory.php
    
  2. Extract the ID of the specified target server with the command:

    glpi-remote list targets
    
  3. Add remote devices with the following command:

    For a Linux remote machine:

    glpi-remote ^
    add ssh://<remote_user>:<remote_pass>@<addr>/?mode=libssh2 ^
    --target <server_id>
    

    Hint

    Make sure to have the perl library Net:SSH2 installed by executing the command perl -e "use Net:SSH2. libssh2 should also be installed on the server machine.

    For Windows remotes:

    glpi-remote ^
    add winrm://<remote_user>:<remote_pass>@<addr>/?mode=ssl ^
    --target <server_id>
    
    • <remote_user> and <remote_pass> are the credentials that GLPI Agent should use on remotes to perform the inventory

    • <addr> is the IP address or hostname of the remote device

    • <server_id> is the ID of the previously inserted target server that can be shown with the glpi-remote list targets command.

    Warning

    NetEye Security is granted only if mode=libssh2 and mode=ssl are used for Linux and Windows remotes respectively.

    Hint

    By exchanging ssh keys, <remote_pass> is not needed when adding the remote device.

  4. Execute the remote inventory task of the GLPI Agent to collect assets and send them to the Master:

    glpi-agent -f --logger=stderr --tasks remoteinventory ^
    -s https://<neteye_addr>/glpi/front/inventory.php
    

Where <neteye_addr> is the address of the endpoint, as previously described in the Asset collection methods Once the inventory has been performed, the GLPI Agent will send it to the specified target hostname.

More information about the glpi-remote command can be found in glpi-agent.