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
// OtlpError writes an OTLP-compliant error response to the given http.ResponseWriter.
315
+
//
316
+
// According to the OTLP spec: https://opentelemetry.io/docs/specs/otlp/#failures-1
317
+
// Re. the error response format
318
+
// > If the processing of the request fails, the server MUST respond with appropriate HTTP 4xx or HTTP 5xx status code.
319
+
// > The response body for all HTTP 4xx and HTTP 5xx responses MUST be a Protobuf-encoded Status message that describes the problem.
320
+
// > This specification does not use Status.code field and the server MAY omit Status.code field.
321
+
// > The clients are not expected to alter their behavior based on Status.code field but MAY record it for troubleshooting purposes.
322
+
// > The Status.message field SHOULD contain a developer-facing error message as defined in Status message schema.
323
+
//
324
+
// Re. retryable errors
325
+
// > 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
326
+
// > 429 Too Many Requests
327
+
// > 502 Bad Gateway
328
+
// > 503 Service Unavailable
329
+
// > 504 Gateway Timeout
330
+
// In loki, we expect clients to retry on 500 errors, so we map 500 errors to 503.
0 commit comments