DEBUGGING PLAYBOOK · REVIEWED 2026-10-08
Prepare a log excerpt for a bug report
A bug report needs reproducible context, but copied headers and bodies may expose credentials or personal identifiers. This sample uses invented values.
Sample input
Authorization: Bearer demo.token
{"password":"demo-secret","requestId":"req-123"}
email=ada@example.com customer_id=customer-42Steps and checks
- Load the sample, keep default fields and email masking enabled, then preview redaction.
- Compare with the reference: authorization, password and email are masked. requestId and customer_id remain and still require review.
- Add customer_id to the field list and run again. Confirm it is masked, then inspect every line before copying or downloading.
Reference result
Authorization: [REDACTED]
{"password":"[REDACTED]","requestId":"req-123"}
email=[EMAIL] customer_id=customer-42Avoid a misleading conclusion
The count measures rule replacements, not all secrets. Object values, multiline fields and unrecognized credential formats can escape the rules. A clean-looking preview is not a privacy guarantee.
What to do next
Share the smallest excerpt needed to reproduce an issue. Replace real values with invented examples, and include the tool URL, steps, expected result and actual result in a report.
Related case and technical reference · Report an error or missing edge case