REPORT_LOGGER.CONF(5)
π REPORT_LOGGER.CONF β the libreport config file, explained by your resident Unix girlie π
okay so bestie, welcome to report_logger.conf(5), part of the LIBREPORT MANUAL. This is the glow-up doc for the config file that tells libreport which work flow definitions get to show up when a problem needs analyzing β and then export all that problem data info out to a text file. π
β¨ NAME β¨
report_logger.conf β the configuration file for libreport. that's it. that's the name. iconic, brief, main character energy. π¦
πΈ DESCRIPTION πΈ
so here's the vibe: this config file is literally the guest list. it specifies which of the work flow definitions are applicable to analyzing problems and exporting the problem data information to a text file. πβ¨
All the applicable work flows get presented to users in the User Interface as possibilities for processing of any problems. like, the UI shows your user all the options that made the cut. and a particular work flow only becomes applicable if its conditions are satisfied β no conditions met, no invite to the party. π ββοΈ
This configuration file consists of condition lines. each condition line has to start with EVENT=workflow_NAME β where workflow_ is a constant prefix and workflow_NAME is the base name of the path to the reporting work flow configuration file. lowkey simple, highkey important. π«Ά
The rest of the condition line has the form VAR=VAL, VAR!=VAL or VAL~=REGEX, where VAR is a name of problem directory element to be checked (for example, "executable", "package", "hostname" etc). and a condition may consist of as many element checks as it is necessary β pile 'em on, queen. π§
β οΈ important one, ngl: all condition lines in this configuration file are commented out by default. therefore all applicable work flows from this file are not presented to users in the User Interface. if you wanna enable this extension, uncomment all condition lines in this configuration file. periodt.
π EXAMPLES π
here's a condition line, fresh out the group chat:
EVENT=workflow_LoggerCCpp analyzer=CCpp
The condition line above expects existence of /usr/share/libreport/workflows/workflow_LoggerCCpp.xml. that's the whole assignment β that file's gotta be there. πβ¨
π SEE ALSO π
report-gtk(1)β go say hi to the sibling page, iykyk π
π AUTHOR π
- ABRT team β the legends behind this whole thing π«‘
cute lil sign-off: this page is from LIBREPORT 2.17.15, dated 07/15/2024 β so if you're reading this, it's the REPORT_LOGGER.CONF(5) you know and love, and now you fr fr understand it. slay, bestie, go uncomment those lines π
ππ¦
π¦ where this page comes from
- opensuse-leap 16.0: libreport-plugin-logger 2.17.15-bp160.1.14 Β· GPL-2.0-or-later
- opensuse-leap 16.0: libreport-plugin-logger 2.17.15-bp160.1.14 Β· GPL-2.0-or-later
- opensuse-leap 16.0: libreport-plugin-logger 2.17.15-bp160.1.14 Β· GPL-2.0-or-later
- opensuse-leap 16.0: libreport-plugin-logger 2.17.15-bp160.1.14 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms