Documentation forWeb Performance Monitor

WPM 2024.2 system requirements

Release date: June 4, 2024

SolarWinds strongly recommends that you install the SolarWinds Platform on a server that is neither public, nor internet-facing. To learn about best practices for configuring your SolarWinds Platform installation securely, see Secure Configuration for the SolarWinds Platform.

These recommended system requirements are for SolarWinds Web Performance Monitor (WPM) 2024.2, as a single product installed on SolarWinds Platform 2024.2.

Note the following details about system requirements:

SolarWinds Platform requirements

For on-premise requirements (software, hardware, or database requirements) as well as for cloud requirements, see SolarWinds Platform 2024.2 system requirements.

Account privileges

Software Requirements
Account privileges

SolarWinds recommends that SolarWinds Platform administrators have local administrator privileges on the SolarWinds Platform server to ensure full functionality of local SolarWinds Platform tools. SolarWinds Platform user accounts limited to the SolarWinds Platform Web Console do not require local administrator privileges.

SolarWinds Pingdom

To use WPM recordings for Transaction Monitoring in Pingdom, you'll need an active Pingdom account to generate Pingdom API tokens for Web Transaction Recorders. See the WPM Getting Started Guide for details.

Not using Pingdom yet? Click here to start your free trial.

Port requirements

Return to top

The following port requirements apply to the primary WPM installation on the SolarWinds Platform server. For remote machines, see Web Transaction Recorder and WPM Player requirements.

  • Ports 4369, 25672, and 5672 are open by default on the SolarWinds Platform server for RabbitMQ messaging, but may be blocked by the firewall. If running SolarWinds High Availability (HA), open ports 4369 and 25672.
  • RPC ports > 1024 (TCP, bidirectional) are used by the Job Engine v2 process to communicate with Windows nodes.

SolarWinds does not recommend the use of HTTP (Port 80). Please use HTTPS (Port 443) to ensure that any web-related connections are secure.

Port # Protocol Service/Process Direction Description Encryption

User-defined default: 22

SSH

SolarWinds Job Engine v2

IIS

Outbound from the SolarWinds Platform server to devices

Access Cisco Adaptive Security Appliance (ASA) devices through the Command-Line Interface (CLI).

Device-based
25 TCP SolarWinds Alerting Service V2 Outbound

SMTP port for non-encrypted messages

 
53 UDP SolarWinds Job Engine V2 Bidirectional

Resolve DNS queries

 
80 TCP IIS Inbound

Default Additional Web Server (AWS) port. If you specify any port other than 80, include that port in the URL used to access the Web Console. For example, if you specify 192.168.0.3 and port 8080, the URL to access the SolarWinds Platform Web Console is http://192.168.0.3:8080the release constraints for 2020.2.3 are the same as for 2020.2.1

Open the port to enable communication from systems to the Web Console.

 
135 TCP Microsoft EPMAP (DCE/RPC Locator service) Bidirectional

Required for WMI polling, this port initiates communication with remotely managed hosts, then switches to a random port between 1024 and 65535.

 
161 UDP SolarWinds Job Engine v2, SolarWinds Cortex (communication) Bidirectional

Send and receive SNMP information.

SNMP v1 and v2 are unencrypted.

SNMP v3 uses AES and 3DES encryption.

162 UDP

SolarWinds Trap Service

SNMP Informs

Bidirectional

Send and receive trap messages.

 
443 TCP IIS Inbound

Default port for HTTPS binding. Also used for bi-directional ESX/ESXi server polling.

SSL
465 TCP SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions.

SSL
514 UDP SolarWinds Syslog Service Inbound

Receive syslog messages

 
587 TCP SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions.

TLS
1433 TCP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Platform Module Engine

Outbound

Supports communication from the SolarWinds Platform server to the SolarWinds Platform database server.

 
1434 UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Platform Module Engine

SQL Server Browse Service

Outbound

Supports communication with the SQL Server Browser Service to determine how to handle certain non-standard SQL Server installations.

Required only if your SolarWinds Platform database server is configured to use dynamic ports.

 
5671 TCP RabbitMQ Bidirectional

For encrypted RabbitMQ messaging (AMQP/TLS) into the Main Polling Engine from scalability engines.

TLS 1.2
17777 TCP

SolarWinds Platform Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex (communication)

Bidirectional

Supports communication between:

  • SolarWinds Platform services and SolarWinds Platform module traffic.
  • The SolarWinds Platform Web Console, the Main Polling Engine, and scalability engines.
  • The main SolarWinds Platform server and pool members.

RSA handshake, AES 256 communication using WCF

TLS 1.2 with Cortex

17778 HTTPS SolarWinds Agent Bidirectional

Supports access to the SWIS API and agent communication.

SSL
17781 TCP WPM Playback Player Bidirectional

Used for communication between the SolarWinds Platform server and remote systems that host WPM Players.

 
17782 TCP WPM Playback Player Bidirectional

Used for WPM Player-initiated communications.

 
17783 TCP WPM Playback Player Bidirectional

Used for automatic WPM Player updates.

 
17784 TCP WPM Playback Player Bidirectional

Used for inter-process communication between the WPM Playback Player service running on the SolarWinds Platform server, an APE, or a remote machine, and the following local apps running on systems that host WPM Players:

 

Web Transaction Recorder requirements

When you install the SolarWinds Platform, two different WPM recorders are added to the SolarWinds Platform server automatically. You can also deploy recorders to remote systems.

Here are minimum requirements for remote systems that host a Web Transaction Recorder, which is based on Chromium 120.0.6099.227:

Resource Requirement
CPU 1 GHz or more
Memory 2 GB
OS
  • x64 systems only
  • Windows 10, 11
  • Windows Server 2016 and 2019
    • WPM uses Electron 28.2.0 with Chromium 120.0.6099.227 and Node.js 18.18.2, which support only the operating systems listed above.
    • Keep Windows scale and layout settings set to 100% to support image validation.

The following macOS versions are supported:

  • Sonoma
  • Ventura
  • Monterey
  • Big Sur
  • Catalina
TCP ports
  • 80, for HTTP traffic
  • 443, for HTTPS traffic
  • 445, for automated remote deployment to target systems by the Agent installer via Microsoft-DS SMB file sharing.
  • 17777, for SolarWinds traffic
  • 17774, for outgoing traffic port for SWIS
  • Two random ports between 1024—65535 for inter-process communication between recorders, probes, and drivers

    Configure firewalls to support binding for random ports 127.0.0.1:1024—127.0.0.1:65535.

Here are minimum requirements for remote systems that host a Deprecated WPM Recorder:

Resource Requirement
CPU 1 GHz or more
Memory 2 GB
OS
  • x64 systems only
  • Windows 10*, 11*
  • Windows Server 2016*, and 2019*

*SSL certificate authentication is not supported on some OS.

TCP ports
  • 80, for HTTP traffic
  • 443, for HTTPS traffic
  • 17777, for SolarWinds traffic
Web browser

Internet Explorer 11

If your organization requires an earlier IE version, use IE 11 Document Mode to emulate earlier versions.

WPM Player requirements

Return to top

Note the following details about remote systems that host the WPM Player Playback service and play recorded transactions at scheduled intervals:

  • If a system hosts a hypervisor or Virtual Machine Monitor (VMM) that runs other servers (such as print or file servers), consider hosting the WPM Player elsewhere.
  • To manage loads on systems that host WPM Players, see Scalability Engine Guidelines for SolarWinds Platform Products. You can also check the Player Load Percentage widget.
  • The WPM Player Playback service is based on Chromium 120.0.6099.227.
  • If not already installed, you may be prompted to verify the installation of:
    • Microsoft Visual C++ 2015-2019 x86 Redistributable
    • Microsoft Visual C++ 2015-2019 x64 Redistributable

The following requirements apply to remote systems that host WPM Players:

Resource Requirement
CPU Quad core processor or better
Memory 3 GB
.NET Framework .NET 4.8 or later
Operating system
  • Windows 10*, 11*
  • Windows Server 2016* and 2019*

WPM uses Electron 28.2.0 with Chromium 120.0.6099.227 and Node.js 18.18.2, which support only the operating systems listed above.

*Steps with certificate validation may interrupt playback, as described here.

Do not install WPM on domain controllers, or on Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers.

Accounts and security
TCP ports
  • 80, for outbound HTTP traffic
  • 135, for executing remote code during WPM Player deployment
  • 443, for outbound HTTPS traffic
  • 445, for automated remote deployment to target systems by the Agent installer via Microsoft-DS SMB file sharing.
  • 17777, for outbound SolarWinds traffic
  • 17781, for bidirectional, server-initiated (passive) communication mode
  • 17782, for bidirectional, player-initiated (active) communication mode
  • 17783, for bidirectional, automatic WPM Player updates
  • 17784, for bidirectional, inter-process communication between:

In addition, allow a random port between 1024 and 65535 for inter-process communication between WPM players, probes, and drivers.

Configure firewalls to support the binding of a random port, between 127.0.0.1:1024 and 127.0.0.1:65535.

Windows settings

The following settings are updated during WPM Player deployment:

  • Net.Tcp Port Sharing Service: The Startup Type is set to Manual on the SolarWinds Platform server and any Additional Polling Engines (APEs). On remote systems, the Startup Type is set to Automatic.
  • SolarWinds WPM Playback Player service: A dependency with the Net.Tcp Port Sharing Service is added.
Web browser

Internet Explorer 11

If your organization requires an earlier IE version, use IE 11 Document Mode to emulate earlier versions.