Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps
In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances.
As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it.
Please provide a way to simply ignore the notimeout option, instead of breaking its connection.
Thanks!
1 vote -
Atlas Capacity Check for Cluster Creation or Changes
When creating large new clusters sometimes Atlas does not have enough resources available from the cloud provider. When this happens a restore or cluster change fails without reporting what the actual issue is.
Solution: Verify available capacity and issue a warning or error if it is possible that the operation will fail & recommend opening a support ticket (or have a dialog to automatically do so listing the details)
4 votes -
Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
5 votes -
SNMP
Enable SNMP setup on Atlas Resources.
1 vote -
Need static private ip for cluster nodes
Please see details in https://support.mongodb.com/case/00682480
3 votes -
Include cluster labels with Invoices API response.
Using the Invoices API to aggregate cluster costs by label involves cross-referencing the Cluster API. Including cluster label information as part of the Invoices response would eliminate this extra step.
4 votes -
Allow db.killOp() and manual restarts on secondaries
Please allow us to kill user threads on Mongo secondaries. Sometimes we have long running queries on secondaries and need to kill those threads but can't do anything about it since we don't have admin privileges to kill threads.
Also please add the ability to manually restart secondaries, not just failover the primary.Thanks.
11 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?
33 votes -
Add MFA status to the API
A field indicating whether MFA is on for organization users (i.e. on https://docs.atlas.mongodb.com/reference/api/organization-users-get-all-users) would be extremely useful!
2 votes -
MongoDB Orphaned Docs Utility
When we upgrade MongoDB there is the possibility that orphaned collections that need to be deleted can prevent the upgrade from completing.
It would make sense for Atlas to include a proactive utility that searched a customers sharded cluster for orphaned docs and gave them the option to clean up the orphaned docs ahead of a major version upgrade.
1 vote -
Add API endpoint for Organizational Settings
To be able to change and read Organizational Settings in an automated matter, support for Organizational Settings should be added to the Mongo Atlas API.
4 votes -
IO throttling
Atlas should be able to throttle IO in a way that does not allow excessive IO to degrade a node or take a node offline. Current functionality has no defense against a high IO data job other than to allow a node to fail.
1 vote -
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.
14 votes -
Governance rules at the organization level
Hello team,
Would it be possible to be able to set up governance rules at the organization level in order to control certain configuration elements.
For example:
Control authorized providers and regions for an organization to prevent creation of cluster in unauthorized regions. (We must keep the data in Canada for some of our databases)Check the allowed IP (IP Access List) addresses
Disable the use of SCRAMS accounts for database access.
Control the "Data Explorer" functionality at the organization level to prevent its activation at the project level.
2 votes -
Redirection of ATLAS activity feed to a MongoDB cluster that we own.
Hello team,
Would it be possible to have a feature to redirect activity logs from ATLAS to a MongoDB cluster.
The idea is to be able to easily retrieve these logs with Kafka Connect and also to be able to easily query in these logs.
One could configure the redirection of activities at the organization and projects level by providing the Atlas cluster to use and the access accounts.
Example:
Main organization
- Project: "Activity Feed"
- - Cluster: "Activity Feed Cluster"
- - DB: "Atlas Activities by organization"
- - - Collection: "Activities by project"1 vote -
Atlas Shard Management
Currently the Atlas UI only presents options for how many shards a cluster can have.
Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/tutorial/manage-data-sharding/#manage-sharded-collections
3 votes -
Support for delayed replicas
It would be great if Atlas provided support for hidden, priority 0 delayed replicas. For workloads that do not need real time data or situations where data recovery is needed, a delayed replica would be the fastest way to mitigate both of those scenarios.
7 votes -
allow for renaming and moving of collections and databases on server
Right now it is difficult to rename and move databases and collections without downloading and re-uploading them.
Please enable this critical functionality as it's very common to need this when administering data.
2 votes -
Setup activity feed retention
It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.
1 vote -
Create alarms base on events + Add control policies
Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.
The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...
For example:
- Be able to avoid the use of user scram.
- Be able to avoid using unauthorized IP addresses
- Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal3 votes
- Don't see your idea?