traceloop / traceloop/openllmetry
🚀 Feature: allow disabling prompt sending as an argument to Traceloop.init()
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
Add a setting called trace_content (which will default to true) and will control whether all the instrumentations are sending sensitive content (like prompts and completions). This should override the env var behavior (similar to other flags we have).
🎤 Why is this feature needed ?
More control on this sensitive feature
✌️ How do you aim to achieve this?
🔄️ 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
Start at Traceloop.init() and inspect how existing flags and environment variables are handled. Trace how each instrumentation sends prompts and completions, then verify that the new setting defaults to true, overrides the environment behavior, and consistently controls sensitive content across the SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100