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
-
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 Atlas1 vote -
Send alert(email) when database is deleted
The alert conditions do not contain conditions like
- when database is deleted
- when cluster is deleted
- when project is deletedWe want to get notified if a malicious person or someone by mistake deleted major parts of the database.
This simple notification is not possible right now.2 votes -
AWS CMK rotation alert should be changed from 90 to 365 days
Originates from https://github.com/mongodb/terraform-provider-mongodbatlas/issues/805#issuecomment-1241569555
Short: The created default alert for encryption key rotation is configured to 90 days, also when using AWS KMS CMK. The automatic rotation for CMK is 365 on AWS side. So, I would vote for creating the default alert with 365 days, when AWS KMS CMK is selected.
Otherwise we get false alerts, as we rely on the automatic rotation of AWS KMS.
3 votes -
Add alerts for long Index building
Add an alert that is triggered if the time it takes for and index to build is higher than X minutes
1 vote -
1 vote
-
BLACKOUT Period to avoid outage
set up blackout period to avoid sending those alert while performing any index rebuilding in a rolling fashion or disk expansion activity ?
1 vote -
Additional metadata for alerts through the API
The lack of metadata is blocking us from having parity with opsmanager on our production alerting capability. Currently, when some alerts come through the API, there is no information to parse so you can't tell where the issue is happening. Even adding just the cluster would be helpful. As of now there is so little information that alerts using the data dog integration are worthless.
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 -
Support Authentication Triggers upon user update
We would be happy to see Authentication Trigger support for UPDATES in user management. For now it seems these triggers are limited to user creation and deletion (https://www.mongodb.com/docs/atlas/app-services/triggers/authentication-triggers/). We had an incident recently where a user was edited by mistake. Having these alerts on user update could have aided to alert us of a potential issue much sooner.
1 vote -
Ability to create a custom alert based on a query run at configurable interval.
There is currently no way to set up an Alert based on the results of a query directly in Atlas.
One can achieve this functionality using realm and triggers but that can be difficult.2 votes -
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.46 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 -
Create new Atlas Alerts integration - Integrate with Atlas App Services HTTPS Endpoints with Authentication
Today we can integrate Atlas Alerts with Atlas App Services HTTPS Endpoints (App Services function) using an Atlas webhook but the process is not easy and the use of webhook requires the alert data traverses the internet. Instead, create an built-in integration that does not traverse the internet but instead uses a private secure communication channel, that also uses Atlas App Services authentication including App Services user definitions.
1 vote -
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 -
Mongo DB alerts for latest version or release
Automatic alerts from Mongo DB Team for the latest releases / versions available similar to the EOL(End of Life) alerts.
This helps in planning the changes and upgrades reducing the manual effort on searching for latest versions.4 votes -
Read your login suggestions.
Possibly implement a suggestion... It's horrible. It's been horrible from day one. You don't need to re-imagine logging in, okay
1 vote -
Project alerts list does have all open and closed alerts
The project alerts in Atlas should show all the alerts that have closed for some period of time. For example, I get alerts about a cluster whose number of connection exceed 80% of the max allowed, but I do not see that alert as an active alerts nor as a closed alert. We should see the alert, even if that alert is for a specific cluster in the project, while the alerting condition is triggered and also when its is closed for some, configurable, period of time.
1 vote -
Having the alert "Acknowledge for" option actually do acknowledge the alert for the specified time period
I gathered that Atlas alerts are design to retrigger once the condition is met. Then what does acknowledge mean in that case when providing any timeframe like forever? To me acknowledging an alert forever means that the alert would never to raise again.
In our case the number of connections for one cluster out of many goes slightly over the threshold, then shortly thereafter, goes below the threshold . The condition is 'flapping'. I know that this connection count condition is not leading to the number of connections to be exceeded. But, I don't want to ignore that alerts for…
2 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
9 votes -
Custom Alert on unsuccessful deployment.
Add an Alert that will inform the user after a specific time that a deployment has not yet been successful, in order to transparently allow the customer to try a different configuration.
1 vote
- Don't see your idea?