Opened 4 months ago

#170 new enhancement

structured logging

Reported by: wiese Owned by: stuerze
Priority: normal Component: BNC
Version: Keywords: logging, monitoring


Currently the logfiles are not easy to parse, as they are not structured. Nowadays the logs are often JSON formated or key=value pairs separated by spaces.
JSON example line: {"level":"debug","time":"2023-12-07T08:03:47.162","sender":"SCP","message":"executed command \"/usr/local/bin/myHooks\", elapsed: 1.007732187s, error: <nil>"}

To facilitate the monitoring purposes with BNC, this should be introduced.
To discuss:

  • as new log to not break existing workflows?
  • new log with metrics only?
  • write to port instead of file?
  • ...

See #168 and #108.

Attachments (0)

Change History (0)

Modify Ticket

Change Properties
as new The owner will remain stuerze.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from stuerze to the selected user. Next status will be 'assigned'.
Next status will be 'needinfo'. The owner will be changed from stuerze to wiese.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from stuerze to anonymous. Next status will be 'accepted'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.