[DRIVERS-2495] Expose connection error that cause check out to fail Created: 03/Nov/22  Updated: 21/Jun/23

Status: Backlog
Project: Drivers
Component/s: CMAP
Fix Version/s: None

Type: New Feature Priority: Unknown
Reporter: Patrick Freed Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to DRIVERS-1675 Add log messages to CMAP spec Implementing
Driver Changes: Needed

 Description   

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


Generated at Thu Feb 08 08:25:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.