Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
62 results found
-
Expiration Date on Database Write Access
Just like the Network Access where you can allow an IP address to be used for connection to the database for a short time, I would like that same feature for Database Access write permissions. I would like to temporarily give someone permissions for X hours and after that time period, it reverts back to the original state, such as read-only access. I have to temp give someone permissions during release nights to perform operations.
Example: "This entry is temporary write access will be deleted in 6 hours and reverted back to the original real-only state."
2 votes -
UX Issues with Collections View in Atlas UI
UX on Collections view has some problems which are listed below;
- It takes around 10-20 seconds to load the Collections page, specifically the left panel which lists namespaces.
- Then without any user interaction or feedback, it takes another 10 seconds to focus on the top most available namespace to display details of it on right hand side panel
- Then filtering namespaces with "auth" doesn't make any change in the screen and not giving any feedback neither.
- Then inputting more letters "authen" triggers the filtering however this time it filters namespaces which had nothing to do with…2 votes -
Export results of an aggregation query to csv file
I have created an aggregation pipeline from the aggregation tab of a collection but unable to export the results of that query to a CSV file.
2 votes -
Add UI to describe collections/fields in Atlas and simple validations
Most old SQL databases allow table and column-level descriptions as a core feature. For distributed teams, or agile teams prototyping an app, it would be useful to be able to document/describe fields, expected/allowed values etc straight in the UI.
I'd like a Definitions tab after Find/Indexes in the Collections view where I can indicate BSON type and add a title/description for each field in my schema.
The JSON Schema Validation mechanism could be used as a basis for storing this information, since it already has a properties definition with a description for each field name in a document.
2 votes -
Count
Whenever a query is fed into the filter search box, ensure that the count of the result is also provided somewhere above the result of the query.
2 votes -
Add visual information to indicate if a collection is capped or not.
Right now there is no way to tell through the portal or Compass if a collection is capped or not. It would be helpful if there were some visual indicator in the Data Explorer if a collection is capped and if so what the retention parameters (bytes and max documents) are set to.
2 votes -
MongoDB Query Debugger Assistant
Overview
Introduce an AI-powered query debugger within MongoDB Atlas to help developers identify performance bottlenecks and syntax inefficiencies in real time as they write queries.Problem
MongoDB’s flexibility sometimes leads to overly complex or inefficient queries, especially when aggregation pipelines or indexes are involved. Developers often need to switch contexts between the query editor, documentation, and performance tools like Atlas Profiler.
Proposed Solution
Build a MongoDB Query Debugger Assistant inside Atlas with the following features:
Inline Warnings & Suggestions: As a user types a query, the assistant highlights potential issues (e.g., full collection scan, missing index usage) and suggests alternatives.
…
1 vote -
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 -
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 -
Cache last aggregation query for each collection
For each collection – on the aggregation tab, cache the last query which was run – keep it pre-populated in the textboxes.
It’s so easy to accidentally click away from this page and when you come back, having to start from scratch always takes a bit. Ideally I want to be able to leave this view and come back as though nothing had changed.
1 vote -
$lookup available cross-db
Hi,
it would be a great feature to be able to use $lookup cross-DB
thanks,
1 vote -
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 -
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 -
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
- Don't see your idea?