APM services' system requirements
Requirements to use an APM library to instrument the services powering your application depend on several variables, such as:
- Which APM library you are deploying.
- The volume of data to display in the browser.
This topic contains:
SolarWinds Observability SaaS general requirements
The following table lists browser requirements and recommendations for using the SolarWinds Observability SaaS web application.
Performance of the computer and internet speed where you open the browser significantly influences the speed of SolarWinds Observability SaaS.
| Software Requirements | |
|---|---|
| Web browsers |
SolarWinds Observability SaaS supports the two most recent versions of the following web browsers:
|
| Browser requirements |
The following must be enabled in your browser:
|
Firewall or access control requirements
The browser you are using to access SolarWinds Observability SaaS's basic features must have unrestricted access to the following locations:
- https://my.xx-yy.cloud.solarwinds.com and all subfolders (where
xx-yyis determined by the URL you use to access SolarWinds Observability SaaS, described in Data centers and endpoint URIs) - https://documentation.solarwinds.com/ and all subfolders
- https://agent-binaries.cloud.solarwinds.com/ and all subfolders
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 (and otel.collector.xx-yy.cloud.solarwinds.com when OTLP is enabled), where xx-yy is determined by the URL you use to access SolarWinds Observability SaaS. See Data centers and 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. This typically requires the system to be set up with trusted CA certificates, for example by installing
ca-certificateson Linux, enabling and triggering Windows Automatic Root Certificates Update on Windows, and checking the trust store configured for JVM applications. - Alternatively, use a proxy to forward connections to the SolarWinds APM collector. See Proxy configuration.
Supported platforms
This page includes a summary of all currently supported platforms for the APM libraries.
Operating Systems
64-bit only
Currently only the Java and .NET libraries support Windows.
Linux
SolarWinds Observability APM libraries work on most Linux systems.
glibc version 2.28 or higher is required on GNU C Library-based systems such as Debian and Ubuntu.
The following Linux platforms have been tested and verified to work with the APM libraries for both x86_64 and aarch64 architectures:
- Debian 10
- Debian 11
- Debian 12
- Ubuntu 20.04
- Ubuntu 22.04
- Alpine Linux 3.13
- Alpine Linux 3.14
- Alpine Linux 3.15
- Alpine Linux 3.16
- Alpine Linux 3.17
- Alpine Linux 3.18
- Alpine Linux 3.19
Windows
- Windows Server 2008 R2
- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
- Windows Server 2022
Container Systems
The APM libraries can be used in a variety of containerized environments, including Docker and Kubernetes.
For full integration with the telemetry gathered by Kubernetes monitoring, ensure the following minimum APM library version is used:
See library-specific notes below.
- .NET Library
Platform as a Service
- Azure App Service – all libraries can be easily enabled for your application running on Azure App Service, see the library-specific links below for details.
Supported components
See each language's list of supported components, frameworks, and libraries: