Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1366 results found
-
Cluster version overview on Owner level
We have partially older mongoDB versions running on our clusters. We get notified about it by EOL mails from mongoDB. However, as an org owner, I cannot see which clusters are affected. This makes it extremely time consuming for me to identify the relevant contacts per cluster. Our org structure entails self-sufficient teams with independent accountability of the mongoDB clusters. There is no central contact person.
It would be desirable to be able to call an overview of all clusters with the respective installed version in the GUI with owner rights.
2 votes -
Project Monitoring Admin -- Access
Hi Team,
We need to give access to a particular team so they can create, edit, clone, disable, and delete the alarm for the entire organization in Alert setting only.
We should not give them access other than the Alert setting. Is there any way to give access for Alert setting only, kindly provide your suggestions at the earliest.
Please provide us steps if there's any way to create custom access for alert settings alone.
6 votes -
Clone collections
Now, you can just delete a collection or add a new one. It would be nice to be able to clone a collection, or at least a part of it.
1 vote -
Google Data Studio Connector
Create official Google Data Studio connector.
6 votes -
Federation metadata.xml for automatic idp certificate rotation
It would be great to have an opportunity to automatically rotate the idp signature certificate.
I could provide a metadata.xml url. With that metadata.xml in generally it's possible that okta rotate the certificate on it's own. But it's not possible to configure in Mongodb Atlas.
Best regards
Fabian1 vote -
Single node clusters
Allow users to create a single node clusters for dev purposes.
5 votes -
Log browser and log search capability across replicaset nodes.
Currently to search through logs we have to download them and search through each log. It would be helpful to have a log browser capability that would allow us to look through and search all logs from the Atlas portal interface.
12 votes -
Setup activity feed retention
It could be very interresting to be able to setup the retention of the events by organisation, projets and clusters. Actually I understand that this value is 30 days. So it to short for us, so we need to download the activities logs and it difficult to seach in files after that.
2 votes -
Create alarms base on events + Add control policies
Events (in the perimeter: organization, projects, cluster) are useful for monitoring activities. But it would be very useful to be able to set the alarm on these events. The goal is to be informed when certain actions occur.
The best is to be able to have a configuration control policy. Especially to control security, network configuration, etc ...
For example:
- Be able to avoid the use of user scram.
- Be able to avoid using unauthorized IP addresses
- Be able to avoid changing the configuration of access to database data (DataExplorer) from the Atlas portal3 votes -
Using Online Archive with Customer Encryption Keys
I'd like to use Online Archive but I need to use Encryption Keys that my company manages, not ones provided by MongoDB.
13 votes -
Teams API should show the projects the team is a member of
Right now the API to retrieve information of a team ( either by ID or by Name ) only gives the name, the id and a link of the specific team.
I would like to see to what projects a team has access with which permissions ( as you can see via the atlas console ).
This would help a lot with automating access management
2 votes -
Warning if attempting to change cluster configuration while an index operation is in progress
When changing the cluster configuration to scale it up or down, there is no warning if there's a index build currently running on the primary/secondary. I created an index, saw it finish on the primary and then scaled the cluster, without thinking about that the index is only now built on the secondary, too.
During the downscaling the index build got aborted and attempted to build in foreground then. However this for some reason did not work and I had to contact support to help me with getting the secondary up again.
My proposal would be to either:
- Display…1 vote -
pause
An option to protect the "Pause" action on clusters with 2FA would help to reduce the chance of accidental pausing of production systems.
14 votes -
Allow instant backup on every type of cluster
Allow to create a backup when we want, on every type of cluster (like we could do with mLab plans)
3 votes -
connect with slack
Whenever the database is about to scale, give an alert via slack to the team.It will be instant and currently, alerts are over email if you could provide it over slack the tech team responsible for particular will be notified.
3 votes -
ignore notimeout cursor (after initial warning?) to avoid breaking compatibility with apps
In Q4 2020, the notimeout cursor was no longer allowed on free or shared instances.
As several DB management tools hardcoded this option for optimum performance it breaks compatibility with them. We use a combination of free/shared-tier instances for dev in combination with dedicated instances for production; this limit effectively means we either have to WAY overprovision our dev resources, or we can't use our tooling anymore on it.
Please provide a way to simply ignore the notimeout option, instead of breaking its connection.
Thanks!
1 vote -
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 -
Official ServiceNow Connector
Would love to see an official connector to ServiceNow for automatic ticket creation triggered by various database alerts.
25 votes -
billing
The billing invoice is split by project. If we have multiple team in the same project, it a puzzle. We need to bill by cluster in this case.
13 votes -
Recently resumed clusters must remain running for 60 minutes
At the moment when you try to pause a recently resumed cluster you get the following message;"Recently resumed clusters must remain running for 60 minutes to process all queued maintenance".
Obviously this requires me to check back in Atlas UI in an hour or so just to pause the cluster. Instead would be good for UI to schedule a Pause to be executed as soon as it's possible.
11 votes
- Don't see your idea?