Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
124 results found
-
Alert when a User accesses Data
Trigger an alert if a specific user directly accesses data (e.g. browsed a collection/performed an operation) using Data Explorer in Atlas
3 votes -
Need Monitoring Feature for MongoDB Charts data transfer usage / alerts
We need to use MongoDB charts but we want to ensure that we don't go beyond the 1GB Free data transfer threshold limit. As per support there is no such monitoring feature . Requesting to add a new feature that will:
1) Help us to automatically monitor the data transfer usage for MongoDB chart
2) Alert the team via email in case it reaches 1GB free threshold limitThanks
1 vote -
Alert configurations should be unique
Atlas allows for the creation of duplicate alerts. Alert configurations should be unique such that exact duplicate configurations are prevented from being saved.
2 votes -
Generate and send MongoDB Alert emails without graphics
Images are always added when generating mails, and unfortunately, our central monitoring system can't cope with that. It would be great if you can generate and send MongoDB Alert emails without graphics.
1 vote -
Get only one invariant IP address as addressee when using webhooks for alerts
When using webhooks, alerts can unfortunately be sent from a large number of IP addresses. This is problematic for our network team and security requirements. It would be great if there was a way to get only one invariant IP address as addressee, possibly by putting a proxy in between.
1 vote -
Multiple Email address for alerting
In alertconfiguration, change the emailaddress argument in "notification" block from "string" to "list(string)".
Main goal here is to allow multiple alert emails like it's possible in the portal.4 votes -
New Default Alert for Connection Timeout
It would be helpful if there is a default alert in the Atlas UI for a connection timeout, rather than this only being in the log file.
1 vote -
webhook
Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.
2 votes -
Allow user provided alert templating for Atlas alerts
I want to have the ability to provide their own templatized text for alerts. Often I may want to provide specific instructions to operations personnel for each alert type, or to provide links to relevant internal runbooks.
Other systems such as Datadog and PagerDuty provide this kind of capability.
5 votes -
pagerduty - User certificate expiration NDS_X509_USER lack of details
The alert type NDSX509USERAUTHENTICATIONMANAGEDUSERCERTSEXPIRATIONCHECK sent to pager duty using integration key miss some important information, such as, the name of the certificate that is about to expire. We have to open MongoDb atlas to see the details.
I want to have all the details, the same when we send the notification by Email.1 vote -
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 -
Pending updates alerts
I'd like to be able to have alerts for all those databases that are using a version that is not the latest major version available.
This will help to be more proactive so that updates can be planned in advance without the need to manually review the available versions from time to time. It will also help in the implementation of security controls such as SOC2.
3 votes -
mute alerts during set times
We would like to be able to set a time frame for when an alert can be triggered.
Our use case is that some devs schedule high impact queries to run at night. If the rule is triggered at night, then we don't care, but if it's triggered during the day, it's something we look at and fix.
2 votes -
selected option scroll disappear on click to scroll
In Atlas within Insert Document: When using the data type selection, clicking on the scroll bar or arrow causes the select option to disappear. Possibly increasing the size of the select option depth to where scroll is not needed may help.
1 vote -
Use existing main Integrations Slack key for all alerts automatically
When updating the main Integrations Slack key, the token changes is not automatically deployed to the mongo alerts created earlier (slack notification). This feature would be helpful as at this time we have to update manually all alerts configured with a new token.
6 votes -
Encryption at rest with our own keys - Manage alert and shutdown parameters
It would be interesting to improve the encryption at rest feature in order to be able to define the alert parameters in case of unavailability of the key as well as the delay before a Replica Set fails.
for example. I want to be alerted if my key is not available x times in the last 10 minutes and stop the replica game after 60 minutes if the situation is not resolved. This makes it possible for the support team to take corrective action without causing downtime.
8 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
13 votes -
Better alert trigger for index suggestions
The current alert trigger for index suggestion is described here: https://docs.atlas.mongodb.com/reference/alert-conditions/#host-alerts
"If the query targeting ratio for a host consistently exceeds 10,000 for a period of 10 minutes, Performance Advisor checks the host for inefficient queries and possible indexes to improve performance."
Firstly we have issues with alerts constantly going on and off every few minutes if the query ratio is fluctuating around the 10k mark.
Secondly, we often do not get alerts for worthwhile index suggestions. We run a multi-tenant platform. We have big clusters with hundreds of databases/tenants and thousands of collections. A huge amount of our queries…
7 votes -
"Replica set elected a new primary" and other information alerts are not recorded in Atlas
Alerts like the "Replica set elected a new primary" are considered informational, they trigger an email being sent but the alerts were not recorded in the open and closed alert page in Atlas UI. Also they cannot be retrieved via API.
This is pretty confusing as you'd imagine once the alert is triggered, it'll be recorded in the page where all the other past alerts are kept, the concept of informational alert is vague and never properly communicated to users.
Please record all types of past alerts in the UI and make them accessible via API.7 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
- Don't see your idea?