21.4.2. Standard ABRT Installation Supported Events

Standard ABRT installation currently provides a number of default analyzing, collecting and reporting events. Some of these events are also configurable using the ABRT GUI application (for more information on event configuration using ABRT GUI, refer to Section 21.4.3, “Event Configuration in ABRT GUI”). ABRT GUI only shows the event's unique part of the name which is more readable the user, instead of the complete event name. For example, the analyze_xsession_errors event is shown as Collect .xsession-errors in ABRT GUI. The following is a list of default analyzing, collecting and reporting events provided by the standard installation of ABRT:

analyze_LocalGDB — Local GNU Debugger: Runs GDB (the GNU debugger) on problem data of an application and generates a backtrace of a program. It is defined in the /etc/libreport/events.d/ccpp_event.conf configuration file.
analyze_xsession_errors — Collect .xsession-errors: Saves relevant lines from the ~/.xsession-errors file to the problem report. It is defined in the /etc/libreport/events.d/ccpp_event.conf configuration file.
report_Logger — Logger: Creates a problem report and saves it to a specified local file. It is defined in the /etc/libreport/events.d/print_event.conf configuration file.
report_RHTSupport — Red Hat Customer Support: Reports problems to the Red Hat Technical Support system. This possibility is intended for users of Red Hat Enterprise Linux. It is defined in the /etc/libreport/events.d/rhtsupport_event.conf configuration file.
report_Mailx — Mailx: Sends a problem report via the Mailx utility to a specified email address. It is defined in the /etc/libreport/events.d/mailx_event.conf configuration file.
report_Kerneloops — Kerneloops.org: Sends a kernel problem to the oops tracker. It is defined in the /etc/libreport/events.d/koops_event.conf configuration file.
report_Uploader — Report uploader: Uploads a tarball (.tar.gz) archive with problem data to the chosen destination using the FTP or the SCP protocol. It is defined in the /etc/libreport/events.d/uploader_event.conf configuration file.