Outcome
A minimized log excerpt with secrets removed, timestamps preserved, and a diff that confirms the redaction pass.
Workflow
Parse logs, remove secrets, and compare sanitized output before posting it to an issue or chat.
Use this path when a stack trace, HAR export, environment file, or application log needs to be shared outside the original incident channel.
A minimized log excerpt with secrets removed, timestamps preserved, and a diff that confirms the redaction pass.
These workflow pages do not process, collect, or store tool input. Use the linked tools directly and review their trust badges before handling sensitive data.
Trim unrelated lines so the shared sample contains the failing request, timestamp window, and nearby context only.
Local Log ParserRun the log through local scrubbing rules for bearer tokens, API keys, cookies, emails, and private identifiers.
Log ScrubberIf the evidence is a HAR file, remove sensitive headers and request bodies before exporting a reduced artifact.
HAR Viewer / SanitizerCompare original and scrubbed text so only expected sensitive fields changed.
Text Diff CheckerRedact secrets, tokens, emails, IP addresses, and credentials from logs locally before sharing.
Parse and analyze logs locally. Supports JSON Lines, plain text, and common log formats.
Inspect browser HAR exports locally and redact headers, cookies, query strings, bodies, and response content before sharing.
Compare two pieces of text side-by-side. Highlights additions, deletions, and modifications instantly.
Parse .env files, validate variables, and export to JSON, YAML, or Docker args.
No automated scrubber can guarantee that. Use the redaction pass, then inspect the diff and the final excerpt manually.
Keep only file names that are necessary to understand the failure. Remove user names, private paths, and customer identifiers.
Use the HAR sanitizer when the evidence includes browser requests, headers, timings, or response metadata.