1001Ferramentas
🪵 Dev

Log Pattern Analyzer

Groups log lines by pattern, replacing numbers, IDs and dates with wildcards, and ranks the groups by frequency with a sample of each.

Replace with wildcards

Your log stays in this tab: the text is never uploaded and no request leaves the page.

Why masking changes the ranking

Two lines that differ only by an order id, a timestamp or a request id are the same event repeated. Replacing those parts with wildcards collapses them into one pattern, so 3.000 lines can turn into 40 groups and the top of the list finally shows which failure actually dominates the file.

The masks are applied in a fixed order — dates, UUIDs, URLs, e-mails, IPs, paths, quoted strings, hex and finally plain numbers — because a timestamp masked as a date must not be eaten piece by piece as three numbers first. If a group looks too broad, turn a mask off and analyze again: the same log will split into finer patterns.

Grouping log lines by repeated pattern

A log file with 5,000 lines rarely holds 5,000 different events. Most of the time it is about forty messages repeating with a different order id, timestamp or address. This analyzer swaps those variable parts for named wildcards, NUM for numbers and DATE for dates, merges the lines that became the same text and ranks the groups by frequency, showing the count, the share of the file and the first and last line number.

Masks are applied in a fixed order: date, UUID, URL, e-mail, IP, path, quoted string, hex and finally plain numbers. The order matters because a timestamp must be recognised as a date before the number rule eats it in three pieces. The severity level is read separately, among the first fields of the line, and becomes its own column, so an ERROR and an INFO carrying the same message never merge in the ranking.

The unique appearances block counts how many groups occurred exactly once. That is the rare noise, and a high number there usually means a mask is missing. If a pattern looks too broad, switch one option off and analyze again: the same log splits into finer groups. Above 20,000 lines only the first ones are counted, with a warning. The pasted text never leaves this browser tab.

Frequently asked questions

Why did two nearly identical messages land in different groups?
Because some variable part is still there and no enabled mask covers it, such as a hostname, a file path or a quoted fragment. Turn on the path and quoted string masks and analyze again; if they still split, put the two normalized patterns side by side and the difference shows up immediately.
How many lines can I paste at once?
Up to 20,000 lines are analyzed per run. Above that the tool processes the first 20,000 and shows a warning with the total it received, so you know the ranking covers only part of the file. For bigger files, slice the log by time window and analyze each slice on its own.
Is my production log sent to a server?
No. All the work happens in JavaScript inside this page and no network request carries the pasted content. Even so, a production log may contain personal data and tokens, so it is worth stripping anything sensitive before pasting it into any tool, this one included.

Related Tools