Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1359 results found
-
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.
22 votes -
When I want to end my membership, show all the steps that must performed and bring me to those pages to perform the actions.
You guys know what needs to be done to end a membership. Currently it is very user unfriendly to let your user hunt for all the steps. Especially when your instruction do not match the latest interface.
My very poor experience to end my membership would give me pause to recommend MongoDB, because it doesn’t show a customer centric view and behaviour.
1 vote -
Notification per Cluster
I would like to see notifications per cluster.
Our Problem is that we have a nonprod Cluster, that is inactive at night. When it comes back in the Morning, we get a lot of mails "Search Index Build Complete" this is simply not usefull... But if this happens on our prod cluster this would be problematic.1 vote -
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…
4 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/0000210993 votes -
Atlas Webhook Integration and Custom JSON Payload
Ability to specify a JSON body along with their Atlas Webhook's for additional functionality.
8 votes -
Allow move jumbo chunks to admin users
As an administrator I want to be able to move jumbo chunks by myself. Currently we are not allowed to clean the jumbo flag, so we need Support to do this.
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.
7 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
8 votes -
Add an API endpoint to query the updated version of Atlas Administration API
Provide an API endpoint that provides a list of all Atlas Administration API versions or at least the latest verssion.
1 vote -
OIDC Authentication Terraform Provider
Hi,
it should be possible to authenticate with a service account from Entra ID to MongDB Atlas with the Usage of OIDC.
Here is an example of this in azurerm: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/service_principal_oidcpros:
- no password / private key needed
- no rotation of credentials needed1 vote -
Archival size
Currently the jobs archive only 1.93GB per run which restricts the amount of data archived per day . Is there any way to increase this limit so that it can archive bigger chunks in the scheduled window ?
1 vote -
Set project limits in AtlasProject CRD
It would be great to be able to set the project limits (API reference: https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Projects/operation/setProjectLimit) in the Atlas Kubernetes Operator through the AtlasProject CRD.
Specific use case for us is the ability to set "atlas.project.deployment.privateServiceConnectionsPerRegionGroup" to tweak the number of PSC connections. Now we have to circumvent the operator to be able to tweak this value.
1 vote -
Higher memory hardware option in NVMe
By experience, an optimized MongoDB usually needs more IO and memory, so we can enable a horizontal scale during the live incident.
So a larger memory SSD would be preferred.
For AWS, eg. x2iedn or x8g(require to switch ARM) would be an option.1 vote -
Improve labeling experience in Network Access
I see option "add my current IP address in allow list" quite handy.
After I click that button there is no labeling option near.
I could use a search bar of browser to find a recent ip address but that is too tedious.I want labeling input just after added the address into allowed list.
One more cool option would be to choose a label color.
That way I can manage or distinguish all addresses/hosts simply in a instant look.
1 vote -
Customize CPU threshold for Autoscaling
Currently, to autoscale a cluster to the next tier, the "Average CPU Utilization must have exceeded 75% of available resources for the past hour."
Problem:
Some workloads remain near the 75% CPU threshold, given the nature of the workload. This can cause constant scaling events to occur which creates unnecessary noise.
We don't want to turn autoscale off because this is a beneficial feature to keep enabled on the cluster.
Solution:
We want to be able to configure the CPU % threshold for cluster tier scaling. For example, rather than 75%, we'd like the option to set the threshold to…
21 votes -
Storage autoscaling of storage should also occur when Atlas searches are being rebuild
When the storage requirement exceeds the available storage when rebuilding Atlas searches a warning is issued and manual intervention is needed.
I would like that autoscaling of storage will occur when needed for rebuilding Atlas indexes.
This would save us time and no need to react to warnings.7 votes -
we can set up alerts in Mongo Atlas for the failed integration for datadog /slack etc\
If integration fails for any available third-party tool, we can get notified from Atlas Alert, which helps in saving any issues from metrics and 3rd party tool always functioning .
1 vote -
Show Mongos Connection Number in Overview.
Currently, the connection number shown in Overview is shard connection, it is the connection from Mongos to Mongod, which should usually be lower than the Mongos connection.
The connection limit for MongoDB is referring to Mongos connection which should be shown in overview or otherwise very misleading when we received connection % alert.1 vote -
We would need the GCP project number associated with a certain Atlas project
We would need the GCP project number associated with a certain Atlas project. Preferably we would need this integrated in the Terraform provider and in an API.
Having the GCP project number corresponding to a certain Atlas project would allow ACL creation with the various features provided by the cloud provider.0 votes
- Don't see your idea?