← All featuresLog Viewer

A log viewer that brings the failure into focus.

Inspect JSON, syslog, Apache, Nginx and application logs in Flame IDE. Filter entries, explore timelines and ask AI about errors.

Logs Viewer inspecting sample checkout API logs. Desktop and tablet show the entry inspector; mobile focuses on the log list. Select the image to enlarge.
WHY IT HELPS

Go from noisy output to useful evidence.

Open a log file, paste an excerpt, or inspect output from Docker, a terminal, or Flame itself. The viewer detects common formats and turns logs into searchable entries alongside your code.

Find the relevant entries

Search terms, quoted phrases, exclusions, case matching or regex. Combine severity, structured fields and time filters, then inspect the original entry and its fields.

Ask AI about the logs

Ask a question with a masked sample of matching entries attached. The agent can read more from the viewer and request filter changes, which require your confirmation.

Inspect and share

Use the Activity timeline, switch between structured and raw views, refresh supported sources, and export matching entries as CSV or JSON Lines.

LOG VIEWER IN PRACTICE

Supported log formats

Flame detects common formats automatically and falls back to plain or timestamped text when a specific format is not recognized. Text and gzip files, UTF-16 and supported legacy encodings are accepted.

JSON and structured logs

JSON documents, JSON Lines / NDJSON, multiline JSON objects, and logfmt. Includes common JSON output from Pino, Bunyan, Winston, ECS, Docker and journald.

Web and system logs

Syslog RFC 5424 and BSD / RFC 3164; Apache and Nginx access and error logs; W3C extended logs used by IIS and CloudFront.

Containers and applications

Kubernetes glog / klog, CRI container logs, Android logcat, basic Python logging, Ruby Logger, Redis and legacy MongoDB text logs.

Delimited and plain text

CSV, TSV, semicolon- and pipe-delimited logs, and plain or timestamped text. Supported multiline entries and stack traces stay together.

LOG VIEWER IN PRACTICE

Investigate the problem in context.

Combine filters to narrow the incident, then inspect or share the evidence.

Find the right time window

Use the Activity chart, time presets from 5 minutes to 30 days, or a custom range with millisecond precision. Switch between UTC and local time; time-only logs support day offsets.

Inspect and refresh

Select a row to see the original entry and filter by field value. Switch to read-only Raw text and use Ctrl/Cmd+F to find text. Docker, terminal and Flame log sources support manual and optional 2.5-second auto-refresh.

Ask AI

With logs loaded, choose Ask AI and enter your question. A bounded sample of matching entries and filter context is staged for the chat, with secrets masked even if revealed in the viewer. The agent can read more matching entries and request filter changes with confirmation.

Export with masking

Export matching entries as CSV or JSON Lines. Secrets are masked by default; exports respect the viewer's current reveal setting, so check it before sharing.

HOW TO USE IT

Start investigating.

  1. Load logs

    Open Logs Viewer from New tab → More tabs and open, drop or paste logs. Or choose Open in Logs Viewer from a Docker container or terminal.

  2. Narrow the results

    Search for an error or request ID, choose a time range, and filter by severity or structured field. Select an entry for its original text and details.

  3. Ask or export

    Choose Ask AI and send your question with masked matching entries, or export the filtered results as CSV or JSON Lines.

REQUIREMENTS & LIMITS

Know what the tool depends on.

  • Files are parsed by Flame's authenticated backend on the IDE host. The viewer does not persist parsed entries or uploaded file paths. AI questions are sent through your configured provider when you send the chat.
  • Uploads are limited to 25 MiB, gzip expansion to 100 MiB, and parsing to 200,000 entries and 256 KiB per line. Warnings report truncation.
  • Live views use bounded snapshots: up to 5,000 Docker lines, the terminal's 256 KiB buffer, or the latest 1 MiB of Flame app and native logs. File logging must be enabled to capture new backend logs.
FAQ

Log Viewer: common questions