Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Future: Consider adding ABRT crash data #24

Open
david-a-wheeler opened this issue Jul 22, 2015 · 2 comments
Open

Future: Consider adding ABRT crash data #24

david-a-wheeler opened this issue Jul 22, 2015 · 2 comments

Comments

@david-a-wheeler
Copy link
Collaborator

Florian Weimer suggested adding ABRT crash report counts. An advantage is that these correlate to potential issues and whether/how quickly those issues are being fixed. CVE counts (by contrast) only show up when someone is looking and bothers to request a CVE number for the issue.

Here is some such data from Fedora and CentOS:
https://retrace.fedoraproject.org/faf/summary/

Source code for the server appears to be here:
https://github.com/abrt/faf/tree/master/src/webfaf2

Based on that code, you can get raw JSON by sending a suitable Accept header:
$ curl -H "Accept: application/json" https://retrace.fedoraproject.org/faf/stats/yesterday/

@ya1gaurav
Copy link

👍

@jfilak
Copy link

jfilak commented Aug 15, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants
@david-a-wheeler @jfilak @ya1gaurav and others