Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

168 results found

  1. Email subject more specific for Alerts

    The email Alerts that MongoDB provide are very useful, especially the Oplog and CPU Usage. However, the subject of the emails are not clear and does not specify the Alert type. It is just a generic "Alert". It would be great if MongoDB can add "Alert Oplog" or "Alert CPU Usage" to the email subjects to make them much more clear and helpful. Thanks!

    13 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Support node type or node tags as condition in MongoDB Atlas Alert

    Currently, the MongoDB Atlas does not support the node types [1] or node tags [2] as the condition in Atlas alerts. That would be super inconvenient for the following scenarios.

    Scenario 1: If the user wants to create an alert to monitor the specific node type, such as READ_ONLY node or ANALYTICS nodes, there is no convenient way to achieve it. The current approach must set up the alert by using the hardcode hostname.

    Scenario 2: If the user has some electable nodes and a analytics node in a cluster, and wants to focus on monitoring the electable nodes (workload),…

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Make AWS EBS Burst Balance metrics available in Atlas UI

    Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.

    You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Automatic information when shared cluster is throttled

    When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting.

    Right now there is no way for a db-owner to see this information, let alone get that information, except for asking support for help.

    11 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Include Human-Friendly Cluster Names in Alert Notifications

    Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Allow log level to be configured per cluster/node

    Atlas clusters don't support the setParameter command and, as a result, users aren't able to configure log levels. I understand the reasoning behind not exposing permissions to run setParameter to DB users so, in lieu of that, it would really helpful if Atlas users were able to configure log levels through the Atlas UI, preferably at the Node or Cluster level.

    Thanks!

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Profiler should only watch queries from certain users

    It would be useful to provide the profiler an "allowlist" and "denylist" of users to watch queries from. Essentially, it is only useful to receive alerts and profiler reports for queries made by actual applications. It is not useful to have alerts show up for one-off queries made by a DB admin using a DB explorer.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Rename Hardware Metric "Util %"

    Under hardware metrics for a given replica set, there is a metric for "Util %". It is unclear on what this represents. After careful digging through the documentation, it appears to be a metric for Disk Bandwidth Utilization. I believe the metric name should be updated to reflect at least "Disk Util %", if not something more specific.

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Show a graph of BANKED iops (AWS)

    Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)

    Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
    During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.

    It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Allow threshold on "System Memory: Available" alert condition to be a percentage

    In Atlas, it would be ideal if you could specify a percentage of total memory as the threshold for the "System Memory: Available Is..." rather than a literal number value. If it was possible to set this as a percentage, then the alert could be applied to all hosts in a project, rather than having to set hostname conditions and create a separate alert for each cluster.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. Data Transfer Limit

    since as documented there are limitation on network traffic in M0/M2/M5 instances, it is mandatory to have a metrics/alerts (also for free ones) to monitor this value in a 7d sliding window

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Stackdriver Integration

    Atlas Monitoring UI is great, but to ease centralization of alerts and dashboards..., it would be nice to have all atlas metrics in Cloud Monitoring too.

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Profiler window should auto zoom to sampling period and show sampling period range

    Atlas documentation states that the Query Profiler shows up to 10,000 queries within the past 24 hours:  https://docs.atlas.mongodb.com/tutorial/profile-database/index.html#data-display-limitations

    However, it is confusing to see that the Profiler cannot show more than a couple hours of data, likely because it is hitting the 10,000 entry limit.

    The plot still shows a view showing 24 hours of time, but only the past couple hours have data plotted, misleadingly indicating that there are no slow queries before a couple hours ago – here's an example: https://p-37FYgJ.b1.n0.cdn.getcloudapp.com/items/JruWZDYK/Image%202020-03-25%20at%2010.49.32%20AM.png?v=7f79362e62c8d15a9f91f8ba4d5aecaf

    Atlas should make the sampling time window clear in the Query Profiler graph so that we…

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Send Alert when IP access list changes

    Customer is requesting that an alert be sent out if project IP access list gets changed

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Keep context of Metrics dashboard

    on MongoAtlas metrics dashboard, I can organize graphically different metrics as I want to display first "insert" metric for example, then "cpu" metric, etc ...
    If I change this actual order, then I go to another screen (for example "network access") and finally I come back to this metric dashboard, my new metrics added (insert, cpu, ...) in first position are not in wanted first position (at the top of metrics list), but at the end of this metrics list.

    It would be great to keep metrics context (displayed metrics and ordering) on Metrics dashboard.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Graph connections per user (or per database)

    Show a graph of connections per user.

    It would be very useful to see how many connections each user has (or also, each db) over time.

    It would allow us to see more clearly and faster which service uses how many connections.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Show in the UI when an index build is ongoing, and when it completes

    When indexes are built from an application or a mongorestore there's no way to see if it's ongoing in the UI.

    There should be an indication in the "Real-time" tab saying that an index on collection X is in progress. This would explain why performance is currently impacted.

    It would be good to see index start and end marked on the "Metrics" visualizations so we can see the impact of index builds on IOPS, CPU, memory etc. This could help understand if we need to upscale the cluster.

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Atlas Alert for Remaining Credits

    MongoDB will email Atlas customer when the prepaid Atlas credit is estimated to be exhausted within 30 days.

    However, it would be good to have an alert for this in Atlas, e.g.

    Alert if the remaining prepaid amount is lower than ... <an amount>

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. metrics

    There might already be a way to do this, but I cannot find it. Please provide a way to combine "all primary" metrics into a single chart.

    I love your metrics, but I hate that when primary moves from one server to another I get "data gaps" in my graphs. So then it becomes exceedingly difficult to look at temporal variations... requiring splicing together multiple segments from 2 or 3 different graphs.

    I have attached a picture of what I am talking about. You can see that primary moved over for a few days so I get a graph with…

    8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base