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. Credits by period

    Provide the ability to display and export credits by period (from date - to date) instead of selecting each single month, so that uers can easily display credit trends, etc. without downloading a lot of cvs and merge them togheter.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Add a Transaction Commits / Sec Metric Graph to Atlas

    Add a graph in Atlas to display "transactions.totalCommitted" on a per second basis to the Atlas metrics UI. Customers that are using transactions are often more interested in the # of transaction commits per second than opcounters.

    I have had to use mongostat on a number customer evaluations because this metric is not available.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Allow to resend alert to a PagerDuty service

    Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.

    The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.

    Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Precautionary Change/Recommendations for Shard Drops

    If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Better message for "Removed Indexes" in Activity Feed during Atlas rolling index build

    During a rolling index build, it is expected to have 2 "Deployment configuration published" notifications - 1 for Added Indexes and another 1 for Removed Indexes. This is because an entry for this desired index is added to the automation config and then the automation agent builds it accordingly. Once the agent is done building it, we remove the entry for that index from the automation config. Indeed, this does not drop the index.

    However, from the term of "Removed Indexes", it can cause confusion that the index is dropped. Hence, this feature request is filed for clearer message so…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Identification and labelling of MongoDB connections

    It'd be REALLY useful if there was an ability to provide a label (basically a string) when creating a new connection to MongoDB from an application, to say where the connection is coming from.

    For example we use a bunch of microservices and each API sets up a new connection. It'd be very useful to be able to see how many connections each API has at any given point, as it'd allow us to determine if the microservice is misbehaving with the database etc.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. Show node region on the metrics tab

    It would be really useful if the Atlas Metrics tab showed the node name and geographic location similar to how the Cluster Overview tab shows the node's region. In this use case, we have nodes located all over the world, so its useful to know where a node is located when reviewing it's metrics.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Disk Usage Breakdown

    When looking at the cluster page, I can see Disk Usage = 1.6GB, for example, but I don't know what the breakdown of that is. For instance, if I look at the same DB and add up the size of the collections themselves it's barely 1.5MB. So 1.6 Gig disk = 1.5 Meg data. I suspect this is oplog etc. but it is a pretty confusing potential red herring when diagnosing performance issues etc.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. Metrics "seconds" improvement

    The uppercase "S" on the metrics which indicates seconds, can be slightly misleading as it can appear to be the number 5 when placed next to another number. This is especially misleading on the Replication Lag metric. It may be easer to read as a lowercase "s" or abbreviating with "sec".

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Invoice: Ability to post items to a collection daily

    You have daily line items on invoices. It would be great to be able to configure our billing to post to one of our collections. This would allow me to put charts on top of usage across all of our project and not just monthly

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Would love to have a little bit more info in the webhook to know what caused the election, or that there was an upgrade (vs a server failure

    Would love to have a little bit more info in the webhook to know what caused the election, or that there was an upgrade (vs a server failure) in the db!

    MongoDB AtlasAPP 12:10 PM
    Project: myProject

    Organization: myProject (Organization)
    INFORMATIONAL
    Replica set elected a new primary
    my-cluser-shard-0
    Created: 2020/01/03 11:10 PST
    Replica Set: my-cluser-shard-0
    Current Member State
    DOWN: 1 member
    SECONDARY: 1 member

    PRIMARY: 1 member
    love the service team, thanks a ton!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. View cluster/storage scalable (yes/no) in "All cluster" dashboard

    Right now in the "all cluster" view, one cannot see, if the clusters are enabled for auto scaling. my idea is to add this also to avoid last minute performance alerts for non scaling enabled clusters

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Collection query audit logs

    It would be nice to be able to see what queries were run on which collection over the last x days.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. MongoDB Atlas historical stats by collection

    It would be helpful to have historical metrics for storage by collection. Storage space used, indexspace used, number of indexes.
    Thanks

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. Improve Metric Correlation

    Would be nice to better correlate metrics, server events, and individual operations.

    For example would be helpful to have in the profiler indication of automatic scale up/down of the cluster in order to easily correlate actions that trigger them in the last 24h.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. Metric Grouping

    A huge improvement and help when it comes to metrics would be the ability to query by grouping (e.g. for database access users). This way if you were to use a specific database user per a specific service connection, we could see how much load to the database that specific service is causing.
    Any form of implementation would be helpful, one example could be adding labels to the prometheus metrics per user, replica/shard etc.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Throttle instances within a shared tier

    Right now, if a cluster is in a shared tier, other "noisy neighbor" tenants can destroy performance by overusing the resources, forcing a restart, causing unstable behevior etc.

    Throttle noisy neighbors so that others don't suffer!

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Dump audit logs to log analytics workspace

    Why can't we dump audit logs to log analytics workspace when we are using azure private endpoints to connect atlas

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Investigation Buckets (dropdown menu) to enable predefined set of MongoDB & Hardware Metrics to investigate certain Data Layer SLAs

    We have many metrics under "MongoDB Metrics" & "Hardware Metrics". User will have a good idea which metrics to enable while troubleshooting certain requirements.

    E.g. User is investigating current lags in the data Layer. User has to select all the metrics that would help them get the data they are looking.

    We can help the customer bit more by provide buckets like.
    Options ( select one )
    1. Investigate Lags
    2. Investigate IOPS
    3. Investigate Replication
    4. Investigate Search Index
    ... and etc..

    This will pre-select certain metrics from list of Mongodb & Hardware metrics which will give them all…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Export only selected Atlas metrics

    This is a request from a customer named: UPAX partnered with Grupo Salinas.
    Inside the cluster metrics, where the Status is displayed, we are able to find the Export option (PDF, PNG) and they would like to export for only specific metrics (only the toggle charts) not the whole of them for reporting purposes with other teams and management.

    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

    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