Summary

ConnetionCheckOutFailed events include a reason for the failure. The reason associated with connection errors doesn't include the actual error though. In the logging spec changes for CMAP, we decided that this would be worthwhile to introduce. We should also update the events to include the error to give users a better idea of why a check out might have failed.

Motivation

Who is the affected end user?

Users, driver authors, TSEs

How does this affect the end user?

They have greater visibility into what connection errors have occured.

How likely is it that this problem or use case will occur?

It's a failure cause, but a relatively common one.

If the problem does occur, what are the consequences and how severe are they?

Users can't observe connection errors when they occur, which makes debugging harder.

Is this issue urgent?

No

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

No