Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1366 results found
-
Ability to apply the same settings to multiple projects
As described in support case #00739901, we have exceeded the 50 limit of clusters in our production project.
We are going to have a lot of new clusters in the coming year, and they all need to be in the production environment.
There should be a way either to add more clusters to one project or to share the same settings between multiple production projects for growing customers of MongoDB like us.
2 votes -
API access over VPC
We have a scheduled process which starts up a GCE instance with both an internal and external IP address. This runs a script which:
- uses the Mongo API to get the id of the latest snapshot
- uses the Mongo API to create a restore job with HTTP delivery
- downloads the backup and perform some verification processes on the backup.
Currently Mongo Cloud only allows access to the Mongo API and the HTTPS download over the public Internet. This requires adding Google Cloud IP addresses to both the API key IP Access List and the Network Access IP Access List. It…
2 votes -
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 -
Alerts based on Activity Feed - Rollback
Our main concern is 'Host experienced a rollback' is not an alert option!
Ideally, anything that shows up in the activity feed should be available as an alert.
15 votes -
improve error messaging
We are running into misleading error messages that learners are complaining about. This error appears when a user tries to use a $limit stage and forgets to add a $ while connected to a Free Tier Atlas cluster:
"OperationFailure: limit is not allowed in this atlas tier, full error: {'ok': 0, 'errmsg': 'limit is not allowed in this atlas tier', 'code': 8000, 'codeName': 'AtlasError'}":
This has been confusing for users. Is there a way that we can catch this issue more precisely and issue a syntax error instead?1 vote -
Don't cut alert names
This is very hard to figure out what these alert mean, I have to go to the documentation and match them somehow, but it also looks like the documentation is not up to date.
3 votes -
Add a single-node option.
mLab had the option to create a single-node deployment, which was very nice for development environments where redundancy isn't important, but keeping costs down is.
Would be nice to see this in Atlas as well.
39 votes -
A terraform resource for managing user access to the console
We have a platform (as code using Terraform) where we integrate Mongo Atlas in AWS. We have multiple teams with various privileges who access the Mongo Atlas console daily basis. We would always like to manage the users in our version control. As Terraform is one of the best infrastructure configuration tools, we would like to have a terraform resource in order to manage the users via.
42 votesThe Atlas Admin API endpoints needed to support this have been created and it's now on our nearer term roadmap to implement MongoDB Cloud user support. Stay tuned for more.
-
Yellow exclamation icon should have a tooltip or explanation
Often in the cluster card, or in the cluster panel, one or more processes are marked with a yellow warning icon (instead of a green dot). However there is no indication about what this means or how to fix it.
Can there be a tooltip or explanation about what this icon represents?
46 votes -
NodeJS Trigger Dependencies
I'd like to have NodeJS dependencies (e.g. the AWS NodeJS SDK) available in my Atlas triggers.
1 vote -
Support ISRG certificate selection in mongodbatlas_cluster
As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.
It would be useful to add support for certificate selection.
1 vote -
1 vote
-
Provide callback method for API calls to avoid polling
Provide some callback method (webhook URL, push notification, etc) that an API call can use to indicate it's done. That way the user doesn't have to sit and poll endlessly.
Some examples of where this would help:
- After creating a restore job, waiting for the snapshot download URL to be ready.
- After modifying the automationConfig, waiting for all agents to report that they're in goal state.
3 votes -
Need static private ip for cluster nodes
Please see details in https://support.mongodb.com/case/00682480
3 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.
5 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…
12 votes -
My entire team receives the billing info every month.
Billing should be limited to organization owners only and not viewable by the entire organization.
6 votes -
Email subject more specific for Alerts
The email Alerts that MongoDB provide are very useful, especially the Oplog and CPU Usage. However, the subject of the emails are not clear and does not specify the Alert type. It is just a generic "Alert". It would be great if MongoDB can add "Alert Oplog" or "Alert CPU Usage" to the email subjects to make them much more clear and helpful. Thanks!
21 votes -
1 vote
-
1 vote
- Don't see your idea?