Logs do not respect the sampling configuration

Open
  • Is something wrong?
#105 2 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

Research direction

Start by reviewing the linked logfire-rust pull request 103 and the current OpenTelemetry sampling behavior for logs. Compare the option of raising the limitation with the OpenTelemetry SDK against implementing a workaround in logfire-rust. The issue is done when a supported approach for configuring log sampling is selected and implemented or documented with clear limits.

Written by the indexing model from the issue text.

Description

At the moment in otel, sampling is provided when you are creating spans, but there is no place to adjust the sampling profile of logs themselves. I found this out when I was fiddling with: https://github.com/pydantic/logfire-rust/pull/103

We could:

  • raise this with the otel sdk itself
  • have some workarounds in logfire-rust
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.