OpenTelemetry Collector: Set the OTLP HTTP Exporter’s Proxy

The Collector receives telemetry from applications, then makes a separate outbound connection to its configured backend. Put the proxy on that outbound HTTP exporter:

exporters:
  otlp_http/proxied:
    endpoint: https://telemetry.example:4318
    proxy_url: http://proxy.example:8080

service:
  pipelines:
    traces:
      receivers: [otlp]
      exporters: [otlp_http/proxied]

Merge this fragment into the existing configuration. It assumes the otlp receiver is already defined and retains the deployment’s required processors and other pipeline settings. Defining an exporter without referencing it from the relevant pipeline does not send data through it.

The endpoint remains the telemetry backend’s base URL. The OTLP HTTP exporter adds the signal path, such as /v1/traces, unless a signal-specific endpoint overrides it. proxy_url identifies the intermediary. For a non-sensitive test backend that is public and permits a public-proxy route, an address from the HTTP proxy list can fill that URL; confirm access to the backend’s actual host and port.

Current upstream documentation names this component otlp_http and describes otlphttp as a deprecated alias. Older distributions can use the older component name; keep both the exporter definition and pipeline reference consistent with the installed distribution.

This is HTTP client configuration. An OTLP gRPC exporter has another transport, and an application’s own proxy environment does not automatically enter the Collector’s container or service process. Likewise, configuring the receiver addresses incoming traffic rather than this backend connection.

Retain the backend’s TLS verification and required service authentication. A proxy 407 and a backend rejection identify different accounts and stages.