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
-
Allow removing database user from all projects
Sometimes we need to remove a database user from more than one project. Right now, the only way to do this is by clicking through each project and doing each one separately. It would be much more convenient if there was a way to search/remove a given database user from all projects at once.
1 vote -
Add boolean for applying changes only during maintenance window
Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.
E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.
See DocumentDB as an example for this feature.
https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html4 votes -
Atlas dedicated tier is not actually dedicated
MongoDB Atlas, despite the documentation and Atlas UI reflecting M10+ as dedicated tier, is not actually dedicating all resources. While CPU and Memory can be considered dedicated, storage is not dedicated until M300+. After working with MongoDB Support, and support working with AWS support, our performance issues were identified by a noisy neighbor who was choking our disk IOPS even though we are running M40_NVME clusters which are supposed to be high performance.
MongoDB should at a minimum highlight this as a consideration for latency sensitive deployments.
A new Atlas alert should be created to identify issues where slow query…
6 votes -
bulk delete backups
Allow bulk deletion of backups on both active and terminated clusters through the Atlas web UI. It is currently quite cumbersome so delete them one by one if needed.
1 vote -
Premium Monitoring Granularity for lower tier clusters
CURRENT STATE
Premium Monitoring Granularity (10 second metrics) only available on M40 clusters or higher
IMPACT
Lower tiered environments (such as testing and staging) cannot have 10 second metrics granularity. Some customers export metrics to third parties such as Data Dog who only handle homogenous granularity of metrics.
When Data Dog accepts different granularities e.g. 10 second granularity for PROD environments (M40+) and lower granularity for STAGE environments (lower than M40) - it leads to poor data integration and dashboards failing to load data properly.
Customer does not have a reliable into their data since some environments send 10 second…
2 votes -
Continuous evaluation
Continuous evaluation Collaboration and actionable alart
1 vote -
Custom Role - blank collection note
This screen should have some indicator saying "If collection is left blank, applies to all collections.
I tried entering a "*" and that didn't work. Did some searching and eventually found I could leave it blank.
1 vote -
Manage Organization Alerts in Terraform
We should be able to manage organization alerts through terraform, not only project level alerts.
I wanted to create a billing alert at organization level with terraform but was not able to do it, because the resource only allows the alert to be created at project level.
Doc: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/alert_configuration2 votes -
User Limit
Hi Team,
Please add a new alert for the Database User limit. Alert should be configure for desired percentage of user . For example ( 80% )
1 vote -
Support for Push-Based Logging to Azure and GCP
Asking on behalf of customer, please add Support for Push-Based Logging to Azure and GCP instead of just to AWS S3 buckets: https://www.mongodb.com/docs/atlas/push-logs/
18 votes -
Rolling Index Build : Hide nodes until replication lag below threshold
During a rolling index build, do not bring a node back online as visible until replication has caught up and/or reached a configurable threshold to ensure optimal data availability
1 vote -
Mongodb Atlas Malaysia AWS regions
Malaysia region is poised to be the largest AWS region and it is pertinent that Atlas can support it for south east asia. Writing in to petition of this region's support.
5 votes -
Propagation of NodeType via Prometheus metrics
Context: we rely on Prometheus metrics for various systems in the company. The setup of clusters until now was pretty standard, so basically we had replica sets and sharded clusters with electable nodes only – clusters with three nodes per RS or shard which numbers correspond to <clustername>-<shardnumber>-<(00|01|02)>>. Now we have a fourth analytics node in the clusters, which out of convention seems to get the next incremented number 03.
The thing is we cannot rely on convention and we need to have a way to distinguish the node types from Prometheus metrics (or at least from the Atlas API)…
33 votes -
Add a Atlas control plane in UK region
Currently Atlas control plane IP addresses originate from your AWS us-east-1 region. With our region being UK, security team does not like request into our network originating from US.
Request a control place in UK region.2 votes -
1 vote
-
mongodbatlas_federated_database_instance add GCP support
Is GCP support planned for terraform provider and GCP?
dataprocessregion {
cloudprovider = "GCP"
region = "IOWAUSA"
}Trying to use this in Terraform results in 500 Internal Server Error
│ Error: error creating MongoDB Atlas Federated Database Instace: https://cloud.mongodb.com/api/atlas/v2/groups/***/dataFederation POST: HTTP 500 Internal Server Error (Error code: "UNEXPECTED_ERROR") Detail: Unexpected error. Reason: Internal Server Error.
1 vote -
Support multiple U2F devices (e.g Yubikeys)
It makes me nervous to only have one entered here. I always add a backup key to each site that use a U2F device. That is generally recommended and I have learned that the hard way.
The means there would be an option to name each device instead of accepting the one I currently plugged in.
And btw, I am very happy about the recent MFA addition. SMS is gone!
1 vote -
Manage Database by Kubernetes Operator
In our use case, we are dynamically creating feature environments based on the branch name. During this process, we are also creating MongoDB databases in the same Atlas cluster (different envs are sharing the same cluster but with different database names). For now, we need to do it with a separate CI step that should create this DB and delete it when the env is deleted.
It would be great to have the possibility to manage DB create/delete process with Kubernetes CRD. For now it's the only 1 missing feature that is blocking us to start using Operator.
8 votesThis is something we're considering for the future.
But the biggest problem we need to solve is that it's incredibly easy to create/delete/update databases within a deployment via many other interfaces. But if this happens, the Operator's source of truth (the custom resources) won't contain the changes, and the Operator would overwrite the changes using it's source of truth.
-
Request for Enabling Vendor-Metered Tagging on AWS Marketplace
Hi Team,
We are currently utilizing MongoDB services via the AWS Marketplace and have encountered an issue related to cost allocation tags.
We have recently been working on improving our cost management and reporting processes within AWS.
A key component of this effort involves leveraging AWS-generated cost allocation tags, particularly those prefixed with "aws:marketplace:isv:".
However, upon review, we have noticed that these specific tags are not available or being applied to MongoDB services that we are using.The absence of vendor-metered tags for MongoDB on AWS Marketplace is hindering our ability to effectively track and allocate costs associated with your…
19 votes -
ชุมชน
ทรัพยากร
1 vote
- Don't see your idea?