Log Formatter

Paste JSON-per-line or plain-text logs — get colour-coded output by level, level counts, extracted IDs, and optional PII redaction.

Runs 100% client-side
Copy output
On this page4 sections
InputJSON-per-line or plain text
Output

Output will appear here after formatting…

HOW TO USE

  1. 01Paste structured (JSON-per-line) or plain-text logs into the input.
  2. 02ERROR/WARN lines are colour-coded, a level-count summary appears, and correlation/request IDs are extracted.
  3. 03Toggle PII redaction before copying if you'll share the output.
  4. 04Copy the formatted output into a bug report.

Try it

Paste the stdout from a failing CI run to highlight the ERROR lines

WHEN TO USE

Use when you need to read through raw application logs to diagnose a failing test or incident. Paste JSON-per-line (structured) or plain-text logs and get colour-coded output by level, an instant level-count summary, extracted correlation/request IDs, and optional PII redaction. Fastest way to go from a wall of log output to the relevant ERROR lines.

WHAT BUGS THIS FINDS

  • Missing error logs

    An exception was swallowed — no ERROR line appears when the test expects one. Level-count summary shows 0 ERRORs.

  • Wrong log level

    A critical failure is logged at INFO instead of ERROR, causing monitoring tools to miss it.

  • PII leaked in logs

    Emails, auth tokens, or user IDs appear in plain text in logs — caught by the redaction scan before the log is shared.

  • Correlation ID absent

    Structured logs are missing the correlation ID field, making cross-service tracing impossible.

QA USE CASES

01

Triage a failed test run

Paste the log output from a CI failure — ERROR/WARN lines are highlighted immediately and counted in the summary.

02

Extract correlation IDs

Automatically pulls request IDs, trace IDs, and correlation IDs from structured JSON logs so you can correlate across services.

03

Redact before sharing

Enable PII redaction before pasting log snippets into a bug report or sharing with a third-party — masks emails, tokens, and numeric IDs.

04

Count log-level distribution

Quickly confirm that a test scenario generates the expected ratio of INFO to WARN to ERROR lines.