Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1369 results found
-
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 -
Increase # of Collections in Performance Advisor
Currently the recommendations are for the 20 most active collections. It would be helpful if there was an option to run this for all collections or to set a larger number of collections.
4 votes -
Attach a newly created Trigger to an existing AWS Event Bridge Bus via Terraform.
Attach a newly created Trigger to an existing AWS Event Bridge Bus via Terraform.
4 votes -
auto scaling on IOPS like the storage autoscaling
the IOPS can be auto scale up when it reach the maximum and stay at the maximum level for more than 1 hour
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 -
Google chat integration with Alerts
Integration Alerts with google chat like done with SLack
4 votes -
Resync progress bar
Our Mongo cluster has had to resync. It would be great to get some kind of time estimate or progress bar to know how far it's got in resyncing so we can let our research team know when the cluster will be ready again.
4 votes -
Single node clusters
Allow users to create a single node clusters for dev purposes.
4 votes -
Allow tagging of mongo atlas alarms
It would be awesome to have possibility to tag alerts in atlas when creating using API or console. It will allow to process groups by alerts by tags without keeping track of ids.
requires:
adding tag field to API create call
adding query by tag to API delete or update calls.Pavel
4 votes -
Make RSS feed entries more consistent
We would like to consume your status RSS feed to help us programmatically warn our internal groups when you have issues in a given region. One problem that we see with this is that the messages that we have seen posted are pretty inconsistent with how they specify regions. Examples: Oregon (us-west-2), AWS EU-WEST-2, AWS Sao Paulo. It would be very helpful to us, and probably your other customers as well, if the messages were more consistent in how they reference AWS regions.
4 votes -
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)
4 votes -
Allow Network Peering to be used by Atlas Triggers / Realm Apps
What is the problem that needs to be solved? Some users want to receive outgoing network connections (e.g. with HTTP/HTTPS traffic) from Atlas (Atlas Triggers / Realm Apps) via their configured Network Peering, i.e. via private IP address space (so that everything is kept in private IP address space and nobody outside could reach it). Example: customer would like to have Atlas Trigger / Realm App which will notify (via HTTP) some of customer's internal system(s) about a change/trigger.
Why is it a problem? (the pain) Current Atlas (Atlas Triggers / Realm Apps) behavior does not allow to use private…
4 votes -
Add a monitoring that always shows the current primary
When there's an election and the primary changes, it's hard to get a good view on how does the primary functions in a macro fashion.
Please add a monitoring column (or an equivalent solution) that can show the monitoring information for the primary at the time, so I could look at the past month or so, and see how does the primary performed, even if it was a different server every time.This will make it much easier to understand various actions we take like changing indexes, improving queries, upgrading the database version, upgrading the driver, etc.
4 votes -
For creating indexes, show a list of fields, so as to easily select and add field that needs indexing.
While creating indexes using MDB atlas, there is no option to select from a list the fields that we want to add for indexing. For ease of use, this functionality must be added to Atlas GUI.
4 votes -
Add editable description to a snapshot
After an incident I may single out a snapshot and decide it is important. At this point I am able to change the retention policy to keep it for a longer time.
It would be useful to also be able to add a note or a description to that snapshot so that I may tell future me why that snapshot was important and what incident it is tied to.
4 votes -
Extend sub-hourly metrics retention to 72 hours
Right now the 1- and 5-minute metric data is lost after 48 hours (when it is combined into the hourly data). This makes it impossible to take a close look, on a weekday, at an event that occurred over the weekend.
It would be nice to be able to look at a problem on the weekend and say "I'll look at this more closely on Monday", and then have the ability to actually investigate it on Monday.
4 votes
- Don't see your idea?