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
-
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
6 votes -
Day granularity for Atlas-managed X.509 certificate
It would be great to add more granularity when creating an Atlas-managed X.509 certificate for a MongoDB user, i mean by day at least.
Thank you6 votes -
Altas CIDR ranges for network containers are too restrictive
Background:
For each MongoDB Altas project, the clusters built in that project are built using a "network container", which tells MongoDB Atlas which pool of IPs it can select from given a CIDR range for its underlying infrastructure.AWS minimum imposed CIDR value/subnet size: /28
MongoDB minimum imposed CIDR value for clusters deployed to AWS: /24Azure minimum imposed CIDR value/subnet size: /29
MongoDB minimum imposed CIDR value for clusters deployed to Azure: /21For customers who elect connecting to MongoDB Atlas via VPC peering, they know that IP space is a scarce resource. Reserving /24 or /21 IP space…
5 votes -
Alert for the absence of a snapshot backup policy
It would be great to have an alert option that notifies when there is a cluster configured without a backup policy defined.
This alert option would be helpful to ensure any defined company backup policy is audited and we are notified if a policy does not exist, or if someone accidently removes any defined policies on a give production cluster.
5 votes -
View billing information at project level
I think it would be a good idea to be able to see billing/invoices at project level. So the project owner will only see the consumption of his projects.
By giving project owners the "Organization Billing Viewer" role, we make it possible for them to see the billing for the whole organization. A new role for the project owner to view only their own project invoices would be nice.
5 votes -
A new role for security auditing purposes
Currently MongoDB Atlas provides two read only roles at project level ("Project Read Only", and " Project Data Access Read Only").
"Project Data Access Read Only" seems to allow access to the data also, while "Project Read Only" role does not allow access to the logs. (https://www.mongodb.com/docs/atlas/reference/user-roles/)
For security officers (internal/external), they need to access to the logs (audit, access, etc) and also to review the configuration; but don't need access to the data.
Therefore, I would like to request a new project level role for security officers with following features.
- access to "Download Logs"
- access…5 votes -
Include "fields" and "options" in index build email notification
Hi, I'm wondering if it would be possible to not only include the database and collection names in the "Index build succeeded" email notification, but also the "fields" and "options" json objects.
It's great to know what indices are built by the team as the database admin, and since there isn't a "createdAt" timestamp in mongodb, the emails would serve as a workaround for that as well.
In short, it would be a valuable addition for our team if the "fields" and "options" data was included in the "Index build succeeded" email notification.
Thanks in advance!
5 votes -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
5 votes -
Atlas project capacity should be discoverable
Atlas project capacity should be discoverable. Based on documentation, it seems project capacity is dependent on various factors and can be arbitrarily increased via support request. We currently do not know how many clusters/nodes we have available to deploy in a given project and that is critical information to inform planning at scale.
5 votes -
Backup persistence after termination should be standard
It is odd that snapshots are tied to clusters and lost/destroyed when clusters are terminated. Snapshots have their own retention policies for a reason. Persistence after cluster termination should be the rule, not the exception.
5 votes -
Change Streams Monitoring and Alerting
Change streams can cause performance issues if not used properly. In some cases, administrators of multi-tenant dbs have no control (and shouldn't) over how various clients create change streams.
I think it is important that we accommodate these use-cases and provide useful metrics in the OM/Atlas metrics pages, and alerts on those metrics. Some potential metrics:
1. Number of change streams open
2. Average change stream lifetime
3. Query targeting ratios for change streams
4. Avg time between consecutive polls of the change stream (and other statistics)
--thought here is that change streams that are polled infrequently will result in…5 votes -
Private endpoint termination protection
Similar to the Cluster Termination Protection, it would be nice to have Private Endpoint termination protection to prevent accidental deletes of private endpoints, which could very likely result in application connectivity loss and downtime.
5 votes -
Granular cost and inventory details
We are building a unified portal to view our databases and almost all other managed cloud providers like AWS provide instance level/node level view of clusters.
Currently, there's no way for me to get instance level/node level inventory details.Also, when billing/cost is generated, it's generated on a cluster-level basis. Since we now have separate sizing for Analytical nodes and Electable nodes, it's better to separate out the cost to be at an instance level.
Again, all cloud providers like AWS do give us instance-level costing for EC2/RDS so I don't see why that can't be technically possible.
Support costs…5 votes -
Notifications
In case of a databreach MongoDB will notify their customer.
Customer is defined as 'the Organization Owner'. However, a databreach should end up with a privay or security officer. It would be a nice feature if some of these roles would be defined and what kind of alerts/nortification they can expect from MongoDB Atlas5 votes -
Restored snapshots from a dedicated instance to a serverless instance
I'd like to be able to spin up serverless instances for automatically provisioned dev/QA environments. I'd like to have production data available in them. So I'd like to restore a dedicated instance snapshot to a serverless instance.
5 votes -
Create Atlas App Services and Link Them To Clusters with Terraform
It would be great to create App Services (Realm Apps) and then create the service link to an Atlas Cluster with Terraform.
This is so that Trigger resources can be created fully within Terraform, rather than having to hack together API calls, CLI commands or manual steps.
5 votes -
A way to enable the Data API via Terraform
I just noticed that MongoDB Data API is no longer in beta (Congrats!). It think it would be quite useful if the there was a way to enable this option programmatically via Terraform.
5 votes -
Activity Feed cluster updates does not show old and new versions
Cluster updates do not show the old version Atlas is updating from, or the new version Atlas is updating to. It'd be great to see both of these pieces of information in the activity feed.
5 votes -
Allow user provided alert templating for Atlas alerts
I want to have the ability to provide their own templatized text for alerts. Often I may want to provide specific instructions to operations personnel for each alert type, or to provide links to relevant internal runbooks.
Other systems such as Datadog and PagerDuty provide this kind of capability.
5 votes -
Add "Triggered Via" or "Initiated By" Filter to Project Activity Feed
I usually visit the Project Activity Feed to discover "who did what", but the feed is littered with events triggered via the System. I would love to be able to filter out those events and just see those initiated by a user. Bonus points for being able to filter by the user :-).
5 votes
- Don't see your idea?