Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Provide option to remove hidden node in NVMe clusters
NVMe clusters default to add a hidden node where backups are pulled from. This is due to the reduced durability of NVMe volumes. In cases where durability isn't a concern, I would like to disable backups and remove the hidden node altogether.
The UI currently provides the ability to stop backups by modifying the backup policies (see attachment). However, I cannot remove the hidden node which is simply incurring extra cost.
Obviously there would need to be a major warning provided to the user, but this is not unprecedented in industry. AWS has spot instances that are quite successful.
My…
4 votes -
disabling snapshots
When we disable de snapshot from one cluster, the following message is shown in the same page but it does not appear at the page that shows the changes that are being made
It would be better if this message were also at the second page (as image uploaded)
Please Note: This action is irreversible. Turning off or altering your type of backup will delete all of your existing snapshots immediately. If you want to keep old versions of your data, visit the backup dashboard and download your snapshots
4 votes -
It would be useful to be able to view a collection schema similar to how you can in Compass
It would be useful to be able to view a collection schema similar to how you can in Compass. At present we have to enable LDAP and configure Compass to remotely connect to Atlas, but this is not always feasible and it would be good to see this useful functionality from Compass translate to Atlas UI
8 votes -
Add support for allowDiskUse when using the Data API
The Data API doesn't support the allowDiskUse option, leaving no way to get around this error:
"Failed to aggregate documents: FunctionError: (QueryExceededMemoryLimitNoDiskUseAllowed) Exceeded memory limit for $group, but didn't allow external spilling; pass allowDiskUse:true to opt in"
12 votes -
Ability to update x509 certificate via the Terraform provider mongodbatlas_x509_authentication_database_user
Provide the ability to create a new certificate when it is close to expiration.
We currently create a database User using - mongodbatlasx509authenticationdatabaseuserTthere is no way to generate a new certificate and update the Secret manager/Vault with this.
Via Terraform (automated)
I am currently updating the resource name to force Terraform to do this.
1 vote -
Associate domains to an IDP at Organization level rather than for entire mongodb.com
At this time domain to IDP associations apply to entire mongodb.com. This makes it very difficult for large companies that have several independent departments to use mongodb.com. Some departments might want to create separate Atlas organizations and others simply access Support section of mongodb.com web-site. They wouldn't want to share an IDP created within one Atlas organization.
One possible approach to addressing this issue is for an Atlas organization to have a distinct sub-domain on mongodb.com (e.g. bigco-org-a.mongodb.com). Another approach would be to have a field for Atlas Organization name on logon page.
7 votes -
sort custom roles
Sort custom roles dropdown when choosing to assign to a user. Currently when creating a new user and selecting a custom role, the roles are ordered by creation date which makes it hard to find when many exist.
1 vote -
Lock a user account
We have an occasional need to disable/lock an individual database user. Either because of a run away process or inactivity. We do not want to change the password or drop the user as we may need to reenable the user quickly with the same permissions and password as before.
8 votes -
Prometheus database and collection metrics
We checked the Prometheus metrics provided by MongoDB Atlas and didn't find metrics for the following:
Database sizeCollection storage size
Record per collection
Indexes per collection
Index size
We would like to have this kind of metrics to add to dashboards.
27 votes -
Suggestion to make the Organization Role Mappings page easier to navigate to
Make Organization Role Mappings page in the Federation Management App quicker to navigate to. Currently the quickest way is to click the "Create Role Mapping" from the Overview page under "Optional: Set Up Advanced Settings" and then click Cancel.
If the "Optional: Set Up Advanced Settings" box is not longer available in the Overview page, you'll have to click the Organization tab from the side navigation bar > [Organization Name] > Create Role Mapping > Cancel in order to reach the Organization Role Mappings page.
3 votes -
Realm device-sync for serverless instance
To make realm more scalable and easy to integrate. Device-sync should also be considered on serverless instances.
1 vote -
Atlas triggers on serverless instance
Atlas triggers on serverless instance
Hello, Atlas triggers would be a really nice to have feature on serverless instances.
2 votes -
Add Terraform support for Device Sync
Device Sync (https://www.mongodb.com/docs/atlas/app-services/sync/get-started/) can't be managed via Terraform. This would be a great addition to the provider!
1 vote -
providing the service as quoted
Very angry and having suffered twice now through the lies told about only going to take 7-10minutes for an upgrade on y to be edging toward an hour now. Last time i have issues with a snapshot being deployed that never fully populated the DB when restored, disgrace, clients only get interruptions, business downtime and you want more money for better service to provide a fix to a problem that you created? its a joke, your company should be investigated by authorities.
1 vote -
Find Database on Multiple Cluster
Enable the search box on Database Deployments to search for a particular database on all clusters under the project.
This would be helpful when having different databases on many isolated clusters.
1 vote -
Add more information to "We are deploying your changes..." blue bar
Occasionally we see the deployment blue bar but aren't sure exactly what is being done. It would be very useful to have a link to click to see what changes are currently being pushed out.
6 votes -
Parent - Child account set up
I have a client that has multiple BUs and would like to organize them under a Parent account. From my understanding, Atlas does not currently support a Parent-child account set up. This would be beneficial to have as we continue to onboard our enterprise clients and we get more use cases.
1 vote -
Notifications
In case of a databreach MongoDB will notify their customer.
Customer is defined as 'the Organization Owner'. However, a databreach should end up with a privay or security officer. It would be a nice feature if some of these roles would be defined and what kind of alerts/nortification they can expect from MongoDB Atlas6 votes -
org owner permissions won't revoke due to role mapping
When choosing to use idp role mapping, if a user is not part of a group, his permissions are revoked, including locking him out of crucial administration options.
Users with the org owner permissions should be handled as super users and be excluded from any role mapping in order to refrain from having their permissions change
1 vote -
Map IDP groups to Atlas teams
At the moment Atlas does not support mapping IDP groups to existing Atlas teams. We would like that the integration would support that. For example:
okta group "devops" --- mapped to ---> Atlas team "devops"
Each time the customer adds a user to this idp group, the user will be given the proper permissions in Atlas.
13 votes
- Don't see your idea?