Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
457 results found
-
1 vote
-
1 vote
-
docsexamined
in profile tab, there are only keysexamined, nreturned we can see.
If we have "docsexamined" , it would be good to check whether the queries are well tuned or not at first glance.1 vote -
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.
11 votes -
Permit setting a default collation at the project level, to apply to all collections etc within the databases it contains.
Currently the highest level that collation can be set is at collection creation, and it is inherited then for any indexes created on that collection and by commands like find() that run against it.
But it would be nice to be able to specify a default collation at the database level, or even the Atlas Project level, to apply to all collections in all databases therein, howsoever created.
2 votes -
Ability to provide IP addresses as a list for Network Access
When adding IP addresses on a cluster/project (Network Access), it would be great to be able to provide a comma-delimited list of IP addresses instead of having to enter them one-by-one.
7 votes -
Support for delayed replicas
It would be great if Atlas provided support for hidden, priority 0 delayed replicas. For workloads that do not need real time data or situations where data recovery is needed, a delayed replica would be the fastest way to mitigate both of those scenarios.
7 votes -
mongomirror with db rename
We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?
14 votes -
Ability to stream logs to Cloudwatch Logs or Datadog
There's no way to stream logs from MongoDB on Atlas right now. I should be able to stream logs, either to Datadog or Cloudwatch or something!
189 votes -
Delete one (last)endpoint deletes private endpoint service
If no further endpoint is associated with Private endpoint service, making a call to api resource https://docs.atlas.mongodb.com/reference/api/private-endpoints-endpoint-delete-one/ will delete the endpoint as well as service.
1 vote -
I'd like the ability to be on premise and burst into Atlas when needed.
As an system administrator running MongoDB EA, I'd like the ability to be on premise and burst into Atlas when needed.
1 vote -
Allow custom DNS hostnames to be added to cluster config / TLS certs
Since Atlas clusters now support different sets of hostnames, it would be good to explore the feasibility of allowing users to add their own hostnames to the cluster configuration and TLS certificates such that custom connection strings can be used.
One use case for this is being able to "wrap" Atlas connection strings, such that an application's connection string would never need to change despite underlying cluster changes (cluster being moved between projects, etc.)
This could also be useful if you wished to whitelabel your cluster.
42 votes -
Support Private Endpoint TO customer's VPC/VNet
This would allow a Private Endpoint to connect FROM an Atlas Project TO a customer's VPC/Vnet (using AWS PrivateLink or Azure Private Link), for accessing private services like a private webhook for alerting, LDAP, and/or KMS
6 votes -
Add date added and date updated to Network Access IP table
The network access table should have a way to see the date an IP was added and if/when is was last updated. This will give better insight and control over company users add and maintain their IPs when only whitelisted access is allowed.
1 vote -
To modify transactionLifetimeLimitSeconds parameter
As this is one of the most common request from Atlas customers to modify
transactionLifetimeLimitSecondsit would be beneficial to grant the privilege so the Atlas customers are able change this parameter within a certain limit. Please add this functionality.2 votes -
Allow domain or URL for whitelisting
Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.
3 votes -
Unpause Cluster for X Duration
Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.
Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours
Current Atlas Control Plane: "Pause Cluster"
Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"
This is similar to how customers can create temporary database users that are only active for X number of hours.…
1 vote -
rolling maintenance for replicasets
Similar to the process outlined in this doc for index builds
https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/
It would be beneficial if the same process can be allowed in Atlas for running database maintenance processes such as dropping large databases that are no longer needed or to purge out old data using this method without impacting the primary.
Bulk Data can be purge out easier using the rolling maintenance method for example when implementing TTL index. If prior to implementing TTL index there is a lot of data to purge out that meets the TTL index criteria, this can be done prior to creating the…
1 vote -
Provide local ssd instances in GCP
In terms of throughput it would be great to be able to configure an Atlas cluster based on local ssd / nvme GCP VM instances.
3 votes -
Support optional fallback to source cluster after cutover in Live Migration
Live Migrate allows for migrations from non-Atlas clusters into Atlas by syncing data from the source to the Atlas destination, and then cutting over the application to direct workload to the destination.
It's possible to test the application on the destination before cutover, but after cutover, there's no way to sync data in reverse in case unforeseen issues arise and it's necessary to fall back to the source (or another) cluster again.
Having a "fallback sync" option could help with this.
7 votes
- Don't see your idea?