Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1258 results found
-
Monitoring Integration with Splunk
Unlike a connector (https://feedback.mongodb.com/forums/924145-atlas/suggestions/40688308-splunk-connector-for-atlas) it would be useful if Alerts could be sent to Splunk.
14 votes -
New view with connection statistics
It would be valuable to have a per-cluster view showing an overview of connections into each cluster including:
- The number of connections per hours (opened, closed == churn)
- Which IPs connections are coming from and how many from each over time
- What drivers are being used for these connections and from which IPs
- Which user is opening the connections
This information can be very useful in understanding which applications/microservices are opening up the most connections, and helping to find old drivers etc.
25 votes -
Using Online Archive with Customer Encryption Keys
I'd like to use Online Archive but I need to use Encryption Keys that my company manages, not ones provided by MongoDB.
11 votes -
Add "scheduled scaling/suspend" option for certain clusters
There should be an option to schedule scale up/down or suspending/resuming at specified time & day.
For example, DEV environments could be auto-suspended at 6pm and resume at 8am on weekdays, and be suspended all weekend.
Production clusters could be scaled down e.g. from M80->M60 every evening and on weekends rather than being suspended completely.
This would help save money but would need to be coordinated with the existing auto-scaling based on load.
This would need to be at the cluster level since sometimes different clusters in a single project could have different workload patterns.
31 votes -
Azure Stack Support
Many of us have a requirement to host our databases in countries without an AWS, GCP or Azure data center.
Azure Stack is a hybrid cloud solution that allows vendors to use Azure in their local data centers using the same APIs. MongoDB atlas support for this would be immensely valuable.
2 votes -
MongoDB Sink Connector - Confluent Cloud
Confluent cloud -Mongodb Sink connector requires Atlas whitelist IP to 0.0.0.0/0 which is a security issue on our side. Can mongodb partner with confluent and provide a solution that can be accessed through VPC private link? We are very interested in mnogodb Sink Connector for our solution so we don't have to maintain aws ec2 instances for the sink connectors.
https://www.confluent.io/blog/confluent-cloud-offers-kafka-mongodb-connector-fully-managed-clusters/
1 vote -
Using replica set tags for invoice categorization
Customer would like replica set tags added to the invoice as a column, in order to further categorize costs. In some instances, the customer has multiple products assigned to a single cluster, and putting the product name in the cluster won't suffice.
The current solution is to use the Invoice API, and then call the Cluster API, in order to programmatically build out a CSV containing the cluster tags as an additional column in the CSV.7 votesWe recently released tags on database deployments. You can apply tags to new or existing clusters or serverless instances.
https://www.mongodb.com/docs/atlas/tags/
We are planning to have these tags displayed in billing Invoices and we'd love to hear more from you. Reach out to me if you'd like to provide additional feedback about this feature request.
-
Splunk connector for Atlas
We need a way to easily ingest logs into Splunk. It needs to be all logs - node and web portal activity. Ideally a Splunk connector would be provided but a stop-gap measure would be the ability to configure Atlas to write all logs to an Azure storage account.
Lack of native log ingestion ability may be an Atlas deal killer for us.
32 votes -
Aggregation builder history
Add some way to restore old aggregations pipelines from history, that way, even if I accidently closed the UI. I will have backup.
1 vote -
API Improvements - OpenAPI and more auth options
The API should be documented with OpenAPI to allow better tooling.
Ideally using the above OpenAPI spec you could auto generate a SDK or API client for popular languages.
Lastly, the API should accept authentication options other than digest. There is very poor support for digest authentication by popular HTTP clients. I don't like trying to implement security protocols myself, as there is often some quirk I have not fully understood that ends up leaving me less secure than I hoped.
In many questions online when searching for information about digest authentication, the person asking the question is asking about…
12 votes -
Atlas alerts - include duration and date/time alert was closed
currently alerts (sent to SLACK but probably other formats as well) reads this:
Project: OS1
Organization: SE Atlas
CLOSED
Host is down
OS1-g-shard-18-05.bxxxxq.gcp.mongodb.net
Created: 2020/06/11 03:44 BSTType: Mongos
It would be helpful to also include:
Closed: 2020/06/11 07:44 BST
Duration: 1h 53mAs the slack is usually set to each users timezone it creates a confusion when one is looking at how long issue lasted.
This should be easy to implement and it would improve end user experience a lot.Same would be nice on Atlas 'closed alerts' tab - there seems to be no way currently to get…
4 votes -
Expo support
It would be great if we could use "MongoDB Realm" with Expo (expo.io).
I understand that the React Native SDK would be hard to integrate therefore the Web SDK for MongoDB Realm would be the ideal integration choice.
Many people use Firebase/Firestore's Web SDK with Expo, enabling the MongoDB Realm Web SDK to work with Expo in the same way would allow many Expo apps to use MongoDB Realm.
2 votes -
Log user Login to Activity Feed for Auditing
When a user logins into the Atlas Portal this is logged to the Activity Feed.
This feature would allow to better user auditing and identify potential security breaches.
21 votes -
Add SHA-256 as Digest Authentication Algorithm for API
For compliance with NIST and other standards, it would be preferred to use SHA-256 as the algorithm for digest authentication for the public API as opposed to the currently implemented MD5.
3 votes -
Provide a granular mechanism to disconnect and disable all active sessions during a planned maintenance.
Provide a per cluster mechanism to shut off client access for restore operations.
3 votes -
Change Username
Ability to change your username after registration and be able to re-use it should you need to.
5 votes -
Please could you extend the modify cluster API so that when an M20+ cluster is downsized to the next size the API command executes a sanity
Please could you extend the modify cluster API so that when an M20+ cluster is downsized to the next smaller size, the API command executes a sanity check to see if the smaller size has sufficient resources?
Return a 40x if the smaller size has insufficient resources.
Many user have Production systems that don't need huge resources over night so smaller machine size is sufficient
1 vote -
Make use of lazyloading, and use dynamic frontend components
The cloud atlas frontend is very buggy, and not usable at all, even with a fast connection takes minutes to load a page on click.
I think we are loading all the components and required data from server side.
Instead we can simply load the core components, and show a user friendly spinner, that will stop spinning once content is loaded via an XHR request. This would be so much more user friendly, just showing them a spinner (maybe estimated time as well).Currently the page stays blank white, which is terrible UX.
1 vote -
Dynamically Calculate Timestamp Limits for Continuous Backup Restore (via OPLOG Timestamp)
Currently, you can put in a OPLOG TIMESTAMP value that exceeds the maximum / minimum value for the Continuous Backup Time Window.
For example, on the "Date & Time" tab of the "Point in Time Restore" menu, you are given a warning that specifies: "You can only restore to a specific point in time after MM/DD/YYYY HH:MM"
This should be added to the "OPLOG TIMESTAMP" tab where a warning could be given such as "You can only restore to a specific point in time after XXXXXXXXXX" (Epoch time).
As such, you should enforce data form validation so that a user…
1 vote -
Change the term "Whitelist" to "Safelist" in the Atlas Network Access UI
To avoid use of terminology that for some will have racial connotations remove the term "whitelist" from the Atlas UI.
1 vote
- Don't see your idea?