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

1415 results found

  1. Allow Alerts to be disabled during Atlas performed Maintenances

    When Atlas is performing maintenances such as setting changes and OS reboots Alerts will be triggered. It would be helpful to have these Alerts be disabled so that it doesn't cause false alarms or so much noise that they are ignored.

    24 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

    7 comments  ·  Alerts  ·  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. Upgrades from shared to dedicated clusters should only make the cluster available after data has been restored

    We have recently upgraded from a shared tier to a dedicated cluster. As document, this process involved a downtime. However, what was not document is that the cluster becomes reachable for clients again before the data has been fully restored. That way, clients can invoke operations on the cluster, that may even interfere with the mongorestore process. I would propose to make the cluster available again to public clients only after all data has been restored to avoid the chance for such race conditions.

    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  ·  Other  ·  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. 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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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…

    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  ·  Alerts  ·  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. Cluster/Database changes from Atlas portal does not show correct user in DB Audit log

    We have enabled Database audit for some projects, because we need to track who have done specific changes , like dropping an index.
    When someone using Atlas portal, the logged-in user does not show up in Audit record.
    Is not that possible to track ?
    Will attached some files..

    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  ·  Other  ·  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. 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>

    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  ·  Alerts  ·  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. 'Find' should offer a JSON mode

    Under Atlas > Clusters > Collections I can select a Collection and use the 'Find' option to quickly seek and edit a Document. At the moment the UI display is like JSON, but has stripped out the brackets, which makes copying the data awkward.

    Feature 1: The find display UI should offer a JSON mode, so the the Document, or parts of it can be copied in JSON format.

    If I select the Edit option, the editing UI is 'intelligent', in that it forces JSON compliance via the various options. However, this makes pasting in new data impossible.

    Feature 2:…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. Support for AWS KMS CMK per cluster (instead of on a project level)

    Hi Team,

    Currently, we have KMS CMK configuration available on the project level.
    We are hoping to see if that can be changed on cluster level.

    Reason: Once we update the key, all the clusters will get re-encrypted with new key, but snapshots will not be re-encrypted with the new key.
    For any reason, if we need to restore snapshot of one particular cluster, we will need to update KMS key with the old one, which impacts all clusters to get re-encrypted and then only can restore.

    Hence we believe cluster level KMS setting would be beneficial in such a…

    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

    2 comments  ·  Other  ·  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. The page fault metric is not available in the Datadog integration

    The page fault metric is not available in the Datadog integration

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. More detail and lead time around maintenance notifications

    When we get email notifications of upcoming maintenances, it doesn't specify if the update is "urgent" or "low". When we received our last notice, it was 3 days out. If it's urgent, then we understand the short time frame around the notice. However, if it's a lower priority update, I would hope we could configure how far out we are aware of the maintenance or at a minimum get notified 2 weeks prior so we can communicate to our end users.

    Additional information around what the maintenance is for would be appreciated as well. Something along the lines of "Patching…

    14 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

    5 comments  ·  Other  ·  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. Expose the `indexStats` action when creating custom roles in Atlas UI.

    The $indexStats aggregation pipeline allows user to get the statistics regarding the use of each index for the collection. This aggregation pipeline requires the indexStats diagnostic action.

    However, currently Atlas UI doesn't expose this action when creating custom roles. It would be nice to have this action listed in the "Collection Actions => Diagnostic Actions" list.

    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  ·  Other  ·  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. Referral links & referral benefits

    MongoDB Atlas should give each user a referral link, and a benefit of this could be that a free account could get increased storage space depending on how many/if the referred person starts paying for Atlas services.

    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

    0 comments  ·  Other  ·  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. 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…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. It would be great to have a tool with historical data about database and collection.

    It would be great to have a function where we can , using only atlas interface to filter a month and a year , and we cann see historical data about sizes.

    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

    0 comments  ·  Other  ·  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. 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)
  17. Provide a default alert for projects using Cloud Backup

    Given how import backups are to an enterprise's business continuity plans, the set of common sense default alerts set by Atlas should include an alert for Cloud Backup on projects with Cloud Backup enabled. Either "CPS snapshot has been stuck in queue for 1 hour" or "Snapshot schedule feel behind by 1 hour" would suffice.

    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  ·  Backup  ·  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. alert

    While setting up alert allow additional text to be added. This would help to write SOP for action needed on such alert

    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

    0 comments  ·  Alerts  ·  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. Include cluster node list in getOneCluster

    Include cluster node information for all nodes in the cluster in the response JSON for the getOneCluster API call. As hostnames are needed for other API calls, there ought to be a better way to get cluster node names.

    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  ·  Other  ·  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. Integrate Netework Access IP Whitelist with GitHub Actions

    I'm trying to setup CI for my project using GitHub actions, while restricting Network Access. The problem is that GitHub's machines have weekly changing IPs: https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#ip-addresses-of-runners-on-github-hosted-machines

    Is there any way to automatically integrate that list of IPs in the Network Access IP Whitelist? This feature would benefit all users of GitHub Actions.

    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

    3 comments  ·  Other  ·  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