-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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/otlphttpexporter] Partial success HTTP response handling #8270
[exporter/otlphttpexporter] Partial success HTTP response handling #8270
Conversation
…ignore responses not encoded as protobuf
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #8270 +/- ##
==========================================
- Coverage 90.27% 90.18% -0.10%
==========================================
Files 301 302 +1
Lines 15596 15775 +179
==========================================
+ Hits 14080 14227 +147
- Misses 1227 1254 +27
- Partials 289 294 +5
☔ View full report in Codecov by Sentry. |
@evan-bradley would you please take a look as well? |
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.
👍🏻
func metricsPartialSuccessHandler(protoBytes []byte) error { | ||
func metricsPartialSuccessHandler(protoBytes []byte, contentType string) error { | ||
if contentType != protobufContentType { | ||
return nil |
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.
@atoulme Why ignore the response if it is not Protobuf? It can be OTLP/JSON which is a valid content type and which can be decoded, right?
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.
Nevermind, I see OTLP/JSON is not yet implemented by this exporter.
Description:
Fix the handling of the HTTP response to ignore responses not encoded as protobuf
Link to tracking Issue:
Fixes #8263