Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1365 results found
-
Granular Permissions
Right now Mongo Atlas allows you to assign two types of roles to all the users: Organization and Project, and for each set it gives you some predefined roles.
The problem with this is you can't have any kind of granular control of what permission is assigned to each user. (e.g. to allow a user to create a trigger through Mongo Stitch it needs the Project Owner role).
This is a major setback as I'm giving my coworkers more access than needed.
A good solution would be to have something like the database access control in this part so we…
491 votes -
Persist setProfilingLevel Setting in Atlas
Currently the profiling level resets to 0 every time the mongod process restarts. You can persist this with a self-hosted mongo by editing operationProfiling.mode in the conf file, but this is not possible in Atlas.
7 votes -
Display EBS actual disk information (gp3)
Currently, clusters created on AWS have gp3 volumes according to support.
However :
* the configuration displays max IOPS 6000 for M50 clusters even though documentation states that iops scale 3:1 with the volume size in GB (1 GB = 3 IOPS) regardless of disk type for M30+ clusters (true with gp2 anwyay, for gp3 that's an enforcement by Atlas)
Documentation link : https://docs.atlas.mongodb.com/customize-storage/#configuring-the-iops-rate=> the configuration should at least display the actual IOPS (as it's also being used for alerting) - ideally it would allow us to have more IOPS than the minimum 3:1 enforcement.
- with gp2 we had…
5 votes -
Zabbix
We should have Zabbix integration to monitor the performance of MongoDB Atlas.
Zabbix is OpenSource popular monitoring tool available and many of enterprise organizations use this tool.
Please add Zabbix in Integrate with Third-Party Monitoring Services.
8 votes -
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 -
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 -
Activity Feed should automatically load new items rather than requiring refresh
Today when looking for items to appear in the activity feed, I have to repeatedly refresh the page which is slow/painful. In future it would be better to automatically stream/poll for changes behind the scenes and load them without requiring a page refresh.
5 votes -
Add Tailscale peering
In lieu of doing 0.0.0.0/0 network access, it'd be great to peer into Tailscale so that anyone that is authorized in our organization's Tailscale VPN can connect effortlessly.
3 votes -
Support migration between Atlas clusters using Atlas API
Support live migration between Atlas Clusters through Atlas API. If we need to migrate, it'd be good to be able to do so through the API.
2 votes -
Multiple Email address for alerting
In alertconfiguration, change the emailaddress argument in "notification" block from "string" to "list(string)".
Main goal here is to allow multiple alert emails like it's possible in the portal.5 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.
7 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 -
Custom metric option on Datadog
Currently, there is no option to use the custom metric option when using the Atlas Datadog integration.
We would like to use this functionality in Atlas : https://docs.datadoghq.com/integrations/guide/mongo-custom-query-collection
14 votes -
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.
9 votes -
Allow user provided alert templating for Atlas alerts
I want to have the ability to provide their own templatized text for alerts. Often I may want to provide specific instructions to operations personnel for each alert type, or to provide links to relevant internal runbooks.
Other systems such as Datadog and PagerDuty provide this kind of capability.
6 votes -
1 vote
-
Better alert trigger for index suggestions
The current alert trigger for index suggestion is described here: https://docs.atlas.mongodb.com/reference/alert-conditions/#host-alerts
"If the query targeting ratio for a host consistently exceeds 10,000 for a period of 10 minutes, Performance Advisor checks the host for inefficient queries and possible indexes to improve performance."
Firstly we have issues with alerts constantly going on and off every few minutes if the query ratio is fluctuating around the 10k mark.
Secondly, we often do not get alerts for worthwhile index suggestions. We run a multi-tenant platform. We have big clusters with hundreds of databases/tenants and thousands of collections. A huge amount of our queries…
8 votes -
"Replica set elected a new primary" and other information alerts are not recorded in Atlas
Alerts like the "Replica set elected a new primary" are considered informational, they trigger an email being sent but the alerts were not recorded in the open and closed alert page in Atlas UI. Also they cannot be retrieved via API.
This is pretty confusing as you'd imagine once the alert is triggered, it'll be recorded in the page where all the other past alerts are kept, the concept of informational alert is vague and never properly communicated to users.
Please record all types of past alerts in the UI and make them accessible via API.8 votes -
provide more details on the replica set elected a new primary
today the details on this event are very low and have only the replica set name which is not enough, can you also add the correlated cluster name to the exposed details?
more over if this is something that can be monitored by the metrics going to Datadog?3 votes
- Don't see your idea?