Logs: read the fields of an entry from a JSON log file #246

Merged
jcoffey-dev merged 1 commits from feat/456-json-log-fields into main 2026-11-18 22:00:20 +00:00
Owner

Part of inbuxa/inbuxa-server#456 (forum t/308).

A Log tracer can now write JSON lines (inbuxa-server #456, server PR to follow). For those entries x:Log hands back the event's fields as a JSON object in details instead of key = value text. The Logs page reads that object as written: strings as they are, and numbers, lists and nested events as JSON. Text entries parse as before, and a file holding both reads both.

The JSON export keeps a JSON entry's fields typed instead of turning them into strings.

Against a server without #456 nothing changes: details is never a JSON object there.

Checked locally: typecheck, lint, i18n:check, all 1137 tests (4 new), the three shell tests, build and notice-check.

Part of inbuxa/inbuxa-server#456 (forum t/308). A Log tracer can now write JSON lines (inbuxa-server #456, server PR to follow). For those entries `x:Log` hands back the event's fields as a JSON object in `details` instead of `key = value` text. The Logs page reads that object as written: strings as they are, and numbers, lists and nested events as JSON. Text entries parse as before, and a file holding both reads both. The JSON export keeps a JSON entry's fields typed instead of turning them into strings. Against a server without #456 nothing changes: `details` is never a JSON object there. Checked locally: typecheck, lint, i18n:check, all 1137 tests (4 new), the three shell tests, build and notice-check.
jcoffey-dev added 1 commit 2026-11-18 21:57:33 +00:00
Logs: read the fields of an entry from a JSON log file
ci / build (pull_request) Skipped
ci / publish (pull_request) Skipped
ci / notices (pull_request) Successful in 1m3s
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 2m38s
f85fda5cfb
A Log tracer can write JSON lines (inbuxa-server #456). For those entries
the server hands back the event's fields as a JSON object in `details`
instead of `key = value` text, so the Logs page reads them as written:
strings as they are, numbers, lists and nested events as JSON. Text
entries are parsed as before, and a file holding both reads both.

The JSON export keeps a JSON entry's fields typed rather than as strings.

Test: parseFields and jsonFields on JSON objects, other JSON and plain
text; the export keeps typed fields.
jcoffey-dev merged commit 6d49081b99 into main 2026-11-18 22:00:20 +00:00
jcoffey-dev deleted branch feat/456-json-log-fields 2026-11-18 22:00:20 +00:00
Sign in to join this conversation.