Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Zabbix integration
It would be interesting, Atlas could also be monitored via SNMP, in order to be monitored by Zabbix.
Many companies have their own CommandCenter, where they centralize monitoring in a single tool.
1 vote -
configure IP whitelisting on database user level
enable the user creation to have the following option
authenticationRestrictions: [
{
clientSource: ["<IP>" | "<CIDR range>", ...],
serverAddress: ["<IP>" | "<CIDR range>", ...]
},
...
],15 votes -
auto scaling on IOPS like the storage autoscaling
the IOPS can be auto scale up when it reach the maximum and stay at the maximum level for more than 1 hour
5 votes -
Disk queue length metric
Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).
Would it be possible to add this metric to Atlas monitoring?
12 votes -
Support optional fallback to source cluster after cutover in Live Migration
Live Migrate allows for migrations from non-Atlas clusters into Atlas by syncing data from the source to the Atlas destination, and then cutting over the application to direct workload to the destination.
It's possible to test the application on the destination before cutover, but after cutover, there's no way to sync data in reverse in case unforeseen issues arise and it's necessary to fall back to the source (or another) cluster again.
Having a "fallback sync" option could help with this.
8 votes -
Cluster version overview on Owner level
We have partially older mongoDB versions running on our clusters. We get notified about it by EOL mails from mongoDB. However, as an org owner, I cannot see which clusters are affected. This makes it extremely time consuming for me to identify the relevant contacts per cluster. Our org structure entails self-sufficient teams with independent accountability of the mongoDB clusters. There is no central contact person.
It would be desirable to be able to call an overview of all clusters with the respective installed version in the GUI with owner rights.
2 votes -
snapshot
Show Snapshot progress (from provider snapshots) and possibly an ETA in Atlas UI
5 votes -
Ability to apply the same settings to multiple projects
As described in support case #00739901, we have exceeded the 50 limit of clusters in our production project.
We are going to have a lot of new clusters in the coming year, and they all need to be in the production environment.
There should be a way either to add more clusters to one project or to share the same settings between multiple production projects for growing customers of MongoDB like us.
2 votes -
Determine index's impact score before creating
Currently in Atlas there is no way to test an index's performance before creation. Performance advisor provides an index impact score for suggested indexes. Requesting a feature where you can upload a proposed index and performance advisor can determine the index's impact score. This would help test an index performance before committing to a build
5 votes -
Teams API should show the projects the team is a member of
Right now the API to retrieve information of a team ( either by ID or by Name ) only gives the name, the id and a link of the specific team.
I would like to see to what projects a team has access with which permissions ( as you can see via the atlas console ).
This would help a lot with automating access management
2 votes -
take snapshots off of the activity tab for maintenance.
When I select the maintenance filter on the activity feed all the daily snapshots show up. I feel like there should be a backup screen that shows all the snapshots on the activity feed. this would make the maintenance screen more precise and relevant.
. The maintenance screen should only show what software maintenance goes on the atlas clusters. This should also include all the release fixes. so, I do not have to go to your
https://docs.mongodb.com/manual/release-notes/software releases page.It is very hard to tell what maintenance will be applied in a given time period. We have timeframes to apply…
1 vote -
ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps
In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances.
As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it.
Please provide a way to simply ignore the notimeout option, instead of breaking its connection.
Thanks!
1 vote -
Don't cut alert names
This is very hard to figure out what these alert mean, I have to go to the documentation and match them somehow, but it also looks like the documentation is not up to date.
3 votes -
Atlas Capacity Check for Cluster Creation or Changes
When creating large new clusters sometimes Atlas does not have enough resources available from the cloud provider. When this happens a restore or cluster change fails without reporting what the actual issue is.
Solution: Verify available capacity and issue a warning or error if it is possible that the operation will fail & recommend opening a support ticket (or have a dialog to automatically do so listing the details)
7 votes -
Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
14 votes -
Provide callback method for API calls to avoid polling
Provide some callback method (webhook URL, push notification, etc) that an API call can use to indicate it's done. That way the user doesn't have to sit and poll endlessly.
Some examples of where this would help:
- After creating a restore job, waiting for the snapshot download URL to be ready.
- After modifying the automationConfig, waiting for all agents to report that they're in goal state.
3 votes -
Scaling cluster connections independent of cluster size/tier
Currently whenever you want to increase Atlas cluster connections, you have to scale up Cluster Tiers. When an application doesn't require additional disk storage but only additional connections the additional cost is difficult to justify.
18 votes -
SNMP
Enable SNMP setup on Atlas Resources.
1 vote -
Need static private ip for cluster nodes
Please see details in https://support.mongodb.com/case/00682480
3 votes -
Include cluster labels with Invoices API response.
Using the Invoices API to aggregate cluster costs by label involves cross-referencing the Cluster API. Including cluster label information as part of the Invoices response would eliminate this extra step.
5 votes
- Don't see your idea?