Documentation forSolarWinds Observability

SolarWinds Observability System Requirements

Requirements depend on several variables, such as:

  • Whether SolarWinds Observability libraries and clients are deployed.
  • The volume of data to display in the browser.
  • The areas you select for monitoring.

This topic contains:

SolarWinds Observability general requirements

The following table lists browser requirements and recommendations for using the SolarWinds Observability web application.

Performance of the computer and internet speed where you open the browser significantly influences the speed of SolarWinds Observability.

Software Requirements
Web browsers

SolarWinds Observability supports the two most recent versions of the following web browsers:

  • Mozilla Firefox
  • Google Chrome

SolarWinds Observability also supports the following browsers:

  • Microsoft Internet Explorer 11 with Active scripting

    Do not enable Enterprise Mode on Internet Explorer. This setting forces Internet Explorer to emulate version 7, which is not supported.

  • Microsoft Edge

Browser requirements

The following must be enabled in your browser:

  • JavaScript
  • Cookies

Firewall or access control requirements

The browser you are using to access SolarWinds Observability's basic features must have unrestricted access to the following locations:

For network device, service, database, and host monitoring, the collectors installed on the monitored device or host must be able to communicate with the SolarWinds Observability ingestion endpoint. To enable access to all SolarWinds Observability ingestion endpoints, open your firewall or access control configuration to allow access to all subdomains and subfolders for cloud.solarwinds.com. For more precise configuration, see Network device entity, Services entity, Database entity, and Host entity.

Website entity

SolarWinds Observability synthetic probes must be able to access your site. To observe websites hosted on a local network, your server or site must open access to SolarWinds Observability probe server IP addresses.

  • To view a list of all IP addresses used click Settings > Synthetic Probes in the left pane. This page lists all available probes and their corresponding region, platform, and IP address. See Synthetic Probes Settings.

Services entity

The SolarWinds Observability APM libraries that monitor your applications must be able to communicate with the SolarWinds APM collector to report collected data. The SolarWinds APM collector endpoint URI is apm.collector.xx-yy.cloud.solarwinds.com, where xx-yy is determined by the URL you use to access SolarWinds Observability, see Endpoint URIs.

  • Open your firewall or access control configuration to permit TCP/HTTPS/TLS outbound connections to your SolarWinds APM collector using port 443.

    The issuer Certificate Authority (CA) for the SolarWinds APM collector's certificate must be considered trusted by the SSL/TLS configuration on the service's system. To view the certificate for the SolarWinds APM collector, go to the URL for the SolarWinds APM collector in a browser and select the padlock in the address bar. In the details about the site's secure connection, select to view the certificate(s) information.

  • Alternatively, use a proxy to forward connections to the SolarWinds APM collector. See Proxy configuration.

Network device entity

The clients and agents installed when monitoring a network device must be able to communicate with the SolarWinds Observability collector to report collected data.

Open your firewall or access control configuration to permit TCP/HTTPS/TLS outbound connections to the following endpoints (where xx-yy is determined by the URL you use to access SolarWinds Observability, see Endpoint URIs) using port 443:

  • uams.xx-yy.cloud.solarwinds.com
  • otel.collector.xx-yy.cloud.solarwinds.com
  • agent-plugins.cloud.solarwinds.com

Review the following port requirements. See also port requirements in SolarWinds Platform on-prem requirements.

Default port Protocol Direction Description
161 UDP, TCP Outbound Port used by the Network Collector for sending and receiving SNMP data from network devices.
443 HTTPS Outbound Port used for communication with cloud endpoints.
2055 UDP Inbound Port for receiving flows on the Network Collector. See NetFlow port requirements.
17777, 17778 TCP Inbound Special case: If the Network Collector and SolarWinds Observability Agent are installed on different servers, inbound rules for these ports are needed.

Database entity

If monitoring a database using the SolarWinds Observability Agent, the SolarWinds Observability Agent must be able to communicate with the SolarWinds Observability collector to report collected data.

Open your firewall or access control configuration to permit TCP/HTTPS/TLS outbound connections to the following endpoints (where xx-yy is determined by the URL you use to access SolarWinds Observability, see Endpoint URIs) using port 443:

  • uams.xx-yy.cloud.solarwinds.com
  • otel.collector.xx-yy.cloud.solarwinds.com
  • agent-plugins.cloud.solarwinds.com

Host entity

If monitoring a self-managed host, the SolarWinds Observability Agent must be able to communicate with the SolarWinds Observability collector to report collected data.

Open your firewall or access control configuration to permit TCP/HTTPS/TLS outbound connections to the following endpoints (where xx-yy is determined by the URL you use to access SolarWinds Observability, see Endpoint URIs) using port 443:

  • uams.xx-yy.cloud.solarwinds.com
  • otel.collector.xx-yy.cloud.solarwinds.com
  • agent-plugins.cloud.solarwinds.com

Operating systems and distributions supported for the script-based installation of SolarWinds Observability Agent

If an operating system/distribution is not in the list, download and run the installer using the PowerShell command provided in the Add Data wizard.

Windows

  • Windows Server 2016
  • Windows Server 2019
  • Windows Server 2022
  • Windows 10
  • Windows 11

On Windows Server 2012, download the MSI file manually and run it using the provided PowerShell command. Script-based installation has issues with establishing a connection to download SWO Agent binaries.

Linux

SWO Agents work on most Linux systems. The following lists the platforms that have been tested and verified to work with the SWO Agents:

  • Amazon Linux 2
  • CentOS 7 and later
  • Debian 9 and later
  • Fedora 32 and later
  • Kali 2021 and later
  • Oracle Linux 8 and later
  • RedHat 7.1 and later
  • Ubuntu 18.04 and later

Logs

When sending logs to SolarWinds Observability, open your firewall or access control configuration to permit TCP/HTTPS/TLS outbound connections to the following endpoints, where xx-yy is determined by the URL you use to access SolarWinds Observability, see Endpoint URIs.

  • https://logs.collector.xx-yy.cloud.solarwinds.com (to post logs over HTTPS)
  • syslog.collector.xx-yy.cloud.solarwinds.com (to send logs using syslog) using port 6514.

Services supported platforms

This page includes a summary of all currently supported platforms for the APM libraries.

Languages

See each language's list of supported components, frameworks, and libraries:

Operating Systems

64-bit only

Currently only the Java and .NET libraries support Windows.

Currently only the Java and PHP libraries supports ARMv8.

Linux

SolarWinds Observability APM libraries work on most Linux systems. The following lists the platforms that have been tested and verified to work with the APM libraries:

  • Debian 8 - AMD64
  • Debian 9 - AMD64, ARMv8
  • Debian 10 - AMD64, ARMv8
  • Ubuntu 14.04 - AMD64
  • Ubuntu 16.04 - AMD64, ARMv8
  • Ubuntu 18.04 - AMD64, ARMv8
  • Ubuntu 20.04 - AMD64, ARMv8
  • RHEL/CentOS 7 - AMD64
  • RHEL/CentOS 8 - AMD64, ARMv8
  • Amazon Linux 2016.03 - AMD64
  • Amazon Linux 2016.09 - AMD64
  • Amazon Linux 2017.03 - AMD64
  • Amazon Linux 2017.09 - AMD64
  • Amazon Linux 2018.03 - AMD64
  • Amazon Linux 2 - AMD64, ARMv8
  • Alpine Linux 3.13 - AMD64, ARMv8
  • Alpine Linux 3.14 - AMD64, ARMv8
  • Alpine Linux 3.15 - AMD64, ARMv8
  • Alpine Linux 3.16 - AMD64, ARMv8

Windows

  • Windows Server 2008 R2
  • Windows Server 2012
  • Windows Server 2012 R2
  • Windows Server 2016
  • Windows Server 2019

Container Systems

  • Docker

Platform as a Service

Database system requirements

For details about the roles and privileges necessary for your database to be monitored by SolarWinds Observability, as well as scripts to help create users with the right permissions, see:

Host requirements

Kubernetes containers

Kubernetes versions 1.18 and higher, and kube-state-metrics 1.5.0 and higher. Local deployments such as Minikube are not supported, even if the functionality is working. Supported architecture is Linux x86 and x64 versions (AMD 64).