We had an incident where the PRIMARY node was considered healthy internally and could communicate with other nodes but lost connectivity with other external services. In these type of cases it would be great to have external connectivity monitoring that can detect whether the PRIMARY is accessible from outside of the cluster.

We should have Zabbix integration to monitor the performance of MongoDB Atlas.

Zabbix is OpenSource popular monitoring tool available and many of enterprise organizations use this tool.

Please add Zabbix in Integrate with Third-Party Monitoring Services.

e.g. list collections, collection size, collection indexes, etc.

It would be great to have an uptime report be it weekly or monthly basis which can be extracted and presented anyone who would like to have an high level overview.

It would be very useful to have some details provided in Atlas to trace the execution of the trigger, like the _id and operation type at a minimum. When a trigger executes the only information we see in Atlas is [
"Sent to AWS EventBridge"
].

it will be very helpful for Atlas customer and Atlas support if there was aa feature to clock on any point on the monitoring graphs, and copy the current time into the computer buffer - in order to paste the specific date/time information into a case

currently, if we click on a point we can see the time/date at the bottom of the chart, however we cannot copy it because as soon as we move the mouse, the time/date it is hidden from view

The CPU Steal % metric and alert seems to be currently implemented only for AWS. Please implement it also on Azure, as there is no easy way currently to get alerted if the underlying burstable VM (e.g. for M20) runs out of credits ...

Currently the Process CPU and Normalized Process CPU metrics for all clusters appear to only show the CPU for mongod. For sharded clusters, please add a metric to track mongos (and possibly mongot, for those using it) usage.

In the profiler page, the charts scale do not make sense.
The maximum values in the Y axis are very high which make the investigation very difficult if the actual values are smaller.
I suggest that Y axis values would be dynamic to each the research.

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.