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.

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.

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.

Integration Alerts with google chat like done with SLack

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

The speed at which usable monitoring metrics data (1m, 5m) is purged and reduced to 1hr is way too quick.

After 1hr, the ability to analyze these metrics that are crucial to investigating a performance issue were lost and hindered the root cause analysis.

I would suggest that 1m or at least 5m resolution metrics be retained for at least a week before being purged.

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

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.

The Profiler shows slow query statistics grouped by namespace, but it would also be helpful to view query records grouped by query pattern (perhaps similar to the "pattern" group option in mplotqueries: http://blog.rueckstiess.com/mtools/mplotqueries.html#group-by) and/or by specific fields used in the query.

This could be helpful, for example, for identifying particular query shapes that are executing slowly or suboptimally so that these can be investigated in more detail.

As an Ops person, access to the Realtime Dashboard Role is important, but it seems like in order to see it, you actually need access to the data itself. Is there a role that can give us that realtime monitoring without requiring access to the data explorer? I can access Profiler and Performance Advisor without those restrictions so it isn't clear as to why I can't also access the RealTime Performance Panel. Both of those show as much or possibly more information with regards to collections, documents, indices, etc than what appears on the RealTime Performance Panel.

When monitoring disk IOPS, it isn't immediately clear when we are limited on IOPS. Having a red limit line on the IOPS chart on the metrics tab would help here.

When a shared cluster has reached it's limit and the cluster is throttled, an email should be sent to each db-owner affected. This would save your customers AND your support a lot of time troubleshooting.

Right now there is no way for a db-owner to see this information, let alone get that information, except for asking support for help.

Make EBS Burst Balance Metrics available within the Atlas UI. Currently it is not easy to 100% understand how much burst credits are being used and whether they have actually been depleted.

You can infer it from the IOPS metrics going above baseline IOPS and then suddenly dropping down but would be better to see the balance itself to be 100% sure. This will save support requests to do so.

Please include the human-friendly cluster/host names in Monitoring Alert Notifications (e.g. email, PagerDuty, etc) in addition to, or instead of, the less clear internal cluster/hostnames (i.e. atlas-abcdef-shard-0).

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)

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.

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.

We find the conditions for billing alerts to be very limited. We were hoping we would be able to setup an alert that triggers when a certain threshold of our total subscription amount has been used for better monitoring. For example, >= 75% of the total subscription amount is used.

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