28.4.9. Configuring Automatic Reporting
- Once enabled, μReports are sent automatically, without user interaction. In contrast, the normal reports are not sent until manually triggered by the user.
- μReports are anonymous and do not contain sensitive information. This eliminates the risk that unwanted data will be submitted automatically.
- A μReport represents the detected problem as a JSON object. Therefore, it is machine-readable and can be created and processed automatically.
- μReports are smaller than full bug reports.
- μReports do not require downloading large amounts of debugging 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
- for kernel oops, possibly information about host hardware
WarningDo not enable μReports if you do not want to share information about your hardware with Red Hat.
- ABRT submits a μReport 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.
AutoreportingEnabled = yes
$USER/.config/abrt/directory. It overrides the system-wide configuration.
service abrtd restart
AutoreportingEventdirective in the
/etc/abrt/abrt.confconfiguration file. See Section 28.4.2, “Standard ABRT Installation Supported Events” for an overview of the standard events.
/etc/machine-idfile), and RHN account number. The advantage of authenticated μReports 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 μReports do. This enables Red Hat to provide customers with instant solutions to crashes.
abrt-auto-reporting enabled -uRHN_username