The log SDK spec contains the skeleton for a "built-in exporters" section. It only contains things specific to OTLP.
|
### Built-in exporters |
|
|
|
TODO: Break out into files under `./sdk_exporters`. |
|
|
|
#### OTLP Exporter |
|
|
|
Exports to an OTLP network destination via OTLP/gRPC or OTLP/HTTP. |
|
|
|
#### OTLP File exporter |
|
|
|
Writes to a file or stdout in either OTLP JSON or OTLP Protobuf binary format. |
|
|
|
 |
|
|
|
TODO: clarify how this functionality co-exists with the overlapping |
|
functionality in logging libraries that allow specifying how logs are written to |
|
a file. |
At this time, the trace SDK does not contain a trace-specific OTLP exporter spec - only a Jaeger and Zipkin exporter spec - see: https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/sdk_exporters. It would seem that the OTLP exporter spec sufficiently covers most things for all signals. Metrics is a small exception as there are metric-specific OTLP configuration options.
It seems there could be a discussion of a greater reorganization of OTLP exporter related specs. For example, maybe centralizing specifics for all signals into the main OTLP exporter spec.
For now, though, I recommend we remove this section from the log SDK spec. We can introduce an sdk_exporters directory under the log specification or decide to reorganize things at a later date if necessary.
The log SDK spec contains the skeleton for a "built-in exporters" section. It only contains things specific to OTLP.
opentelemetry-specification/specification/logs/sdk.md
Lines 369 to 385 in 150451d
At this time, the trace SDK does not contain a trace-specific OTLP exporter spec - only a Jaeger and Zipkin exporter spec - see: https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/trace/sdk_exporters. It would seem that the OTLP exporter spec sufficiently covers most things for all signals. Metrics is a small exception as there are metric-specific OTLP configuration options.
It seems there could be a discussion of a greater reorganization of OTLP exporter related specs. For example, maybe centralizing specifics for all signals into the main OTLP exporter spec.
For now, though, I recommend we remove this section from the log SDK spec. We can introduce an
sdk_exportersdirectory under the log specification or decide to reorganize things at a later date if necessary.