Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
117 results found
-
Enable Atlas Maintenance Notification without specifying a maintence window
There should be an option to enable Alert notification for Atlas maintenence without specifying an Alert Window. Just because a specific window is not required, MongoDB Atlas should allow an option to receive notification that one occurred. This would save time hunting down root cause for restart events and allow customers to be notified when a change occurs in their cluster.
8 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 -
Alerts for Atlas Limits
It would really help to get alerts on Atlas Limits (https://www.mongodb.com/docs/atlas/reference/atlas-limits/). Defining certain thresholds that would trigger an Alert as hitting these limits often involves work to re-structure something or creating a workaround. E.g. it is not possible to have more than 50 Endpoints per Project. But creating a new project is not a straightforward exercise. If the alert had occurred earlier there would have been more time to account for this.
7 votes -
Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running
Replicaset elected new primary alert needs to show user given cluster name and the region in which the primary node is running. For a multi-region cluster, cross-region failovers are a major application impacting event, so the Alert needs to include details around the region in which the primary is running. Also Alerts should use the same node names that are visible in the Atlas console and not use the internal node names in the Alert. This very critical for support teams ability to identify impacted clsuters and applications.
7 votes -
Custom templates of Alerts to deploy across many projects within an organization
When I make a new project, I don’t want to have to redeploy the same set of Alerts I've already configured for another project.
I want to be able to create custom templates/policies of Alerts at the organization-level that can be applied to projects within the organization. This template should be editable at the project-level after it is inherited to allow unique Alert configuration if a project requires.
These templates should keep track of all edits that I make to default Alerts and new ones that I configure, including threshold values and notification settings.
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 -
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 -
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 -
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
7 votes -
Allow Billing Alerts per Project
Currently, we can configure Atlas to send an alert when the current bill for any project is above a specific amount. It would be great to be able to set alerts for specific projects. This way we could more easily manage budget fors projects and alert project owners.
7 votes -
Disable Query Targeting alert notifications for $changeStream operations
Change streams require scanning of the oplog and cannot make use of indexes, meaning that $changeStream operations frequently trigger Query Targeting: Scanned Objects / Returned alerts that cannot be actioned. It would be ideal to allow $changeStream operations to be filtered from the Query Targeting alerts.
6 votes -
"Deviation from Norm" and "Frog Boil" type alerting
Currently Atlas only alerts us when CPU reaches a critical threshold such as 90%. We would like to see additional types of alerts to detect issues sooner, including the following.
- “Deviation from norm” - A given metric is X% worse than the Y-hour average at the same time window for the past Z days (e.g. “CPU today at 4am is much worse than the average of 3am ~ 4am for the past 7 days”.)
- “Frog boils” - A given metric is becoming progressively X% worse over Y hours / days / weeks (e.g. "CPU usage is 10% higher on average…
6 votes -
Webhook
Currently alert notification configuration allows webhook targets with a secret configuration. This limits us in terms of which webhooks could be configured. There are multiple webhooks which do not support secret configuration rather support Headers to be passed with authentication details.
This request is to support additional set of header to be passed/added in the webhook configuration for alert notification.
For example, during alert notification configuration I should be allow to configure additional set of headers like Authorization: "Basic cdge....==" and Source: "Atlas"; with Webhook URL configuration which is further used by target to first authorise POST call made by…
6 votes -
Cluster events - create, modify, delete
Add an alert category for cluster scale events such as creation, modification and deletion
6 votes -
Include "fields" and "options" in index build email notification
Hi, I'm wondering if it would be possible to not only include the database and collection names in the "Index build succeeded" email notification, but also the "fields" and "options" json objects.
It's great to know what indices are built by the team as the database admin, and since there isn't a "createdAt" timestamp in mongodb, the emails would serve as a workaround for that as well.
In short, it would be a valuable addition for our team if the "fields" and "options" data was included in the "Index build succeeded" email notification.
Thanks in advance!
5 votes -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
5 votes -
Notifications
In case of a databreach MongoDB will notify their customer.
Customer is defined as 'the Organization Owner'. However, a databreach should end up with a privay or security officer. It would be a nice feature if some of these roles would be defined and what kind of alerts/nortification they can expect from MongoDB Atlas5 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 -
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…
5 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.
5 votes
- Don't see your idea?