Journal detail levels

The systemd journal is voluminous and most of it is not operationally
interesting. Journal lines are classified into lifecycle, health, access,
and other, and the detail parameter selects a cumulative ladder:

detail Includes
lifecycle (default) Service start, stop, failure, reload, main-process exit
+health Plus VPP state changes, heartbeats, IPMI activity
+access Plus HTTP access lines
all Everything

Unit attribution prefers the unit acted upon over the unit emitting, which is
usually the init scope, with a regular-expression fallback that recovers a unit
name from the message text.