Clarify max_scan_chars behavior for secrets detection; Added notes on detection limit...

diff --git a/config.example.yaml b/config.example.yaml
index 3ac44d6a4fa03f192dee054b484c03c93246f8a1..abfede7b620ea473d675edf269be0e008a7d9d09 100644 (file)
--- a/config.example.yaml
+++ b/config.example.yaml
@@ -125,7 +125,9 @@ secrets_detection:
     # - BEARER_TOKEN
 
   # Maximum characters to scan per request (performance limit)
-  # Set to 0 to scan entire request (not recommended for large payloads)
+  # Note: Secrets placed after this limit won't be detected.
+  # Set to 0 to scan entire request (full coverage, but slower for large payloads)
+  # The 200KB default covers typical use cases
   max_scan_chars: 200000
 
   # Placeholder format for redaction (only used if action: redact)