-
Notifications
You must be signed in to change notification settings - Fork 742
🚀 Feature: allow disabling prompt sending as an argument to Traceloop.init() #137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
is this still available to work on? |
Yes @randolfuy01 :) |
perfect I'll look into it! |
@nirga @randolfuy01 Hi there! Is it still WIP? If not, I would love to start looking around this issue:) |
Not sure what's @randolfuy01's status, but there are other issues that you can also look at that are unassigned @sanspareilsmyn! |
@nirga Hi! Is this issue still open? If so, I would be happy to look at it :) |
Sounds good @liamjdavis! |
@nirga To clarify in greater detail,
the sensitive content being shared for each individual instrument is controlled. |
Yes! |
@nirga is the issue still open to work on? |
Yes @thapasya-m! |
@nirga is the issue still open? |
Yes @shivarag200701! |
Which component is this feature for?
Traceloop SDK
🔖 Feature description
Add a setting called
trace_content
(which will default totrue
) 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?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: