Documentation forSolarWinds Observability

Proxy configuration

If your application runs in an environment that restricts outbound network connections and your firewall and access control settings restrict communication with the SolarWinds APM collector, our libraries can be configured to use an explicit HTTP proxy server to forward connections to the SolarWinds APM collector

The connection between the library and collector is encrypted via TLS, so the proxy needs to support tunneling HTTPS traffic via HTTP CONNECT. Examples of supported proxies include Squid, HAProxy and Apache with mod_proxy_connect. The libraries support connecting to the proxy with no authentication or with Basic authentication.

Proxy configuration can either be set globally for the application process using environment variables or runtime properties, or set specifically for just the library outbound connections. If the proxy is set in both places, the library-specific configuration takes precedence.

See the links below on how to set proxy configuration for each library: