Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1273 results found
-
Allow domain or URL for whitelisting
Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.
3 votes -
Export results of an aggregation query to csv file
I have created an aggregation pipeline from the aggregation tab of a collection but unable to export the results of that query to a CSV file.
2 votes -
Seeing ports that Clusters listen to
In your documentation and even through the atlas web api, there is no straightforward method to see what ports my clusters communicate on. This is highly frustrating as I am using the Mongodb Atlas Private endpoint and need to Allow Inbound/Outbound communications on certain ports for the endpoint to work.
1 vote -
Improve Cluster Name Limits
Cluster names currently impose the following limits:
Cluster names shorter than 23 characters can't end with hyphen or dash (-)
Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.
Instead, we should either trim or replace the hyphen at the end of a 23 character name.
3 votes -
1 vote
-
1 vote
-
1 vote
-
in Atlas Cloud Manager, sort the network IP access list
page security/network/accessList
the list of IP addresses is unsorted and unmanageable
please allow sort by IP or Name (Comment)
1 vote -
8 votes
-
Tag-aware permissions to control access to analytics nodes
MongoDB has the great future of Workload Isolation based on node tags: we can add nodes tagged for analytics or reporting and then configure the same tag for this type of connections so that they do not interfere with the main operational workload.
But it is the responsibility of the BI/Data Scientist/Analyst to properly configure the connection: it cannot be enforced in a centralised way. It would be great if MongoDB permissions could be "tag aware", and allow access for a particular user only to some nodes of the cluster.
5 votes -
SAML login on feedback.mongodb.com does not work with Google Auth
It shows "SAML Error" and redirects the login page to cloud manager. As a result the login success is never passed to feedback.mongodb.com, it's necessary to login again (on the second attempt, it works)
1 vote -
migration should check actual disk space used by source MongoDB
The easy migration system seems to check the total disk space used on the source machine, and does not discriminate between that disk space used for MongoDB (which will be needed on Atlas) and those used for other applications.
Because the source system contains a lot of logs and a complete copy of our databases in different folders, we have had to configure Atlas to use >2x the actual disk space it'll need.
3 votes -
For resource mongodbatlas_cluster all properties related to provider move to separate block
Current resource
resource "mongodbatlas_cluster" "cluster" { project_id = var.project_id name = var.cluster_name disk_size_gb = var.disk_size_gb num_shards = var.num_shards replication_factor = var.replication_factor auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled mongo_db_major_version = var.mongo_db_major_version //Provider Settings "block" provider_name = var.provider_name provider_disk_iops = var.provider_disk_iops provider_volume_type = var.provider_volume_type provider_instance_size_name = var.provider_instance_size_name provider_region_name = var.provider_region_name provider_backup_enabled = var.provider_backup_enabled }Suggested resource
…resource "mongodbatlas_cluster" "cluster" { project_id = var.project_id name = var.cluster_name disk_size_gb = var.disk_size_gb num_shards = var.num_shards replication_factor = var.replication_factor auto_scaling_disk_gb_enabled = var.auto_scaling_disk_gb_enabled mongo_db_major_version = var.mongo_db_major_version //Provider Settings "block" cluster_provider = { name = var.provider_name disk_iops = var.provider_disk_iops volume_type = var.provider_volume_type instance_size_name = var.provider_instance_size_name region_name = var.provider_region_name backup_enabled = var.provider_backup_enabled3 votes -
Monitoring for WiredTiger data handles
Add process measurements for monitoring WiredTiger data handles.
From Atlas documentation https://docs.atlas.mongodb.com/reference/atlas-limits/#collection-and-index-limits :
While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.
but now there is no way to get this information except
db.serverStatus()5 votes -
Allow threshold on "System Memory: Available" alert condition to be a percentage
In Atlas, it would be ideal if you could specify a percentage of total memory as the threshold for the "System Memory: Available Is..." rather than a literal number value. If it was possible to set this as a percentage, then the alert could be applied to all hosts in a project, rather than having to set hostname conditions and create a separate alert for each cluster.
9 votes -
support external nodes
Allow manual addition of externally-hosted non-voting (hidden) node(s) to an Atlas cluster. This would permit:
- compliance with data management rules that require a copy of all data to be kept in-house (ie outside cloud)
- easier migration out of Atlas for real-time DB use cases where a stop/backup/restore is not a feasible route3 votes -
Ability to block sending of Alert Close Notification
We have set up alerts and have noticed that when a condition is back to normal, there is another alert generated acknowledging its closed. Is there a way we can manage this (like disable or block it for some alerts)?
2 votes -
Atlas auto-scaling configurable alerts
It would be useful, and contribute to a complete alert experience, to have auto-scaling event alerts configurable in project alerts. Users should be able to send alerts to their target system of choice, and prevent numerous alerts to specific users.
Currently auto-scaling alerts are only emails to project members (as per the following https://docs.atlas.mongodb.com/cluster-autoscaling/#acknowledge-auto-scaling-events).
Examples of configurable alerts:
- Scale-up unsuccessful due to max cluster-tier too low -> change email recipient of these alerts
- Scale-up event has occurred -> send alert via SMS and Slack.63 votes -
High resolution monitoring and alerting for WT dirty cache ratio, eviction workloads and checkpoints.
Implement better monitoring and alerting for WT dirty cache ratio. This should include sub-minute resolution and support an understanding of eviction workload as well as performance impact of checkpoints under heavy write workloads.
2 votes -
track collection size
I would like to be able to track the size of our collections (i.e. # of records, total disk size) over time. It would be ideal if there was an automated way to do this with Atlas, perhaps with Charts ?
5 votes
- Don't see your idea?