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
-
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 -
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 -
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 -
Add an alert or notification option for every "pause" or "resume" cluster action
Add an alert or notification option for every "pause" or "resume" cluster action
9 votes -
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 -
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 -
provide more details on the replica set elected a new primary
today the details on this event are very low and have only the replica set name which is not enough, can you also add the correlated cluster name to the exposed details?
more over if this is something that can be monitored by the metrics going to Datadog?3 votes -
Allow user provided alert templating for Atlas alerts
I want to have the ability to provide their own templatized text for alerts. Often I may want to provide specific instructions to operations personnel for each alert type, or to provide links to relevant internal runbooks.
Other systems such as Datadog and PagerDuty provide this kind of capability.
5 votes -
Multiple Email address for alerting
In alertconfiguration, change the emailaddress argument in "notification" block from "string" to "list(string)".
Main goal here is to allow multiple alert emails like it's possible in the portal.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 -
"Replica set elected a new primary" and other information alerts are not recorded in Atlas
Alerts like the "Replica set elected a new primary" are considered informational, they trigger an email being sent but the alerts were not recorded in the open and closed alert page in Atlas UI. Also they cannot be retrieved via API.
This is pretty confusing as you'd imagine once the alert is triggered, it'll be recorded in the page where all the other past alerts are kept, the concept of informational alert is vague and never properly communicated to users.
Please record all types of past alerts in the UI and make them accessible via API.7 votes -
Use existing main Integrations Slack key for all alerts automatically
When updating the main Integrations Slack key, the token changes is not automatically deployed to the mongo alerts created earlier (slack notification). This feature would be helpful as at this time we have to update manually all alerts configured with a new token.
4 votes -
Alert configurations should be unique
Atlas allows for the creation of duplicate alerts. Alert configurations should be unique such that exact duplicate configurations are prevented from being saved.
2 votes -
Pending updates alerts
I'd like to be able to have alerts for all those databases that are using a version that is not the latest major version available.
This will help to be more proactive so that updates can be planned in advance without the need to manually review the available versions from time to time. It will also help in the implementation of security controls such as SOC2.
3 votes -
Better alert trigger for index suggestions
The current alert trigger for index suggestion is described here: https://docs.atlas.mongodb.com/reference/alert-conditions/#host-alerts
"If the query targeting ratio for a host consistently exceeds 10,000 for a period of 10 minutes, Performance Advisor checks the host for inefficient queries and possible indexes to improve performance."
Firstly we have issues with alerts constantly going on and off every few minutes if the query ratio is fluctuating around the 10k mark.
Secondly, we often do not get alerts for worthwhile index suggestions. We run a multi-tenant platform. We have big clusters with hundreds of databases/tenants and thousands of collections. A huge amount of our queries…
5 votes -
webhook
Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.
2 votes -
Show overlapping Alert configurations between different scopes
I wish there was a way to show an overlapping alert configuration. When alerts are defined on a global level but overridden on a project level, it is very hard to tell if something was overridden.
2 votes -
A default ‘Send to’ method for Alert configuration
I want to be able to define a default ‘Send to’ method that will be automatically configured during Alert creation.
The default is email, but when we use a 3rd party integration like PagerDuty, it is quite tedious to create alerts manually. The only quick and perhaps correct way is through automation such as MongoCLI or Terraform.
2 votes -
Single page to view all configured Alerts
I want to be able to look through all of my Alerts for all of my projects on a single page to easily understand their state. I'd also like features to help me make sense of the aggregated list. (some type of sorting or filtering)
I struggle to understand the state of all of my Alerts, across all projects, because there isn't a centralized place to view all of them. It's also hard to maintain a large set of alerts for a given project because there's no way to sort/order them.
2 votes
- Don't see your idea?