Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1262 results found
-
1 vote
-
snapshots without indexes
It would be great to have the option to save Atlas backup snapshots without indexes. When using TTL indexes, when the data is restored, it is automatically removed because it is expired. Being able to create snapshots without indexes would save a lot of time to the current workaround.
6 votes -
Allow cost allocation tags
on behalf of the customer,
would be great if we could allow tags on Org/ project level for cost allocation reasons (similar to how AWS allows this). When creating a project we can eg. add the type of environment, cost centre, bearer etc - without it showing up in the name. Does not necessarily need to show up on the invoice but we must be able to create a view which includes this info.24 votesI'm excited to announce that we recently released tags on database deployments. Start applying tags today and they will soon be available in billing invoices.
https://www.mongodb.com/docs/atlas/tags/
-
Online Archive - Automatically defragment data file and release disk space after archiving
This is a request for Atlas to automatically defragment the data file and for the WiredTiger storage engine to automatically release empty space to the operating system, for clusters with active Online Archive.
After implementing Online Archive, and seeing data be archived to S3 based on our archiving rule, we expected the available cluster storage to increase since Online Archive had effectively deleted data from the cluster.
However, MongoDB Docs states: "When you archive data, Atlas first copies the data to the cloud object storage and then deletes the data from your Atlas cluster. WiredTiger does not release the storage…
7 votes -
Increase the notice period for changes
You need to increase the notice period that you provide to your customers for changes that could affect their ability to connect to their database.
A good example of this was the upcoming change announced yesterday "Prepare for MongoDB Atlas TLS certificate root change starting May 1, 2021". You provided 3 days notice which is woefully inadequate.
I work with a lot of large financial institutions and have contractual obligations to provide them with 20 business days advance notice for any planned maintenance. This is simply not possible with the notice periods that you provide.
1 vote -
Manage Database Access and Network access
I would like to give colleagues the ability to manage Database Access and Network access for a project without giving the the project owner role.
A way to provide more granular access in Atlas would be nice
10 votes -
max database users not visible
We need more than 100 database users, and have had the limit raised for existing projects, but new projects require us to have the limit increased. There is no way for us to verify which projects have the default 100 database users and which ones have had the limit raised. It would also be nice to track the percentage or number of database users available as a metric.
14 votes -
Include cluster labels in the billing usage details
Similar to how AWS includes tags/labels in their billing dashboard, I'd like the ability for my cluster labels to be included as a column in my billing usage details (or even the exported CSV).
This will allow me to categorize my billing usage as granular as clusters in addition to the current method which is by project.
59 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 domain or URL for whitelisting
Currently Atlas IP Access List entries allow to specify only either a single source IP addresses or ranges of IP addresses using CIDR notation. It would be great if user can add a domain or url for whitelisting where the IP address or range is not static.
3 votes -
Export results of an aggregation query to csv file
I have created an aggregation pipeline from the aggregation tab of a collection but unable to export the results of that query to a CSV file.
2 votes -
Seeing ports that Clusters listen to
In your documentation and even through the atlas web api, there is no straightforward method to see what ports my clusters communicate on. This is highly frustrating as I am using the Mongodb Atlas Private endpoint and need to Allow Inbound/Outbound communications on certain ports for the endpoint to work.
1 vote -
Improve Cluster Name Limits
Cluster names currently impose the following limits:
Cluster names shorter than 23 characters can't end with hyphen or dash (-)
Cluster names 23 characters or longer can't use a hyphen or dash (-) as its 23rd character.
Instead, we should either trim or replace the hyphen at the end of a 23 character name.
3 votes -
1 vote
-
1 vote
-
1 vote
-
in Atlas Cloud Manager, sort the network IP access list
page security/network/accessList
the list of IP addresses is unsorted and unmanageable
please allow sort by IP or Name (Comment)
1 vote -
8 votes
-
Tag-aware permissions to control access to analytics nodes
MongoDB has the great future of Workload Isolation based on node tags: we can add nodes tagged for analytics or reporting and then configure the same tag for this type of connections so that they do not interfere with the main operational workload.
But it is the responsibility of the BI/Data Scientist/Analyst to properly configure the connection: it cannot be enforced in a centralised way. It would be great if MongoDB permissions could be "tag aware", and allow access for a particular user only to some nodes of the cluster.
5 votes -
SAML login on feedback.mongodb.com does not work with Google Auth
It shows "SAML Error" and redirects the login page to cloud manager. As a result the login success is never passed to feedback.mongodb.com, it's necessary to login again (on the second attempt, it works)
1 vote
- Don't see your idea?