Back to Tools

Log Analyzer

Extract statistics, errors, and frequency counts from massive log dumps.

Input Data

Get the shape of a log before reading it line by line

When someone hands you a few hundred lines of output, the first useful question is usually how bad it is. The Log Analyzer answers that by classifying every line and showing three large counters: errors, warnings and informational messages. Under them it lists example error lines so you can see what kind of failure is involved.

Running an analysis

  1. Paste your log text into Input Data. The Sample button fills in six lines that include a repeated timeout, and Clear resets the box.
  2. Click Process Now.
  3. Read the three cards labelled Errors, Warnings and Infos, and the Total Lines Parsed figure in the summary row.
  4. Look at Recent Errors Sample for the actual text of the error lines, then copy or download the result if needed.

How lines are classified

Each non-empty line is upper-cased and checked in a fixed order. If it contains ERROR, FATAL or FAIL it counts as an error. Otherwise, if it contains WARN it is a warning. Otherwise, if it contains INFO or DEBUG it is counted as info. Lines that match none of these still add to the total but not to any card, so the three numbers may not add up to the total. The error sample shows at most ten lines, taken from the top of your input in order, not the newest, despite the word Recent in the heading.

Practical uses

  • Triage: deciding whether a nightly job log needs attention or looks routine.
  • Comparing two runs of a script by pasting each and comparing the counters.
  • Spotting a repeating error such as the same timeout appearing again and again.
  • Putting numbers into a status update without counting lines by hand.

Caveats

The classification is keyword-based, so a line such as an info message that mentions a failed retry counts as an error, and a line that names its level in some other way, like CRITICAL or NOTICE, is not tallied. It does not group identical messages or read timestamps, and multi-line stack traces are counted line by line. For grouping by level with colour, use the Log Formatter afterwards. Analysis runs in your browser on the text you paste.

Related Tools


Frequently Asked Questions

How does it decide whether a line is an error, warning or info?
It checks in order: ERROR, FATAL or FAIL makes it an error; WARN makes it a warning; INFO or DEBUG makes it info. Matching ignores case, and the first category that matches wins.
Why do the three counts not add up to the total?
Lines that contain none of the recognised keywords, such as CRITICAL, TRACE or plain output, count toward Total Lines Parsed but are not assigned to a card. This is expected for logs that use different level names.
Is the error sample the most recent errors?
No. It shows up to the first ten error lines in the order they appear in your input, despite the heading. If you need the latest errors, paste the end of the log or reverse the order first.
Does it group duplicate messages?
No. Every matching line is counted individually, and the sample lists repeats as separate entries. A repeated timeout error will therefore inflate the error count, which can itself be a useful signal.
Can it read timestamps or JSON logs?
It only looks for keywords in each line of text. It does not parse dates or JSON fields. For structured JSON lines, the JSON Log Viewer displays the level and message columns properly.
Support Chat
We typically reply within minutes

Hello! 👋 Before we start, please tell us your name.