Summary

Currently there isn't a standardized method for diagnosing client-side issues within the Drivers ecosystem. The MongoDB Server implemented a Full Time Diagnostic Data Capture mechanism in 3.2 that Technical Services engineers have used to troubleshoot performance and behavioral issues more rapidly and efficiently.

Due to a lack of client-side performance counters and basic telemetry, when application issues are reported typically the only artifact that can be shared is a log excerpt with stack traces. With only a stack trace, if the state of the system the application is running on was a contributing factor to the failure, a full reproduction is required to validate the issue and move an investigation forward. This can be cumbersome and time consuming in many scenarios and results in prolonged investigations.

Having a common mechanism for capturing platform-agnostic telemetry can expedite investigations and resolutions surrounding connectivity issues, client-side resource availability, networking behavior and other areas that are only visible from the application server.

Motivation

Who is the affected end user?

Any user building applications using an official MongoDB driver where this information can be collected.

How does this affect the end user?

With the initial users being our Technical Services and Professional Services teams, having this functionality would empower them to better diagnose issues with customer applications.

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

N/A

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

N/A

Is this issue urgent?

No

Is this ticket required by a downstream team?

N/A

Is this ticket only for tests?

No