ABRT Analytics collects reports from ABRT and aggregates them. Developer or DevOps admin can sort them using number of occurences and see all similar reports.
ABRT Analytics collects thousands of reports a day serving needs of three different projects:
Live ABRT Analytics instances:
ABRT Analytics is part of the ABRT project
ABRT Analytics was originally named FAF (Fedora Analysis Framework).
Currently, the typical crash reporting workflow consists of generating so-called µReport (micro-report) designed to be completely anonymous so it can be sent and processed automatically avoiding costly Bugzilla queries and manpower.
ABRT Analytics in this scenario works like the first line of defense — collecting massive amounts of similar reports and responding with tracker URLs in case of known problems.
If a user is lucky enough to hit a unique issue not known by ABRT Analytics, reporting chain continues with reporting to Bugzilla, more complex process which requires user having a Bugzilla account and going through numerous steps including verification that the report doesn't contain sensitive data.
You can read more about the technical aspects of ABRT at our documentation site: http://abrt.readthedocs.org.
The easiest way to deploy ABRT Analytics is in a container using podman images. Learn how to use and build them in the container specific README.
Nightly builds of ABRT Analytics can be obtained from these repositories: