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

1365 results found

  1. Purge of unused accounts after X days/months

    After X number of days/months (say 12 months), accounts that haven't been accessed or have never been accessed go into a 3 month freeze period, before they are automatically disabled and deleted. A report of such accounts should be auto generated and archived. The freeze period intention sends a warning to the account holder as well as an alert to administrators of the atlas org.

    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)
  2. Prevent Federated Users to gain access to other Projects

    Hi,

    We have set Federated authication and RoleMapping to project. This roleMapping gives Project Owner Rights to a particular project. Project Owner have the right to invite other people into their project.

    Role mapping is only applied when a user logs in. However, if the user receives an invitation to a project when logged in (to say Project ***) and accepts an invitation (to say Project YYY, for which they should not have any access), they will receive the Atlas role in that project (Project YYY) designated by the invitation, allowing them to perform any actions provisioned by that role.

    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

    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. webhook

    Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.

    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

    1 comment  ·  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)
  4. description in sso group mapping

    Add a description field in the Atlas UI in the group mapping page when SSO is enabled. Today only an object ID is 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)
  5. Migrate to new cluster without auto upgrade (5.1.0)

    Hi,
    Our clusters are in auto upgraded feature of MongoDB versions right now.

    We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.

    But, when we try to create a new cluster it's not showing the option for version 5.1.0.
    And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.

    Your help is much appreciated.

    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

    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)
  6. mute alerts during set times

    We would like to be able to set a time frame for when an alert can be triggered.

    Our use case is that some devs schedule high impact queries to run at night. If the rule is triggered at night, then we don't care, but if it's triggered during the day, it's something we look at and fix.

    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)
  7. PITR should allow to choose which snapshot to use as base

    PITR mechanism does not allow the user to choose which snapshot to use as base before replaying the oplog. Given that Atlas does not validate the snapshots after they have been taken, the user ends up needing to setup their own validation process. That alone is not a problem. However, when one needs to use the PITR mechanism, not being able to select a previously validated snapshot may lead for PITR restores to use unvalidated snapshots.

    Either Atlas should enable, uppon choosing, the validation of snapshots right after they are taken, or allow the selection of valid snapshots (snapshots taken…

    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  ·  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)
  8. Delete documents from backups

    Allow to delete documents from existing backups based on a query.

    When off-boarding customers, we sometime need to delete all of their data, including historical data from backups. Having the ability to clean up those backups, without having to restore, delete, and take a new backup, would be amazing.

    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  ·  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)
  9. Derisk cluster changes that cause restarts

    Problem statement:
    Some configuration changes cause rolling restarts of the cluster (e.g. audit filter, enabling x509 auth). It is not immediately obvious which changes will cause restarts and for a big cluster, this is a huge hit to performance due to cold caches.

    Ideas:
    1. Block planner changes which would cause restarts until maintenance window (maybe with an opt-in for this, + notification that the config change is blocked)
    2. Throttle replica set restarts, allowing time for the cache to be warmed on secondaries (would require mirrored reads in 4.4 to be effective)
    3. Properly document what changes will cause…

    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)
  10. Expiration Date on Database Write Access

    Just like the Network Access where you can allow an IP address to be used for connection to the database for a short time, I would like that same feature for Database Access write permissions. I would like to temporarily give someone permissions for X hours and after that time period, it reverts back to the original state, such as read-only access. I have to temp give someone permissions during release nights to perform operations.

    Example: "This entry is temporary write access will be deleted in 6 hours and reverted back to the original real-only state."

    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. alerting when a node has a non standard state

    Add a new type of alert : to be alerted when one cluster node goes to a state different of standard states ("primary" or "secondary").
    For example, I have a cluster that one secondary node is on a transient state : "other".
    Thank you.

    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)
  12. Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.

    Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it.

    But it would be nice to be able to specify a default collation at the database level, or even the Atlas Project level, to apply to all collections in all databases therein, howsoever created.

    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. Add Process CPU metrics for `mongos`

    Currently the Process CPU and Normalized Process CPU metrics for all clusters appear to only show the CPU for mongod. For sharded clusters, please add a metric to track mongos (and possibly mongot, for those using it) usage.

    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)
  14. allow control of pagerduty urgency (currently high) so that alerts can be managed better

    Some alerts you need to know about immediately, others, the next working day will suffice. Allowing the user to set the urgency for each alert will allow a greater control over pager fatigue without having to bypass PagerDuty

    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)
  15. 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  ·  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. payment

    Add PIX payment method. I don't know how much of a hassle it's to implement such payment method for brazillians, but I think it would be one of the "killer feature" for us. Thank you.

    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  ·  Billing  ·  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. killAllSessionsByPattern and kill sessions

    Please add killAllSessionsByPattern and kill sessions feature in Atlas UI

    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)
  18. Metrics charts x-axis showing more than 24 hours of data should be labeled according to the scale

    Metrics charts x-axis showing more than 24 hours of data should be labeled according to the scale

    Currently, when a mouse is not hovering over a Metrics plot, the plot will show particular hours as labels for the x-axis. For example, if an 8 hour range of time is displayed, the time every two hours will be labeled.

    However, if more than 1 day is displayed, the x-axis labels are less useful. The particular time once/day is displayed, but the day is not included. For example, when I display a week of data, 07:00 is highlighted on each particular day,…

    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)
  19. UX Issues with Collections View in Atlas UI

    UX on Collections view has some problems which are listed below;
    - It takes around 10-20 seconds to load the Collections page, specifically the left panel which lists namespaces.
    - Then without any user interaction or feedback, it takes another 10 seconds to focus on the top most available namespace to display details of it on right hand side panel
    - Then filtering namespaces with "auth" doesn't make any change in the screen and not giving any feedback neither.
    - Then inputting more letters "authen" triggers the filtering however this time it filters namespaces which had nothing to do with…

    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)
  20. Put some kind of connection string generator / link / text on the "Database Access" screen

    Hello!

    It took quite a while for me to find a template connection string for Atlas, as I only thought to check the "Database Access" screen. Eventually I found the "Connect" button the "Clusters" screen, but it was a pretty frustrating time looking for something as essential as a connection string.

    It would be great if you added something that would have prevented that-- a little widget where you pick your cluster and it spits out a template string. Or even just some text like "Looking for your connection string? Go to clusters, it's over there!"

    Thanks!

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

Feedback and Knowledge Base