.NET structured log investigation
Serilog Analyzer
Explore Serilog events, group repeated errors, search properties and trace IDs, and inspect complete exceptions without uploading your logs.
Drop a log file here
.log, .txt, .json, .jsonl, .ndjson, or .clef · format is detected from content
Paste logs instead
Serilog formats supported
Open newline-delimited JsonFormatter output, CompactJsonFormatter (CLEF), RenderedCompactJsonFormatter, and common file or console text layouts with timestamps and bracketed levels. Arbitrary custom output templates and top-level JSON arrays are not supported. UTF-8 text is expected.
Inspect every event
Open a record to see its complete original entry, exception and inner-exception traces, message template, and structured properties. Rendered messages are shown when recorded; otherwise the original template is shown without inventing formatted values. SourceContext, event IDs, trace and span IDs, and nested properties remain available in metadata and full-text search.
Investigate large logs
Summary counts cover the whole file. Record searches run in a background worker and return 100 entries per page. Changing a filter or page rescans the local file to keep record memory bounded. Time-only console timestamps remain time-only; no date is invented. Warnings and events containing exceptions are included in the issue count.
Private, local log analysis
Files are sliced and processed by a Web Worker in your browser. ToolsWeave does not upload log content, filenames, IP addresses, URLs, messages, or stack traces. Exports are also generated locally.
Serilog Analyzer FAQ
Which Serilog levels are recognized?
Verbose, Debug, Information, Warning, Error, and Fatal, including their common three-letter text abbreviations. Omitted CLEF levels are Information.
Can I inspect nested exceptions and custom properties?
Yes. Open View details on any event to inspect complete exception text, nested JSON properties, and the original log entry. Copy or download the original entry locally.
Are log files uploaded?
No. Analysis runs in a browser Web Worker and the selected file is read in local chunks.
Can I analyze a large log file?
Yes. File input is chunked and aggregate counters are built incrementally. Full-file searches return 100 records per page and rescan the source when filters or pages change. Actual limits depend on the browser, individual entry size, and device.
Related log tools
Online Log Analyzer · JSON Log Analyzer · Error Log Analyzer
Browse all developer tools.