Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
62 results found
-
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 -
Google Data Studio Connector
Create official Google Data Studio connector.
5 votes -
Add specific database API Metrics for MongoDB Atlas.
A while back we ran into an issue where we ran out of connections in MongoDB Atlas. It took quite a while to determine which database was being overrun with bad connections. It would be very nice if the API, which we use to pull metrics into another monitoring platform, allowed us to get certain metrics at the database level instead of the overall system level. The metrics I am suggesting are
Active Connections
Response Time
Failed Connections
Number of requests
Operation Execution TimeThese would help us more quickly discover the source of the problem and trace it back…
4 votes -
Allow Network Peering to be used by Atlas Triggers / Realm Apps
What is the problem that needs to be solved? Some users want to receive outgoing network connections (e.g. with HTTP/HTTPS traffic) from Atlas (Atlas Triggers / Realm Apps) via their configured Network Peering, i.e. via private IP address space (so that everything is kept in private IP address space and nobody outside could reach it). Example: customer would like to have Atlas Trigger / Realm App which will notify (via HTTP) some of customer's internal system(s) about a change/trigger.
Why is it a problem? (the pain) Current Atlas (Atlas Triggers / Realm Apps) behavior does not allow to use private…
4 votes -
Datadog integration for AP1 region
I am using Datadog region AP1 (Japan) and I learned that Atlas doesn't support the region for the integration.
It would be really great and helpful if the integration supports the AP1 region.
3 votes -
AWS ME Central Region Support
I have an ECS cluster in AWS me-central-1 region and I am not able to establish a peering connection with my AWS VPC as me-central-1 region is missing in the options. When will this option be available?
3 votes -
Add per-user connection limit
To prevent one user/application from exhausting available connections it would be extremely helpful to have the ability to set per-user connection limits.
This connection limit would only prevent the specified user from connecting once their limit is reached and still allow other users to connect.
3 votes -
Add Tailscale peering
In lieu of doing 0.0.0.0/0 network access, it'd be great to peer into Tailscale so that anyone that is authorized in our organization's Tailscale VPN can connect effortlessly.
3 votes -
Support for customer-managed keys (CMK) on the volume-level instead of Encryption-at-Rest
For some customers managing a set of low-latency workloads is crucial, so volume-based encryption using their own KMS encryption keys is preferred over the encryption-at-rest feature of the WiredTiger storage engine. https://docs.aws.amazon.com/kms/latest/developerguide/key-policy-modifying-external-accounts.html
The support is required for clusters, their backups and Atlas Data Lake.3 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 -
mongoexport with Client Side Field Level Encryption
I would like to have mongoexport and mongodump tools with Client Side Field Level Encryption /Decryption. Please consider while developing new feature.
3 votes -
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 -
MongoDb Atlas Network Peering with Oracle OCI (Similar to Azure and AWS)
Please add similar Atlas network peering capabilities as that of Azure and AWS, for Oracle Cloud Infrastructure customers. We are currently using Azure, but would like to use OCI as well.
2 votes -
tgw support for Atlas
Can you please provide TGW support for Atlas? We are using confluent.io kafka with TGW, and found ourselves caught up in situation where kafka has no direct access to atlas, both our EKS and kafka are directly connected to Kafka, but there's no way for kafka to access atlas, because EKS and atlas are connected over vpc peering. We do not take interest in PrivateLink. Our Kafka needs direct access to Atlas because we are running the mongo source connector. Only viable solution now is to run the mongo source connector on our EKS, which while works defeats the purpose…
2 votes -
Add EventBridge integration for Serverless instances
Currently EventBridge integration doesn't work for serverless instances
2 votes -
Prometheus metrics formatting to match Grafana
Building on "Export metrics to Prometheus" (marked as completed) https://feedback.mongodb.com/forums/924145-atlas/suggestions/40463872-export-metrics-to-prometheus
I have configured the Prometheus metrics integration to make metrics available to Grafana Cloud which has a MongoDB Integration built in. I was disappointed to see that most of the metric names don't match the ones expected by the MongoDB Integration in Grafana.
The MongoDB documentation doesn't define a standard metric nameset so I appreciate that this is nominally correct behaviour, but it would be good to see some consistency between the MongoDB Atlas integration and the metrics expected by Grafana.
2 votes -
Allow atlas integration with Jira to create tickets directly based on Atlas alerts
Atlas alerts setup should be able to directly create a ticket in the Jira board to the respective team. This will resolve the burden to check email alerts for alll the setup alerts.
Instead, we can setup the critical alerts in such a way that it will directly create a Jira ticket.
Thanks,
Rohan Kumar2 votes -
New relic integration
We have an atlas account where all of are databases are, and we use new relic for monitoring and alerting.
It would be great if i could show in new relic dashboards of the status of our mongoDB, because all other dashboards are already there2 votes -
Allow more than one DataDog API Key
When I enable the DataDog integration in Atlas, I can add just one DataDog API Key. It'll be great if I could add two or more DataDog API Key.
2 votes -
description in sso group mapping
Add a description field in the Atlas UI in the group mapping page when SSO is enabled. Today only an object ID is available.
2 votes
- Don't see your idea?