1358 results found

1. create API keys that support linked orgs

   It is possible to link multiple orgs to each other. It should therefore be possible to use a single API key to access all linked orgs.

   12 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

   2 comments  ·  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

2. Disk queue length metric

   Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).

   Would it be possible to add this metric to Atlas monitoring?

   12 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

3. Allow db.killOp() and manual restarts on secondaries

   Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
   Also please add the ability to manually restart secondaries, not just failover the primary.

   Thanks.

   12 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

4. Allow option to configure default project_owner when creating projects through API key

   We're currently using the Atlas Service Broker (https://github.com/mongodb/atlas-osb) which is built using the native Atlas REST APIs.

   In the project creation, it creates the project using the POST /api/atlas/v1.0/groups endpoint via an API key. As a result, we have an unexpected user added as the project_owner of the project.

   THis is due to:
   IMPORTANT

   To create a project using API Key credentials, you must specify an orgId. When you do, Atlas automatically selects the Owner of the specified organization with the earliest account creation date and time as the Project Owner for the newly created project.

   The API should be expanded to allow for a user to be configured as the default project owner, or the project should not require a default project_owner at all when it is created via an API.

   We're currently using the Atlas Service Broker (https://github.com/mongodb/atlas-osb) which is built using the native Atlas REST APIs.

   In the project creation, it creates the project using the POST /api/atlas/v1.0/groups endpoint via an API key. As a result, we have an unexpected user added as the project_owner of the project.

   THis is due to:
   IMPORTANT

   To create a project using API Key credentials, you must specify an orgId. When you do, Atlas automatically selects the Owner of the specified organization with the earliest account creation date and time as the Project Owner for the newly created project.

   The API… more

   12 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

   3 comments  ·  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. Live Migrate modal: Allow users to point and click to select another Atlas source cluster

   It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project with minimal downtime).

   Currently, the Live Migrate modal requires connection details from the source cluster, including the hostname of the primary, port, etc. Validation will fail if there are typos/errors in these inputs.

   It would be easier to have a point-and-click option to "Migrate from another Atlas cluster" -- it could be a drop-down menu with names of other Atlas clusters in the project/organization that could be selected. The required connection parameters could then be automatically populated based on the particular cluster. A temporary user with the required permissions could even be created and then removed after the migration is complete.

   This could make it easier to start Live Migrations between Atlas clusters, and avoid the need for the user to locate and confirm specific source connection requirements.

   It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project with minimal downtime).

   Currently, the Live Migrate modal requires connection details from the source cluster, including the hostname of the primary, port, etc. Validation will fail if there are typos/errors in these inputs.

   It would be easier to have a point-and-click option to "Migrate from another Atlas cluster" -- it could be a drop-down menu with names of other Atlas clusters in… more

   12 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

6. Have the ability to downgrade

   Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?

   As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster name. And on top of that, you have to take a longer outage to move all of your data between clusters.

   Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?

   As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster… more

   12 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

   2 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

7. Via API call invite existing atlas user & assigne them to project & teams

   in are organization we want user to have a self serve service that allow them to create project, cluster ,etc ...

   for now we can only automate half of the process, because we need the web UI to invite user & wait that they approve the invitation before assigning them to project.

   It would be great than we could, via API call, invite user & assign them to project or team without having to use manual process & wait for user to acknowledge the invitation

   thanks

   12 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

   started  ·  0 comments  ·  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

8. Log browser and log search capability across replicaset nodes.

   Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.

   12 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  ·  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

9. Private Endpoint Tags / Custom Names

   Private Endpoint names are not user friendly, they are just Amazon resource ID's. If you have multiple Private Endpoints for a project this makes it difficult to select the right one. It would be nice if these endpoints could be tagged or have custom names.

   12 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  ·  Resource Tagging  ·  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. Profiler should only watch queries from certain users

    It would be useful to provide the profiler an "allowlist" and "denylist" of users to watch queries from. Essentially, it is only useful to receive alerts and profiler reports for queries made by actual applications. It is not useful to have alerts show up for one-off queries made by a DB admin using a DB explorer.

    12 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

    2 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

11. Being able to change the cluster name

    a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..

    12 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

    3 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

12. Improve 2FA and auth management

    Right now, there is no way to require Google auth or to require 2FA. The only way to enforce 2FA for a team is to check the team mangagement page. However, since some users may have only used Google auth to login, they will show up in this view as not having 2FA, creating auditing headaches. Please
    - indicate if a user does not have 2fa because they do not have a password vs just not having 2fa
    - ideally, add the ability to require 2fa and/or Google auth for all team members

    12 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

    6 comments  ·  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. Show a graph of BANKED iops (AWS)

    Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)

    Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
    During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.

    It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight as to when we need to scale up.

    Atlas monitoring is great... but it would be super helpful to see a graph of banked iops. (or an approximation of this)

    Suppose my iops limit is 100... and during the night my bank gets fully charged to 5.4MM.
    During the heavy loads on my server, let's say my iops jump to a steady 500. This means that I am drawing 400 units from my bank. I can do this for 3.75 hours until my bank is exhausted.

    It would be so helpful to see an iops bank balance drawing down during peak, recharging during off-peak... and thus getting insight… more

    12 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  ·  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

14. Enable Terraform export of HCL for existing Atlas configurations

    Allow for a standardized export tool that outputs Terraform HCL from existing, manually provisioned Atlas resources (e.g., projects, clusters, users, role mappings, et cetera). This would be similar to GCP's Terraformer or Azure's Export for Terraform.

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

15. Activity feed filters - allow filtering by cluster node name

    We need to be able to filter the activity feed based on the name of the cluster's nodes, not just the name of the cluster itself.

    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

    2 comments  ·  Activity Feed  ·  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. Allow customization of where $merge creates the temp collection used when rehydrating data from Online Archive --> Atlas

    When you restore data from the Online Archive back into your Atlas cluster (aka "rehydrate") you need to use $merge within an aggregation pipeline. What isn't documented is that $merge will create a temporary collection in the same database you're rehydrating to, which requires that you have readWrite@<dbName> privileges so that the new collection can be created.

    For customers that operate on the "principle of least privilege," where you only grant literally exactly what is needed to accomplish database CRUD operations, the user would the more narrowly scoped "readWrite@<dbName>.<collName>" privilege granted to the user to scope the actions to only the collection itself, thus not opening up readWrite capabilities for other collections in the same DB. For those customers, the $merge will fail with an error like:

    MongoServerError: failed to execute $merge into <DB>.<COLL>: not authorized on <DB> to execute command { aggregate: "tmp.agg_merge.d8af7e12-3f40-4b9c-b0b8-a9aef271a89f", allowDiskUse: false, comment: "via Atlas Data Federation, correlationID = xxxxxxxx", pipeline: [ { $merge: ...

    Since those narrow privileges won't permit the creation of the "tmp.agg_merge.<UUID>" collection within the DB they're rehydrating data to. Adding an option to the $merge aggregation stage that would allow the customer to control which DB the temp collection is created in, or to explicitly specify fully namespace of the temp collection (so that they can pre-grant the privileges needed for the user within Atlas) would allow customers to not have to violate internal security policies in alignment with the "least privilege needed" paradigm.

    When you restore data from the Online Archive back into your Atlas cluster (aka "rehydrate") you need to use $merge within an aggregation pipeline. What isn't documented is that $merge will create a temporary collection in the same database you're rehydrating to, which requires that you have readWrite@<dbName> privileges so that the new collection can be created.

    For customers that operate on the "principle of least privilege," where you only grant literally exactly what is needed to accomplish database CRUD operations, the user would the more narrowly scoped "readWrite@<dbName>.<collName>" privilege granted to the user to scope the actions to only… 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  ·  Online Archive  ·  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. Ability to schedule "Hedged read" Turn on/off

    Customer experienced read latency during maintenance after sharding.
    Our guidance is to turn on "Hedged read" option.
    So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.

    Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.

    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

    1 comment  ·  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. 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

19. Serverless instances on AWS South American region

    It will be nice to have serverless instances on AWS South America. This model is great for this region and I strongly believe that it can have a lot of demand.

    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

    4 comments  ·  Serverless Instances  ·  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. change streams serverless

    Hi. I need the "change streams" feature implemented for serverless deployments.

    At this time it's unclear when will it be implemented, hence it's difficult to plan ahead.

    Why is that important?
    My nodejs app relies on change streams. Without it - the app simply cannot start because basic functionality is missing.

    Our devteam maintains a few complete vertical qa/testing stacks. Developers/QA/Product people load their change into these stacks and share with others. They are then used for product UI validation, sanity/automated testing etc.

    Because the app depends on change streams, those stacks are restricted to use only production Atlas clusters.

    The bandwidth and performance required from those stacks is miniscule. Using the production clusters is not cost effective (and waste of hw resources!).

    My understanding is that the Serverless deployments were created exactly for this reason. However for us they are completely useless unless to us they support change streams.

    Please update re the feature's expected timeline.

    Hi. I need the "change streams" feature implemented for serverless deployments.

    At this time it's unclear when will it be implemented, hence it's difficult to plan ahead.

    Why is that important?
    My nodejs app relies on change streams. Without it - the app simply cannot start because basic functionality is missing.

    Our devteam maintains a few complete vertical qa/testing stacks. Developers/QA/Product people load their change into these stacks and share with others. They are then used for product UI validation, sanity/automated testing etc.

    Because the app depends on change streams, those stacks are restricted to use only production Atlas clusters.

    … 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

    1 comment  ·  Serverless Instances  ·  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