Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
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 -
Persist setProfilingLevel Setting in Atlas
Currently the profiling level resets to 0 every time the mongod process restarts. You can persist this with a self-hosted mongo by editing operationProfiling.mode in the conf file, but this is not possible in Atlas.
4 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 -
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.
5 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.
5 votes -
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…
5 votes -
max database users not visible
We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.
14 votes -
Send Alert when IP access list changes
Customer is requesting that an alert be sent out if project IP access list gets changed
21 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"
].6 votes -
webhook
Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.
2 votes -
Show overlapping Alert configurations between different scopes
I wish there was a way to show an overlapping alert configuration. When alerts are defined on a global level but overridden on a project level, it is very hard to tell if something was overridden.
2 votes -
A default ‘Send to’ method for Alert configuration
I want to be able to define a default ‘Send to’ method that will be automatically configured during Alert creation.
The default is email, but when we use a 3rd party integration like PagerDuty, it is quite tedious to create alerts manually. The only quick and perhaps correct way is through automation such as MongoCLI or Terraform.
2 votes -
Single page to view all configured Alerts
I want to be able to look through all of my Alerts for all of my projects on a single page to easily understand their state. I'd also like features to help me make sense of the aggregated list. (some type of sorting or filtering)
I struggle to understand the state of all of my Alerts, across all projects, because there isn't a centralized place to view all of them. It's also hard to maintain a large set of alerts for a given project because there's no way to sort/order them.
2 votes -
Make BI Connector Settings Permanent
Allow the "SET GLOBAL mongodbmaxvarcharlength = n" to be permanent after a Mongosqld restart. Currently, the setting is ephmeral and must be set everytime the mongosqld daemon is restarted. Currently, our production environment mongosqld can restart without our knowledge at anytime. This results in the mongodbmaxvarharlength variable being reset to zero, which can lead to a production outage. Is there anyway this can be automated, maybe through database trigger?
33 votes -
Authentication Process Improvement
At the time for user login authentication VDI user authentication is not done properly. Not able to fetch the system details. Need improve in that section--- For example--->" You're receiving this message because of a successful sign-in from a device that we didn’t recognize. If you believe that this sign-in is suspicious, please reset your password immediately. "
1 vote -
Enable and disable balancing on a collection
Shell commands sh.enableBalancing() and sh.disableBalancing() were not permitted on Atlas hosted MongoDB. Is it possible to grant this permission?
Currently it failed with error:
uncaught exception: Error: command failed: {
"ok" : 0,
"errmsg" : "not authorized on config to execute command { update: \"collections\", ordered: true, writeConcern: { w: \"majority\", wtimeout: 60000.0 }, lsid: { id: UUID(\"ed83ed26-e07b-4f34-a90a-a145bbe58a48\") }, $clusterTime: { clusterTime: Timestamp(1646788928, 17), signature: { hash: BinData(0, 347249E35ED43BDADAE12FB0F794C091CB86206E), keyId: 7052082196881866761 } }, $db: \"config\" }",
"code" : 13,
"codeName" : "Unauthorized",
"operationTime" : Timestamp(1646788928, 18),
"$clusterTime" : {
"clusterTime" : Timestamp(1646788928, 18),
"signature" : {
"hash" : BinData(0,"NHJJ417UO9ra4S+w95TAkcuGIG4="),
"keyId"1 vote -
Migrate to new cluster without auto upgrade (5.1.0)
Hi,
Our clusters are in auto upgraded feature of MongoDB versions right now.We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.
But, when we try to create a new cluster it's not showing the option for version 5.1.0.
And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.Your help is much appreciated.
2 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.
7 votes
- Don't see your idea?