Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1365 results found
-
Allow custom duration for Temporary Users
In our software development lifecycle, we have sprints that are 2 weeks long.
We create temporary users for Software Engineers that are "onCall" during a sprint. The role is moving to a different engineer each new sprint.
It would be great to be able to specify an explicit
deleteAfterDatevalue or a custom duration greater than the current 6 days.3 votes -
Scaling cluster connections independent of cluster size/tier
Currently whenever you want to increase Atlas cluster connections, you have to scale up Cluster Tiers. When an application doesn't require additional disk storage but only additional connections the additional cost is difficult to justify.
18 votes -
Be able to see the replica set member states via MongoDB Atlas on a Datadog dashboard and get alerts if it changes
It doesn't look like these health metrics are available for the Atlas product. Would love to be able to use the metric mongodb.replset.health in MongoDB Atlas for both monitoring and alerting so that we can see the replica set member state on a dashboard as well as get alerted if it changes.
5 votes -
Expose unplanned cloud provider hardware issues in Activity Feed or logs
It would be good to post-facto expose some indication (in the Activity Feed, or a logfile or alert) that an unplanned VM migration occurred at the cloud provider level. This would allow customers to identify and distinguish cloud provider hardware issues from cluster issues arising from other causes.
6 votes -
Need Monitoring Feature for MongoDB Charts data transfer usage / alerts
We need to use MongoDB charts but we want to ensure that we don't go beyond the 1GB Free data transfer threshold limit. As per support there is no such monitoring feature . Requesting to add a new feature that will:
1) Help us to automatically monitor the data transfer usage for MongoDB chart
2) Alert the team via email in case it reaches 1GB free threshold limitThanks
1 vote -
Update the MERN Stack tutorial, it's out of date.
RE: https://www.mongodb.com/languages/mern-stack-tutorial
The MERN stack tutorial is out of date and can't be completed in it's current state.
- Section on creating Atlas Cluster is out of date and needs updating.
- The React section uses the old Class way of doing things, this should be updated to use Functional Components and Hooks.
- Uses the old React Router system.
You might as well remove this tutorial in it's current state.
My solution for MERN stack tutorial using functional React components and TypeScript is available here:
https://github.com/carlwicker/mongodb-atlas-MERN-typescript1 vote -
PITR should allow to choose which snapshot to use as base
PITR mechanism does not allow the user to choose which snapshot to use as base before replaying the oplog. Given that Atlas does not validate the snapshots after they have been taken, the user ends up needing to setup their own validation process. That alone is not a problem. However, when one needs to use the PITR mechanism, not being able to select a previously validated snapshot may lead for PITR restores to use unvalidated snapshots.
Either Atlas should enable, uppon choosing, the validation of snapshots right after they are taken, or allow the selection of valid snapshots (snapshots taken…
2 votes -
Generate and send MongoDB Alert emails without graphics
Images are always added when generating mails, and unfortunately, our central monitoring system can't cope with that. It would be great if you can generate and send MongoDB Alert emails without graphics.
1 vote -
Get only one invariant IP address as addressee when using webhooks for alerts
When using webhooks, alerts can unfortunately be sent from a large number of IP addresses. This is problematic for our network team and security requirements. It would be great if there was a way to get only one invariant IP address as addressee, possibly by putting a proxy in between.
1 vote -
Increase monitoring metrics resolution retention time on views of 1min & 5mins
The speed at which usable monitoring metrics data (1m, 5m) is purged and reduced to 1hr is way too quick.
After 1hr, the ability to analyze these metrics that are crucial to investigating a performance issue were lost and hindered the root cause analysis.
I would suggest that 1m or at least 5m resolution metrics be retained for at least a week before being purged.
23 votes -
Allow setting of advanced server parameters such as disable flow control, ttlMonitor and redactClientLogData
For some more advanced/demanding use cases, advanced server parameters are key to provide the performance/latency or security that applications will require, either due to contractual or complaince obligations.
FlowControl throttles writes for consistency sake, but for very low latency use cases it becomes a factor for "perceived" client SLO breach. In such particular scenarios, the cost consistent across all replicas is higher than low latency reply.
redactClientLogData is important to ensure complaince with several sectors such has identity management.
TTL monitor should be able to be controled via API call to better manage the migrations between self-managed clusters and Atlas.
1 vote -
Delete documents from backups
Allow to delete documents from existing backups based on a query.
When off-boarding customers, we sometime need to delete all of their data, including historical data from backups. Having the ability to clean up those backups, without having to restore, delete, and take a new backup, would be amazing.
2 votes -
Allow multiple private endpoints (Private Link Service) per region in multi-region cluster
Some situations require multiple private endpoints (using the Private Link service) to be created per region. This is not currently supported for multi-region replica sets.
One scenario is especially for when there is a shared VPC/VNet for initial transit from on-prem to cloud plus another VPC/VNet for an application. Both of those VPC/VNets would want a Private Endpoint to connect directly to the Atlas cluster. Even if it is possible (sometimes is not), routing traffic via multiple VPC/VNets would mean 3 hops to Atlas from on-prem
14 votes -
Support Dynatrace integration for monitoring with Atlas
This is a request to support an integration with Dynatrace for monitoring MongoDB deployments in Atlas.
20 votes -
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 -
Display better Slack notifications
Currently, MongoDB Atlas Slack integration only send RAW text.
For easier reading, it would be nice (if not a must have) to leverage Slack notification format to have colors that represent at least the state of an alert.
Here is a suggestion from common things we can see in other tools:
* alert.open: Red
* alert.close: Green
* alert.update: Yellow
* alert.acknowledge: Grey
* alert.cancel: Brown
* alert.inform: BlueBonus: Leverage Slack App capabilities and have a
/command to acknowledge an alert directly from Slack.3 votes -
New Default Alert for Connection Timeout
It would be helpful if there is a default alert in the Atlas UI for a connection timeout, rather than this only being in the log file.
1 vote -
Add a simple log filter in the Atlas log API call
In the Atlas log API call, add a new Request Query Parameter which allow people to set a phase or string, to avoid downloading log lines including this phase or string.
So people don't have to download large quantity of log messages that they don't need.
For example the the NETWORK log message between replica-set members.
3 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).
25 votes -
Document Atlas Cluster Tier Performance Expectations
Document approximate Atlas cluster tier performance expectations that application development teams could reference when requesting an Atlas cluster (IOPS, max connections, network performance).
This information is currently available in the Atlas UI.
Other cloud providers such as CloudAMQP do this: https://www.cloudamqp.com/plans.html.
3 votes
- Don't see your idea?