Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1358 results found
-
Incorporate Resource Tags in Atlas alerts
Enhance the alert content by incorporating the resource tags of the entity that triggered the alert.
14 votes -
Alert when database user is created or removed
currently there is no alert option for database users
14 votes -
Public API to get cluster pricing
Currently, we have to use the UI to get a pricing estimate for a cluster. Having a programmatic way to get this estimate would be very valuable.
14 votes -
Ability to choose a Primary shard for newly created database
In a multi tenant architecture, the isolation of a tenant on a specific shard (when database sharding is involved) is expected. At this time, the ability to choose a Primary shard for newly created database would come in handy
14 votes -
Add metrics to monitor CPU credits for burstable performance Atlas clusters
Add metrics to Atlas for tracking burstable CPU credit spend for M10 and M20 cluster tier instances. Additional add support for creating alerts based on these metrics.
14 votes -
Deploy Custom Role to specific clusters only.
You added the ability to deploy users to specific clusters. Great but you forgot to do it for the "custom roles". We use the "custom role" with LDAPS so we do not create a user on Atlas.
Can you extend this functionality to "custom role" also %
14 votes -
Allow registering multiple security keys in MFA
Currently, only a single security key can be registered as an MFA device. As a backup to this key, only other mechanisms such as authenticator apps can be used. It would be nice if multiple keys could be registered to avoid having to use a different method as the backup.
14 votes -
Add an alert or notification option for every "pause" or "resume" cluster action
Add an alert or notification option for every "pause" or "resume" cluster action
14 votes -
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 information to the billing API reponse
When retrieving the billing details through the API, we are missing some information for a perfect understanding (and automation) :
- Number of nodes of the cluster. Indeed, without this information, the field "quantity" is kind of complicated to interpret
- Group Name. Each entry is attached to a groupId, but sometimes when the project has been deleted, it is impossible to retrieve its name, so pretty complicated to interpret (in the UI, the group name is available, so I guess it can be in the API)
14 votes -
Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
14 votes -
Make AWS EBS Burst Balance metrics available in Atlas UI
Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.
You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.14 votes -
Ability to schedule monthly maintenance windows
Ideally we'd have the ability to schedule maintenance windows that are monthly. Either the option to say maintenance run on the 3rd of the month or every 2nd Tuesday. The current issue I see is that your non-prod clusters and prod clusters can share the same window and get patched at the same time, or you pick different days of the week for patches (e.g. Monday for non-prod, Friday for prod), but we risk having prod patched before non-prod in that situation.
I realize we have the ability to defer maintenances for a week, which is great. However, we're now…
14 votes -
Alert setup for failed logins
There is no good monitoring or alert functionality for dealing with potential invalid login attempts.
I suggest an alert setup to handle events when known users fail more than 3 times to login (either in Atlas or via driverlogin to db).
We have had an external audit done and this is something they have found as a shortage in the MongoDB Atlas environment.
Log files are good but not to monitor potential security issues
14 votes -
Allow Atlas User Data Access Permissions to be configured on a per-database/collection basis
Similarly to how database user data access permissions can be configured on a per-database or per-collection basis, it would be ideal if Atlas user data access permissions (as they apply to Data Explorer) could be configured on a more granular basis as well.
14 votes -
pause
An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.
14 votes -
Credits API
I need an API that will allow access to the items under credits in the billing page.
This will allow me to pull this information daily into our master usage database to support our dashboards14 votes -
More detail and lead time around maintenance notifications
When we get email notifications of upcoming maintenances, it doesn't specify if the update is "urgent" or "low". When we received our last notice, it was 3 days out. If it's urgent, then we understand the short time frame around the notice. However, if it's a lower priority update, I would hope we could configure how far out we are aware of the maintenance or at a minimum get notified 2 weeks prior so we can communicate to our end users.
Additional information around what the maintenance is for would be appreciated as well. Something along the lines of "Patching…
14 votes -
Provide state import capability on mongodbatlas_organization resource
The mongodbatlas_organization resource does not have state import capabilities and I don't understand why. This doesn't seem to be a difficult one to implement and for us it will greatly help, because we have a need to import into state existing organisations which were created (unfortunately) outside terraform.
13 votes -
Map IDP groups to Atlas teams
At the moment Atlas does not support mapping IDP groups to existing Atlas teams. We would like that the integration would support that. For example:
okta group "devops" --- mapped to ---> Atlas team "devops"
Each time the customer adds a user to this idp group, the user will be given the proper permissions in Atlas.
13 votes
- Don't see your idea?