Type to search.

Proxy settings for EDOT SDKs

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.

Elastic Agent

Elastic Agent can run in OpenTelemetry mode to retrieve traces, metrics, and logs from your infrastructure and applications, and forward 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.

EDOT SDKs generally use the standard proxy environment variables. However, there are exceptions and limitations depending on the language and exporter type. For general connectivity troubleshooting, refer to Connectivity issues.

The Python SDK honors HTTP_PROXY and HTTPS_PROXY only when using the http/protobuf exporter.

If you use the default gRPC-based exporter, proxy settings are ignored. To enable proxy support, you can either:

  • Switch to the http/protobuf exporter, which supports standard proxy environment variables.

  • Route telemetry through a local Elastic Agent configured with proxy settings.

The Node.js SDK does not currently support HTTP_PROXY, HTTPS_PROXY, or NO_PROXY by default. You can route telemetry through an Elastic Agent.

If you're using Java SDK, you must configure Java system properties using the Java Virtual Machine (JVM). Refer to Troubleshooting Java SDK proxy issues for more information.

Other EDOT SDKs honor standard proxy environment variables with no additional setup required. For example:

Text 
export HTTP_PROXY=http://<proxy.address>:<port>
export HTTPS_PROXY=http://<proxy.address>:<port>