Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1364 results found
-
Better alert trigger for index suggestions
The current alert trigger for index suggestion is described here: https://docs.atlas.mongodb.com/reference/alert-conditions/#host-alerts
"If the query targeting ratio for a host consistently exceeds 10,000 for a period of 10 minutes, Performance Advisor checks the host for inefficient queries and possible indexes to improve performance."
Firstly we have issues with alerts constantly going on and off every few minutes if the query ratio is fluctuating around the 10k mark.
Secondly, we often do not get alerts for worthwhile index suggestions. We run a multi-tenant platform. We have big clusters with hundreds of databases/tenants and thousands of collections. A huge amount of our queries…
8 votes -
1 vote
-
Support for customer-managed keys (CMK) on the volume-level instead of Encryption-at-Rest
For some customers managing a set of low-latency workloads is crucial, so volume-based encryption using their own KMS encryption keys is preferred over the encryption-at-rest feature of the WiredTiger storage engine. https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html
The support is required for clusters, their backups and Atlas Data Lake.3 votes -
new Role Paying Org Owner
For CrossOrg Billing - should allow this role to see billing details of linked orgs (IN linked Orgs)
1 vote -
Zabbix
We should have Zabbix integration to monitor the performance of MongoDB Atlas.
Zabbix is OpenSource popular monitoring tool available and many of enterprise organizations use this tool.
Please add Zabbix in Integrate with Third-Party Monitoring Services.
8 votes -
docsexamined
in profile tab, there are only keysexamined, nreturned we can see.
If we have "docsexamined" , it would be good to check whether the queries are well tuned or not at first glance.1 vote -
point in time
Create option to change the database name of target when you use point in time restore.
This allows to refresh environments in development and staging with one click.1 vote -
"Replica set elected a new primary" and other information alerts are not recorded in Atlas
Alerts like the "Replica set elected a new primary" are considered informational, they trigger an email being sent but the alerts were not recorded in the open and closed alert page in Atlas UI. Also they cannot be retrieved via API.
This is pretty confusing as you'd imagine once the alert is triggered, it'll be recorded in the page where all the other past alerts are kept, the concept of informational alert is vague and never properly communicated to users.
Please record all types of past alerts in the UI and make them accessible via API.8 votes -
Please add a debit card payment method.
Some countries use debit cards primarily so it would be great if we could have that option as a payment method.
3 votes -
Ability to get collection stats via the API
e.g. list collections, collection size, collection indexes, etc.
3 votes -
Derisk cluster changes that cause restarts
Problem statement:
Some configuration changes cause rolling restarts of the cluster (e.g. audit filter, enabling x509 auth). It is not immediately obvious which changes will cause restarts and for a big cluster, this is a huge hit to performance due to cold caches.Ideas:
1. Block planner changes which would cause restarts until maintenance window (maybe with an opt-in for this, + notification that the config change is blocked)
2. Throttle replica set restarts, allowing time for the cache to be warmed on secondaries (would require mirrored reads in 4.4 to be effective)
3. Properly document what changes will cause…2 votes -
Uptime report for Atlas cluster
It would be great to have an uptime report be it weekly or monthly basis which can be extracted and presented anyone who would like to have an high level overview.
10 votes -
Delete one (last)endpoint deletes private endpoint service
If no further endpoint is associated with Private endpoint service, making a call to api resource https://docs.atlas.mongodb.com/reference/api/private-endpoints-endpoint-delete-one/ will delete the endpoint as well as service.
1 vote -
Add Terraform support for Realm Apps
Realm Apps (https://docs.mongodb.com/realm/get-started/create-realm-app/) can't be managed via Terraform. This would be a great addition to the provider!
32 votes -
Trigger execution details
It would be very useful to have some details provided in Atlas to trace the execution of the trigger, like the _id and operation type at a minimum. When a trigger executes the only information we see in Atlas is [
"Sent to AWS EventBridge"
].7 votes -
Add Atlas users to existing teams even though the Atlas user is still pending invite
Currently when we send invite emails for the organization we have to wait for the users to accept the invite before we are able to configure project level permissions. This often creates confusion and bad user experience; when users first sign in they are anticipating to see their projects but instead they see nothing until configuration is finalized.
Please make it possible to add users to teams which are still pending invite acceptance so the user experience is more seamless and less confusing.
9 votes -
Add date added and date updated to Network Access IP table
The network access table should have a way to see the date an IP was added and if/when is was last updated. This will give better insight and control over company users add and maintain their IPs when only whitelisted access is allowed.
1 vote -
Transactions support for Merge operation in aggregation pipeline
Hi Team,
can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictionsWe have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.
The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.
thank you
6 votes -
Expiration Date on Database Write Access
Just like the Network Access where you can allow an IP address to be used for connection to the database for a short time, I would like that same feature for Database Access write permissions. I would like to temporarily give someone permissions for X hours and after that time period, it reverts back to the original state, such as read-only access. I have to temp give someone permissions during release nights to perform operations.
Example: "This entry is temporary write access will be deleted in 6 hours and reverted back to the original real-only state."
2 votes -
Unpause Cluster for X Duration
Allow customers to specify the duration they wish the unpause the cluster before Atlas will automatically re-pause the cluster. Namely for use cases where development / testing is going to commence and customer wishes to ensure cluster is paused again to reduce Atlas spend.
Example: QA Tester is performing Atlas testing and wishes to unpause cluster, but only for the next 10 hours
Current Atlas Control Plane: "Pause Cluster"
Future Atlas Control Plane: "Pause Cluster for __ minutes (or hours)"
This is similar to how customers can create temporary database users that are only active for X number of hours.…
1 vote
- Don't see your idea?