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
-
Mongo DB alerts for latest version or release
Automatic alerts from Mongo DB Team for the latest releases / versions available similar to the EOL(End of Life) alerts.
This helps in planning the changes and upgrades reducing the manual effort on searching for latest versions.4 votes -
Last Database User Access
My team has found ourselves in the position of needing to iterate through the Database Access History Logs in order to discover whether or not a database user is still being used for the past t time periods.
We need to have this functionality in order to guarantee a seamless credential rotation.
With the current API this operation will require iterating over each cluster's access logs for the past t time periods. If I have "n" clusters and "t" time periods this is an O(n * t) runtime. I'm not really great at O() notation, but if t is greater…
4 votes -
Multiple Email address for alerting
In alertconfiguration, change the emailaddress argument in "notification" block from "string" to "list(string)".
Main goal here is to allow multiple alert emails like it's possible in the portal.4 votes -
Display EBS actual disk information (gp3)
Currently, clusters created on AWS have gp3 volumes according to support.
However :
* the configuration displays max IOPS 6000 for M50 clusters even though documentation states that iops scale 3:1 with the volume size in GB (1 GB = 3 IOPS) regardless of disk type for M30+ clusters (true with gp2 anwyay, for gp3 that's an enforcement by Atlas)
Documentation link : https://docs.atlas.mongodb.com/customize-storage/#configuring-the-iops-rate=> the configuration should at least display the actual IOPS (as it's also being used for alerting) - ideally it would allow us to have more IOPS than the minimum 3:1 enforcement.
- with gp2 we had…
4 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 -
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.
4 votes -
Uptime report for Atlas cluster
It would be great to have an uptime report be it weekly or monthly basis which can be extracted and presented anyone who would like to have an high level overview.
4 votes -
Transactions support for Merge operation in aggregation pipeline
Hi Team,
can we consider supporting the transactions when we use $merge stage in mongodb aggregation pipeline?
https://docs.mongodb.com/manual/reference/operator/aggregation/merge/#restrictionsWe have a requirement where we need to use the merge stage in pipeline and we would like to ensure automaticity in the transaction.
The aggregation pipeline we are building can merge multiple documents into the same collection and we would like to have either all or none by using transactions and the current merge operation cant support it.
thank you
4 votes -
See the history of autoscaling
Most of my clusters keep autoscaling (scale up and scale down) 3 to 4 times in a week. I would like to see the history of the cluster when the cluster scaled up or scaled down along with scaling reason (e.g. high CPU in Analytics node) and the time it took to complete the scaling transition.
4 votes -
Support GCP Private Services Access to Atlas
Hello,
this is a request to support Private Service Access for Atlas deployments on GCP. Today, our options with Atlas are IP access lists or VPC Peering. However, these options create downstream limitations for our organizations. Additionally, only one peering connection can be made per Atlas project, which also limits us.
Thanks
4 votes -
Show date in UI DB Stats axes
Show date in UI DB Stats axes
Currently the x-axis of DB Stats charts do not show dates, making it difficult to interpret the range of time displayed in the chart.
For example, you can see in the date menu shown in the attached image that the chart range is over 4 days, but this is not apparent in the x-axis of each chart -- the x-axis only shows one reference time of 07:00.
It would be more helpful if the axis showed a reference date in addition to the time, and ideally a couple dates so that it is…
4 votes -
Log Redaction for Atlas
It would be good to see Log Redaction work in Atlas as well, similar to On Prem
https://docs.mongodb.com/manual/administration/monitoring/#log-redaction4 votes -
Allow designating some team members to administer team membership
Currently adding and removing members from team requires Organization Owner privileges. We would like to distribute management of team membership to users without having to grant them root privileges on Atlas account.
The feature would allow us to designate some team members as admins for the team, and they could then add/remove team members. This is in similar in concept to how Github implements team maintainers for a GitHub Team.
4 votes -
snapshot
Show Snapshot progress (from provider snapshots) and possibly an ETA in Atlas UI
4 votes -
Determine index's impact score before creating
Currently in Atlas there is no way to test an index's performance before creation. Performance advisor provides an index impact score for suggested indexes. Requesting a feature where you can upload a proposed index and performance advisor can determine the index's impact score. This would help test an index performance before committing to a build
4 votes -
Atlas Capacity Check for Cluster Creation or Changes
When creating large new clusters sometimes Atlas does not have enough resources available from the cloud provider. When this happens a restore or cluster change fails without reporting what the actual issue is.
Solution: Verify available capacity and issue a warning or error if it is possible that the operation will fail & recommend opening a support ticket (or have a dialog to automatically do so listing the details)
4 votes -
Include cluster labels with Invoices API response.
Using the Invoices API to aggregate cluster costs by label involves cross-referencing the Cluster API. Including cluster label information as part of the Invoices response would eliminate this extra step.
4 votes -
Add API endpoint for Organizational Settings
To be able to change and read Organizational Settings in an automated matter, support for Organizational Settings should be added to the Mongo Atlas API.
4 votes -
domain names in access whitelist
Allow domain names in whitelist for IP address. (And rename whitelist to allowlist).
I have a server (app) on heroku. It has a domain name. I don't have a dedicated ip address range. But if I could put my domain name in (myapp.herokupapp.com or myapp.com if I get that name from godaddy), then when my server connects, you could do a DNS lookup of the domain names in the whitelist, and allow connection from those. And then, my app, and many others would be more secure. People could also use dynamic dns to support connections from their home computers, more…
4 votes -
LDAP Authentication: Allow Private Endpoint to the customer
Currently, LDAP Authentication from Atlas to a customer's LDAP service can go via the Internet or via VPC peering. In lieu of VPC peering, I propose using a Private Endpoint FROM Atlas TO a customer VPC that hosts the LDAP service.
NOTE: This would NOT be using the same Private Endpoint connection that Atlas currently supports today, which allows customers to reach their clusters privately (Customer -> Atlas).
This would be an additional Private Endpoint in the other direction (Atlas -> Customer).Advantages of using Private Endpoint vs VPC peering:
* Security: The customer VPC is not exposed to Atlas,…4 votes
- Don't see your idea?