Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1367 results found
-
Increase maximum storage size for M60 servers
Currently the maximum storage size allowed for an M60 tier is 4TB. Our cluster is approaching this size, and we're facing having to shard our data, which we would really prefer not to do.
I understand that the maximum sizes are selected for performance reasons, but not every cluster is the same - ours is doing just fine and not struggling at all at this data size, and we would like to be able to continue to grow over time.
4 votes -
Ability to add multiple IP's to the whitelist and download the current whitelisted IP's
If I want to add comma separated IP's it is not possible. We have to add each IP painfully from the UI. Please allow to add comma or semicolon separated IP's to be added at once.
Also, why can't I download the current whitelisted IP's as a CSV or other file?
4 votes -
invoice should show support costs under project and not organization
We need the support costs (in our case Atlas Pro) to show up for each cluster under the project on the invoice. Right now, it shows up as a separate line item in a lump sum under the organization. It makes it difficult or impossible to properly bill the individual cost centers for support costs for their clusters.
If those costs showed up next to the clusters within the project, it would be easy to say project1 goes to cost center 1, but now we have to do project 1 goes to cost center 1 plus some percentage of the…
4 votes -
Ability to search for filter conditions in Atlas Alert builder
It would be helpful to be able to search for a trigger condition in the Alert builder when creating/editing an alert.
Currently, you need to scroll to find specific conditions, but the list is long so it can take some time to find the particular one needed.
4 votes -
Sort IP Whitelists in Atlas
Enable sorting and filtering on the whitelist management screen.
There is no logical order to the list of ips.4 votes -
Shorter Temporary Durations for Network Access whitelist
Hello,
it would be nice if you could add options for temporary whitelist entries that are shorter than 6 hours. Often in our Team we find ourselves just needing to whitelist an ip for a short amount of time to look up some documents or fix a bug.
For that case it would be nice to have additional shorter options like 3h, 1h, 30m, 15m.Thanks for taking a look
4 votes -
Atlas alerts - include duration and date/time alert was closed
currently alerts (sent to SLACK but probably other formats as well) reads this:
Project: OS1
Organization: SE Atlas
CLOSED
Host is down
OS1-g-shard-18-05.bxxxxq.gcp.mongodb.net
Created: 2020/06/11 03:44 BSTType: Mongos
It would be helpful to also include:
Closed: 2020/06/11 07:44 BST
Duration: 1h 53mAs the slack is usually set to each users timezone it creates a confusion when one is looking at how long issue lasted.
This should be easy to implement and it would improve end user experience a lot.Same would be nice on Atlas 'closed alerts' tab - there seems to be no way currently to get…
4 votes -
Migration Tutorial Video
I did a live migration from mLab to Atlas quite recently. Although, the steps for migration were simple and easy to execute it took me alot of time to get over the fear of migrating without losing any data. A tutorial video of the entire process would have calmed my nerves and helped me take a lot less time in the process.
4 votes -
Ability to create and update database triggers via API
It would be really usefule to have the ability to create and update database triggers via the API. Currently, updates to triggers cannot be integrated into our testing and deployment process because the only way to update them is manually through the interface.
4 votes -
Alerts change from time based pattern to include actual alert in subject
So far we are receiving atlas alerts in time based manner which are difficult to undersatnd/analyze just by looking at email subject.
We are expecting a model in which we want to Separate alerts for each instance instead of combining alerts on a single time frame and Changing email alert subject to include alert description. This will allows us to understand the alert by looking at email subject , combine/view all alerts in email client (for example outlook) , write some rules on them and analyze the alert timing pattern by sorting and group by alert description.
For example,
Present…
4 votes -
Allow "Project Data Access Read Only" to retrieve restore links.
Allow "Project Data Access Read Only" to retrieve restore links. Currently, to retrieve a restore link from an Atlas cluster you must be a Project Owner.
In the current version to take the link to the snapshot we need to use Restore Jobs part of the API. Problem is that the same POST endpoint is used for the restore job which can do changes in the system and needs Owner level of the access and to generate link to the stream with the snapshot data. This second type of the job should not need so big access level as should…
4 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 -
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 -
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 -
Atlas - Preferences - My Date Format - allow 24hr
We can specify date format but the time format is limited to 12hr clock. Please allow us to specify 24hr so the activity log and rest of the UI is a little easier to read. Thanks
4 votes -
Atlas tags exposed as labels in GCP billling
When you link your Atlas Account to the GCP Billing, the total cost comes through as an aggregated amount; I wish to use the Label functionality to further drill-down the costs by the Tag names and values assigned to Atlas resources (such as clusters).
This is a followup as suggested by Mongo support representative in support case #01436008
3 votes -
Include “Tag” Field in the Cost Explorer API Response
We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usageBackground
Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
• Organization ID
• Project ID
• Cluster NameTo categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing…
3 votes -
Surface hourly usage data and charges
Usage pattern can change very quickly throughout the day so a daily granularity of usage/cost is not sufficient for us to analyse usage behaviour.
We need a further granularity which is the hour by hour usage and charges in order to help us monitor cost and spot pattern/irregularities.
3 votes -
Add boolean for applying changes only during maintenance window
Add boolean for applying changes only during maintenance window in order to not affect workloads during peak periods.
E.g.: we want to modify the instance type of our cluster, but we don't want to affect workloads during the day, therefore, any change to the cluster should be applied only during maintenance hours. The same functionality should be available in the console. As a matter of fact, all changes should be by default applied during maintenance window and user can choose to opt out and apply them immediately.
See DocumentDB as an example for this feature.
https://docs.aws.amazon.com/documentdb/latest/developerguide/db-instance-modify.html3 votes
- Don't see your idea?