Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
122 results found
-
Optimise alerts UI on smaller screens
You can’t save edits made to alerts in Atlaa when on a mobile device (see screenshot). The site doesn’t let users scale the screen, nor does flipping to landscape help - the save button is hidden.
1 vote -
Configure and show alert thresholds directly from Metrics view
Please show alert thresholds and allow configuration of alerts directly in the Metrics view for an Atlas cluster.
1 vote -
alerting when a node has a non standard state
Add a new type of alert : to be alerted when one cluster node goes to a state different of standard states ("primary" or "secondary").
For example, I have a cluster that one secondary node is on a transient state : "other".
Thank you.2 votes -
Add option to alert on "degraded" state of cluster
I would like to setup an alert for the cluster state 'degraded', which isn't available as an option at the moment. Could you consider adding this as an option?
3 votes -
Option to edit maintenance alerts via API
Maintenance alerts are created automatically when a maintenance window is set and these alerts by default send an email to the project owner.
If you want something different in those alerts (Slack notification, PagerDuty, etc.), having to go one by one when you have multiple clusters is not practical, lot of manual interaction for a managed service.
The goal of this request is to let configure/edit/create these alerts using the API, so it can be later included in Terraform.
7 votes -
Fix typo in email verification popup
In email verification popup: your*
1 vote -
allow control of pagerduty urgency (currently high) so that alerts can be managed better
Some alerts you need to know about immediately, others, the next working day will suffice. Allowing the user to set the urgency for each alert will allow a greater control over pager fatigue without having to bypass PagerDuty
2 votes -
Display better Slack notifications
Currently, MongoDB Atlas Slack integration only send RAW text.
For easier reading, it would be nice (if not a must have) to leverage Slack notification format to have colors that represent at least the state of an alert.
Here is a suggestion from common things we can see in other tools:
* alert.open: Red
* alert.close: Green
* alert.update: Yellow
* alert.acknowledge: Grey
* alert.cancel: Brown
* alert.inform: BlueBonus: Leverage Slack App capabilities and have a
/command to acknowledge an alert directly from Slack.3 votes -
Alerts on Configuration Changes
It would be nice to have an alert configurable when any change is made to the cluster configuration. It helps with compliance that there is knowledge of such changes without having to manually search and activity feed.
7 votes -
Using REGEX to exclude node from Alerts
Please exclude specific node(s) from Alerts using REGEX with a negative lookahead/ exclusion (instead of an inclusion matcher on hostnames in a replica set).
1 vote -
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
3 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.67 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),…
15 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 see your idea?