Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1330 results found
-
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.html3 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 -
mongodbatlas_cloud_backup_snapshot_restore_job
Add waitforcompletion field to mongodbatlascloudbackupsnapshotrestore_job to wait untile restore job has finished
1 vote -
In the Project Overview interface of Atlas, show users that the set of clusters is incomplete
In the Project Overview web interface, in the Clusters pane, four of our clusters are listed. I am new to our MongoDB deployment and to this UI. I had no way of concluding we had more than four clusters. I thought that was the complete list.
I feel strongly that if you are going to show only a subset of clusters in a UI, you need to also give users some visual clue that this is only a subset, that the list is incomplete, and that more can be found somewhere.
1 vote -
Auto downscale - Scaling down during peak moments
The auto downscale checks for the average of usage for the last 4h. But, sometimes we have a cluster with little usage for almost all the 4 hours, but at the last 30, 15 minutes, it starts to consume more CPU (something higher than 60% or even higher).
As the autoscale only checks at the last 4h it sometimes happen that a cluster does a auto downscale when it shouldn't. A litler time after it needs to scale back up because the usage goes higher than 90% (or at least higher than 75%)
It would be much better if the…
2 votes -
Configuring provider with shared credentials file for secrets manager
Currently the provider allows configuration for secrets manager for the API key, however it looks like only static AWS credentials can be used which require assuming a role first and exporting environment variables. It would be much cleaner if you could support shared profiles, much like the AWS provider does https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile-1.
https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html
Specifically https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/internal/provider/credentials.go#L49 is static credentials, but would be great to add profile as an option as well.5 votes -
Granular permissions needed with Federated Authentication in Atlas
Granular permissions needed with Federated Authentication in Atlas
For example(but not limited to), it would be good to assign to an external role, via Federated Authentication:
-to create RS users;
-to restore a RS.1 vote -
index stat
Merge index stats from all replicas in index page UI, and enable the reset stats in UI.
Preferably merge all stats from all shards and show it is coming from a secondary replica or a primary replica. Current index stats in UI only show primary stats and it is not useful.1 vote -
Alert When Cluster Nodes Not Regionally Fault Tolerant
If a cluster is not regionally fault tolerant, generate alert to associated email address(es). Since regional fault tolerance is typically only a concern in production environments, provide the ability to only alert on clusters that contain specific tag values. Also, it would be helpful to see the lack of regional fault tolerance as an icon in the console screen for the end user.
1 vote -
1 vote
-
Support for folders with snapshot export bucket
When creating a snapshot export in Atlas, there isn't any support for storing exports in specific folders, i.e. bucketname/mongodbatlas/exportedsnapshots. Instead, the exports have to be stored in bucketname/exported_snapshots.
This creates an issue for posterity, which could in-turn result in data being accidentally deleted.
1 vote -
Alerting mechanism to notify when the node internal/external IP changes for MongoDB Atlas Cluster node
We would need an alerting mechanism to notify the team when the node external/internal IP changes. This helps us to troubleshoot the problem quicker and can change in the firewall configuration quickly.
1 vote -
copy an Online Archive to another region
Provide the possibility to copy an Online Archive to another region, the same way a backup snapshot can be copied to another region.
1 vote -
Provide support for "allowed queries"
I'd love a feature that allows you to select which kind of queries can be run from the Data Explorer UI.
Running ad-hoc queries is a something very common for a development team so its important to allow devs to have access to the Data Explorer, but what is also very important is to make sure that the ad-hoc queries won't impact the production database performance, which might happen in case the queries are not well written and are not making use of indexes.
It would be really great to have some sort of "allowed queries" list, or at least…
1 vote -
Export Aggregation Results as Metrics to Prometheus
Add support for exporting MongoDB aggregation results as Prometheus metrics. This would allow users to track custom queries and dynamic data, enabling more granular and meaningful monitoring and alerting in Prometheus and Grafana.
6 votes -
Calculate Atlas Enterprise by sku
On the invoice, calculate the support value per SKU. Currently, the value of Atlas Enterprise is not included in the SKU.
1 vote -
general cpu class for M400 and M600
Currently when selecting M400 or M600 only "Low CPU" class is available. Our only option to increase CPU is going back to M300 with "General" class to get 96cpu. We would benefit a lot from "General" option of 128cpu and 160cpu.
7 votes -
Data Explorer should reflect the status of the Hybrid Index Build process
At present the Data Explorer has a very limited ability to report the status of the hybrid index build. For instance, when the coordinator is waiting for quorum the Data Explorer may report the index at 100% readiness. That may lead to a confusion that the index should already be available for use - it's not. Such a condition can last for hours.
Ideally, Data Explorer should reflect the status of the Hybrid Index build process showing the progress per individual nodes.
1 vote
- Don't see your idea?