We want to add a ConnectionId to exceptions somewhere (see CSHARP-1097), but MongoException doesn't seem to be the right place because not all subclasses of MongoException are connection related exceptions.

We need to review the driver exception hierarchy. Perhaps something like:

• MongoException
  • MongoConnectionException (base class for all connection related exceptions)
  • other exceptions

In any case, it seems like the entire driver exception hierarchy needs to be revisited.