The fast way to capture unhandled and processing mistakes. great that I can automatically collect diagnostic information. Also, I guess the more important step that I can see how many times an fault happens.
The information Bugsnag captures in Go isn't that useful. Stack traces can be misleading. I'd like to track multiple levels of log in Bugsnag but not necessarily report them all through to Pagerduty (i.e. I'd like to also capture warnings but not have them...
The user steps feature allows us to easily see the path the user took to generate the bug. Also, the API was easy to install. And, bugs are simple to view and see logs etc.
I'm not sure about the performance impact of including instabug. The screenshot mechanism is kind of a dupe with the built-in iOS one.
The fast way to capture unhandled and processing mistakes. great that I can automatically collect diagnostic information. Also, I guess the more important step that I can see how many times an fault happens.
The user steps feature allows us to easily see the path the user took to generate the bug. Also, the API was easy to install. And, bugs are simple to view and see logs etc.
The information Bugsnag captures in Go isn't that useful. Stack traces can be misleading. I'd like to track multiple levels of log in Bugsnag but not necessarily report them all through to Pagerduty (i.e. I'd like to also capture warnings but not have them...
I'm not sure about the performance impact of including instabug. The screenshot mechanism is kind of a dupe with the built-in iOS one.