WORKED EXAMPLE · SYNTHETIC INPUT
Prepare a log excerpt for a support ticket
A useful request trace may contain a token, password or customer identifier. Removing the whole trace loses the request ID needed to investigate.
阅读中文版
These inputs demonstrate reproducible behaviour; they are not customer incidents or evidence of real usage.
Reproducible input
Authorization: Bearer demo.token.value
{"password":"demo-secret","email":"ada@example.com","requestId":"req-123"}
customer_id=customer-42Steps
- Load the sample and generate a redacted preview.
- Verify that the authorization header, password and email are masked while requestId remains.
- Add customer_id to the sensitive field list and run again. Review the entire result before copying it into a ticket.
Expected result
The credential values and selected customer ID are replaced; req-123 remains available for correlation. Only tool paths, never log contents, can be saved in the toolkit shelf.
Limits and manual checks
Pattern matching is not a complete privacy scanner. Escaped names, object values, multiline secrets and unrecognized identifiers may remain. Use fictional data to test rules and manually inspect every real excerpt.
Technical reference