Atlas

Display EBS actual disk information (gp3)

Currently, clusters created on AWS have gp3 volumes according to support. However : * the configuration displays max IOPS 6000 for M50 clusters even though documentation states that iops scale 3:1 with the volume size in GB (1 GB = 3 IOPS) regard...

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

6 VOTE

Atlas Shard Management

Currently the Atlas UI only presents options for how many shards a cluster can have. Putting in a suggestion to perhaps allow similar functionality / features to Cloud Manager's shard management as shown : https://docs.cloudmanager.mongodb.com/t...

Guest over 5 years ago in Atlas 0 Submitted

2 VOTE

Better streamlined logs in GCP

Running Application and MongoDB in the same public cloud provider. Want to have logs in one place so that in case of any issues, I can debug any production issues properly. For example, in our Development or local environment, we have everything r...

Guest almost 2 years ago in Atlas 0 Submitted

2 VOTE

Query profiler drilldown by number of write conflicts

One sort of issue that can lead to elevated CPU utilization but is otherwise hard to identify is queries with high numbers of write conflicts. Having some way to drill down to queries that exhibit these symptoms would be quite convenient.

Guest almost 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

6 VOTE

Add Cluster name to process list api

Currently the processes API (https://docs.atlas.mongodb.com/reference/api/processes-get-all/) returns only the ReplicaSet name of the process not the cluster name, while the cluster API (https://docs.atlas.mongodb.com/reference/api/clusters-get-al...

Guest over 5 years ago in Atlas 0 Submitted

2 VOTE

In Atlas, add an alert condition for long-running queries

Eli Solo almost 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

7 VOTE

Give an option to pause the cluster as a parameter, at the moment it is auto activating after 30 days of cluster pause which is not required

Give an option to pause the cluster as a parameter for specific duration of time, at the moment it is auto activating after 30 days of cluster pause which is not required for all the users and manually we have to keep an eye on this at the moment.

Guest over 6 years ago in Atlas 0 Submitted

2 VOTE

Forward MongoDB Atlas logs to Securonix

This is a feature request to integrate the forwarding of MongoDB Atlas logs to Securonix.

Guest almost 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

3 VOTE

Include more actionable data in Alert emails

Currently the alert emails just link to the profiler page with nothing selected. This makes it guess work if there are multiple items in the profiler to examine. If you are unable to check the profiler within 24 hours of the email, no data could e...

Guest almost 3 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

1 VOTE

org level resource utilization for projects

Org level resource utilization for all Project resources - usage for clusters - CPU, Database Storage Memory , Data transfers, backups to view over utilization / under utilization of resources.

Guest 11 months ago in Atlas Monitoring, Alerts & Observability 0 Submitted

Please enter your email address

FILTER BY CATEGORY