Exclude Pattern Filter

Noisy logs hide signal behind the same few recurring lines. Exclude Pattern Filter strips any lines matching your blocklist — healthchecks, heartbeats, probes, debug chatter — so the meaningful entries stand out.

Plain words or regexes, case control, and a clear kept/removed tally make decluttering any paste a two-step job.

Each pattern box entry is its own rule and rules are combined with OR logic — a line is dropped the moment any single pattern matches it, so you do not need to write one giant regex to cover several kinds of noise. In substring mode every pattern is matched literally: no escaping, no special characters to worry about, and by default the comparison is case-insensitive so "ERROR" and "error" both hit a pattern of "error". Toggle the case-sensitive checkbox when you need an exact-case match, for example to exclude only the capitalized "DEBUG" tag and keep lowercase "debug" mentions inside a message body. Regex mode compiles every pattern line as its own RegExp, so you can combine word boundaries, alternation, and anchors — useful when a plain substring would also catch lines you want to keep. If any regex fails to compile, the tool reports which pattern was invalid instead of silently ignoring it.

• Multi-pattern — one rule per line, combined with OR logic.
• Regex mode — advanced matching with anchors, alternation and character classes.
• Case control — exact or insensitive comparison for either mode.
• Kept/removed stats — measurable cleanup, so you know exactly how much noise a pattern set took out.
• Invalid-regex feedback — broken patterns are reported by name instead of failing silently.
• Copyable output — the kept lines are ready to paste into a ticket or another tool.

1. Paste the noisy log into the left box.
2. List one pattern per line in the exclude box — substrings by default, or tick "Treat patterns as regex" for full expressions.
3. Choose whether matching should be case-sensitive; leave it off to catch mixed-case noise with fewer rules.
4. Filter. Review the total/kept/removed counts, confirm nothing important was dropped, then copy the cleaned lines.

Example 1 — Healthchecks. Exclude "healthcheck", "/health" and "heartbeat" to see real traffic only — typical in Kubernetes liveness/readiness probes and load-balancer pings that otherwise dominate an access log.

Example 2 — Probes. Regex-exclude "(curl|wget|monitor)\." to hide uptime bots and synthetic monitoring clients that repeat the same request every few seconds.

Example 3 — Dev noise. Drop DEBUG and "cache hit" lines before sharing a log with the team, so reviewers see the handful of WARN/ERROR entries instead of scrolling past thousands of routine cache lookups.

Example 4 — Known-good sources. Regex-exclude your own office or CI runner IP (for example ^\S+\s+\S+\s+YOUR_IP) before triaging a suspected attack, so internal traffic does not pad the counts.

• Immediate signal — recurring noise disappears in one pass.
• Flexible rules — plain words for quick cleanup, regex for precision.
• Quantified — kept/removed counts show the effect of every pattern set.
• Safe to iterate — adjust patterns and re-run without losing the original paste.
• Private — fully in-browser, logs never leave the page.