[JAVA-4907] Add operationId to events and log messages Created: 12/Mar/23 Updated: 28/Oct/23 Resolved: 25/Apr/23 |
|
| Status: | Closed |
| Project: | Java Driver |
| Component/s: | Logging, Monitoring |
| Affects Version/s: | None |
| Fix Version/s: | 4.10.0 |
| Type: | New Feature | Priority: | Unknown |
| Reporter: | Jeffrey Yemin | Assignee: | Jeffrey Yemin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Documentation Changes: | Not Needed | ||||||||
| Documentation Changes Summary: | 1. What would you like to communicate to the user about this feature? |
||||||||
| Description |
|
The lack of support for operationId makes it difficult to correlate events and log messages forĀ
So there is no way to reliably determine, for example, how long an operation spent in a connection pool's wait queue. |
| Comments |
| Comment by Githook User [ 25/Apr/23 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Add operation identifier to connection check out/in events (#1105)
|
| Comment by Githook User [ 30/Mar/23 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Add operationId to command events (#1101)
|
| Comment by Githook User [ 28/Mar/23 ] |
|
Author: {'name': 'Jeff Yemin', 'email': 'jeff.yemin@mongodb.com', 'username': 'jyemin'}Message: Add OperationContext to Binding (#1097)
|
| Comment by Jeffrey Yemin [ 22/Mar/23 ] |
|
Phase one in review |