Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
111 results found
-
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!
4 votes -
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.
3 votes -
More documentation about alert
It would be great if there were a doc explaning what each Alert Event Types means (and even that could give us some examples). And the same documentation should explain wich alerts have thresholdconfig or metricthreshold_config.
The documentation that I have found with a little explanation is thw below (and it shows some alerts type that don´t work)
Example: OPLOGBEHIND => When trying to use this one on terraform, it returns an error saying it does not exist (the one that works is: REPLICATIONOPLOGWINDOWRUNNING_OUT)https://www.mongodb.com/docs/ops-manager/current/reference/alert-types/#user
2 votes -
Include more actionable data in Alert emails
Currently the alert emails just link to the profiler page with nothing selected. This makes it guess work if there are multiple items in the profiler to examine. If you are unable to check the profiler within 24 hours of the email, no data could exist specifically for the alert email.
It would be much more actionable if the email alerts mentioned the collection that was being queried, the appName that triggered the query, and a direct link to the query in the profiler showing complete details of the query that triggered the alert.
This would make triage near instant…
2 votes -
Suppres/Stop Alerts caused by Mirrored Reads
Sometimes the "Mirrored Reads" queries cause alerts of "Query targeting " to appear in Profiler. Since these queries are related to mongod process, we want to stop this type of alerts
1 vote -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
1 vote -
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…
2 votes -
Alert when database user is created or removed
currently there is no alert option for database users
13 votes -
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 -
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.
2 votes -
Allow alerts to be created for when a MDB engineer manually intervenes on a cluster issue
This would be for cases when a cluster cannot self heal, and a member of the technical team needs to do a manual intervention. Their activity may show up in the logs after the fact, but there doesn't seem to be a way (currently) to have a proactive notification go out when the update is being made.
Having such an alert would give customers transparency/visibility into what MDB teams are working on, allowing them to focus their attention accordingly (ie. if customers encounter an issue but are alerted that the MDB team is already working on a fix, they'll know…
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 -
Atlas Alerting with greater granularity
more granularity for Atlas Alerting including database creation, collection creation, user creation, etc..
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 - 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 -
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 -
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 -
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.1 vote
- Don't see your idea?