From 438d045755c50616cb19abfb59313e2e5abcce12 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Robert=20Paj=C4=85k?= Date: Fri, 20 Oct 2023 08:28:20 +0200 Subject: [PATCH] protcol/exporter: Clarify that the env vars do not need to be implemented directly in the exporter --- specification/protocol/exporter.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md index a7d5a02fa21..744046ca230 100644 --- a/specification/protocol/exporter.md +++ b/specification/protocol/exporter.md @@ -10,7 +10,9 @@ This document specifies the configuration options available to the OpenTelemetry ## Configuration Options -The following configuration options MUST be available to configure the OTLP exporter. Each configuration option MUST be overridable by a signal specific option. +The following configuration options MUST be available to configure the OTLP exporter. +The configuration options MAY be implemented directly in the OTLP exporter, in the SDK, or in a seperate component (e.g. environment-based autoconfiguration component). +Each configuration option MUST be overridable by a signal specific option. - **Endpoint (OTLP/HTTP)**: Target URL to which the exporter is going to send spans or metrics. The endpoint MUST be a valid URL with scheme (http or https) and host, MAY contain a port, SHOULD contain a path and MUST NOT contain other parts (such as query string or fragment). A scheme of https indicates a secure connection. When using `OTEL_EXPORTER_OTLP_ENDPOINT`, exporters MUST construct per-signal URLs as [described below](#endpoint-urls-for-otlphttp). The per-signal endpoint configuration options take precedence and can be used to override this behavior (the URL is used as-is for them, without any modifications). See the [OTLP Specification][otlphttp-req] for more details. - Default: `http://localhost:4318` [1]