Reputation: 5228
Very frequently I see error reporting GUIs in commercial software. This includes the whole gamut of commercial software: games, enterprise apps, office apps, etc.
For some of my company's software I would like to provide exception reporting GUIs if (and ultimately when) my application fails unexpectedly. Building the GUI is not hard. It boils down to this: Are there any existing solutions for the backend systems in exception reporting? Ideally I am looking for a java library and a corresponding server backend. I could roll my own solution; for example, I could send the data to a webserver via POST data.
I feel like a solution for this already exists somewhere -- I just haven't run into it. Any recommendations?
Edit:
Example frontend GUI for a user. I need a library to manage the backend of the error reporting. (I won't need user login functionality, just basic reporting.)
Upvotes: 4
Views: 1341
Reputation: 1638
Are there any existing solutions for the backend systems in exception reporting? Ideally I am looking for a java library and a corresponding server backend.
Have a look at Ctrlflow Automated Error Reporting, which is a software-as-a-service backend to send error reports to. Your frontend GUI would then use one of the available Java libraries to communicate with your Ctrlflow Automated Error Reporting instance.
To get a good overview of the backend’s feature set (which may offer more than you need), take the product tour. Or just log into the demo server to get a feel for the backend.
Hope that helps.
Upvotes: 1
Reputation: 1
This product has an instrumentation feature that allow you to track the exceptions by sending the data to a portal : http://www.preemptive.com/products/dasho/overview. These features were added to the 6.7 release. Although it is an obfuscator, you can turn those features off and just use the instrumentation features to send the data or use the APIs directly. PS - this is my company's product.
Upvotes: 0
Reputation: 1176
I think there is no common existing solutions in exception reporting because of specific features of every project. Some projects need to send report using simple HTTP, someone uses web services, someone makes a file report.
I've found old post where author suggest to extract error reporting code from Netbeans and make independent project from it.
Anyway, there is no problem to implement error reporting tool yourself. You could use HttpClient of JAX-WS (if you have a rich client) or you could use AJAX (if you have a web client) for sending reports.
Implementation is strongly depend of what kind of communication do yo use if tour project, what kind of project, what kind of front-end do you use and etc. It's really hard to implement common library for all projects.
Upvotes: 1