You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Transient errors are not correctly nor completely defined in the OTLP exporter spec.
As discussed in this week's SIG meeting the following statement is apparently out-of-date and should be considered a bug. The status codes referenced in this statement do not align with the set of retryable HTTP status codes in the protocol specification.
In addition to addressing this bug, I believe it would be valuable to more clearly define transient error in the exporter spec to avoid the need to comb over the protocol specification to try and deduce the definition.
The text was updated successfully, but these errors were encountered:
Fixes#3652
This PR attempts to clearly define `transient error` in the OTLP
exporter specification.
It also fixes a bug in that the set of retryable status codes in the
OTLP exporter spec vs. the protocol spec are not aligned.
carlosalberto
pushed a commit
to carlosalberto/opentelemetry-specification
that referenced
this issue
Oct 31, 2024
…#3653)
Fixesopen-telemetry#3652
This PR attempts to clearly define `transient error` in the OTLP
exporter specification.
It also fixes a bug in that the set of retryable status codes in the
OTLP exporter spec vs. the protocol spec are not aligned.
Related to #3639
Transient errors are not correctly nor completely defined in the OTLP exporter spec.
As discussed in this week's SIG meeting the following statement is apparently out-of-date and should be considered a bug. The status codes referenced in this statement do not align with the set of retryable HTTP status codes in the protocol specification.
In addition to addressing this bug, I believe it would be valuable to more clearly define
transient error
in the exporter spec to avoid the need to comb over the protocol specification to try and deduce the definition.The text was updated successfully, but these errors were encountered: