-
Notifications
You must be signed in to change notification settings - Fork 417
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
[EXPORTER] Add logging for async gRPC errors #3108
[EXPORTER] Add logging for async gRPC errors #3108
Conversation
✅ Deploy Preview for opentelemetry-cpp-api-docs canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3108 +/- ##
==========================================
+ Coverage 87.12% 87.91% +0.79%
==========================================
Files 200 195 -5
Lines 6109 6133 +24
==========================================
+ Hits 5322 5391 +69
+ Misses 787 742 -45 |
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.
LGTM, thanks for the fix.
See proposed change to fix CI.
OTEL_INTERNAL_LOG_ERROR("[OTLP GRPC Client] ERROR: Export " | ||
<< export_data_name << " failed with status_code: \"" | ||
<< grpc_status.error_code() << "\" error_message: \"" | ||
<< grpc_status.error_message() << "\""); |
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.
Not related to this PR, but we need to figure out some way of throttling, as this can otherwise flood the logs for the non-recoverable issues.
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.
LGTM and thanks
[EXPORTER] Add logging for async gRPC errors (open-telemetry#3108)
Changes
If there's a gRPC error when exporting telemetry data via
gRPC
withENABLE_ASYNC_EXPORT
set, this error is not printed via logs in the same way as it's done when exporting the data synchronously. Print the error stored ingrpc::Status
in the same way.