Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Automatic information when shared cluster is throttled
When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting.
Right now there is no way for a db-owner to see this information, let alone get that information, except for asking support for help.
2 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.
3 votes -
Splunk connector for Atlas
We need a way to easily ingest logs into Splunk. It needs to be all logs - node and web portal activity. Ideally a Splunk connector would be provided but a stop-gap measure would be the ability to configure Atlas to write all logs to an Azure storage account.
Lack of native log ingestion ability may be an Atlas deal killer for us.
9 votes -
pause
An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.
11 votes -
Please bring Atlas to digital ocean PaaS as a first class offering!
Hey there,
I know it's hard for big companies to get along, but I'd love to have a seamless experience for using MongoDB alongside DO's new PaaS offering. Can you all strike a deal please?
2 votes -
Elections bar colors in Metrics should be more vivid
The atlas metrics show node election statuses in colors - red/orange and brown. When there are multiple re-elections in a short period of time, these all merge together making it hard to decipher the order of occurrence - especially the near overlap of orange and brown Having vivid/contrasting colors should make debugging easier.
It would be helpful if some aspect about the x-axis would tell you what status the node was in at a given time. For example: the x-axis is also that color from time X to time Y, and then the node was demoted/down and the axis turns…
18 votes -
Autoscaling improvements
Hi, we have tried BETA of Autoscaling feature and we have some thoughts how to make it better. In its current setup its not really suitable for our production workloads. Here are some thoughts how to make it better:
- Define separate scaling steps
At them moment the scaling step is always 1. Going from M10 -> M20 which is not really suitable for burst loads where going one step up might not be enough. Same goes for rapid scaling down
Example:
Scale range = M10 - M50
Scale step up 4 = (M10 -> M50)
Scale step down 2 =…61 votes - Define separate scaling steps
-
Vault Lock to protect Atlas Cloud Backups
We are currently looking for a solution to secure our Atlas backups.
Something similar to AWS Glacier Vault Lock [1] or a simple grace period before backups are deleted once and for all would be nice.
It would be amazing to protect the Atlas backups from being deleted.
Currently, if one of our Atlas admins was compromised, the damage for the company would be enormously high. So we need to implement measures against the final deletion of our most mission critical data.also mentioned in: [2]
[1] https://aws.amazon.com/de/blogs/security/amazon-glacier-introduces-vault-lock/
[2] https://developer.mongodb.com/community/forums/t/is-there-a-vault-lock-for-atlas-backups/110412 votes -
Monitoring Integration with Splunk
Unlike a connector (https://feedback.mongodb.com/forums/924145-atlas/suggestions/40688308-splunk-connector-for-atlas) it would be useful if Alerts could be sent to Splunk.
6 votes -
Add "scheduled scaling/suspend" option for certain clusters
There should be an option to schedule scale up/down or suspending/resuming at specified time & day.
For example, DEV environments could be auto-suspended at 6pm and resume at 8am on weekdays, and be suspended all weekend.
Production clusters could be scaled down e.g. from M80->M60 every evening and on weekends rather than being suspended completely.
This would help save money but would need to be coordinated with the existing auto-scaling based on load.
This would need to be at the cluster level since sometimes different clusters in a single project could have different workload patterns.
7 votes -
Cluster Termination Protection
It is possible to quickly delete an entire cluster, for example through terraform, if you're not careful.
It would be great to have a "Termination Protection" feature that can only be disabled in the Admin UI and not via the public APIs.
In terraform I could then enable it like so
```
resource "mongodbatlascluster" "mycluster" {
enabledeleteprotection = true
}
```When I would run
terraform destroy
the cluster should not be destroyed and instead the API returns an error saying that the Cluster has Termination Protection enabled. If I want to disable it, I can…17 votes -
Enable AWS EBS Fast Snapshot Restore (FSR) on Atlas
To speed up recovery after restoring from a snapshot or having a node replaced, it would be nice to have the option to use AWS Fast Snapshot Restore
https://aws.amazon.com/blogs/aws/new-amazon-ebs-fast-snapshot-restore-fsr/
This would allow the disk to have full performance as soon as available.
2 votes -
domain names in access whitelist
Allow domain names in whitelist for IP address. (And rename whitelist to allowlist).
I have a server (app) on heroku. It has a domain name. I don't have a dedicated ip address range. But if I could put my domain name in (myapp.herokupapp.com or myapp.com if I get that name from godaddy), then when my server connects, you could do a DNS lookup of the domain names in the whitelist, and allow connection from those. And then, my app, and many others would be more secure. People could also use dynamic dns to support connections from their home computers, more…
1 vote -
Option to configure an on-prem hidden replica set member for an Atlas replica set
As described in https://docs.mongodb.com/manual/tutorial/configure-a-hidden-replica-set-member/, on-prem mongodb deployments allow to configure a hidden replica set members which are good for workloads with different usage patterns from the other members in the replica set. It would be useful to have similar functionality for Atlas replica sets.
In fact, to elaborate, being able to configure an on-prem hidden replica set member for an Atlas replicaset will help in meeting regulatory requirements where organisations are required to host a near real time mirror of data on on-premises.2 votes -
Setup activity feed retention
It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.
1 vote -
Create alarms base on events + Add control policies
Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.
The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...
For example:
- Be able to avoid the use of user scram.
- Be able to avoid using unauthorized IP addresses
- Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal2 votes -
Replay the point-in-time-restore journal for debug/diagnosis
When performing a forensic analysis for the purposes of a restore, in order to determine the appropriate point in time when our data was last "sane", it would be awesome if we could start with a point-in-time restoration, and play the journal forward, e.g. performing a bisect on the data.
2 votes -
Show total disk size and index size used for each cluster prominently so we can upgrade if we need to
Right now, I do this manually. Would be good to see the totals prominently, along with a recommended upgrade/ not next to it, and single click to select the next size.
1 vote -
Enable Removal of a Subset Documents From Online Archive
Hi,
We'd like to have the ability to remove documents from an Online Archive. Mainly based on a date, but possibly other criteria.
Thanks!
4 votesWe’re currently researching the best way to add support for this.
-
Allow instant backup on every type of cluster
Allow to create a backup when we want, on every type of cluster (like we could do with mLab plans)
2 votes
- Don't see your idea?