Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
A way to enable the Data API via Terraform
I just noticed that MongoDB Data API is no longer in beta (Congrats!). It think it would be quite useful if the there was a way to enable this option programmatically via Terraform.
5 votes -
Add filters for easily finding projects that have encryption/audit enabled in the UI
The https://cloud.mongodb.com/v2#/clusters has certain filters to get specific Atlas clusters. Can we add couple of more filters that can easily identify, whether that project has been enabled for encryption at rest or if the auditing has been enabled/disabled. This will help us easily generate reports for cis20 reporting.
1 vote -
I WANT UPI OPTION
UPI option for India users would be great.
1 vote -
Add Teams to a Project
Allow to add a team to a project and set roles.
Split the creation of the project and the role assignment.
Based on the API: https://www.mongodb.com/docs/atlas/reference/api/project-add-team/6 votes -
Allow autoscale for connections
Allow autoscale for connections
7 votes -
Terraform support for Database Triggers using Function events
The Database Triggers resource supports only EventBridge right now. It would be awesome to see support for Function events as well
15 votesHi we working to enhance the the use of Triggers and Functions in Terraform, but this effort still several quarters away. Feel free to reach on in the interim in case of any questions and happy to help.
-
Have EventBridge send an error message to Atlas to stop flow of Trigger data at the source
Currently, once a Mongo Trigger makes a successful hand-off to EventBridge, it doesn't have insight into EventBridge issues landing the data in its destination. Currently, you have to set up separate code to process failed EventBridge events using the DeadLetter queue. You also need to set up a process to integrate this data from the DeadLetter queue back into the EventBridge destination. If the requested functionality existed, you would only need the Trigger restart process to handle any failure in the data stream from Mongo to EventBridge destination. This will also enable a single place to monitor the data stream.
1 vote -
invoice
Invoice should show the ClusterName combined with Cluster Tier and Server Hours same with Data Transfer. With these, it is easy to determine how much cost we are spending per ClusterName. Right now it only shows per ClusterTier which is hard to separate the cost if you have 2 same ClusterTier.
4 votes -
Administration API Auditing
Looking for more verbose and central auditing of Administration API key usage. Currently, not all actions are logged to the activity feed.
We understand we can refer to the Access Control List for the API key and get date/time for last usage, but, we would like to have visibility into endpoint, action, last used, etc. for each usage of the key.
9 votes -
Allow --removeAutoIndexId option to Atlas live migration as default
Apparently Atlas live migration does not support --removeAutoIndexId option due to which some collections having
autoIndexId set to falsedoes not allow live migration to work successfully. Please add --removeAutoIndexId option to live migration.1 vote -
Add support for HTTP based scraping without IP restriction
Prometheus supports a lot in the HTTP scraping space, including oauth and Bearer token based scrape targets.
Currently we use Grafana cloud that has a list of IP address that can scrape from. This "can" change, and if it does and we hardcode this access into Atlas based on IP then it will break the scrape.
Could Mongo add support for token/oauth based scraping. Where we provide these tokens in a HTTPS call?
I think this would solve the issues with things like private link, or peered network connections. It would also allow "any" prometheus server that can make outbound…
2 votes -
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 -
Re-run a query from the profiler tab
When using the profiler tab, if there is a $regex expression specified, it comes back in the logs as $regularExpression. Similar issues for ObjectID() vs generated $oid.
For some reason, you can’t take the query the profiler outputs and just plug it back in to mongo. You have to manipulate it.
Displaying a valid query from the profiler tab in which I could either click “Open query in aggregation viewer” and open the aggregation pane for that collection with this query pre-populated, and/ allow easy copy+pasting of a valid query elsewhere.
The first thing I've been doing with query optimization…
1 vote -
Allow switching between shards in the profiler and/or have a combined view
Since the profiler tabs are shard specific, it would radically improve the usability to:
a) Combine the profiler events to truly have a cluster level view so you don’t need to worry about shard specific views
b) Add a drop-down to the top of the page near the title that has the various shards listed in it, selecting a different shard brings you back to the same tab, but now with the changed view.
c) Consider tweaking the URL so that rather than using a SHA in the URL, you use the shard name, making it easy to manipulate the…2 votes -
Always show shard name on cluster's profiler page
On a cluster’s detail page, there is the Profiler tab. If you click on that, you are brought to the slow query profiler page. What’s not apparent from this view is that this page is not scoped to be cluster wide, but instead is scoped just to the primary mongo node. If you go back to the Overview tab, click on a specific shard on the left and then go to the profiler tab, you see how now, the title is shard specific and truly shows what you’re looking at? Please always display this shard name regardless of the breadcrumb…
1 vote -
1 vote
-
Show queries that exceeded maxTimeMs in the Atlas Profiler
We had some queries hit the maxTimeMS and fail. We had to download the log files for visibility into those errors. That is info that we would love to see in the Profiler!
2 votes -
Recommendation to the change the tier cluster
Based on CPU and memory usage metrics over a certain period of time, a recommendation could be made to change the cluster tier to a higher or lower one (inform which cluster it would be recommended to change to) and notify through some channel, such as eg email/slack.
4 votes -
View TOP N queries per CPU / memory / disk and number of execution for each query.
This type of metric is common in relational databases and I think it's important to deploy in the Atlas interface.
Top queries by CPU/memory and disk over a period of time or real time. It is important to have this visibility and improve the respective query(s).
It is good to know how many times each query was executed during the respective analyzed period.
3 votes -
Feedback and public roadmap.
I have voted and written since 2020 several improvement ideas for your platform.
Being a client for a major insurance company, I'm disappointed to see that for several suggestions dating back more than 12 months, it doesn't even seem to have been looked at by your team.
It would be more than interesting to have an idea for your roadmap as well as a dynamic management of the catalog of ideas (feedback) maintained by your customers.
I consider this a lack of respect for your users and customers.
Some examples:
https://feedback.mongodb.com/forums/924145-atlas/suggestions/40638277-atlas-backup-to-second-region
https://feedback.mongodb.com/forums/924145-atlas/suggestions/43289796-max-database-users-not-visible
https://feedback.mongodb.com/forums/924145-atlas/suggestions/42163234-authentication-on-azure-iam
3 votes
- Don't see your idea?