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
-
Atlas - Preferences - My Date Format - allow 24hr
We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks
4 votes -
Add boolean for applying changes only during maintenance window
Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.
E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.
See DocumentDB as an example for this feature.
https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html3 votes -
Mongodb Atlas Malaysia AWS regions
Malaysia region is poised to be the largest AWS region and it is pertinent that Atlas can support it for south east asia. Writing in to petition of this region's support.
3 votes -
Push Atlas org events and projects to S3
Similar to cluster logs being pushed to s3 feature, if a feature to push organization, project and cluster events to s3, our event ingestion pipelines could be simplified significantly. Without the feature we are forced spin up event ingestion agents and make them reliable/available. These ingestion agents source the events via API and publish them to cloud watch logs, that are eventually fed into our observability stack. If the events can be pushed into s3, we can eliminate multiple intermediate components.
3 votes -
Backup Compliance Policy to enforce "Snapshot Distribution"
Backup Compliance policy currently can help with protecting snapshots in other regions using "Keep all snapshots when removing additional snapshot regions" option to prevent users from deleting backups copied to other regions. However we do not have a way to enforce that snapshot backups are copied to all regions where a primary could be elected.
In order to achieve faster RTO having backup snapshots in all regions where a primary can be elected is important. Hence the feature to enforce copying backup snapshots and oplog backups to other regions via backup compliance policy is very important to compliance mandates and…
3 votes -
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
3 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…3 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
3 votes -
Make the to delete indexes endpoint public
In the Performance Advisor, the recommended indexes to drop are only avaible throw the cnsole. We would like to have this information available from the API.
3 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.net3 votes -
Safe mode to pause non-essential changes
I'd like to be able to put the cluster into a "Safe Mode" during an incident.
For example, I'm responding to an incident or I suspect something's fragile or breaking, and I don't want any scheduled activities to make it worse or distract me. I also don't want to have to know what changes are scheduled, I want to pause them all regardless.
This would pause any scheduled or non-critical changes, like upgrades, building indexes, probably resyncs, etc.
But it would keep running cluster-safety/health-supporting mechanisms like auto-heal, and probably backups.
And it would put up a banner on the cluster…
3 votes -
BI connector host name via API call
BI connector hostnames in the Atlas UI: https://www.mongodb.com/docs/atlas/bi-connection/ is not supported via API , Currently, customer has to manually copy and store the values to be reused by other applications. The customers are hoping to get these values in an automated way, for example with API calls or SDK.
3 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
3 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…
3 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
3 votes -
Retrieve latest/max oplog timestamp via the Atlas Administration API
At the moment the latest/max oplog timestamp can be retrieved via the Atlas UI in the backups section for point in time restores. This feedback post is to make this information available as part of the atlas administration api.
For example, in the UI it states:
You can only restore up to this oplog timestamp: 1692580549 and this increment: 1.
Would be good to have this value available to be retrieved via the API for restores requiring oplog timestamp values in this format.
3 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…3 votes -
Datadog integration for AP1 region
I am using Datadog region AP1 (Japan) and I learned that Atlas doesn't support the region for the integration.
It would be really great and helpful if the integration supports the AP1 region.
3 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
3 votes -
Support migration of existing projects, clusters, ... to be CloudFormation managed
When MongoDB::Atlas::* resources are created and the specifed project, cluster, ... already exists, then these resources should not raise an error on resource creation but use the existing project, cluster, ... and apply the given configuration. In other words, the Create event that is initially sent by CloudFormation should be handled similar to an Update event but return the physical id of already existing resources. Apparently, this behaviour should be enabled by an opt-in flag.
3 votes
- Don't see your idea?