Type to search.

Proxy issues with EDOT Java SDK

Serverless Observability

Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Stack

The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

EDOT Java

The Elastic Distribution of OpenTelemetry (EDOT) Java SDK collects performance metrics, traces, and logs in OpenTelemetry format, and sends them to Elastic Observability.

Availability

  • Generally available

    This functionality is generally available and ready for production usage.

This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.

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. For general proxy configuration guidance, refer to Proxy settings for EDOT SDKs. For connectivity troubleshooting, refer to Connectivity issues.

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:

Shell 
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:

Shell 
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