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
-
Cloud backup to new cluster
Two different ideas for this:
-When building a new cluster having the option to build it using a cloud backup snapshot for DR when a cluster is down-Same idea to restore to a new cluster but from the restore target dropdown IE Restore to New cluster which opens the create a cluster workflow with the cloudbackup snapshot section populated
7 votes -
Save common collection filter/query
As an ex-mLab customer, I used to really enjoy having common queries on collections saved, like "find a customer", "list latest X" etc Is a dropdown with a name and the query, so when you select it you can quickly perform the search.
7 votes -
Support for Azure VNet Gateway Transit
Azure VNet Peering is currently very limited as access is only possible from the VNet that is peered.
Could you please support access from onprem via private network (Express Route or S2S VPN) and Gateway Transit.
Maybe another way to achieve the same could be via "Private Endpoint".7 votes -
VPC management at the organization layer (cross-project VPC) in addition of projects layer
In order to match with GCP Host project/service projects mechanisms (network resource is managed by the host project and used by its service projects), which is usefull for companies having a large number of GCP projects to manage, in different business units, it could be very usefull to be able to not manage VPC inside projects only, but also at Organization layer: an Atlas admin could create an "organization level VPC", and peer it with a GCP host project, and several Atlas projects could 'consume' this VPC, by running clusters in it.
That would permit to avoid having to create…7 votes -
Viewing Collection Pages
Would like the option to view collection pages by 10, 20, 50, 100. Along with ability to move to (<first) (last>). Similar to mLab
7 votes -
Atlas activity feed
We want option to export Atlas activity feed in a file to export and work with it. Parse it etc ...
Even better, make a collection with it.
7 votes -
M30 Cluster Tier option with 4 CPUs
There is a gap in the Cluster Tiers for clients that have high CPU requirements but lower disk space requirements. We run on a M30 Cluster where we max out the CPU when running aggregations, we use little of the available disk and do not want to move to a M40.
7 votes -
Sharable Atlas URL query
Add a way to share queries on Atlas UI. We could have something like:
https://cloud.mongodb.com/v2/<id>#metrics/replicaSet/<id>/explorer/<db_name>/<collection>/find?query={"email": "..."}
(URL encoded, of course)
That would open the Atlas UI in the collections tab, auto-insert and auto-run the query. This would allow non-tech users to look at data easily.
(People using the link would have to be logged in and also have the necessary permissions to access those pages, as they normally would)
7 votes -
Allow Atlas to send additional metrics to New Relic via integration
This is a request to add some additional metrics to those that are currently sent from Atlas to New Relic when the integration is enabled.
The specific metrics of interest here are:
- Disk Space (%) Used (or Free)
- DB Storage
- Query TargetingHaving pointed out the above metrics specifically, I would also say: the closer that the metrics sent to New Relic via the Atlas integration can resemble those available in the Atlas cluster Metrics page, the better.
7 votes -
Expose the `indexStats` action when creating custom roles in Atlas UI.
The $indexStats aggregation pipeline allows user to get the statistics regarding the use of each index for the collection. This aggregation pipeline requires the
indexStatsdiagnostic action.However, currently Atlas UI doesn't expose this action when creating custom roles. It would be nice to have this action listed in the "Collection Actions => Diagnostic Actions" list.
7 votes -
Add replica set name to cluster info main page
It would be nice to get quick access to the name of the replica set from the cluster overview page.
7 votes -
Add support for arbiters
We have a situation where we are required to build in an AWS region that only has two AZs (ca-central-1). In addition, there are no other AWS regions in the country (Canada). And due to our requirement around data sovereignty, we can't host this data set within a different country.
Because of this, we can't guarantee our cluster will stay up if we lose a single AZ unless we put an arbiter in a 2nd region (since no data is copied to the arbiter). However, Atlas does not support arbiters currently. I know arbiters aren't ideal, but in this edge…
7 votes -
Day granularity for Atlas-managed X.509 certificate
It would be great to add more granularity when creating an Atlas-managed X.509 certificate for a MongoDB user, i mean by day at least.
Thank you7 votes -
Give an option to pause the cluster as a parameter, at the moment it is auto activating after 30 days of cluster pause which is not required
Give an option to pause the cluster as a parameter for specific duration of time, at the moment it is auto activating after 30 days of cluster pause which is not required for all the users and manually we have to keep an eye on this at the moment.
7 votes -
Return 'CreatedAt' for Programmatic API keys endpoints
We have an issue where we get emails from our internal Cybersecurity team 90 days after creating a MongoDB Atlas API key for rotation purposes.
For other SaaS providers we're able to stay ahead of those emails by querying their APIs and getting the date at which an API key will expire or the date after 90 days of when it has been created. This allows us to rotate keys before emails from Cyber.
The Mongo Atlas Administration API doesn't seem to provide that capability with the Programmatic access endpoints (though I am able to see the CreatedAt date in…
6 votes -
Improve "Host has index suggestions" alert by including the database name and collection name
The "Host has index suggestions" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
6 votes -
Update the regex used to split a database user import id to match the database name constraint
Hello,
While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.
The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.
I've got the following error when i launch my terraform import:
Error: error splitting database User info from ID
│ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
=> https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349Is it possible to update the regex to allow others…
6 votes -
Atlas dedicated tier is not actually dedicated
MongoDB Atlas, despite the documentation and Atlas UI reflecting M10+ as dedicated tier, is not actually dedicating all resources. While CPU and Memory can be considered dedicated, storage is not dedicated until M300+. After working with MongoDB Support, and support working with AWS support, our performance issues were identified by a noisy neighbor who was choking our disk IOPS even though we are running M40_NVME clusters which are supposed to be high performance.
MongoDB should at a minimum highlight this as a consideration for latency sensitive deployments.
A new Atlas alert should be created to identify issues where slow query…
6 votes -
"Manage your own encryption keys deactivated" event
We recently discovered that there is no event when deactivating the option "Manage your own encryption keys" within the cluster configuration.
While there are hints towards this within the CLUSTERUPDATESTARTED and AUTOMATIONCONFIGPUBLISHED_AUDIT events, there is no clear warning that the encryption keys of the cluster are affected.
As an unwanted change of encryption at rest keys for data can have severe impact on data accessibility and security, I would propose adding a "Manage your own encryption keys deactivated" event to the Activity Feed.
6 votes -
Altas CIDR ranges for network containers are too restrictive
Background:
For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.AWS minimum imposed CIDR value/subnet size: /28
MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24Azure minimum imposed CIDR value/subnet size: /29
MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…
6 votes
- Don't see your idea?