Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1257 results found
-
Add storage class configuration option to Cloud Backup snapshot Export to S3
Setting the desired value for
x-amz-storage-classheader for the S3 PUT Object for snapshot export so that exported snapshots can be put directly to the desired storage class without any custom lifecycle rules and wait time on S3 side.2 votes -
Introduce Serverless for AWS Frankfurt region
Company policy (speaking for a customer) requires data to be deployed in Frankfurt. Serverless would be very convenient to reduce pause/resume and scale-up times.
1 vote -
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.
6 votes -
Investigation Buckets (dropdown menu) to enable predefined set of MongoDB & Hardware Metrics to investigate certain Data Layer SLAs
We have many metrics under "MongoDB Metrics" & "Hardware Metrics". User will have a good idea which metrics to enable while troubleshooting certain requirements.
E.g. User is investigating current lags in the data Layer. User has to select all the metrics that would help them get the data they are looking.
We can help the customer bit more by provide buckets like.
Options ( select one )
1. Investigate Lags
2. Investigate IOPS
3. Investigate Replication
4. Investigate Search Index
... and etc..This will pre-select certain metrics from list of Mongodb & Hardware metrics which will give them all…
1 vote -
Export mongo dump to AWS S3 Bucket
It would be good to have the ability to export mongodump's and mongoexport's files directly from Atlas to the S3 bucket. This kind of feature exists for backup snapshots. In our particular case, we want to delete a cluster but before that just export all data to S3. The backup snapshot takes about 1.6TB and mobgodump's file is around 650Gb. Of course, I can take a dump to my local machine and upload it to the S3 bucket. The problem is that my SSD is only 512GB on my laptop so it is impossible to export a full dump.
Thank…1 vote -
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)…
26 votes -
Need a Instance with unlimted storage .
We are seeking an instance with 2 vCPUs, 4 GB of memory, and a storage capacity of 500 GB.While we understand that the available M20 instance type supports the desired vCPU and memory specifications, we noticed that the maximum storage capacity for M20 instances is limited to 256 GB. Unfortunately, this falls short of our project's storage needs.
Considering this, we kindly request assistance in identifying an alternative instance type or solution that can meet our requirements for 2 vCPUs, 4 GB of memory, and a larger storage capacity of 500 GB. We would appreciate your guidance in selecting an…1 vote -
Permit downloading of serverless instance snapshots.
Currently this is not supported. The consequence is that there is no way to restore just a single database or collection from a snapshot. This obviously greatly reduces the value of snapshots.
2 votes -
Atlas metrics granularity after 48 hours
For metrics older than 48 hours, the data is presented in 1-hour intervals. This level of granularity is often too coarse for a thorough examination of past events and trends. Such a broad view can obscure smaller yet significant details critical for understanding and resolving performance issues that occurred in the past.
Suggested Improvement:
having a smaller granularity value for historical metrics beyond the 48-hour timeframe. Providing data in smaller intervals would greatly enhance our ability to conduct in-depth analyses and diagnose past performance issues accurately. This would be particularly beneficial for conducting detailed investigations of historical data and identifying…
4 votes -
Reference existing third party integration in alert configuration notifications
Provide a mechanism that enables referencing an existing atlas third party integration when using the alert configuration resource to create or update a third party notification.
This is useful when a third party integration is imported or accessed through a data source, meaning the api token is not available. An example of this would be Slack integration as it has to be created through the Atlas UI using OAuth2, so the api token cannot be accessed in the terraform configuration.More details in: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1074
1 vote -
Support europe-west4 in GCP
As the title says really, we want to make extensive use of serverless but can't do so until you support west4. You support west4 on dedicated instances, but support say there are no plans for west4 on serverless, which is disappointing.
1 vote -
Serverless queries could return their RPU & WPU along with the results
Currently it's impossible to control the serverless spending. By being able to log and alert on queries resulting in huge RPU/WPU usage during development it would be safer to release changes without billing surprises
1 vote -
Modify MongoDB Autoscaling Logic for CPU Usage Interval
Currently, the autoscaling feature in MongoDB is configured to initiate scaling based on the last 1-hour CPU usage. The trigger for autoscaling is set at 75% CPU usage within this hourly interval. However, there is a requirement to adjust this logic to a more granular level.
Request:
The request is to modify the autoscaling logic in MongoDB to consider the last 30 minutes of CPU usage instead of the current 1-hour interval. Specifically, scaling should be triggered if the CPU usage exceeds 75% within the last 30 minutes.
1 vote -
Sync Atlas alert configurations between projects.
Since we can export all Alert configurations from a project, add the ability to sync alerts on all the projects to be consistent with notifications/alerts.
Alerts can be created individually but not in bulk. Please enhance the Mongo Atlas API for the following functionalities:
- The ability to sync all alerts from one project to another.
Thank you
1 vote -
Specifying who receives notifications for auto-scaling events
Having ability to manage wich roles receive auto-scaling notifications when a cluster scales up or down.
Now this is limited to Project Owner but this feature will be helpfull to manage notifications to inform other Team Members wich doesn't have to get all permissions related to Project Owner.
1 vote -
Support for VPC Lattice
Additionally to the existing VPC PrivateLink Endpoint method to have connectivity it would be great if I could integrate a MongoDB Atlas project via a VPC Lattice service and share that one with customer accounts on AWS. - Red Bull Media House
2 votes -
1 vote
-
Ability to schedule "Hedged read" Turn on/off
Customer experienced read latency during maintenance after sharding.
Our guidance is to turn on "Hedged read" option.
So the customer need to turn on/off "Hedged read" before/after maintenance, because turning on "hedged read" increase CPU usage that means server cost increasing.Currently "hedged read" on/off can be done by technical support from MongoDB but this feature is needed for operational efficiency and reducing human error.
8 votes -
On-Demand Pricing
I have been an enthusiastic MongoDB user for a couple of years now. My business is very small and the utilization of the database is very irregular. For example, I only have a higher workload on one day of the week and on most other days I only have a load in the morning and often nothing at all at night and at weekends. That's why the smallest available plan that can also be used in production (M30) is actually too expensive for me. A pay-per-use pricing concept would be ideal and I'm not sure whether this would be possible…
1 vote -
add cluster manager email
Hi,
It would be nice to be able to assign a cluster manager email / contact per cluster and not per project. We have different team members managing different clusters within each of our projects and it would be great if we could alert them specifically on specific events in a cluster (like new index suggestions, disk increase, etc.)2 votes
- Don't see your idea?