Atlas Monitoring, Alerts & Observability

Showing 297 of 4003

Add document count to Datadog metrics

We'd like to monitor the number of documents in a collection via DataDog. For On-Premise MongoDB the stats are already reported via mongodb.collection.count, mongodb.collection.size and mongodb.collection.avgobjsize. If the same metrics could be...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

8 VOTE

Ability to "Mass Kill" slow running queries

Currently, Atlas has a "Kill Op" option which is useful to kill single long-running queries. When upgrading to MongoDB 7.0, we were faced with a situation where the Slot-Based Query Engine (SBE) was causing 1000s of queries to execute slowly, we ...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

20 VOTE

add details to alert Query Targeting: Scanned / Returned to identify what triggered it

If you want to catch full scan on collection you could set up alert "Query Targeting: Scanned / Returned > 1". OPS Manager does not provide any details where it was triggered. it would be nice to get db/collection/query which caused this issue...

Guest over 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

15 VOTE

Add an alert or notification option for every "pause" or "resume" cluster action

Guest over 4 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

18 VOTE

Alerts Messaging Customization

At the moment, it appears one cannot customize the messaging or subject line of the alerts. This makes it difficult to categorize the alerts. For instance, we would like to categorize alerts into different severity levels, such that severity level...

Guest over 5 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

9 VOTE

Alerts for Atlas Limits

It would really help to get alerts on Atlas Limits (https://www.mongodb.com/docs/atlas/reference/atlas-limits/). Defining certain thresholds that would trigger an Alert as hitting these limits often involves work to re-structure something or creat...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

7 VOTE

Atlas metrics granularity after 48 hours

For metrics older than 48 hours, the data is presented in 1-hour intervals. This level of granularity is often too coarse for a thorough examination of past events and trends. Such a broad view can obscure smaller yet significant details critical ...

Guest about 2 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

7 VOTE

"Deviation from Norm" and "Frog Boil" type alerting

Currently Atlas only alerts us when CPU reaches a critical threshold such as 90%. We would like to see additional types of alerts to detect issues sooner, including the following. 1. “Deviation from norm” - A given metric is X% worse than the Y-h...

Guest over 2 years ago in Atlas Monitoring, Alerts & Observability 0 Submitted

18 VOTE

MMS Alert for Balancer Down status

please provide an option in Ops Manager to monitor the balancer status and add to alerts? So, we will know if balancer is not running. Note: Normally the balancer would be disabled during backups and during a scheduled Balancing Window downtime. ...

Guest almost 6 years ago in Atlas Monitoring, Alerts & Observability 3 Submitted

10 VOTE

Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running

Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running. For a multi-region cluster, cross-region failovers are a major application impacting event, so the Alert needs to inclu...

Guest over 3 years ago in Atlas Monitoring, Alerts & Observability 1 Submitted

Please enter your email address

FILTER BY CATEGORY