Documentation forNetwork Performance Monitor
Monitoring network performance is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Network Performance Monitor (NPM). Hybrid Cloud Observability and NPM are built on the self-hosted SolarWinds Platform.

Discover your network with NPM

  See this video: Creating a Manual Discovery Job.

After you have installed and configured NPM, log in to the SolarWinds Platform Web Console and scan your network for devices to monitor.

Log in to the SolarWinds Platform Web Console

In a web browser, navigate to http://HostnameOrIPaddress:port, where

  • HostnameOrIPaddress the hostname or IP address of the server where NPM is installed
  • port is the port defined for the website, specified in the Configuration wizard. By default, this is 8787.

Discovery is a term used to describe the process to identify network elements.

Before you discover your network, go through the Discovery checklist.

  1. If the Discovery Wizard does not start automatically after configuration, click Settings > Network Discovery.

  2. Click Add New Discovery, and then click Start.

  3. On the Network panel, if this is your first discovery, add a limited number of IP addresses.

    As you scale your implementation, you can use the following scanning options.

    Option Description
    IP Ranges

    Use this option when you want to scan one or more IP ranges.

    If you have many IP ranges to scan, consider adding multiple discovery jobs rather than including all ranges in a single job.

    Subnets

    Use this option to scan every IP address in a subnet. SolarWinds recommends scanning at most a /23 subnet (512 addresses max).

    Scanning a subnet returns everything that responds to ping, so we recommend only scanning subnets where the majority of devices are objects you want to monitor.

    IP Addresses

    Use this option for a limited number of IP addresses that do not fall in a range.

    A network discovery job can take a long time to complete, and soSolarWinds recommends using this option when you are first starting out.

    Active Directory

    Use this option to scan an Active Directory Domain Controller.

    Using Active Directory for discovery is particularly useful for adding large subnets because the discovery can use the devices specified in Active Directory instead of scanning every IP address.

  4. If the Agents panel appears, you enabled the Quality of Experience (QoE) agent during installation. The QoE agent monitors packet-level traffic. If there are any nodes using agents, select the Check all existing nodes check box.

    This setting ensures that any agents you deploy, including the one on your SolarWinds Platform server, are up-to-date. If there are no nodes using agents, you can leave this option unchecked.

  5. On the Virtualization panel, to discover VMware vCenter or ESX hosts on your network:

    1. Check Poll for VMware, and click Add vCenter or ESX Credential.

    2. Select <New credential> and provide required information.

      If you do not add the host credentials, the virtual machines (VMs) on the host are still discovered. However, you will not be able to see the relationships mapped between the VMs and hosts.

  6. On the SNMP panel:

    1. If all devices on your network require only the default SNMPv1 and SNMPv2 public and private community stings, click Next.

    2. If any device on your network uses a community string other than public or private, or if you want to use an SNMPv3 credential, click Add Credential and provide the required information.

  7. On the Windows panel, to discover WMI or RPC-enabled Windows devices, click Add New Credential and provide the required information.

    SolarWinds recommends that you monitor Windows devices with WMI instead of SNMP.

  8. On the Monitoring Settings panel, SolarWinds recommends manually setting up monitoring the first time you run discovery. This allows you to review the list of discovered objects and select the ones you want to monitor.

    When you scale monitoring, you can configure discovery to automatically start monitoring objects it finds.

  9. On the Discovery Settings panel, click Next.

  10. Accept the default frequency and run the discovery immediately.

    Discovery can take anywhere from a few minutes to a few hours, depending on the number of network elements the system discovers.