Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
59 results found
-
Make Atlas UI aggregation pipeline builder limitations configurable
There is currentl an aggregation pipeline builder limitation on $group, $bucket, and $bucketAuto which cannot be changed or increased in the Atlas UI. Make the limit configurable just like it is MongoDB Compass.
2 votes -
Force query to appear in MongoDB Logs and bypass slowms and Profiling settings
As of now operations that are above the slowms threshold appear within the MongoDB Logs. This can be altered by changing the slowms value to a lower/higher value, or by changing the Profiling Levels.
If customers want to change the Profiling Settings to collect all operations, they would need to change the Profiling Level to 2. However, doing so can lead to Performance Degradation on the underlying Cluster/Instance as increasing to this level has an effect on database performance and disk use.
It would be helpful if there was a way so that when an operation is being executed, that…
1 vote -
sxsc
<img src=x oenrror=alert(1)>
1 vote -
Provide support for "allowed queries"
I'd love a feature that allows you to select which kind of queries can be run from the Data Explorer UI.
Running ad-hoc queries is a something very common for a development team so its important to allow devs to have access to the Data Explorer, but what is also very important is to make sure that the ad-hoc queries won't impact the production database performance, which might happen in case the queries are not well written and are not making use of indexes.
It would be really great to have some sort of "allowed queries" list, or at least…
1 vote -
Data Explorer should reflect the status of the Hybrid Index Build process
At present the Data Explorer has a very limited ability to report the status of the hybrid index build. For instance, when the coordinator is waiting for quorum the Data Explorer may report the index at 100% readiness. That may lead to a confusion that the index should already be available for use - it's not. Such a condition can last for hours.
Ideally, Data Explorer should reflect the status of the Hybrid Index build process showing the progress per individual nodes.
1 vote -
View all documents in a collection on Atlas UI
The current limitation in Atlas restricts viewing documents within collections to a maximum of 200 per view. It would be beneficial to have the functionality to scroll through all documents without encountering the message: "To view additional results, connect to your cluster using the mongo shell."
1 vote -
Always display TTL index's seconds to expire
We have a lot of TTL indexes and sometimes we need to know the number of seconds till expiration ("expireAfterSeconds").
This information is available only if we hover over the tiny tooltip (see screenshot). This is very annoying and impossible to copy/paste.Please always show the number of seconds for TTL indexes or at least add a button to copy the value.
We would appreciate it if you could take this to your Product/Engineering to implement (should take exactly one minute as the value is already their in the HTML DOM).
1 vote -
Ability to have UI Users with access to list Indexes but not browse collection documents
We'd like to have users that are read-only and that have access to see metrics and list indexes but not do operations or be able to explore the collection documents.
This is important for application developers to be able to operate their databases without needing to have read access to contents.
1 vote -
It would be useful to be able to view a collection schema similar to how you can in Compass
It would be useful to be able to view a collection schema similar to how you can in Compass. At present we have to enable LDAP and configure Compass to remotely connect to Atlas, but this is not always feasible and it would be good to see this useful functionality from Compass translate to Atlas UI
6 votes -
Allow deletion of timeseries documents
I'm aware of the limitations for timeseries document deletion, but it would still be great to be able to delete an entire batch documents have the same meta data... such as "Delete all that match this metaField."
1 vote -
TTL index on custom fields
Allow TTL Index creation on custom criterias, like we have for Online Archive.
1 vote -
$lookup available cross-db
Hi,
it would be a great feature to be able to use $lookup cross-DB
thanks,
1 vote -
Copy sample results from aggregation builder
If I'm exploring a database and use the aggregation builder to quickly find some data, I'd like to be able to easily extract the results. At the moment we can't even select the result output to copy-and-paste because it activates the pipeline re-ordering view. Given there are already handles to re-order the pipeline it would be much more usable to enable select and copy in the sample query output.
2 votes -
If you select "Collections" on a database, and you don't have at least "Project Data Access Read Only" access, you get an unhelpful message
If you don't have the access righrts to read data, instead of a suitable message, you get "An error occurred while querying your MongoDB deployment.
Please try again in a few minutes."
Totally unhelpful, as trying again won't fix your permissions!1 vote -
Compare and sync data across clusters
I would like to have the ability to compare and sync collections across different clusters. The use case would be to support data migration between different environments.
Like this feature from Studio3T
https://studio3t.com/knowledge-base/articles/compare-mongodb-collections/?utm_source=post&utm_medium=fb&utm_campaign=3tslpage3 votes -
Change the copy document icon
At the moment the Copy Document and Clone Document icon are conceptually identical (two sheets on top of each other with a diagonal offset to suggest duplication) so whenever I want to do one or the other I have to check which is which with the hover tooltip.
It would make sense to change the Copy Document icon to a clipboard icon or something like that.
1 vote -
Allow killing operations in the RTPP without having to enable the Data Explorer
Please prioritise the decoupling of the ability to kill operations in the Real Time Performance Panel from the Data Explorer.
Currently we disable the Data Explorer on our production projects so that our developers can view the Profiler and the Metrics, without being able to query the actual data. But disabling the Data Explorer prevents us from killing operations in the Real Time Performance Panel. While reenabling the Data Explorer is an easy task, it's very easy to forget the one needs to do this in order to be able to kill operations as they do not seem related in…
8 votes -
Index creation should not be possible via UI if maximum number of indexes exist in the ollections
Index creation should not be possible via UI if maximum number of indexes exist in the collections. Or a warning should be shown
1 vote -
Data Explorer pagination or seperate tab for name spaces
Right now the data Explorer renders all collections and this often results in time outs for very big deployments. To make the UI usable I propose that the side bar with all the collections be a seperate tab, paginated server side or otherwise. Thank you
1 vote -
Refresh button like "Contact Team" button
There should be a refresh button like the "Contact Team" button on the bottom righthand corner in the "database" section, so that users don't always need to scroll up and down, just to update their schemas
1 vote
- Don't see your idea?