Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
117 results found
-
Add alerts on disk IOPS and CPU IOWAIT %
To help catch heavy disk workloads before they become problematic, it would be great to have alerts on:
- disk IOPS percentage utilization for disks without burstable IOPS
- burst credit utilization for disks with burstable IOPS
- CPU IOWAIT %70 votes -
Atlas auto-scaling configurable alerts
It would be useful, and contribute to a complete alert experience, to have auto-scaling event alerts configurable in project alerts. Users should be able to send alerts to their target system of choice, and prevent numerous alerts to specific users.
Currently auto-scaling alerts are only emails to project members (as per the following https://docs.atlas.mongodb.com/cluster-autoscaling/#acknowledge-auto-scaling-events).
Examples of configurable alerts:
- Scale-up unsuccessful due to max cluster-tier too low -> change email recipient of these alerts
- Scale-up event has occurred -> send alert via SMS and Slack.62 votes -
Suggested actions for alerts
Alerts are often very cryptic & don't provide any useful information. For example, when alerting that queries are returning too many rows, without informing me the query or at least the collection, that's very useless. I'm looking at a replication oplog window alert right now and I have no idea what to do about it.
57 votes -
Add the ability to trigger alerts for testing purposes
It would be useful to have a "Test Alert" button for each configured alert in order to integrate and test alerts with third-party systems. Otherwise, it is difficult if not impossible to determine what the alert will look like until it is triggered.
30 votes -
make auto scaling alert message granular
When a cluster is changed due to auto scaling a message is sent to all project members. Project member cannot unsubscribe to this.
Request :
Provide the option, like all other alerts, to change the the alert settings for auto scaling29 votes -
Allow Alerts to be disabled during Atlas performed Maintenances
When Atlas is performing maintenances such as setting changes and OS reboots Alerts will be triggered. It would be helpful to have these Alerts be disabled so that it doesn't cause false alarms or so much noise that they are ignored.
21 votes -
Include Human-Friendly Cluster Names in Alert Notifications
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).
20 votes -
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 will help determine the level of attention that is paid to the alerts when they trigger. If it is possible to prefix or append some customization code and message to either the subject line and/or actual message, then a monitoring team can use the custom code/message to determine the severity or category of the alert when it triggers.
Some alerts…18 votes -
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. Query still can be fast (for example, not many document in collection yet or hardware is idle/fast at the moment) and will not go to slow operation group.18 votes -
Email subject more specific for Alerts
The email Alerts that MongoDB provide are very useful, especially the Oplog and CPU Usage. However, the subject of the emails are not clear and does not specify the Alert type. It is just a generic "Alert". It would be great if MongoDB can add "Alert Oplog" or "Alert CPU Usage" to the email subjects to make them much more clear and helpful. Thanks!
15 votes -
Support node type or node tags as condition in MongoDB Atlas Alert
Currently, the MongoDB Atlas does not support the node types [1] or node tags [2] as the condition in Atlas alerts. That would be super inconvenient for the following scenarios.
Scenario 1: If the user wants to create an alert to monitor the specific node type, such as READ_ONLY node or ANALYTICS nodes, there is no convenient way to achieve it. The current approach must set up the alert by using the hardcode hostname.
Scenario 2: If the user has some electable nodes and a analytics node in a cluster, and wants to focus on monitoring the electable nodes (workload),…
14 votes -
Improvement: Add severity to alert definitions in Atlas MongoDB
The alert payload only contains status field with 'open' or 'closed' value. No severity definition option is available.
14 votes -
Alert when database user is created or removed
currently there is no alert option for database users
13 votes -
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.
I believe that the Balancer has a duty cycle of either 10 secs when nothing recently to balance, or 1 sec when there's a bunch of balancing to do.
Any alert would need to account for these:
the changelog shows chunk moves commanded
the actionlog shows balancer state change history
the settings collection has the balancer state13 votes -
Improve the "host is down" alert by eliminating false positive alerts
Currently, whenever an index build is kicked off on a replica set, it tends to trigger a "host is down" alert. Although this is benign and a false positive alert the on-call DBA has to wake up in the middle of a night when this alert pages us to make sure the host is NOT DOWN. When the monitoring agent tries to ping a node (where index build is running) and fails to communicate with it, it tends to think that the host is down and triggers this alert, although the host is up and running. When an index build…
10 votes -
Incorporate Resource Tags in Atlas alerts
Enhance the alert content by incorporating the resource tags of the entity that triggered the alert.
9 votes -
Alert - Network & Security
Ability to setup alerts on the project to notify if any user added network ranges / IP's to access the database cluster.
You can see the activity in the feed but there is no options available to set alert for such?
9 votes -
Add an alert or notification option for every "pause" or "resume" cluster action
Add an alert or notification option for every "pause" or "resume" cluster action
9 votes -
Add alert setting for cluster being auto-scaled up or down
Hi,
I'd like to set up a slack hook to our #emergency room when the cluster is being automatically scaled up/down.
In the project settings in the Alerts / Alert Settings section there are ways how to email/slack notify on some events: maintenance events, index suggestions or even Disk I/O % utilization and may more...
Though somehow I'm unable to modify the behaviour when the cluster is auto-scaled up due to high CPU/RAM usage for 1 hour.
Would love to see this alert type in the settings among the rest of other alerts.
9 votes -
Atlas Alert for Remaining Credits
MongoDB will email Atlas customer when the prepaid Atlas credit is estimated to be exhausted within 30 days.
However, it would be good to have an alert for this in Atlas, e.g.
Alert if the remaining prepaid amount is lower than ... <an amount>
9 votes
- Don't see your idea?