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-42

Steps and checks

  1. Load the sample, keep default fields and email masking enabled, then preview redaction.
  2. Compare with the reference: authorization, password and email are masked. requestId and customer_id remain and still require review.
  3. 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-42

Avoid 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

Continue this workflow

Prepare a log excerpt for a support ticket →

About this tool

Prepare a log excerpt for a bug report by masking common credential fields and emails. Processing stays in the browser; no inputs or results are stored. The replacement count measures rule matches, not verified secrets or a privacy score.

How to use

Run the sample and check that the password, authorization header and email disappear while requestId remains. Add customer_id to the comma-separated field names and run again to mask that identifier too. Compare the original and result before copying.

Tips & Notes

This is a rule-based helper, not a complete privacy scanner. It supports quoted scalar or whitespace-free key=value / key:value fields plus whole authorization and cookie header lines. Nested object values, multiline values, escaped keys and many personal identifiers are not recognized. Review every line before sharing. Maximum input: 100,000 characters.