On Tue, May 20, 2025 at 10:13:32AM +0200, Etienne Doms wrote:
> Hi,
>
> We're developing an embedded application which is run through a
> systemd service, and we use sd-journal for logging.
>
> We just figured out that something is not scaling up: we log at INFO
> level things like "user pushed t
I don't know about journald's design performance, but at "every 40ms", I'd
probably second the suggestion to switch to something else for DEBUG-level
stuff (while perhaps keeping regular journald for regular INFO messages),
although instead of periodic-rotation-based logs consider some kind of
"rin
Hi,
We're developing an embedded application which is run through a
systemd service, and we use sd-journal for logging.
We just figured out that something is not scaling up: we log at INFO
level things like "user pushed that button so we did that" (which
occurs once in a while) and at DEBUG level
I would like to second this - that having different policies for different
log levels can be very useful. Also filtering these during log view.
On Tue, May 20, 2025 at 11:14 AM Etienne Doms
wrote:
> Hi,
>
> We're developing an embedded application which is run through a
> systemd service, and we
