Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
484 results found
-
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 -
Add option to "Explain" a query from the "Profiler" page.
The profiler page shows a list of queries with metadata about them. It would be great to have the option to "explain" any query from this view, or in the slide-out view after clicking on a query.
6 votes -
Support exporting Custom routes
Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
We have peering with other product and they support it !2 votes -
Implement AWS transit gateway support
VPC peering and Private Endpoints have limitations that make them unusable in some environments. Implementing native transit gateway support would allow admins with hybrid infrastructures and strict security requirements to control routing and security at a lower level then is currently supported.
VPC peers do not support pass through routing, so organizations that use transit gateways to attach IPSEC tunnels or other external networks to AWS are unable to access atlas servers via these peer connections.
Private Endpoints do allow connectivity in these cases, but cause an additional layer of expense, complexity, and reduced security. First, the "user" side still…
10 votes -
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 -
Approval workflow for database deletion
The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.
Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.
2 votes -
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 -
Atlas shards with different clusters tiers
For solutions of hot and cold storage, there is at least 2 options:
- Online archiving
- Hot and cold cluster (using a trigger and datalake)
But these solutions have limitations (https://www.mongodb.com/docs/datalake/limitations/)There is another solution: using sharding.
We can set shards like so:
1 shard: Data from the last 2 months -> Hot data
1 shard: Data between 2 and 24 months -> Warm data
1 shard: Data more than 24 months -> Cold dataThe usage pattern: 95% of the accesses/queries go to shard with the hot data.
On Atlas, we need to set the same…3 votes -
Control IP Access list for project-only API keys at the project-level exclusively
When setting up API keys as a project owner, you only get one opportunity to manage the access list without getting an Organization Owner to modify it thereafter.
This creates a bottleneck where users need to ask for their API key access list to get changed (or alternatively make a new keypair, and have the API Keys list cluttered).
If a key is only being used in one project, it should be allowed by the project owner to update the access list at any time since there is no risk of it affecting the organization.
19 votes -
Test maintenance effects
While Atlas provides the 'test failover' feature, this only takes effect on the primary of each shard. Customers who run large sharded clusters on Atlas require testing the effects of a full maintenance patch that would restart all mongod's and mongos's, config servers, etc. This feature is a request to improve the chaos engineering features of Atlas.
At present, customers are being advised to change the TLS version of the cluster which could force restarts of all mongod's, mongos's and config servers. While this may be acceptable in non-production environments, it is unlikely in production environments.
I believe there's an…
3 votes -
Add hint support for MongoDB API functions
The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.
However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.
I think that "hint" is a great "backup" feature for cases where…
2 votes -
Expose API for Self-Service Increase of the Clusters per Project Limit
Give Atlas users the ability to increase the number of clusters they can create in a single project above the 25 cluster limit without having to file a support ticket.
6 votes -
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 -
Carbon Footprint Calculator
A widget or calculator in the Atlas UI, where the user can see the projected carbon footprint of a deployment per year while they are configuring the deployment. And / or a live counter of the carbon Footprint for each deployment/project/org.
22 votes -
Deploy Custom Role to specific clusters only.
You added the ability to deploy users to specific clusters. Great but you forgot to do it for the "custom roles". We use the "custom role" with LDAPS so we do not create a user on Atlas.
Can you extend this functionality to "custom role" also %
13 votes -
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 -
disabling mongo user
Instead of completely removing a Mongo database user, its better if there is option to disable user so that if there is any untoward incident we can enable it back. After observing for some time, we can delete/disable the user based on organization requirements. Its useful in some cases like mongo db user returned to same department after some time .
3 votes -
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
- Don't see your idea?