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
-
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
-
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 when database user is created or removed
currently there is no alert option for database users
13 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 -
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 -
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?
8 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 -
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 -
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 -
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 -
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 -
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 -
Alert for Cluster Deployment
Have an alert for when a cluster has been deployed sucessfully. This way the person setting up the cluster in the UI and others in the projects know that the deployment is ready.
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 -
Auditing on high volume of data/records to capture malicious activity
We would like to requesting in the MongoDB Audit logs the following attributes: (available in profiler )
nreturnedsystem.profile.responseLength
Additionally if this could be a MongoDB Alert that would be extremely helpful as well if we could provide a threshold in size BYTES (system.profile.responseLength) and/or RECORDS returned (nreturned)
This will help with security management in particular active auditing for capturing high volume of data/records returned by an account and could identify malicious activity or being hacked.
2 votes -
Authentication Process Improvement
At the time for user login authentication VDI user authentication is not done properly. Not able to fetch the system details. Need improve in that section--- For example--->" You're receiving this message because of a successful sign-in from a device that we didn’t recognize. If you believe that this sign-in is suspicious, please reset your password immediately. "
1 vote -
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 -
How to configure an alert to trigger based on a specific query executing longer than, for example, 1 second.
If query is running more than X sec an alert to trigger based on a specific query executing longer than, for example, 1 second.
2 votes
- Don't see your idea?