Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chore: modify LogExporter and TraceExporter interfaces to support returning failure #2381
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
chore: modify LogExporter and TraceExporter interfaces to support returning failure #2381
Changes from all commits
2c24988
5b243a6
77d9a01
dc5d9b1
1b49188
a670a4e
6440a73
3c68efa
c2586ce
a460184
b1fff95
0ad193f
4df322f
26bbdc4
de49068
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Check warning on line 58 in opentelemetry-otlp/src/exporter/http/logs.rs
opentelemetry-otlp/src/exporter/http/logs.rs#L56-L58
Check warning on line 70 in opentelemetry-otlp/src/exporter/http/trace.rs
opentelemetry-otlp/src/exporter/http/trace.rs#L68-L70
Check warning on line 95 in opentelemetry-otlp/src/exporter/tonic/logs.rs
opentelemetry-otlp/src/exporter/tonic/logs.rs#L95
Check warning on line 97 in opentelemetry-otlp/src/exporter/tonic/logs.rs
opentelemetry-otlp/src/exporter/tonic/logs.rs#L97
Check warning on line 94 in opentelemetry-otlp/src/exporter/tonic/trace.rs
opentelemetry-otlp/src/exporter/tonic/trace.rs#L94
Check warning on line 96 in opentelemetry-otlp/src/exporter/tonic/trace.rs
opentelemetry-otlp/src/exporter/tonic/trace.rs#L96
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is exposing internal details. "Client" may or may not be a thing, depending on the exporter.
Can we live with the following for Provider.ShutDown()
Provider.ShutDown() is expected to pass shutdown() calls to registered Processors/Readers, and clean up its own internal state, if any. There is no "export" notion in provider, as provider don't even have access to Exporters.
Also wondering if we should even have Result with custom Error types for processor.shutdown(), exporter.shutdown() reader.shutdown() ? Or can be return just Result with just String, and do internal logging? These are anyway not invoked by user (user only invoke provider.shutdown()), so is there value in returning Result with custom Errors?
Check warning on line 77 in opentelemetry-sdk/src/error.rs
opentelemetry-sdk/src/error.rs#L75-L77
Check warning on line 146 in opentelemetry-sdk/src/logs/log_emitter.rs
opentelemetry-sdk/src/logs/log_emitter.rs#L146