All Tools View Categories About Contact Privacy

Log Level Filter

Isolate ERROR / WARN / INFO / DEBUG / TRACE / FATAL lines from any log paste.

Runs entirely in your browser — your logs never leave this page.
Levels
Mode
0
total
0
kept
0
dropped
-
levels

  

About Log Level Filter

The fastest way to silence noise. Log Level Filter isolates ERROR, WARN, INFO, DEBUG, TRACE or FATAL lines from any log paste, letting you focus on exactly the severity you care about.

Output keeps or removes matching lines and reports per-level counts so you see the full severity profile at a glance.

Features

  • Level checkboxes — pick any combination.
  • Keep or drop mode — isolate or exclude.
  • Unmatched lines — keep or remove toggle.
  • Per-level counts — full profile.
  • Plain-text output — ready to copy.

How to Use

  1. Paste your log lines.
  2. Check the levels you want (or uncheck for drop mode).
  3. Choose keep-or-drop.
  4. Filter. Copy the result.

Examples

Example 1 — Debugging. Select DEBUG + INFO to see the fine-grained flow.

Example 2 — Alerting drill. Select ERROR + FATAL only, drop everything else, and review what actually broke.

Example 3 — Noise removal. Check DEBUG and switch to Drop to strip noisy trace lines before analysis.

Benefits

  • Instant focus — one click per severity.
  • Lossless — unmatched-line option.
  • Profile view — severity histogram.
  • Private — fully client-side.

Frequently Asked Questions

Which levels are recognized?
ERROR, WARN/WARNING, INFO, DEBUG, TRACE, FATAL/CRITICAL, plus lowercase variants. The regex handles bracketed, bare, and colon-separated forms.
What happens to lines with no level?
They are kept by default so you never silently lose context; a toggle lets you drop them if you only want level lines.
Does it match inside words?
No — the level must be a standalone token, so "WARNING:" and "ERROR]" match but "unwarned" does not.
Can I combine with other filters?
Run the output through any other tool in this suite, such as the IP filter or duplicate remover.
Is it case sensitive?
No, matching is case-insensitive.