[DRIVERS-821] Record Client connection URI Created: 31/Jan/20 Updated: 20/Jan/24 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | None |
| Fix Version/s: | None |
| Type: | Epic | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Driver Changes: | Needed | ||||||||||||||||||||||||
| Description |
|
Epic Summary SummaryCollect and store the the uri used by the client driver when connecting to a mongodb server process. MotivationWhen users connect to a server today, it is not currently possible to know exactly what options they passed when connecting to that server. Some crucial information includes the style of mongo uri (mongodb:// or mongodb+srv://), the topology (replica set vs standalone) and the specific hosts (what hostname are we connecting to over what horizon). Passing the uri used and exposing it server side would allow us to better understand how user's interact with our software and would enable projects that pivot off that information in the future. Cast of Characters
DocumentationScope Document |
| Comments |
| Comment by Shameek Ray [ 13/Oct/22 ] |
|
rachelle.palmer@mongodb.com, based on bernie@mongodb.com's comment above, do we see this project joining the DBX team's roadmap? The readPreference information would be valuable from a Server Product Metrics perspective. cc judah.schvimer@mongodb.com |
| Comment by Bernie Hackett [ 07/Oct/21 ] |
|
I don't think we should record the entire URI. We definitely should not record user credentials, we don't need to record the hostnames since they are where we are sending the data. We also don't need to report the authentication mechanism since the server already records that by nature of us authenticating. The real value of this project would be reporting the other options set globally (readPreference, readConcern, writeConcern and connection pool settings are really valuable). We also need to limit the data reported to avoid ballooning the size of the hello payload. |