Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1374 results found
-
Show index name/details when creating or dropping index via Data Explorer
When Atlas user creates a rolling index in Data Explorer, we can see the name of the index being built in Activity Feed. However, if Atlas user creates an index or drops an index, the index name is not revealed in Activity Feed. This creates some complexity to trace which index is created or dropped via the Data Explorer
1 vote -
Allow Atlas users to issue movePrimary command
Currently Atlas users are unable to issue the movePrimary command for moving the primary shard for a db, and instead have to open a support case to do so. Can we please allow the ability for Atlas users to issue this command themselves?
2 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 -
private link - common dns suffix
when creating a private link, the resulted dns for the cluster is in the form of "cluster-pl-.{somerandomstring}.mongodb.net"
the only difference from the public endpoint is the 'pl' addition in the first section.in order to configure the vpn wildcards and rules,
it can be extremely helpful to have this separation more general, for example
cluster.{randomstring}.pl.mongodb.net -- private links
cluster.{randomstring}.mongodb.net -- publicthat way we can use the wild card *.pl.mongodb.net to differentiate and route the traffic accordingly
2 votes -
Disk Usage Breakdown
When looking at the cluster page, I can see Disk Usage = 1.6GB, for example, but I don't know what the breakdown of that is. For instance, if I look at the same DB and add up the size of the collections themselves it's barely 1.5MB. So 1.6 Gig disk = 1.5 Meg data. I suspect this is oplog etc. but it is a pretty confusing potential red herring when diagnosing performance issues etc.
2 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 -
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 -
support
Being unable to lodge a support ticket without paying for a support plan - when we are paying for a premium service is seriously f'ed up
1 vote -
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…
3 votes -
mongorestore
As per the mongorestore
- to preserve UUID must use drop collection
- if the collection is dropped then it will affect user/login access.
This cascading effect makes it's impractical to use. We wanted to use mongorestore UUID as an idempotent operation, in case halfway things go wrong and have to start again then it's useful to preserve UUID.
Also, in the mongorestore there should be an option to ignore/skip index creation, we were trying to bring data from the legacy app without indexes. It seems that's not possible at this moment.
1 vote -
default country
When I tried to register for Atlas webinar, host country selection was mandatory. By default it displays the USA first value in the dropdown and have to scroll down to select another country. It would be a good user experience if on the registration page visitor/user's country is identified and by default selected, this will prevent unnecessary scrolling.
Also, a very annoying thing is that in order to register for the webinar have to agree to subscription. Subscription to email and other notification should be optional, otherwise, it's a bit dodgy tactic more suitable to some social media companies who…
1 vote -
Terminate existing connections from IPs when removed from the whitelist
When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be…
4 votes -
Privilege advisor capability
It would be incredibly helpful to have some sort of capability that allows users within the Atlas portal to be able to see what privileges are needed to perform various actions. For example, we have users that are not able to configure alerts, or other users that are not able to add users to a project. It isn't always clear what privileges are needed in order to give users those capabilities. Either some sort of tool would be helpful, or very clear documentation on privileges that are needed for each capability within Atlas.
1 vote -
CLI for working with atlas
Revive this tool https://github.com/ralphcapassomongo/atlas-cli and create a formal CLI for working with Atlas in the command line.
3 votes -
Find filter autofill list should be Collection dependant
The Clusters > Collections > Find option offers an auto-fill drop-down of previous entries, which is super helpful. However, it seems to offer suggestions from previous queries of all the Collections. This is not helpful, since Document keys tend not to overlap across Collections, so it would be even more helpful if the drop-down only listed previous queries from the selected Collection.
1 vote -
Expose oauth apps to let other services integrate with Atlas
Expose oauth apps to let other services integrate with Atlas, this way other platform can integrate with atlas for provisioning a mongodb instance.
It would allow for a lot of opportunities for developers like automatic mongodb provisioning for a deployment platform
Right now if you deploy with platforms like Zeit or Heroku you have to create a mongodb database and whitelist the right iP manually
1 vote -
Atlas - Preferences - My Date Format - allow 24hr
We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks
8 votes -
Give an option to pause the cluster as a parameter, at the moment it is auto activating after 30 days of cluster pause which is not required
Give an option to pause the cluster as a parameter for specific duration of time, at the moment it is auto activating after 30 days of cluster pause which is not required for all the users and manually we have to keep an eye on this at the moment.
6 votes -
regular
Restore snapshots to different clusters.
I have a staging environment cluster whose data I'd like updated daily with anything new from my production cluster.
Currently I do a dump and restore, but this is slow because it gets piped externally.
Ideally I'd be able to restore a production snapshot to my staging cluster through a script running on a cron. Whether than is API or CLI doesn't matter.
1 vote -
Make a more realist design, with hack themes, and fancy UI
Please look at the images, try to make similar UI, it would improve a lot the productivity
1 vote
- Don't see your idea?