MongoByte MongoDB Logo

Welcome to the new MongoDB Feedback Portal!

{Improvement: "Your idea"}
We’ve upgraded our system to better capture and act on your feedback.
Your feedback is meaningful and helps us build better products.

Add new feedback Subscribe
Status Submitted
Categories Atlas
Created by Guest
Created on Jun 23, 2020

RELATED FEEDBACK

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.
  • Attach files
  • Guest
    Jun 6, 2023
    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.
    Reply
  • Guest
    Aug 22, 2022
    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.
    Reply
  • Guest
    Jun 23, 2021
    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?
    Reply
  • Guest
    Aug 25, 2020
    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.
    Reply
  • Guest
    Jun 25, 2020
    Thanks Nic - would appName be also useful (if it's passed in the connection string?)
    Reply