otelcol.exporter.otlphttp.md

---

title: otelcol.exporter.otlphttp

---

otelcol.exporter.otlphttp

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

NOTE: 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.

Multiple otelcol.exporter.otlphttp components can be specified by giving them different labels.

Usage

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

Arguments

otelcol.exporter.otlphttp supports the following arguments:

Name	Type	Description	Default	Required
metrics_endpoint	string	The endpoint to send metrics to.	client.endpoint + "/v1/metrics"	no
logs_endpoint	string	The endpoint to send logs to.	client.endpoint + "/v1/logs"	no
traces_endpoint	string	The 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.

Blocks

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

Hierarchy	Block	Description	Required
client	client	Configures the HTTP server to send telemetry data to.	yes
client > tls	tls	Configures TLS for the HTTP client.	no
queue	queue	Configures batching of data before sending.	no
retry	retry	Configures retry mechanism for failed requests.	no

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:

Name	Type	Description	Default	Required
endpoint	string	host:port to send telemetry data to.		yes
read_buffer_size	string	Size of the read buffer the HTTP client uses for reading server responses.	0	no
write_buffer_size	string	Size of the write buffer the HTTP client uses for writing requests.	"512KiB"	no
timeout	duration	Time to wait before marking a request as failed.	"30s"	no
headers	map(string)	Additional headers to send with the request.	{}	no
compression	string	Compression mechanism to use for requests.	"gzip"	no
max_idle_conns	int	Limits the number of idle HTTP connections the client can keep open.	100	no
max_idle_conns_per_host	int	Limits the number of idle HTTP connections the host can keep open.	0	no
max_conns_per_host	int	Limits the total (dialing,active, and idle) number of connections per host.	0	no
idle_conn_timeout	duration	Time to wait before an idle connection closes itself.	"90s"	no
auth	capsule(otelcol.Handler)	Handler from an otelcol.auth component to use for authenticating requests.		no

{{< docs/shared lookup="flow/reference/components/otelcol-compression-field.md" source="agent" >}}

tls block

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

{{< docs/shared lookup="flow/reference/components/otelcol-tls-config-block.md" source="agent" >}}

queue block

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

{{< docs/shared lookup="flow/reference/components/otelcol-queue-block.md" source="agent" >}}

retry block

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

{{< docs/shared lookup="flow/reference/components/otelcol-retry-block.md" source="agent" >}}

Exported fields

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

Name	Type	Description
input	otelcol.Consumer	A 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 does not expose any component-specific debug information.

Example

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

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