FAF

Originated as Fedora Analysis Framework. The ultimate tool to fix problems of application crashes.

FAF collects thousands of reports a day serving needs of three different projects:

Live FAF instances:

https://retrace.fedoraproject.org/faf

FAF is part of the ABRT project

How it works

Currently, typical crash reporting workflow consists of generating so called ureport (micro report) designed to be completely anonymous so it can be sent and processed automatically avoiding costly bugzilla queries and manpower.

FAF in this scenario works like a first line of defense — collecting massive amounts of similar reports and responding with tracker URLs in case of known problems.

If user is lucky enough to hit a unique issue not known by FAF, 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 technical aspects of ABRT at our documentation site: http://abrt.readthedocs.org.

Features

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 platform
Retracing of C/C++ backtraces and kernel oopses
Simple knowledge base to provide instant responses to certain reports
Bug tracker support

Developer resources

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

Technologies behind FAF

RPM Repositories

Nightly builds of FAF can be obtained from these repositories:

License

marusak/faf

ErrorLooks like something went wrong!

About

Resources

License

Code of conduct

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Languages

Error
Looks like something went wrong!

Packages