Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
116 results found
-
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 -
Incorporate Resource Tags in Atlas alerts
Enhance the alert content by incorporating the resource tags of the entity that triggered the alert.
9 votes -
Need Prior notification For The Scheduled maintenance
We have noticed that our servers undergo scheduled maintenance, resulting in unexpected reboots. However, we lack information about the nature and purpose of these maintenance activities. We require a prior notification regarding scheduled minor/major maintenance to ensure that we can take proactive measures from our end. This would enable us to prepare appropriately and minimize any potential disruptions or issues caused by the maintenance.
2 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 -
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 -
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 -
Atlas raise alerts if resource consumption hits threshold notifications only when it's already scales up to the max tier
Atlas can be configured to raise alerts if resource consumption hits threshold only when the Atlas cluster already scales up to the max tier allowed. This can be help to avoid notification spams which does not require operation team actions and focus on the critical resource consumption alerts like cpu, memory, disk IO.
2 votes -
automatic upgrade
Forced automatic major version database upgrade.
When there is an extension the automatic database upgrade, remove the banner that says it is going to upgrade at the previous date. This is confusing and unnerving as it looks like it is going to upgrade.
1 vote -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
5 votes -
Three icons on the top right go unnoticed
The three icons on the top right are going unnoticed, and it causes troubles to users to find stuff in the UI.
I wanted to find "alerts" in the account, and it took me ~fifteen minutes to find it in the UI.
The three icons the top right are as following:
1. Invite to project
2. View the project activity feed
3. View the project alertsI've highlighted these three icons in the screenshot. Need to improve the UX.
1 vote -
We I propose integrating built-in alerts for KMIP key expiration into MongoDB Ops Manager, enhancing our security management and preventing
One crucial feature currently lacking in ops manager is the ability to alert users on impending KMIP key expirations in a similar vein to SSL certificate expiration alerts.
I propose integrating built-in alerts for KMIP key expiration into MongoDB Ops Manager, enhancing our security management and preventing inadvertent lapses in key validity.
2 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 -
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 -
Specifying who receives notifications for auto-scaling events
Having ability to manage wich roles receive auto-scaling notifications when a cluster scales up or down.
Now this is limited to Project Owner but this feature will be helpfull to manage notifications to inform other Team Members wich doesn't have to get all permissions related to Project Owner.
1 vote -
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
2 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 -
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 -
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
- Don't see your idea?