systemd Developer Lennart Poettering lennart@poettering.net systemd.journal-fields 7 systemd.journal-fields Special journal fields Entries in the journal resemble an environment block in their syntax, however with fields that can include binary data. Primarily, fields are formatted ASCII strings, and binary formatting is used only where formatting as ASCII makes little sense. New fields may be freely defined by applications, but a few fields have special meaning. All fields with special meaning are optional. User fields are fields that are directly passed from clients and stored in the journal. MESSAGE= The human readable message string for this entry. This is supposed to be the primary text shown to the user. It is not translated, and is not supposed to be parsed for meta data. MESSAGE_ID= A 128bit message identifier ID for recognizing certain message types, if this is desirable. This should contain a 128bit id formatted as lower-case hexadecimal string, without any separating dashes or suchlike. This is recommended to be a UUID compatible ID, but this is not enforced, and formatted differently. Developers can generate a new ID for this purpose with journalctl --new-id. PRIORITY= A priority value between 0 (emerg) and 7 (debug) formatted as decimal string. This field is compatible with syslog's priority concept. CODE_FILE= CODE_LINE= CODE_FUNC= The code location generating this message, if known. Contains the source file name, the line number and the function name. SYSLOG_FACILITY= SYSLOG_IDENTIFIER= SYSLOG_PID= Syslog compatibility fields containing the facility (formatted as decimal string), the identifier string (i.e. "tag"), and the client PID. Fields prefixed with an underscore are trusted fields, i.e. fields that are implicitly added by the journal and cannot be altered by client code. _PID= _UID= _GID= The process, user and group ID of the process the journal entry originates from formatted as decimal string. _COMM= _EXE= _CMDLINE= The name, the executable path and the command line of the process the journal entry originates from. _AUDIT_SESSION= _AUDIT_LOGINUID= The session and login UID of the process the journal entry originates from, as maintained by the kernel audit subsystem. _SYSTEMD_CGROUP= _SYSTEMD_SESSION= _SYSTEMD_UNIT= _SYSTEMD_OWNER_UID= The contol group path in the systemd hierarchy, the systemd session ID (if any), the systemd unit name (if any) and the owner UID of the systemd session (if any) of the process the journal entry originates from. _SELINUX_CONTEXT= The SELinux security context of the process the journal entry originates from. _SOURCE_REALTIME_TIMESTAMP= The earliest trusted timestamp of the message, if any is known that is different from the reception time of the journal. The time in usec since the epoch formatted as decimal string. _BOOT_ID= The kernel boot ID for the boot the message was generated in, formatted as 128bit hexadecimal string. _MACHINE_ID= The machine ID of the originating host, as available in machine-id5. _HOSTNAME= The name of the originating host. During serialization into external formats the addresses of journal entries are serialized into fields prefixed with double underscores. Note that these aren't proper fields when stored in the journal, but addressing meta data of entries. __CURSOR= The cursor for the entry. A cursor is an opaque text string that uniquely describes the position of an entry in the journal and is portable across machines, platforms and journal files. __REALTIME_TIMESTAMP= The wallclock time (CLOCK_REALTIME) at the point in time the entry was received by the journal. This has different properties from _SOURCE_REALTIME_TIMESTAMP= as it is usually a bit later but more likely to be monotonic. __MONOTONIC_TIMESTAMP= The monotonic time (CLOCK_MONOTONIC) at the point in time the entry was received by the journal. To be useful as an address for the entry this should be combined with with boot ID in _BOOT_ID=. systemd1, journalctl1, journald.conf5