Add table for OTLP/HTTP response code and client retry recommendation (…

…#3028)
open-telemetry · Dec 20, 2022 · ff19b9e · ff19b9e
1 parent 9153048
commit ff19b9e
Show file tree

Hide file tree

Showing 2 changed files with 14 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -641,6 +641,7 @@ release.
   ([#2235](https://github.com/open-telemetry/opentelemetry-specification/pull/2235))
 - Parameters for private key and its chain added
   ([#2370](https://github.com/open-telemetry/opentelemetry-specification/pull/2370))
+- Add table for OTLP/HTTP response code and client retry recommendation([#3028](https://github.com/open-telemetry/opentelemetry-specification/pull/3028))
 
 ### SDK Configuration
 

diff --git a/specification/protocol/otlp.md b/specification/protocol/otlp.md
@@ -547,6 +547,19 @@ defined in `Status` message schema.
 The server MAY include `Status.details` field with additional details. Read
 below about what this field can contain in each specific failure case.
 
+The server SHOULD use HTTP response status codes to indicate
+retryable and not-retryable errors for a particular erroneous situation. The
+client SHOULD honour HTTP response status codes as retryable or not-retryable.
+The requests that receive a response status code listed in following table SHOULD be retried.
+All other `4xx` or `5xx` response status codes MUST NOT be retried.
+
+|HTTP response status code|
+|---------|
+|429 Too Many Requests|
+|502 Bad Gateway|
+|503 Service Unavailable|
+|504 Gateway Timeout|
+
 ##### Bad Data
 
 If the processing of the request fails because the request contains data that