Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Alerts for Atlas Limits
It would really help to get alerts on Atlas Limits (https://www.mongodb.com/docs/atlas/reference/atlas-limits/). Defining certain thresholds that would trigger an Alert as hitting these limits often involves work to re-structure something or creating a workaround. E.g. it is not possible to have more than 50 Endpoints per Project. But creating a new project is not a straightforward exercise. If the alert had occurred earlier there would have been more time to account for this.
8 votes -
Enable database users separate read/write permissions based on cluster
We have multiple clusters in the same project, and we need to limit write access to certain CLUSTERS while leaving read only access to any other cluster. The problem is that we cannot do this by DATABASE name as there are many of them, as well as dynamically addition of new ones in clusters, so it will become obsolete and very hard to maintain.
Trying to use the restriction does not help as it limits all access, including read only, to those clusters.
What we'd like to see is that we can limit write access by cluster (not database/collection) and…4 votes -
We I propose integrating built-in alerts for KMIP key expiration into MongoDB Ops Manager, enhancing our security management and preventing
One crucial feature currently lacking in ops manager is the ability to alert users on impending KMIP key expirations in a similar vein to SSL certificate expiration alerts.
I propose integrating built-in alerts for KMIP key expiration into MongoDB Ops Manager, enhancing our security management and preventing inadvertent lapses in key validity.
2 votes -
Support GCP private link with Serverless clusters
Like it’s done in Azure and AWS, we should have a way of using private link to connect from GCP to the MongoDB Atlas Serverless clusters through Private Service Connect.
We are using all 3 major clouds and this is the only reason why we don’t use Serverless clusters deployed in GCP (all our clusters must have private networking only).
Can this be implemented?
2 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.
6 votes -
Monitoring Metrics on dhandle
We'd like to monitor the WiredTiger dhandle over the time, directly from Cloud Atlas Monitoring view. It would allow to directly see the impact when updating cluster settings.
We'd like also being able to configure alert triggers on it, the goal for us is being alerted when an excessive amount of files (collections & indexes) is loaded into the MongoDB Memory, to avoid reaching an Out Of Memory error.
4 votes -
Allow multiregion sharded clusters to have Primary nodes in multiple regions
For multi-region sharded clusters, the primaries for each shard remain in a single (highest priority) region in Atlas. If these primaries can be spread across multiple regions, that will a) provide consistent average response time for applications that connect from multiple regions as active-active b) Limit the blast radius if the highest priority region is unavailable c) Better distribution of workload from an application side.
This architecture is currently possible with EA deployments but not with Atlas.
7 votes -
View Epoch in Compass
I use epoch times in almost every collection for created time, last modified, etc. Currently I have to copy the time value and paste it into epochconverter.com. It would be very handy if the time showed as a string in a bubble when you hovered over it in Compass.
1 vote -
Create an AtlasRole custom resource
Currently roles are configured as a list inside the AtlasProject resource. I propose managing these as individual AtlasRole custom resources instead.
Consider a typical microservice based application with several microservices deployed by individual Helm charts, each sharing the same project and cluster. In this scenario the app developer may want to create custom roles for each app / group of apps with access to certain collections, eg to stop them from being able to read collections with sensitive data
Currently it is possible for apps to create their own users, but those users must assume one or more existing roles.…
2 votes -
It would be useful to be able to view a collection schema similar to how you can in Compass
It would be useful to be able to view a collection schema similar to how you can in Compass. At present we have to enable LDAP and configure Compass to remotely connect to Atlas, but this is not always feasible and it would be good to see this useful functionality from Compass translate to Atlas UI
8 votes -
Change global default compressor setting
Hello,
I wanted to request a feature that would enable us to change the global default compressor setting ourselves? Something that could possibly be exposed on the Advanced Configuration settings page in Atlas? We're looking to re-compress our existing collections usingzstdfrom the defaultsnappyoption and we want to create future collections using thezstdblock compressor automatically.Today, we have to create a support ticket and co-ordinate with them. It would be great if we could have this feature on the Atlas portal so that we can monitor the progress and trigger it whenever we want to…
2 votes -
Google Private Service Connect
Greeting from Fivetran!
This is somewhat related to https://feedback.mongodb.com/forums/924145-atlas/suggestions/45272014-allow-customers-to-specify-the-number-of-service-a . Having 50 service attachments is not scalable for us which requires 50 IP addresses for each PSC. We have a large customer base and having each of them create PSC would require a lot of IP addresses and would quickly exhaust our subnets.
From the support case it seems that the decision to use 50 PSC attachments comes from the fact that GCP load balancer does not allow more than one pool of servers per service attachment and that the ports are passed through as is as opposed to AWS…
5 votes -
prometheus integration to use PrivateLink
There is a possibility to integrate Prometheus into an Atlas project.
However, for enabling this integration, one needs to add Prometheus's IP address in the IP Access List.
This procedure has 2 flaws in it:
1. Prometheus runs as pods on some use-cases, meaning that its IP is ephemeral.
2. For projects that work solely with PrivateLink enabled and no open IP in the IP Access List, one cannot use the Prometheus integration (already talked with support about that).The improvement here is to add the Prometheus integration to work as well in "PrivateLink-only" mode.
115 votes -
More documentation about alert
It would be great if there were a doc explaning what each Alert Event Types means (and even that could give us some examples). And the same documentation should explain wich alerts have thresholdconfig or metricthreshold_config.
The documentation that I have found with a little explanation is thw below (and it shows some alerts type that don´t work)
Example: OPLOGBEHIND => When trying to use this one on terraform, it returns an error saying it does not exist (the one that works is: REPLICATIONOPLOGWINDOWRUNNING_OUT)https://www.mongodb.com/docs/ops-manager/current/reference/alert-types/#user
4 votes -
Hello, your login captcha is a real pain ********** !!!!!
Hello, your login captcha is a real pain ********** !!!!!
2 votes -
Serverless RPU estimator
RPU calculations can be difficult to understand and generally involves how much "processing" is being done by MongoDB to complete a particular read operation. There are instances where RPU's can skyrocket such as when COLLSCANs are performed due to lack of indexes. This can result in large spikes in the bill for serverless instances. It would be great to have some RPU estimator to calculate the approximate RPU's a particular operation would generate.
10 votes -
Investigation Buckets (dropdown menu) to enable predefined set of MongoDB & Hardware Metrics to investigate certain Data Layer SLAs
We have many metrics under "MongoDB Metrics" & "Hardware Metrics". User will have a good idea which metrics to enable while troubleshooting certain requirements.
E.g. User is investigating current lags in the data Layer. User has to select all the metrics that would help them get the data they are looking.
We can help the customer bit more by provide buckets like.
Options ( select one )
1. Investigate Lags
2. Investigate IOPS
3. Investigate Replication
4. Investigate Search Index
... and etc..This will pre-select certain metrics from list of Mongodb & Hardware metrics which will give them all…
1 vote -
Bulk explain() command
I want to be able to run the "explain" command for multiple database operations so that I can quickly estimate the RPUs and WPUs for my workload (instead of having to do it one by one for each operation).
2 votes -
dynamic auto-downscale (configurable)
MongoDB have automatic fixed limit for auto-downscale (50%) but sometimes is neccessary downscale with other amount, ie: in our case in the night the clusters have 55%, 60%... will be productive for us that the % limit for downscale will be parametrizable.
If I configure 60% I know that all the nights the cluster auto-downscale to previus instance.5 votes -
tgw support for Atlas
Can you please provide TGW support for Atlas? We are using confluent.io kafka with TGW, and found ourselves caught up in situation where kafka has no direct access to atlas, both our EKS and kafka are directly connected to Kafka, but there's no way for kafka to access atlas, because EKS and atlas are connected over vpc peering. We do not take interest in PrivateLink. Our Kafka needs direct access to Atlas because we are running the mongo source connector. Only viable solution now is to run the mongo source connector on our EKS, which while works defeats the purpose…
2 votes
- Don't see your idea?