Atlas exposes a few hardware metrics including Util% (presumably obtained from iostat or similar). However this metric is not very significant in the age of SSDs - a volume could be 100% utilized and still have spare capacity. A more useful storage-level metric is Average queue length - this is easier to interpret (high queue length = storage contention).

Would it be possible to add this metric to Atlas monitoring?

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

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.

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.

Customer is requesting that an alert be sent out if project IP access list gets changed

Hi MongoDB Atlas Team,

Some of enterprise customers are left out with improper monitoring via Webhook to ServiceNow (an ITSM tool). Can you please improve on it so right set of fields can be included like "Priority", "Service", "Assignment Group" etc. other details which can be filled up via dropdown or entered manually so alerts to generate incidents via ServiceNow.

Regards,
Varun
Toyota Europe Database Team

Within Atlas today, we have a number of channel options to send alerts (Ex. OpsGenie, Slack, VictorOps).

I would like to see a hook integration provided by Atlas so any tool can recieve alerts from their cluster. Ex. I can recieve my cluster alert in Microsoft Teams.

3rd party hooks can increase the stickiness of Atlas and improve freedoms for teams and their existing toolsets.

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)?

We would like the possibility to freeze the row S S P (freeze the top row) when we scroll down to the different 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.

Currently closed alerts are just a simple text card unlike open alert which does have links. This functionality should be available in closed alert as well.

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.

The metrics replset.replicationheadroom and replset.replicationlag would be useful to have exposed to identify network limtiations and/or too small oplogs

This is very hard to figure out what these alert mean, I have to go to the documentation and match them somehow, but it also looks like the documentation is not up to date.

Currently the Query Profiler can plot queries that were logged up to 24 hours in the past.

It would be helpful to allow for visualization of a custom date range older than 24 hours ago, rather than only queries logged within the past 24 hours. This could help with RCAs for events that occurred more than 1 day ago, and also help teams who collaborate to investigate queries over a time period longer than 1 day.

Right now, I do this manually. Would be good to see the totals prominently, along with a recommended upgrade/ not next to it, and single click to select the next size.

At present the finest granularity of ATLAS metrics is 1 minute ,as the metrics are averaged by 1 minute , this would not provide info on spikes lasting less than few seconds
reducing the granularity to 1 second would give more insight

Any way could analyze and store all the queries we have made
Fields would be: execution time, IO, cpu usage, etc...
This collection would store only 1 or 2 months of data.