Documentation forSolarWinds Observability SaaS

Private probe requirements

Hardware and Software requirements

To deploy a private probe, your system must meet baseline requirements. Each private probe requires the following minimum resources. These values represent the base overhead for running the probe container itself.

Baseline requirements per private probe instance

  • CPU: 20 mCores

  • Memory: 100 MiB

These requirements scale depending on the number of parallel checks (checks that run at the same time) you plan to run.

SolarWinds recommends an additional 100 MiB memory allocation for each parallel check execution for the in-memory result buffer for maximum private probe performance. You should monitor your resource usage to make sure you have enough memory to execute the checks on your private probe.

Additional requirements per parallel check execution

For each additional check execution running in parallel, the following resources are required.

  • CPU: 30 mCores

  • Memory: 30 MiB

  • Buffer Memory (recommended): 100 MiB (for in-memory result buffering)

For more information about how checks are counted within SolarWinds Observability Digital Experience, see Subscription.

Requirements example

Consider the following example. You execute 1000 checks every 60 seconds. If your probe location performs 1000 checks every 60 seconds, you can calculate the number of parallel check executions as:

1000/60≈16.61000

This rounds up to 17 parallel check executions. In this scenario, our resources are calculated as follows.

Resource Calculation

  • CPU:

    • Base: 20 mCores

    • Per check: 30 mCores × 17 = 510 mCores

    • Total: ~530 mCores, rounded up to 1 vCPU

  • Memory:

    • Base: 100 MiB

    • Per check: 30 MiB × 17 = 510 MiB

    • Buffer: 100 MiB × 17 = 1.7 GiB

    • Total: ~2.31 GiB, rounded up to 3 GiB

Summary of Recommended Resources for 17 Parallel Executions:

Resource Calculation Recommended Total
CPU 20 + (30 × 17) = 530 mCores 1 vCPU
Memory 100 + (30 × 17) + (100 × 17) = 2.31 GiB 3 GiB

Private probe endpoints

The private probe agent requires access to the following SolarWinds Observability services.

URLs

The following URLs are used by the private probe to retrieve check schedules and submit check results to the Synthetics-Collector service through gRPC protocol.

  • synthetics.collector.na-01.cloud.solarwinds.com

  • synthetics.collector.na-02.cloud.solarwinds.com

  • synthetics.collector.eu-01.cloud.solarwinds.com

  • synthetics.collector.ap-01.cloud.solarwinds.com

See the endpoint system requirements to determine which endpoint is correct for your organization.

This process uses port 443 and is only an outbound communication.

Additional services

The private probe exposes the following services.

Service Port Endpoint Description
Prometheus 9091 /metrics It provides access to the private probe metrics. It needs to be exposed in docker. It allows only inbound connections.
Healthcheck 8080

/readyz

/livez

 Serves the private probe service health status. It needs to be exposed in docker. It allows only inbound connections.