ELOGIND.JOURNAL-FIELDS(7)

πŸ“¦
version 255.24 Β· 3 versions
, in alpine 3.24

πŸ’– NAME πŸ’–

elogind.journal-fields(7) β€” special journal fields rerouted to syslog by elogind, bestie. That’s the whole vibe: this page is the guest list of fields elogind actually forwards. πŸ’…

✨ DESCRIPTION ✨

Okay so picture this: systems that use elogind have no systemd-journald running. Not a single journald in sight. Applications that use structured log messages via sd-journal.h use specific variables for this structure. The following is a list of variables that are parsed by elogind and passed to syslog for logging. Slay.

Note: Fields not listed here are ignored and their information is thrown away. This may change in the future. So if your fave field isn’t on this list, it’s giving β€œnot invited” for now. πŸ’€

πŸŽ€ USER JOURNAL FIELDS πŸŽ€

User fields are fields that are directly passed from clients and stored in the journal. No middleman energy.

  • MESSAGE= β€” the human-readable message string for this entry. This is supposed to be the primary text shown to the user. It is usually not translated (but might be in some cases), and it is not supposed to be parsed for metadata. In order to encode multiple lines in a single log entry, separate them by newline characters (ASCII code 10), but encode them as a single MESSAGE= field. Do not add multiple values of this field type to the same entry (also see above), as consuming applications generally do not expect this and are unlikely to show all values in that case. So keep it one MESSAGE=, bestie. 🫢
  • PRIORITY= β€” a priority value between 0 ("emerg") and 7 ("debug") formatted as a decimal string. This field is compatible with syslog's priority concept. It’s giving severity scale, and honestly? iconic. πŸ”₯
  • CODE_FILE=, CODE_LINE=, CODE_FUNC= β€” the code location generating this message, if known. Contains the source filename, the line number and the function name. Basically the β€œwhere was this sent from” receipts. πŸ•΅οΈβ€β™€οΈ

🌈 SEE ALSO 🌈

  • elogind(8) β€” go hang out there too, bestie.

πŸ’… That’s the tea from elogind version 255.24 β€” source/version: elogind 255.24, manual footer: ELOGIND.JOURNAL-FIELDS(7), and this copy didn’t show a separate date, so no invented lore from me. No cap. periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from