ixudra
commented
9 years ago Hi Braunson
The basic idea of the concept is the following:
- Exception is thrown in application A
- CSI package in application A is triggered
- CSI package sends exception information to the collection point via POST, default is ixudra.be/api/crashes. Let's call this application B for simplicity's sake
- Application B registers the POST call (basically, set up a route and a controller method) and verifies the project via the API keys. I have some encryption here, but you can set this up any way you like, really. A project ID is basically enough, or you can skip this step entirely (not recommended though)
- Application B registers the exception in the database. How you do this is pretty much up to you: I set up a model for every component of the crash (Exception, Session and Request), each with their own set of members (see Ixudra\Csi\Services\CrashFactory for all the members). Lastly, there is a Crash class that ties it all together
- Admin users of application B are notified of the crash via email (again: optional)
- Admin users of application B can CRUD the crashes in order to solve possible issues (this part basically involves making some views and some CRUD operations - basic stuff)
It's really not all that complicated. All I do is deliver the information. How you use or display it is entirely up to you. Also: this is how I use this information. Your version might be as simple as sending an email, who knows?
My intentions are to make a second package that kind of bundles the functionality mentioned above. I'm not sure when I will get around to this as time is somewhat limited. I hope I will get around to it soon though, since I'm enjoying this package very much.
Hope this helps you out
Braunson
How is this suppose to work with http://ixudra.be/api/crash? How do we re-create our own API for this package?