PRD: Egress traffic logging #207
Reference in New Issue
Block a user
Delete Branch "feat/egress-log-option"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #203.
PRD 0056
Summary
egress.log(integer 0/1/2) as a global log level for the egress proxyegress_request/egress_responseJSON lines for every forwarded connection (headers, body after auth injection)Configdataclass inegress_addon_corewrapsroutes + log;parse_config()/load_config()are the new entry points (oldload_routeskept for backward compat)[log=off],[log=blocks],[log=full]test_egress_addon_core,test_egress, andtest_manifest_egressfeat(egress): add global log option for full request/response loggingto PRD 0056: Egress traffic loggingPRD 0056: Egress traffic loggingto PRD: Egress traffic loggingEach DLP block/warn now reports where the match was found (body, authorization header, response body) and includes a context snippet: SNIPPET_CONTEXT chars before and after the match, with the matched value replaced by REDACT ("********"). scan_token_patterns/scan_known_secrets/scan_naive_injection all gain `location` and `context` fields on their ScanResult returns. The outbound scanner takes `auth_header` as a separate kwarg so the two locations are scanned and reported independently. redact_tokens() is added to dlp_detectors and used in egress_addon.py to scrub token patterns and provisioned secrets from host/path fields before they appear in any log output (level 1 and 2). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>5091552625to8743299226