Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1293 results found
-
Forward MongoDB Atlas logs to Securonix
This is a feature request to integrate the forwarding of MongoDB Atlas logs to Securonix.
1 vote -
Disable/Opt out of email notifications
We would like the option to disable email alerts within an individual user's settings.
We have users who need admin/owner level status for multiple projects but do not need to receive granular daily alerting like the rest of the project members. Differentiating alerts on user type alone will not solve our use case.2 votes -
Manage Database by Kubernetes Operator
In our use case, we are dynamically creating feature environments based on the branch name. During this process, we are also creating MongoDB databases in the same Atlas cluster (different envs are sharing the same cluster but with different database names). For now, we need to do it with a separate CI step that should create this DB and delete it when the env is deleted.
It would be great to have the possibility to manage DB create/delete process with Kubernetes CRD. For now it's the only 1 missing feature that is blocking us to start using Operator.
4 votesThis is something we're considering for the future.
But the biggest problem we need to solve is that it's incredibly easy to create/delete/update databases within a deployment via many other interfaces. But if this happens, the Operator's source of truth (the custom resources) won't contain the changes, and the Operator would overwrite the changes using it's source of truth.
-
Integrating mongod audit logs with exabeam
Need to integrate mongod logs with exabeam to view the audit logs. And we need these logs for PCI compliance.
1 vote -
Allow showing Total Usage chart based on Usage Date instead of Billed Date
On the billing page (cloud.mongodb.com/v2#/org/.../billing/invoice/...) there is a “Total Usage” chart that uses the Billed Date to paint the bars.
It would be great to be able to switch to the Usage Date instead.
This would help me to better understand on which day how much usage accrued in terms of costs. I am looking at it because I want to monitor the effects of changes that I made to the backup policy or the effects of code updates to reduce data transfer volumes.
Thanks a lot for considering this!
1 vote -
UI/UX: make site scaling for large screens
UI/UX: make site scaling for large screens, now text fonts are too small
1 vote -
Properly Formatted Prometheus Integration (mongodb_ metrics)
The (mongodb*) metrics collected by the integration lack the metric type and the description is extremely vague (mongodbcatalogStats_views has "catalogStats." as description). It would be easier to setup dashboards and queries if the type (e.g., gauge, counter) was properly set up and the metric provided a proper description.
1 vote -
Domain Mapping for Federated Authentication
Improvements to Domain Mapping for Federated Authentication.
1. Update the documentation (https://www.mongodb.com/docs/atlas/security/manage-domain-mapping/) to clearly state if the TXT/HTML record should persist or if they can be deleted after a domain has been verified.
2. If the record has to persist, consider changing the name of the key. TXT records are public and can be used by security researchers to map all companies using Atlas by looking for TXT records with "mongodb-site-verification".1 vote -
Atlas SQL Interface: Support queries based on BinData (UUID)
We have a need to write reports that query MongoDB via the Atlas SQL Interface using BinData (a UUID with BinData type 4) as selection criteria (see support ticket Case 01313460: Query bindata using atlas sql interface). We were told that this is currently not supported, although querying data based on a unique identifier is a most basic and essential function as far as DB interfaces are concerned.
Example query from ticket: SELECT * FROM bn_events WHERE _id = CAST('6b0be834-c03e-47bc-9c7d-4726a1e8c69a' AS BINDATA)
This is a serious limitation that may prevent us from being able to use Atlas SQL Interface for…
1 vote -
12 hour option for Temporary User
Add support for a 12 hour Temporary User.
6 hours is too short for a working day
24 hours is too long for a working day12 hours is just right.
1 vote -
Performanse advisor node type filter (to exclude analytics)
Performance Advisor should allow selecting node types to exclude analytics nodes.
In most cases, analytics queries don't require indexes as queries are very different and might be filtered by any field.
6 votes -
Edit PSC connections
Allow admins to edit existing GCP PSC networks -- currently, if a client wants to increase the number of IPs allocated in a PSC, they have to increase the limit, delete the PSC, then create a new PSC.
In a Production environment, this can cause 2 hours of downtime while reprovisioning PSC IPs that don't need to be provisioned, rather than scaling the number of IPs in-place.
1 vote -
logs - pull from s3 over private link
When reviewing push to s3 feature, our security teams have raised concerns around 3rd Party having the ability to write into our application team's s3 bucket (push model), the existing pull model (pulling logs via API) transmits logs over internet and additionally requires HA log agents to deployed at our end. As a middle ground if Atlas can expose logs over s3 API that's consumable via private link it will help to address security concerns while reducing the complexity involved in pulling logs over atlas control plane API.
1 vote -
logs push to s3 over private link
Currently push to s3 feature transmits data over internet, due to possible presence of sensitive data in logs and to address security concerns push to s3 feature should support pushing logs over private link.
2 votes -
Adding balancer activity from sharding Statistics into Atlas UI
The customer often experience multiple performance issues in different clusters related to chunk migrations and in each case the customers are struggling with being able to determine that chunk migrations were occurring and started at the same time as the performance issue. The customer is limited in the observability available to identify this problem via Atlas UI:
Using db.serverStatus().shardingStatistics on each shard can provide what the customers need.
In particular, key metrics below will provide good insight on balancer activity :
For donor:
- db.serverStatus().shardingStatistics.countDonorMoveChunkStarted
: The total number of times that MongoDB starts the moveChunk command or moveRange command…
2 votes -
Order the slow queries by shape
We are trying to use the API to get slow queries from a given cluster. Today, each line represents a single command, but it would be very usefull if we could group it by command shape. This way we could for example group it and filter by average running time, so we could simply get the most expensive queries despite the query data.
2 votes -
To Include sub dashboards Format in Atlas Charts
To Integrate related dashboards as sub-dashboards under a single main dashboard to improve organization and navigation
1 vote -
Support for CDK SAM Template in Publishing Serverless Applications in AWS
I suggest that AWS supports CDK SAM Template for publishing serverless applications. Currently, when attempting to publish a serverless application using a SAM template that includes MongoDB Atlas CloudFormation extensions, such as MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList, an error is encountered.
Error Message:
Error: SAM template is invalid. It cannot be deployed using AWS CloudFormation due to the following validation error: Template format error: Unrecognized resource types: [MongoDB::Atlas::Project, MongoDB::Atlas::DatabaseUser, MongoDB::Atlas::Cluster, MongoDB::Atlas::ProjectIpAccessList]
While deployments proceed smoothly, this error arises when attempting to publish the serverless application. It would be beneficial if AWS supports CDK SAM Template for publishing serverless applications, allowing for…
1 vote -
Atlas Webhook Integration and Custom JSON Payload
Ability to specify a JSON body along with their Atlas Webhook's for additional functionality.
6 votes -
Allow Organizations without a Subscription to have linked organizations
Currently, to be able to link organizations to a single paying organization (ie. linked organizations), it requires an active (paid) subscription.
My use-case is that we have an enterprise subscription on our production organization, but wish to have a sandbox organization to test infrastructure as code, creating/deleting sub-organizations, and linking API keys.
In my opinion, developers / administrators should be able to test out managing the org structure in a separate account without affecting the primary "root" paying account structure.1 vote
- Don't see your idea?