traceloop / traceloop/openllmetry
🚀 Feature: Support for trace sampling
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.4k
- Forks
- 1.1k
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 2
Description
Which component is this feature for?
Traceloop SDK
🔖 Feature description
Traces should have support for setting sampling rate.
🎤 Why is this feature needed ?
Sampling rate helps control the trace volume and improves performance for very high throughput or latency sensitive applications. Also, limiting trace volume helps control cost.
✌️ How do you aim to achieve this?
Similar to https://langfuse.com/docs/tracing-features/sampling or via configuration
🔄️ Additional Information
No response
👀 Have you spent some time to check if this feature request has been raised before?
- I checked and didn't find similar issue
Are you willing to submit PR?
None
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or specific entry points are named. Start by locating the Traceloop SDK's tracing configuration and trace creation flow, then review the linked Langfuse sampling approach. Done should mean callers can configure a sampling rate and trace volume is reduced accordingly without breaking tracing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100