Data centers and endpoint URIs
SolarWinds Observability SaaS is deployed across multiple data centers spanning various global regions and cloud providers. When you create a new organization in SolarWinds Observability SaaS, you can select a data center based how close it is to you or whether you prefer your data is hosted in AWS or Azure. See Find the data center and endpoints for your organization for the available data centers.
The endpoints used to send collected data to SolarWinds Observability SaaS will vary based on the data center your organization uses.
- General endpoints
- Find the data center and endpoints for your organization
- Public IP addresses used by SolarWinds Observability SaaS per data center
General endpoints
The following table describes the general format of the endpoints used to send collected data to SolarWinds Observability SaaS. For each endpoint, replace xx-yy with your data center. See Find the data center and endpoints for your organization.
| Endpoint purpose | URI |
Monitored area | Usage details |
|---|---|---|---|
| General collector | collector.xx-yy.cloud.solarwinds.com
|
All | Location for the SolarWinds Observability collector endpoints. Each endpoint exists in a subdomain of the general collector. Open your firewall to allow access to all subdomains of collector.xx-yy.cloud.solarwinds.com. |
| Syslog logs collector | syslog.collector.xx-yy.cloud.solarwinds.com
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via syslog. |
| HTTPS logs collector | logs.collector.xx-yy.cloud.solarwinds.com/v1/logs
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via HTTPS. |
| APM collector | apm.collector.xx-yy.cloud.solarwinds.com
|
Services |
Configure your APM library to send collected data to SolarWinds Observability SaaS using this endpoint. |
| SolarWinds Observability Agent | uams.xx-yy.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for instrumentation and sending non-OTel data to SolarWinds Observability SaaS. |
| OTLP telemetry data ingestion |
port 443 |
Self-managed hosts, databases, network devices, and services |
Used by the SolarWinds Observability Agent, SWO K8s Collector, and SWO APM libraries to send collected telemetry and entity data to SolarWinds Observability SaaS. Depending on protocol, the endpoint should be as follows: OTLP/HTTP:
OTLP/gRPC:
See OTLP Exporter Configuration and OpenTelemetry Protocol Exporter for details on configuring OTel Collector or SDK exporting. |
| Collector binary connection for SolarWinds Observability Agent | agent-plugins.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for connection with the binaries that monitor entities and collect data. |
| Agent storage | agent-binaries.cloud.solarwinds.com
|
Self-managed hosts, databases, network devices, and services |
Location where SolarWinds Observability Agent and APM libraries are stored. The SolarWinds Observability Agent and some APM libraries may reach out to the following endpoints for updates.
|
| RUM collector |
|
Websites | To collect and send RUM data to SolarWinds Observability SaaS, your website visitors must have unrestricted access to the following domains. See Visitor access to the RUM script disabled. |
| Public API - Swagger | api.xx-yy.cloud.solarwinds.com
|
all areas, via public API | Used to create, read, update, or delete entities and entity data using Swagger API. See SolarWinds Observability SaaS REST API. |
| Public API - GraphQL | api.xx-yy.cloud.solarwinds.com/graphql
|
all areas, via public API | Used to access select DEM and database data using the GraphQL API. See SolarWinds Observability SaaS GraphQL API. |
Library and agent proxy configuration
If necessary, use a proxy to forward connections to the SolarWinds Observability Agent or SolarWinds APM collector endpoints. See Proxy configuration to configure a proxy for the APM libraries and Agents to configure a proxy for the SolarWinds Observability Agent.
SolarWinds APM collector certificate authority
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.
The following ports must also be opened for communication with the SolarWinds Observability SaaS collectors to report collected data. For network devices, see in SolarWinds Platform on-prem requirements for additional port 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 and the SolarWinds APM collector. |
| 6514 | TCP, HTTPS, TLS | Outbound | Port used to send logs via syslog or HTTPS. |
| 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. |
Find the data center and endpoints for your organization
The endpoint URIs used to send collected data to SolarWinds Observability SaaS vary based on the data center your organization uses. You can find the data center your organization uses by referring to the URL you use to access SolarWinds Observability SaaS. In this sample URL, XX-YY denotes the data center name: https://my.XX-YY.cloud.solarwinds.com.
Data centers and endpoint URIs:
na-01: North American AWS data center
If your organization's data is hosted on the na-01 data center, the URL you use to access SolarWinds Observability SaaS is my.na-01.cloud.solarwinds.com. All endpoints used for organizations hosted in the na-01 data center use na-01 in the URI. For any endpoint you are given that includes xx-yy in the URI, replace xx-yy with na-01. The following table shows the exact endpoints for organizations that use my.na-01.cloud.solarwinds.com.
| Endpoint purpose | URI | Monitored area | Usage details |
|---|---|---|---|
| General collector | collector.na-01.cloud.solarwinds.com
|
All | Location for the SolarWinds Observability collector endpoints. Each endpoint exists in a subdomain of the general collector. Open your firewall to allow access to all subdomains of collector.xx-yy.cloud.solarwinds.com. |
| Syslog logs collector | syslog.collector.na-01.cloud.solarwinds.com
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via syslog. |
| HTTPS logs collector | logs.collector.na-01.cloud.solarwinds.com/v1/logs
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via HTTPS. |
| APM collector | apm.collector.na-01.cloud.solarwinds.com
|
Services |
Configure your APM library to send collected data to SolarWinds Observability SaaS using this endpoint. The URI |
| SolarWinds Observability Agent | uams.na-01.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for instrumentation and sending non-OTel data to SolarWinds Observability SaaS. |
| OTLP telemetry data ingestion |
port 443 |
Self-managed hosts, databases, network devices, and services |
Used by the SolarWinds Observability Agent, SWO K8s Collector, and SWO APM libraries to send collected telemetry and entity data to SolarWinds Observability SaaS. Depending on protocol, the endpoint should be as follows: OTLP/HTTP:
OTLP/gRPC:
See OTLP Exporter Configuration and OpenTelemetry Protocol Exporter for details on configuring OTel Collector or SDK exporting. |
| Collector binary connection for SolarWinds Observability Agent | agent-plugins.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for connection with the binaries that monitor entities and collect data. |
| Agent storage | agent-binaries.cloud.solarwinds.com
|
Self-managed hosts, databases, network devices, and services |
Location where SolarWinds Observability Agent and APM libraries are stored. The SolarWinds Observability Agent and some APM libraries may reach out to the following endpoints for updates.
|
| RUM collector |
|
Websites | To collect and send RUM data to SolarWinds Observability SaaS, your website visitors must have unrestricted access to the following domains. See Visitor access to the RUM script disabled. |
| Public API - Swagger | api.na-01.cloud.solarwinds.com
|
all areas, via public API | Used to create, read, update, or delete entities and entity data using Swagger API. See SolarWinds Observability SaaS REST API. |
| Public API - GraphQL | api.na-01.cloud.solarwinds.com/graphql
|
all areas, via public API | Used to access select DEM and database data using the GraphQL API. See SolarWinds Observability SaaS GraphQL API. |
na-02: North American Azure data center
If your organization's data is hosted on the na-02 data center, the URL you use to access SolarWinds Observability SaaS is my.na-02.cloud.solarwinds.com. All endpoints used for organizations hosted in the na-02 data center use na-02 in the URI. For any endpoint you are given that includes xx-yy in the URI, replace xx-yy with na-02. The following table shows the exact endpoints for organizations that use my.na-02.cloud.solarwinds.com.
| Endpoint purpose | URI | Monitored area | Usage details |
|---|---|---|---|
| General collector | collector.na-02.cloud.solarwinds.com
|
All | Location for the SolarWinds Observability collector endpoints. Each endpoint exists in a subdomain of the general collector. Open your firewall to allow access to all subdomains of collector.xx-yy.cloud.solarwinds.com. |
| Syslog logs collector | syslog.collector.na-02.cloud.solarwinds.com
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via syslog. |
| HTTPS logs collector | logs.collector.na-02.cloud.solarwinds.com/v1/logs
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via HTTPS. |
| APM collector | apm.collector.na-02.cloud.solarwinds.com
|
Services |
Configure your APM library to send collected data to SolarWinds Observability SaaS using this endpoint. |
| SolarWinds Observability Agent | uams.na-02.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for instrumentation and sending non-OTel data to SolarWinds Observability SaaS. |
| OTLP telemetry data ingestion |
port 443 |
Self-managed hosts, databases, network devices, and services |
Used by the SolarWinds Observability Agent, SWO K8s Collector, and SWO APM libraries to send collected telemetry and entity data to SolarWinds Observability SaaS. Depending on protocol, the endpoint should be as follows: OTLP/HTTP:
OTLP/gRPC:
See OTLP Exporter Configuration and OpenTelemetry Protocol Exporter for details on configuring OTel Collector or SDK exporting. |
| Collector binary connection for SolarWinds Observability Agent | agent-plugins.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for connection with the binaries that monitor entities and collect data. |
| Agent storage | agent-binaries.cloud.solarwinds.com
|
Self-managed hosts, databases, network devices, and services |
Location where SolarWinds Observability Agent and APM libraries are stored. The SolarWinds Observability Agent and some APM libraries may reach out to the following endpoints for updates.
|
| RUM collector |
|
Websites | To collect and send RUM data to SolarWinds Observability SaaS, your website visitors must have unrestricted access to the following domains. See Visitor access to the RUM script disabled. |
| Public API - Swagger | api.na-02.cloud.solarwinds.com
|
all areas, via public API | Used to create, read, update, or delete entities and entity data using Swagger API. See SolarWinds Observability SaaS REST API. |
| Public API - GraphQL | api.na-02.cloud.solarwinds.com/graphql
|
all areas, via public API | Used to access select DEM and database data using the GraphQL API. See SolarWinds Observability SaaS GraphQL API. |
eu-01: European (Frankfurt) AWS data center
If your organization's data is hosted on the eu-01 data center, the URL you use to access SolarWinds Observability SaaS is my.eu-01.cloud.solarwinds.com. All endpoints used for organizations hosted in the eu-01 data center use eu-01 in the URI. For any endpoint you are given that includes xx-yy in the URI, replace xx-yy with eu-01. The following table shows the exact endpoints for organizations that use my.eu-01.cloud.solarwinds.com.
| Endpoint purpose | URI | Monitored area | Usage details |
|---|---|---|---|
| General collector | collector.eu-01.cloud.solarwinds.com
|
All | Location for the SolarWinds Observability collector endpoints. Each endpoint exists in a subdomain of the general collector. Open your firewall to allow access to all subdomains of collector.xx-yy.cloud.solarwinds.com. |
| Syslog logs collector | syslog.collector.eu-01.cloud.solarwinds.com
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via syslog. |
| HTTPS logs collector | logs.collector.eu-01.cloud.solarwinds.com/v1/logs
|
Logs | Use this endpoint to send logs to SolarWinds Observability SaaS via HTTPS. |
| APM collector | apm.collector.eu-01.cloud.solarwinds.com
|
Services |
Configure your APM library to send collected data to SolarWinds Observability SaaS using this endpoint. The URI |
| SolarWinds Observability Agent | uams.eu-01.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for instrumentation and sending non-OTel data to SolarWinds Observability SaaS. |
| OTLP telemetry data ingestion |
port 443 |
Self-managed hosts, databases, network devices, and services |
Used by the SolarWinds Observability Agent, SWO K8s Collector, and SWO APM libraries to send collected telemetry and entity data to SolarWinds Observability SaaS. Depending on protocol, the endpoint should be as follows: OTLP/HTTP:
OTLP/gRPC:
See OTLP Exporter Configuration and OpenTelemetry Protocol Exporter for details on configuring OTel Collector or SDK exporting. |
| Collector binary connection for SolarWinds Observability Agent | agent-plugins.cloud.solarwinds.com
|
Self-managed hosts, databases, and network devices | Used by the SolarWinds Observability Agent for connection with the binaries that monitor entities and collect data. |
| Agent storage | agent-binaries.cloud.solarwinds.com
|
Self-managed hosts, databases, network devices, and services |
Location where SolarWinds Observability Agent and APM libraries are stored. The SolarWinds Observability Agent and some APM libraries may reach out to the following endpoints for updates.
|
| RUM collector |
|
Websites | To collect and send RUM data to SolarWinds Observability SaaS, your website visitors must have unrestricted access to the following domains. See Visitor access to the RUM script disabled. |
| Public API - Swagger | api.eu-01.cloud.solarwinds.com
|
all areas, via public API | Used to create, read, update, or delete entities and entity data using Swagger API. See SolarWinds Observability SaaS REST API. |
| Public API - GraphQL | api.eu-01.cloud.solarwinds.com/graphql
|
all areas, via public API | Used to access select DEM and database data using the GraphQL API. See SolarWinds Observability SaaS GraphQL API. |
Public IP addresses used by SolarWinds Observability SaaS per data center
Static addresses per data center
| Data Center | Collector/API Endpoints |
|---|---|
| NA-01 |
18.218.62.74/32 3.140.28.6/32 3.136.235.39/32 3.135.141.14/32 3.129.1.189/32 3.19.126.102/32 |
| NA-02 | 4.156.144.188/30 |
| EU-01 |
52.58.44.37/32 18.198.140.84/32 18.158.219.227/32 18.158.205.190/32 3.73.109.223/32 3.64.66.148/32 |
Synthetic probe IP addresses (DEM)
To see the list of synthetic probe server IP addresses, click Digital Experience > Probes in SolarWinds Observability SaaS. See Probe servers and associated IP addresses.