Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1372 results found
-
Support multiple LDAP servers and TLS connection options
When integrating my Atlas project with an LDAP service, we want to specify multiple LDAP servers rather than just one, and to specify options for the TLS connection such as allowing invalid hostnames. Both of these can be done in self-managed MongoDB Enterprise.
1 vote -
Improve 2FA and auth management
Right now, there is no way to require Google auth or to require 2FA. The only way to enforce 2FA for a team is to check the team mangagement page. However, since some users may have only used Google auth to login, they will show up in this view as not having 2FA, creating auditing headaches. Please
- indicate if a user does not have 2fa because they do not have a password vs just not having 2fa
- ideally, add the ability to require 2fa and/or Google auth for all team members12 votes -
Vanity URLs for projects and clusters
Right now URLs for mongodb clusters are generatd by MongopDB. For the clusters I create it would be much easier to remember and distribute if I could create a canonical name per project and have each cluster member have its named assigned by the cluster.
So instead of demodata.rgl39.mongodb.net I could use demodata.joedrumgoole.com.
3 votes -
Separate metric graphs of egress outside the region per database, collection, user, destination
Separate metric graphs of egress outside the region per database, collection, user, destination, so that I can easily find out what is causing the egress traffic which is billed on my account. This will also help me identify what parts could be good to move to different cluster in another region closer to the user,
1 vote -
Allow default settings on alerts on project/organization level
It would be great if there was a way to set the default notification channels for alerts on the project and organization level.
I was recently informed by the support team that there is no possible way of doing so, and that all alerts should be changed individually rather than for the whole project in one go.
1 vote -
Show in the UI when an index build is ongoing, and when it completes
When indexes are built from an application or a mongorestore there's no way to see if it's ongoing in the UI.
There should be an indication in the "Real-time" tab saying that an index on collection X is in progress. This would explain why performance is currently impacted.
It would be good to see index start and end marked on the "Metrics" visualizations so we can see the impact of index builds on IOPS, CPU, memory etc. This could help understand if we need to upscale the cluster.
10 votes -
Show Index Error on UI
When creating an index on your UI, if the index creation gives an error, the error doesn't show on the UI, for example if you have a field of type string, and have a value longer than 1024 bytes, and try to create a normal index on this field, the UI will tell you the index it's been creating successfully, but when you go to your collection and see your indexes, this will not appear, but when you create it on the MongoDB console, it gives the following error. It would be nice to have this error shown on the…
16 votes -
Use the User's Profile Time Zone for PIT Restore
When viewing Cloud Provider Snapshot information, all dates are listed in the time zone on the User's profile. However, the date/time to be entered when trying to perform a PIT restore has to be entered in UTC time. This is asking a lot of someone who is probably already really nervous to be able to correctly calculate the difference between their time zone and UTC time.
3 votes -
Ability to Drop Indexes via API
Allow users to not only add indexes via the API, but also allow them to drop indexes the same way. Also incorporate index creation/deletion into Terraform.
19 votes -
Terraform for LDAP user/groups
We'd love to be able to create LDAP user and group accounts in Atlas via terraform. The existing mongodbatlasdatabaseuser resource doesn't support LDAP, so we are forced to use the API to create those users and groups.
3 votes -
MongoDB to throw error when detect '.' in keys insert
Not sure if MongoDB was supposed to be unstructured even for keys. Because MongoDB currently does not support '$' and '.' in its keys, is it possible for MongoDB to throw an error if '$' or '.' are detected in keys during insert? MongoDB currently does not do that and is problematic to fix for previous large databases which have '$' or '.' in keys
1 vote -
Add colors to Backup times
Hi can I suggest a feature to the developers? Can the developers add colors to the Backup times? Because I have accidentally Backup an instance at 3:21 PM instead of a 3:21 AM I wanted. The colors will definitely help prevent such accidents from happening. It would also be nice if the developers can ensure that Backup times are not the same for AM and PM. Thanks!
2 votes -
Provide Atlas support for "Classic" VNet Peering topology
Provide Peering support for "Classic" (Hub and Spoke) VNet Peering topology, either directly or via a NAT
13 votes -
It would be useful to have an ability to pragmatically keep up to date with the latest prices in a RESTful fashion.
Something like /offerings/aws/compute/M10 returns:
{
// some metadata about this pricing api.
"prices": [
{
"priceId": "c800b6d9163b0db7",
"region": "us-east-1",
"charges": {
"compute": {
"price": 0.11,
"interval": "hourly",
"currency": "USD"
},
"storage-GB-month": {
"price": 0.015,
"interval": "hourly",
"currency": "USD"
},
"backup-GB-month": {
"price": 2.5000000001,
"interval": "hourly",
"currency": "USD"
}
}
}
]
}Use case: For those that use programs to calculate costs, this will reduce some of the guesswork involved by looking at cryptic documentation and invoices to calculate and forecast costs and be able to charge appropriately to match systems with demand.
Amazon has similar API endpoints available:
https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/us-east-1/index.json…
5 votes -
Login auto-redirects to 2FA screen but shouldn't, or offer logout
I have three MongoDB Atlas logins and when I visit the Atlas login page it then redirects me to the 2FA page.
I actually just want to swap between accounts, so either a logout option would be useful, or let me return to the login screen from the 2FA screen. Unfortunately if I click 'back' the app forwards me back to the 2FA screen.
1 vote -
Stackdriver Integration
Atlas Monitoring UI is great, but to ease centralization of alerts and dashboards..., it would be nice to have all atlas metrics in Cloud Monitoring too.
10 votes -
Expose the `indexStats` action when creating custom roles in Atlas UI.
The $indexStats aggregation pipeline allows user to get the statistics regarding the use of each index for the collection. This aggregation pipeline requires the
indexStatsdiagnostic action.However, currently Atlas UI doesn't expose this action when creating custom roles. It would be nice to have this action listed in the "Collection Actions => Diagnostic Actions" list.
7 votes -
Adding indexes using terraform
Ability to add indexes after new clusters are created using Terraform and data has been loaded. It will help in more automation and auto recovery.
52 votes -
Create databases and collections via API thorough Terraform
Create databases (DB) and collections via API thorough Terraform after the cluster has been created in Atlas. This would provide the ease of writing and running it in a single script before any data is loaded.
144 votes -
Add replica set name to cluster info main page
It would be nice to get quick access to the name of the replica set from the cluster overview page.
7 votes
- Don't see your idea?