Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1322 results found
-
Support HITRUST certification for Atlas
Some companies want a certification from HITRUST https://hitrustalliance.net/about-us/ in order to put workloads in the cloud
1 vote -
More functionalities in Collection (Data Explorer) Tab in Atlas UI
Here are some suggested functionalities
- Import and export of bulk documents.
- Quickly filter and sort the required documents. (This is achievable in Compass but not in Atlas UI)12 votes -
Extend / Configurable retention time of audit logs
This is a feature request to extend or have configurable retention time of audit logs more than 30 days in Atlas.
13 votes -
Change/Option to change Default Storage Compression to zlib
This is a feature request to change or provide an option to change Default Storage Compression to zlib
7 votes -
Separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster
This is a request to separate Atlas metric graphs of the outgoing traffic from the internal/replication traffic in Atlas cluster
4 votes -
Pause and Resume clusters needs a timestamp in the JSON
Currently clusters can only be paused for 7 days. After that period they must be resumed for at least one hour. However the time of resumption is not included in the result from the resume REST call. If that data was included a script could determine easily when to pause a cluster again after maintenance jobs are finished.
1 vote -
Allow individual Atlas database user to connect from different specific IP address only
The feature request is to allow individual Atlas database user to be able to connect from different specific IP address, instead of compulsorily having the whitelisted IP address apply to all database users.
I.e.
UserA can only connect from ipA
UserB can only connect from ipB12 votes -
Atlas Alert for Remaining Credits
MongoDB will email Atlas customer when the prepaid Atlas credit is estimated to be exhausted within 30 days.
However, it would be good to have an alert for this in Atlas, e.g.
Alert if the remaining prepaid amount is lower than ... <an amount>
9 votes -
Granular Permissions
Right now Mongo Atlas allows you to assign two types of roles to all the users: Organization and Project, and for each set it gives you some predefined roles.
The problem with this is you can't have any kind of granular control of what permission is assigned to each user. (e.g. to allow a user to create a trigger through Mongo Stitch it needs the Project Owner role).
This is a major setback as I'm giving my coworkers more access than needed.
A good solution would be to have something like the database access control in this part so we…
455 votes -
Allow multiple Billing emails
Allow multiple billing e-mails instead of just one. There are multiple people in our org who want a copy of the invoices, but I don't want them sent to the entire org (which is what happens if there's no billing e-mail)
5 votes -
Stitch - use the same function to resend confirmation as when initially signing up
When signing up with Email/Pwd, one of the options is to have the confirmation run through a function.
In that function, a call to an external email provider has been set up to use a template with a logo.However, the "token" & "tokenId" parameters provided in the link are only valid for 30'.
This makes it likely for people to be too late to confirm their email address.
When calling "resendConfirmationLink", an email with a new link will indeed be sent out, but this is the standard MongoDB email. This request is to have this "resend" use the same…
3 votes -
disk iops
The Disk IOPS graph shows 2 colored lines. (read/write). It would be great to add a third line which is the SUM of the 2 lines. Or... a toggle switch so we can see the sum line instead of the 2 components. Thanks!
15 votes -
Add eventTypeName for Maintenance Windows in alertConfigs response
After adding a maintenance window to an Atlas project, the alertConfigs returns additional entries that do not include an eventTypeName field, it seems that these additional entries relate to the maintenance window but it's not clear:
{
"created" : "2020-02-28T16:04:18Z",
"enabled" : true,
"groupId" : "",
"id" : "",
"links" : [ {
"href" : "https://cloud.mongodb.com/api/public/v1.0/groups/***/alertConfigs/5e593a02559f765dca07acfe",
"rel" : "self"
} ],
"matchers" : [ ],
"notifications" : [ {
"delayMin" : 0,
"emailEnabled" : true,
"intervalMin" : 60,
"roles" : [ "GROUPOWNER" ],
"smsEnabled" : false,
"typeName" : "GROUP"
} ],
"updated" : "2020-02-28T16:04:18Z"
},…1 vote -
metrics
There might already be a way to do this, but I cannot find it. Please provide a way to combine "all primary" metrics into a single chart.
I love your metrics, but I hate that when primary moves from one server to another I get "data gaps" in my graphs. So then it becomes exceedingly difficult to look at temporal variations... requiring splicing together multiple segments from 2 or 3 different graphs.
I have attached a picture of what I am talking about. You can see that primary moved over for a few days so I get a graph with…
9 votes -
Terminate existing connections from IPs when removed from the whitelist
When removing entries from an Atlas Project's IP whitelist, existing connections from those IPs are maintained, and thus those hosts can continue to perform operations until the connection times out. I'm aware such connections can be dropped by doing a Test Failover or pausing and unpausing the cluster, but in some scenarios this is not ideal if even possible. This also seems like a security gap: When access is revoked from a particular IP or CIDR block, any existing client connections originating from that IP or CIDR should be terminated and the hosts behind that IP or CIDR should be…
4 votes -
1 vote
-
Limit certain users to create only specific cluster sizes
After discovering over-spending forced to remove Atlas permissions for all developers. Would be nice if I could limit them to create only M0 / M2 / M5 clusters as sandbox.
4 votes -
Description field for VPC peering page
Add a description field to easily identity the peering items in Peerings tab. Example: "Peering for Stage Kubernetes cluster apps"
4 votes -
Project Homepage / Ability to add descriptions to Atlas projects
We have a lot of Atlas projects in our org, some are outdated, unused, orphaned, some important and used for production. It would be great to have a way to describe what each of them are for, who to contact for questions, etc.
For example, when you switch to a project, you land on the project homepage that has the description right there, alongside an overview of how many clusters, users, last change, if whitelists are enabled etc. Even better if I can use Markdown or some other "rich" editing experience to create the description and add links, bullet points,…
2 votes -
Add Option to Disable Federated Authentication Automatic Account Creation
Based on the documentation it appears there is no option available to disable automatic account creation when Federated Authentication is used.
The business case for disabling automatic account creation is to allow a limited set of users from the Identity Provider to have access to Atlas and the databases, while not allowing anyone with an account in the same domain to create an Atlas/Database account.
2 votes
- Don't see your idea?