From cf79597f25669709b39ddf3e90e951604c58d8ec Mon Sep 17 00:00:00 2001 From: Alex Boten Date: Fri, 17 Nov 2023 04:07:23 -0800 Subject: [PATCH 1/2] add definition for standard output span exporter (#3740) --- CHANGELOG.md | 3 +++ specification/trace/sdk_exporters/stdout.md | 22 +++++++++++++++++++++ 2 files changed, 25 insertions(+) create mode 100644 specification/trace/sdk_exporters/stdout.md diff --git a/CHANGELOG.md b/CHANGELOG.md index 5debda72f5f..e46c4e9d708 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,9 @@ release. ### Traces +- Add definition for standard output span exporter. + ([#3740](https://github.com/open-telemetry/opentelemetry-specification/pull/3740)) + ### Metrics ### Logs diff --git a/specification/trace/sdk_exporters/stdout.md b/specification/trace/sdk_exporters/stdout.md new file mode 100644 index 00000000000..0ec93f343b5 --- /dev/null +++ b/specification/trace/sdk_exporters/stdout.md @@ -0,0 +1,22 @@ + + +# 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). From f1bdc378204ee5dde3c1c42d06ff2497c7f191f2 Mon Sep 17 00:00:00 2001 From: Alex Boten Date: Mon, 20 Nov 2023 07:22:20 -0800 Subject: [PATCH 2/2] add definition for standard output logging exporter (#3741) ## Changes I couldn't find the definition for a standard output exporter for the logging signal, so I'm submitting one. This is mostly a copy of the definition already present for the metrics exporter. It doesn't specify a format for the output itself. Similar to https://github.com/open-telemetry/opentelemetry-specification/pull/3740 --- CHANGELOG.md | 3 +++ specification/logs/sdk_exporters/stdout.md | 22 ++++++++++++++++++++++ 2 files changed, 25 insertions(+) create mode 100644 specification/logs/sdk_exporters/stdout.md diff --git a/CHANGELOG.md b/CHANGELOG.md index e46c4e9d708..b21d69656a8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -18,6 +18,9 @@ release. ### Logs +- Add definition for standard output log record exporter. + ([#3741](https://github.com/open-telemetry/opentelemetry-specification/pull/3741)) + ### Resource ### OpenTelemetry Protocol diff --git a/specification/logs/sdk_exporters/stdout.md b/specification/logs/sdk_exporters/stdout.md new file mode 100644 index 00000000000..63efd060f44 --- /dev/null +++ b/specification/logs/sdk_exporters/stdout.md @@ -0,0 +1,22 @@ + + +# 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).