Re: [EXT] Re: SyslogIdentifier= no flexible enough

["Windl, Ulrich" <u.windl@xxxxxx>]

Hi!

Why trying it, I got:
journalctl: unrecognized option '--output-fields=MESSAGE,_SYSTEMD_UNIT'

(seems to be a newer feature)

> -----Original Message-----
> From: systemd-devel <systemd-devel-bounces@xxxxxxxxxxxxxxxxxxxxx> On
> Behalf Of Carl Lei
> Sent: Friday, August 16, 2024 11:41 AM
> To: systemd-devel@xxxxxxxxxxxxxxxxxxxxx
> Subject: [EXT] Re:  SyslogIdentifier= no flexible enough
> 
> On Fri, 16 Aug 2024 09:34:57 +0000
> "Windl, Ulrich" <u.windl@xxxxxx> wrote:
> 
> > Hi!
> >
> > I'm running the same binary concurrently with different options using
> > timers and instances, and I have the problem that it's not obvious
> > which instance logged an error.
> >
> > Like this:
> > Aug 16 00:00:01 v04 systemd[1]: Started Check (auth-fail-xyz).
> > Aug 16 00:00:01 v04 systemd[1]: Started Check (grace-logins).
> > Aug 16 00:00:01 v04 systemd[1]: Started Check (grace-logins-xyz).
> > Aug 16 00:00:01 v04 systemd[1]: Started Check (pw-expiration-xyz).
> > Aug 16 00:00:01 v04 systemd[1]: Started Check (auth-fail).
> > Aug 16 00:00:01 v04 systemd[1]: Started Check (pw-expiration).
> > ...
> > Aug 16 00:00:01 v04 systemd[1]: Started Session 20118 of user root.
> > Aug 16 00:00:01 v04 systemd[1]: Started Session 20119 of user root.
> > Aug 16 00:00:01 v04 systemd[1]: Started Session 20120 of user root.
> > ...
> > Aug 16 00:00:01 v04 check[15985]: [0] notification_message: undefined
> > value of LAST_PW_CHANGE_T
> >
> > Now my obvious problem is: "Which instance created PID 15985?"
> 
> How do you like: journalctl -t check -o verbose
> --output-fields=MESSAGE,_SYSTEMD_UNIT?