1360 results found

1. Better streamlined logs in GCP

   Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the index or fine tune our query or change the code - making it super easy. But in our GCP Production every thing runs in GCP kubernetes and logs are stderr and stdout of kubernetes and app but no mongoDB even when MongoDB is deployed within GCP. GCP support stated that we can install Google Cloud Ops Agent can be installed to forward the logs to GCP but it seems that won't work as there will be lag. We were told to do a lot of work to make it work which is error prone. It should be out of the box so that any users are not tempted to use cloud native DB solutions that comes with public cloud and still use MongoDB. Please refer Case #01336915

   Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything running on Docker Desktop and MongoDB on local Windows laptop. Using Docker tilt - Dev team can see UI, Service tier and backend(MongoDB) logs one after the other in one place. If the request is timing out, we can see that it's a collection scan that is happening not index scan so we need to either create the… more

   2 votes

   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

2. Hard to find menus

   Either the MongoDB Atlas web interface is too complicated
   or the tutorials are missing steps, some menus are impossible to find.

   Example
   https://www.mongodb.com/docs/atlas/app-services/data-api/custom-endpoints
   Create a Custom HTTPS Endpoint
   1. Click HTTPS Endpoints in the left navigation menu and then click Add An Endpoint.

   ^ this is not the first step, the menu is not even visible, it is buried away under some advanced settings button, no where is it mentioned where to reveal this totally different "BUILD" menu section on the left hand side.

   There are lots of features hidden from view, almost impossible to access from the Top or Left menus. It doesn't seem like a good interface for all the features on offer.

   That aside, MongoDB is pretty cool thumbs-up

   Either the MongoDB Atlas web interface is too complicated
   or the tutorials are missing steps, some menus are impossible to find.

   Example
   https://www.mongodb.com/docs/atlas/app-services/data-api/custom-endpoints
   Create a Custom HTTPS Endpoint
   1. Click HTTPS Endpoints in the left navigation menu and then click Add An Endpoint.

   ^ this is not the first step, the menu is not even visible, it is buried away under some advanced settings button, no where is it mentioned where to reveal this totally different "BUILD" menu section on the left hand side.

   There are lots of features hidden from view, almost impossible to access from the Top or… 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  ·  Tutorials/How-tos  ·  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. Query profiler drilldown by number of write conflicts

   One sort of issue that can lead to elevated CPU utilization but is otherwise hard to identify is queries with high numbers of write conflicts. Having some way to drill down to queries that exhibit these symptoms would be quite convenient.

   2 votes

   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  ·  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. One tab or one button to quit from the whole platform without begging the support to help

   There is no simple way to quit the service and erase the data. You have to go though clusters, projects and organizations without any links provided. The links given in messages are misleading. I had to work with helpdesk for almost an hour just to delete all my data that included: 1 organization, 1 project and two 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  ·  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. Allow the Worforce Federation to be able to grant permissions on groups and user at the same time

   When Worforce federation is enabled you have to choose weather to configure your users based on id or on group membership.

   We want the ability to configure general base line permissions for groups based on the group claim on the oauth2 token and the username as well.

   This enable us to grant a baseline of permissions and is flexible enough to also grant certain snowflake individuals higher privelages.

   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  ·  Administration API  ·  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. Alerts on password reset in Atlas UI

   Alert should be sent on specific accounts in case of reset is initiated from 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  ·  Alerts  ·  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. logs push to s3 over private link

   Currently push to s3 feature transmits data over internet, due to possible presence of sensitive data in logs and to address security concerns push to s3 feature should support pushing logs over private link.

   3 votes

   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  ·  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. In Atlas, add an alert condition for long-running queries

   In Atlas, add an alert condition for long-running queries

   2 votes

   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  ·  Alerts  ·  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. Global Multi-Region Read/Write Databases with Serverless Atlas and Realm Device Sync

   Global Multi-Region Read/Write Databases with Serverless Atlas and Realm Device Sync

   As the world goes global, moving workloads and data closer to users for lower latency is becoming essential, even for startups that can't afford dedicated clusters. The ability to set up a global read/write, multi-region, serverless MongoDB Atlas would be a game changer.

   Currently, I am using a combination of two different database systems to achieve what MongoDB could provide out of the box, allowing us to start on a serverless scale and grow as our traffic and revenue increase. Unfortunately, we can't yet afford dedicated pricing, and this impacts our users' experience. The read/write latency between Australia and Europe prevents us from delivering the best possible service.

   Global Multi-Region Read/Write Databases with Serverless Atlas and Realm Device Sync

   As the world goes global, moving workloads and data closer to users for lower latency is becoming essential, even for startups that can't afford dedicated clusters. The ability to set up a global read/write, multi-region, serverless MongoDB Atlas would be a game changer.

   Currently, I am using a combination of two different database systems to achieve what MongoDB could provide out of the box, allowing us to start on a serverless scale and grow as our traffic and revenue increase. Unfortunately, we can't yet afford dedicated pricing, and this… 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. Expose just the server name (without the rest of the connection string) as a cluster attribute

    There are many connection_strings available, but all of them are a full URI. Since the canonical way to connect is with the login and password in the URI, I always need to parse the value of a connection_strings, insert login info, and then reformat it.

    I'd like to just have the server name available as an attribute.

    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  ·  Terraform Provider  ·  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. Improved deletion protection against malicious users

    Currently, the only option of preventing malicious admin users from deleting a cluster with all its backups is to enable a backup compliance policy. However, this policy is quite the beast with complex processes and guarded by a single user account (which could then as well be the malicious one).

    It would be good to have some less impactful way of protection against malicious users.

    For example, when deleting a project in Google Cloud, an email is sent to all project owners and the project including all of its data can easily be restored within a period of 30 days. This does not impact regular operation but also effectively prevents malicious users from causing permanent damage.

    Currently, the only option of preventing malicious admin users from deleting a cluster with all its backups is to enable a backup compliance policy. However, this policy is quite the beast with complex processes and guarded by a single user account (which could then as well be the malicious one).

    It would be good to have some less impactful way of protection against malicious users.

    For example, when deleting a project in Google Cloud, an email is sent to all project owners and the project including all of its data can easily be restored within a period of 30 days.… more

    7 votes

    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  ·  Administration API  ·  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. A new role for security auditing purposes

    Currently MongoDB Atlas provides two read only roles at project level ("Project Read Only", and " Project Data Access Read Only").

    "Project Data Access Read Only" seems to allow access to the data also, while "Project Read Only" role does not allow access to the logs. (https://www.mongodb.com/docs/atlas/reference/user-roles/)

    For security officers (internal/external), they need to access to the logs (audit, access, etc) and also to review the configuration; but don't need access to the data.

    Therefore, I would like to request a new project level role for security officers with following features.
    - access to "Download Logs"
    - access to "View Database Access History"
    - View-only access to all the configurations (with sensitive data are masked).
    - Do not allow access to data stored in the database.

    BR,
    Manjula

    Currently MongoDB Atlas provides two read only roles at project level ("Project Read Only", and " Project Data Access Read Only").

    "Project Data Access Read Only" seems to allow access to the data also, while "Project Read Only" role does not allow access to the logs. (https://www.mongodb.com/docs/atlas/reference/user-roles/)

    For security officers (internal/external), they need to access to the logs (audit, access, etc) and also to review the configuration; but don't need access to the data.

    Therefore, I would like to request a new project level role for security officers with following features.
    - access to "Download Logs"
    - access… more

    7 votes

    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

    1 comment  ·  IAM  ·  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. As a DBA I need to be able to create/delete a single backup policy via CLI/API

    As a DBA I need to be able to create/delete a single backup policy via CLI/API.

    For some projects, I would like to be able to create a single hourly policy.
    Currently it's impossible. Default policies are created and via API I cannot delete all the other policies one by one leaving just hourly one. I also can't delete all and add a single one.

    I would like this functionality to be available both in API and CLI.

    Currently you can only
    - delete all policies
    - update existing policy by policyId

    I need to be able to delete a single policy by id
    I need to be able to create a new policy without using policyId

    Currently in CLI only the following are available
    Available Commands:
    describe Describe a cloud backup schedule for the cluster you specify.
    update Modify the backup schedule for the specified cluster for your project.
    delete Delete all backup schedules of a cluster.

    As a DBA I need to be able to create/delete a single backup policy via CLI/API.

    For some projects, I would like to be able to create a single hourly policy.
    Currently it's impossible. Default policies are created and via API I cannot delete all the other policies one by one leaving just hourly one. I also can't delete all and add a single one.

    I would like this functionality to be available both in API and CLI.

    Currently you can only
    - delete all policies
    - update existing policy by policyId

    I need to be able to delete a… 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  ·  Data API  ·  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. Improve Atlas cost utilization tracking by time and label

    Currently for any Atlas instance, cost granularity is limited to the cluster. It would be a significant improvement to enable cost utilization tracking by database for storage and compute. Specifically, storage and cost records should be granular in time and label, where labels can be assigned to databases. That is, as a common example with GCP for example, costs should be tracked by second, and in the billing data, aggregated to the hour by label.

    This will allow chargeback, showback, and improved allocation methods for modern FinOps practices. As it is, MongoDB Atlas falls well short of any ability to align costs in a manner that many cloud customers expect and are using from all modern cloud providers.

    I would be happy to discuss this with your billing development product manager or other leads, and will appreciate your consideration of this improvement.

    Currently for any Atlas instance, cost granularity is limited to the cluster. It would be a significant improvement to enable cost utilization tracking by database for storage and compute. Specifically, storage and cost records should be granular in time and label, where labels can be assigned to databases. That is, as a common example with GCP for example, costs should be tracked by second, and in the billing data, aggregated to the hour by label.

    This will allow chargeback, showback, and improved allocation methods for modern FinOps practices. As it is, MongoDB Atlas falls well short of any ability 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  ·  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

15. Forward MongoDB Atlas logs to Securonix

    This is a feature request to integrate the forwarding of MongoDB Atlas logs to Securonix.

    2 votes

    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  ·  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. Backup Compliance Policy to enforce "Snapshot Distribution"

    Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.

    In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and also makes backup compliance policy feature comprehensive/consistent covering all backup related features offered by Atlas.

    Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.

    In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and… more

    4 votes

    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  ·  Backup  ·  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. Atlas - Queue cluster pause request to perform it when it's possible

    It is impossible to pause a cluster that was recently resume.

    The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.

    I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either staying later just to replay the pause or leaving the cluster running all night for example.

    I want to suggest you to improve this feature by recording the pause request and applied it once you finished your maintenances. You might introduce a new cluster state (terminating ?) to show to everyone that the cluster will be paused in few time.

    It is impossible to pause a cluster that was recently resume.

    The documentation indicates it is a voluntary feature (https://www.mongodb.com/developer/products/atlas/pause-resume-atlas-clusters/) to allow the Atlas service to apply any pending changes or fixes to the cluster that may have accumulated while it was paused.

    I agree with this, but it cause a problem for automation (for example sometimes we launch a platform exclusively for testing purpose and then shut it down, it is complicated to add a delay for pausing the Atlas cluster) and even manually for example at the end of the day of work this requires either… more

    11 votes

    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

18. The oplog configuration is a bit confusing

    The oplog configuration is a bit confusing. I think it's not clear that if we set the oplog window, we don't need to set the maximum oplog size. I believe this configuration should be more specific.

    •  

    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

19. Could we increase the vCPU's of the Atlas cluster without increasing its memory.(RAM)

    For example: suppose right now, we have 2 vCPU's with 8GB RAM. But we are facing high CPU utilization error. Can we change the vCPU's to 4 and keep RAM as it is i.e.8GB?

    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  ·  Resource Tagging  ·  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. Make the to delete indexes endpoint public

    In the Performance Advisor, the recommended indexes to drop are only avaible throw the cnsole. We would like to have this information available from the API.

    5 votes

    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  ·  Administration API  ·  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