Use Case

As a... developer tools maintainer
I want... to have more detailed information in the error message we display to users when a connection fails
So that... we can figure out why exactly connection attempts are failing more easily

Dependencies

This is something we’d like to improve on the developer tools products. I’m not sure if driver spec work is necessary.

Unknowns

What is the best way to provide the information about the cause of the server selection timeout to users? Extending the error message would be easy for us, because we already display it.

If it is preferable that we display the information from the reason field (i.e. the TopologyDescription) to users, then I think we would appreciate some guidance on what parts of it to display exactly.

Acceptance Criteria

Implementation Requirements

• functional reqs, potential snafus to avoid, performance targets, etc

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc