Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
480 results found
-
Ability to stream logs to Cloudwatch Logs or Datadog
There's no way to stream logs from MongoDB on Atlas right now. I should be able to stream logs, either to Datadog or Cloudwatch or something!
257 votes -
I'd like to be able to connect to my cluster directly from the UI and have a shell-like experience i.e. run queries and operational commands
It would be great if I could connect to and run commands against my cluster via the Atlas UI so I don't have to rely on downloading and running the shell locally.
I'd also be more confident I was running commands against the right cluster as I would have less reliance on managing connection strings and differentiating between them. This would be helpful if I'm not on my regular machine and need to do some ad-hoc querying or debugging.
166 votes -
Force restart of unhealthy node
Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.
If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)
110 votes -
Administrate user rights for the Billing area
Hi.
We would like to have the possibility to administrate user rights also for the Billing area. In order to restrict all users seeing the invoices and to give this right only to particular people who are directly responsible for it. Please consider such feature for the next releases.85 votes -
Live Migrate Individual Namespaces
Mongomirror allows you to migrate particular databases or collections using the --includeDB and --includeNamespace parameters:
https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includedb
https://docs.atlas.mongodb.com/reference/mongomirror/#cmdoption-includenamespaceIt would be helpful if Live Migrate allowed for use of these options as well to migrate subsets of data, instead of only migrating an entire cluster.
73 votes -
Allow custom DNS hostnames to be added to cluster config / TLS certs
Since Atlas clusters now support different sets of hostnames, it would be good to explore the feasibility of allowing users to add their own hostnames to the cluster configuration and TLS certificates such that custom connection strings can be used.
One use case for this is being able to "wrap" Atlas connection strings, such that an application's connection string would never need to change despite underlying cluster changes (cluster being moved between projects, etc.)
This could also be useful if you wished to whitelabel your cluster.
46 votes -
Create distinct indexes for Analytics nodes
To effectively use Workload Isolation, it is desirable to have different indexes on the operational cluster nodes than the indexes used to support analytics and reporting query patterns. It would be powerful for Atlas to enable different indexes on Analytics nodes.
45 votes -
Make BI Connector Settings Permanent
Allow the "SET GLOBAL mongodbmaxvarcharlength = n" to be permanent after a Mongosqld restart. Currently, the setting is ephmeral and must be set everytime the mongosqld daemon is restarted. Currently, our production environment mongosqld can restart without our knowledge at anytime. This results in the mongodbmaxvarharlength variable being reset to zero, which can lead to a production outage. Is there anyway this can be automated, maybe through database trigger?
39 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.
37 votes -
Compact collection from UI
Compacting of a collection directly from the MongoDB Atlas website UI.
No need to run CLI commands and changing primary database.
Making regular maintenance easier.
33 votes -
Atlas maintenance Notification should include description of maintenance
Whenever Atlas wants to do maintenance, it is sending email alert about the timing of maintenance. In addition to that we are requesting information about the nature of maintenance also like Mongo patching , BI connector upgrade or increasing no of connections etc. This will give us the information about the work and we can broadcast the same to our counterparts so that they can also use the product efficiently.
32 votes -
peering
allow multiple Atlas CIDR (VPC Region) in the same project and allow attaching each cluster to the desired vpc.
today in order to have multiple vpcs in atlas (for example dev &prod)
they need to be separated projects, that create a lot of duplicated work and settings31 votes -
Allow multiple VPC CIDR ranges in Peering connection
Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.
Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
Today, I need to create a separate private link connection to be able to connect to the second CIDR range.30 votes -
Allow cluster to define priority of availability zones
Similar to how it's possible to select the preferred region in a multi-region cluster, it would be beneficial being able to select the preferred availability zone in a single-region cluster. This would allow an application to live as close to the cluster's PRIMARY node as is possible.
27 votes -
Restrict specific users or client IPs to only Analytics node(s)
There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.
Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…
23 votes -
Carbon Footprint Calculator
A widget or calculator in the Atlas UI, where the user can see the projected carbon footprint of a deployment per year while they are configuring the deployment. And / or a live counter of the carbon Footprint for each deployment/project/org.
22 votes -
Control IP Access list for project-only API keys at the project-level exclusively
When setting up API keys as a project owner, you only get one opportunity to manage the access list without getting an Organization Owner to modify it thereafter.
This creates a bottleneck where users need to ask for their API key access list to get changed (or alternatively make a new keypair, and have the API Keys list cluttered).
If a key is only being used in one project, it should be allowed by the project owner to update the access list at any time since there is no risk of it affecting the organization.
19 votes -
Allow maintenance window definition per cluster
Currently maintenance windows are defined per project. With multiple clusters in a project, maintenance will be performed at the very same time.
We would like to space out maintenance windows per cluster in the same project, to prevent replica set election on multiple clusters taking place simultaneously.
18 votes -
Allow the ability for a rolling cluster restart like during maintenance
Currently there is no way to test how applications behave during maintenance apart from waiting for maintenance, the ability to force a rolling cluster restart as happens during maintenance would be great. The failover is a different process and affects primary mainly.
18 votes -
Set schedules for pausing clusters
It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.
17 votes
- Don't see your idea?