Logs: structured entries, level/component filters, live tail and export #229

Closed
opened 2026-11-17 15:05:00 +00:00 by jcoffey-dev · 1 comment
Owner

From a forum request (topic 308): make the Logs page easier to work with.

Asked for:

  • structured entries with expandable fields instead of one long text line
  • color-coded levels (ERROR, WARN, INFO, DEBUG)
  • filters by level, time range, component and free text
  • live streaming with pause/resume
  • download/export of the filtered entries

Notes:

  • Build on the existing tracers rather than a separate logging system.
  • Server side: the Log tracer writes plain text today. A JSON (one object per line) format option would let the console show fields without parsing text, and suits container/Kubernetes log collectors too. That part needs an inbuxa-server issue when this is picked up.
From a forum request (topic 308): make the Logs page easier to work with. Asked for: - structured entries with expandable fields instead of one long text line - color-coded levels (ERROR, WARN, INFO, DEBUG) - filters by level, time range, component and free text - live streaming with pause/resume - download/export of the filtered entries Notes: - Build on the existing tracers rather than a separate logging system. - Server side: the Log tracer writes plain text today. A JSON (one object per line) format option would let the console show fields without parsing text, and suits container/Kubernetes log collectors too. That part needs an inbuxa-server issue when this is picked up.
jcoffey-dev added this to the 27.7 milestone 2026-11-17 15:05:00 +00:00
jcoffey-dev added the enhancement
priority
p3
labels 2026-11-17 15:05:00 +00:00
jcoffey-dev self-assigned this 2026-11-17 15:05:00 +00:00
Author
Owner

Thanks to StefanSa for the request in forum t/308. Done in #244, with inbuxa/inbuxa-server#455 on the server side:

  • Each log entry opens to show its fields, split out of the tracer's key = value text.
  • Levels are shown in colour.
  • Filters: level and above, component (smtp matches smtp.* but not smtps.*), text, and a from/to time.
  • Follow live, with Pause, checks for new entries every 5 seconds while the tab is open.
  • Save as file saves up to 5,000 filtered entries as JSON lines or plain text.

As before, entries come from the node that answered, so a cluster still has one log per node. A JSON line format for the Log tracer itself is now inbuxa/inbuxa-server#456. Text filtering works with older servers; the level, component and time filters need the next server release. Both parts ship in the next console and server RCs.

Thanks to StefanSa for the request in forum t/308. Done in #244, with inbuxa/inbuxa-server#455 on the server side: - Each log entry opens to show its fields, split out of the tracer's `key = value` text. - Levels are shown in colour. - Filters: level and above, component (`smtp` matches `smtp.*` but not `smtps.*`), text, and a from/to time. - **Follow live**, with Pause, checks for new entries every 5 seconds while the tab is open. - **Save as file** saves up to 5,000 filtered entries as JSON lines or plain text. As before, entries come from the node that answered, so a cluster still has one log per node. A JSON line format for the Log tracer itself is now inbuxa/inbuxa-server#456. Text filtering works with older servers; the level, component and time filters need the next server release. Both parts ship in the next console and server RCs.
jcoffey-dev modified the milestone from 27.7 to 27.1 2026-11-19 16:29:46 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: inbuxa/inbuxa-admin#229