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
-
Autogenerate a secret for AtlasDatabaseUser if none provided
I'd like for the controller to make a random password at the point of submitting the request, the password itself is not relevant to me as it'll be included in the returned connection string to be consumed by the applications themselves.
More details found on the Github Issue: https://github.com/mongodb/mongodb-atlas-kubernetes/issues/1370
4 votes -
MongoAtlas Orga - Maximum number API keys exceeded
We have detected in our organisation that the limit of API keys has been reached. This is currently affecting our project teams in terms of resource distribution, so we are asking for an increase in the quoter in the short term.
Problem: We can't create keys and also delete them. The problem is that the key does not have an owner. Only org owner can delete this key. They did but this is only a reference deletion.
Alerting: Condition for alerting is not there
What we want to achieve:
- Transparency for the org owners about what the limit level…4 votes -
Use cluster id as app_id when creating a trigger via terraform
We would like to specify the cluster id as appid inside the mongodbatlasevent_trigger resources in order to match the trigger creation available via gui
4 votes -
Not even able to close my free account
Hi I have opened my free account and now i am not able to close this account. Even there are no available clusters showing on my account then also Project0 is not getting deleted. kindly help to close
4 votes -
Atlas DNS name more than 23 characters from the cluster name.
Allow users to have longer DNS name from the cluster name. Currently, Atlas cuts the first 23 characters from the cluster name and the users can't check the cluster name inside the mongo shell.
Example:
Cluster name longer than 23 characters : xxxx-us-east-1-multi-use-1
DNS name : xxxx-us-east-1-multi-us.xsj8t.mongodb.net4 votes -
API change date format for log download
While programming a script to download the activity feed and audit logs, we found out that the date format which is accepted for API calls does not match. While the Activity Feed is fetched with a date in the ISO 8601 format (&minDate=2024-01-24T12:30:06.415944), the audit log accepts only an epoch timestamp (...?endDate=1702632210&startDate=1702625017).
This causes several conversion issues when automating log-fetching. To avoid these issues, we suggest changing the API call to use the same date format.
4 votes -
Support tagging individual replicas in the cluster
Thank for the support for the tagging at the cluster level during database deployments( https://feedback.mongodb.com/forums/924145-atlas/suggestions/43032180-support-for-tagging-clusters-in-atlas)
However it would be useful to have support for tagging individual replicas in the cluster.
For example., we want to deploy the same app as two deployments tagged as tier-1 and tier-2, with tier-1 deployment service accessing tier-1 tagged readonly replicas and vice-versa.
4 votes -
Reference existing third party integration in alert configuration notifications
Provide a mechanism that enables referencing an existing atlas third party integration when using the alert configuration resource to create or update a third party notification.
This is useful when a third party integration is imported or accessed through a data source, meaning the api token is not available. An example of this would be Slack integration as it has to be created through the Atlas UI using OAuth2, so the api token cannot be accessed in the terraform configuration.More details in: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/1074
4 votes -
Sync Atlas alert configurations between projects.
Since we can export all Alert configurations from a project, add the ability to sync alerts on all the projects to be consistent with notifications/alerts.
Alerts can be created individually but not in bulk. Please enhance the Mongo Atlas API for the following functionalities:
- The ability to sync all alerts from one project to another.
Thank you
4 votes -
Manage Feature Compatibility Version (FCV) flag separately from version upgrade
When performing a major server version upgrade (e.g. to MongoDB 7.0), Atlas automatically set the Feature Compatibility Version (FCV) flag to the same version.
We would like to see this be a two-step, i.e.
1. When upgrading to 7.0, Atlas keeps the FCV pinned at "6.0"
2. 1~2 weeks after upgrading, Atlas reminds us increase the FCV to "7.0", i.e. once we've seen it running stable.We had a major production-outage issue in upgrading to MongoDB 7.0 and because of the current Atlas FCV behavior we could not downgrade back to 6.0.
We understand that some users don't care about…
4 votes -
Manage federated database views via Terraform
The mongodbatlasfederateddatabase_instance resource allows managing tables in the federated instance, but it does not allow us to manage views. Please update the provider so we can also create and manage views
4 votes -
better index usage
Currently most of our indexes show a usage of <1/min which isn't very useful. If I hover over them I can see the usage which might say 20/day but I would prefer to not have to hover.
4 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 -
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 -
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 -
CDC
Wanted to have the CDC information stored as json or parquet in a bucket storage for retrieval at a later point to understand the data transformations that has happened in our Application Transactional collections.
4 votes -
Remove the requirement to have an API Access List CIDR before being able to manage backup schedules
The issue is described in this github issue, specifically in the linked comment: https://github.com/mongodb/terraform-provider-mongodbatlas/issues/222#issuecomment-855905952
Here is the requirement as described in the API docs: Remove All Cloud Backup Schedules
Removes all cloud backup schedules for the specified cluster. "This schedule defines when MongoDB Cloud takes scheduled snapshots and how long it stores those snapshots. To use this resource, the requesting API Key must have the Project Atlas Admin role and an entry for the project access list."
https://www.mongodb.com/docs/atlas/reference/api-resources-spec/#tag/Cloud-Backups/operation/deleteAllBackupSchedulesOur request is that the requirement to have an API Access List to manage backup policies be removed.
At the very least,…
4 votes -
Provide option to remove hidden node in NVMe clusters
NVMe clusters default to add a hidden node where backups are pulled from. This is due to the reduced durability of NVMe volumes. In cases where durability isn't a concern, I would like to disable backups and remove the hidden node altogether.
The UI currently provides the ability to stop backups by modifying the backup policies (see attachment). However, I cannot remove the hidden node which is simply incurring extra cost.
Obviously there would need to be a major warning provided to the user, but this is not unprecedented in industry. AWS has spot instances that are quite successful.
My…
4 votes -
disabling snapshots
When we disable de snapshot from one cluster, the following message is shown in the same page but it does not appear at the page that shows the changes that are being made
It would be better if this message were also at the second page (as image uploaded)
Please Note: This action is irreversible. Turning off or altering your type of backup will delete all of your existing snapshots immediately. If you want to keep old versions of your data, visit the backup dashboard and download your snapshots
4 votes -
MongoDB Connection Pool Proxy
Currently there is no Connection Pool proxy supported by MongoDB.
With the ever increasing use of serverless and containers, clusters will need to be over provisioned in order to account for the increased connection counts.
A better solution would be a Connection Pool proxy allowing for a many-to-one relation for connections to MongoDB.
In the case of Lambda, this would reduce the number of Zombie connections (Connections that have been terminated on the Lambda side but are still open on the server side.)
4 votes
- Don't see your idea?