Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1262 results found
-
Resync progress bar
Our Mongo cluster has had to resync. It would be great to get some kind of time estimate or progress bar to know how far it's got in resyncing so we can let our research team know when the cluster will be ready again.
2 votes -
Increase maximum storage size for M60 servers
Currently the maximum storage size allowed for an M60 tier is 4TB. Our cluster is approaching this size, and we're facing having to shard our data, which we would really prefer not to do.
I understand that the maximum sizes are selected for performance reasons, but not every cluster is the same - ours is doing just fine and not struggling at all at this data size, and we would like to be able to continue to grow over time.
4 votes -
Viewing Collection Pages
Would like the option to view collection pages by 10, 20, 50, 100. Along with ability to move to (<first) (last>). Similar to mLab
6 votes -
More simple scheduled aggregations
When we set up an aggregation in Aggregation Pipeline Builder, we can "Export pipeline to languages"..
I think it would be great to be able to export complete, copy-paste-ready code as a function to be triggered in Atlas Triggers, as a Function, eg. on schedule,
or any other simple way (no-code / low-code) to run aggregations on schedule.1 vote -
Manually replace / restart virtual machine
Allow to replace / restart the underlying virtual machine of a node.
Sometimes this is all that is needed to get a cluster out of an unhealthy state. Currently, only support seem to be able to do this.
3 votes -
Show Index Error on UI
When creating an index on your UI, if the index creation gives an error, the error doesn't show on the UI, for example if you have a field of type string, and have a value longer than 1024 bytes, and try to create a normal index on this field, the UI will tell you the index it's been creating successfully, but when you go to your collection and see your indexes, this will not appear, but when you create it on the MongoDB console, it gives the following error. It would be nice to have this error shown on the…
13 votes -
MongoDB Orphaned Docs Utility
When we upgrade MongoDB there is the possibility that orphaned collections that need to be deleted can prevent the upgrade from completing.
It would make sense for Atlas to include a proactive utility that searched a customers sharded cluster for orphaned docs and gave them the option to clean up the orphaned docs ahead of a major version upgrade.
1 vote -
An API endpoint for Live Migration
When customers have dozens and hundreds of clusters to migrate from on-prem to Atlas, automation is very important and Live Migrate is not supported via API today. Mongomirror is a shell command that can be leveraged for automation but having Live Migrate available as API will be a great enhancement to CD/CI pipeline.
2 votes -
Allow Atlas to send additional metrics to New Relic via integration
This is a request to add some additional metrics to those that are currently sent from Atlas to New Relic when the integration is enabled.
The specific metrics of interest here are:
- Disk Space (%) Used (or Free)
- DB Storage
- Query TargetingHaving pointed out the above metrics specifically, I would also say: the closer that the metrics sent to New Relic via the Atlas integration can resemble those available in the Atlas cluster Metrics page, the better.
6 votes -
Have the ability to configure cache_size
I'd like to see the ability to modify the cache size setting for a given cluster. MongoDB has a straight forward pattern of using 50% of the memory for cache size. However, Atlas has scaled that down to (RAM - 1 GB) / 2. Apparently that was done to allow for extra memory for other Atlas features like BI Connector and Atlas Search. However, we currently aren't using those features, so we're stuck with the lower cache size.
It would be great to have the ability to get the most of our servers instead of being limited based on logic…
3 votes -
Provide Atlas support for "Classic" VNet Peering topology
Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT
12 votes -
Alert for WiredTiger Cache
Hi,
Can you please create an alert for WiredTiger metrics, such as used cache?
We had several cluster instances going over the 5% of used cached (dirty data) and would like to be notified when it happens.
Regards,
SergeiThis is needed in order to determine whether
7 votes -
IO throttling
Atlas should be able to throttle IO in a way that does not allow excessive IO to degrade a node or take a node offline. Current functionality has no defense against a high IO data job other than to allow a node to fail.
1 vote -
Domain Validation should use subdomain rather than domain root
When entering the txt value for validation atlas should use its own subdomain for the verification rather than requiring the domain root which is often populated with spf keys.
Other examples of this implementation are
Github: github-challenge-org.domain.com
Mandrill: mandrill.domainkey.domain.com
Google: google._domainkey.domain.com1 vote -
Display the MongoDB Network Peering Container ID in the console
Instead of forcing use of the API, why not display the MongoDB Network Peering Container ID for the peering connection in use?
1 vote -
Allow bulk changes to alerts - e.g. changing slack channel
Changes alerts is really painful. For one thing, pressing the Enter key doesn't close the dialog and nor does pressing Escape.
This makes it really painful to change something simple like the slack channel used for alerts.
2 votes -
Add editable description to a snapshot
After an incident I may single out a snapshot and decide it is important. At this point I am able to change the retention policy to keep it for a longer time.
It would be useful to also be able to add a note or a description to that snapshot so that I may tell future me why that snapshot was important and what incident it is tied to.
4 votes -
Allow Billing Alerts per Project
Currently, we can configure Atlas to send an alert when the current bill for any project is above a specific amount. It would be great to be able to set alerts for specific projects. This way we could more easily manage budget fors projects and alert project owners.
7 votes -
More detailed update status
It would be amazingly helpful to see more detailed information on recovering nodes. Just knowing that the node is, for example, "81% of the way on initial sync" is much more informational (and lets users know that it isn't stuck) as compared to the node being in "Startup2" recovery.
3 votes -
Support for Azure VNet Gateway Transit
Azure VNet Peering is currently very limited as access is only possible from the VNet that is peered.
Could you please support access from onprem via private network (Express Route or S2S VPN) and Gateway Transit.
Maybe another way to achieve the same could be via "Private Endpoint".5 votes
- Don't see your idea?