Find Two Queue Errors in a Saved NDJSON Log
Admin ·
When a queue stalls, a shared log often contains recoverable records mixed with blank separators and broken lines. Identify the malformed line first, then make a separate export for the events you need to review.
Find the failure on line 4
Load the example and select Parse log with filters blank. The result shows six physical lines and four valid values. Line 3 is blank. Line 4 has an empty message value, which the parser reports at column 27. Line 6 is the valid JSON value null.
Turn on Report blank lines as errors and parse again. Lines 3 and 4 now have diagnostics, while the four valid records remain eligible for export.
NDJSON core specification and parsing rulesRFC 8259, JSON grammar and exact numeric interoperability
Filter the queue errors by severity and text
Enter error in Level or severity. The result selects lines 2 and 5. Line 2 uses uppercase ERROR in severity. Line 5 uses lowercase error in level.
Add drained in Source text contains and parse again. The combination keeps only line 5. This filter searches the original record text case insensitively, including JSON key names and escape spellings.
NDJSON core specification and parsing rulesRFC 8259, JSON grammar and exact numeric interoperability
Check the event ID and original line ending
Download matching records and reopen selected-log.ndjson as text. The one-record export contains the ID 9007199254740997 exactly. The tool copies the record’s original separator and preserves a missing final newline if the source ended that way.
Download diagnostics for counts and locations without cell values. Verify the reported line in the same saved source before fixing it. A UTF-8 BOM is tolerated at the start and is included when physical line 1 is exported.
NDJSON core specification and parsing rulesJSON Lines UTF-8 and line termination requirements
Common questions
Does a field buried inside a JSON object count as the log level?
Level filtering examines top-level level and severity keys. A source text search can match words elsewhere in the record.
Can I submit a live logging URL?
Open a local capture or paste saved log text. The parser operates on that supplied data.
Sources
Put it into practice.
- NDJSON Log Stream Parser
- JSON Lines Validator and Fixer
- NDJSON to CSV Converter
- NDJSON JSONL Compressor