Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1263 results found
-
Save common collection filter/query
As an ex-mLab customer, I used to really enjoy having common queries on collections saved, like "find a customer", "list latest X" etc Is a dropdown with a name and the query, so when you select it you can quickly perform the search.
5 votes -
Recently resumed clusters must remain running for 60 minutes
At the moment when you try to pause a recently resumed cluster you get the following message;"Recently resumed clusters must remain running for 60 minutes to process all queued maintenance".
Obviously this requires me to check back in Atlas UI in an hour or so just to pause the cluster. Instead would be good for UI to schedule a Pause to be executed as soon as it's possible.
9 votes -
mongorestore
As per the mongorestore
- to preserve UUID must use drop collection
- if the collection is dropped then it will affect user/login access.
This cascading effect makes it's impractical to use. We wanted to use mongorestore UUID as an idempotent operation, in case halfway things go wrong and have to start again then it's useful to preserve UUID.
Also, in the mongorestore there should be an option to ignore/skip index creation, we were trying to bring data from the legacy app without indexes. It seems that's not possible at this moment.
1 vote -
default country
When I tried to register for Atlas webinar, host country selection was mandatory. By default it displays the USA first value in the dropdown and have to scroll down to select another country. It would be a good user experience if on the registration page visitor/user's country is identified and by default selected, this will prevent unnecessary scrolling.
Also, a very annoying thing is that in order to register for the webinar have to agree to subscription. Subscription to email and other notification should be optional, otherwise, it's a bit dodgy tactic more suitable to some social media companies who…
1 vote -
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".6 votes -
[Atlas] Enforce password policy for DB access
Currently is not possible to enforce any kind of password policy via Atlas UI.
Would be nice to let user define an expiration time and password policy that user should meet.14 votes -
Show driver/application/user metadata in Query Profiler query summaries
It would be helpful if the Query Profiler showed the driver and user metadata associated with the connection over which a particular query was run.
After clicking on a particular plotted operation in the Query Profiler, the sidebar pops up and shows execution statistics and structure of the plotted op, but doesn't show anything about the driver/application/user that issued the command.
This query summary would be more actionable if the driver, driver version, application name, and user were also displayed in the query sidebar (these details may be recorded in a separate log entry from the command itself).
This information…
14 votes -
Sort IP Whitelists in Atlas
Enable sorting and filtering on the whitelist management screen.
There is no logical order to the list of ips.3 votes -
Privilege advisor capability
It would be incredibly helpful to have some sort of capability that allows users within the Atlas portal to be able to see what privileges are needed to perform various actions. For example, we have users that are not able to configure alerts, or other users that are not able to add users to a project. It isn't always clear what privileges are needed in order to give users those capabilities. Either some sort of tool would be helpful, or very clear documentation on privileges that are needed for each capability within Atlas.
1 vote -
Shorter Temporary Durations for Network Access whitelist
Hello,
it would be nice if you could add options for temporary whitelist entries that are shorter than 6 hours. Often in our Team we find ourselves just needing to whitelist an ip for a short amount of time to look up some documents or fix a bug.
For that case it would be nice to have additional shorter options like 3h, 1h, 30m, 15m.Thanks for taking a look
4 votes -
Live Migrate through VPC peering connections
Many teams put their databases in subnets without internet access or with just a NAT gateway. It would be great if the Live Migrate could be use through already configured VPC peering connections.
5 votes -
Autoscaling - CPU/ Memory Utilization duration monitor - Minutes
Hi, Currently there is no option to initiate auto scaling during heavy workload/ requests comes and the cpu/ memory utilization is 75% for the even within
- 5 minutes
- 15 minutes
- 30 minutes
- 45 minutesThe system has to wait for 1 hour to autoscale to next tier.This one of the concerns for the heavy workload applications.
Idea:
Add a custom duration option as
- minutes also while monitoring the cpu / memory utilization
Example : When a CPU / Memory utilization is above 75% for the past 15 minutes , move the cluster to the next tier…
28 votes -
Add horizontal scroll bar to metrics tab
I can't see metrics for all of my nodes while in the metrics tabs unless I make the window very large. It would be much easier to analyze the health of my cluster if I could review metrics for all the nodes by scrolling horizontally, rather than having to switch between a grouping of nodes.
5 votes -
Show node region on the metrics tab
It would be really useful if the Atlas Metrics tab showed the node name and geographic location similar to how the Cluster Overview tab shows the node's region. In this use case, we have nodes located all over the world, so its useful to know where a node is located when reviewing it's metrics.
2 votes -
Annual Snapshot Retention Policy Option
I have customers that would like the ability to retain annual snapshots going back 5 or so years for compliance reasons. Currently, you can do this with monthly snapshots by retaining for 5*12 months, but then you have to store all the monthly snapshots in between.
23 votes -
Define via UI time windows on which the cluster is paused
Test environment are usually paused during the night and the weekends. Currently the only way to do that is to automatise a RestAPI call or call mongocli automatically (e.g. via crontab)
Would be nice to allow to define a time windows on which the cluster stays pause via UI9 votes -
Find filter autofill list should be Collection dependant
The Clusters > Collections > Find option offers an auto-fill drop-down of previous entries, which is super helpful. However, it seems to offer suggestions from previous queries of all the Collections. This is not helpful, since Document keys tend not to overlap across Collections, so it would be even more helpful if the drop-down only listed previous queries from the selected Collection.
1 vote -
'Find' should offer a JSON mode
Under Atlas > Clusters > Collections I can select a Collection and use the 'Find' option to quickly seek and edit a Document. At the moment the UI display is like JSON, but has stripped out the brackets, which makes copying the data awkward.
Feature 1: The find display UI should offer a JSON mode, so the the Document, or parts of it can be copied in JSON format.
If I select the Edit option, the editing UI is 'intelligent', in that it forces JSON compliance via the various options. However, this makes pasting in new data impossible.
Feature 2:…
3 votes -
Use 24-hour time format in Metrics date pickers
Timestamps in Metrics plots are displayed in 24-hour time format, but the date/time filter inputs require 12-hour time (using am/pm).
12-hour time is not widely used around the world, and it is cumbersome to use in the date pickers especially give that other parts of the UI use 24-hour time.
Can we update these date pickers to use 24-hour time instead?
5 votes -
Migrate users and roles with cluster data
It would be great to be able to transfer users with their credentials and permissions from our on-premises deployment to Atlas during migration to avoid having to recreate those users using the Atlas interface or API.
21 votes
- Don't see your idea?