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

1186 results found

  1. Kubernetes AtlasProject backup compliance

    Extending the AtlasProject Kubernetes resource to allow management of a backup compliance policy, including setting project-wide backup schedules and enabling backup persistence after termination by default, would be a major improvement over the current experience.

    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)
  2. Kubernetes reconcilation interval

    Kubernetes resources generally should be reconciled on a sensible schedule to prevent configuration drift between k8s and Atlas API.

    AtlasProject is a critical one that can have widespread impact if API configuration drifts from Kubernetes and is not promptly corrected.

    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)
  3. DataDog integration: add metrics for any current resource limits

    We're using the DataDog integration to bring MongoDB metrics to DataDog. We want to re-create a DataDog monitor which is an equivalent to Altas alert "Connections of configured limit has gone above <>". However, we cannot do that relying solely on metrics, since the only connection related metric we found is "mongodb.atlas.connections.current".
    It looks like the only way to solve this issue is to create a DataDog monitor based on the received event from 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

    0 comments  ·  Integrations  ·  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. Retrieve latest/max oplog timestamp via the Atlas Administration API

    At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.

    For example, in the UI it states:

    You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.

    Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.

    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)
  5. Enable database users separate read/write permissions based on cluster

    We have multiple clusters in the same project, and we need to limit write access to certain CLUSTERS while leaving read only access to any other cluster. The problem is that we cannot do this by DATABASE name as there are many of them, as well as dynamically addition of new ones in clusters, so it will become obsolete and very hard to maintain.
    Trying to use the restriction does not help as it limits all access, including read only, to those clusters.
    What we'd like to see is that we can limit write access by cluster (not database/collection) and…

    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)
  6. Integrated Benchmark utility for mongodb

    I would like to request a mongodb utility which can do benchmark tests and can be used by developers and DBA to test mongodb for release changes, application code changes etc. The utlity should be able to simulate multiple users and produce different types of workloads (like reads, updates, deletes, inserts etc). This would need to be similar to other nosql benchmark tool like asbench used in aerospike nosql database.
    Link is : https://docs.aerospike.com/tools/asbench

    4 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)
  7. Hyperlink to "all cases" that's under the "create new case" link

    To access the support portal from the projects page:

    • Navigate to Support to the left side of the page
    • Click on Visit Support Portal button under Request Support

    It will be easier to navigate if a hyper link of "all cases" can be added to "create new case" from the "get help" drop down as in screenshot attached.

    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)
  8. Monitoring Metrics on dhandle

    We'd like to monitor the WiredTiger dhandle over the time, directly from Cloud Atlas Monitoring view. It would allow to directly see the impact when updating cluster settings.

    We'd like also being able to configure alert triggers on it, the goal for us is being alerted when an excessive amount of files (collections & indexes) is loaded into the MongoDB Memory, to avoid reaching an Out Of Memory error.

    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. Improve Atlas suggested indexes

    Suggested indexes
    - Currently it will suggest indexes that can't be created, such as with multiple array fields.
    -- This should be detectable before suggesting an index.
    -- Highlight array fields in the suggested index
    - Include partial index expressions
    - Make more than one suggestion for queries

    Trying to create an index that contains multiple array fields (for some documents being indexed) won't fail until it hits one such document.
    - Pre-parse to first confirm the fields being indexed don't include more than 1 array for the index?
    - Pre-parse and inform the user if any of the fields…

    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. LDAP Users shouldn't be successfully authenticated if not authorized

    Today, if you login with proper LDAP credentials to an Atlas cluster, you are authenticated into that cluster, even if you are not authorized to have access. This is not at all how databases should work, nor is it how most databases do work today. If a user is not authorized, that connection should fail immediately.

    Allowing successful authentication, even when not authorized, can increase the security vector for ddos attempts as well as causes confusion when successful attempts are logged, even though the user was not authorized to see data.

    Please reject any non-authorized user from connecting to an…

    4 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)
  11. Exponential Backoff

    Exponential Backoff:

    Data come from AWS event bridge, connection issues happened
    Exponential backoff would have helped that that this connection issues are recognized and the customer would not have intervened manually.
    There was no alarm once trigger was suspended - an automatic alarming would have been helpful.

    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  ·  Integrations  ·  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. Duplication detection

    One of our custmoers would like to see duplication detection as their project is spread out over various projects.

    Value: It is important as different regions create sometimes duplicates and duplicates can be avoided in advance.

    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. Add document count to Datadog metrics

    We'd like to monitor the number of documents in a collection via DataDog.

    For On-Premise MongoDB the stats are already reported via mongodb.collection.count, mongodb.collection.size and mongodb.collection.avgobjsize.

    If the same metrics could be made available for Atlas (E.g. mongodb.atlas.stats.collection.count) that would really help in monitoring.

    E.g. spikes in different parts of the application could be tied to the number of documents on a glance. Without having that metric available, it is hard to pinpoint if a recent change had a negative impact on performance.

    If the metrics can't be made available on the collection but only on the database level, this…

    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)
  14. Monospace font for Atlas project user creation fields

    When you start a new project using Atlas, a username and password are suggested. The username and password fields use a font with almost identical lowercase L and capital i.

    My suggestion is to use a monospace font in those fields for disambiguation.

    I use a password manager on my phone (as do, I imagine, many others), which means it’s very annoying to have to figure out if a character is an l or an I on the computer every time I have to copy down info for a new project.

    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)
  15. Add a command to set cluster to read only mode in MongoDB

    Relational databases (oracle, mysql, postgres) provide a single command to change a database to read only mode. e.g. alter system set database read only; This is often used to enable read only access to a cluster that is in process of being upgraded, or provide a look back to verify functionality or setup post upgrade. MongoDB should implement such a feature.

    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)
  16. enable a specific set of tags to go in the logs.

    Enable a specific set of tags to go in the logs.

    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  ·  Resource Tagging  ·  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. attribute based access control on the roadmap? Authorization based on tag value

    attribute based access control on the roadmap? Authorization based on tag value

    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  ·  Resource Tagging  ·  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. Include IdP Group and Atlas Role mapped in the ROLE_MAPPING_CREATED event

    When an Atlas Role is mapped to an IdP group in the Federation Management Console, an event is created with the eventTypeName "ROLEMAPPINGCREATED" and the description "A Role Mapping was Created". The event returns in both the Atlas Admin API events endpoint and the Organization Alerts. It would be beneficial for auditing to include the IdP group and Atlas Role in the event.

    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  ·  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)
  19. Datadog integration for AP1 region

    I am using Datadog region AP1 (Japan) and I learned that Atlas doesn't support the region for the integration.

    It would be really great and helpful if the integration supports the AP1 region.

    https://docs.datadoghq.com/getting_started/site/

    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. Cluster configuration protection

    I would like to request adding a configuration protection feature in MongoDB Atlas. In our client's scenario, the DBA must manage multiple clusters simultaneously, posing the risk of accidental misconfigurations. Therefore, the client's feedback is that hope MongoDB Atlas can have the option to enable configuration protection so that any adjustments or changes require disabling the configuration protection first

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

Feedback and Knowledge Base