[vitorvasc]

• I have read and followed the Contributing docs, especially the "First-time contributing?" section.
• This PR has content that I did not fully write myself.
  • I used AI and I have read and followed the Generative AI Contribution Policy.
• I have the experience and knowledge necessary to understand, review, and validate all content in this PR.¹

---

Contributes to #11557.

• Add the env-var-note.md include, the OTLP/gRPC endpoint note and the W3C Baggage header paragraph
• Translate the new metrics-specific configuration section
• Fix the pre-existing misplaced and untranslated "Configurações de protocolo" heading
• Bump default_lang_commit and drop drifted_from_default

> check:i18n
> node scripts/i18n/drift.mjs diff content/pt/docs/languages/sdk-configuration/otlp-exporter.md
# content/pt/docs/languages/sdk-configuration/otlp-exporter.md: drifted from 99bddc40d1e15c5f33311b736b92fa227f04664a
diff --git a/content/en/docs/languages/sdk-configuration/otlp-exporter.md b/content/en/docs/languages/sdk-configuration/otlp-exporter.md
index 004948744..0ddf82dc3 100644
--- a/content/en/docs/languages/sdk-configuration/otlp-exporter.md
+++ b/content/en/docs/languages/sdk-configuration/otlp-exporter.md
@@ -3,8 +3,11 @@ title: OTLP Exporter Configuration
 linkTitle: OTLP Exporter
 weight: 20
 aliases: [otlp-exporter-configuration]
+cSpell:ignore: lowmemory
 ---
 
+{{% include "env-var-note.md" %}}
+
 ## Endpoint Configuration
 
 The following environment variables let you configure an OTLP/gRPC or OTLP/HTTP
@@ -34,6 +37,11 @@ and logs, the following URLs are constructed from the example above:
 - Metrics: `"http://my-api-endpoint/v1/metrics"`
 - Logs: `"http://my-api-endpoint/v1/logs"`
 
+For OTLP/gRPC, endpoint values are gRPC targets. Do not append OTLP/HTTP signal
+paths such as `/v1/traces`, `/v1/metrics`, or `/v1/logs` to gRPC endpoint
+values; gRPC exporters use the OTLP protobuf service method for each signal
+after connecting to the configured target.
+
 ### `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT`
 
 Endpoint URL for trace data only, with an optionally-specified port number.
@@ -106,6 +114,14 @@ ends with `v1/profiles` when using OTLP/HTTP.
 The following environment variables let you configure additional headers as a
 list of key-value pairs to add in outgoing gRPC or HTTP requests.
 
+Headers are represented in a format matching to the
+[W3C Baggage](https://www.w3.org/TR/baggage/#header-content), for example
+`key1=value1,key2=value2`. Semi-colon delimited
+[metadata](https://www.w3.org/TR/baggage/#property) is not supported. For more
+details, see
+[Specifying headers via environment variables](/docs/specs/otel/protocol/exporter/#specifying-headers-via-environment-variables)
+in the protocol specification.
+
 ### `OTEL_EXPORTER_OTLP_HEADERS`
 
 A list of headers to apply to all outgoing data (traces, metrics, and logs).
@@ -276,3 +292,42 @@ Valid values are:
 - `grpc` to use OTLP/gRPC
 - `http/protobuf` to use OTLP/HTTP + protobuf
 - `http/json` to use OTLP/HTTP + JSON
+
+## Metrics-specific configuration
+
+The following environment variables configure exporter options that are
+exclusive to metrics.
+
+### `OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE`
+
+Configures the exporter's aggregation temporality preference on the basis of
+instrument kind.
+
+**Default value:** `cumulative`
+
+**Example:** `export OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE=delta`
+
+Valid values are:
+
+- `cumulative` to use cumulative aggregation temporality for all instrument
+  kinds.
+- `delta` to use delta aggregation temporality for Counter, Asynchronous
+  Counter, and Histogram, and cumulative for UpDownCounter and Asynchronous
+  UpDownCounter.
+- `lowmemory` to use delta aggregation temporality for Synchronous Counter and
+  Histogram, and cumulative for others.
+
+### `OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION`
+
+Configures the exporter's default aggregation for the Histogram instrument kind.
+
+**Default value:** `explicit_bucket_histogram`
+
+**Example:**
+`export OTEL_EXPORTER_OTLP_METRICS_DEFAULT_HISTOGRAM_AGGREGATION=base2_exponential_bucket_histogram`
+
+Valid values are:
+
+- `explicit_bucket_histogram` to use explicit bucket histogram aggregation.
+- `base2_exponential_bucket_histogram` to use base2 exponential bucket histogram
+  aggregation.

Footnotes

1. Yes, I can answer maintainer questions about the content of this PR, without using AI. ↩

[opentelemetry-pr-dashboard]

Pull request dashboard status

Waiting on reviewers · refreshed 2026-10-23 12:23 UTC

Review the latest changes.

Status above doesn't look right?

• Just replied or pushed? Anything around or after the refresh time above may not be picked up yet — give it a few minutes.
• Anything look wrong? Report it with what you expected; it helps us improve the dashboard.