返回首页
博客

日志查看器

分析和过滤日志文件

总计:0
错误:0
警告:0
信息:0
调试:0

日志条目 (0)

未找到日志

请上传日志文件或调整筛选条件

日志详情

未选择日志

点击日志条目查看详情

日志查看器功能

  • • 自动解析常见日志格式
  • • 按日志级别筛选(ERROR, WARN, INFO, DEBUG)
  • • 搜索日志消息和来源
  • • 基于时间筛选(最近一小时、一天、一周)
  • • 查看原始日志行或解析格式
  • • 将筛选后的日志导出为 JSON
  • • 实时统计与计数
  • • 支持多种日志格式和时间戳

About the Log Viewer

Reading raw log files is tedious the moment they grow past a few hundred lines — everything runs together in a monospace wall of text, and finding the one error line buried among thousands of INFO entries turns into a scroll-and-squint exercise. The Log Viewer is a browser-based tool for opening a log file and actually making sense of it: it splits each line into timestamp, level, source and message, colours the level (red for ERROR, yellow for WARN, blue for INFO, grey for DEBUG), and lets you narrow thousands of lines down to the few that matter. It's built for developers, sysadmins, and support engineers who need to dig through application, server, or system logs without installing a desktop app or piping files through grep and less on the command line.

The parser recognises the common application-log layouts: a date and time followed by a [LEVEL] and an optional [Source], an ISO timestamp in brackets followed by LEVEL Source: message, LEVEL followed by a timestamp, and a bare LEVEL: message. Lines in any other shape still load as INFO entries, so free-text search works on every file. Once a .log or .txt file is loaded you can combine four filters (level, source, a relative time window, and a text search over messages and sources), and the entry count updates with them. Filtering happens live, so you can tighten or loosen a view without reloading the file.

All parsing and filtering happens client-side in your browser, so log content never leaves your machine unless you choose to share it — a meaningful point for anyone working with logs that contain internal hostnames, IPs, or other sensitive operational details. There's no signup and no file upload to a server involved. A practical habit: start with the level filter set to Error, open the first entry in the details panel to read its raw line, then switch the level back to All and search for the request ID or service name from that line to see what happened around it.

How to view and analyze a log file

Load a log file into the Log Viewer and use the level, source, time and text filters to find what matters.

  1. 1

    Open your log file

    Click Upload and choose a .log or .txt file, or click Sample to try the tool on a built-in example log.

  2. 2

    Let it parse the entries

    Each line is split into timestamp, level, source and message when it follows a common layout such as 2026-03-02 14:05:09 [ERROR] [Service] message; other lines are kept as INFO entries.

  3. 3

    Search for what you need

    Type a keyword, error code, or request ID into the search field; it matches the message and source of each entry.

  4. 4

    Apply filters

    Narrow the list with the level menu (Error, Warning, Info, Debug), the source menu, and the Last Hour / Last Day / Last Week time window.

  5. 5

    Inspect an entry

    Click any entry to see its timestamp, source, message and raw line in the Log Details panel, and copy the raw line from there. The Raw button switches the whole list to unparsed lines.

  6. 6

    Export what you found

    Click Export to save the currently filtered entries, with the filter settings, as a JSON file you can share.

Frequently Asked Questions

What log formats does the viewer support?

It parses plain-text application logs where each line carries a level: for example 2026-03-02 14:05:09 [ERROR] [Service] message, [2026-03-02T14:05:09Z] ERROR Service: message, ERROR 2026-03-02 14:05:09 message, or ERROR: message. JSON lines, Apache/Nginx access logs and syslog are loaded one entry per line and can be searched, but their fields are not extracted.

Can I filter log entries by severity level?

Yes. The level menu filters to ERROR, WARN, INFO or DEBUG, and it combines with the source menu, a Last Hour / Last Day / Last Week window and a plain-text search. Levels outside those four, such as FATAL or TRACE, are treated as INFO. Search is plain text, not regex.

Is my log data sent to any server?

No, all log processing happens entirely in your browser. Your log data is never uploaded or transmitted anywhere. This makes the tool safe to use with sensitive production logs.