Split oversize exports

Open
  • Is something wrong?
#47 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
observability-sre

Research direction

Start by reading related issue #19 and the existing OTEL exporter implementation, then compare the Python SDK's splitting logic. Done means oversized exports are divided into smaller payloads before sending and the behavior is covered by tests.

Written by the indexing model from the issue text.

Description

Related to #19

We should wrap our otel exporter such that if it sends oversize exports we split them into smaller payloads. The Python SDK has logic we can replicate to achieve this.

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.