Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
455 results found
-
Fix the broken link from the attached image
Fix the broken link pointed out in the attached image.
1 vote -
Support Linode as a cloud service
Linode is a widely used cloud provider between developers that do not like the outrageous interface & costs of the main providers (Google, Atlas, AWS). Linode has free in-network bandwidth as well, making for private connections to be much cheaper.
3 votes -
Deletion Protection
Customer suggested protection from Cluster deletion similar to AWS RDS
https://www.amazonaws.cn/en/new/2018/amazon-rds-now-provides-database-deletion-protection/
TL;DR - a notification when a user tries to delete a cluster, that "this cluster is protected, if you need to delete please visit the console to enable deletion"
This would be a critical piece of functionality where roles/permissions are not sufficient.
6 votes -
Atlas should allow deployments of non-voting members on region for tiebreaking purposes
No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.
This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.
1 vote -
Ability to read the logs in old format
there should be option to download log files as native format, as we need to download multiple tools to get it to normal!!
1 vote -
Feature Request: DNS record per zone for global cluster
Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.
This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…
1 vote -
Atlas Screen Navigation
In both Atlas & Ops Manager, on screen navigation is not good. When I click an icon or item, the screen shows different layouts for each click.
For example, if I want to see Billing info, I have to click little 'mongo logo' icon, then Bill menu appears.
Then if I click All Cluster item, the Bill menu disappears and left navigation/ menu also disappear.
I have click multiple times, different icon, or menu to get what we want.
There is no consistency in the screen appearance when we click an 'icon or menu'. Each click shows different screens.
Same…
1 vote -
Setting up the New MFA/Adding a disabled user back to project
The whole process of setting up the new 2FA or MFA is very tiring. It should be simplified with the roles who can add new members and set up the method for new team members.
Chat was helpful but it's not easy to follow up for every team person.Also for a change in phone or lost device should have some details to get ahead for the user to access the db, after authentication.
As authenticator app gets lost with the device, it should not end in loop where it keep asking for Admin password.
1 vote -
Hide Intercom button/window
The intercom window frequently pops up and blocks information when I log in to Atlas or refresh a page. This is annoying and it should never open automatically (or at least I should have an option to make it never open automatically)
1 vote -
1 vote
-
1 vote
-
docsexamined
in profile tab, there are only keysexamined, nreturned we can see.
If we have "docsexamined" , it would be good to check whether the queries are well tuned or not at first glance.1 vote -
Derisk cluster changes that cause restarts
Problem statement:
Some configuration changes cause rolling restarts of the cluster (e.g. audit filter, enabling x509 auth). It is not immediately obvious which changes will cause restarts and for a big cluster, this is a huge hit to performance due to cold caches.Ideas:
1. Block planner changes which would cause restarts until maintenance window (maybe with an opt-in for this, + notification that the config change is blocked)
2. Throttle replica set restarts, allowing time for the cache to be warmed on secondaries (would require mirrored reads in 4.4 to be effective)
3. Properly document what changes will cause…2 votes -
Delete one (last)endpoint deletes private endpoint service
If no further endpoint is associated with Private endpoint service, making a call to api resource https://docs.atlas.mongodb.com/reference/api/private-endpoints-endpoint-delete-one/ will delete the endpoint as well as service.
1 vote -
Add Atlas users to existing teams even though the Atlas user is still pending invite
Currently when we send invite emails for the organization we have to wait for the users to accept the invite before we are able to configure project level permissions. This often creates confusion and bad user experience; when users first sign in they are anticipating to see their projects but instead they see nothing until configuration is finalized.
Please make it possible to add users to teams which are still pending invite acceptance so the user experience is more seamless and less confusing.
7 votes -
Add date added and date updated to Network Access IP table
The network access table should have a way to see the date an IP was added and if/when is was last updated. This will give better insight and control over company users add and maintain their IPs when only whitelisted access is allowed.
1 vote -
Transactions support for Merge operation in aggregation pipeline
Hi Team,
can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictionsWe have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.
The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.
thank you
4 votes -
Unpause Cluster for X Duration
Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.
Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours
Current Atlas Control Plane: "Pause Cluster"
Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"
This is similar to how customers can create temporary database users that are only active for X number of hours.…
1 vote -
rolling maintenance for replicasets
Similar to the process outlined in this doc for index builds
https://docs.mongodb.com/manual/tutorial/build-indexes-on-replica-sets/
It would be beneficial if the same process can be allowed in Atlas for running database maintenance processes such as dropping large databases that are no longer needed or to purge out old data using this method without impacting the primary.
Bulk Data can be purge out easier using the rolling maintenance method for example when implementing TTL index. If prior to implementing TTL index there is a lot of data to purge out that meets the TTL index criteria, this can be done prior to creating the…
1 vote -
Add a simple log filter in the Atlas log API call
In the Atlas log API call, add a new Request Query Parameter which allow people to set a phase or string, to avoid downloading log lines including this phase or string.
So people don't have to download large quantity of log messages that they don't need.
For example the the NETWORK log message between replica-set members.
3 votes
- Don't see your idea?