Support handling Retryable error for OTLP exporter (OTLP/gRPC and OTLP/HTTP)

[mks26]

Hi,

If OTel collector is down or due to some other reason if OTLP exporter received Retryable error code from OTel collector, it has to be handled and the OTLP exporter has to retry sending the same trace span. Currently there is no code in OTLP exporter(both OTLP/gRPC and OTLP/HTTP) to handle retryable error code in opentelmetry-cpp sdk. As currently retryable error code is not handled for OTLP exporters, so it will discard the trace span when OTel collector returned retryable error code).

Error codes that are retryable and non-retryable is mentioned in OTLP spec at :
https://opentelemetry.io/docs/reference/specification/protocol/otlp/

OTLP/GRPC: https://opentelemetry.io/docs/reference/specification/protocol/otlp/#failures
OTLP/HTTP : https://opentelemetry.io/docs/reference/specification/protocol/otlp/#failures-1

I this this can be a candidate for feature.

discussion link: #2042

Thanks,
Mukesh

[lalitb]

Thanks for raising the issue. Just to add, the support for handling retryable/non-retryable response from OTLP collector is marked as optional feature in the specs - https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#exporters. Which means, this won't be of high priority, will mark this as help required if someone wants to contribute it.

[mks26]

Thanks @lalitb !

[github-actions]

This issue was marked as stale due to lack of activity.