Open source


otelcol.exporter.otlphttp accepts telemetry data from other otelcol components and writes them over the network using the OTLP HTTP protocol.


otelcol.exporter.otlphttp is a wrapper over the upstream OpenTelemetry Collector otlphttp exporter. Bug reports or feature requests will be redirected to the upstream repository, if necessary.

You can specify multiple otelcol.exporter.otlphttp components by giving them different labels.


otelcol.exporter.otlphttp "LABEL" {
  client {
    endpoint = "HOST:PORT"


otelcol.exporter.otlphttp supports the following arguments:

metrics_endpointstringThe endpoint to send metrics to.client.endpoint + "/v1/metrics"no
logs_endpointstringThe endpoint to send logs to.client.endpoint + "/v1/logs"no
traces_endpointstringThe endpoint to send traces to.client.endpoint + "/v1/traces"no

The default value depends on the endpoint field set in the required client block. If set, these arguments override the client.endpoint field for the corresponding signal.


The following blocks are supported inside the definition of otelcol.exporter.otlphttp:

clientclientConfigures the HTTP server to send telemetry data to.yes
client > tlstlsConfigures TLS for the HTTP
sending_queuesending_queueConfigures batching of data before
retry_on_failureretry_on_failureConfigures retry mechanism for failed
debug_metricsdebug_metricsConfigures the metrics that this component generates to monitor its

The > symbol indicates deeper levels of nesting. For example, client > tls refers to a tls block defined inside a client block.

client block

The client block configures the HTTP client used by the component.

The following arguments are supported:

endpointstringThe target URL to send telemetry data to.yes
encodingstringThe encoding to use for messages. Should be either "proto" or "json"."proto"no
read_buffer_sizestringSize of the read buffer the HTTP client uses for reading server responses.0no
write_buffer_sizestringSize of the write buffer the HTTP client uses for writing requests."512KiB"no
timeoutdurationTime to wait before marking a request as failed."30s"no
headersmap(string)Additional headers to send with the request.{}no
compressionstringCompression mechanism to use for requests."gzip"no
max_idle_connsintLimits the number of idle HTTP connections the client can keep open.100no
max_idle_conns_per_hostintLimits the number of idle HTTP connections the host can keep open.0no
max_conns_per_hostintLimits the total (dialing,active, and idle) number of connections per host.0no
idle_conn_timeoutdurationTime to wait before an idle connection closes itself."90s"no
disable_keep_alivesboolDisable HTTP keep-alive.falseno
http2_read_idle_timeoutdurationTimeout after which a health check using ping frame will be carried out if no frame is received on the connection.0sno
http2_ping_timeoutdurationTimeout after which the connection will be closed if a response to Ping isn’t received.15sno
authcapsule(otelcol.Handler)Handler from an otelcol.auth component to use for authenticating

When setting headers, note that:

  • Certain headers such as Content-Length and Connection are automatically written when needed and values in headers may be ignored.
  • The Host header is automatically derived from the endpoint value. However, this automatic assignment can be overridden by explicitly setting a Host header in headers.

Setting disable_keep_alives to true will result in significant overhead establishing a new HTTP or HTTPS connection for every request. Before enabling this option, consider whether changes to idle connection settings can achieve your goal.

If http2_ping_timeout is unset or set to 0s, it will default to 15s.

If http2_read_idle_timeout is unset or set to 0s, then no health check will be performed.

By default, requests are compressed with Gzip. The compression argument controls which compression mechanism to use. Supported strings are:

  • "gzip"
  • "zlib"
  • "deflate"
  • "snappy"
  • "zstd"

If you set compression to "none" or an empty string "", the requests aren’t compressed.

tls block

The tls block configures TLS settings used for the connection to the HTTP server.

The following arguments are supported:

ca_filestringPath to the CA
ca_pemstringCA PEM-encoded text to validate the server
cert_filestringPath to the TLS
cert_pemstringCertificate PEM-encoded text for client
insecure_skip_verifybooleanIgnores insecure server TLS
include_system_ca_certs_poolbooleanWhether to load the system certificate authorities pool alongside the certificate authority.falseno
insecurebooleanDisables TLS when connecting to the configured
key_filestringPath to the TLS certificate
key_pemsecretKey PEM-encoded text for client
max_versionstringMaximum acceptable TLS version for connections."TLS 1.3"no
min_versionstringMinimum acceptable TLS version for connections."TLS 1.2"no
cipher_suiteslist(string)A list of TLS cipher suites that the TLS transport can use.[]no
reload_intervaldurationThe duration after which the certificate is reloaded."0s"no
server_namestringVerifies the hostname of server certificates when

If the server doesn’t support TLS, you must set the insecure argument to true.

To disable tls for connections to the server, set the insecure argument to true.

If reload_interval is set to "0s", the certificate never reloaded.

The following pairs of arguments are mutually exclusive and can’t both be set simultaneously:

  • ca_pem and ca_file
  • cert_pem and cert_file
  • key_pem and key_file

If cipher_suites is left blank, a safe default list is used. See the Go TLS documentation for a list of supported cipher suites.

sending_queue block

The sending_queue block configures an in-memory buffer of batches before data is sent to the HTTP server.

The following arguments are supported:

enabledbooleanEnables an in-memory buffer before sending data to the client.trueno
num_consumersnumberNumber of readers to send batches written to the queue in parallel.10no
queue_sizenumberMaximum number of unwritten batches allowed in the queue at the same time.1000no

When enabled is true, data is first written to an in-memory buffer before sending it to the configured server. Batches sent to the component’s input exported field are added to the buffer as long as the number of unsent batches doesn’t exceed the configured queue_size.

queue_size determines how long an endpoint outage is tolerated. Assuming 100 requests/second, the default queue size 1000 provides about 10 seconds of outage tolerance. To calculate the correct value for queue_size, multiply the average number of outgoing requests per second by the time in seconds that outages are tolerated. A very high value can cause Out Of Memory (OOM) kills.

The num_consumers argument controls how many readers read from the buffer and send data in parallel. Larger values of num_consumers allow data to be sent more quickly at the expense of increased network traffic.

retry_on_failure block

The retry_on_failure block configures how failed requests to the HTTP server are retried.

The following arguments are supported:

enabledbooleanEnables retrying failed requests.trueno
initial_intervaldurationInitial time to wait before retrying a failed request."5s"no
max_elapsed_timedurationMaximum time to wait before discarding a failed batch."5m"no
max_intervaldurationMaximum time to wait between retries."30s"no
multipliernumberFactor to grow wait time before retrying.1.5no
randomization_factornumberFactor to randomize wait time before retrying.0.5no

When enabled is true, failed batches are retried after a given interval. The initial_interval argument specifies how long to wait before the first retry attempt. If requests continue to fail, the time to wait before retrying increases by the factor specified by the multiplier argument, which must be greater than 1.0. The max_interval argument specifies the upper bound of how long to wait between retries.

The randomization_factor argument is useful for adding jitter between retrying Alloy instances. If randomization_factor is greater than 0, the wait time before retries is multiplied by a random factor in the range [ I - randomization_factor * I, I + randomization_factor * I], where I is the current interval.

If a batch hasn’t been sent successfully, it is discarded after the time specified by max_elapsed_time elapses. If max_elapsed_time is set to "0s", failed requests are retried forever until they succeed.

debug_metrics block

The debug_metrics block configures the metrics that this component generates to monitor its state.

The following arguments are supported:

disable_high_cardinality_metricsbooleanWhether to disable certain high cardinality metrics.trueno
levelstringControls the level of detail for metrics emitted by the wrapped collector."detailed"no

disable_high_cardinality_metrics is the Grafana Alloy equivalent to the telemetry.disableHighCardinalityMetrics feature gate in the OpenTelemetry Collector. It removes attributes that could cause high cardinality metrics. For example, attributes with IP addresses and port numbers in metrics about HTTP and gRPC connections are removed.


If configured, disable_high_cardinality_metrics only applies to otelcol.exporter.* and otelcol.receiver.* components.

level is the Alloy equivalent to the telemetry.metrics.level feature gate in the OpenTelemetry Collector. Possible values are "none", "basic", "normal" and "detailed".

Exported fields

The following fields are exported and can be referenced by other components:

inputotelcol.ConsumerA value that other components can use to send telemetry data to.

input accepts otelcol.Consumer data for any telemetry signal (metrics, logs, or traces).

Component health

otelcol.exporter.otlphttp is only reported as unhealthy if given an invalid configuration.

Debug information

otelcol.exporter.otlphttp doesn’t expose any component-specific debug information.


This example creates an exporter to send data to a locally running Grafana Tempo without TLS:

otelcol.exporter.otlphttp "tempo" {
    client {
        endpoint = "http://tempo:4317"
        tls {
            insecure             = true
            insecure_skip_verify = true

Compatible components

otelcol.exporter.otlphttp has exports that can be consumed by the following components:


Connecting some components may not be sensible or components may require further configuration to make the connection work correctly. Refer to the linked documentation for more details.