Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1260 results found
-
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 -
Allow to set billing alerts per project
I have different projects where I expect and calculate with different costs. I would like to set billing alerts per project, for example if an internal evaluation projects execeeds a specific biling the threshold is probably lower then for a production project.
Similar to the currenty billing alerts, I would to set a billing alert, but either per project or with different thresholds for each project.
2 votes -
Add MFA status to the API
A field indicating whether MFA is on for organization users (i.e. on https://docs.atlas.mongodb.com/reference/api/organization-users-get-all-users) would be extremely useful!
2 votes -
Governance rules at the organization level
Hello team,
Would it be possible to be able to set up governance rules at the organization level in order to control certain configuration elements.
For example:
Control authorized providers and regions for an organization to prevent creation of cluster in unauthorized regions. (We must keep the data in Canada for some of our databases)Check the allowed IP (IP Access List) addresses
Disable the use of SCRAMS accounts for database access.
Control the "Data Explorer" functionality at the organization level to prevent its activation at the project level.
2 votes -
allow for renaming and moving of collections and databases on server
Right now it is difficult to rename and move databases and collections without downloading and re-uploading them.
Please enable this critical functionality as it's very common to need this when administering data.
2 votes -
Replay the point-in-time-restore journal for debug/diagnosis
When performing a forensic analysis for the purposes of a restore, in order to determine the appropriate point in time when our data was last "sane", it would be awesome if we could start with a point-in-time restoration, and play the journal forward, e.g. performing a bisect on the data.
2 votes -
Google chat integration with Alerts
Integration Alerts with google chat like done with SLack
2 votes -
major version downgrade request (4.0 to 3.6)
Right now I am running the MongoDB cluster on 3.6. Now I want to upgrade this cluster to 4.0. But when I want again to revert back to 3.6 I have no option to downgrade.
Use case :
Right now our production is running on 3.6, when we upgrade this to 4.0 and if we face any major issues on prod, then we have no option to get back to old version 3.6.
Without this option we cannot move our production to 4.0.
2 votes -
LDAP support for Atlas Organization
This is a request to support LDAP for Atlas Organizations, not just Atlas Projects. The reason would be for easier access management - when someone leaves the company and their access to the Atlas Org (or in general cloud.mongodb.com / the Atlas portal) needs to be revoked, it would be easier to manage this from the LDAP console.
An alternate solution would be the ability to add IP addresses to an access list at the Atlas Org level (not just Project level.) Then when someone leaves the company, their IP address could easily be removed from the Atlas Org and…
2 votes -
Enable Compression
We would like to see better compression for data stored in the Online Archive.
Data in our cluster is compressed very well using the WiredTiger storage engine.
Moving it out into the archive grows our data size by almost 4x.2 votes -
Option to group Profiler records by query pattern
The Profiler shows slow query statistics grouped by namespace, but it would also be helpful to view query records grouped by query pattern (perhaps similar to the "pattern" group option in mplotqueries: http://blog.rueckstiess.com/mtools/mplotqueries.html#group-by) and/or by specific fields used in the query.
This could be helpful, for example, for identifying particular query shapes that are executing slowly or suboptimally so that these can be investigated in more detail.
2 votes -
Please bring Atlas to digital ocean PaaS as a first class offering!
Hey there,
I know it's hard for big companies to get along, but I'd love to have a seamless experience for using MongoDB alongside DO's new PaaS offering. Can you all strike a deal please?
2 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.
2 votes -
please offer a way to delete the content of a collection
I wish there were a way to allow a user to delete the contents of a collection within a database, that allows the collection to continue. Essentially I want an easy way to empty a collection to allow new data to be filled in its place.
2 votes -
Add full screen mode for multi-graph Metrics and Status views
Unless I've missed a button somewhere, it would be nice if the "Metrics" tab for clusters and "Status" tab for shards had an option for expanding the entire tiled graph view into a full screen view. We have some TVs around our dev pod where we display these graphs and it would be great to see several graphs at once in full screen view.
2 votes -
Deactivate use of charts on org-level
As charts meta data are processed only on US servers, a toggle to forbid the usage of charts for autonomous teams would be helpful, considering GDPR requirements
2 votes -
Count
Whenever a query is fed into the filter search box, ensure that the count of the result is also provided somewhere above the result of the query.
2 votes -
Project Alerts: show details about "Closed Alerts"
In "Project Alerts" we can only see certain details about "Closed Alerts," e. g. for an "Index Suggestion" we can only see the timestamp and the fact, that there was an index suggestion. You can't see what the specific suggestion was. So if you look through the history of alerts, you cannot tell if for multiple alerts it was always about the same index to be created, or whether it was for different indexes.
Likewise, for "Daily amount billed ($) is above threshold" you can see that the threshold was exceeded, but you can't see what the specific billed amount…
2 votes -
Implement create-before-destroy when migrating NVME instances
When triggering a cross-region migration Atlas immediately degrades a cluster by going to N-1 nodes prior to creating a replacement node in the new region.
When using NVME instances, this violates the agreed upon replication depth. Once the NVME instance in the source region is destroyed, there are only N-1 copies of the data left, as there is no EBS backing.
NVME target instances should be brought up as {hidden=true, priority=0} until leaving STARTUP2 and entering SECONDARY. Once this occurs, the target instance should be brought to {hidden=false, priority=P}, and a source instance hidden, removed after a quiescence period, and…
2 votes -
An API endpoint for Live Migration
When customers have dozens and hundreds of clusters to migrate from on-prem to Atlas, automation is very important and Live Migrate is not supported via API today. Mongomirror is a shell command that can be leveraged for automation but having Live Migrate available as API will be a great enhancement to CD/CI pipeline.
2 votes
- Don't see your idea?