Skip to content

Atlas

← MongoDB Feedback Engine
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

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

485 results found

  1. Allow the ability for a rolling cluster restart like during maintenance

    Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.

    18 votes
    1 comment  ·  Other  ·  Admin →
    How important is this to you?

  2. Set schedules for pausing clusters

    It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.

    18 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  3. max database users not visible

    We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.

    16 votes
    3 comments  ·  Other  ·  Admin →
    How important is this to you?

  4. Use wildcard databases in user role privileges (like collections)

    Use wildcard databases in user role privileges (like collections)

    https://jira.mongodb.org/browse/SERVER-78575

    15 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  5. Extend / Configurable retention time of audit logs

    This is a feature request to extend or have configurable retention time of audit logs more than 30 days in Atlas.

    15 votes
    3 comments  ·  Other  ·  Admin →
    How important is this to you?

  6. Support for Push-Based Logging to Azure and GCP

    Asking on behalf of customer, please add Support for Push-Based Logging to Azure and GCP instead of just to AWS S3 buckets: https://www.mongodb.com/docs/atlas/push-logs/

    14 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  7. Support for AWS China (Beijing/Ningxia) regions

    Please make Atlas available in AWS's Beijing/Ningxia regions. This is important to due to China's internet restrictions to achieve the best possible performance/latency for our Mainland China customers.

    14 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  8. mongomirror with db rename

    We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?

    14 votes
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  9. Allow Alerts to be sent to an Atlas Team

    Alerts can be configured to send to specific Atlas Users, but not Atlas Teams, which diminishes the value of setting up a team of users.

    14 votes
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  10. Ability to choose a Primary shard for newly created database

    In a multi tenant architecture, the isolation of a tenant on a specific shard (when database sharding is involved) is expected. At this time, the ability to choose a Primary shard for newly created database would come in handy

    13 votes
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

  11. Deploy Custom Role to specific clusters only.

    You added the ability to deploy users to specific clusters. Great but you forgot to do it for the "custom roles". We use the "custom role" with LDAPS so we do not create a user on Atlas.

    https://feedback.mongodb.com/forums/924145-atlas/suggestions/38819875-ability-to-create-database-users-limited-to-specif

    Can you extend this functionality to "custom role" also %

    13 votes
    1 comment  ·  Other  ·  Admin →
    How important is this to you?

  12. Ability to provide IP addresses as a list for Network Access

    When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.

    13 votes
    1 comment  ·  Other  ·  Admin →
    How important is this to you?

  13. configure IP whitelisting on database user level

    enable the user creation to have the following option

    authenticationRestrictions: [
    {
    clientSource: ["<IP>" | "<CIDR range>", ...],
    serverAddress: ["<IP>" | "<CIDR range>", ...]
    },
    ...
    ],

    13 votes
    3 comments  ·  Other  ·  Admin →
    How important is this to you?

  14. Ability to schedule monthly maintenance windows

    Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.

    I realize we have the ability to defer maintenances for a week, which is great. However, we're now…

    13 votes
    1 comment  ·  Other  ·  Admin →
    How important is this to you?

  15. pause

    An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.

    13 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

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

    13 votes
    5 comments  ·  Other  ·  Admin →
    How important is this to you?

  17. storage autoscaling at N %

    Dear Mongo Team,

    Your engineers advise to add more storage to the clusters when it reach 80 % usage as this is when performance degradation can occur. At the time of writing the autoscaling happens at 90 % disk usage. We want to be able to adjust at what % of usage the autoscaling happens and set it to the value of 80 % basically what your engineers advise.

    12 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  18. Set MongoDB Production Support Employee Access to Atlas Backend Infrastructure at Project Level

    The Restrict MongoDB Production Support Employee Access to Atlas Backend Infrastructure is currently set on the organizational level. This should also be possible at the project level. Secondly, add the possibility to grant access indefinitely until revoked.

    12 votes
    2 comments  ·  Other  ·  Admin →
    How important is this to you?

  19. billing

    The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.

    12 votes
    4 comments  ·  Other  ·  Admin →
    How important is this to you?

  20. Provide Atlas support for "Classic" VNet Peering topology

    Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT

    12 votes
    1 comment  ·  Other  ·  Admin →
    How important is this to you?
2 4 5 … 24 25
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)