Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
449 results found
-
Page title says "Create Cluster" when editing cluster config
Small thing I just noticed (confused me for a second because I had a second tab open to actually create a new cluster). My idea is to have the the title say "Edit Cluster" instead.
1 vote -
Allow transactionLifetimeLimitSeconds to be modified from Atlas
We need to be increasing the default value of transactionLifetimeLimitSeconds to larger numbers (usually 300 instead of default 60). Considering number of clusters we running / we are going to be spinning up in the future its cumbersome to keep requesting this change from support. Instead please allow us to set or modify this from the Atlas GUI.
1 vote -
Improve database access tab
Managing permissions for users is a pain right now. It's a lot of clicks, it quickly becomes messy and sometimes the modal closes without saving changes.
It would be a lot easier if we could import a CSV containing all permissions for a certain user (user name, permission type, database name, collection name)
4 votes -
allow for renaming and moving of collections and databases on server
Right now it is difficult to rename and move databases and collections without downloading and re-uploading them.
Please enable this critical functionality as it's very common to need this when administering data.
2 votes -
billing
The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.
11 votes -
Recently resumed clusters must remain running for 60 minutes
At the moment when you try to pause a recently resumed cluster you get the following message;"Recently resumed clusters must remain running for 60 minutes to process all queued maintenance".
Obviously this requires me to check back in Atlas UI in an hour or so just to pause the cluster. Instead would be good for UI to schedule a Pause to be executed as soon as it's possible.
9 votes -
Log browser and log search capability across replicaset nodes.
Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.
9 votes -
Being able to change the cluster name
a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..
11 votes -
Setup activity feed retention
It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.
1 vote -
Define via UI time windows on which the cluster is paused
Test environment are usually paused during the night and the weekends. Currently the only way to do that is to automatise a RestAPI call or call mongocli automatically (e.g. via crontab)
Would be nice to allow to define a time windows on which the cluster stays pause via UI9 votes -
Include security group and tag for privateLink setup
On the Private Endpoint (and VPC Peering) setup screen in Atlas, present options to:
- include or modify "security group"
- attach a "tag = name"
That way when user has the AWS CLI command generated, it includes security & tag
1 vote -
Billing Estimator
The ability to estimate monthly price not just at the cluster, but also by editable storage, data transfer, cloud backup with sliders to change the values.
Estimated forecast based upon last 3 months of usage/growth would be great too.
1 vote -
Cluster version overview on Owner level
We have partially older mongoDB versions running on our clusters. We get notified about it by EOL mails from mongoDB. However, as an org owner, I cannot see which clusters are affected. This makes it extremely time consuming for me to identify the relevant contacts per cluster. Our org structure entails self-sufficient teams with independent accountability of the mongoDB clusters. There is no central contact person.
It would be desirable to be able to call an overview of all clusters with the respective installed version in the GUI with owner rights.
1 vote -
Dynamically switch primary between multi-region clusters based on client request locality
Consider an application that uses a multi-region implementation in an active/passive configuration - we'll call the regions "A" and "B" and assume they're located on opposite ends of the continental US. This application also leverages a multi-region Atlas cluster with single nodes in region A and B. Both the application and Primary node of the Atlas cluster are operating out of region A.
If something were to cause the application to fail-over from region A to B but that trigger did not include a complete regional outage, the Atlas cluster's primary would still be operating in region A. This is…1 vote -
Single node clusters
Allow users to create a single node clusters for dev purposes.
3 votes -
Allow triggers to be tested locally
Our team uses and loves Stitch/Realm triggers. We've got them wired up so that we can update them from a bash script. They work well, but they are hard to debug -- it'd be nice if there was a CLI option to test them against a local mongodb instance.
3 votes -
Expose Atlas Replica Set Tags in UI
Atlas replica set members are pre-configured with tag sets: https://docs.atlas.mongodb.com/reference/replica-set-tags/
There's no way to see what the tags are set to via the UI. It would be helpful to see this information.
9 votes -
Ability to add multiple IP's to the whitelist and download the current whitelisted IP's
If I want to add comma separated IP's it is not possible. We have to add each IP painfully from the UI. Please allow to add comma or semicolon separated IP's to be added at once.
Also, why can't I download the current whitelisted IP's as a CSV or other file?
4 votes -
Allow customers to download Atlas BI Connector process logs (similar to MongoDB Server logs)
What is the problem that needs to be solved? Customers are willing to troubleshoot / analyze Atlas BI Connector logs by themselves (they would like to investigate schema sampling timings, SQL/MongoDB query optimizations, connectivity issues, etc.).
Why is it a problem? (the pain) Currently available Download Logs option on Atlas Clusters does not include Atlas BI Connector process logs.
5 votes -
Using replica set tags for invoice categorization
Customer would like replica set tags added to the invoice as a column, in order to further categorize costs. In some instances, the customer has multiple products assigned to a single cluster, and putting the product name in the cluster won't suffice.
The current solution is to use the Invoice API, and then call the Cluster API, in order to programmatically build out a CSV containing the cluster tags as an additional column in the CSV.7 votesWe recently released tags on database deployments. You can apply tags to new or existing clusters or serverless instances.
https://www.mongodb.com/docs/atlas/tags/
We are planning to have these tags displayed in billing Invoices and we'd love to hear more from you. Reach out to me if you'd like to provide additional feedback about this feature request.
- Don't see your idea?