ABRT Analytics collects reports from ABRT and aggregate 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:
https://retrace.fedoraproject.org/faf
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.
- Support for various programming languages and software projects:
- C/C++
- Java
- Python
- Python 3
- Linux (kernel oops)
- De-duplication of incoming reports
- Clustering of similar reports (Problems)
- Collection of various statistics about a platform
- Retracing of C/C++ backtraces and kernel oopses
- Simple knowledge base to provide instant responses to certain reports
- Bug tracker support
- Sources: git clone https://github.com/abrt/faf.git
- IRC: #abrt @ freenode
- Mailing list
- Contribution guidelines
- Wiki
- Installation Guide
- Github repository
- Issue tracker
- ABRT Documentation
- ABRT stack - (abrt libreport, satyr)
- Python
- PostgreSQL
- SQLAlchemy
- Alembic
- Flask
- Celery
Nightly builds of ABRT Analytics can be obtained from these repositories: