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.

We have a lot of cursor not found errors and currently there isn't an easy way to locate them at the Atlas integrated monitoring.
It would be nice to have this feature.

It would be awesome to have possibility to tag alerts in atlas when creating using API or console. It will allow to process groups by alerts by tags without keeping track of ids.
requires:
adding tag field to API create call
adding query by tag to API delete or update calls.

Pavel

Integration Alerts with google chat like done with SLack

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

Unless I've missed a button somewhere, it would be nice if the "Metrics" tab for clusters and "Status" tab for shards had an option for expanding the entire tiled graph view into a full screen view. We have some TVs around our dev pod where we display these graphs and it would be great to see several graphs at once in full screen view.

When receiving tens of emails regarding a dangerous condition on a node it would be helpful to know which node instead of having to click in the email to get to the portal to know if the issue affects our primary node or a secondary node.

Thanks

I can't see metrics for all of my nodes while in the metrics tabs unless I make the window very large. It would be much easier to analyze the health of my cluster if I could review metrics for all the nodes by scrolling horizontally, rather than having to switch between a grouping of nodes.

Currently there doesn't seem to be a way to set up custom alerts and monitoring on specific metrics such as when the size of documents returned form a query exceeds a certain limit, even though that information is available through the Profiler when looking at query samples.

It would be very useful to be able to either configure these metrics to be sent to an external service like Loggly for better monitoring and alerts or allowing to create customized alerts/webhooks within Atlas that would be triggered based on a custom-specified condition.

Allow to replace / restart the underlying virtual machine of a node.

Sometimes this is all that is needed to get a cluster out of an unhealthy state. Currently, only support seem to be able to do this.

Hi,

Can you please create an alert for WiredTiger metrics, such as used cache?

We had several cluster instances going over the 5% of used cached (dirty data) and would like to be notified when it happens.

Regards,
Sergei

This is needed in order to determine whether

Would love to see an official connector to ServiceNow for automatic ticket creation triggered by various database alerts.

Add alerts for when Triggers are suspended or exceed a threshold.

Filing this on behalf of customers that are having a hard time telling orange and brown apart in Atlas metric timeline annotations (node become secondary, node becomes primary)

This is a request to add some additional metrics to those that are currently sent from Atlas to New Relic when the integration is enabled.

The specific metrics of interest here are:
- Disk Space (%) Used (or Free)
- DB Storage
- Query Targeting

Having pointed out the above metrics specifically, I would also say: the closer that the metrics sent to New Relic via the Atlas integration can resemble those available in the Atlas cluster Metrics page, the better.

When there's an election and the primary changes, it's hard to get a good view on how does the primary functions in a macro fashion.
Please add a monitoring column (or an equivalent solution) that can show the monitoring information for the primary at the time, so I could look at the past month or so, and see how does the primary performed, even if it was a different server every time.

This will make it much easier to understand various actions we take like changing indexes, improving queries, upgrading the database version, upgrading the driver, etc.

We want option to export Atlas activity feed in a file to export and work with it. Parse it etc ...

Even better, make a collection with it.