Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1337 results found
-
Misleading error message when connecting to MongoDB Atlas with wrong password
When you connect to MongoDB Atlas from your application with wrong password using Mongoose, you get error message:
"Could not connect to any servers in your MongoDB Atlas cluster. Make sure your current IP address is on your Atlas cluster's IP whitelist: https://docs.atlas.mongodb.com/security-whitelist "
even though your IP address is whitelisted.
Very frustrating and misleading error message, please fix this!!
3 votes -
Ability to create more than one index at once
We have migrated a huge collection with nearly 100million records into Atlas. It takes 3 hours to add indexes to it using the rollover strategy and we have tens of indexes to create.
It would be great to simply define all indexes once before starting to apply them.
8 votes -
eviction metrics
Please include eviction metrics as well in monitored metrics in atlas so that it will provide an overview how many evictions are happening in particular time and there by decide correct memory for the instance.
1 vote -
Editing custom Role and Action toggle issue
When adding or editing a custom role in Atlas - When I expand/collapse the Actions or Roles in dropdown, it also toggles the checkboxes. So, when I want to see the roles and actions available, it also checks/unchecks the checkbox, which makes editing the actions in roles difficult.
Please click on highlighted areas in Atlas, as shown in screenshot attached
Thanks.
1 vote -
Allow Billing Alerts per Project
Currently, we can configure Atlas to send an alert when the current bill for any project is above a specific amount. It would be great to be able to set alerts for specific projects. This way we could more easily manage budget fors projects and alert project owners.
7 votes -
Being able to change the cluster name
a cluster has been in development for awhile .. but as new cluster are created within the project.. we'd like to change the cluster name ..
11 votes -
Ability to create and update database triggers via API
It would be really usefule to have the ability to create and update database triggers via the API. Currently, updates to triggers cannot be integrated into our testing and deployment process because the only way to update them is manually through the interface.
4 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.
6 votes -
Alerts "Users do not have two-factor authentication enabled" should name violators
In the email for alerts of type "Users do not have two-factor authentication enabled" it would be helpful to see the user id of the “violator” (user which does not have two-factor authentication enabled), so that I don’t even have to click and log in to Atlas.
Maybe this could be make optional, if there are privacy/security concerns about sending around the user ID in cleartext.
1 vote -
Increase the Contrast of the Delete Document Button
The delete button with low contrast is the one that appears after you click the delete icon on for a document on the collections screen.
The button text is white on a pink background.
See attached file.
It is hard to see the button.1 vote -
Allow NewRelic integration to use EU APIs instead of default US APIs for clusters in EU region
The NewRelic integration in MongoDB is using the default NewRelic API that is in non-EU region. There is a separate API endpoint for EU region, that is described at https://docs.newrelic.com/docs/using-new-relic/welcome-new-relic/get-started/introduction-eu-region-data-center#.
This is causing 'newRelicLicenseKey' failed to authenticate error for the MongoDB Atlas cluster setup in EU region.
5 votes -
Creating cluster specific network Access rules
I am running several clusters while one of them is for the main product we run extras to have consistent data between our test deployments issue is while we are running we change or deploy multiple servers and adding all these servers one by one for testing is not convenient not to mention we use our personal computers as well so we are opening a connection from all IP addresses. When we do that our main server also opens for every IP address which is not good.
2 votes -
Atlas Cluster Labels in UI
With the Atlas API, there is functionality to add labels to various clusters like EC2. It would be great if that was exposed through the Atlas UI as well.
19 votes -
Expose oauth apps to let other services integrate with Atlas
Expose oauth apps to let other services integrate with Atlas, this way other platform can integrate with atlas for provisioning a mongodb instance.
It would allow for a lot of opportunities for developers like automatic mongodb provisioning for a deployment platform
Right now if you deploy with platforms like Zeit or Heroku you have to create a mongodb database and whitelist the right iP manually
1 vote -
Option to restore one or more db from snap to cluster. Right now, it involves manual dump and restore
Currently we can only restore full cluster from backup like snap using GUI interface. If we want to restore one or more specific db, it needs manual dump and restore from backup. if we have an option to restore specific db to cluster through GUI interface, it will be very useful.
164 votesHi all – We are currently developing collection and database-level restores. We expect this feature to be released in CY2025, but will update here once it is launched.
-
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)
6 votes -
Include cluster node list in getOneCluster
Include cluster node information for all nodes in the cluster in the response JSON for the getOneCluster API call. As hostnames are needed for other API calls, there ought to be a better way to get cluster node names.
5 votes -
Integrate Netework Access IP Whitelist with GitHub Actions
I'm trying to setup CI for my project using GitHub actions, while restricting Network Access. The problem is that GitHub's machines have weekly changing IPs: https://help.github.com/en/actions/reference/virtual-environments-for-github-hosted-runners#ip-addresses-of-runners-on-github-hosted-machines
Is there any way to automatically integrate that list of IPs in the Network Access IP Whitelist? This feature would benefit all users of GitHub Actions.
2 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.
6 votes -
There should be a way to try MongoDB beta versions in Atlas
As we move into a more stable version of testing the 4.4 beta it would be useful to allow beta-testers to spin up a cluster with the beta version of MongoDB. Right now beta testers have to download MongoDB which means for some of the more exotic server features in 4.4 they have to build a sharded cluster or replica set. This would be much easier to do in Atlas.
1 vote
- Don't see your idea?