Loading

Proxy issues with EDOT Java SDK

Stack Serverless Observability EDOT Java

If your Java SDK sends telemetry but fails to communicate with the APM server, the issue might be due to missing or misconfigured proxy settings, which are required for outbound HTTP/S communication in some environments.

These symptoms typically indicate that your Java SDK is experiencing a proxy issue:

  • Telemetry data is not received in Elastic APM after instrumenting the app.
  • Logs show errors like Connection timed out, TLS handshake failure, or other network-related issues when connecting to Elastic APM.

Set standard Java system properties to configure proxy settings.

Configure the following JVM system properties to enable outbound HTTP/HTTPS communication through a proxy:

java \
-Dhttp.proxyHost=proxy.example.com \
-Dhttp.proxyPort=8080 \
-Dhttps.proxyHost=proxy.example.com \
-Dhttps.proxyPort=8080 \

You can test end-to-end connectivity to validate proxy routing. To confirm that your application or collector can reach the endpoint through the proxy, use curl with the --proxy option:

curl --proxy http://proxy.example.com:8080 https://example.elastic.co

If the proxy is working, you'll get a valid response. If not, common errors include:

  • Connection timed out
  • Could not resolve host
  • Proxy CONNECT aborted