Summary

Add support for OpenTelemetry-standardized tracing into the MongoDB drivers.

Motivation

Who is the affected end user?

All Drivers users

How does this affect the end user?

Users currently lack insight into performance degradations and connection issues on the client-side. They are sometimes able to piece together some parts of why performance issues might occur by looking at Profiler on Atlas, but for the latter, we currently expose no information. Users can make use of OpenTelemetry autoinstrumentation where available, but we have heard that it is insufficient, or in some cases, not available (C/C++). 

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

Connection-related issues comprise anywhere from 15-25% of all Drivers-related cases created (according to the TS Drivers report).

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

The lack of easily available information can lead to extended mean-time-to-resolution when issues occur, as well as developer pain and frustration.

Is this issue urgent?

N/A

Is this ticket required by a downstream team?

N/A

Is this ticket only for tests?

No.

Cast of Characters

Engineering Lead:
Document Author:
POCers:
Product Owner: ashni.mehta@mongodb.com 
Program Manager:
Stakeholders:

Channels & Docs

Slack Channel

[Scope

[Technical Design