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

1257 results found

  1. disabling mongo user

    Instead of completely removing a Mongo database user, its better if there is option to disable user so that if there is any untoward incident we can enable it back. After observing for some time, we can delete/disable the user based on organization requirements. Its useful in some cases like mongo db user returned to same department after some time .

    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  ·  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. Support NVMe for Atlas Azure

    Support NVMe disk for MongoDB Atlas Azure.

    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)
  3. Copy/Duplicate Cluster configuration

    It would be really useful to create a new cluster based on an existing configuration.

    Snapshots are supposed to be loaded into clusters of the same configuration, but having to set up the configuration manually is prone to human error. Having an option to copy the cluster configuration would be helpful.

    Support suggested the following workarounds, but the option should really exist in the UX, given that snapshots can be taken and loaded in the UX.
    - use the API to create all clusters so that the config exists in code
    - use terraform to create clusters

    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)
  4. View TOP N queries per CPU / memory / disk and number of execution for each query.

    This type of metric is common in relational databases and I think it's important to deploy in the Atlas interface.

    Top queries by CPU/memory and disk over a period of time or real time. It is important to have this visibility and improve the respective query(s).

    It is good to know how many times each query was executed during the respective analyzed period.

    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)
  5. 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  ·  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. be able to download cluster logs as minimun of 6 months

    there is no way to download cluster logs after one month, we have an issue of one process today and the cluster log shows the operations registered and the time spent, the same process ran a couple of months ago and it's impossible to know or check in the cluster logs the operations(insert,update...) if the process had an issue two or three months ago.

    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)
  7. Make the app_id optional in the mongodbatlas_event_trigger resource when an aws_eventbridge event processor is defined

    Currently, when you define a trigger that uses the AWS Eventbridge via the UI it auto creates a realm App that links the DB change to the event bridge.

    However, with the mongodbatlaseventtrigger resource you have to manually defined an empty realm app and give the resource the app_id of that empty app.

    This is obviously not a 100% automated process.

    This could be, if the provider created the empty realm app by itself, then referencing the created app app_id.

    This would only be needed:
    1. when the appid is not provided
    2. the following attribute was

    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. Compare and sync data across clusters

    I would like to have the ability to compare and sync collections across different clusters. The use case would be to support data migration between different environments.

    Like this feature from Studio3T
    https://studio3t.com/knowledge-base/articles/compare-mongodb-collections/?utm_source=post&utm_medium=fb&utm_campaign=3tslpage

    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)
  9. Add specific database API Metrics for MongoDB Atlas.

    A while back we ran into an issue where we ran out of connections in MongoDB Atlas. It took quite a while to determine which database was being overrun with bad connections. It would be very nice if the API, which we use to pull metrics into another monitoring platform, allowed us to get certain metrics at the database level instead of the overall system level. The metrics I am suggesting are
    Active Connections
    Response Time
    Failed Connections
    Number of requests
    Operation Execution Time

    These would help us more quickly discover the source of the problem and trace it back…

    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. Database Audits information

    Add information to event source audit logs.

    For example, I add in the Atlas portal a new user with access to databases.

    When I download the cluster level audit file, I only find the information that the user was added by "mms automation", I don't have any information on which user or API Key was used for create this new database user. It is therefore very difficult for the monitoring team to verify if the user was created by an authorized user or API Key.

    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)
  11. Add Tailscale peering

    In lieu of doing 0.0.0.0/0 network access, it'd be great to peer into Tailscale so that anyone that is authorized in our organization's Tailscale VPN can connect effortlessly.

    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)
  12. Separate access control for read-only replicas

    There is a multi-replica cluster and there are read replicas. I consider it necessary to add the ability to restrict access separately for a read-only replica. Thus, limit the connection not only to the entire cluster at the project level, but also to specific replicas (for example, limiting access to read replicas).
    I think that this is a standard business problem, the solution of which is simply necessary to exist in a product like yours.

    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  ·  IAM  ·  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. provide more details on the replica set elected a new primary

    today the details on this event are very low and have only the replica set name which is not enough, can you also add the correlated cluster name to the exposed details?
    more over if this is something that can be monitored by the metrics going to Datadog?

    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  ·  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)
  14. Allow access from anywhere button to be a separate UI permission

    "allow access from anywhere" button should be a separate privilege. This would allow the ability to add it to a role. The goal is to allow developers to log into the control plane, use the UI to add 1 single IP(theirs)...but not open up IPs to all(0.0.0.0/0).

    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  ·  IAM  ·  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. Warm up cache automatically when there is any server/node restart events

    Usually it takes hour or so for the cache to warm up depending on the data size when an server restart scenario occurs ( increasing the tier / storage etc). And there are alternatives like running cache warm up queries to bring the nodes up to speed .

    However if this cache warm up should be inherent and automatic for the server restart scenarios .

    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. Add the In-Memory Storage Engine to Atlas

    Enable the use of the in-memory storage engine in atlas shards. That way atlas users can get the same level of functionality as enterprise. Atlas is a great platform, but not being able to use an in-memory storage engine replica set in a shard is a huge letdown (at least for me).

    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  ·  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)
  17. Send alert on mongodb database users changes and permission changes

    This will be a important tool to get alerted if any databases get exposed or hacked.

    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)
  18. Pending updates alerts

    I'd like to be able to have alerts for all those databases that are using a version that is not the latest major version available.

    This will help to be more proactive so that updates can be planned in advance without the need to manually review the available versions from time to time. It will also help in the implementation of security controls such as SOC2.

    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  ·  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. 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)
  20. Support Linode as a cloud service

    Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.

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

Feedback and Knowledge Base