Reporting Errors Is Good, Airbrake Makes It Even Better.
February 11, 2022
Reporting Errors Is Good, Airbrake Makes It Even Better.
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Airbrake
We use Airbrake to track multiple things: the errors that appear in the console of the end-users, to make sure that our product works as intended and to get notified about any error before the user reaches out to our Customer Care team (and get more information about the error) track the failed API calls that we have sent from our frontend. We use this to check faulty implementations or how the user is misusing our software so we can foolproof it better :D we made it kinda a habit to keep an eye on those numbers, we don't strive to get it to 0 but for stability.
Pros
- Report errors
- Versioning
Cons
- Aggregated errors are not so clear why they got grouped together
- Not clear why some filters don't work
- Tracking errors
- Early notifications about possible problems
Do you think Airbrake delivers good value for the price?
Yes
Are you happy with Airbrake's feature set?
Yes
Did Airbrake live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Airbrake go as expected?
Yes
Would you buy Airbrake again?
Yes
Comments
Please log in to join the conversation