Handle partial success responses in the OTLP exporter

[evan-bradley]

Description:

Handle partial success messages returned from OTLP gRPC backends.

Link to tracking Issue:

Fixes #6686

Testing:

Unit tests. I haven't been able to test this against any live backends, any recommendations would be welcome.

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.01 🎉

Comparison is base (a8a01ef) 91.25% compared to head (e27da35) 91.27%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6971      +/-   ##
==========================================
+ Coverage   91.25%   91.27%   +0.01%     
==========================================
  Files         296      296              
  Lines       14477    14498      +21     
==========================================
+ Hits        13211    13233      +22     
+ Misses       1002     1001       -1     
  Partials      264      264              

Impacted Files	Coverage Δ
exporter/otlpexporter/otlp.go	95.68% <100.00%> (+2.00%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[evan-bradley]

@bogdandrutu @jpkrohling could one of you please take a look?

I will look into the decreased test coverage again today. Last time I checked, it wanted me to test what was essentially an impossible condition, but I will see if I can cover it.

[jpkrohling]

@bogdandrutu seems to have had concerns with the log statement. Perhaps @dmitryax or @codeboten could take a look as well, in case @bogdandrutu is not available?

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[dmitryax]

@evan-bradley do you think we need to merge this now or wait until we have a long-term plan as discussed in #7439 (comment)?

[evan-bradley]

@dmitryax I think we can merge this as-is, I don't expect any functional changes to how partial success responses are handled even after we change the errors.

[evan-bradley]

@dmitryax Could you give this a look? I think it is ready to go, and would like to be able to use this.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[dmitryax]

@dmitryax I think we can merge this as-is, I don't expect any functional changes to how partial success responses are handled even after we change the errors.

Ok, maybe it'll change the messaging only

[evan-bradley]

Ok, maybe it'll change the messaging only

I expect that to be the only thing that changes, since we will still be returning some form of permanent error.

[dmitryax]

LGTM as a temporary solution until we have structured permanent errors