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
  1. Allow to create Dashboard

    Please provide feature to create a dashboard for metrics like CPU, memory consumption etc for a cluster or more than one cluster in single graphs like for cpu one graph, for memory one graph like that just like monitoring tools provide for example zabbix screens and dashboards, stackdriver dashboards, dynatrace dashboards.

    This is to have a glance on our entire architecture instead of checking each and every cluster every time. This will be particularly useful during load tests or business peak period where we need to check more than one cluster performance.

    4 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 →
  2. Alerts change from time based pattern to include actual alert in subject

    So far we are receiving atlas alerts in time based manner which are difficult to undersatnd/analyze just by looking at email subject.

    We are expecting a model in which we want to Separate alerts for each instance instead of combining alerts on a single time frame and Changing email alert subject to include alert description. This will allows us to understand the alert by looking at email subject , combine/view all alerts in email client (for example outlook) , write some rules on them and analyze the alert timing pattern by sorting and group by alert description.

    For example,

    Present…

    2 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 →
  3. 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!

    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

    3 comments  ·  Monitoring and Metrics  ·  Flag idea as inappropriate…  ·  Admin →
  4. Separate metric graphs of egress outside the region per database, collection, user, destination

    Separate metric graphs of egress outside the region per database, collection, user, destination, so that I can easily find out what is causing the egress traffic which is billed on my account. This will also help me identify what parts could be good to move to different cluster in another region closer to the user,

    1 vote

    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 →
  5. Allow default settings on alerts on project/organization level

    It would be great if there was a way to set the default notification channels for alerts on the project and organization level.

    I was recently informed by the support team that there is no possible way of doing so, and that all alerts should be changed individually rather than for the whole project in one go.

    1 vote

    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 →
  6. 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.

    5 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 →
  7. 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.

    7 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 →
  8. Elections bar colors in Metrics should be more vivid

    The atlas metrics show node election statuses in colors - red/orange and brown. When there are multiple re-elections in a short period of time, these all merge together making it hard to decipher the order of occurrence - especially the near overlap of orange and brown Having vivid/contrasting colors should make debugging easier.

    It would be helpful if some aspect about the x-axis would tell you what status the node was in at a given time. For example: the x-axis is also that color from time X to time Y, and then the node was demoted/down and the axis turns…

    19 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 →
  9. Add replica set name to cluster info main page

    It would be nice to get quick access to the name of the replica set from the cluster overview page.

    5 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 →
  10. 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.

    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 →
  11. 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…

    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 →
  12. Separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster

    This is a request to separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster

    3 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 →
  13. 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>

    6 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 →
  14. disk iops

    The Disk IOPS graph shows 2 colored lines. (read/write). It would be great to add a third line which is the SUM of the 2 lines. Or... a toggle switch so we can see the sum line instead of the 2 components. Thanks!

    5 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 →
  15. Add eventTypeName for Maintenance Windows in alertConfigs response

    After adding a maintenance window to an Atlas project, the alertConfigs returns additional entries that do not include an eventTypeName field, it seems that these additional entries relate to the maintenance window but it's not clear:

    {

    &quot;created&quot; : &quot;2020-02-28T16:04:18Z&quot;,
    
    &quot;enabled&quot; : true,
    &quot;groupId&quot; : &quot;***&quot;,
    &quot;id&quot; : &quot;***&quot;,
    &quot;links&quot; : [ {
    &quot;href&quot; : &quot;<a rel="nofollow noreferrer" href="https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07acfe&quot;">https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07acfe&quot;</a>,
    &quot;rel&quot; : &quot;self&quot;
    } ],
    &quot;matchers&quot; : [ ],
    &quot;notifications&quot; : [ {
    &quot;delayMin&quot; : 0,
    &quot;emailEnabled&quot; : true,
    &quot;intervalMin&quot; : 60,
    &quot;roles&quot; : [ &quot;GROUP_OWNER&quot; ],
    &quot;smsEnabled&quot; : false,
    &quot;typeName&quot; : &quot;GROUP&quot;
    } ],
    &quot;updated&quot; : &quot;2020-02-28T16:04:18Z&quot;

    }, {

    &quot;created&quot;
    1 vote

    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 →
  16. 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…

    6 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 →
  17. 1 vote

    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 →
  18. Add 1 second granularity to ATLAS metrics

    At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
    reducing the granularity to 1 second would give more insight

    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 →
  19. Time Sensitive Alerts

    I would like the ability to (optionally) set a time window for any alert. IE Alert me if average write latency rises above 500 msec from 8am to 8pm. If outside those times don't alert me.

    1 vote

    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 →
  20. 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…

    7 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 →
  • Don't see your idea?

Feedback and Knowledge Base