Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Performance Advisor Case Insensitive Queries and $lookup Recommendations - Include Relevant Queries
Currently the Performance Advisor features suggestions for two distinct situations:
* Queries Using regex With Case Insensitivity.
* Queries Using $lookup.Currently the query or queries that triggered the suggestions are not shared within the Performance Advisor message which requires an extra effort in finding them either in the MongoDB Logs or using the Performance Advisor. As such, it would be useful to attach the relevant query or queries that triggered the suggestions to the Performance Advisor details.
2 votes -
Provide local ssd instances in GCP
In terms of throughput it would be great to be able to configure an Atlas cluster based on local ssd / nvme GCP VM instances.
2 votes -
OCSP stapling support for Atlas Clusters
What is the problem that needs to be solved? As a user (MongoDB Driver) you'd like to check revocation status of X.509 certificate via TLS Certificate Status Request extension (also known as OCSP stapling) instead of doing outgoing HTTP connection to OCSP endpoint from a user (MongoDB Driver) side.
Why is it a problem? (the pain) [MongoDB Server v. 4.4.X introduces OCSP stapling functionality](https://docs.mongodb.com/manual/release-notes/4.4/index.html#ocsp), however OCSP stapling is not enabled on Atlas Clusters with MongoDB Server v. 4.4.X.
4 votes -
Atlas UI to manage and spin up on-prem clusters
CSM submitting on behalf of customer
Spinning up new clusters for on-prem deployments through the Atlas UI would save time and efforts for DBAs managing MongoDB deployments
2 votes -
make empty teams possible
It is currently not possible to create empty teams of remove all users from teams.
We would like to arrange our access management through teams. For our production environment we want a 'read only' and an 'admin' team. The admin team should be empty at all times, except in the case of incidents where we want to add specific users to the admin team to be able to solve the incident.4 votes -
Include Human-Friendly Cluster Names in Alert Notifications
Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).
7 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.
1 vote -
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.
2 votes -
Project teams
Hello,
I think it would be a good idea to have team management at project level.
We have many projects and members in our Atlas account.
I'm a organization owner. The people in my organization use the Altas service. I create
a project for them and give my colleagues the project owner authorizations.Project owners can invite other members. This is good. But it's a little inconsistent that
they are not able to create groups or teams within their projects They have to manage the permissions for each member separately.We can't use organization teams, because they are located at…
28 votes -
Provide an interface that can stream logs directly to Splunk.
I'm trying to get logs from MongoDB Atlas to Splunk, and there's currently no native interface to do it, so instead of streaming to Splunk directly, I'm having to execute https calls in intervals, unzip them and then ship them to Splunk. Many products have interfaces to stream to Splunk directly, and it would certainly be handy in this situation.
10 votes -
2 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_enabled2 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()2 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 -
Add Test Failover permissions to the Project Cluster Manager role
Add Test Failover permissions to the Project Cluster Manager role.
Use Case:
We'd like to have folks with this permission without also allowing them to modify Project membership and all the other permissions that come with being an Owner.4 votes -
Create distinct indexes for Analytics nodes
To effectively use Workload Isolation, it is desirable to have different indexes on the operational cluster nodes than the indexes used to support analytics and reporting query patterns. It would be powerful for Atlas to enable different indexes on Analytics nodes.
8 votes -
Leverage atlas search indexes in find and count operations
Currently the documentation wasn't outright clear that Atlas search indexes can only be leveraged through Aggregation operation. It will be great if we can leverage them in find and count operations as well.
1 vote -
1 vote
-
Provide offending query shape in Query Targeting alert notifications
It would be ideal if the alert notifications for Query Targeting ratio alerts included a reference to the query shape that caused the alert to fire. This would assist customers in locating the exact query/queries with poor targeting ratios so that they can be optimized in a more expeditious manner.
2 votes
- Don't see your idea?