Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1360 results found
-
Add storage class configuration option to Cloud Backup snapshot Export to S3
Setting the desired value for
x-amz-storage-classheader for the S3 PUT Object for snapshot export so that exported snapshots can be put directly to the desired storage class without any custom lifecycle rules and wait time on S3 side.6 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 -
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.
5 votes -
South Africa Region
Please add a deployment for MongoDB serverless instances in a South African region (either on AWS or Azure). Like the UK, South Africa has strict data privacy and residency laws and regulations, and a local serverless deployment would go a long way in unlocking domestic business.
1 vote -
Use wildcard databases in user role privileges (like collections)
Use wildcard databases in user role privileges (like collections)
17 votes -
Better auditing of App Service actions in Activity Feed
The Activity Feed should show who has created an app in the App Services. Currently this is not the case, instead you will find the following information in the Activity Feed:
A user(or Code Deployment) has deployed changes successfully to an App Service.
7 votes -
limit the size of tmp files created as part of $sort stage
Our docs says, "Starting in MongoDB 6.0, pipeline stages that require more than 100 megabytes of memory to execute write temporary files to disk by default."
These 'temporary files' can take up ALL the disk space if auto storage scale isn't turned on and crash the cluster.
1 vote -
Expose billing usage on free tiers
An email was just sent out with the following information:
As a user of the App Services free tier, we have some exciting updates for you. After receiving your feedback, we will be moving to a daily free tier model that provides more clarity and makes it easier for you to track your usage.
In July, you’ll see an updated App Services UI dashboard that reflects this daily free tier usage rather than the current monthly model.
In this new model, the following daily free tier limits will apply:
• 50,000 Requests
• 0.5 GB of Data Transfer
• 25…1 vote -
Atlas Console option to start the resynchronization of a primary node
It would be great if during an automatic maintenance process, considering the restart of all nodes you were able to find a button in the Atlas Console to start the restart of the primary node, so that way you can select this process in a less operative window and avoid a severe business impact in your organization.
1 vote -
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 -
Ability to "Mass Kill" slow running queries
Currently, Atlas has a "Kill Op" option which is useful to kill single long-running queries.
When upgrading to MongoDB 7.0, we were faced with a situation where the Slot-Based Query Engine (SBE) was causing 1000s of queries to execute slowly, we wanted to kill them all, but it was more than a human could do by clicking "Kill Op" 1-by-1. Hence a "Mass Kill" feature which kills queries longer than X seconds (X is configurable) would have helped us greatly in an outage scenario. We ultimately rebooted our cluster to kill queries, then manually implemented a script which did this…
8 votes -
Parity of metrics between Atlas UI and Prometheus integration
It would be great if any metrics that are available in the Atlas UI are also available via the the Prometheus integration, especially since the metrics in the Atlas UI get coarse-grained after a while.
For example, in a recent incident it took us a while to do some preliminary investigations, and we wanted to confirm by looking at historical values for the metric "Operation Execution Time".
Unfortunately the chart in the Atlas UI was already too coarse-grained and the metric also does not seem to get exposed via the Prometheus integration.
10 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 -
Alert notification for new cluster created in the project
Greetings, Support
After looking over the alert settings, I discovered that there aren't any alarms that can be monitored to be informed when a new cluster is created on the present project. Please include a notice about the future release, as it directly correlates with and impacts the price and invoicing.(Confirmed with support as there is not such alerts in Atlas with the current settings and case:01298603)
2 votes -
Export logs to S3 at the organization level rather than project level
Currently if we have to export logs to S3 we need to enable log export to S3 at project level. If I multiple projects then same things needs to be done, there should be an option to send logs to S3 on organization level when setup should send the logs to S3 bucket with path name (projectname+'/'+clustername).
3 votes -
Allow multiple VPC CIDR ranges in Peering connection
Allow multiple VPC CIDR for a single Peering connection from Atlas to AWS.
Our AWS account has two CIDR ranges for a single VPC. Atlas peering connection only allows connection to a single CIDR range.
Today, I need to create a separate private link connection to be able to connect to the second CIDR range.38 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 -
ServerlessPrivateEndpoint should allow the consumer to specify a security group
Currently, the AwsPrivateEndpointConfigurationProperties object allows the consumer to specify a VpcId and SubnetIds, but it does not allow us to specify a custom Security Group into which the AWS-side VPC Private Endpoint should be added.
The ServerlessPrivateEndpoint custom resource also does not create a security group for the endpoint, instead just dumping it into the default security group for the VPC. I can see no way to customize this behavior.
1 vote -
Within Atlas, create service to allow project owners to schedule shutdown/start up times of cluster to reduce hosting costs
Request to provide an enhancement to the Atlas service to allow project owners to schedule shutdown/start up times of clusters(or databases) and provide some notification of a successful shutdown and startup. This should be a feature with the Atlas UI and API.
This will allow teams that have non-critical environments to effectively "turn off" and freeze the state of a cluster in order to reduce hosting cost during off hours. This can provide a better value proposition for existing customers and a selling point for new customers, without having to introduce a third party tool that requires additional configuration and/or…
2 votes -
Support tags in terraform-provider-mongodbatlas mongodbatlas_project
terraform-provider-mongodbatlas mongodbatlas_project doesn't currently support tags.
2 votes
- Don't see your idea?