28.4.9. Configuring Automatic Reporting ABRT can be configured to use mReports . This additional type of bug report has these advantages: Once enabled, mReports are sent automatically , without user interaction. In contrast, the normal reports are not sent until manually triggered by the user. mReports are anonymous and do not contain sensitive information . This eliminates the risk that unwanted data will be submitted automatically. A mReport represents the detected problem as a JSON object. Therefore, it is machine-readable and can be created and processed automatically. mReports are smaller than full bug reports. mReports do not require downloading large amounts of debugging information. mReports serve several goals. They help to prevent duplicate customer cases that might get created because of multiple occurences of the same bug. Additionally, mReports enable gathering statistics of bug occurences and finding known bugs across different systems. Finally, if authenticated mReports are enabled as described at the end of this section, ABRT can automatically present instant solutions to the customers. However, mReports do not necessarily provide engineers with enough information to fix the bug, for which a full bug report may be necessary. A mReport generally contains the following information: a call stack trace of a program without any variables, or, in case of multi-threaded C, C++, and Java programs, multiple stack traces which operating system is used versions of the RPM packages involved in the crash whether the program ran under the root user for kernel oops, possibly information about host hardware Warning Do not enable mReports if you do not want to share information about your hardware with Red Hat. For mReport examples, see the Examples of mReports article. With mReports enabled, the following happens by default when a crash is detected: ABRT submits a mReport with basic information about the problem to Red Hat's ABRT server. The server determines whether the problem is already in the bug database. If it is, the server returns a short description of the problem along with a URL of the reported case. If not, the server invites the user to submit a full problem report. To enable mReports for all users, run as root : or add the following line to the /etc/abrt/abrt.conf file: User-specific configuration is located in the USDUSER/.config/abrt/ directory. It overrides the system-wide configuration. To apply the new configuration, restart the ABRT services by running: The default autoreporting behavior - sending mReports - can be changed. To do that, assign a different ABRT event to the AutoreportingEvent directive in the /etc/abrt/abrt.conf configuration file. See Section 28.4.2, "Standard ABRT Installation Supported Events" for an overview of the standard events. In Red Hat Enterprise Linux 7.1 and later, customers can also send authenticated mReports, which contain more information: hostname, machine-id (taken from the /etc/machine-id file), and RHN account number. The advantage of authenticated mReports is that they go directly to the Red Hat Customer Portal, and not only to Red Hat's private crash-report server, as the regular mReports do. This enables Red Hat to provide customers with instant solutions to crashes. To turn the authenticated automatic reporting on, run the following command as root : Replace RHN_username with your Red Hat Network username. This command will ask for your password and save it in plain text into the /etc/libreport/plugins/rhtsupport.conf file.

Commands:
~]# abrt-auto-reporting enabled
AutoreportingEnabled = yes
~]# service abrtd restart
~]# abrt-auto-reporting enabled -u RHN_username