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
-
Rejecting Index Suggestions
Some Index Suggestions don't work. The Performance Advisor doesn't sample data, and therefore can not predict if some field is worthwhile in an index or not (e.g. some fields may contain the same value for all documents).
If we decide to not apply the Index Suggestion, or we apply it, test it, and remove the Index again because it's not being used by MongoDB, the Index Suggestion is still showing up. It can also trigger alerts.
Please add the possibility to reject an index suggestion, so that it's hidden from the UI and can not trigger alerts.
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 -
Better alert trigger for index suggestions
The current alert trigger for index suggestion is described here: https://docs.atlas.mongodb.com/reference/alert-conditions/#host-alerts
"If the query targeting ratio for a host consistently exceeds 10,000 for a period of 10 minutes, Performance Advisor checks the host for inefficient queries and possible indexes to improve performance."
Firstly we have issues with alerts constantly going on and off every few minutes if the query ratio is fluctuating around the 10k mark.
Secondly, we often do not get alerts for worthwhile index suggestions. We run a multi-tenant platform. We have big clusters with hundreds of databases/tenants and thousands of collections. A huge amount of our queries…
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 -
track collection size
I would like to be able to track the size of our collections (i.e. # of records, total disk size) over time. It would be ideal if there was an automated way to do this with Atlas, perhaps with Charts ?
5 votes -
Allow Performance Advisor reporting export
Having the ability to extract/export the Performance Advisor report. This would allow users to share a file with others who may not have access to Mongo Atlas.
5 votes -
configure IP whitelisting on database user level
enable the user creation to have the following option
authenticationRestrictions: [
{
clientSource: ["<IP>" | "<CIDR range>", ...],
serverAddress: ["<IP>" | "<CIDR range>", ...]
},
...
],5 votes -
Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
5 votes -
Accept-Range for backup download
The backup archives can be very large, and if my download is interrupted, without Accept-Range, it is not resumable. A length header is also missing, so the downloader doesn't know the size of the archive.
5 votes -
Add Cluster name to process list api
Currently the processes API (https://docs.atlas.mongodb.com/reference/api/processes-get-all/) returns only the ReplicaSet name of the process not the cluster name, while the cluster API (https://docs.atlas.mongodb.com/reference/api/clusters-get-all/) returns the replicaset name only in the MongoDB URI.
If you have multiple clusters in the same Atlas project and you list the processes is difficult to make an association between MongoDB processes and the Cluster (Atlas UI name)
Would be nice to have also the cluster name in the processes api
5 votes -
Show index build percentage in the UI
During an index build from atlas the only status update you see is:
"We are deploying your changes (current action: configuring MongoDB)"When checking the logs of the replicaset memeber you can actually see the percentage of completion on that member of the replicaset:
2020-11-25T11:15:44.002+0000 I - [conn12] Index Build: 54798100/206784433 26%
It would be nice to have this percentage displayed through the UI.
5 votes -
Billing Alerts Improvement
We find the conditions for billing alerts to be very limited. We were hoping we would be able to setup an alert that triggers when a certain threshold of our total subscription amount has been used for better monitoring. For example, >= 75% of the total subscription amount is used.
5 votes -
Improve "Host has index suggestions"" alert by including the hostname
The "Host has index suggestions" alert notification does not contain any reference to the host/deployment that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
5 votes -
Custom replica set tags
Currently Atlas comes with pre-defined Replica set tags such as Provider, Node Types, Region.. But as of now no options for user-defined tags.
Please provide options for custom/user-defined replica set tags.5 votes -
My entire team receives the billing info every month.
Billing should be limited to organization owners only and not viewable by the entire organization.
5 votes -
Project Monitoring Admin -- Access
Hi Team,
We need to give access to a particular team so they can create, edit, clone, disable, and delete the alarm for the entire organization in Alert setting only.
We should not give them access other than the Alert setting. Is there any way to give access for Alert setting only, kindly provide your suggestions at the earliest.
Please provide us steps if there's any way to create custom access for alert settings alone.
5 votes
- Don't see your idea?