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

Implement SpanProcessor::force_flush #349

Closed
frigus02 opened this issue Nov 8, 2020 · 0 comments · Fixed by #358
Closed

Implement SpanProcessor::force_flush #349

frigus02 opened this issue Nov 8, 2020 · 0 comments · Fixed by #358

Comments

@frigus02
Copy link
Member

frigus02 commented Nov 8, 2020

Implement force_flush as specified here: https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/sdk.md#forceflush

Exports all spans that have not yet been exported to the configured Exporter.

ForceFlush SHOULD provide a way to let the caller know whether it succeeded, failed or timed out.

ForceFlush SHOULD only be called in cases where it is absolutely necessary, such as when using some FaaS providers that may suspend the process after an invocation, but before the Processor exports the completed spans.

ForceFlush SHOULD complete or abort within some timeout. ForceFlush can be implemented as a blocking API or an asynchronous API which notifies the caller via a callback or an event. Language library authors can decide if they want to make the flush timeout configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant