Log tracer: a JSON line format option #456
Closed
opened 2026-11-18 19:54:27 +00:00 by jcoffey-dev
·
1 comment
No Branch/Tag Specified
main
spec/client-gateway
feat/singleton-role-lease
release/2026
merge/upstream-v1.0.0
upstream
next
v27.1-rc.39
v2026.11.20.2
v27.1-rc.38
v2026.11.20.1
v27.1-rc.37
v27.1-rc.36
v27.1-rc.35
v2026.11.20
v27.1-rc.34
v27.1-rc.33
v27.1-rc.32
v27.1-rc.31
v2026.11.18.3
v27.1-rc.30
v2026.11.18.2
v27.1-rc.29
v2026.11.18.1
v27.1-rc.28
v2026.11.18
v2026.11.17
v27.1-rc.27
v27.1-rc.26
v27.1-rc.25
v27.1-rc.24
v27.1-rc.23
v27.1-rc.22
v2026.11.11
v27.1-rc.21
v27.1-rc.20
v27.1-rc.19
v27.1-rc.18
v2026.11.10
v27.1-rc.17
v2026.11.9.2
v2026.11.9.1
v2026.11.9
v27.1-rc.16
v27.1-rc.15
v27.1-rc.14
v27.1-rc.13
v27.1-rc.12
v27.1-rc.11
v27.1-rc.10
v27.1-rc.9
v27.1-rc.8
v27.1-rc.7
v27.1-rc.6
v27.1-rc.5
v27.1-rc.4
v2026.10.29.1
v27.1-rc.3
v2026.10.29
v27.1-rc.2
v27.1-rc.1
v2026.10.28
v2026.10.19
v2026.10.16
v2026.10.15
v2026.10.12.1
v2026.10.12
v2026.10.10.1
v2026.10.10
v2026.10.9
v2026.10.8.1
v2026.10.8
v2026.10.6.3
v2026.10.6.2
v2026.10.6.1
v2026.10.6
v2026.10.5.1
v2026.10.5
v2026.9.30.2
v2026.9.30.1
v2026.9.30
v2026.9.29.2
v2026.9.29.1
v2026.9.29
v2026.9.28.6
v2026.9.28.5
v2026.9.28.4
v2026.9.28.3
v2026.9.28.2
v2026.9.28.1
v2026.9.28
v2026.9.27.2
v2026.9.27.1
v2026.9.27
v2026.9.26.1
v2026.9.26
v2026.9.25.1
v2026.9.25
v2026.9.24.4
v2026.9.24.3
v2026.9.24.2
v2026.9.24
v2026.9.23
v2026.9.22
v2026.9.20
Labels
Clear labels
bug
dependencies
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs info
question
security
translation
wontfix
Something isn't working
Dependency updates
Docs, README or site copy
Already tracked elsewhere
New feature or improvement
Good for newcomers
Contributions welcome
Not a valid issue
Waiting on the reporter for details
Needs an answer, not a code change
Security issue or hardening
New language or translation fixes
Will not be worked on
priority
p1
High priority
priority
p2
Medium priority
priority
p3
Low priority
Projects
Clear projects
No projects
Assignees
jcoffey-dev (John Coffey)
Clear assignees
No Assignees
jcoffey-dev
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: inbuxa/inbuxa-server#456
Reference in new issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split out of inbuxa/inbuxa-admin#229 (forum t/308).
The Log tracer writes text only:
<time> <LEVEL> <description> (<event id>) key = value, …. The console's Logs page now splits those fields itself (inbuxa-admin#244), but the text isn't fully unambiguous (a quote inside a string isn't escaped), and log collectors (Loki, Vector, Kubernetes) want one JSON object per line.Proposal: a
formatsetting on the Log tracer,text(default, as today) orjson: one object per line withtimestamp,level,event,descriptionand the event's keys as typed values (nested events as objects, lists as arrays).x:Logreads either format, so the console's Logs page keeps working, and gets exact fields from JSON files.Done when
format = jsonwrites one JSON object per linex:Log/getandx:Log/query(incl. the #455 filters) read JSON files as well as textFixed in #462, with the Logs page side in inbuxa/inbuxa-admin#246. Thanks to StefanSa for asking for this in community t/308.
A Log tracer now has a Format setting: Text (the default, unchanged) or JSON lines, one object per line with
timestamp,level,event,descriptionand the event's fields underdataas typed values. The console's Logs page andx:Logread both formats, including a file that holds both after a switch, and show a JSON entry's fields exactly as written. The Console (stdout) tracer still writes text only.It ships in the next server and console release candidates.