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
-
CPU Steal % on Azure
The CPU Steal % metric and alert seems to be currently implemented only for AWS. Please implement it also on Azure, as there is no easy way currently to get alerted if the underlying burstable VM (e.g. for M20) runs out of credits ...
5 votes -
Alerts on Configuration Changes
It would be nice to have an alert configurable when any change is made to the cluster configuration. It helps with compliance that there is knowledge of such changes without having to manually search and activity feed.
7 votes -
Atlas API to update Project Timezone
At the moment, Project Timezone setting can only be done via Atlas UI. We are automating project and cluster creation and setup for our application. We need an API to update Project Timezone setting just like other project settings. This feature is important for our organization to keep all the project with the same settings without a manual intervention.
19 votes -
Show last activity of user
For managing Database Users, it would be nice to see when that user was last used to authenticate with the cluster - so that we can spot potentially unused accounts and to act as an extra layer of confirmation when deleting accounts that we think are not needed anymore.
8 votes -
Atlas should allow deployments of non-voting members on region for tiebreaking purposes
No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.
This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.
1 vote -
payment failure
I tried couple of credit cards including Amex India and Visa. It keeps giving message "The card has been declined."
1 vote -
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)
12 votes -
Support node type or node tags as condition in MongoDB Atlas Alert
Currently, the MongoDB Atlas does not support the node types [1] or node tags [2] as the condition in Atlas alerts. That would be super inconvenient for the following scenarios.
Scenario 1: If the user wants to create an alert to monitor the specific node type, such as READ_ONLY node or ANALYTICS nodes, there is no convenient way to achieve it. The current approach must set up the alert by using the hardcode hostname.
Scenario 2: If the user has some electable nodes and a analytics node in a cluster, and wants to focus on monitoring the electable nodes (workload),…
14 votes -
Feature Request: DNS record per zone for global cluster
Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.
This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…
1 vote -
Change the copy document icon
At the moment the Copy Document and Clone Document icon are conceptually identical (two sheets on top of each other with a diagonal offset to suggest duplication) so whenever I want to do one or the other I have to check which is which with the hover tooltip.
It would make sense to change the Copy Document icon to a clipboard icon or something like that.
1 vote -
description in sso group mapping
Add a description field in the Atlas UI in the group mapping page when SSO is enabled. Today only an object ID is available.
2 votes -
Add support for profile configuration file in the Terraform provider
To be able to quickly change which account we use for the Terraform provider without having the keys in the terraform variables, supporting profile config file like what aws does for it's provider would be a great help for us.
1 vote -
Please remove the text-transform uppercase style on the graph axes.
I yelled out "WTF!" in the office when I saw that a steep peak in the graph indicated a query that took 8MS. Turns out it meant to say 8ms.
The M means Mega (one million). We, I assume, are all very familiar with it, and therefore I assume that I'm not the only one who automatically reads it as one million.
Note that I did not confuse the s and S. That is because the s and the S are much less visually distinct. Still it's technically incorrect too.
1 vote -
Option to restore one or more db from snap to cluster. Right now, it involves manual dump and restore
Currently we can only restore full cluster from backup like snap using GUI interface. If we want to restore one or more specific db, it needs manual dump and restore from backup. if we have an option to restore specific db to cluster through GUI interface, it will be very useful.
131 votes -
Transactions support for Merge operation in aggregation pipeline
Hi Team,
can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictionsWe have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.
The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.
thank you
4 votes -
Exclude nodes from Autoscaling
We run huge analytics, reports and queries over our analytics node. And its expected that analytics node is sometimes over immense CPU or Memory pressure.
Current behaviour: When I enable Autoscaling, all the nodes in my cluster scales up when there is heavy load.
Expected behaviour: I would like my analytics node to slow down or the query to timeout rather than scaling the entire cluster.Therefore, I should have an option to exclude the metrics of analytics node while deciding for autoscaling.
7 votes -
Specific Privilege selection on Org Level
It would be great to select specific privileges for on the Organization Level as well. Similar to what one can do on the Project Level. E.g. Org Member but without being able to see billing.
1 vote -
Add Default Alert: Secondary is Down
Secondary is down should be a default alert.
1 vote -
Support for customer-managed keys (CMK) on the volume-level instead of Encryption-at-Rest
For some customers managing a set of low-latency workloads is crucial, so volume-based encryption using their own KMS encryption keys is preferred over the encryption-at-rest feature of the WiredTiger storage engine. https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html
The support is required for clusters, their backups and Atlas Data Lake.3 votes -
Recreate Account | Sign Up | MongoDB Atlas
There are many new web developer come on MongoDB Atlas. There create there account and start working but don't know any thing about MongoDB. Something goes wrong on there setup and decided to recreate there account and follow all the instructions. But after deleting there account they see that they can't use there old email address.
Because of this situations that I faced. I don't want these to be faced by someone else so I recommend MongoDB Atlas to remove this security policy. Guys, Do you support me?1 vote
- Don't see your idea?