Documentation forServer & Application Monitor
Monitoring your applications and environment is a key capability of Hybrid Cloud Observability and is also available in a standalone module, Server & Application Monitor (SAM). Hybrid Cloud Observability and SAM are built on the self-hosted SolarWinds Platform.

SAM component monitors

As described in the SAM Administrator Guide, SAM includes predefined component monitors, comprised of code and scripts, that you can use to assess the status and performance of applications, services, processes, and event on nodes throughout your environment.

SAM application monitor templates are collections of component monitors that you can assign to nodes as "application monitors" that are also called "applications." A single component monitor can be used on its own and applied to a node in an application monitor, or it can be used in multiple templates.

For example, an HTTPS Monitor is included in the following templates:

For a quick overview, watch Common SAM template elements.

Note the following details about SAM component monitors:

The following predefined component monitors are included in SAM:

Can't find a suitable component monitor? Use the Component Monitor Wizard to create a custom monitor. You can also use API pollers to gather metrics from remote APIs.

SolarWinds Platform server port requirements for component monitors

WinRM is now the default method used to fetch data for WMI-based component monitors. Per SAM WMI port requirements, open port 5985 for HTTP, or 5986 for HTTPS.

The following table outlines port requirements for SAM component monitors.

Component monitor Port Port
DHCP User Experience Monitor See Notes. UDP

For DHCP requests, the default port is 67 (IPv4) or 547 (IPv6).

For DHCP responses, the default port is 68 (IPv4) or 546 (IPv6).

Directory Size Monitor

See SAM WMI requirements.

DNS Monitor - TCP

DNS Monitor - UDP

DNS User Experience Monitor

53 TCP/UDP Used for DNS queries.
Download Speed Monitor 19 Used for the character generator service.
ESX Hardware Monitoring 5989 Used to collect vCenter data via API.

File Age Monitor

File Change Monitor

File Existence Monitor

File Size Monitor

File Count Monitor


See SAM WMI requirements and Poll devices with SolarWinds SolarWinds Platform agents.

FTP Monitor

FTP User Experience Monitor

21 Used for FTP sessions.

HTTP Form Login Monitor

HTTP Monitor

TCP Port Monitor

80 Used for HTTP form-based login sessions.
HTTPS Monitor 443 Used to test a web server's ability to accept incoming sessions over a secure channel and then transmit the requested page.
IMAP4 Monitor 143 (default) IMAP4 Used for IMAP 4 sessions.
585 IMAP4 Used for Secure IMAP (IMAP4-SSL) sessions.
993 IMAP4 Used for IMAP4 over SSL (IMAPS) sessions.
IMAP4 User Experience Monitor 25 SMTP Used to communicate with a Microsoft Exchange mail server.
143 IMAP4
993 IMAP4
LDAP User Experience Monitor 389 Used for LDAP connections.
636 Used for LDAP connections over SSL, with default port 636.
Linux/Unix Script Monitor Ports 22 Used for SSH connections.
NNTP Monitor 119 UDP Used for Network News Transfer Protocol (NNTP) connections.
ODBC User Experience Monitor 1630 TCP

To configure ODBC to use the SolarWinds Platform Agent, see Configure Linux/Unix systems for monitoring by the SolarWinds Platform agent in SAM.

Oracle User Experience Monitor 1521 TCP Configure the Oracle SQL*Net Listener to allow Oracle Client connections to the database with the SQL*Net protocol during installation. You can also use the Oracle Net Configuration Assistant.
Performance Counter Monitor See Description. TCP

For monitors configured to use RPC instead of WinRM, open the following ports:

  • TCP/135
  • RPC/named pipes (NP) TCP 139
  • RPC/NP TCP 445
  • RPC/NP UDP 137
  • RPC/NP UDP 138
POP3 Monitor See Description.

This monitor uses the following ports to communicate with Microsoft Exchange mail servers:

  • 102 X.400 MTA
  • 110 POP3
  • 119 NNTP
  • 143 IMAP4
  • 389 LDAP
  • 563 POP3 over SSL
  • 636 LDAP over SSL
  • 993 IMAP4 over SSL
  • 995 Secure POP3 over SSL

POP3 Monitor

POP3 User Experience Monitor

110 (default) Used for POP3 connections.
995 Used for Secure POP3 (SSL-POP) connections.
25 SMTP Used for SMTP sessions.
Process Monitor  


Uses SNMP communication.

Process Monitor - Windows

Used to test if a specified Windows process is running and reports statistics about all instances of the process.

RADIUS User Experience Monitor



Used to authenticate RADIUS protocols, along with port 1813. Cisco devices may require port 1645 or 1646.

RWHOIS Port Monitor 4321 Used to test the ability of a Referral Whois (RWhois) server to accept incoming sessions.
SMTP Monitor 465 SMTP Used for Secure SMTP (SSMTP).
SNMP Monitor 444 SNMP Used to test the ability of an SNMP server to accept incoming sessions.
SQL Server User Experience Monitor 1433 By default, SQL Server uses port 1433. To use a different port, use the ODBC User Experience Monitor instead, and manually define a connection string for the port.
TACACS+User Experience Monitor 49 Used for TACACS+ protocol connections.
Tomcat Server Monitor 8080 Used to collect status the Apache Tomcat status website.
VMware Performance Counter Monitor 443 Used to communicate with the VMware API.
Windows Event Log Monitor

Uses the following ports:

  • TCP/135
  • RPC/named pipes (NP) TCP 139
  • RPC/NP TCP 445
  • RPC/NP UDP 137
  • RPC/NP UDP 138
  • POP3 User Experience Monitor port 110

SAM WMI port requirements

Starting in SAM 2020.2, WinRM is the default transport method for WMI-based component monitors that gather data from target nodes for component monitors. A fallback mechanism automatically switches to legacy RPC/DCOM polling, if necessary. Component monitors that use WinRM require a single open port: 5985 (HTTP), or 5986 (HTTPS).

In SAM 2019.4 or earlier, you may need to create firewall exceptions to allow bidirectional TCP/UDP traffic on those ports to support component monitors that use WMI. If wide ranges of open ports present security concerns, you can either:

The following component monitors use WMI:

  • Performance Counter Monitor
  • Process Monitor – WMI*
  • Windows Event Log Monitor
  • Windows PowerShell Monitor*
  • Windows Script Monitor
  • Windows Service Monitor*

* Required if scripts use WMI

Learn more