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
tracing: Emit native journal MESSAGE_ID for lifecycle events
bootc already routes INFO tracing events to the journal (when run as
root), and a number of lifecycle events carry a `message_id` field with
a hardcoded 128-bit hex constant, intended to populate systemd's
well-known MESSAGE_ID so operators can query e.g.
`journalctl MESSAGE_ID=<id>` and hook the message catalog.
Two defects prevented this from working:
- tracing-journald prefixes all custom fields with `F_`, so the field
landed as `F_MESSAGE_ID` rather than the native MESSAGE_ID, and
`bootc.image.reference` as `F_BOOTC_IMAGE_REFERENCE`. Dropping the
prefix (with_field_prefix(None)) lets the layer's name sanitizer map
`message_id` -> MESSAGE_ID and `bootc.image.reference` ->
BOOTC_IMAGE_REFERENCE, while MESSAGE is left untouched.
- many of the id constants were 33 hex chars (132-bit), which systemd
rejects as a malformed MESSAGE_ID. Regenerate them as valid, unique
128-bit values (this also removes two accidental duplicates).
Prep for the unified-storage upgrade fix, which relies on these events
being usefully queryable in the journal.
Assisted-by: opencode (Claude Opus 4.8)
Signed-off-by: Colin Walters <walters@verbum.org>
0 commit comments