Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
-
Ability to create/update a temporary Database user using terraform
Hi
Presently, we can only create permanent database users via Terraform Modules. The creation of temporary DB users is only allowed through the UI or by consuming MongoDb Atlas's APIs. In addition, the "deleteAfterDate" property is only applicable for a temporary user already existent. The point is to avoid using "null_resource" and "local-exec" in our Terraform Modules.4 votes -
Add truncate collection button, delete documents older than...
In the old interface we can truncate collections without using additional software, just using WEB GUI to keep small database size.
It would be nice to have the ability to delete older documents. This option is usable for IOT or medical implementations (Nightscout).2 votes -
Provide an interface that can stream logs directly to Splunk.
I'm trying to get logs from MongoDB Atlas to Splunk, and there's currently no native interface to do it, so instead of streaming to Splunk directly, I'm having to execute https calls in intervals, unzip them and then ship them to Splunk. Many products have interfaces to stream to Splunk directly, and it would certainly be handy in this situation.
7 votes -
Include Human-Friendly Cluster Names in Alert Notifications
Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).
5 votes -
Support GCP IAM for Cluster Authentication
Achieve feature parity with AWS IAM cluster authentication support.
7 votes -
Multitenancy of the billing section in MongoDB Atlas
Hi MongoDB team,
as the organization owner I don't want that my organizational members (developers, project owners etc.) have access to the billing section. Currently every member (independent on the granted rights) has the rights to see the complete billing section and can see the whole invoice incl. the names of the projects. This isn't acceptable regarding compliance because we are working together with external companies and their colleagues shouldn't have the ability to see all invoices.
Please make the billing section of MongoDB Atlas available to handle multitenancy - so that only the organization owner can see the billing…
5 votes -
Allow an "Any Database" option for actions in custom roles
Much like built-in roles have the ability to target all databases/any database, it would be ideal if collection actions could also target any database. Similarly to how, when adding collection actions to a custom role, if you leave the "collection" field blank, it applies to all collections in the specified DB, it would be great if you could leave the "database" field blank too (or add an "any database" option) and have the actions associated with the role be allowed on any database.
This feature gap creates unnecessary maintenance overhead for clusters with large numbers of databases. This is particularly…
7 votes -
Provide callback method for API calls to avoid polling
Provide some callback method (webhook URL, push notification, etc) that an API call can use to indicate it's done. That way the user doesn't have to sit and poll endlessly.
Some examples of where this would help:
- After creating a restore job, waiting for the snapshot download URL to be ready.
- After modifying the automationConfig, waiting for all agents to report that they're in goal state.
3 votes -
Expose the killOp() action when creating custom roles in Atlas UI
It would be nice to have the
killOp()
action exposed when creating a custom role in Atlas.I also think it would make sense to grant this action to the
atlasAdmin
role, but at a minimum I feel that Project Owners should be able to create a custom role that is allowed to kill ops that were initiated by other database users.12 votes -
LDAP configuration using Terraform
We would like to be able to use Terraform to configure LDAP authentication/authorization on projects.
The functionality is available via the API:
https://docs.atlas.mongodb.com/reference/api/ldaps-configuration/However, go-client-mongodb-atlas does not have these endpoints implemented, so that would need to be done before this functionality is included in the provider.
32 votes -
Add tunnelling to allow querying Cloud Backup snapshots
The Legacy Backups have a feature to allow connecting (tunnelling) to a snapshot to query it. This allows querying a database snapshot which is great for quickly inspecting data in the past for troubleshooting. This would be handy to have for the Cloud Backups. With Cloud Backups instead I now have to download a snapshot, load it temporarily on a cluster and remove it when done.
5 votes -
Add Elastic integration to Atlas
Add support to send cluster metrics to Elastic. Elastic has recently been putting a lot of work into their APM and logging solution, this is now a viable alternative to NewRelic and Datadog and is gaining traction. It would be great if Atlas supported sending metrics to Elastic. Please see below for references
https://www.elastic.co/apm
https://www.elastic.co/siemThe use case for this is the same as NewRelic or Datadog. I wish to monitor my Atlas clusters from inside Elastic, create dashboards and set up alerting
13 votes -
3rd Party Hooks
Within Atlas today, we have a number of channel options to send alerts (Ex. OpsGenie, Slack, VictorOps).
I would like to see a hook integration provided by Atlas so any tool can recieve alerts from their cluster. Ex. I can recieve my cluster alert in Microsoft Teams.
3rd party hooks can increase the stickiness of Atlas and improve freedoms for teams and their existing toolsets.
3 votes -
more information in AWS IAM audit logs
We are using MongoDB-AWS for authentication, and have set up the audit log to log events taken by AWS roles. However, there is insufficient information in the logs to identify who is doing those actions, as roles can be assumed by multiple people.
An example log line in the current audit log:
{ "atype" : "authenticate", "ts" : { "$date" : "2021-01-05T00:21:52.628+00:00" }, "local" : { "ip" : "192.168.248.203", "port" : 27017 }, "remote" : { "ip" : "172.31.0.5", "port" : 54195 }, "users" : [ { "user" : "arn:aws:sts::555555555555:assumed-role/developer-role/", "db" : "$external" } ], "roles" : [ {…2 votes -
Set schedules for pausing clusters
It could be incredibly helpful if we had a way to set a schedule to pause any given cluster as well as a schedule to un-pause it. This would help with cost savings and would allow to shutdown development clusters on weekends, after hours and holidays.
2 votes -
Support for delayed replicas
It would be great if Atlas provided support for hidden, priority 0 delayed replicas. For workloads that do not need real time data or situations where data recovery is needed, a delayed replica would be the fastest way to mitigate both of those scenarios.
1 vote -
Live Migrate modal: Allow users to point and click to select another Atlas source cluster
It is often practical to Live Migrate from one Atlas cluster to another Atlas cluster (e.g. to create another staging environment if backups are not enabled on the source, or migrate a production/staging environment to another dedicated project with minimal downtime).
Currently, the Live Migrate modal requires connection details from the source cluster, including the hostname of the primary, port, etc. Validation will fail if there are typos/errors in these inputs.
It would be easier to have a point-and-click option to "Migrate from another Atlas cluster" -- it could be a drop-down menu with names of other Atlas clusters in…
6 votes -
mongomirror with db rename
We have a need to rename our databases as we sync them over to Atlas. However, mongomirror doesn't support that. So that leaves us with mongodump and mongorestore but our databases are large enough that we can't take the outage window necessary to go down that path. When will mongomirror support renaming databases during the import process?
4 votes -
Projects Organization
It would be great if we could organize the projects and not have them all at the same level of organization.
We could use this hierarchy to put rights, consult costs ...
A bit like the idea of Azure's management group or GCP's "Folder".17 votes -
Show max IOPS line on IOPS graphs
When monitoring disk IOPS, it isn't immediately clear when we are limited on IOPS. Having a red limit line on the IOPS chart on the metrics tab would help here.
3 votes
- Don't see your idea?