Merge branch 'main' into event_space_namespace_update

CHANGELOG.md

@@ -11,13 +11,15 @@ release.
 
 ### Traces
 
-- Add a new AddLink() operation to Span (experimental).
-  ([#3678](https://github.com/open-telemetry/opentelemetry-specification/pull/3678))
+- Add definition for standard output span exporter.
+  ([#3740](https://github.com/open-telemetry/opentelemetry-specification/pull/3740))
 
 ### Metrics
 
 ### Logs
 
+- Add definition for standard output log record exporter.
+  ([#3741](https://github.com/open-telemetry/opentelemetry-specification/pull/3741))
 - BREAKING: Remove `event.domain` from log event attributes.
   ([#473](https://github.com/open-telemetry/semantic-conventions/pull/473))
 - BREAKING: Change `event.name` definition to include `namespace`.
@@ -27,12 +29,47 @@ release.
 
 ### OpenTelemetry Protocol
 
+### Compatibility
+
+### SDK Configuration
+
+### Common
+
+### Supplementary Guidelines
+
+## v1.27.0 (2023-11-08)
+
+### Context
+
+- No changes.
+
+### Traces
+
+- Add a new AddLink() operation to Span (experimental).
+  ([#3678](https://github.com/open-telemetry/opentelemetry-specification/pull/3678))
+
+### Metrics
+
+- No changes.
+
+### Logs
+
+- No changes.
+
+### Resource
+
+- No changes.
+
+### OpenTelemetry Protocol
+
 - New exporter implementations do not need to support
   `OTEL_EXPORTER_OTLP_SPAN_INSECURE` and `OTEL_EXPORTER_OTLP_METRIC_INSECURE`.
   ([#3719](https://github.com/open-telemetry/opentelemetry-specification/pull/3719))
 
 ### Compatibility
 
+- No changes.
+
 ### SDK Configuration
 
 - Define file configuration parse and create operations.
@@ -47,6 +84,8 @@ release.
 
 ### Supplementary Guidelines
 
+- No changes.
+
 ## v1.26.0 (2023-10-10)
 
 ### Context

specification/baggage/api.md

@@ -146,7 +146,7 @@ reasons.
 
 The API layer or an extension package MUST include the following `Propagator`s:
 
-* A `TextMapPropagator` implementing the [W3C Baggage Specification](https://w3c.github.io/baggage).
+* A `TextMapPropagator` implementing the [W3C Baggage Specification](https://www.w3.org/TR/baggage).
 
 See [Propagators Distribution](../context/api-propagators.md#propagators-distribution)
 for how propagators are to be distributed.

specification/context/api-propagators.md

@@ -333,9 +333,9 @@ Required parameters:
 The official list of propagators that MUST be maintained by the OpenTelemetry
 organization and MUST be distributed as OpenTelemetry extension packages:
 
-* [W3C TraceContext](https://www.w3.org/TR/trace-context/). MAY alternatively
+* [W3C TraceContext](https://www.w3.org/TR/trace-context). MAY alternatively
   be distributed as part of the OpenTelemetry API.
-* [W3C Baggage](https://w3c.github.io/baggage). MAY alternatively
+* [W3C Baggage](https://www.w3.org/TR/baggage). MAY alternatively
   be distributed as part of the OpenTelemetry API.
 * [B3](https://github.com/openzipkin/b3-propagation).
 * [Jaeger](https://www.jaegertracing.io/docs/latest/client-libraries/#propagation-format).

specification/logs/README.md

@@ -284,7 +284,7 @@ auto-instrumenting solutions that modify trace logging libraries used by the
 application to automatically output the trace context such as the trace id or
 span id with every log statement. The trace context can be automatically
 extracted from incoming requests if standard compliant request propagation is
-used, e.g. via [W3C TraceContext](https://w3c.github.io/trace-context/). In
+used, e.g. via [W3C TraceContext](https://www.w3.org/TR/trace-context). In
 addition, the requests outgoing from the application may be injected with the
 same trace context data, thus resulting in context propagation through the
 application and creating an opportunity to have full trace context in logs

specification/logs/sdk_exporters/stdout.md

@@ -0,0 +1,22 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: Stdout
+--->
+
+# OpenTelemetry LogRecord Exporter - Standard output
+
+**Status**: [Experimental](../../document-status.md)
+
+"Standard output" LogRecord Exporter is a [LogRecord
+Exporter](../sdk.md#logrecordexporter) which outputs the logs to
+stdout/console.
+
+[OpenTelemetry SDK](../../overview.md#sdk) authors MAY choose the best idiomatic
+name for their language. For example, ConsoleExporter, StdoutExporter,
+StreamExporter, etc.
+
+If a language provides a mechanism to automatically configure a
+[LogRecordProcessor](../sdk.md#logrecordprocessor) to pair with the associated
+exporter (e.g., using the [`OTEL_LOGS_EXPORTER` environment
+variable](../../configuration/sdk-environment-variables.md#exporter-selection)), by
+default the standard output exporter SHOULD be paired with a [simple
+processor](../sdk.md#simple-processor).

specification/protocol/exporter.md

@@ -13,11 +13,11 @@ This document specifies the configuration options available to the OpenTelemetry
 The following configuration options MUST be available to configure the OTLP exporter.
 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.
+- **Endpoint (OTLP/HTTP)**: Target URL to which the exporter is going to send spans, metrics, or logs. 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]
   - Env vars: `OTEL_EXPORTER_OTLP_ENDPOINT` `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT` `OTEL_EXPORTER_OTLP_LOGS_ENDPOINT`
 
-- **Endpoint (OTLP/gRPC)**: Target to which the exporter is going to send spans or metrics. The endpoint SHOULD accept any form allowed by the underlying gRPC client implementation. Additionally, the endpoint MUST accept a URL with a scheme of either `http` or `https`. A scheme of `https` indicates a secure connection and takes precedence over the `insecure` configuration setting. A scheme of `http` indicates an insecure connection and takes precedence over the `insecure` configuration setting. If the gRPC client implementation does not support an endpoint with a scheme of `http` or `https` then the endpoint SHOULD be transformed to the most sensible format for that implementation.
+- **Endpoint (OTLP/gRPC)**: Target to which the exporter is going to send spans, metrics, or logs. The endpoint SHOULD accept any form allowed by the underlying gRPC client implementation. Additionally, the endpoint MUST accept a URL with a scheme of either `http` or `https`. A scheme of `https` indicates a secure connection and takes precedence over the `insecure` configuration setting. A scheme of `http` indicates an insecure connection and takes precedence over the `insecure` configuration setting. If the gRPC client implementation does not support an endpoint with a scheme of `http` or `https` then the endpoint SHOULD be transformed to the most sensible format for that implementation.
   - Default: `http://localhost:4317` [1]
   - Env vars: `OTEL_EXPORTER_OTLP_ENDPOINT` `OTEL_EXPORTER_OTLP_TRACES_ENDPOINT` `OTEL_EXPORTER_OTLP_METRICS_ENDPOINT` `OTEL_EXPORTER_OTLP_LOGS_ENDPOINT`
 
@@ -138,7 +138,7 @@ relative to `http://collector:4318/mycollector/`.
 
 ### Specify Protocol
 
-The `OTEL_EXPORTER_OTLP_PROTOCOL`, `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL`, and `OTEL_EXPORTER_OTLP_METRICS_PROTOCOL` environment variables specify the OTLP transport protocol. Supported values:
+The `OTEL_EXPORTER_OTLP_PROTOCOL`, `OTEL_EXPORTER_OTLP_TRACES_PROTOCOL`, `OTEL_EXPORTER_OTLP_METRICS_PROTOCOL` and `OTEL_EXPORTER_OTLP_LOGS_PROTOCOL` environment variables specify the OTLP transport protocol. Supported values:
 
 - `grpc` for protobuf-encoded data using gRPC wire format over HTTP/2 connection
 - `http/protobuf` for protobuf-encoded data over HTTP connection
@@ -155,7 +155,7 @@ release).
 
 ### Specifying headers via environment variables
 
-The `OTEL_EXPORTER_OTLP_HEADERS`, `OTEL_EXPORTER_OTLP_TRACES_HEADERS`, `OTEL_EXPORTER_OTLP_METRICS_HEADERS` environment variables will contain a list of key value pairs, and these are expected to be represented in a format matching to the [W3C Correlation-Context](https://github.com/w3c/baggage/blob/master/baggage/HTTP_HEADER_FORMAT.md), except that additional semi-colon delimited metadata is not supported, i.e.: key1=value1,key2=value2. All attribute values MUST be considered strings.
+The `OTEL_EXPORTER_OTLP_HEADERS`, `OTEL_EXPORTER_OTLP_TRACES_HEADERS`, `OTEL_EXPORTER_OTLP_METRICS_HEADERS`, `OTEL_EXPORTER_OTLP_LOGS_HEADERS` environment variables will contain a list of key value pairs, and these are expected to be represented in a format matching to the [W3C Baggage](https://www.w3.org/TR/baggage/#header-content), except that additional semi-colon delimited metadata is not supported, i.e.: key1=value1,key2=value2. All attribute values MUST be considered strings.
 
 ## Retry
 

specification/resource/sdk.md

@@ -137,7 +137,7 @@ has higher priority.
 
 The `OTEL_RESOURCE_ATTRIBUTES` environment variable will contain of a list of
 key value pairs, and these are expected to be represented in a format matching
-to the [W3C Baggage](https://w3c.github.io/baggage), except that additional
+to the [W3C Baggage](https://www.w3.org/TR/baggage/#header-content), except that additional
 semi-colon delimited metadata is not supported, i.e.: `key1=value1,key2=value2`.
 All attribute values MUST be considered strings and characters outside the
 `baggage-octet` range MUST be percent-encoded.

specification/trace/sdk_exporters/stdout.md

@@ -0,0 +1,22 @@
+<!--- Hugo front matter used to generate the website version of this page:
+linkTitle: Stdout
+--->
+
+# OpenTelemetry Span Exporter - Standard output
+
+**Status**: [Stable](../../document-status.md)
+
+"Standard output" Span Exporter is a [Span
+Exporter](../sdk.md#span-exporter) which outputs the spans to
+stdout/console.
+
+[OpenTelemetry SDK](../../overview.md#sdk) authors MAY choose the best idiomatic
+name for their language. For example, ConsoleExporter, StdoutExporter,
+StreamExporter, LoggingExporter etc.
+
+If a language provides a mechanism to automatically configure a
+[Span processor](../sdk.md#span-processor) to pair with the associated
+exporter (e.g., using the [`OTEL_TRACES_EXPORTER` environment
+variable](../../configuration/sdk-environment-variables.md#exporter-selection)), by
+default the standard output exporter SHOULD be paired with a [simple
+processor](../sdk.md#simple-processor).