Skip to content

Commit

Permalink
add definition for standard output logging exporter (#3741)
Browse files Browse the repository at this point in the history
## 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
#3740
  • Loading branch information
Alex Boten committed Nov 20, 2023
1 parent cf79597 commit f1bdc37
Show file tree
Hide file tree
Showing 2 changed files with 25 additions and 0 deletions.
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
22 changes: 22 additions & 0 deletions specification/logs/sdk_exporters/stdout.md
Original file line number Diff line number Diff line change
@@ -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).

0 comments on commit f1bdc37

Please sign in to comment.