`phosphor-logging` APIs (RFC)

Patrick Williams patrick at stwcx.xyz
Wed Jul 28 16:25:17 AEST 2021

On Wed, Jul 28, 2021 at 03:22:43PM +0930, Andrew Jeffery wrote:
> On Wed, 28 Jul 2021, at 05:54, Patrick Williams wrote:
 >     - Source location data is invalid (issue openbmc/openbmc#2207).
> I think you wanted openbmc/openbmc#2297 there, but yes!

Indeed, that's the issue I meant to refer to.  Seems I mentioned it correctly in
the commit.

> >     - Useful data is missing from `journalctl` resulting in people working
> >       around it by generating strings with `fmt` et.al.
> Sounds promising! Reading the proposal it seems like you're appending 
> certain bits of structured data to the message. I think it would be 
> nice if the data could be interpolated into arbitrary positions and not 
> just appended (note, I'm not asking for interpolation of arbitrary 
> variables here unlike what can be achieved with raw use of fmt, only 
> those captured via the structured logging).

Can you give me a concrete example of what you mean by this?  I'm not

> Andrew

Patrick Williams
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20210728/7fc1633e/attachment.sig>

More information about the openbmc mailing list