Use Case

As a node driver user
I want to be able to easily tell whether a thrown error is due to the driver or a general runtime issue
So that I can more easily tell when to contact mongodb support

Dependencies

• None

Unknowns

• Investigate the extent to which it is possible for us to identify Node.js runtime errors and where we might be doing it

Acceptance Criteria

• If there are any identifiable places where an error coming from node itself might be caught and rewrapped, attempt to exclude it (via, for example, instanceof checks)

Implementation Requirements

• There may not be any code changes needed or possible, in that case, discuss with team before leaving a comment describing the findings and closing the ticket

Testing Requirements

• New unit tests for anything not already covered

Documentation Requirements

• None

Follow Up Requirements

• None