Files
zooqueen 2483819907 mod: finish the zap 1.28 bump so every module resolves again
A dependency bump reached the go.sum files but not the go.mod files: 27
modules still required go.uber.org/zap v1.27.1 while their go.sum carried
only v1.28.0. Go then refused to build them at all — 43 modules answered
`go list ./...` with "updates to go.mod needed" or "missing go.sum entry".

They went unnoticed because every one of them sorts after cmd/otelcorecol,
and gotest walks the modules in sorted order and stops at the first error,
so the walk never reached them. Adding the missing sums to the four modules
before that point moves the wall without removing it.

Ran the tree's own tidy in every module, pinning each module's existing go
directive so the local toolchain cannot raise it. cmd/otelcorecol is
generated and carries a DO-NOT-EDIT header, so its result was checked
against `make genotelcorecol`: byte-identical, go.mod and go.sum both.

The rest is the convergence that bump implied — zap 1.27.1 -> 1.28.0, otel
1.40 -> 1.45, grpc 1.79.1 -> 1.80.0 and the x/ packages that follow them.
Two requirements were missing outright (hashicorp/golang-lru/v2,
go.yaml.in/yaml/v2) and configgrpc gained the root collector module it
already replaces locally. mostynb/go-grpc-compression leaves the graph; no
.go file imports it.

go list ./... is clean in all 118 modules and no go directive moved.
2026-08-12 21:04:37 -07:00
..

OTLP HTTP Exporter

Status
Stability alpha: profiles
stable: traces, metrics, logs
Distributions core, contrib, k8s, otlp
Issues Open issues Closed issues

The otlp_http exporter sends logs, metrics, profiles and traces via HTTP using OTLP format.

The otlphttp deprecated alias exists for the component name. It will be removed in a future version. If you use the deprecated alias otlphttp in your configuration, change it to otlp_http.

The following settings are required:

  • endpoint (no default): The target base URL to send data to (e.g.: https://example.com:4318). To send each signal a corresponding path will be added to this base URL, i.e. for traces "/v1/traces" will appended, for metrics "/v1/metrics" will be appended, for logs "/v1/logs" will be appended.

The following settings can be optionally configured:

  • traces_endpoint (no default): The target URL to send trace data to (e.g.: https://example.com:4318/v1/traces). If this setting is present the endpoint setting is ignored for traces.
  • metrics_endpoint (no default): The target URL to send metric data to (e.g.: https://example.com:4318/v1/metrics). If this setting is present the endpoint setting is ignored for metrics.
  • logs_endpoint (no default): The target URL to send log data to (e.g.: https://example.com:4318/v1/logs).
  • profiles_endpoint (no default): The target URL to send profile data to (e.g.: https://example.com:4318/v1development/profiles). If this setting is present the endpoint setting is ignored for logs.
  • tls: see TLS Configuration Settings for the full set of available options.
  • timeout (default = 30s): HTTP request time limit. For details see https://golang.org/pkg/net/http/#Client
  • read_buffer_size (default = 0): ReadBufferSize for HTTP client.
  • write_buffer_size (default = 512 * 1024): WriteBufferSize for HTTP client.
  • encoding (default = proto): The encoding to use for the messages (valid options: proto, json)
  • retry_on_failure: see Retry on Failure for the full set of available options.
  • sending_queue: see Sending Queue for the full set of available options.

Example:

exporters:
  otlp_http:
    endpoint: https://example.com:4318

By default gzip compression is enabled. See compression comparison for details benchmark information. To disable, configure as follows:

exporters:
  otlp_http:
    ...
    compression: none

By default proto encoding is used, to change the content encoding of the message configure it as follows:

exporters:
  otlp_http:
    ...
    encoding: json

The full list of settings exposed for this exporter are documented here with detailed sample configurations here.