[COMPASS-4370] Handle user caused errors gracefully in compass (not passed to bugsnag) Created: 28/Jul/20  Updated: 10/Jan/24  Resolved: 24/Feb/22

Status: Closed
Project: Compass
Component/s: Import/Export
Affects Version/s: None
Fix Version/s: No version

Type: Investigation Priority: Major - P3
Reporter: Rhys Howell Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Documentation Changes: Not Needed

 Description   

Currently a number of user errors are being reported in bugsnag:
[https://app.bugsnag.com/mongodb/mongodb-compass/errors?filters[event.since][0]=30d&filters[error.status][0]=new&sort=last_seen]

These are oftentimes errors caused by the user trying to import incorrect data types in import export or bad regexes. These are things which we should handle inside of the app and shouldn't surface to bugsnag unless it's our code breaking.
This ticket involves identifying and fixing some - or all - of the places where these events originate. If there are a lot of places maybe break it into separate tickets to be worked on in the future.



 Comments   
Comment by Rhys Howell [ 24/Feb/22 ]

We've removed bugsnag and now with the new logging this has gone away. There are still some errors to catch but I think we'll get to them in time.

Generated at Wed Feb 07 22:36:07 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.