Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
475 results found
-
Upgrades from shared to dedicated clusters should only make the cluster available after data has been restored
We have recently upgraded from a shared tier to a dedicated cluster. As document, this process involved a downtime. However, what was not document is that the cluster becomes reachable for clients again before the data has been fully restored. That way, clients can invoke operations on the cluster, that may even interfere with the mongorestore process. I would propose to make the cluster available again to public clients only after all data has been restored to avoid the chance for such race conditions.
1 vote -
View dashboards as if another user
As a Project Owner, when I start rolling out dashboards to new users, I would find it very useful to see the dashboards as they can see them with their current permissions. I would like to be able to "View As" a particular user, so I can see that I have granted them the correct set of dashboards and test their permissions work for them. Obviously a feature for Owners only.
2 votes -
Referral links & referral benefits
MongoDB Atlas should give each user a referral link, and a benefit of this could be that a free account could get increased storage space depending on how many/if the referred person starts paying for Atlas services.
2 votes -
Edge Computing Support for MongoDB Clusters
We extensively use Atlas for tools, utilities as well as production apps. We would like to have the option to create an Edge MongoDB Server on-premises pointed to specific clusters in MongoDB.
This would allow everyone working from a specific location to hit the edge server instead of sending all calls over the internet to Atlas.
The edge server should automatically keep itself in sync with Atlas.
It should be low maintenance and auto updating - set it and forget it.
TFS Proxy Server is a similar idea which Microsoft had for teams working from offshore/ remote locations to improve…
1 vote -
Scheduler for Aggregations that runs for more than 90 seconds
A online Atlas service, where you can upload/write your aggregation and then schedule the aggregation to run. It should allow for aggregations that might run for a few hours.
2 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 -
Allow suggest password feature
In both mobile and desktop version of Chrome and Safari, there is a feature for automatically generating a strong password.
In the registration form for MongoDB Atlas, the password field in the registration form cannot take values entered this way. Please add this feature since password managers are in fact quite normal in this era.
1 vote -
Allow 'Download Logs' for user that is not a Project Owner but Project Data Access Read Only or Project ReadOnly
Currently in order to allow a user to download logs, it is necessary to make that user Project Owner. In a situation when a user outside the company is invited to review the project, it is not possible to grant such high level role when the access needed is only to look at logs. Project ReadOnly or Project Data Access ReadOnly should be sufficient to access logs, if the user is also granted atlasAdmin@admin access to Database
3 votes -
Thank you
As a diabetic who relies on Nightscout but is not very experienced regarding building apps and utilising databases, etc., I just wanted to say thank you very much for the clear step-by-step mlab migration instructions and video that you provided. I was able to follow these and it all seems to have worked! Thank you.
1 vote -
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 -
Increase maximum storage size for M60 servers
Currently the maximum storage size allowed for an M60 tier is 4TB. Our cluster is approaching this size, and we're facing having to shard our data, which we would really prefer not to do.
I understand that the maximum sizes are selected for performance reasons, but not every cluster is the same - ours is doing just fine and not struggling at all at this data size, and we would like to be able to continue to grow over time.
4 votes -
Replace editor with MLab's editor
Get rid of the dropdowns and give me a text box. Or at least an option to toggle off type safety.
I see the strength of Mongo as being untyped, but this editor is forcing in type. In addition, it is incredibly clunky to use when adding new fields by hand.
1 vote -
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 -
Alias for Cluster name
Add an alias to cluster name, as we are not allowed to change the cluster name. If we have an option to add an alias to cluster name. We can use it, in-case the user created the cluster with the wrong name. And in-screen u can show as clustername(alias). For better understanding.
1 vote -
Force restart of unhealthy node
Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.
If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)
109 votes -
Trigger event when user confirmation state change
I suggest that after user registered they should ve able to log in regardless of his account confirmation state, but if he is in a pending state, he could not do any read/write operation unless his own user data and his own user extra data,
And the user can also detect if his confirmation state is change
1 vote -
It would be great to have a tool with historical data about database and collection.
It would be great to have a function where we can , using only atlas interface to filter a month and a year , and we cann see historical data about sizes.
3 votes -
invoice should show support costs under project and not organization
We need the support costs (in our case Atlas Pro) to show up for each cluster under the project on the invoice. Right now, it shows up as a separate line item in a lump sum under the organization. It makes it difficult or impossible to properly bill the individual cost centers for support costs for their clusters.
If those costs showed up next to the clusters within the project, it would be easy to say project1 goes to cost center 1, but now we have to do project 1 goes to cost center 1 plus some percentage of the…
4 votes -
Implement a refresh button for the BI Connector in Atlas
When changes, such as when collections are added or removed, occur to an existing database with BI Connector enabled, the BI Connector needs to be cycled off and then on. This process is not well explained for Atlas. I feel that a refresh button that ripples Bi Connector in Atlas when changes occur would be beneficial, rather than having to dive in to edit configurations --> slide the "enable bi connector" from off, wait, than back to on.
2 votes -
Have the ability to downgrade
Currently Atlas doesn't support the ability to downgrade major version. I know with Ops Manager on-prem you can do that, which is helpful if you find issues during an upgrade. Would it be possible to get the ability to downgrade one major version on the roadmap?
As of today, if we have issues with an upgrade, we have to build a new cluster with the older version, export and import into the new cluster. That's a much more painful process including the fact that you have to change the connection strings of your applications to point to the new cluster…
11 votes
- Don't see your idea?