Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
122 results found
-
This is a feature request to integrate the forwarding of MongoDB Atlas logs to Azure Managed Grafana instance
This is a feature request to integrate the forwarding of MongoDB Atlas logs to Azure Grafana Managed Instance.
Azure Managed Grafana instance has Enterprise plugin for MongoDB but that is a Market place product which is not available to customers with CSP contract with Microsoft.
1 vote -
Alerts on password reset in Atlas UI
Alert should be sent on specific accounts in case of reset is initiated from Atlas UI.
1 vote -
In Atlas, add an alert condition for long-running queries
In Atlas, add an alert condition for long-running queries
2 votes -
Disable/Opt out of email notifications
We would like the option to disable email alerts within an individual user's settings.
We have users who need admin/owner level status for multiple projects but do not need to receive granular daily alerting like the rest of the project members. Differentiating alerts on user type alone will not solve our use case.2 votes -
Atlas Webhook Integration and Custom JSON Payload
Ability to specify a JSON body along with their Atlas Webhook's for additional functionality.
6 votes -
Alert notification for new cluster created in the project
Greetings, Support
After looking over the alert settings, I discovered that there aren't any alarms that can be monitored to be informed when a new cluster is created on the present project. Please include a notice about the future release, as it directly correlates with and impacts the price and invoicing.(Confirmed with support as there is not such alerts in Atlas with the current settings and case:01298603)
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 -
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 -
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 -
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.
15 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 -
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 -
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 -
"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 -
Incorporate Resource Tags in Atlas alerts
Enhance the alert content by incorporating the resource tags of the entity that triggered the alert.
12 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 -
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 -
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 -
Alarm on potential data breach events
Provide capability to raise alarms on specific events like mongodump, mongoexport (eventually mongorestore, mongoimport)
5 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
3 votes
- Don't see your idea?