Please add killAllSessionsByPattern and kill sessions feature in Atlas UI

To change the resources monitoring function agents which is currently using Shared resources, we prefer it to be on a separate host to have workload isolation

Need to find out a way to fetch the entire cluster status (paused/resumed) for all projects in an organization in a single command/api.

This is required to keep track of the paused cluster remaining days and thus save a lot of unnecessary cost.

The AZ details (ideally including the AZ ID) for each replica set member would be helpful to display in the Atlas UI, mainly to easily verify nodes are distributed across AZs.

From the collections tab, show an aggregation of typical queries (for that collection) to help discover index opportunities

It would be helpful to be able to view the resources used by the BI connector in Metrics, similar to how you can view resources used by Atlas Search (Search Disk Space Used, Search Normalized Process CPU, etc). This could help with identifying issues due to resource intensive queries submitted through the BI connector.

Currently it is only possible to guess that an issue could be related to the BI Connector by viewing system resource use.

Given that I address certain kinds of queries to certain tagged nodes,
As a developer,
I would like to filter the "real time view" tab to show only activity for my tags
So that I can monitor how my application impacts its node

add an audit log even when any user within the organization creates a new project. Currently you can see when a collection is created, but nothing for new projects. This is helpful for auditing and accountability purposes.

This metric will show the available bytes for reuse. If it's too much and its graph is changed a little bit, we can decide to compact it for saving cost (from disk usage).
Currently, we have to run dbstat command to see the available bytes for reuse and can't know its trend.

It would be good to see Log Redaction work in Atlas as well, similar to On Prem
https://docs.mongodb.com/manual/administration/monitoring/#log-redaction

Add process measurements for monitoring WiredTiger data handles.

From Atlas documentation https://docs.atlas.mongodb.com/reference/atlas-limits/#collection-and-index-limits :

While there is no hard limit on the number of collections in a single cluster, the performance of a cluster might degrade if it serves a large number of collections and indexes. Larger collections have a greater impact on performance.

but now there is no way to get this information except db.serverStatus()

In Atlas, it would be ideal if you could specify a percentage of total memory as the threshold for the "System Memory: Available Is..." rather than a literal number value. If it was possible to set this as a percentage, then the alert could be applied to all hosts in a project, rather than having to set hostname conditions and create a separate alert for each cluster.

We have set up alerts and have noticed that when a condition is back to normal, there is another alert generated acknowledging its closed. Is there a way we can manage this (like disable or block it for some alerts)?

It would be useful, and contribute to a complete alert experience, to have auto-scaling event alerts configurable in project alerts. Users should be able to send alerts to their target system of choice, and prevent numerous alerts to specific users.

Currently auto-scaling alerts are only emails to project members (as per the following https://docs.atlas.mongodb.com/cluster-autoscaling/#acknowledge-auto-scaling-events).

Examples of configurable alerts:
- Scale-up unsuccessful due to max cluster-tier too low -> change email recipient of these alerts
- Scale-up event has occurred -> send alert via SMS and Slack.

Implement better monitoring and alerting for WT dirty cache ratio. This should include sub-minute resolution and support an understanding of eviction workload as well as performance impact of checkpoints under heavy write workloads.

I would like to be able to track the size of our collections (i.e. # of records, total disk size) over time. It would be ideal if there was an automated way to do this with Atlas, perhaps with Charts ?

We have configured several alerts and are having them emailed to us. The subject line of the email alert is something like "[External]Alert - <CLUSTER NAME> - 2021-04-08T12:26Z". We would like the subject line to show what exactly is the alert for - for example - if the alert is for "System Memory: Available has gone below 3.2 GB", we would like the subject to include this information. All the email alerts have the same subject line except for the change in time. Please consider this request. Thank you.