All Tools View Categories About Contact Privacy

Log Comparison Report Generator

Compare before/after log windows and see what changed.

Runs entirely in your browser — your logs never leave this page.
0
before
0
after
0
added
0
removed

  

About Log Comparison Report Generator

The question after any deploy or reprocessing is the same: what changed in the logs? Log Comparison Report Generator takes a before window and an after window and answers structurally — lines added, lines removed, and what stayed the same.

Underneath it compares the signals that matter: which client IPs appeared or vanished, how the HTTP status histogram moved, whether error volume rose or fell, and how log levels shifted. The result is a tight before/after summary ready for review boards and postmortems.

Features

  • Before/after diff — added, removed, common lines.
  • IP movement — new and departed sources.
  • Status drift — bucket deltas, top codes.
  • Error delta — failure volume before vs after.
  • Level shift — severity mix compared.
  • Plain-text report — paste-ready.

How to Use

  1. Paste the before window (left).
  2. Paste the after window (right).
  3. Compare. The report renders instantly.
  4. Copy the before/after summary.

Examples

Example 1 — Deploy review. Error delta zero but a new IP appeared — traffic source changed, behavior didn’t.

Example 2 — Reprocessing proof. Added/removed line counts match the expected reparse, and the status histogram drifted as intended.

Example 3 — Rate-limit test. 429 volume rising after the change is caught by both the code bucket and error sections.

Benefits

  • Change-focused — what actually moved.
  • Signal aware — IPs, statuses, errors, levels.
  • Multiset-correct — duplicates handled.
  • Review-ready — plain-text output.
  • Private — all processing client-side.

Frequently Asked Questions

What does it compare?
Two pastes (before / after). It computes line counts, added and removed lines, the common core, plus signal-level diffs for client IPs, HTTP status buckets, error counts and log levels.
How are added/removed lines counted?
Line membership is multiset-aware: identical duplicates count correctly, so a line removed at the same time another is added is reported both ways. The first few examples of each are listed.
Which IP changes are reported?
New IPs that appeared in the after window and departed IPs that vanished — perfect for spotting a new scanner or a load balancer swap.
How is status drift shown?
The report compares 2xx/3xx/4xx/5xx totals and the individual most common status codes between windows, with the per-bucket delta.
Is the output embeddable?
Yes — the report is plain text, easy to paste into an incident or change review.