Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1360 results found
-
Azure VNet terminology needs updating
Setting up the Peering Connection (Project Network) has antiquated terminology and instructions.
Microsoft Entra ID is the new name for Azure AD. The names Azure Active Directory, Azure AD, and AAD are replaced with Microsoft Entra ID. Microsoft Entra is the name for the product family of identity and network access solutions. Microsoft Entra ID is one of the products within that family. https://learn.microsoft.com/en-us/entra/fundamentals/new-name#:~:text=Microsoft Entra ID is the,the products within that family.
The name change took place on July 15, 2023. https://learn.microsoft.com/en-us/azure/active-directory/fundamentals/new-name
Currently:
Directory/Tenant ID
This is a 32-character alphanumeric string. Find this in the Azure portal in Azure Active…
1 vote -
Return a user createdDate for Atlas control plane and database users
Automated user systems such as Hashi-Vault will automatically create users. Typically these users have a 90day expiration. Any team using continuous delivery hits the atlas user limit. There is not a way to know when an atlas user was created from the API data
5 votes -
Sync Atlas alert configurations between projects.
Since we can export all Alert configurations from a project, add the ability to sync alerts on all the projects to be consistent with notifications/alerts.
Alerts can be created individually but not in bulk. Please enhance the Mongo Atlas API for the following functionalities:
- The ability to sync all alerts from one project to another.
Thank you
4 votes -
Add document count to Datadog metrics
We'd like to monitor the number of documents in a collection via DataDog.
For On-Premise MongoDB the stats are already reported via mongodb.collection.count, mongodb.collection.size and mongodb.collection.avgobjsize.
If the same metrics could be made available for Atlas (E.g. mongodb.atlas.stats.collection.count) that would really help in monitoring.
E.g. spikes in different parts of the application could be tied to the number of documents on a glance. Without having that metric available, it is hard to pinpoint if a recent change had a negative impact on performance.
If the metrics can't be made available on the collection but only on the database level, this…
9 votes -
Support OIDC as Authentication Protocol for access to Mongo Portal
Currently SAML is supported: https://www.mongodb.com/docs/atlas/security/federated-authentication/#configure-federated-authentication
It would be preferable if OIDC was supported.
6 votes -
Terraform provider should handle pagination for mongodbatlas_atlas_users resource
The resource mongodbatlasatlasusers limits results returned by page with a default of 100 and max of 500. Attempting to retrieve a complete list of users where that list is not a known size isn't possible because of Terraform limitations on dynamic blocks. It would be quite helpful if the Terraform provider handled pagination and this resource by default returned a complete list.
1 vote -
Customer feedback around the UI of Atlas - unable to edit multiple documents at once
The customer wanted me to provide product feedback around the inability to edit multiple documents at once from the Atlas UI. The customer uses a 3rd party tool to do this instead and thought it would be better and more intuitive if this was built right into the Atlas UI.
1 vote -
More Granular Node Read Preference Tags
I would like the ability to set tags on individual nodes so that I can change the read preference with more granularity.
Mongo supports these tags on non-Atlas deployments: https://www.mongodb.com/docs/manual/core/read-preference-tags/#std-label-replica-set-read-preference-tag-sets
Analytic Nodes are very useful, and they are built as way of isolating workloads. The problem is that you can only really isolate into two different buckets (well three if you consider local read nodes). What I'd like to do is isolate more than two different sets of users and queries, so say user reporting and internal dev activities have their own sets, and they work independently.
You could kind…
1 vote -
Stop scamming your users
How about you stop scamming your users with deceptive instruction on your download pages.
1 vote -
Atlas access management similar to Azure AD Privileged Identity Management (PMI)
Hello, we are looking for functionality that allows users to auto-promote or adjust their privileges based on the access needed.
For example: if user XYZ needs access to DB:123 he can elevate access himself to this db.
This would be similar to Azure Active Directory (Azure AD) Privileged Identity Management (PIM). A service offered by Microsoft as part of its Azure cloud platform. It helps organizations manage, control, and monitor access within their Azure AD environment, particularly for privileged accounts. These accounts have elevated permissions that can perform critical tasks, such as managing resources, configuring settings, or accessing sensitive data.
…
6 votes -
Change Streams Monitoring and Alerting
Change streams can cause performance issues if not used properly. In some cases, administrators of multi-tenant dbs have no control (and shouldn't) over how various clients create change streams.
I think it is important that we accommodate these use-cases and provide useful metrics in the OM/Atlas metrics pages, and alerts on those metrics. Some potential metrics:
1. Number of change streams open
2. Average change stream lifetime
3. Query targeting ratios for change streams
4. Avg time between consecutive polls of the change stream (and other statistics)
--thought here is that change streams that are polled infrequently will result in…10 votes -
Terraform Downward Autoscaling "Use Smallest possible" placeholder
When setting "providerautoscalingcomputemininstancesize", is it possible to either;
- Loosen the validation by ignoring current disk configuration size.
- Create a placeholder to indicate "Use smallest possible value".
Atlas appears to support invalid values, provided it was entered when it was valid.
I think this will help simplify deployment of "providerautoscalingcomputemininstancesize", we set the ideal value and THE MACHINE will interpret the best match and remove the possibility of a once valid Terraform definition becoming invalid without any updates on the definition. Like the following example,
1. I define an…1 vote -
serverless concurrent connection limit
Increase to the 500 concurrent connections hard limit so that we can use this in a production domain service. We would also need connection pooling / proxy as described in another idea.
1 vote -
Restore a snapshot from one organization to another organization via API call
I have tried to create automation to restore the snapshot from One organization cluster to other organization cluster. Example Prod cluster from Organization A -> Stage cluster from Organization B.
currently this method is not possible to restore a snapshot from one organization to another organization via API call as API key cannot be shared over the scope of different organization.( As per mongo atlas support Engineer)
Please enable this feature to automate the snapshot restore instead of using UI for restore.
1 vote -
Analytics node with NVMe option
We currently have use mongodb mainly to correct data and visualize with chart features. Some chart require heave disk read operation and need more performance. We need fast storage access only for analytics nodes. If we can select NVMe option only for analytics nodes, we use it but we don't want to switch whole clusters to it since main cluster don't need higher cpu/memory/stroage/iops. We just want to use NVMe only with analytics nodes. Some restriction such as min storage size for main cluster is acceptable but don't want to upgrade to higher tier of main cluster.
1 vote -
Atlas project capacity should be discoverable
Atlas project capacity should be discoverable. Based on documentation, it seems project capacity is dependent on various factors and can be arbitrarily increased via support request. We currently do not know how many clusters/nodes we have available to deploy in a given project and that is critical information to inform planning at scale.
7 votes -
Add Terraform resource for functions
Would be great to have a terraform resource like mongodbatlas_function.
Was mentioned here https://github.com/mongodb/terraform-provider-mongodbatlas/issues/828 but I didn't find the idea mentioned there, so I added this one here.67 votes -
Reestablish private endpoint if in status "Rejected"
Create an AWS endpoint for connection with the (already established) MongoDB Atlas endpoint service -> AWS endpoint is in "Pending acceptance" status.
Establish the connection with "mongodbatlasprivatelinkendpointservice" -> AWS endpoint goes into "Available" status.
Destroy the "mongodbatlasprivatelinkendpointservice" connection -> AWS endpoint goes into "Rejected" status.
Recreate "mongodbatlasprivatelinkendpoint_service" with the same variables -> terraform does recreate he resource, but the resource is not functional.
In the MongoDB Atlas GUI it shows "Failed. Endpoint failed to reach available state. Click 'Edit' to fix the problem."
The problem cannot be fixed by using "Edit" !…
2 votes -
Retrieve latest/max oplog timestamp via the Atlas Administration API
At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.
For example, in the UI it states:
You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.
Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.
7 votes -
Support hourly backup every 24 hours, or support Point-In-Time restore without an hourly backup
To have Point-In-Time restore, an hourly backup policy is required.
However, the maximal interval for an hourly backup is every 12 hours.
I would like to take a backup only once every 24 hours, but still have Point-In-Time restore possible.So, please support either PIT-restore without an hourly backup policy in place, or support an hourly backup policy with an interval of 24 hours.
2 votes
- Don't see your idea?