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
-
when making backups don't have the banner say "deploying your changes"
I was very confused recently when I logged in and saw the message "We are deploying your changes" despite nobody having made any changes to the cluster. Apparently what was happening was our scheduled backup was happening. This was a really confusing message to be seeing and resulted in a support request to work out what changes were being made.
It would be much better if the message when a scheduled backup was happening was more clear about what is happening and less misleading.
1 vote -
selected option scroll disappear on click to scroll
In Atlas within Insert Document: When using the data type selection, clicking on the scroll bar or arrow causes the select option to disappear. Possibly increasing the size of the select option depth to where scroll is not needed may help.
1 vote -
Deletion Protection
Customer suggested protection from Cluster deletion similar to AWS RDS
https://www.amazonaws.cn/en/new/2018/amazon-rds-now-provides-database-deletion-protection/
TL;DR - a notification when a user tries to delete a cluster, that "this cluster is protected, if you need to delete please visit the console to enable deletion"
This would be a critical piece of functionality where roles/permissions are not sufficient.
7 votes -
Use existing main Integrations Slack key for all alerts automatically
When updating the main Integrations Slack key, the token changes is not automatically deployed to the mongo alerts created earlier (slack notification). This feature would be helpful as at this time we have to update manually all alerts configured with a new token.
7 votes -
Refresh button like "Contact Team" button
There should be a refresh button like the "Contact Team" button on the bottom righthand corner in the "database" section, so that users don't always need to scroll up and down, just to update their schemas
1 vote -
Encryption at rest with our own keys - Manage alert and shutdown parameters
It would be interesting to improve the encryption at rest feature in order to be able to define the alert parameters in case of unavailability of the key as well as the delay before a Replica Set fails.
for example. I want to be alerted if my key is not available x times in the last 10 minutes and stop the replica game after 60 minutes if the situation is not resolved. This makes it possible for the support team to take corrective action without causing downtime.
9 votes -
Atlas should allow deployments of non-voting members on region for tiebreaking purposes
No allowing non-voting members criples the ability to combine regional failover, while keeping the application servers in just two regions, where the event of having a third region primary may imply high latencies, that impacts SLOs.
This particular severe for architectures that rely on 2 main datacenters (regions) and use a 3rd for tiebreaking purposes only.
1 vote -
Applying an index suggestion should remove redundant indices automatically
An index suggestion for a compound index should check if it makes an existing index redundant. If so, it should remove it automatically after adding the compound index, or at least add the option to do so.
1 vote -
Ability to read the logs in old format
there should be option to download log files as native format, as we need to download multiple tools to get it to normal!!
1 vote -
Feature Request: DNS record per zone for global cluster
Today Atlas creates a single DNS record for the global cluster which has SRV records pointing to all servers in the cluster across all zones.
This causes issues when a service hosted in US tries to use this DNS record as it now connects to every server in the SRV list of the DNS record. We ideally would want the US service to connect to its closest mongos router (US zone) and not all the mongos routers as it is unnecessary waste of resources. Our workaround today is to manually pick the servers and build the connection string in old…
1 vote -
Add an alert or notification option for every "pause" or "resume" cluster action
Add an alert or notification option for every "pause" or "resume" cluster action
14 votes -
Change Display name for clusters
Ability to change display name for clusters.
1 vote -
PITR should allow to choose which snapshot to use as base
PITR mechanism does not allow the user to choose which snapshot to use as base before replaying the oplog. Given that Atlas does not validate the snapshots after they have been taken, the user ends up needing to setup their own validation process. That alone is not a problem. However, when one needs to use the PITR mechanism, not being able to select a previously validated snapshot may lead for PITR restores to use unvalidated snapshots.
Either Atlas should enable, uppon choosing, the validation of snapshots right after they are taken, or allow the selection of valid snapshots (snapshots taken…
2 votes -
Atlas Screen Navigation
In both Atlas & Ops Manager, on screen navigation is not good. When I click an icon or item, the screen shows different layouts for each click.
For example, if I want to see Billing info, I have to click little 'mongo logo' icon, then Bill menu appears.
Then if I click All Cluster item, the Bill menu disappears and left navigation/ menu also disappear.
I have click multiple times, different icon, or menu to get what we want.
There is no consistency in the screen appearance when we click an 'icon or menu'. Each click shows different screens.
Same…
1 vote -
Setting up the New MFA/Adding a disabled user back to project
The whole process of setting up the new 2FA or MFA is very tiring. It should be simplified with the roles who can add new members and set up the method for new team members.
Chat was helpful but it's not easy to follow up for every team person.Also for a change in phone or lost device should have some details to get ahead for the user to access the db, after authentication.
As authenticator app gets lost with the device, it should not end in loop where it keep asking for Admin password.
1 vote -
Hide Intercom button/window
The intercom window frequently pops up and blocks information when I log in to Atlas or refresh a page. This is annoying and it should never open automatically (or at least I should have an option to make it never open automatically)
1 vote -
1 vote
-
Delete documents from backups
Allow to delete documents from existing backups based on a query.
When off-boarding customers, we sometime need to delete all of their data, including historical data from backups. Having the ability to clean up those backups, without having to restore, delete, and take a new backup, would be amazing.
2 votes -
Rejecting Index Suggestions
Some Index Suggestions don't work. The Performance Advisor doesn't sample data, and therefore can not predict if some field is worthwhile in an index or not (e.g. some fields may contain the same value for all documents).
If we decide to not apply the Index Suggestion, or we apply it, test it, and remove the Index again because it's not being used by MongoDB, the Index Suggestion is still showing up. It can also trigger alerts.
Please add the possibility to reject an index suggestion, so that it's hidden from the UI and can not trigger alerts.
9 votes -
Global overview of Index Suggestions
We run more than 60 clusters today on Atlas, and will probably hit 100 clusters in the foreseeable future.
The Index Suggestion alerts are not dependable for us (see https://feedback.mongodb.com/forums/924145-atlas/suggestions/44243568-better-alert-trigger-for-index-suggestions ).
Going through many clusters manually to check them for Index Suggestions is an extremely time-consuming process. We would like to have a global overview of all open Index Suggestions, or at least an overview on a project-basis.
7 votes
- Don't see your idea?