Debug & Review · LOCAL TOOL

Log Triage

Triage a pasted log excerpt by recognized severity words, timestamps, and repeated messages, while preserving the original line text for follow-up.

Runs in this page
No API call

WORKSPACEINPUT → RESULT

Your input

LOCAL

Result

Run the tool to see a result.

Your result will appear here. Input is not saved.

Browser-side processingNothing is sent to a tool API.

WHY THIS TOOL EXISTS

A focused job, not a black box.

Counts and repeat groups help narrow a noisy excerpt into a review queue. The tool labels its recognition rules so plain text is not mistaken for a structured logging format.

How to use it

Paste a bounded log excerpt.
Run the local grouping pass.
Inspect severity counts and repeated-line summaries.

TRY A WORKING EXAMPLE

Start with known input.

Load this sample into the workspace, run the tool, and compare the result shown below.

Show sample input

{
  "logs": "2026-10-18T10:30:00Z INFO server started\n2026-10-18T10:30:02Z ERROR request failed\n2026-10-18T10:30:03Z WARN retry scheduled\n2026-10-18T10:30:04Z ERROR request failed"
}

Expected sample result from the local tool

4 non-empty line(s) · 1 repeated pattern(s).

{
  "counts": {
    "FATAL": 0,
    "ERROR": 2,
    "WARN": 1,
    "INFO": 1,
    "DEBUG": 0,
    "UNCLASSIFIED": 0
  },
  "repeatedLines": [
    {
      "count": 2,
      "normalizedText": "ERROR request failed"
    }
  ],
  "records": [
    {
      "line": 1,
      "level": "INFO",
      "timestamp": "2026-10-18T10:30:00Z",
      "text": "2026-10-18T10:30:00Z INFO server started"
    },
    {
      "line": 2,
      "level": "ERROR",
      "timestamp": "2026-10-18T10:30:02Z",
      "text": "2026-10-18T10:30:02Z ERROR request failed"
    },
    {
      "line": 3,
      "level": "WARN",
      "timestamp": "2026-10-18T10:30:03Z",
      "text": "2026-10-18T10:30:03Z WARN retry scheduled"
    },
    {
      "line": 4,
      "level": "ERROR",
      "timestamp": "2026-10-18T10:30:04Z",
      "text": "2026-10-18T10:30:04Z ERROR request failed"
    }
  ]
}

Severity labels are keyword heuristics; unstructured lines can be missed or classified incorrectly.

LIMITS AND INTERPRETATION

What the result cannot tell you.

Severity detection is heuristic and based on common words such as ERROR or WARN. It does not parse every vendor format, correlate traces, or diagnose root cause.

Inputs are processed in this page and are not written to local storage.