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
-
API for configuring Organization Alerts
There is an API for configuring and managing Project Level alerts but we still have to manage any Organization level alerts manually.
It would be good to release an API for the Organization level alerts as well so we can automate those.
1 vote -
Option to Export all alerts via Atlas UI for compliance purpose
Today we can export the alerts via Atlas UI but it would be helpful if they can be exported via UI also. Its a common request from team.
1 vote -
Feature request
Feature request one:
When I go to a project > click 3 dots at top left > select integrations tab, I can only create one webhook… we have multiple systems that we’d like to notify via webhook.Feature request two:
When I create a new alert I’d like to have the flexibility to shape the alert payload sent via webhook. For example, an alert is sent for a CPU usage, I would like the ability to change the severity property in the json payload to show as “Info” and the priority property set to “Low”. But, when a “Host is…1 vote -
mTLS for Atlas Alert Webhook Integration
Atlas currently does not support mTLS on HTTPS traffic to Alert webhooks. Some customers whose alerting services are on-premises may require this per their security policy. We should support mTLS on webhook integrations to enable those customers to use their on-premises alerting systems.
2 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 -
Alert - Network & Security
Ability to setup alerts on the project to notify if any user added network ranges / IP's to access the database cluster.
You can see the activity in the feed but there is no options available to set alert for such?
9 votes -
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
-
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.62 votes -
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 -
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
- Don't see your idea?