Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1360 results found
-
Manage Feature Compatibility Version (FCV) flag separately from version upgrade
When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.
We would like to see this be a two-step, i.e.
1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.
We understand that some users don't care about…
4 votes -
Allow to change defaultWriteConcernSource to global to avoid flipping the flag
Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.
Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.
Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.
Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.
Option location:
Cluster > configuration > Additional Settings >
More Configuration Options > Default…2 votes -
Metric Grouping
A huge improvement and help when it comes to metrics would be the ability to query by grouping (e.g. for database access users). This way if you were to use a specific database user per a specific service connection, we could see how much load to the database that specific service is causing.
Any form of implementation would be helpful, one example could be adding labels to the prometheus metrics per user, replica/shard etc.2 votes -
Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.
Enable the choices of using NVMe SSDs in MS Azure from tier M60 to M40, M50, comparable to AWS.
1 vote -
View all documents in a collection on Atlas UI
The current limitation in Atlas restricts viewing documents within collections to a maximum of 200 per view. It would be beneficial to have the functionality to scroll through all documents without encountering the message: "To view additional results, connect to your cluster using the mongo shell."
1 vote -
Support for GCP Saudi Arabia/Dammam me-central2 for Atlas
GCP announced availability of services in me-central2. Can MongoDB please support this region in GCP?
5 votes -
MongoDb Atlas Network Peering with Oracle OCI (Similar to Azure and AWS)
Please add similar Atlas network peering capabilities as that of Azure and AWS, for Oracle Cloud Infrastructure customers. We are currently using Azure, but would like to use OCI as well.
2 votes -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
6 votes -
Make IP linking easy for Atlas customers deployed on Google Cloud
I know it may not seem MongoDB's responsibility, but understanding how to get IP addresses for my Google app engine services so that I can put them in MongoDB (which for some reason wants IP addresses instead of URLs) it's difficult. If MongoDB wants to sell to Google Cloud customers they should make it easy to set up, not only for the billing.
1 vote -
Atlas raise alerts if resource consumption hits threshold notifications only when it's already scales up to the max tier
Atlas can be configured to raise alerts if resource consumption hits threshold only when the Atlas cluster already scales up to the max tier allowed. This can be help to avoid notification spams which does not require operation team actions and focus on the critical resource consumption alerts like cpu, memory, disk IO.
2 votes -
I would like to compact to oplog myself instead of opening cases to resize it
To compact my oplog and reclaim 300GB of disk space right after I finisihed migrating a database to Atlas using mongomirror, I had to open a support case. With that we were able to reduce our cluster tier thanks to lowering the disk tier (Azure deployment)
It would be nice to do it myself to be faster without opening a case with severity 4 that will take me at least 2 days to accomplish that. Also, I assume that people without a subscription can't do it since you have to open a case which is exclusive only if you have…
8 votes -
kill process for rolling index build from atlas
If index builds are rolling, then the Atlas console does not have the functionality to kill them if they take a longer time on a node. Is it possible to kill it like regular index creation from atlas UI instead raising a ticket to mongo
5 votes -
Backup persistence after termination should be standard
It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
6 votes -
Define the secret name for the connection string output from the operator
Hello all, instead of using a predictable naming convention for secrets:
$project-$cluster-$username
I'd like to be able to nominate the output secret name similar to how crossplane does this.
More details found at the Github Issue: https://github.com/mongodb/mongodb-atlas-kubernetes/issues/1369
1 vote -
Larger disk for smaller cluster tier (instance type)
We have TB-scale data in production, and we also have several databases of the same-size for development environment.
Since Atlas's smaller cluster tier such as M20, M30 doesn't support large disks, we need to pay a lot for staging environment too even though we don't need many CPUs / RAMs.
We hope Atlas to support varied storage options in smaller cluster tier
2 votes -
automatic upgrade
Forced automatic major version database upgrade.
When there is an extension the automatic database upgrade, remove the banner that says it is going to upgrade at the previous date. This is confusing and unnerving as it looks like it is going to upgrade.
1 vote -
Sortability for Network Access IP list
In the Network Access page for Mongo Atlas, on the IP Access List tab, it lists the IP addresses/blocks that are defined, along with their comments, in a table.
The rows in this table don't seem to be sorted in any way. Doesn't look like they're ordered by IP address, Comment, or creation date. And when I click on the column headers, it doesn't sort them. IMHO, that makes it hard to find specific entries, and also to skim through to get an overview of what all is in there.
It would be nice if this table were sortable by…
2 votes -
Default Maintenance Window to Out of Hours
With Atlas MongoDB, maintenance windows when not defined default in many cases to periods during peak hours. With maintenance such as automated rolling upgrades, this can impact performance. I would suggest defaulting this to a time overnight relative to the hosted region of the cluster.
In addition, there appears to be no obvious way to see what the maintenance window is without inspecting automated updates in the Activity Feed. If this is the case, adding it to the interface would be useful. Note that even toggling the manual setting of the maintenance window to on will default to the first…
1 vote -
Setup the Atlas web user's team membership as part of the invitation.
Doing so, removes the extra step of assigning the team after the user has accepted the invitation.
2 votes -
Manage federated database views via Terraform
The mongodbatlasfederateddatabase_instance resource allows managing tables in the federated instance, but it does not allow us to manage views. Please update the provider so we can also create and manage views
4 votes
- Don't see your idea?