Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1362 results found
-
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 -
Allow maintenance window definition per cluster
Currently maintenance windows are defined per project. With multiple clusters in a project, maintenance will be performed at the very same time.
We would like to space out maintenance windows per cluster in the same project, to prevent replica set election on multiple clusters taking place simultaneously.
20 votes -
Alert configurations should be unique
Atlas allows for the creation of duplicate alerts. Alert configurations should be unique such that exact duplicate configurations are prevented from being saved.
2 votes -
mongodbatlas_cloud_backup_snapshot_restore_job should wait until the restore operation is complete
mongodbatlascloudbackupsnapshotrestorejob creates a job and returns immediately , but I think it should wait until the restore operation is complete. just like mongodbatlascluster that waits until the cluster is in ready state.
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 -
Warm up cache automatically when there is any server/node restart events
Usually it takes hour or so for the cache to warm up depending on the data size when an server restart scenario occurs ( increasing the tier / storage etc). And there are alternatives like running cache warm up queries to bring the nodes up to speed .
However if this cache warm up should be inherent and automatic for the server restart scenarios .
3 votes -
Purge of unused accounts after X days/months
After X number of days/months (say 12 months), accounts that haven't been accessed or have never been accessed go into a 3 month freeze period, before they are automatically disabled and deleted. A report of such accounts should be auto generated and archived. The freeze period intention sends a warning to the account holder as well as an alert to administrators of the atlas org.
2 votes -
Activity Feed should automatically load new items rather than requiring refresh
Today when looking for items to appear in the activity feed, I have to repeatedly refresh the page which is slow/painful. In future it would be better to automatically stream/poll for changes behind the scenes and load them without requiring a page refresh.
5 votes -
Carbon Footprint Calculator
A widget or calculator in the Atlas UI, where the user can see the projected carbon footprint of a deployment per year while they are configuring the deployment. And / or a live counter of the carbon Footprint for each deployment/project/org.
23 votes -
Multiple Email address for alerting
In alertconfiguration, change the emailaddress argument in "notification" block from "string" to "list(string)".
Main goal here is to allow multiple alert emails like it's possible in the portal.5 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 -
Prevent Federated Users to gain access to other Projects
Hi,
We have set Federated authication and RoleMapping to project. This roleMapping gives Project Owner Rights to a particular project. Project Owner have the right to invite other people into their project.
Role mapping is only applied when a user logs in. However, if the user receives an invitation to a project when logged in (to say Project ***) and accepts an invitation (to say Project YYY, for which they should not have any access), they will receive the Atlas role in that project (Project YYY) designated by the invitation, allowing them to perform any actions provisioned by that role.
…
2 votes -
Enable Private Link for Azure Data Factory
Private Link for Azure Data Factory is not currently supported. This appears to be the most secure way for ADF to connect to Atlas / MongoDB, and support for this feature would be ideal for our use-case.
15 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 the In-Memory Storage Engine to Atlas
Enable the use of the in-memory storage engine in atlas shards. That way atlas users can get the same level of functionality as enterprise. Atlas is a great platform, but not being able to use an in-memory storage engine replica set in a shard is a huge letdown (at least for me).
3 votes -
webhook
Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.
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 -
Send alert on mongodb database users changes and permission changes
This will be a important tool to get alerted if any databases get exposed or hacked.
3 votes -
Migrate to new cluster without auto upgrade (5.1.0)
Hi,
Our clusters are in auto upgraded feature of MongoDB versions right now.We want to stop the auto upgrade feature for now and migrate our clusters to new one with the MongoDB version 5.1.0.
But, when we try to create a new cluster it's not showing the option for version 5.1.0.
And we need 5.1.0, because we're going to restore the data from the current cluster which is versioned 5.1.0.Your help is much appreciated.
2 votes
- Don't see your idea?