73 results found

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

2. Misleading error message when connecting to MongoDB Atlas with wrong password

   When you connect to MongoDB Atlas from your application with wrong password using Mongoose, you get error message:

   "Could not connect to any servers in your MongoDB Atlas cluster. Make sure your current IP address is on your Atlas cluster's IP whitelist: https://docs.atlas.mongodb.com/security-whitelist "

   even though your IP address is whitelisted.

   Very frustrating and misleading error message, please fix this!!

   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

   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

3. Helpful error message when restoring backup

   When I recently attempted to restore a db backup I got a cryptic error message stating "Error: Cluster Not Found"--which was extremely confusing considering that I pressed the restore button in the backup options. After some great tech support, I added my user as project owner and everything worked fine.

   Please make the error message clearer in both the Restore and Download backup scenarios.

   •  

   •  

   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

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

4. Precautionary Change/Recommendations for Shard Drops

   If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).

   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

5. Implement SCRAM-SHA-256 mechanism for Atlas or make a SCRAM-SHA-1 as default

   The main problem is inconsistency in the default authentication mechanism of clients and Atlas.

   This causes a failover from SCRAM-SHA-256 to SCRAM-SHA-1 by clients on authentication failure.

   This causes a huge number of errors in "Database Access History" which becomes useless.

   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

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

7. Editing custom Role and Action toggle issue

   When adding or editing a custom role in Atlas - When I expand/collapse the Actions or Roles in dropdown, it also toggles the checkboxes. So, when I want to see the roles and actions available, it also checks/unchecks the checkbox, which makes editing the actions in roles difficult.

   Please click on highlighted areas in Atlas, as shown in screenshot attached

   Thanks.

   •  

   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

8. 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 any way from a user perspective.
   The error message is also not very informative that the problem is the Data Explorer. In fact it mentions only that the user does not have permissions to kill the operation.

   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… more

   9 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  ·  Data Explorer  ·  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. improve error messaging

   We are running into misleading error messages that learners are complaining about. This error appears when a user tries to use a $limit stage and forgets to add a $ while connected to a Free Tier Atlas cluster:
   "OperationFailure: limit is not allowed in this atlas tier, full error: {'ok': 0, 'errmsg': 'limit is not allowed in this atlas tier', 'code': 8000, 'codeName': 'AtlasError'}":
   This has been confusing for users. Is there a way that we can catch this issue more precisely and issue a syntax error instead?

   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

10. Update the regex used to split a database user import id to match the database name constraint

    Hello,

    While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.

    The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.

    I've got the following error when i launch my terraform import:
    Error: error splitting database User info from ID
    │ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}

    Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
    => https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349

    Is it possible to update the regex to allow others characters like my underscore in this case, and maybe match only the constraints that are set on database's name creation ?

    Thanks

    Best regards

    Hello,

    While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.

    The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.

    I've got the following error when i launch my terraform import:
    Error: error splitting database User info from ID
    │ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}

    Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
    => https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349

    Is it possible to update the regex to allow others… more

    6 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  ·  Terraform Provider  ·  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. zoom resolution icons

    At certain browser (Chrome) zoom settings, the checkboxes disappear. Boxes that are unchecked remain, but some (not all) of the checked boxes are just not shown.
    Unfortunately I have to use these zoom levels (67%) to be able to see sufficient information on my dashboards. Can the icons (checked boxes) be made to appear properly (not blank) at all zoom levels?

    •  

    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  ·  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. Atlas Capacity Check for Cluster Creation or Changes

    When creating large new clusters sometimes Atlas does not have enough resources available from the cloud provider. When this happens a restore or cluster change fails without reporting what the actual issue is.

    Solution: Verify available capacity and issue a warning or error if it is possible that the operation will fail & recommend opening a support ticket (or have a dialog to automatically do so listing the details)

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

13. Copy/move snapshots from a source to a target cluster

    It is recommended that restoring a cluster must either:
    1) Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or,
    2) Ensure that the target Atlas cluster cannot receive client requests while you restore data.
    (src https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore/#prerequisites)

    While doing a PIT restore with the source and target cluster being the same, our clusters have gone into a "down" state 3 times due to obscure errors, opslog not being large enough, or writes happening to the cluster during restore.

    We would like to take the safer route of always restoring to a new cluster.

    However, in doing so we lose the Atlas snapshots and possibly opslog data.

    Feature ask: Ability to copy or move snapshots from a source cluster to a target cluster. This operation would take place after the primary restore completes, if needed.

    A similar feature was asked here, but not exactly the same thing: https://feedback.mongodb.com/forums/924145-atlas/suggestions/44074839-restore-snapshots-on-s3-back-to-atlas-cluster

    It is recommended that restoring a cluster must either:
    1) Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or,
    2) Ensure that the target Atlas cluster cannot receive client requests while you restore data.
    (src https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore/#prerequisites)

    While doing a PIT restore with the source and target cluster being the same, our clusters have gone into a "down" state 3 times due to obscure errors, opslog not being large enough, or writes happening to the cluster during restore.

    We would like to take the safer route… more

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

14. Display the Atlas-generated replica-set name in the cluster Dashboard

    This is an easy one, and it'll help a lot.

    Inconvenience:

    In the past, every time I created a cluster, the name of the replica-set was in line with the name of the cluster:
    e.g.:
    Cluster Name: asteroids-tracking
    Replicaset Name: asteroids-tracking-shard-0

    Now when I create a cluster, the name of the replica-set is a random set of characters prefixed by "atlas-"
    e.g.:
    Cluster Name: asteroids-tracking
    Replicaset Name: atlas-[randomChars]-shard-0

    This makes it unnecessarily difficult to find (in the Atlas Organization) the cluster referred to when I receive text message alerts. Mainly when you are in charge of so many clusters.
    Additionally, the name of the replica-set for each cluster is not shown anywhere in the clusters dashboard, and the only way to see it is by going to the Connect option for each specific cluster.

    Proposal:

    Since:
    - every cluster we create in Atlas is a replica-set
    - each cluster is displaying the given Cluster Name in the clusters dashboard.

    Could you please also add the Replicaset name (assigned by Atlas) next to the cluster name?

    or

    Include the Cluster Name in the alert messages and not only the Replicaset Name?

    I will highly appreciate any solution.

    Thanks

    This is an easy one, and it'll help a lot.

    Inconvenience:

    In the past, every time I created a cluster, the name of the replica-set was in line with the name of the cluster:
    e.g.:
    Cluster Name: asteroids-tracking
    Replicaset Name: asteroids-tracking-shard-0

    Now when I create a cluster, the name of the replica-set is a random set of characters prefixed by "atlas-"
    e.g.:
    Cluster Name: asteroids-tracking
    Replicaset Name: atlas-[randomChars]-shard-0

    This makes it unnecessarily difficult to find (in the Atlas Organization) the cluster referred to when I receive text message alerts. Mainly when you are in charge of so many clusters.
    Additionally,… more

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

15. Allow NewRelic integration to use EU APIs instead of default US APIs for clusters in EU region

    The NewRelic integration in MongoDB is using the default NewRelic API that is in non-EU region. There is a separate API endpoint for EU region, that is described at https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center#.

    This is causing 'newRelicLicenseKey' failed to authenticate error for the MongoDB Atlas cluster setup in EU region.

    •  

    6 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

16. ) User A login inot Mongo Portal 2) He selects an organization and sends an invitation to User B 3) Now in the Activity Feed menu we can see

    1)User A login inot Mongo Portal
    2) He selects an organization and sends an invitation to User B
    3) Now in the Activity Feed menu we can see User B was invited to the organization
    4)Before the user B accepts the invitation , User A goes and deletes the pending invitation
    5)Nothing is shown in activity feed.

    This would help products which are integrating with MongoDB atlas to get the true status of pending invitations.

    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

17. Ability to customize the name of the invite sender in emails when inviting users via API

    When inviting new Atlas Users to organizations via the API, the invite email says that the invite was sent by the API public key that performed the API call. This makes the invitation emails read like this:

    "You have been invited by tfqzvwrs to join the Example - Atlas organization on MongoDB Atlas."

    The ability to customize this (e.g. using an additional field in the request body) would be ideal since the random string being shown as the sender of the invite could make the email look suspect.

    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

18. Stitch CLI error messages - account/publicApi redirect fails

    Stitch CLI error messages are obsolete.

    I'm having difficult with connecting to a Stitch app and the 403 forbidden returns a message to check https://cloud.mongodb.com/v2#/account/publicApi but it redirects to /overview.

    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. Support migration of existing projects, clusters, ... to be CloudFormation managed

    When MongoDB::Atlas::* resources are created and the specifed project, cluster, ... already exists, then these resources should not raise an error on resource creation but use the existing project, cluster, ... and apply the given configuration. In other words, the Create event that is initially sent by CloudFormation should be handled similar to an Update event but return the physical id of already existing resources. Apparently, this behaviour should be enabled by an opt-in flag.

    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

    1 comment  ·  CloudFormation Resources  ·  Delete…  ·  Admin →
    completed  ·  AdminMelissa (Lead Product Manager, MongoDB) responded

    Hello, Import w/ MongoDB CloudFormation Resources is now supported (github)

20. Monitoring Metrics on dhandle

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

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

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