Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
470 results found
-
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 -
Memory managed on the mongodb atlas nodes
we recently had a major outage due to OOM on the mongodb shard nodes . we would suggest help preventing this by providing below features so this can be managed properly going forward
- Set the memory allocated to the WireTiger Cache
- Configure more memory for a tier. The current tier is M50 (8 vCPUs, 32GB memory). We would like to be able to allocate more memory for M50 to handle more connections and memory use for workloads. Scaling up to M60 will double the vCPUs to 16 which we do not want. Perhaps offer tier with high memory usage for…
1 vote -
og the size of oplog-mongomirror.bson.sz at time of deletion in mongomirror logs
currently when we run the mongomirror with --oplog, it does the status when it is deleted.
It will be good , to add the size information ofoplog-mongomirror.bson.sz
, that will help us to decide the appropriate disk .1 vote -
secrets versioning for database users
We would like to have secrets versioning on atlas end so that secrets rotation is easier - as it is a periodic procedure in most companies, would be great to refer to a new secret version of an existing user instead of recreating the user.
also considering this is sadly not gonna be handled https://feedback.mongodb.com/forums/924145-atlas/suggestions/44283477-vault-should-return-users-only-once-they-can-be-us would be cool to make rotation easier.1 vote -
There is a grammatic error in button text.
The button says "Do not me show again"; it should say "Do not show me again".
Thank you,
Alpesh1 vote -
Change shortcut for GOTO
The current shortcut (CTRL + SPACE + TAB) for the GOTO functionality is incredibly annoying as it results in a tab switch in Chrome, and it's also quite slow to reach for a shortcut.
A suggestion would be to use CTRL + K which usually in Chrome is "Search on Google", but it's also used by GitHub for their version of "GOTO", so pressumably a whole lot of people are already used to it.
1 vote -
mongoexport - generate multiple compress files as output
This is a feature request for https://github.com/mongodb/mongo-tools/blob/master/mongoexport/main/mongoexport.go
- similar to s3.format.maxFileSize parameter in ADL $out, cut a new file every xxxMB
- similar to s3.format.columnCompression parameter in ADL $out, use gzip/zstd to compress the output BSON or JSON
- support write to locally-mounted file system (EBS/NFS) and cloud object store S3/GCS
The similar logic has probably implemented in the ADL $out codebase already, we just need to port them over to mongoexport
1 vote -
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 -
Atlas Administration API: Expose more information on cluster status
We are using the Atlas Administration API in order to automate scaling a production database cluster deployment in a more fine-grained way than the existing autoscaling offer. The specific database cluster is deployed as a replica set, so there is a number of electable nodes (one primary + 2, 4 or 6 secondaries) and any number of read-only (RO) nodes.
The goal is to be able to tune the number of nodes in a specific region, and being able to monitor the progress of the change being rolled out. Currently, the API offerings are too limited to do this effectively,…
1 vote -
Don't overwrite explicitl role with default organisation role configured in identity provider
we have user created in Atlas on Organisation level with specific org role. If we configure Identity Provider and set some default role, then after first login this user will receive this default role and original role will be lost. So, even after disabling identity provider, user will have this default role.
Suggestion: explicitly granted roles should be keep untouched, but not be applied in case of active identity provider.
1 vote -
Copying gbs of collection data from one project to another project
Currently it is highly time consuming process of copying a 100gb collection from one project to another project. There is no faster and proper way of copying the data. This feature is highly needed. Because each environment resides in different projects. If someone want to copy only handfull of collections from one project to another(dev to prod and vice versa) then its a nightmare for doing this kind of job. Tried mongomirror and mongodump feature but those are not quite impressive.
1 vote -
m10 for gcp santiago zone
I would love if i can select m10 than m30 on santiago region.
1 vote -
Automatically detect location for Global Clusters
Currently Global Clusters require a location field for zone targeting. Could the user get an option to be auto-detected based on the incoming connection? The reason for this is, not all app services have the ability to include location, so would be good to auto-detect it.
1 vote -
Multiple connection URLs for Atlas clusters
Allow generation of multiple application-specific connection strings/URIs to the same Atlas cluster. This would ease migration of databases to different clusters over time; consolidating smaller databases to lower costs, or separating busier databases to isolate performance impact.
Multiple connection strings will allow us to redirect connections seamlessly when migrating databases without requiring developers to re-deploy changes to application connection strings, minimizing downtime and coordination.
1 vote -
Need "Inactive" sessions "Terminated" connected via Atlas
We need a feature that would automatically timeout individual user "inactive" sessions after x number of minutes, connected via Atlas. Thanks
1 vote -
TDE Encryption Key automatically rotation
when we got the alert like "Azure encryption key needs rotation", we need connected to our it team and they rotated the key in azure key vault then they shared us the value of new Key Identifier, then we logged into atlas and under security-->Advanced under that we updated the Key Identifier under Encryption at Rest using your Key Management option, all these steps we were done manually.
Is it possible to rotate/update the key automatically, when the key is rotated in azure key vault, without doing it manually.
1 vote -
Add filters for easily finding projects that have encryption/audit enabled in the UI
The https://cloud.mongodb.com/v2#/clusters has certain filters to get specific Atlas clusters. Can we add couple of more filters that can easily identify, whether that project has been enabled for encryption at rest or if the auditing has been enabled/disabled. This will help us easily generate reports for cis20 reporting.
1 vote -
Allow --removeAutoIndexId option to Atlas live migration as default
Apparently Atlas live migration does not support --removeAutoIndexId option due to which some collections having
autoIndexId set to false
does not allow live migration to work successfully. Please add --removeAutoIndexId option to live migration.1 vote -
API for Granting Infrastructure Access to MongoDB Support for 24 Hours
As per documentation at https://www.mongodb.com/docs/atlas/security-restrict-support-access/#grant-infrastructure-access-to-mongodb-support-for-24-hours one can grant access for support for 24h only via the UI. It would be very useful to be able to do this via the Atlas API.
1 vote
- Don't see your idea?