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
-
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 -
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.2 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 -
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 IOPS
2 votes -
Fix typo in email verification popup
In email verification popup: your*
1 vote -
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 scaling28 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 -
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 -
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 -
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.17 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.
56 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 -
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.
13 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
- Don't see your idea?