The journald design is horrible to the point of useless

Posted Nov 21, 2011 8:29 UTC (Mon) by aleXXX (subscriber, #2742)
In reply to: The journald design is horrible to the point of useless by michich
Parent article: That newfangled Journal thing

If you replace "insist on using unreadable UUIDs" with "recommend on using unreadable UUIDs" this doesn't really make it better, the part with the unreadable is still there.

Alex

to post comments

The journald design is horrible to the point of useless

Posted Nov 21, 2011 8:52 UTC (Mon) by michich (guest, #17902) [Link] (2 responses)

The UUID does not replace the human-readable text of the message. It is an optional addition to it.

The journald design is horrible to the point of useless

Posted Nov 21, 2011 11:47 UTC (Mon) by vrfy (guest, #13362) [Link] (1 responses)

Right, the UUIDs are just attached to general useful messages which are meant to be recognized by machines. In these cases the UUID + the key/values replace the unreliable regex log parsing.

The human readable part of the message is still passed to syslog the same way as is always was.

The text says: "Most projects will probably never generate more than 30 of these during their entire development time", which should illustrate that this is in no way *every* message.

But hey, why reading the text when you can match on a few keywords, mix some random things from your head into it, and start talking?

The journald design is horrible to the point of useless

Posted Nov 23, 2011 23:01 UTC (Wed) by dlang (guest, #313) [Link]

so why create an entirely new way to log instead of just putting your UUID in your 'regular' log message?