If your application runs in an environment that restricts outbound network connections and whitelisting IPs is not possible, our agents can be configured to use an explicit HTTP proxy server to forward connections to the AppOptics backend
collector.appoptics.com (aka the collector).
The connection between the agent and collector is encrypted via TLS, so the proxy needs to support tunneling HTTPS traffic via HTTP CONNECT. Examples of such proxies include Squid, HAProxy and Apache with mod_proxy_connect. The agents support connecting to the proxy with no authentication, or with Basic authentication.
Note that proxy configuration can be set globally for the application process using environment variables or runtime properties, or set specifically for just the agent outbound connections. If set in both places, the agent-specific configuration takes precedence.
See the links below on how to set proxy configuration for each agent:
- .NET (agent version 4.0.0 and up)
- Go (agent version 1.12.0 and up)
- Java (agent version 6.16.0 and up)
- PHP (agent version 4.0.0 and up)
- Python (agent version 4.2.0 and up)
When the APM Integrated Experience is enabled, AppOptics shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate AppOptics and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.