1366 results found

1. Provide a more granular breakdown of monthly Atlas billing (in the Azure dashboard)

   Provided more flexibility/transparency into the monthly Atlas spend for Azure marketplace customers (in the Azure billing dashboard). Ie. allow users to break down spend by project, tag, cluster etc.

   Currently, only a single total monthly spend value is available in the Azure dashboard, with no additional details.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Mongodb Atlas in the ca-west-1 AWS region

   AWS is releasing the ca-west-1 region in H1 2024. We currently use MongoDB Atlas and would like to see serverless instances in this region come available at approximately the same time.eryt

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Serverless Instances  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. online archive

   Enable MongoDB Online Archive in Azure South Africa Northen Region.

   As a Nedbank client we got an urgent requirement to do archiving on a current solution and use it as a pattern moving forward for new and current project deployments. This will enable Nedbank to be in line with its deployment patterns.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Online Archive  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Restrict Organization Subscription/Credit to certain Project(s)

   We want multiple internal groups to belong to a single Payer Atlas Organization for our company to simplify management but those groups also have separate internal cost centers.

   Currently if any single project purchases atlas marketplace subscriptions or commitment subscriptions, they can be consumed by all projects in the Organization (and linked organizations). We want to ensure that only the projects for that purchased the subscription can utilize the subscriptions they paid for.

   This is similar to AWS Compute savings plans, where by default they are spread/utilized by any member organization account but you have the flexibility to restrict only certain accounts which can utilize the savings plan that they purchased.

   This will greatly simplify our internal chargeback models and push more teams to purchase commitment subscriptions which are a nightmare to manage across teams in the current model.

   We want multiple internal groups to belong to a single Payer Atlas Organization for our company to simplify management but those groups also have separate internal cost centers.

   Currently if any single project purchases atlas marketplace subscriptions or commitment subscriptions, they can be consumed by all projects in the Organization (and linked organizations). We want to ensure that only the projects for that purchased the subscription can utilize the subscriptions they paid for.

   This is similar to AWS Compute savings plans, where by default they are spread/utilized by any member organization account but you have the flexibility to restrict only… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. Ability to create mirror/snapshot clusters for load and behavior testing

   We would like to request the following:

   1. The ability to create a "mirror" or "snapshot" of a production cluster to a staging cluster.
   2. This could be either real-time or scheduled (once per day, once per week, etc.) If scheduled, it would be nice to be able to spin up a new cluster each time it's mirrored (so that previous mirrored cluster remains available)
   3. The mirroring should be allowed to use a different hardware type, for example, our production cluster uses NVME disks, but our mirrored cluster we'd use cheaper HDDs with lower CPU.
   4. The mirrored cluster should be allowed to use a different MongoDB server version than the one it replicated from.
   5. When mirroring, have ability to exclude collections and exclude/mask certain fields within a collection (e.g. via an aggregation pipeline-like syntax)
   6. Ability to get API triggers when the mirrored cluster is copied and ready. We would use these triggers to perform additional actions such as switching our staging environment to point to the new cluster, inserting/removing data manually, etc.
   7. Have ability to mirror production cluster query traffic to the mirror cluster, i.e. for load-testing. This is particularly useful when upgrading database version, or experimenting with different instance types. Having the ability to "sample" queries (e.g. 1-out-of-10 queries gets mirrored) would be useful, and also to restrict any data insertion so the queries are read-only.

   Related to: https://feedback.mongodb.com/forums/924145-atlas/suggestions/40311163-option-to-restore-one-or-more-db-from-snap-to-clus

   We would like to request the following:

   1. The ability to create a "mirror" or "snapshot" of a production cluster to a staging cluster.
   2. This could be either real-time or scheduled (once per day, once per week, etc.) If scheduled, it would be nice to be able to spin up a new cluster each time it's mirrored (so that previous mirrored cluster remains available)
   3. The mirroring should be allowed to use a different hardware type, for example, our production cluster uses NVME disks, but our mirrored cluster we'd use cheaper HDDs with lower CPU.
   4. The mirrored cluster should be allowed to… more
   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Enforce MFA for google login users

   Our organization needs to enforce MFA for users signing in with google login. Is there any way to do it other than "Require MFA"?

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Data Usage Reporting & Improved Profiler

   The Current Problem:
   The existing issue stems from MongoDB's inability to provide concrete evidence supporting the data charges for your data usage. This predicament becomes especially troublesome when your system typically operates within a data usage threshold of less than 100GB daily. Suddenly, over a span of 7 days, you are billed for data usage exceeding 1000-2000GB daily, only to subsequently revert to using less than 100GB daily. The absence of substantiated evidence leaves you in a quandary, unsure whether the issue lies with your system or is a reporting error on MongoDB's part. MongoDB Support relies on the slowest queries from the profiler as evidence; however, it's essential to note that these queries have persisted both before and after the anomaly.

   Feature Request:
   The proposed feature request centers on the creation of improved data usage reporting, aiming to address the aforementioned challenges. This feature would empower users to access comprehensive data consumption reports which would provide quantifiable evidence to reconcile data usage discrepancies. Key additions include enhancing the Profiler to provide an option to display all queries, not limited to just the slow queries. Additionally, a report should be introduced, offering precise insights into data usage, broken down by cluster, node, and collections per day. This report should tally the number of queries to each collection, along with the amount of data retrieved by each IP Address and user that queried that collection. These comprehensive reports are pivotal in facilitating a more effective understanding of invoices and Atlas Costs.

   The Current Problem:
   The existing issue stems from MongoDB's inability to provide concrete evidence supporting the data charges for your data usage. This predicament becomes especially troublesome when your system typically operates within a data usage threshold of less than 100GB daily. Suddenly, over a span of 7 days, you are billed for data usage exceeding 1000-2000GB daily, only to subsequently revert to using less than 100GB daily. The absence of substantiated evidence leaves you in a quandary, unsure whether the issue lies with your system or is a reporting error on MongoDB's part. MongoDB Support relies on the slowest… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Ability to have UI Users with access to list Indexes but not browse collection documents

   We'd like to have users that are read-only and that have access to see metrics and list indexes but not do operations or be able to explore the collection documents.

   This is important for application developers to be able to operate their databases without needing to have read access to contents.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Data Explorer  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Incremental backup on Serverless Instances

   Hey,

   I would like to know when the access read/write of the "oplog" collection in the "local" database will be enabled in Serverless instances. I need this access for making an incremental backup/restore of the database. The doc does not explain the reason of this limitation and I would like understand why.

   There is mainly 2 reasons of my request. First is for a local backup/restore for dev purpose, I don't need/want to restore all the databases each time in local due to the size and time consuming from the restore. The second one is that if I need to restore one database in the project, or even one collection of one of the database, I can not. The snapshots restore all the databases from a fixed time and that's not what I want.

   Thanks in advance for the answer.

   Hey,

   I would like to know when the access read/write of the "oplog" collection in the "local" database will be enabled in Serverless instances. I need this access for making an incremental backup/restore of the database. The doc does not explain the reason of this limitation and I would like understand why.

   There is mainly 2 reasons of my request. First is for a local backup/restore for dev purpose, I don't need/want to restore all the databases each time in local due to the size and time consuming from the restore. The second one is that if I need to… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Serverless Instances  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Prevent exposure of Azure Vault or KMS

    Today Mongodb communication with the BYOK key is by internet, it is necessary to allow public IPs:

    https://learn.microsoft.com/en-us/azure/key-vault/general/private-link-service?tabs=portal

    https://learn.microsoft.com/en-us/security/benchmark/azure/baselines/key-vault-security-baseline

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Integrations  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. List user id in access screen, needed for project owner id in when setting up a project inpulumi

    As title. I want to easily find user IDs from teh Atlas UI

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Export only selected Atlas metrics

    This is a request from a customer named: UPAX partnered with Grupo Salinas.
    Inside the cluster metrics, where the Status is displayed, we are able to find the Export option (PDF, PNG) and they would like to export for only specific metrics (only the toggle charts) not the whole of them for reporting purposes with other teams and management.

    • 

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. CORS on the Atlas API

    The Atlas API does not yet support CORS. Without CORS, calling the API from within a browser, using a React Client, for example, fails the 'preflight checks'.

    "...has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource...."

    If the Atlas API could add the 'Access-Control-Allow-Origin: *in the header response, then browsers would permit the API to be called.

    Note: for the pre-flight check, the browsers call the OPTION method.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Set Customer Managed Key (CMK) for wiredtiger encryption at the Organization level

    For Organizations with a large number of projects, it is cumbersome to rotate keys for every project. If there was an option to set a default at the Organization level, and maybe override by CMKs set at project level, it will reduce the effort of key rotation for every project.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. ATENDIMENTO PERSONA

    TER MAIS RELAÇÕES DE DADOS INDIVIDUAIS SOBRE CADA CLIENTE, AGRUPAR EM DE MODO CURTO COMO UM ATALHO AS REGIÕES MAIS PROEMINENTES DE USO QUENTE OU FRIO DO EMPREENDIMENTO, OU SEJA, O DEDICADO COM OS CLUSTERS.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Hello, I had a superb consultative experience with Colin Phillips. He assisted me with understanding support options for a website database

    Colin Phillips provided superb and outstanding help to me with the next steps for realizing my dream project.
    
    With Gratitude, Amilcar

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Code support

    Your website is a monster where is very difficult to get the useful information.

    I wanted to use Realm to use a mongo cluster and after hours trying I give up.
    I couldn't connect to the cluster after I created serveral ids (app, api, another api id, ...)

    Solution: Let's say I have a single cluster and a single realm app created.
    Just give me the code with all the ids necessary.

    In my case I wanted to run it from the browser.
    This is the code I tried to execute:

        const app = new Realm.App({ id: 'tradeapp-bozmd' });
        const credentials = Realm.Credentials.apiKey('51f080c1-f0f7-41de-a69c-9a408db76e57');
        // Authenticate the user
        const user = await app.logIn(credentials);
        // `App.currentUser` updates to match the logged in user
        console.assert(user.id === app.currentUser.id);
        this.db = user.mongoClient('mongodb-atlas').db('TradeTeam');
        console.log("this.db :", this.db )
    

    One of the issues was that I couldn't find anything about Realm inside cloud.mongodb.com. I had to search on internet (gpt told me about Realm). Terrible.

    Simplify your website. What a terrible design.

    Your website is a monster where is very difficult to get the useful information.

    I wanted to use Realm to use a mongo cluster and after hours trying I give up.
    I couldn't connect to the cluster after I created serveral ids (app, api, another api id, ...)

    Solution: Let's say I have a single cluster and a single realm app created.
    Just give me the code with all the ids necessary.

    In my case I wanted to run it from the browser.
    This is the code I tried to execute:

        const app = new Realm.App({ id: 'tradeapp-bozmd' });
        const

    … more
    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Atlas Role

    The idea would be to have more advanced options when configuring access management to different projects/clusters.

    A lot of companies would benefit greatly from seeing a segregation of roles and access to different features on a project.

    It would be beneficial to have more read roles - focus on the metadata layer, but it would be also nice to have it on the DB level e;g. Onboarding a local entity - DBAs want to see only dedicated DB information - should be then between their responsibility.

    The idea is to have differentiation between metadata and data, It can be particularly useful for holding companies who don't want to expose advanced rights to most users, narrowing the view of what can be seen.

    The need for more in-depth user validation and granular permissions on each cluster/DB is key going forward to ensure confidentiality within different projects.

    The idea would be to have more advanced options when configuring access management to different projects/clusters.

    A lot of companies would benefit greatly from seeing a segregation of roles and access to different features on a project.

    It would be beneficial to have more read roles - focus on the metadata layer, but it would be also nice to have it on the DB level e;g. Onboarding a local entity - DBAs want to see only dedicated DB information - should be then between their responsibility.

    The idea is to have differentiation between metadata and data, It can be particularly… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  IAM  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Kubernetes AtlasDeployment snapshot persistence flag

    When AtlasDeployment resources are deleted, the cluster is immediately terminated without the opportunity to enable snapshot persistence after deletion as there is in the Atlas UI. An option in the spec should be added to opt-into this behavior from a Kubernetes perspective.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

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

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Kubernetes Operator  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    started  ·  AdminDan (Admin, MongoDB) responded

    It will be coming in a release in the next few weeks!