Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1310 results found
-
Request for Addition of Seoul Region to Reduce Latency
Sure! Here's the translation of your request:
A brief description of what you are looking to do
I would like to request the addition of the Seoul region because there is currently only the Japan region, which results in a 2-second delay for requests.How you think this will help
Adding the Seoul region will reduce the latency and improve the overall performance of our application.Why this matters to you
This matters to me because the current delay is affecting the user experience and efficiency of our services. Reducing latency is crucial for maintaining high performance and user satisfaction.17 votes -
Activity feed filters - allow filtering by cluster node name
We need to be able to filter the activity feed based on the name of the cluster's nodes, not just the name of the cluster itself.
8 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…
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)…
27 votes -
Support Google IdP for OIDC Workforce Federation
The Atlas supports federated login with external Identity Providers via OIDC (https://www.mongodb.com/docs/atlas/workforce-oidc/) for authenticating human users in tools like mongosh or Mongo Compass.
Unfortunately the OIDC login doesn't work with the GCP IdP: OAuth2 clients in Google IdP always have a client secret (even clients considered as "public"). There is no way to specify the client secret in Atlas UI in the Workload Federation configuration and this leads to "invalidrequest (clientsecret is missing.)" error returned from the IdP as it always expects a client secret to be present.
The support of an optional client secret in…
4 votes -
Performanse advisor node type filter (to exclude analytics)
Performance Advisor should allow selecting node types to exclude analytics nodes.
In most cases, analytics queries don't require indexes as queries are very different and might be filtered by any field.
6 votes -
Support for push-based logging integration with Google Cloud Storage
As of now, MongoDB Atlas supports log export functionality exclusively with AWS S3. In addition to the existing AWS S3 bucket integration, would be good to have the capability of pushing logs to GCP Cloud Storage for organisations who depend on GCP for cloud infrastructure.
8 votes -
Improve Admin API for API keys rotation
Given we have security mandates where we need to rotate API keys for an organization, every 365 days. It would be ideal if when calling
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Programmatic-API-Keys/operation/getApiKeygetApiKey from admin api that it should return the created date. This way programmatically we can rotate keys and maintain security posture. As well if there was a way to just refresh the api secret and not generate a new one that would be a plus
3 votes -
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.
4 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.
-
Disable Query Targeting alert notifications for $changeStream operations
Change streams require scanning of the oplog and cannot make use of indexes, meaning that $changeStream operations frequently trigger Query Targeting: Scanned Objects / Returned alerts that cannot be actioned. It would be ideal to allow $changeStream operations to be filtered from the Query Targeting alerts.
15 votes -
API - Version 2
We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/
We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
"replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}What I need to change is only the…
9 votes -
Integrar la alerta de Replication lag de Atlas en el API de Prometheus
Se solicita incluir métricas en el API de prometheus para poder implementar la alarma de Replication lag
6 votes -
Atlas Webhook Integration and Custom JSON Payload
Ability to specify a JSON body along with their Atlas Webhook's for additional functionality.
6 votes -
More information about snapshots and oplog sizes for backup optimization
Backup optimizations always involve costs. However, currently, we only have access to the number of GB we are consuming. I'm not able to tell which snapshots are full or incremental. Also, when Continuous Backup is enabled, I can't see how much I'm spending on oplogs and snapshots.
Without that information, I can't figure out if it would be better to reduce the Point-in-Time window, delete old snapshots, or change the snapshot policy.
I went through these documentation, but I still miss the actual sizes of snapshots and logs to make the correct decision.
- https://support.mongodb.com/article/000021504
- https://support.mongodb.com/article/0000210992 votes -
Control Over how to upgrade minor versions or rollback if required
Hello Team,
We recently faced an issue with the automatic minor version upgrade that rolled our clusters from 6.0.16 to 6.0.17 through Atlas. Since 6.0.17 has some problems, can we request the following features:
1. Disable automatic upgrades of minor versions.
2. Allow manual rollback to previous minor versions when necessary.2 votes -
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 -
Control shard balancing window with Terraform
This documentation page talks about how to manage shard balancing - https://www.mongodb.com/docs/manual/tutorial/manage-sharded-cluster-balancer/#schedule-the-balancing-window
but it requires connecting to the db first, I see no way to manage this through the Atlas Gui or terraform.
We have had some instances recently where shard balancing has caused a large resource usage spike on our cluster and affected our services and we would really like to be able to set a shard balancing window using terraform to prevent this from happening during the middle of the day2 votes -
Option to prevent backups restores into particular cluster
Today it is possible to accidentally restore backup into live production database. There is a "I confirm" dialog in the UI but it is not fool proof, plus when using terraform provider you still could do yourself harm.
It would be nice to have an option similar to Termination Protection where I could mark a cluster that it should be impossible to restore backup into. If I want to restore backup into existing cluster I would have to turn the restore protection off. Or I could restore into a new cluster.
Another way to do it would be to have…
2 votes -
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/
7 votes -
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…
8 votes
- Don't see your idea?