You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using systemd to manage Lighthouse and systemd does its own timestamping. It would make the logfiles nicer and smaller if there would be an option to disable the Lighthouse timestamping.
Present Behaviour
Currently the logfiles of systemd do look like this:
Mar 18 12:47:36 hostname lighthouse[1554781]: Mar 18 11:47:36.387 INFO New block received root: 0xdabf1994c1c90eb947fa16dfc7b303bbe0a6e03261462a7319b4e230d98559ee, slot: 3398336
Expected Behaviour
It would be nicer this way:
Mar 18 12:47:36 hostname lighthouse[1554781]: INFO New block received root: 0xdabf1994c1c90eb947fa16dfc7b303bbe0a6e03261462a7319b4e230d98559ee, slot: 3398336
Steps to resolve
I would suggest a new flag like --disable-timestamp-output. This should only affect the console output (stdout, stderr), not the Lighthouse logfiles.
Another option could be --log-format SYSTEMD, --log-format JSON does already exist.
The text was updated successfully, but these errors were encountered:
Description
I'm using systemd to manage Lighthouse and systemd does its own timestamping. It would make the logfiles nicer and smaller if there would be an option to disable the Lighthouse timestamping.
Present Behaviour
Currently the logfiles of systemd do look like this:
Expected Behaviour
It would be nicer this way:
Steps to resolve
I would suggest a new flag like
--disable-timestamp-output
. This should only affect the console output (stdout, stderr), not the Lighthouse logfiles.Another option could be
--log-format SYSTEMD
,--log-format JSON
does already exist.The text was updated successfully, but these errors were encountered: