Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1358 results found
-
Display the error code within Atlas UI if an index fails
When creating an index via the Atlas UI, the interface currently does not display the error code if the index build fails. This lack of visibility makes it difficult for customers to understand the cause of failure without contacting support.
This limitation is particularly impactful for unique index creation. In these cases, mongod validates constraints only at the end of the build process. If duplicate keys are found, the index build fails after consuming significant time and resources — but the Atlas UI does not surface the underlying E11000 duplicate key error (or other relevant error codes).
If I submit…
1 vote -
Intro to MongoDB Learning Path Issue : I could complete 25% very long back. Kindly permit me to complete the remaining part and resume path
Intro to MongoDB Learning Path Issue : I could complete 25% very long back. Kindly permit me to complete the remaining part and resume path
1 vote -
break down usage on DB level on bill summary
We have multiple application using different DB on the same cluster, current bill has usage breakdown on the cluster level which we are not able to bill application for their usage, would like to have bill breakdown on DB level, so we can bill proper team for their usage.
thanks
Li1 vote -
break an invoice down to the database level
We have different application using different DB on the same cluster. current billing break down on the cluster level which we can't itemized the bill and know how much each application usage on the bill. would like to have bill break down usage on the DB level.
thanks.
Li1 vote -
Expose more in depth metrics
We have had cases where support has been able to investigate issues with our clusters that we ourselves can't due to access to metrics that are not available via atlas, but are avalible to support.
All available metrics should be presented via the UI as well as the datadog add on (or even via tools we can use to get access to these metrics separately).
Notable metrics include: system TcpExt DelayedACKs, system Tcp RetransSegs, ss metrics repl apply batches num, rs member _id 1 heartbeat time, ss ss global: queued writers
2 votes -
Billing Alerts on Atlas
Currently the alerting for billing is based on fixed values. It would be better to have the option to set up billing alerting based on increased percentages instead of fixed values. This way it would be easier to set up applicable cross-functional alerts for enterprise organisations to monitor costs.
7 votes -
Support Billing Alerts Based on Usage Date
Currently, Billing Alerts in MongoDB Atlas are triggered based on the Billed Date, not the Usage Date.
This often results in alerts caused by delayed reporting from cloud providers, rather than actual real-time usage spikes.I suggest adding an option to trigger Billing Alerts based on Usage Date.
This would make alerts more accurate, reflect actual activity, and help users respond promptly to unexpected cost increases.2 votes -
CMK - Customer Master Key Region to allow multiple regions to select
Currently while setting up CMK for cluster only allowed to give one region as "Customer Master Key Region". For multi-region cluster, in case of Region outage, though MongoDB promotes writer to cross region, customer needs to re-configure the "Master Key Region" to another available region. If customers are using multi-region CMK, selecting only one region as "Master Key Region" needs manual intervention incase of region failures.
Could you have multiple region option "Master Key Region" to support multi-region CMK.1 vote -
Granular permission for project level
Atlas project-level roles (like readWriteAnyDatabase or readAnyDatabase) apply universally across all clusters within the project.
We understand the current limitation where roles like readWriteAnyDatabase or readAnyDatabase apply across all clusters within a project. However, for our use case, it is critical to assign granular database permissions per cluster for AWS IAM roles—especially to avoid unintentionally granting access to sensitive clusters like Unification.Given this, we would like to formally request this as a feature enhancement. Specifically, the ability to:Ensure isolation of role permissions per cluster within the same Atlas project. We also opened a case 01493221 for this with support
3 votes -
Preventing archives from being orphaned due to certain sharding operations
When performing a moveCollection operation to move an unsharded collection from one shard to another, it would be ideal if the archive did not become orphaned. It would likewise be ideal if resharding and disabling sharding on a collection did not cause the archive to become orphaned.
1 vote -
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks and how to pause
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks and how to pause those cluster automatically which help us to save cost.
1 vote -
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks and how to pause
We would like to know the how to find out the inactive atlas cluster which are not actively using user more than two weeks or some specific period and how to pause those cluster automatically which help us to save cost.
1 vote -
Allow the creation of an Atlas Resource Policy based on database user authentication type
We would like to create Atlas Resource Policies based on the user authentication type. In a more specific example, we would like to allow ip("0.0.0.0/0") only when the database user authentication type available is Federated Auth. Another way to look at it is to deny ip("0.0.0.0/0") when the database user authentication types of x.509 or SCRAM are being used.
7 votes -
2 problems in Atlas metrics webUI
There are two annoying bugs in the metrics page on Atlas web related to the browsers refresh button:
1) Try to rearrange the different metric graphs (panels) to anything other than the default order (like move them up and down to a different order). When you hit refresh - their order is reset.
2) Open two different pages with graphs of any replica sets (or shards). They can be the same or different. Then, on one of them, change the zoom pulldown menu for a different setting (like 1 hour to 8 hours). Wait for the graphs to update to…
1 vote -
Terraform to have a generic org_owner_id instead of personal email for org creation
For now; I was told that the orgownerid while using org create using terraform has to be a non- generic email ID
data "mongodbatlasorguser" "test" {
orgid = mongodbatlasorguser.test.orgid
username = mongodbatlasorguser.test.username
}For example siri.bhar@centene.com can we have a feature to have a generic one in place or a distribution list?
4 votes -
Developer Sandbox M0 should be supported within private link
Part of the developer sandbox we can now provision M0 through self services. But we don't support private networking for M0. For FSI industry, Pharma especially this is a deal breaker as developers would want to use PII/PHI data for their PoCs/MVPs.
If we can provide M0s in their private network like other tier's there could be wide adoption of MongoDB by developers within these industries.
2 votes -
DataBases Prices
Several clients from Brazil frequently complain that MongoDB is expensive. One of the reasons is the need to create separate clusters (even M10-sized clusters) for development and/or staging for each production cluster.
One alternative they are using to reduce MongoDB costs is to share DEV and/or staging clusters among multiple teams. However, this introduces another challenge: how to split these costs internally between different departments.
To address this demand, which has been raised by several clients—including Ambev, Anhanguera, DASA, and Digibee—my suggestion is for Atlas to provide a way for customers to see the cost per database within a cluster.…
1 vote -
Atlas GovCloud Archival
Please add the online archive feature for GovCloud
1 vote -
Early-Warning Alert for AWS PrivateLink Limits in MongoDB Atlas
Problem
- Cluster create/scale fails only after AWS PrivateLink endpoint quota is exhausted.
Request
- Add a threshold-based alert (e.g. 80 % of limit) via UI banner + email / webhook.
Benefit
- Prevents surprise downtime, lets admins request AWS quota increases or clean up unused endpoints in advance, and cuts support tickets.
Quick Implementation Ideas
Show current usage vs. limit in Network Access → PrivateLink and Admin API.
Allow per-project alert threshold.
Display projected endpoint use on the Review & Deploy screen.
9 votes -
Add single link between workload identity provider and organization via Terraform
We currently have multiple Terraform workspaces for different environments that each set up their own MongoDB Atlas workload identity provider (AKS cluster). In order to link these providers to the organization you have to manage a "mongodbatlasfederatedsettingsorgconfig" resource and pass a list of ALL identitiy provider ids. The Terraform workspace only knows (or rather: should only know) about its own identity provider, so it would be nice to have a single Terraform resource that manages a single workload identity provider <-> organization link.
1 vote
- Don't see your idea?