Upgrade OpenTelemetry to preserve HTTP export errors

Open Beginner friendly
  • Is something wrong?
#161 0 comments 0 reactions 0 assignees View on GitHub

@bruno-espino is already working on this.

Since Nov 5, 2026.

  • #162 by @bruno-espino — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
69/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
observability

Research direction

Start by checking the OpenTelemetry dependency versions in the repository manifests and lockfile, then trace how the HTTP exporter is selected in the published dependency stack. Compare the current version with opentelemetry-http 0.33.0, which includes the upstream fix. Done when a local OTLP/HTTP collector returning 401, 429, or 503 exposes the original status instead of network error.

Written by the indexing model from the issue text.

Description

Logfire 0.13.1 still uses OpenTelemetry 0.32. With the published dependency stack, a local OTLP/HTTP collector returning 401, 429 or 503 produces HTTP export failed: network error, hiding the original status.

Upstream fixed this by preserving response status and Retry-After. The fix shipped in opentelemetry-http 0.33.0.

Dominant language
Rust
Stars
78
Forks
13
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 pydantic/logfire-rust

All issues in pydantic/logfire-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.