Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1334 results found
-
Backup persistence after termination should be standard
It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
5 votes -
Integrated Benchmark utility for mongodb
I would like to request a mongodb utility which can do benchmark tests and can be used by developers and DBA to test mongodb for release changes, application code changes etc. The utlity should be able to simulate multiple users and produce different types of workloads (like reads, updates, deletes, inserts etc). This would need to be similar to other nosql benchmark tool like asbench used in aerospike nosql database.
Link is : https://docs.aerospike.com/tools/asbench5 votes -
Add a data source for the Atlas Control Plane inbound/outbound IPs
It would be nice to be able to fetch all outbound and inbound IPs for the Atlas control plane so that we can add them to the list of allowed IPs on Azure keyvaults for example
5 votes -
Private endpoint termination protection
Similar to the Cluster Termination Protection, it would be nice to have Private Endpoint termination protection to prevent accidental deletes of private endpoints, which could very likely result in application connectivity loss and downtime.
5 votes -
Granular cost and inventory details
We are building a unified portal to view our databases and almost all other managed cloud providers like AWS provide instance level/node level view of clusters.
Currently, there's no way for me to get instance level/node level inventory details.Also, when billing/cost is generated, it's generated on a cluster-level basis. Since we now have separate sizing for Analytical nodes and Electable nodes, it's better to separate out the cost to be at an instance level.
Again, all cloud providers like AWS do give us instance-level costing for EC2/RDS so I don't see why that can't be technically possible.
Support costs…5 votes -
Add more information to "We are deploying your changes..." blue bar
Occasionally we see the deployment blue bar but aren't sure exactly what is being done. It would be very useful to have a link to click to see what changes are currently being pushed out.
5 votes -
Notifications
In case of a databreach MongoDB will notify their customer.
Customer is defined as 'the Organization Owner'. However, a databreach should end up with a privay or security officer. It would be a nice feature if some of these roles would be defined and what kind of alerts/nortification they can expect from MongoDB Atlas5 votes -
Restored snapshots from a dedicated instance to a serverless instance
I'd like to be able to spin up serverless instances for automatically provisioned dev/QA environments. I'd like to have production data available in them. So I'd like to restore a dedicated instance snapshot to a serverless instance.
5 votes -
REST API for sizing and pricing information
To keep our configuration on optimized terms we need a way to keep sizing and pricing data of the configuration on our side up to date. We have to get this information automatically for example via REST API.
This would help us to be up to date concerning
- Tier sizing: e.g. tier, RAM, CPU, min HDD, price included HDD, max HDD
- Pricinig: e.g. how much $ per hour / month for tier ***, with XX GB HDD and RAM, KMS encryption, backup and so on5 votes -
AWS multi-region key (CMK)
While using AWS multi-region key, if a customer selects a new region for their CMK, Atlas will trigger a key rotation process which could take some time to complete depending on the disk usage. Can we introduce native support for AWS multi-region key so Atlas does not have to re-encrypt data if CMK ID is the same in the new region.
https://docs.aws.amazon.com/kms/latest/developerguide/multi-region-keys-overview.html
5 votes -
Last Database User Access
My team has found ourselves in the position of needing to iterate through the Database Access History Logs in order to discover whether or not a database user is still being used for the past t time periods.
We need to have this functionality in order to guarantee a seamless credential rotation.
With the current API this operation will require iterating over each cluster's access logs for the past t time periods. If I have "n" clusters and "t" time periods this is an O(n * t) runtime. I'm not really great at O() notation, but if t is greater…
5 votes -
Allow user provided alert templating for Atlas alerts
I want to have the ability to provide their own templatized text for alerts. Often I may want to provide specific instructions to operations personnel for each alert type, or to provide links to relevant internal runbooks.
Other systems such as Datadog and PagerDuty provide this kind of capability.
5 votes -
Global overview of Index Suggestions
We run more than 60 clusters today on Atlas, and will probably hit 100 clusters in the foreseeable future.
The Index Suggestion alerts are not dependable for us (see https://feedback.mongodb.com/forums/924145-atlas/suggestions/44243568-better-alert-trigger-for-index-suggestions ).
Going through many clusters manually to check them for Index Suggestions is an extremely time-consuming process. We would like to have a global overview of all open Index Suggestions, or at least an overview on a project-basis.
5 votes -
Uptime report for Atlas cluster
It would be great to have an uptime report be it weekly or monthly basis which can be extracted and presented anyone who would like to have an high level overview.
5 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
5 votes -
Reuse email address for new Atlas account
Please allow email addresses to be reused/reinstated for new Atlas accounts if an Atlas account associated with that email address has been deleted.
5 votes -
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 -
reactive table
Hi, i would like to ask for you to make the table view under collections when we choose a particular database to be reactive. when i press a header we want it to sort the rows from asc to desc or vise versa. thank you
5 votes -
Tag-aware permissions to control access to analytics nodes
MongoDB has the great future of Workload Isolation based on node tags: we can add nodes tagged for analytics or reporting and then configure the same tag for this type of connections so that they do not interfere with the main operational workload.
But it is the responsibility of the BI/Data Scientist/Analyst to properly configure the connection: it cannot be enforced in a centralised way. It would be great if MongoDB permissions could be "tag aware", and allow access for a particular user only to some nodes of the cluster.
5 votes -
Monitoring for WiredTiger data handles
Add process measurements for monitoring WiredTiger data handles.
From Atlas documentation https://docs.atlas.mongodb.com/reference/atlas-limits/#collection-and-index-limits :
While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.
but now there is no way to get this information except
db.serverStatus()
5 votes
- Don't see your idea?