New view with connection statistics
It would be valuable to have a per-cluster view showing an overview of connections into each cluster including:
- The number of connections per hours (opened, closed == churn)
- Which IPs connections are coming from and how many from each over time
- What drivers are being used for these connections and from which IPs
- Which user is opening the connections
This information can be very useful in understanding which applications/microservices are opening up the most connections, and helping to find old drivers etc.
Nic
shared this idea
-
Hernán
commented
also would be really important to have a sense of time duration per connection and mongod logs online analyzer inside mongo atlas cluster tools.
to monitor connections is something critical as currently there is no way to manage them with mongo atlas online tools, and neither autoscaling is triggered when connection max limit is reached, so it can cause database to be unreachable and it's not going to automatically expand to a cluster with a greater limit.
-
Buddy
commented
This keeps coming up for up due to misbehaving clients.
It is critical that we identify the number of connections per DB user.Even after a couple of support cases, I still do not know of a way to determine how many DB connections are open for a user.
-
Shawn
commented
I agree that better insight into the Connections would be helpful. Maybe updating the existing "Connections" stats on the Metrics tab to include the counts for "opened" and "closed" connections, alongside the existing "current" connection count?
-
Nic
commented
Yes @Rez that would be great. Maybe filters by appName and driver type would make it possible to drill down and target the root of excessive connections.
-
Thanks Nic - would appName be also useful (if it's passed in the connection string?)
