Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
426 results found
-
Governance rules at the organization level
Hello team,
Would it be possible to be able to set up governance rules at the organization level in order to control certain configuration elements.
For example:
Control authorized providers and regions for an organization to prevent creation of cluster in unauthorized regions. (We must keep the data in Canada for some of our databases)Check the allowed IP (IP Access List) addresses
Disable the use of SCRAMS accounts for database access.
Control the "Data Explorer" functionality at the organization level to prevent its activation at the project level.
2 votes -
Redirection of ATLAS activity feed to a MongoDB cluster that we own.
Hello team,
Would it be possible to have a feature to redirect activity logs from ATLAS to a MongoDB cluster.
The idea is to be able to easily retrieve these logs with Kafka Connect and also to be able to easily query in these logs.
One could configure the redirection of activities at the organization and projects level by providing the Atlas cluster to use and the access accounts.
Example:
Main organization
- Project: "Activity Feed"
- - Cluster: "Activity Feed Cluster"
- - DB: "Atlas Activities by organization"
- - - Collection: "Activities by project"1 vote -
Atlas Shard Management
Currently the Atlas UI only presents options for how many shards a cluster can have.
Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/tutorial/manage-data-sharding/#manage-sharded-collections
3 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.
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 -
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 -
Create alarms base on events + Add control policies
Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.
The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...
For example:
- Be able to avoid the use of user scram.
- Be able to avoid using unauthorized IP addresses
- Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal3 votes -
major version downgrade request (4.0 to 3.6)
Right now I am running the MongoDB cluster on 3.6. Now I want to upgrade this cluster to 4.0. But when I want again to revert back to 3.6 I have no option to downgrade.
Use case :
Right now our production is running on 3.6, when we upgrade this to 4.0 and if we face any major issues on prod, then we have no option to get back to old version 3.6.
Without this option we cannot move our production to 4.0.
1 vote -
Provide an option to block access for certain username and source IP
We would like to provide users an access to database from our VPN to browse the data with some database tools - this access should be read only. As for now if somebody connected via VPN and uses production credentials he will be able to write to the database. To be able to configure it I think Atlas should provide a IP whitelist/blacklist during the user creation becaouse global Access Lists are not enough.
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 -
Merge All Of the MongoDB services Into 1
I have multiple feedbacks/ideas:
1) There is MongoDB Atlas, Realm, & Stitch. Why don't you merge all of it into one - MongoDB Atlas.
2) Instead of creating Organizations -> Project -> Clusters, you can just create Organizations -> Clusters without the Project.
There are a lot of platforms, which is very confusing for all of the developers to use. Instead, there can be only one platform in which, they can perform everything with simple integration of the programming languages.
You could simplify your docs as well and like I said, have only one type of integration with all of…
1 vote -
Set schedules for pausing clusters
It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.
16 votes -
LDAP support for Atlas Organization
This is a request to support LDAP for Atlas Organizations, not just Atlas Projects. The reason would be for easier access management - when someone leaves the company and their access to the Atlas Org (or in general cloud.mongodb.com / the Atlas portal) needs to be revoked, it would be easier to manage this from the LDAP console.
An alternate solution would be the ability to add IP addresses to an access list at the Atlas Org level (not just Project level.) Then when someone leaves the company, their IP address could easily be removed from the Atlas Org and…
2 votes -
Add Cluster name to process list api
Currently the processes API (https://docs.atlas.mongodb.com/reference/api/processes-get-all/) returns only the ReplicaSet name of the process not the cluster name, while the cluster API (https://docs.atlas.mongodb.com/reference/api/clusters-get-all/) returns the replicaset name only in the MongoDB URI.
If you have multiple clusters in the same Atlas project and you list the processes is difficult to make an association between MongoDB processes and the Cluster (Atlas UI name)
Would be nice to have also the cluster name in the processes api
5 votes -
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 -
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 -
Expose Collection TTL in the UI
It is very difficult to discover the TTL of a given collection. It would be great if the TTLs for each collection was visible in the collection UI.
3 votes -
Renaming DATABASE without dump/restore
Hello,
after a discussion with a MongoDB architect during a consulting day, the rename of a database was possible in previous version of MongoDB but now, it's impossible without a dump / restore process.
We don't want use a dump/restore process to rename a database because it's use a lot of time.
Could you tell me why this feature was deleted ? and will it be possible in a future MongoDb version ?
thanks.
regards,
David.3 votes -
Show index build percentage in the UI
During an index build from atlas the only status update you see is:
"We are deploying your changes (current action: configuring MongoDB)"When checking the logs of the replicaset memeber you can actually see the percentage of completion on that member of the replicaset:
2020-11-25T11:15:44.002+0000 I - [conn12] Index Build: 54798100/206784433 26%
It would be nice to have this percentage displayed through the UI.
4 votes -
Resync progress bar
Our Mongo cluster has had to resync. It would be great to get some kind of time estimate or progress bar to know how far it's got in resyncing so we can let our research team know when the cluster will be ready again.
2 votes
- Don't see your idea?