Quick answer
The analyzer detects log levels by common keywords: ERROR, FATAL, WARN, WARNING, INFO, DEBUG, TRACE.
Log Lines Not Detected by Level
The analyzer detects log levels by common keywords: ERROR, FATAL, WARN, WARNING, INFO, DEBUG, TRACE. If your log format uses different labels (e.g. SEVERE, NOTICE) or no level at all, those lines are grouped as "Other".
Common causes
- Custom log level names (e.g. SEVERE, NOTICE, VERBOSE) instead of ERROR/INFO.
- Log format without a level field (e.g. plain timestamps and messages).
- Level in a different language or abbreviated differently.
How to fix
- Use standard keywords in log output when possible: ERROR, WARN, INFO, DEBUG, TRACE.
- If you control the logger, configure it to emit these level names so the analyzer can categorize.
- For custom formats, you still get total lines and empty lines; only the per-level breakdown may show mostly "Other".
Examples
Bad
SEVERE: Connection failed
Good
[ERROR] Connection failed
FAQ
- Can I analyze JSON logs?
- Yes. If the JSON contains level fields or level keywords in the message (e.g. "level": "error" or message with "ERROR"), those lines can be categorized. The analyzer looks for keywords in the full line text.
- What is the max log size?
- Input is limited to 50,000 characters. For larger files, split or sample the log before pasting.
Fix it now
Try in validator (prefill this example)