OTLP HTTP exporter reports a 3xx response as a successful export, so redirected batches are dropped without any log

Open Beginner friendly
#5,865 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@d4rshnn is already working on this.

Since Oct 31, 2026.

  • #5868 by @d4rshnn — open
  • #5905 by @2Zest — closed without merging
  • #5911 by @2Zest — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
observability

Research direction

Start with the shared exporter logic in exporter/opentelemetry-exporter-otlp-common/src/opentelemetry/exporter/otlp/common/http.py, especially the lines linked in the issue. Check the existing tests for HTTP export status handling, then verify that a 3xx response produces SpanExportResult.FAILURE and an error log while successful responses remain successful.

Written by the indexing model from the issue text.

Description

bug
Describe your environment

OS: macOS (Darwin 25.5.0)
Python version: 3.14.6
SDK version: 1.45.1 (opentelemetry-exporter-otlp-proto-http 1.45.1, opentelemetry-exporter-otlp-common 0.66b1, opentelemetry-exporter-http-transport 0.66b1)
API version: 1.45.1

What happened?

Redirections are not followed and are not logged as error. It makes the batches silently dropped.

Both HTTP transports turn off redirects since #5194.
The shared exporter code still counts any status from 200 to 399 as success. So a 308 comes back as SpanExportResult.SUCCESS, nothing is logged and the batch is lost.

https://github.com/open-telemetry/opentelemetry-python/blob/3462000f323b4f3d03c10d09b9d82c03119f2c59/exporter/opentelemetry-exporter-otlp-common/src/opentelemetry/exporter/otlp/common/http.py#L203-L218

Steps to Reproduce

The following code runs a server that always redirects and tries to export to that server. The export is successful.

import logging
import threading
from http.server import BaseHTTPRequestHandler, HTTPServer

from opentelemetry.exporter.otlp.proto.http.trace_exporter import OTLPSpanExporter
from opentelemetry.sdk.trace import TracerProvider

logging.basicConfig(level=logging.DEBUG)

class AlwaysRedirect(BaseHTTPRequestHandler):
    def do_POST(self):
        self.rfile.read(int(self.headers["Content-Length"]))
        self.send_response(308)
        self.send_header("Location", "/elsewhere/v1/traces")
        self.send_header("Content-Length", "0")
        self.end_headers()


server = HTTPServer(("127.0.0.1", 0), AlwaysRedirect)
threading.Thread(target=server.serve_forever, daemon=True).start()

span = TracerProvider().get_tracer("repro").start_span("span")
span.end()

exporter = OTLPSpanExporter(endpoint=f"http://127.0.0.1:{server.server_port}/v1/traces")
print("export result:", exporter.export([span]))
Expected Result

The export is reported as failed (SpanExportResult.FAILURE) with an error log.

Actual Result

The export is successful but nothing is really exported and batches are lost.

Additional context

No response

Would you like to implement a fix?

No response

Tip

No response

Dominant language
Python
Stars
2.7k
Forks
1.1k
Avg merge
4d 13m
Merged PRs (30d)
38

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from open-telemetry/opentelemetry-python

All issues in open-telemetry/opentelemetry-python

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.