Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify SpanExporter#ForceFlush is required #2654

Merged
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions specification/trace/sdk.md
Original file line number Diff line number Diff line change
Expand Up @@ -602,8 +602,8 @@ primarily a simple telemetry data encoder and transmitter.

### Interface Definition
dyladan marked this conversation as resolved.
Show resolved Hide resolved

The exporter must support two functions: **Export** and **Shutdown**. In
strongly typed languages typically there will be 2 separate `Exporter`
The exporter must support three functions: **Export**, **Shutdown**, and **ForceFlush**.
dyladan marked this conversation as resolved.
Show resolved Hide resolved
In strongly typed languages typically there will be 2 separate `Exporter`
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not blocking, maybe we can just remove this sentence? It mentioned metrics in a tracing spec (also it might be inaccurate because LogExporter does exist https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/logs/logging-library-sdk.md#logexporter).

interfaces, one that accepts spans (SpanExporter) and one that accepts metrics
(MetricsExporter).

Expand Down