Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
1273 results found
-
Have live tool migration re-establish connectivity with on-prem cluster in case of connection failures
While trying out Live Migration tool for data transfer from our on-prem cluster to Atlas, we had an issue where Atlas ran into connectivity issues with the on-prem cluster with respect to Live Migration tool. As the tool couldn't re-establish connectivity with on-prem cluster, we had to cancel migration and initiate data sync all over again. While this is fine for a small cluster, this can't be feasible for a large PROD cluster where we have 20+ shards and with data volume in order of 40-50TB compressed size.
So, even if there is a network disconnect or any maintenance happening…
2 votes -
Migration Tutorial Video
I did a live migration from mLab to Atlas quite recently. Although, the steps for migration were simple and easy to execute it took me alot of time to get over the fear of migrating without losing any data. A tutorial video of the entire process would have calmed my nerves and helped me take a lot less time in the process.
4 votes -
Allow to resend alert to a PagerDuty service
Like with other type of alert targets (Send to), we would like to be able to resend an alert to PagerDuty.
The reason is that an alert sent to PagerDuty can be mistakenly resolved but the real issue is still there, and the alert is still firing in Atlas.
Because it is already firing, it won't fire again so from that moment on, there is no way to get a notification of that alert so we might be missing a real issue.
2 votes -
1 vote
-
Include cluster node list in getOneCluster
Include cluster node information for all nodes in the cluster in the response JSON for the getOneCluster API call. As hostnames are needed for other API calls, there ought to be a better way to get cluster node names.
5 votes -
Precautionary Change/Recommendations for Shard Drops
If a user submits a configuration change to drop a shard, Atlas will sift through the cluster metrics and advise any necessary changes needed in order to complete the change without any errors/delays. For example, it will share the correct number of IOPS/cluster tier that needs to be used since the workload to drain a shard will increase; as well as other precautionary measures that should happen prior to dropping the shard (i.e. balancer needs to be turned on, etc).
2 votes -
Enable live migration tool to work with Global cluster configuration enabled
Currently, there is no Live migration tool option while enabling Global Cluster Configuration in Atlas. Please treat this ticket as a FEATURE ENHANCEMENT REQUEST to make this happen.
3 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 -
Allow to create Dashboard
Please provide feature to create a dashboard for metrics like CPU, memory consumption etc for a cluster or more than one cluster in single graphs like for cpu one graph, for memory one graph like that just like monitoring tools provide for example zabbix screens and dashboards, stackdriver dashboards, dynatrace dashboards.
This is to have a glance on our entire architecture instead of checking each and every cluster every time. This will be particularly useful during load tests or business peak period where we need to check more than one cluster performance.
4 votes -
Alias for Cluster name
Add an alias to cluster name, as we are not allowed to change the cluster name. If we have an option to add an alias to cluster name. We can use it, in-case the user created the cluster with the wrong name. And in-screen u can show as clustername(alias). For better understanding.
1 vote -
Add support for arbiters
We have a situation where we are required to build in an AWS region that only has two AZs (ca-central-1). In addition, there are no other AWS regions in the country (Canada). And due to our requirement around data sovereignty, we can't host this data set within a different country.
Because of this, we can't guarantee our cluster will stay up if we lose a single AZ unless we put an arbiter in a 2nd region (since no data is copied to the arbiter). However, Atlas does not support arbiters currently. I know arbiters aren't ideal, but in this edge…
6 votes -
Love The New Look
Just wanted to say I love the new look!
1 vote -
Better message for "Removed Indexes" in Activity Feed during Atlas rolling index build
During a rolling index build, it is expected to have 2 "Deployment configuration published" notifications - 1 for Added Indexes and another 1 for Removed Indexes. This is because an entry for this desired index is added to the automation config and then the automation agent builds it accordingly. Once the agent is done building it, we remove the entry for that index from the automation config. Indeed, this does not drop the index.
However, from the term of "Removed Indexes", it can cause confusion that the index is dropped. Hence, this feature request is filed for clearer message so…
2 votes -
Trigger event when user confirmation state change
I suggest that after user registered they should ve able to log in regardless of his account confirmation state, but if he is in a pending state, he could not do any read/write operation unless his own user data and his own user extra data,
And the user can also detect if his confirmation state is change
1 vote -
Add Alert for outdated Agents
Add an alert type for outdated agents
2 votes -
Export metrics to AWS Cloudwatch
Have an integration with AWS Cloudwatch to send the metrics from MongoDB Clusters to Cloudwatch so metrics and alarms can be setup in CW.
13 votes -
Add visual information to indicate if a collection is capped or not.
Right now there is no way to tell through the portal or Compass if a collection is capped or not. It would be helpful if there were some visual indicator in the Data Explorer if a collection is capped and if so what the retention parameters (bytes and max documents) are set to.
2 votes -
Implement a refresh button for the BI Connector in Atlas
When changes, such as when collections are added or removed, occur to an existing database with BI Connector enabled, the BI Connector needs to be cycled off and then on. This process is not well explained for Atlas. I feel that a refresh button that ripples Bi Connector in Atlas when changes occur would be beneficial, rather than having to dive in to edit configurations --> slide the "enable bi connector" from off, wait, than back to on.
2 votes -
More detail and lead time around maintenance notifications
When we get email notifications of upcoming maintenances, it doesn't specify if the update is "urgent" or "low". When we received our last notice, it was 3 days out. If it's urgent, then we understand the short time frame around the notice. However, if it's a lower priority update, I would hope we could configure how far out we are aware of the maintenance or at a minimum get notified 2 weeks prior so we can communicate to our end users.
Additional information around what the maintenance is for would be appreciated as well. Something along the lines of "Patching…
8 votes -
Smart backup scheduler (deferring snapshot backups X minutes based on load metrics)
seems like a potential enhancement for the snapshot schedule to consider cpu/connection/etc load metrics before deciding to run or not
3 votes
- Don't see your idea?