Named MongoDB Connections
When a service is acting erroneously and generating hundreds or thousands of connections, it's currently difficult to determine which service is doing so when you have 30+ services connecting to MongoDB.
My proposal is that we should be optionally able to specify a non-unique name for the connection in the MongoDB URL (possibly after a #), which would allow DB administrators to see how many of each named connection was connected at any given time, and also other metrics (operations/s per name, average/max query execution time per name, etc.).
Example URL:
mongodb://user:****@clustername.abcd.mongodb.net:27017/dbName?authSource=admin#myServiceName
Andrew
shared this idea
-
AdminShameek
(Admin, MongoDB)
commented
Hi Andrew,
Thank you for reaching out about this problem. We are currently researching new techniques for customers to understand the root cause of their application failures. I'd like to understand more about your use case and the alternatives that are considered. Would you be willing to share more over a short call?