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

1258 results found

  1. Create new Atlas Alerts integration - Integrate with Atlas App Services HTTPS Endpoints with Authentication

    Today we can integrate Atlas Alerts with Atlas App Services HTTPS Endpoints (App Services function) using an Atlas webhook but the process is not easy and the use of webhook requires the alert data traverses the internet. Instead, create an built-in integration that does not traverse the internet but instead uses a private secure communication channel, that also uses Atlas App Services authentication including App Services user definitions.

    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  ·  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. Atlas feature request

    While adding access for teams to a project in Mongo UI, there should be an option to limit access to a particular cluster.
    For example: If there are 3 clusters in a project, then team 1 should have access only to cluster1 and team2 to cluster 2 and so on.

    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  ·  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)
  3. Need new redundancy node type

    Atlas requires that the use of Private Service Connect for a geo-replicated cluster, requires PSC to be configured in all regions that cluster is in.

    The best practice for a DR configuration in Atlas is to have a 2-2-1 configuration over 3 regions so that the cluster fails over automatically in the case of a region outage and there is no split-brain possibility.

    The applications themselves really only need to be in 2 regions. The requirement for a PSC in the 3rd region, along with a customer-side project to host that connection is wasteful. This situation is especially problematic in…

    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)
  4. AWS multi-region key (CMK)

    While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.

    https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html

    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)
  5. Add support for HTTP based scraping without IP restriction

    Prometheus supports a lot in the HTTP scraping space, including oauth and Bearer token based scrape targets.

    Currently we use Grafana cloud that has a list of IP address that can scrape from. This "can" change, and if it does and we hardcode this access into Atlas based on IP then it will break the scrape.

    Could Mongo add support for token/oauth based scraping. Where we provide these tokens in a HTTPS call?

    I think this would solve the issues with things like private link, or peered network connections. It would also allow "any" prometheus server that can make outbound…

    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)
  6. 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)
  7. Allow switching between shards in the profiler and/or have a combined view

    Since the profiler tabs are shard specific, it would radically improve the usability to:
    a) Combine the profiler events to truly have a cluster level view so you don’t need to worry about shard specific views
    b) Add a drop-down to the top of the page near the title that has the various shards listed in it, selecting a different shard brings you back to the same tab, but now with the changed view.
    c) Consider tweaking the URL so that rather than using a SHA in the URL, you use the shard name, making it easy to manipulate the…

    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)
  8. Encryption at rest with our own keys - Manage alert and shutdown parameters

    It would be interesting to improve the encryption at rest feature in order to be able to define the alert parameters in case of unavailability of the key as well as the delay before a Replica Set fails.

    for example. I want to be alerted if my key is not available x times in the last 10 minutes and stop the replica game after 60 minutes if the situation is not resolved. This makes it possible for the support team to take corrective action without causing downtime.

    8 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  ·  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)
  9. Mongo DB alerts for latest version or release

    Automatic alerts from Mongo DB Team for the latest releases / versions available similar to the EOL(End of Life) alerts.
    This helps in planning the changes and upgrades reducing the manual effort on searching for latest versions.

    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  ·  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)
  10. More granular user privileges for Database User in same project

    When having several clusters in the same project, it would be nice if we could configure different privileges to different clusters for the same user credentials.

    Like in the following example

    Name | Cluster1 | Cluster2 | Cluster3 | Cluster4
    User1 | R/W | R | R | R/W
    User2 | R | R/W | R | R

    Currently it's not possible to specify different privileges on the cluster level.

    8 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  ·  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)
  11. Read your login suggestions.

    Possibly implement a suggestion... It's horrible. It's been horrible from day one. You don't need to re-imagine logging in, okay

    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  ·  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. Multiple connection URLs for Atlas clusters

    Allow generation of multiple application-specific connection strings/URIs to the same Atlas cluster. This would ease migration of databases to different clusters over time; consolidating smaller databases to lower costs, or separating busier databases to isolate performance impact.

    Multiple connection strings will allow us to redirect connections seamlessly when migrating databases without requiring developers to re-deploy changes to application connection strings, minimizing downtime and coordination.

    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)
  13. Allow killing operations in the RTPP without having to enable the Data Explorer

    Please prioritise the decoupling of the ability to kill operations in the Real Time Performance Panel from the Data Explorer.

    Currently we disable the Data Explorer on our production projects so that our developers can view the Profiler and the Metrics, without being able to query the actual data. But disabling the Data Explorer prevents us from killing operations in the Real Time Performance Panel. While reenabling the Data Explorer is an easy task, it's very easy to forget the one needs to do this in order to be able to kill operations as they do not seem related in…

    8 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. 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)
  15. Link two different clusters to the same Vercel app with the Vercel Integration

    At the moment, one can only link one cluster to a Vercel app (which creates a MONGODBURI variable in Vercel). It would be nice to be able to link another cluster (e.g. a dev cluster) to the same vercel app by customising the name of the MONGOBURI variable created (e.g. MONGODBURIDEV).

    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)
  16. Support export Prometheus metrics via remote_write

    High throughput prometheus compatible database like mimir, thanos, and the likes of GCP's managed prometheus really like metrics sent to them via remotewrite https://prometheus.io/docs/prometheus/latest/configuration/configuration/#remotewrite. Grafana cloud for instance doesn't allow you to configure any scrape rules. The only option is to push metrics to them.

    Currently Atlas only allows you to scrape metrics, which means for a user to get these metrics into a highly available version of Prometheus you need to relay this off of an intermediary process (prometheus exporter or a standalone prometheus server that supports scraping)

    I think a good addition to this capability would…

    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)
  17. 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)
  18. Allow atlas integration with Jira to create tickets directly based on Atlas alerts

    Atlas alerts setup should be able to directly create a ticket in the Jira board to the respective team. This will resolve the burden to check email alerts for alll the setup alerts.

    Instead, we can setup the critical alerts in such a way that it will directly create a Jira ticket.

    Thanks,
    Rohan Kumar

    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)
  19. Reshard Global Writes Collections

    MongoDB supports resharding, so not being able to change the global writes shard configuration is very strange. It makes it impossible to fix mistakes with the shard configuration. Even if it requires blocking to redo or remove the shard configuration it should be possible.

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

Feedback and Knowledge Base