| Events | Performance | Crashs | Http requests | Problems | |
|---|---|---|---|---|---|
| Fabric | Easy to implement and very neat to read | No | Ver easy to understand, includes memory usage | No | Limited |
| AppDynamics | Configurable | Something like it | Automatic, a lot of info, but not neat | Automatic, its awesome! Has everything! | Compile time went from 7 to 90 seconds, price |
| New Relic | Configurable | Incredible, annotation based easy implementation | Automatic, low info | Automatic not all and configurable | Price is outrageous |
| Crittercism | Configurable | Dont know | Not such a good info | No | Free is very limited and price is too high |
| BugDefender | Mostly automatic, can see common Log class in account | No | No | Could catch it using a Lod | Is very limited |
Fabric Previously known as "CrashAlytics". Is very easy to use, is free, has an Android Studio plugin, but is very limited. This is my favorite by the way.
AppDynamics We find it trying to fix an unknown connection error. Http reporting turn to be great, cause despite the library lack of info, this catch the error by it self and in a known manner. The downer is: Compile time, went from second to minutes each time you want to compile.
Crittercism Crash reporting is automatic and is initiated in one liner, we had the luck to get an account when there were free tier availables, but now I dont know. The problem is, the crash are not so good the ui is not that friendly.
New Relic It does get Http connection automatically, but not all. So if you get in the same problem we got, the configurable http reports are gonna be tied by the http connection library. I really liked the JAVA performance feature, using a simple @trace annotation over a method and is config to be tracked (you will known time execution). The problem is the price 1000USD for mobile apps. New Relic is great for Rails app, but not that much for Android.
BugDefender Is plain simple and straigth forward. You will get a very similar log to the Android Monitor in Android Studio, but clean. This make the user flow in the application to be very clear. The most great feature is this can catch automatically the common Log (Lod.d... Log.e...). For some issues a event tracker could be an overkill, by example, if you want to known the response code of any http request, this is great. Definitely, something to have in the production toolbelt.