Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1365 results found
-
Alert when a User accesses Data
Trigger an alert if a specific user directly accesses data (e.g. browsed a collection/performed an operation) using Data Explorer in Atlas
3 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 -
bad experience
sorry to say but your service is very bad because when i upload a data collection after few hours my data automatically jumbled.
please send me the reason why this is happening.
1 vote -
If you select "Collections" on a database, and you don't have at least "Project Data Access Read Only" access, you get an unhelpful message
If you don't have the access righrts to read data, instead of a suitable message, you get "An error occurred while querying your MongoDB deployment.
Please try again in a few minutes."
Totally unhelpful, as trying again won't fix your permissions!1 vote -
Alert configurations should be unique
Atlas allows for the creation of duplicate alerts. Alert configurations should be unique such that exact duplicate configurations are prevented from being saved.
2 votes -
Compact collection from UI
Compacting of a collection directly from the MongoDB Atlas website UI.
No need to run CLI commands and changing primary database.
Making regular maintenance easier.
35 votes -
Warm up cache automatically when there is any server/node restart events
Usually it takes hour or so for the cache to warm up depending on the data size when an server restart scenario occurs ( increasing the tier / storage etc). And there are alternatives like running cache warm up queries to bring the nodes up to speed .
However if this cache warm up should be inherent and automatic for the server restart scenarios .
3 votes -
Restrict specific users or client IPs to only Analytics node(s)
There are use-cases where certain users or client IPs need to be given access restricted to only the Analytics node(s) . While it is possible to grant such users read-only permissions at the database/collection level, and have them use the ANALYTICS replica set tag in their connection string URI, it might still be possible for those users to connect to a Primary or a Secondary node (when not using the Analytics replica set tag) and run their query there.
Therefore, a feature that will either restrict specific users access to only the Analytics node(s) or a functionality that will restrict…
26 votes -
Online Archive - Automatically defragment data file and release disk space after archiving
This is a request for Atlas to automatically defragment the data file and for the WiredTiger storage engine to automatically release empty space to the operating system, for clusters with active Online Archive.
After implementing Online Archive, and seeing data be archived to S3 based on our archiving rule, we expected the available cluster storage to increase since Online Archive had effectively deleted data from the cluster.
However, MongoDB Docs states: "When you archive data, Atlas first copies the data to the cloud object storage and then deletes the data from your Atlas cluster. WiredTiger does not release the storage…
16 votes -
Send Alert when IP access list changes
Customer is requesting that an alert be sent out if project IP access list gets changed
23 votes -
Pending updates alerts
I'd like to be able to have alerts for all those databases that are using a version that is not the latest major version available.
This will help to be more proactive so that updates can be planned in advance without the need to manually review the available versions from time to time. It will also help in the implementation of security controls such as SOC2.
3 votes -
Option to edit maintenance alerts via API
Maintenance alerts are created automatically when a maintenance window is set and these alerts by default send an email to the project owner.
If you want something different in those alerts (Slack notification, PagerDuty, etc.), having to go one by one when you have multiple clusters is not practical, lot of manual interaction for a managed service.
The goal of this request is to let configure/edit/create these alerts using the API, so it can be later included in Terraform.
8 votes -
Provide "Password Age" for Atlas password auth users via Atlas API
Similar to "Last Login Date" suggestion, add the age of the password for SCRAM users. I see that https://jira.mongodb.org/browse/SERVER-3197 was closed as "Won't Fix", but this will at least allow reporting, audit, external maintenance, etc.
1 vote -
Prevent Federated Users to gain access to other Projects
Hi,
We have set Federated authication and RoleMapping to project. This roleMapping gives Project Owner Rights to a particular project. Project Owner have the right to invite other people into their project.
Role mapping is only applied when a user logs in. However, if the user receives an invitation to a project when logged in (to say Project ***) and accepts an invitation (to say Project YYY, for which they should not have any access), they will receive the Atlas role in that project (Project YYY) designated by the invitation, allowing them to perform any actions provisioned by that role.
…
2 votes -
Force restart of unhealthy node
Right now, there's a "test failover" option, which shuts down the primary and forces an election. However, the option is only available if the cluster is in a healthy state.
If, for whatever reason, the cluster is unhealthy, it's impossible to manually restart the primary. It should be possible to force an election in an unhealthy state. Often, this is all that is required to get back into a healthy state (e.g. if the primary is in a CPU burning loop that was caused by an unexpected write pattern that has stopped.)
124 votes -
Need network whitelisting of API key for CI and Terraform
Hi great Mongo people.
The API key under organizational settings operates under a whitelisting model. There is currently no way (I can see) to open the key to 0.0.0.0/0.
But in use cases where you make calls to Atlas to manage infrastructure through Terraform (like I do) and use a CI SAAS tool like Gitlab (like I do) that is built on a cloud (like GCP) there is an insane amount of whitelisting that is required. Also, about every 3rd run I have to come in and add another white list IP so that my Terraform can run.
Could you…
1 vote -
Add an option to include sample data during cluster build
When working through tutorials or University courses, often you need to build a new cluster and then add sample data to it. It would be nice if you could just check a box in the cluster creation page to have the cluster brought up with sample data already provisioned, thus combining two commonly used steps, into one.
1 vote -
Add information to the billing API reponse
When retrieving the billing details through the API, we are missing some information for a perfect understanding (and automation) :
- Number of nodes of the cluster. Indeed, without this information, the field "quantity" is kind of complicated to interpret
- Group Name. Each entry is attached to a groupId, but sometimes when the project has been deleted, it is impossible to retrieve its name, so pretty complicated to interpret (in the UI, the group name is available, so I guess it can be in the API)
15 votes -
Atlas policies
In the MongoDB atlas portal, there should be a way to configure policies across an organization. ie: policies to restrict users from creating clusters from certain cloud providers (ie: azure), restrict users from creating databases of a certain size, etc.
9 votes -
webhook
Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.
2 votes
- Don't see your idea?