Log Analyzer
Parse supported log files, filter records and export matching entries.
Find the signal. Follow the story.
Drop .log or .txt here
Awaiting log data...
A little less noise.
A clearer trail.
Inspect recognised log records, compare recurring sources and paths, and follow the lines behind a summary.
How to explore a log file
- Load a log. Choose a .log or .txt file, or try the sample. Use one supported format per file.
- Check recognition. Review recognised and unmatched counts. Inspect unmatched lines by original line number to understand parser coverage.
- Follow a pattern. Explore sources and errors, then combine Raw Explorer search with status/severity and IP/host filters. Dashboard summaries still cover all recognised records.
- Keep the evidence. Export all matching recognised lines as text or parsed CSV, and unmatched lines separately as CSV. Keep the original log; summaries do not establish attack intent or incident severity.
Which log formats are supported?
Load .log or .txt files containing Apache/Nginx-style access records or a traditional Syslog pattern. The first 50 lines determine one parser mode. If none match, the file is rejected; custom, JSON and mixed-format logs are not universally supported.
How are recognised and unmatched lines counted?
Dashboard summaries cover all recognised records. Nonempty lines that fail the detected pattern are counted separately; blank lines are excluded. Inspect unmatched lines to see their original source line numbers, including intervening blank lines. That inspector is independent of Raw Explorer filters.
What do Explorer filters change?
Case-insensitive text search combines with exact status/severity and an exact IP/host value using AND. Suggestions list only the 100 most frequent sources; other sources remain filterable by typing their exact value. They filter Raw Explorer and its exports only, not dashboard totals or summaries. Results display 200 lines per page; Clear explorer filters restores all recognised records.
What can I export, and are summaries security diagnoses?
Export all matching recognised records across pages as text lines with line endings normalized to LF, or mode-specific parsed CSV. Export unmatched lines separately with source line numbers. Summaries are investigation clues, not proof of an attack. Syslog severity is inferred from recognised process-text suffixes, not a complete severity decoder.
Are my logs uploaded or saved?
Analysis runs in browser memory; chart libraries are served from this site. Work is not automatically saved and device memory limits apply. Logs can contain sensitive IPs and messages; keep original files and review exported content before sharing. This is not a live monitoring service.