Truncate data before exporting

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
observability-sre

Research direction

No file, test, or entry point is named. First determine which exported data is in scope and what truncation rules and limits are required, then define measurable size or cost behavior and tests that establish when the work is done.

Written by the indexing model from the issue text.

Description

We should make an effort to truncate data before exporting to minimise cost over the wire.

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.