REPORTER-SYSTEMD-J(1)

💖 reporter-systemd-journal — the LIBREPORT manual, but make it make sense 💖

okay bestie, so this page is REPORTER-SYSTEMD-J(1) from the LIBREPORT manual, and it's literally all about yeeting your problem info straight into the systemd journal. buckle up 🎀

---

✨ NAME ✨

reporter-systemd-journal — reports problem information into systemd journal. that's it, that's the vibe 💅

---

🌸 SYNOPSIS 🌸

reporter-systemd-journal [-v] [-d DIR] [-m MESSAGEID] [-F FMTFILE] [-p NONE|ESSENTIAL|FULL] [-s SYSLOGID]

---

🦋 DESCRIPTION 🦋

so the tool reads the problem directory DIR and sends all its deets into systemd journal as a message. slay. and if MESSAGEID is defined, the tool also creates a catalog message. icon behavior. and by parameter -p you can specify how much detailed the report will be — like how much tea gets spilled 🍓

example, in all its glory:

Catalog message:
-- 13a16aacbc85495c96e3627cc64f5263
Subject: testing reporter-systemd-journal message
Defined-By: libreport

Testing reporter-systemd-journal catalog message
@PROBLEM_REPORT@
This usually indicates a programming error in the crashing program.

Formatting file:
%summary:: Formatting reporter-systemd-journal message
::%bare_%short_backtrace

Reporting:
# reporter-systemd-journal --message-id 13a16aacbc85495c96e3627cc64f5263 -F $FORMATTING_FILE

Systemd journal catalog message:
Sep 27 16:50:49 dhcp-24-126.brq.redhat.com reporter-systemd-journal[31675]: Formatting reporter-systemd-journal message
-- Subject: testing reporter-systemd-journal message
-- Defined-By: libreport
--
-- Testing reporter-systemd-journal catalog message
--
-- #1 crash in /usr/bin/will_segfault
-- #2 varargs in /usr/bin/will_segfault
-- #3 f in /usr/bin/will_segfault
-- #4 callback in /usr/bin/will_segfault
-- #5 call_me_back in /usr/lib64/libwillcrash.so.0.0.0
--
-- This usually indicates a programming error in the crashing program.

ngl that backtrace example is giving main character energy 😭 will_segfault literally doing what it says on the tin 💀

---

💜 OPTIONS 💜

• -d DIR — path to problem directory. where the problem lives, bestie 🏠
• -m MESSAGEID, --message-id MESSAGEID — catalog message id. that's the ID for the catalog message 🎀
• -F FMTFILE — formatting file for systemd journal catalog message. the file that does the cute little formatting ✨
• -p NONE|ESSENTIAL|FULL, --dump NONE|ESSENTIAL|FULL — defines how much detailed the report will be:
  • NONE means only default problem details, as reason, pid etc., are sent into journal.
  • ESSENTIAL means less important problem details are sent as well.
  • FULL means all text problem dir details are sent into journal.

tl;dr: NONE is the bare minimum, ESSENTIAL is the mid tier, FULL is the whole entire lore drop 📖

• -s SYSLOGID, --syslog-id SYSLOGID — define SYSLOD_IDENTIFIER systemd journal field. (yes it says SYSLOD_IDENTIFIER, that's the field name, don't come for me 🙈)
• -v — be more verbose. can be given multiple times. stack them like little verbose bracelets 💫

---

🌈 ENVIRONMENT VARIABLES 🌈

• REPORTER_JOURNAL_SYSLOG_ID — define SYSLOD_IDENTIFIER systemd journal field. same deal as -s but via the environment, iykyk 🧚

---

⭐ SEE ALSO ⭐

journalctl(1), systemd.journal-fields(7) — go read these, they're the supporting cast 🫶

---

👑 AUTHORS 👑

• ABRT team 💖

---

and that's the whole page, no cap. LIBREPORT 2.17.15, dated 07/15/2024 — mwah, go report some problems into that journal bestie 💅✨