Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
131 results found
-
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 -
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 -
Optimise alerts UI
You can’t save edits made to alerts 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 -
Optimise alerts UI on smaller screens
You can’t save edits made to alerts 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 -
Optimise alerts UI on smaller screens
You can’t save edits made to alerts 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 -
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 -
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 -
Fix typo in email verification popup
In email verification popup: your*
1 vote -
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.
32 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 -
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 scaling30 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.
7 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.
85 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 -
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
10 votes -
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 -
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!
20 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?