Skip to content

OTLP HTTP Server Response Code #3203

Description

@dineshg13

What are you trying to achieve?
We are trying to setup a OTLP HTTP Server, it is not clear if responding with any code other than 200 is considered error. Every SDK is handling this differently.

  1. OTLP exporter n collector treats all codes in [200, 300) as success:

  2. Java otlp http exporter treats all codes in [200, 300) as success: https://github.com/open-telemetry/opentelemetry-java/blob/3d73283a71a2a6e1d6dd5e725098f697b1edae03/exporters/common/src/main/java/io/opentelemetry/exporter/internal/okhttp/OkHttpExporter.java#L120 .

public boolean isSuccessful()
Returns true if the code is in [200..300), which means the request was successfully received, understood, and accepted.
  1. Python http exporter treats 200 and 202 as success:
  2. Go HTTP Exporter treats only 200 status code as success.

What did you expect to see?
I would expect the specification to say explicitly that any 2xx shouldn't be considered an error.

Additional context.
See discussion on PR open-telemetry/opentelemetry-go#3707

Metadata

Metadata

Assignees

Labels

[label deprecated] triaged-needmoreinfo[label deprecated] The issue is triaged - the OTel community needs more information to decidespec:protocolRelated to the specification/protocol directory

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions