Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
Allow to provide names/descriptions for peering connections
If the user has 3 peering connections in a project, it's error prone terminating one, as you may end the connection with the wrong VPC and cause a disaster. Adding a description field allows to clearly see the purpose of the peering.
1 vote -
Cluster Update Details in Activity Feed
When a cluster update happens and things change such as the certificates, why wouldn't this show in the activity feed? The only thing noted in a recent issue we had was "cluster update". If we could see the details of the update we could have resolved our problem quickly without opening a case.
10 votes -
API Key Expiration date
We have a security reqirement that secrets must expire after 2 years.
Therefore it would be awesome if MongoDB Atlas API Keys would support an expiration date.
Somethig similar exists for the IP Whitelisting. Here we have the option to remove IP Whitelist entries after er certain time period. But for API Keys it would be better to have an expiration date and keep the API Key in the list even if its expired.
In addition it would be good to have a daily notification once the expiration date is ahead less than 30 day.
20 votes -
Bytes available for reuse metric
This metric will show the available bytes for reuse. If it's too much and its graph is changed a little bit, we can decide to compact it for saving cost (from disk usage).
Currently, we have to run dbstat command to see the available bytes for reuse and can't know its trend.2 votes -
Accept Cryptocurrency Payments
Accept cryptocurrency payments for billing purposes as Paypal or Cards are very unreliable. Recommended cryptos - Bitcoin (BTC), Ethereum (ETH), Bitcoin Cash (BCH), Dash.
Commerce between users and mongoDB platform will greatly improve by allowing payment mechanisms that have instant transactions at a much lower fees.
5 votes -
improve error messaging
We are running into misleading error messages that learners are complaining about. This error appears when a user tries to use a $limit stage and forgets to add a $ while connected to a Free Tier Atlas cluster:
"OperationFailure: limit is not allowed in this atlas tier, full error: {'ok': 0, 'errmsg': 'limit is not allowed in this atlas tier', 'code': 8000, 'codeName': 'AtlasError'}":
This has been confusing for users. Is there a way that we can catch this issue more precisely and issue a syntax error instead?1 vote -
Add information to the billing API reponse
When retrieving the billing details through the API, we are missing some information for a perfect understanding (and automation) :
- Number of nodes of the cluster. Indeed, without this information, the field "quantity" is kind of complicated to interpret
- Group Name. Each entry is attached to a groupId, but sometimes when the project has been deleted, it is impossible to retrieve its name, so pretty complicated to interpret (in the UI, the group name is available, so I guess it can be in the API)
15 votes -
Support ISRG certificate selection in mongodbatlas_cluster
As described in https://docs.atlas.mongodb.com/reference/faq/security/ and a recent email announcement, the root certificate is changing. Changing the cert used is available in the UI, but not in the provider.
It would be useful to add support for certificate selection.
1 vote -
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.
8 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.27 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…
16 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
11 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.
17 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.
73 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-redaction5 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
- Don't see your idea?