Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1366 results found
-
Permission level to query snapshots
Right now I have to give an admin permission to allow someone on my team to query snapshots from a backup (i.e. downloading the tunnel file).
I don't want to give an admin permission just to allow our data analysts or a developer trying to understand data corruptions to view the database at an older date.3 votes -
Display chart annotations more conspicuously
To access chart annotations, users have to first hover over the metrics display, click on the info icon next to the title of a specific metric, and then read the annotations under the explanation of that metric. I didn't know they even existed until a support person happened to mention the vertical lines and I asked what they were. It would be more user-friendly to have the annotations (really, a legend for vertical lines) displayed separately in a more conspicuous location. Maybe in an info icon next to the annotation toggle? Another option would be for the vertical lines to…
1 vote -
Add SHA-256 as Digest Authentication Algorithm for API
For compliance with NIST and other standards, it would be preferred to use SHA-256 as the algorithm for digest authentication for the public API as opposed to the currently implemented MD5.
3 votes -
Provide a granular mechanism to disconnect and disable all active sessions during a planned maintenance.
Provide a per cluster mechanism to shut off client access for restore operations.
3 votes -
Allow adjustable sensitivity
Currently I see many queries in Profiler that the Performance Advisor is not recommending to fix.
1 vote -
Allow suggest password feature
In both mobile and desktop version of Chrome and Safari, there is a feature for automatically generating a strong password.
In the registration form for MongoDB Atlas, the password field in the registration form cannot take values entered this way. Please add this feature since password managers are in fact quite normal in this era.
2 votes -
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 -
Project migration should not require org-owner rights
Before project migration from one org into another, we have been told to define the responsible users in both orgs with org-owner rights. There should be no need at all to permit org-owner rights on project migration. The org-owner-level should only be reserved to the very smallest group of people (admins) necessary. Project owner level should be enough for a migration of projects.
1 vote -
Have live tool migration re-establish connectivity with on-prem cluster in case of connection failures
While trying out Live Migration tool for data transfer from our on-prem cluster to Atlas, we had an issue where Atlas ran into connectivity issues with the on-prem cluster with respect to Live Migration tool. As the tool couldn't re-establish connectivity with on-prem cluster, we had to cancel migration and initiate data sync all over again. While this is fine for a small cluster, this can't be feasible for a large PROD cluster where we have 20+ shards and with data volume in order of 40-50TB compressed size.
So, even if there is a network disconnect or any maintenance happening…
2 votes -
Allow to resend alert to a PagerDuty service
Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.
The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.
Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.
2 votes -
Description field for VPC peering page
Add a description field to easily identity the peering items in Peerings tab. Example: "Peering for Stage Kubernetes cluster apps"
6 votes -
Add support for arbiters
We have a situation where we are required to build in an AWS region that only has two AZs (ca-central-1). In addition, there are no other AWS regions in the country (Canada). And due to our requirement around data sovereignty, we can't host this data set within a different country.
Because of this, we can't guarantee our cluster will stay up if we lose a single AZ unless we put an arbiter in a 2nd region (since no data is copied to the arbiter). However, Atlas does not support arbiters currently. I know arbiters aren't ideal, but in this edge…
7 votes -
1 vote
-
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 -
Live Migration Should Include Database User, Password and Role Information
Please provide the option to include database username, password and role information during a Live Migration. DBAs often do not have direct access to database credentials and have to collect them from the various development teams.
3 votes -
Enable live migration tool to work with Global cluster configuration enabled
Currently, there is no Live migration tool option while enabling Global Cluster Configuration in Atlas. Please treat this ticket as a FEATURE ENHANCEMENT REQUEST to make this happen.
3 votes -
Azure Stack Support
Many of us have a requirement to host our databases in countries without an AWS, GCP or Azure data center.
Azure Stack is a hybrid cloud solution that allows vendors to use Azure in their local data centers using the same APIs. MongoDB atlas support for this would be immensely valuable.
2 votes -
Limit certain users to create only specific cluster sizes
After discovering over-spending forced to remove Atlas permissions for all developers. Would be nice if I could limit them to create only M0 / M2 / M5 clusters as sandbox.
6 votes -
Allow "Project Data Access Read Only" to retrieve restore links.
Allow "Project Data Access Read Only" to retrieve restore links. Currently, to retrieve a restore link from an Atlas cluster you must be a Project Owner.
In the current version to take the link to the snapshot we need to use Restore Jobs part of the API. Problem is that the same POST endpoint is used for the restore job which can do changes in the system and needs Owner level of the access and to generate link to the stream with the snapshot data. This second type of the job should not need so big access level as should…
5 votes -
Alias for Cluster name
Add an alias to cluster name, as we are not allowed to change the cluster name. If we have an option to add an alias to cluster name. We can use it, in-case the user created the cluster with the wrong name. And in-screen u can show as clustername(alias). For better understanding.
1 vote
- Don't see your idea?