Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1293 results found
-
Option to take a Cloud Backup snapshot on destination cluster before restoring if Cloud Backup is enabled on it
An option should be provided to allow a user to take a snapshot of the destination cluster of a Cloud Backup restore before the restore is performed so that they can easily "revert" the restore if they need to (by just requesting a restore using the snapshot that was taken just prior).
It's possible to be in a situation where you've selected an incorrect snapshot for restoring or that you'd supplied the incorrect cluster for the snapshot to occur (this is less likely to happen in the UI than it is to happen programmatically via the API). Taking a snapshot…
1 vote -
Allow transactionLifetimeLimitSeconds to be modified from Atlas
We need to be increasing the default value of transactionLifetimeLimitSeconds to larger numbers (usually 300 instead of default 60). Considering number of clusters we running / we are going to be spinning up in the future its cumbersome to keep requesting this change from support. Instead please allow us to set or modify this from the Atlas GUI.
1 vote -
Include Username in Profile page
The profile page would be more use if the listing included the username so you could work out which application was making the queries.
1 vote -
Provide insight to slow queries on shared instances (like M5)
Currently, features to give insight to slow/optimisable queries are only supported on non-shared instances (i.e. M10+). Would like to see this for shared instances too.
On a side note, this was possible in the cheaper mlab.com setup, which was forced into Atlas.
1 vote -
Ideally migration of terraform state should be handled or provide a tool for migrating state
Hello,
We initially rolled out all our clusters with mongo atlas terraform provider version 0.7.0. Since we hadn't pinned the version, we started seeing warning listed below in the terraform plan.Updating as indicated based on the warning means, a deletion and recreation of the private endpoint/link related resources which will lead to downtime as the cluster will be inaccessible while the private endpoint/link is being recreated.
Ideally migration of terraform state should be handled or provide a tool for migrating state so the resource can be migrated without recreation.
============================================
There are warnings related to your configuration. If no…
1 vote -
Correct DNS lookup with cross-region peering connection
A cross-region peering connection, say from an Atlas cluster in us-east-1 to some application running in eu-west-1, should allow the application to connect to the Atlas cluster through the peering connection. However, the DNS names of the cluster, e.g. my-cluster-shard-00-00.abx.mongodb.net, resolve to the public IP address of the cluster's node when looked up in eu-west-1. As a result, the application doesn't route the connection through the peering connection but rather tries to route it through the public Internet.
The solution is to manually find the private IP of each mongo node, and add an entry in /etc/hosts for each. This…
1 vote -
Number of times particular index used in last 24 hours.
It is really helpful to get use of indexes in numbers in last 24 hours to eastimate the use of particular index.
1 vote -
code
can you make it so that you can connect from mongodb like you would in mongoose
1 vote -
Include security group and tag for privateLink setup
On the Private Endpoint (and VPC Peering) setup screen in Atlas, present options to:
- include or modify "security group"
- attach a "tag = name"
That way when user has the AWS CLI command generated, it includes security & tag
1 vote -
if we had option for diabling javascript execution on database we would have to no worry about it
javascript excuiton can be used for harm and mass deletion data. İf we had no javascript execution we would be safer.
1 vote -
Change write concern on the Atlas Clusters
Atlas does not currently allow to change the default write concern at the cluster level.
It it necessary to have a possibility to change it in order to avoid or minimize rollbackfiles during failover.
1 vote -
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 -
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.
1 vote -
Show hardware stats like CPU, System Memory in Metrics single-node view
Currently, some hardware metrics charts like Normalized System CPU are only available in Metrics when viewing the replica set (multiple nodes).
But if you click on one node to see metrics for that server alone, the hardware metrics do not appear in the available charts.
This is confusing -- it'd be helpful if the same metrics plots, including hardware metrics, were shown in all Metrics views.
It's possible to remove some nodes from the "replica set" view by unchecking them in the Toggle Members boxes at the top of the screen, but that will now allow you to view charts…
1 vote -
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 -
SNMP
Enable SNMP setup on Atlas Resources.
1 vote -
Kotlin support and Tutorials
Add Tutorials and Native support for Kotlin language. Preferable with ktor as the server
1 vote -
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 -
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
- Don't see your idea?