Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
112 results found
-
Be able to see the replica set member states via MongoDB Atlas on a Datadog dashboard and get alerts if it changes
It doesn't look like these health metrics are available for the Atlas product. Would love to be able to use the metric mongodb.replset.health in MongoDB Atlas for both monitoring and alerting so that we can see the replica set member state on a dashboard as well as get alerted if it changes.
2 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 -
The Atlas Disk IOPs Read/Write alerts for data/index/journal partitions should be combined & not reference partitions.
The current Atlas Disk IOPs Read/Write alerts are for data/index/journal partitions.
However, Atlas does not use seperate partitions for data/index/journal so it can be misleading to rely on the alert message.The Atlas Disk IOPs Read/Write alerts for data/index/journal partitions should be combined & not reference partitions.
Alerts like:
Host - of any type - Disk write IOPS
Host - of any type - Disk read IOPS2 votes -
alerts on specific database
I'd like to setup an alert on my cluster for specific database but currently I can only setup alerts for all databases on my cluster. for example, send alerts when "Document Metrics: Deleted above 1" on zyz database
4 votes -
Cluster events - create, modify, delete
Add an alert category for cluster scale events such as creation, modification and deletion
6 votes -
Have the capability to manage contact details for Atlas-level 'Teams'
There should be a capability to manage/assign contact details (such as email) at the Atlas level, to the created organizational 'Teams' (such as assigning a team distro email address), so that alerting can be streamlined, instead of sending out separate emails to each and every member of the team.
1 vote -
Profiler output is confusing
Not so much a feature perhaps as a bug, but it seems that in the profiler page, the chart changes with the time window of interest, e.g. from 24hr to 6 hr or 1hr, but the listing of the namespaces underneath does not. So suppose you think you've fixed an issue and want to check 4 hours later. The chart seems to indicate things are ok, but the namespace table is actually confusing in this case. When you click on an item in a listed namespace (i.e. collection), it goes into the detail view and that one does conform to…
1 vote -
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.46 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),…
13 votes -
Active link on closed alerts
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.
1 vote -
Don't cut alert names
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.
3 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…15 votes -
Billing Alerts Improvement
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.
4 votes -
Project Alerts: show details about "Closed Alerts"
In "Project Alerts" we can only see certain details about "Closed Alerts," e. g. for an "Index Suggestion" we can only see the timestamp and the fact, that there was an index suggestion. You can't see what the specific suggestion was. So if you look through the history of alerts, you cannot tell if for multiple alerts it was always about the same index to be created, or whether it was for different indexes.
Likewise, for "Daily amount billed ($) is above threshold" you can see that the threshold was exceeded, but you can't see what the specific billed amount…
2 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 -
Alert setup for failed logins
There is no good monitoring or alert functionality for dealing with potential invalid login attempts.
I suggest an alert setup to handle events when known users fail more than 3 times to login (either in Atlas or via driverlogin to db).
We have had an external audit done and this is something they have found as a shortage in the MongoDB Atlas environment.
Log files are good but not to monitor potential security issues
6 votes -
alert
While setting up alert allow additional text to be added. This would help to write SOP for action needed on such alert
2 votes -
Add Alert for outdated Agents
Add an alert type for outdated agents
2 votes -
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 %65 votes
- Don't see your idea?