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
-
Create TTL index based on local timezone as opposed to UTC time
Create TTL index based on local timezone as opposed to UTC time
4 votes -
Database Access History: sort and export
Would be nice to export the database access history and/or sort by a column.
4 votes -
Global Cluster Configuration Warning & Guardrails
The Problem: We intended to perform a simple M30 to M40 scale-up but accidentally enabled the 'Global Cluster Configuration' option in the UI. This unintended action triggered sharding, leading to a severe and unexpected two-hour outage that resulted in revenue loss.
The Feature Request: We need to implement a more robust system for these critical changes to protect customers from operational mistakes.
A good solution would include:
Clear Warning Message: When a user attempts to activate the 'Global Cluster Configuration' option, a prominent and clear warning should appear, stating: "This action will initiate cluster sharding and may cause a service…
3 votes -
Support Billing Alerts Based on Usage Date
Currently, Billing Alerts in MongoDB Atlas are triggered based on the Billed Date, not the Usage Date.
This often results in alerts caused by delayed reporting from cloud providers, rather than actual real-time usage spikes.I suggest adding an option to trigger Billing Alerts based on Usage Date.
This would make alerts more accurate, reflect actual activity, and help users respond promptly to unexpected cost increases.3 votes -
Granular permission for project level
Atlas project-level roles (like readWriteAnyDatabase or readAnyDatabase) apply universally across all clusters within the project.
We understand the current limitation where roles like readWriteAnyDatabase or readAnyDatabase apply across all clusters within a project. However, for our use case, it is critical to assign granular database permissions per cluster for AWS IAM roles—especially to avoid unintentionally granting access to sensitive clusters like Unification.Given this, we would like to formally request this as a feature enhancement. Specifically, the ability to:Ensure isolation of role permissions per cluster within the same Atlas project. We also opened a case 01493221 for this with support
3 votes -
Include Project Activity Feed logs in Push-Based Log Export
With the "Push-Based Log Export" option available in a project, only specific types of logfiles (mongod, mongos and mongod_audit) are being written to the S3 bucket. It would be useful to also have the option of exporting Project Activity Feeds to the S3 bucket.
3 votes -
logs push to s3 over private link
Currently push to s3 feature transmits data over internet, due to possible presence of sensitive data in logs and to address security concerns push to s3 feature should support pushing logs over private link.
3 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 -
Include more actionable data in Alert emails
Currently the alert emails just link to the profiler page with nothing selected. This makes it guess work if there are multiple items in the profiler to examine. If you are unable to check the profiler within 24 hours of the email, no data could exist specifically for the alert email.
It would be much more actionable if the email alerts mentioned the collection that was being queried, the appName that triggered the query, and a direct link to the query in the profiler showing complete details of the query that triggered the alert.
This would make triage near instant…
3 votes -
Ability to quickly filter backup activity from the project activity feed
The activity feed is often clogged with backup activities. It would be extremely useful to be able to quickly filter out the common 4 or 5 project activities that are related to a backup snapshot being taken.
3 votes -
Suggestion to make the Organization Role Mappings page easier to navigate to
Make Organization Role Mappings page in the Federation Management App quicker to navigate to. Currently the quickest way is to click the "Create Role Mapping" from the Overview page under "Optional: Set Up Advanced Settings" and then click Cancel.
If the "Optional: Set Up Advanced Settings" box is not longer available in the Overview page, you'll have to click the Organization tab from the side navigation bar > [Organization Name] > Create Role Mapping > Cancel in order to reach the Organization Role Mappings page.
3 votes -
AWS ME Central Region Support
I have an ECS cluster in AWS me-central-1 region and I am not able to establish a peering connection with my AWS VPC as me-central-1 region is missing in the options. When will this option be available?
3 votes -
Option to Enforce Certain MFA Methods
Allow certain MFA methods to be disabled for our Organization.
e.g. we don't trust SMS or Email so want to force our users to only use Google Auth / Security Key/Biomeytric or Okta.3 votes -
Option to deploy the databases with pinned version.
Atlas by default picks the latest patch when we create the databases for any major version. It would be helpful if the customers can choose and control the minor version of the databases(including patch version) when we deploy the cluster. For example: We want to deploy the databases with 4.2.19 but the Atlas is automatically creating 4.2.22
This will help us identify any application dependencies on any particular patch version during our migration to Atlas, also this will help us test the patch versions in dev/lower environments before we promote the version to production.
This feature is important for us…
3 votes -
Display Total Cluster Data Size in Atlas UI
Atlas doesn't display the total data size of the databases hosted on the sharded cluster. This feature was available in Opsmanager and will be very helpful for the DBA's and the product development teams to glance at the data size of the cluster.
Attached the screenshot for example.
Nice to have or display the size of each database and also display the historical datasize metric for each database in a sharded cluster.
3 votes -
Atlas shards with different clusters tiers
For solutions of hot and cold storage, there is at least 2 options:
- Online archiving
- Hot and cold cluster (using a trigger and datalake)
But these solutions have limitations (https://www.mongodb.com/docs/datalake/limitations/)There is another solution: using sharding.
We can set shards like so:
1 shard: Data from the last 2 months -> Hot data
1 shard: Data between 2 and 24 months -> Warm data
1 shard: Data more than 24 months -> Cold dataThe usage pattern: 95% of the accesses/queries go to shard with the hot data.
On Atlas, we need to set the same…3 votes -
Test maintenance effects
While Atlas provides the 'test failover' feature, this only takes effect on the primary of each shard. Customers who run large sharded clusters on Atlas require testing the effects of a full maintenance patch that would restart all mongod's and mongos's, config servers, etc. This feature is a request to improve the chaos engineering features of Atlas.
At present, customers are being advised to change the TLS version of the cluster which could force restarts of all mongod's, mongos's and config servers. While this may be acceptable in non-production environments, it is unlikely in production environments.
I believe there's an…
3 votes -
WriteOnly DATA API
Hello,
We have a similar need as the one in ticket 44935186, but we would like a WriteOnly (no delete nor read) access to the API so a partner could push data in a collection without being able to read it
Thx and have a nice day!
3 votes -
Copy/move snapshots from a source to a target cluster
It is recommended that restoring a cluster must either:
1) Restore to a new Atlas cluster and reconfigure your application to use that new cluster once the new deployment is running, or,
2) Ensure that the target Atlas cluster cannot receive client requests while you restore data.
(src https://www.mongodb.com/docs/atlas/backup/cloud-backup/restore/#prerequisites)While doing a PIT restore with the source and target cluster being the same, our clusters have gone into a "down" state 3 times due to obscure errors, opslog not being large enough, or writes happening to the cluster during restore.
We would like to take the safer route of…
3 votes -
AWS CMK rotation alert should be changed from 90 to 365 days
Originates from https://github.com/mongodb/terraform-provider-mongodbatlas/issues/805#issuecomment-1241569555
Short: The created default alert for encryption key rotation is configured to 90 days, also when using AWS KMS CMK. The automatic rotation for CMK is 365 on AWS side. So, I would vote for creating the default alert with 365 days, when AWS KMS CMK is selected.
Otherwise we get false alerts, as we rely on the automatic rotation of AWS KMS.
3 votes
- Don't see your idea?