[DRIVERS-2527] Log timeoutMS at the operation level Created: 19/Jan/23  Updated: 26/Jun/23

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

Type: Improvement Priority: Minor - P4
Reporter: Alex Bevilacqua Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CDRIVER-4560 Log timeoutMS at the operation level Blocked
split to CSHARP-4489 Log timeoutMS at the operation level Blocked
split to CXX-2641 Log timeoutMS at the operation level Blocked
split to GODRIVER-2740 Log timeoutMS at the operation level Blocked
split to JAVA-4857 Log timeoutMS at the operation level Blocked
split to MOTOR-1088 Log timeoutMS at the operation level Blocked
split to NODE-5001 Log timeoutMS at the operation level Blocked
split to PHPLIB-1069 Log timeoutMS at the operation level Blocked
split to PYTHON-3578 Log timeoutMS at the operation level Blocked
split to RUBY-3210 Log timeoutMS at the operation level Blocked
split to RUST-1579 Log timeoutMS at the operation level Blocked
Related
related to DRIVERS-1204 Easier debugging with standardized lo... Implementing
Driver Changes: Needed
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4560 Blocked
CXX-2641 Blocked
CSHARP-4489 Blocked
GODRIVER-2740 Blocked
JAVA-4857 Blocked
NODE-5001 Blocked
MOTOR-1088 Blocked
PYTHON-3578 Blocked
PHPLIB-1069 Blocked
RUBY-3210 Blocked
RUST-1579 Blocked
SWIFT-1695 Won't Do

 Description   
  • It should be clear from the application log whether timeoutMS was applied for operation execution and why. If timeoutMS value was inherited, then from which level.
  • It should be clear on which exact stage the timeout triggered while executing an operation (reading/writing to socket, serializing/deserializing the message, maxTimeMS…).
  • If the operation was retried and then timed out, it should be clear from the log, how many times it retried before the timeout.
  • If the timeout occurred due to maxTimeMS, we would like to know which exact command triggered that. What was the estimation of maxTimeMS used for the command. How it was estimated, what were the values of network RTT, remaining timeoutMS, percentile
  • For cursor timeout, we need to know whether the timeoutMode was set and to each value (CURSOR_LIFETIME or ITERATION)

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