Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
468 results found
-
support external nodes
Allow manual addition of externally-hosted non-voting (hidden) node(s) to an Atlas cluster. This would permit:
- compliance with data management rules that require a copy of all data to be kept in-house (ie outside cloud)
- easier migration out of Atlas for real-time DB use cases where a stop/backup/restore is not a feasible route3 votes -
Validation
Show what parts of the document are failing against a defined validation schema
2 votes -
geospatial
Could we please consider boosting MongoDB's geospatial capabilities by incorporating Turf.js into Atlas. I would hope this would be an integration similar to Lucene in that it exposes some functionality through the UI, and some through aggregation. It would allow us to gain a huge amount of functionality. https://turfjs.org/
3 votes -
Add the possibility to add a description for IP's in access control list for API keys
In the Atlas UI, allow to add a description in the IP's allowed to use an API key. This may improve security and ease management as it allows to easily maintain this list up to date.
6 votes -
Warning if attempting to change cluster configuration while an index operation is in progress
When changing the cluster configuration to scale it up or down, there is no warning if there's a index build currently running on the primary/secondary. I created an index, saw it finish on the primary and then scaled the cluster, without thinking about that the index is only now built on the secondary, too.
During the downscaling the index build got aborted and attempted to build in foreground then. However this for some reason did not work and I had to contact support to help me with getting the secondary up again.
My proposal would be to either:
- Display…1 vote -
Atlas collection explorer UI: The list of collections should not scroll with the rest of the page
I work with hundreds of collections, and I have two issues with the UI that make a not optimal UX:
- my collection names are large, and the collection list is not resizable.
Alternatively to resizing, a popping up tooltip could show the full name of the collection being hovered with the pointer- the list of collection scrolls with the rest of the page. when I want to search a collection at the bottom of the page I have to scroll down to select it, and then scroll up again to see the results.
2 votes -
Allow designating some team members to administer team membership
Currently adding and removing members from team requires Organization Owner privileges. We would like to distribute management of team membership to users without having to grant them root privileges on Atlas account.
The feature would allow us to designate some team members as admins for the team, and they could then add/remove team members. This is in similar in concept to how Github implements team maintainers for a GitHub Team.
4 votes -
Improving Directions to Support on Atlas
Submitting this on behalf of customer (libra@wavecreststudios.com):
If I may provide some feedback, the Atlas site is not clear for how to get
support. Clicking Support in the upper right menu brings you to the support
portal, which you can't use if you don't have a plan. It's only when
you're viewing all your projects (and not viewing a specific project) that
there's a support link on the left side to upgrade your plan.Also, and this was very frustrating, it's not clear that "chat support" is
for general questions and not for urgent issues (usually chat means…1 vote -
Improving Directions to Support on Atlas
Submitting this on behalf of customer (libra@wavecreststudios.com):
If I may provide some feedback, the Atlas site is not clear for how to get
support. Clicking Support in the upper right menu brings you to the support
portal, which you can't use if you don't have a plan. It's only when
you're viewing all your projects (and not viewing a specific project) that
there's a support link on the left side to upgrade your plan.Also, and this was very frustrating, it's not clear that "chat support" is
for general questions and not for urgent issues (usually chat means…1 vote -
Provide local ssd instances in GCP
In terms of throughput it would be great to be able to configure an Atlas cluster based on local ssd / nvme GCP VM instances.
3 votes -
Console to see what's actually happening
My cluster operations is at 100 and i don't know what's causing that. I would appreciate having a console to see what are those operations
1 vote -
Atlas UI to manage and spin up on-prem clusters
CSM submitting on behalf of customer
Spinning up new clusters for on-prem deployments through the Atlas UI would save time and efforts for DBAs managing MongoDB deployments
2 votes -
Support Private Endpoint TO customer's VPC/VNet
This would allow a Private Endpoint to connect FROM an Atlas Project TO a customer's VPC/Vnet (using AWS PrivateLink or Azure Private Link), for accessing private services like a private webhook for alerting, LDAP, and/or KMS
6 votes -
Role to work with vpc peering with READ ONLY access for rest in the Atlas Dashboard
The requirement is:-
An individual will be able to see (READ ONLY access) the Metrics. He/She will be able to work (Add/Delete) with Network VPC Peering.
1 vote -
Support of new EBS Volume type (gp3)
When creating cluster , We have not option to select GP3/GP2. while newly introduce gp3 EBS volume have less price and high IOPS.
So why we need to settle for less.
1 vote -
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 -
NodeJS Trigger Dependencies
I'd like to have NodeJS dependencies (e.g. the AWS NodeJS SDK) available in my Atlas triggers.
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 -
MongoDB Atlas Provider for AWS CDK
We use AWS CDK to deploy our infrastructure. Currently there is only a Terraform provider available to automate the MongoDB Atlas deployment. We would like to have such a provider also for AWS CDK.
In a first step this provider should support:
- mongodbatlascluster create, edit and delete clusters
- mongodbatlasdatabaseUser create and remove usersLater full feature set like in Terraform should be supported.
Currently we use a self written provider. But this has hundreds of lines of code and means a lot of maintenance effort. For our teams this additional effort can be a reason to…
6 votes -
Determine programmatically if maintenance includes server version upgrade
Recently, Atlas introduced a feature that shows a cluster will have its MongoDB server version upgraded to the next dot version. This is displayed on the cluster card in the UI. However, this information is not surfaced in the Activity Feed or through any maintenance endpoints in the API. We would like to be able to identify when maintenance includes a MongoDB server version upgrade and do so programmatically.
3 votes
- Don't see your idea?