Skip to content
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

[feature request] enable key redaction with the @tracer.chain decorator #1292

Open
mikeldking opened this issue Feb 17, 2025 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@mikeldking
Copy link
Contributor

mikeldking commented Feb 17, 2025

Since tracer decorators serialize IO automatically, sometimes it results in un-wanted capturing of things like credentials

{
    "test_setup": {
        "run_id": "run_BmrvEMsS_20250214_153051",
        "run_timestamp": "20250214-153051",
        "prompts": {
        " prompt 1 ": <redacted>, 
        " prompt 2 " : <redacted>,
        etc}
        "aws_creds": {
            "awsAccessKeyId": <redacted>,
             "awsSecretAccessKey": <redacted>,
             "awsSessionToken": <redacted>,
           }
}

The decorator should be sufficiently configurable such that you can omit certain paths in the input and output payloads. That or this should be globally configurable so that IO can be redacted appropriately via TraceConfig.

@mikeldking mikeldking added enhancement New feature or request triage Issues that require triage and removed triage Issues that require triage labels Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants