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
-
Restore protection similar to termination protection
A restore protection option similar to the termination protection for clusters.
When a cluster has restore protection enabled, it can't be the target cluster for a restore operation. This will prevent accidental restores to the wrong target cluster from affecting the protected cluster.The motivation is preventing mishaps from affecting critical production clusters.
The UI for selecting the target cluster of a restore operation has you select the cluster from a dropdown and then type in "I Agree". That still leaves you open to mistakenly select the wrong cluster if you aren't paying good enough attention.
The restore protection feature…2 votes -
2 votes
-
Disable duplicate linked Organization names
Currently, one can create multiple linked sub-organizations under a main billing organization, but having the exact same names. The below API command, run repeatedly, will create the same sub-org name with different orgId's. I believe this only serves to confuse administrators and makes management more difficult -- therefore, I'd rather have the API fail with "HTTP 4xx: Another organization already exists with the same name."
curl -s -X POST --digest -u "$ATLASPUBLICKEY:$ATLASPRIVATEKEY" \
--header "Content-Type: application/json" \
--data '{ "name": "MYORG", "orgOwnerId": "MYORGOWNERID" }' "https://cloud.mongodb.com/api/atlas/v1.0/orgs" \
| jq -r .organization.name2 votes -
mTLS for Atlas Alert Webhook Integration
Atlas currently does not support mTLS on HTTPS traffic to Alert webhooks. Some customers whose alerting services are on-premises may require this per their security policy. We should support mTLS on webhook integrations to enable those customers to use their on-premises alerting systems.
2 votes -
Add a button to retry to collect a payment on the billing - invoices tab
Add a button to retry to collect the payment from a credit card on user request. This will help when there are problems with the credit card funds or credit limit.
2 votes -
Lock a user account
We have an occasional need to disable/lock an individual database user. Either because of a run away process or inactivity. We do not want to change the password or drop the user as we may need to reenable the user quickly with the same permissions and password as before.
2 votes -
Atlas triggers on serverless instance
Atlas triggers on serverless instance
Hello, Atlas triggers would be a really nice to have feature on serverless instances.
2 votes -
U domain Verification
If you are able to verify the parent domain for your company, then you shouldn't need to have to verify the sub-domains associated with that domain. Company's do not generally advertise their internal u-domains on the internet therefore any verification on that sub-domain will naturally fail. This is hindering us from integrating our Okta credentials with our login information.
2 votes -
Feature: Atlas UI -- Star/Favorite/Bookmark of Project
It would be nice to be able to star/bookmark projects, so I don't have to type half the project name in every time I switch between environments--eg. like in Datadog, star a dash board and it shows up at the top of the list/without search
2 votes -
Add EventBridge integration for Serverless instances
Currently EventBridge integration doesn't work for serverless instances
2 votes -
Support exporting Custom routes
Supporting export of custom routes with peering connection (with GCP in our case). At this point it's not possible to access atlas from our on-prem network with -priv FQDN, we would have to use the public ones by managing source ip in GCP firewall (painful on a remote workers world) or adding a Google Cloud VPN product to create some kind of vpn connection. Just permitting export of private subnets would be great !
We have peering with other product and they support it !2 votes -
Approval workflow for database deletion
The current Termination Protection only prevents accidental deletion of a cluster. It helps to have a similar protection to databases inside the cluster.
Even better if there is an approval workflow, in which several people must accept before a database/cluster is deleted.
2 votes -
Restore indexes from AWS S3 snapshot.
While working with export snapshot to AWS S3, I found there is no way to restore indexes from metadata.json, along with data there must be opportunity to restore indexes as well otherwise have to rely on custom solutions and this may include external dependencies.
2 votes -
Send alert(email) when database is deleted
The alert conditions do not contain conditions like
- when database is deleted
- when cluster is deleted
- when project is deletedWe want to get notified if a malicious person or someone by mistake deleted major parts of the database.
This simple notification is not possible right now.2 votes -
Control KMIP Key Rotation Timing
We need the ability to change the automatic key rotation time for our cluster. Currently the automatic rotation is set at 90 days but we cannot specify the time at which the rotation should occur. We want to avoid automatic key rotation activity during business hours.
2 votes -
Add hint support for MongoDB API functions
The "hint" option for Mongo Shell query/write operations is very useful when the Query Planner does not select the right index by default, or just to make sure the right index is used. When you cannot use the "Hide index" feature on the index selected by default, "hint" becomes the only way to have an efficient IXSCAN.
However, the "hint" feature does not exist on the MongoDB API functions (https://www.mongodb.com/docs/atlas/app-services/functions/mongodb/api/). This means that no command we can run inside a Trigger can specify a "hint" option.
I think that "hint" is a great "backup" feature for cases where…
2 votes -
Accept VPC peering connection when created by MongoDB::Atlas::NetworkPeering
VPC peering connection created by CloudFormation resource
MongoDB::Atlas::NetworkPeeringhave to accepted in AWS, using GUI, CLI etc. Would that be possible to get this done using CF only?2 votes -
Use additional metadata to differentiate processes
Right now Ops Manager monitoring identifies MongoDB processes according to hostname:port. Unfortunately, if 2 processes have the same short hostname & port in the same Ops Manager project, they'll be treated the same even if they are actually different processes with different FQDN.
Please either allow the use of additional characteristics (FQDN, replica set name, config server name, etc) for differentiating MongoDB processes or provide some way to tag 2 or more processes so monitoring doesn't accidentally miscategorize them as the same process.
2 votes -
Atlas shards with different clusters tiers
For solutions of hot and cold storage, there is at least 2 options:
- Online archiving
- Hot and cold cluster (using a trigger and datalake)
But these solutions have limitations (https://www.mongodb.com/docs/datalake/limitations/)There is another solution: using sharding.
We can set shards like so:
1 shard: Data from the last 2 months -> Hot data
1 shard: Data between 2 and 24 months -> Warm data
1 shard: Data more than 24 months -> Cold dataThe usage pattern: 95% of the accesses/queries go to shard with the hot data.
On Atlas, we need to set the same…2 votes -
Should give download CSV option for getting all the slow queries details
It will be better if a have an option to download all the slow query related information as whatever we see in the Atlas UI.
2 votes
- Don't see your idea?