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
-
Improve "Host has index suggestions"" alert by including the hostname
The "Host has index suggestions" alert notification does not contain any reference to the host/deployment that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.
8 votes -
Deactivate use of charts on org-level
As charts meta data are processed only on US servers, a toggle to forbid the usage of charts for autonomous teams would be helpful, considering GDPR requirements
2 votes -
Project migration should not require org-owner rights
Before project migration from one org into another, we have been told to define the responsible users in both orgs with org-owner rights. There should be no need at all to permit org-owner rights on project migration. The org-owner-level should only be reserved to the very smallest group of people (admins) necessary. Project owner level should be enough for a migration of projects.
1 vote -
Count
Whenever a query is fed into the filter search box, ensure that the count of the result is also provided somewhere above the result of the query.
2 votes -
Add a grace period between a failure to obtain a certificate and the cluster shutting down.
If you set up encryption at rest on Atlas using an external key provider, such as an Azure Key Vault, then a link is created between being able to access the key vault and the status of the MongoDb cluster.
For example, on the 28th September, there was an issue at Azure (SM79-F88) and for over 2hrs around 19% of all authentication processes in Europe failed. This included accessing the KeyVault used by our MongoDb cluster. As Atlas checks the keys roughly every 15 minutes it failed to obtain the key at the beginning of this period and our cluster…
1 vote -
Option to configure an on-prem hidden replica set member for an Atlas replica set
As described in https://docs.mongodb.com/manual/tutorial/configure-a-hidden-replica-set-member/, on-prem mongodb deployments allow to configure a hidden replica set members which are good for workloads with different usage patterns from the other members in the replica set. It would be useful to have similar functionality for Atlas replica sets.
In fact, to elaborate, being able to configure an on-prem hidden replica set member for an Atlas replicaset will help in meeting regulatory requirements where organisations are required to host a near real time mirror of data on on-premises.3 votes -
Allow customer encryption key validation time interval
Currently, Atlas has a 15 minute interval where it checks access to remotely stored Customer Managed Encryption keys for the custom encryption at rest feature.
This value is not changeable, and it implies a problem: access to encryption keys can be lost for longer periods than 15 minutes without that implying that the key has been invalidated by the customer.
A perfect example of this was the recent Azure AD global outage that prevented all authentication to the Azure platform for about 3 hours (complete outage description: https://app.azure.com/h/SM79-F88/691d78). While the key used for one of our clusters was not…
9 votes -
Make RSS feed entries more consistent
We would like to consume your status RSS feed to help us programmatically warn our internal groups when you have issues in a given region. One problem that we see with this is that the messages that we have seen posted are pretty inconsistent with how they specify regions. Examples: Oregon (us-west-2), AWS EU-WEST-2, AWS Sao Paulo. It would be very helpful to us, and probably your other customers as well, if the messages were more consistent in how they reference AWS regions.
5 votes -
Project Alerts: show details about "Closed Alerts"
In "Project Alerts" we can only see certain details about "Closed Alerts," e. g. for an "Index Suggestion" we can only see the timestamp and the fact, that there was an index suggestion. You can't see what the specific suggestion was. So if you look through the history of alerts, you cannot tell if for multiple alerts it was always about the same index to be created, or whether it was for different indexes.
Likewise, for "Daily amount billed ($) is above threshold" you can see that the threshold was exceeded, but you can't see what the specific billed amount…
2 votes -
My entire team receives the billing info every month.
Billing should be limited to organization owners only and not viewable by the entire organization.
6 votes -
Auto-build indexes for slow-queries
Add an option for Atlas to automatically build indexes for slow queries instead of having to manually check slow queries and build the indexes.
1 vote -
Add the ability to trigger alerts for testing purposes
It would be useful to have a "Test Alert" button for each configured alert in order to integrate and test alerts with third-party systems. Otherwise, it is difficult if not impossible to determine what the alert will look like until it is triggered.
34 votes -
1 vote
-
Implement create-before-destroy when migrating NVME instances
When triggering a cross-region migration Atlas immediately degrades a cluster by going to N-1 nodes prior to creating a replacement node in the new region.
When using NVME instances, this violates the agreed upon replication depth. Once the NVME instance in the source region is destroyed, there are only N-1 copies of the data left, as there is no EBS backing.
NVME target instances should be brought up as {hidden=true, priority=0} until leaving STARTUP2 and entering SECONDARY. Once this occurs, the target instance should be brought to {hidden=false, priority=P}, and a source instance hidden, removed after a quiescence period, and…
2 votes -
Manually replace / restart virtual machine
Allow to replace / restart the underlying virtual machine of a node.
Sometimes this is all that is needed to get a cluster out of an unhealthy state. Currently, only support seem to be able to do this.
3 votes -
An API endpoint for Live Migration
When customers have dozens and hundreds of clusters to migrate from on-prem to Atlas, automation is very important and Live Migrate is not supported via API today. Mongomirror is a shell command that can be leveraged for automation but having Live Migrate available as API will be a great enhancement to CD/CI pipeline.
2 votes -
export list of database users
For audit purposes, I would like to have an export function to create a list of database users. The current view of database access contains the name and the associated roles. Having this information as a csv or pdf file would make it easier to deliver this access information to compliance teams.
3 votes -
Have the ability to configure cache_size
I'd like to see the ability to modify the cache size setting for a given cluster. MongoDB has a straight forward pattern of using 50% of the memory for cache size. However, Atlas has scaled that down to (RAM - 1 GB) / 2. Apparently that was done to allow for extra memory for other Atlas features like BI Connector and Atlas Search. However, we currently aren't using those features, so we're stuck with the lower cache size.
It would be great to have the ability to get the most of our servers instead of being limited based on logic…
3 votes -
Allow bulk changes to alerts - e.g. changing slack channel
Changes alerts is really painful. For one thing, pressing the Enter key doesn't close the dialog and nor does pressing Escape.
This makes it really painful to change something simple like the slack channel used for alerts.
2 votes -
Improve database access tab
Managing permissions for users is a pain right now. It's a lot of clicks, it quickly becomes messy and sometimes the modal closes without saving changes.
It would be a lot easier if we could import a CSV containing all permissions for a certain user (user name, permission type, database name, collection name)
5 votes
- Don't see your idea?