Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
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" !…
1 vote -
1 vote
-
Allow customization of where $merge creates the temp collection used when rehydrating data from Online Archive --> Atlas
When you restore data from the Online Archive back into your Atlas cluster (aka "rehydrate") you need to use $merge within an aggregation pipeline. What isn't documented is that $merge will create a temporary collection in the same database you're rehydrating to, which requires that you have readWrite@<dbName> privileges so that the new collection can be created.
For customers that operate on the "principle of least privilege," where you only grant literally exactly what is needed to accomplish database CRUD operations, the user would the more narrowly scoped "readWrite@<dbName>.<collName>" privilege granted to the user to scope the actions to only…
10 votes -
Support tagging individual replicas in the cluster
Thank for the support for the tagging at the cluster level during database deployments( https://feedback.mongodb.com/forums/924145-atlas/suggestions/43032180-support-for-tagging-clusters-in-atlas)
However it would be useful to have support for tagging individual replicas in the cluster.
For example., we want to deploy the same app as two deployments tagged as tier-1 and tier-2, with tier-1 deployment service accessing tier-1 tagged readonly replicas and vice-versa.
1 vote -
Improved deletion protection against malicious users
Currently, the only option of preventing malicious admin users from deleting a cluster with all its backups is to enable a backup compliance policy. However, this policy is quite the beast with complex processes and guarded by a single user account (which could then as well be the malicious one).
It would be good to have some less impactful way of protection against malicious users.
For example, when deleting a project in Google Cloud, an email is sent to all project owners and the project including all of its data can easily be restored within a period of 30 days.…
4 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 -
Allow to change defaultWriteConcernSource to global to avoid flipping the flag
Customers experience following error messages due to the defaultWriteConcernSource mismatch between the source and target cluster when restore the snapshot.
Error: Can not restore a snapshot with custom default write concern 1 to a cluster that does not have a custom default write concern.
Error: Can not restore a snapshot with custom default write concern majority to a cluster that does not have a custom default write concern.
Ability to directly change the defaultWriteConcernSource without flipping between w:1 and w:majority will be convenient for the users.
Option location:
Cluster > configuration > Additional Settings >
More Configuration Options > Default…2 votes -
SIEM
Add audit log integration with enterprise SIEMs
6 votes -
Improve Metric Correlation
Would be nice to better correlate metrics, server events, and individual operations.
For example would be helpful to have in the profiler indication of automatic scale up/down of the cluster in order to easily correlate actions that trigger them in the last 24h.
1 vote -
Metric Grouping
A huge improvement and help when it comes to metrics would be the ability to query by grouping (e.g. for database access users). This way if you were to use a specific database user per a specific service connection, we could see how much load to the database that specific service is causing.
Any form of implementation would be helpful, one example could be adding labels to the prometheus metrics per user, replica/shard etc.1 vote -
Profiler: expose the dashboard ID and chart ID from which the query is originating
My MongoDB analytics node performance is decreasing.
Looking at the profiler it seems that some specific queries are super slow.
I can see the full query, I can see that they originate from MongoDB charts ("appName": "atlas-data-federation|app-services|xxxxx").
But I cannot see which dashboard ID and which specific chart ID this query is originating from.
So I cannot, for example, easily find which chart to delete.Is this something you could help with? or any work around?
thanks!1 vote -
BI connector host name via API call
BI connector hostnames in the Atlas UI: https://www.mongodb.com/docs/atlas/bi-connection/ is not supported via API , Currently, customer has to manually copy and store the values to be reused by other applications. The customers are hoping to get these values in an automated way, for example with API calls or SDK.
2 votes -
All Clusters permission for ORG level roles
Today, for you to be able to use All Clusters you need to have permissions on each project, your user needs to be included in each project.
When we use a federation, we generally don't grant permission for each project to a team of administrators. We grant ORGOWNER, for example. By doing this, we lose access to All Clusters. The idea was to include the permission to use All Clusters for project-level permissions that have permissions to read project resources, for example ORGOWNER or ORGREADONLY.
6 votes -
Throttle instances within a shared tier
Right now, if a cluster is in a shared tier, other "noisy neighbor" tenants can destroy performance by overusing the resources, forcing a restart, causing unstable behevior etc.
Throttle noisy neighbors so that others don't suffer!
1 vote -
MongoDb Atlas Network Peering with Oracle OCI (Similar to Azure and AWS)
Please add similar Atlas network peering capabilities as that of Azure and AWS, for Oracle Cloud Infrastructure customers. We are currently using Azure, but would like to use OCI as well.
1 vote -
AtlasProject CRD status fields
Hi, we have created the Atlas project via Terraform and used the mongodb operator for cluster and user management, but for now, we use sidecar to set the status.id field in AtlasProject CRD since we use skip-sync flag ( so operator will not change project config) and the operator will not sync this field for us.
If it is possible add a parameter to the spec where I could set this ID within resource creation ( so if we have a skip flag it will automatically set status.id ), so we can get rid of sidecar ( sidecar was implemented…1 vote -
View Epoch in Compass
I use epoch times in almost every collection for created time, last modified, etc. Currently I have to copy the time value and paste it into epochconverter.com. It would be very handy if the time showed as a string in a bubble when you hovered over it in Compass.
1 vote -
Larger disk for smaller cluster tier (instance type)
We have TB-scale data in production, and we also have several databases of the same-size for development environment.
Since Atlas's smaller cluster tier such as M20, M30 doesn't support large disks, we need to pay a lot for staging environment too even though we don't need many CPUs / RAMs.
We hope Atlas to support varied storage options in smaller cluster tier
1 vote -
A new role for security auditing purposes
Currently MongoDB Atlas provides two read only roles at project level ("Project Read Only", and " Project Data Access Read Only").
"Project Data Access Read Only" seems to allow access to the data also, while "Project Read Only" role does not allow access to the logs. (https://www.mongodb.com/docs/atlas/reference/user-roles/)
For security officers (internal/external), they need to access to the logs (audit, access, etc) and also to review the configuration; but don't need access to the data.
Therefore, I would like to request a new project level role for security officers with following features.
- access to "Download Logs"
- access…5 votes -
Setup the Atlas web user's team membership as part of the invitation.
Doing so, removes the extra step of assigning the team after the user has accepted the invitation.
2 votes
- Don't see your idea?