View and filter JSON-structured logs with search, time range selection, severity filtering, and field extraction.
JSON log entries can contain useful evidence alongside a large amount of unrelated context. This viewer presents structured records and narrows them with text search, time-range selection, severity filtering, and field extraction. The common surprise is that JSON defines a data format, not a logging schema. Timestamp, severity, message, and identifier fields have no universal names or value conventions. A record can therefore be valid JSON while lacking the structure needed for a meaningful time filter, severity filter, or requested field extraction.
Search provides a textual criterion, while the time and severity controls constrain records using their corresponding log values. The visible set reflects the active filters rather than rewriting the supplied records. If an expected entry disappears, clear filters individually or widen the selected interval to determine which condition excluded it.
Field extraction surfaces named members from structured records, such as request_id, actor, or message, so relevant values can be compared without reading every property. It cannot invent a shared schema. A top-level message member differs from one nested inside another object, and level differs from severity. Missing or differently located properties remain absent from the extracted view.
No. Valid JSON guarantees syntactic structure, not a particular arrangement of log records. Time and severity filtering require suitable corresponding values, and field extraction requires the requested members to exist where expected. A valid document can still use unfamiliar field names, nesting, timestamp representations, or record packaging that prevents the desired operation.
No. This tool runs entirely in the browser, so the supplied log content is not uploaded for viewing, searching, time selection, severity filtering, or field extraction. That does not remove sensitive data from the records. Treat copied matches, screenshots, and manually saved results according to the same handling requirements as the original logs.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Generate strong, random passwords with customizable length, character sets, and complexity requirements.
Analyze password strength with entropy scoring, crack-time estimates, and improvement suggestions.
Create cryptographically random strings for API keys, tokens, salts, and unique identifiers.
Create QR codes for URLs, text, Wi-Fi credentials, vCards, and more with customizable size and colors.
Scan and decode QR codes from uploaded images or your device camera to extract embedded data.
Compute MD5, SHA-1, SHA-256, and SHA-512 checksums to verify file integrity and detect tampering.