If your application, host, database, or integration runs in an environment that restricts outbound network connections and your firewall and access control settings restrict communication with the SolarWinds Observability endpoints, our agents, collectors, and libraries can be configured to use an explicit HTTP proxy server to forward connections to SolarWinds Observability endpoints.
SolarWinds Observability Agent proxy
For hosts, databases, and OTel integrations monitored with the SolarWinds Observability Agent, you can use the global environment variable HTTPS_PROXY to set up a proxy for the Agent. The variable is natively supported by the gprc library. For details, see Configure proxy for SolarWinds Observability Agents.
APM library proxy
For SolarWinds Observability APM libraries, the connection between the library and SolarWinds APM 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: