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.

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.

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.

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.

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.

We would like to consume your status RSS feed to help us programmatically warn our internal groups when you have issues in a given region. One problem that we see with this is that the messages that we have seen posted are pretty inconsistent with how they specify regions. Examples: Oregon (us-west-2), AWS EU-WEST-2, AWS Sao Paulo. It would be very helpful to us, and probably your other customers as well, if the messages were more consistent in how they reference AWS regions.

I have different projects where I expect and calculate with different costs. I would like to set billing alerts per project, for example if an internal evaluation projects execeeds a specific biling the threshold is probably lower then for a production project.

Similar to the currenty billing alerts, I would to set a billing alert, but either per project or with different thresholds for each project.

since as documented there are limitation on network traffic in M0/M2/M5 instances, it is mandatory to have a metrics/alerts (also for free ones) to monitor this value in a 7d sliding window

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

With the Atlas API, there is functionality to add labels to various clusters like EC2. It would be great if that was exposed through the Atlas UI as well.

The profile page would be more use if the listing included the username so you could work out which application was making the queries.

It is really helpful to get use of indexes in numbers in last 24 hours to eastimate the use of particular index.

The "Host has index suggestions" alert notification does not contain any reference to the host/deployment that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.