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
-
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 -
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 -
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 -
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 -
Have a configurable "active_for" alert parameter to only open alerts when conditions last a specified duration
Some conditions are only worth an alert if this conditions persists for some time (usually minutes).
One example: some poorly performing background queries produce spikes in the "Scanned objects/returned objects" metric. We only want an alert if the ratio remains consistently high for x minutes/hours, instead of triggering the alert whenever a workload has a short spike that crosses the threshold.
My perception of the current state is as follows: once the metric reaches 1000, atlas will open an alert right away (it will show up in the UI under open alerts), but will wait with sending notifications until the…
2 votes -
Alert when a User accesses Data
Trigger an alert if a specific user directly accesses data (e.g. browsed a collection/performed an operation) using Data Explorer in Atlas
2 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 -
webhook
Allow for more than 1 webhook in the Atlas Integrations-->webhook popup dialogue window.
2 votes -
mute alerts during set times
We would like to be able to set a time frame for when an alert can be triggered.
Our use case is that some devs schedule high impact queries to run at night. If the rule is triggered at night, then we don't care, but if it's triggered during the day, it's something we look at and fix.
2 votes -
alerting when a node has a non standard state
Add a new type of alert : to be alerted when one cluster node goes to a state different of standard states ("primary" or "secondary").
For example, I have a cluster that one secondary node is on a transient state : "other".
Thank you.2 votes -
allow control of pagerduty urgency (currently high) so that alerts can be managed better
Some alerts you need to know about immediately, others, the next working day will suffice. Allowing the user to set the urgency for each alert will allow a greater control over pager fatigue without having to bypass PagerDuty
2 votes -
Be able to see the replica set member states via MongoDB Atlas on a Datadog dashboard and get alerts if it changes
It doesn't look like these health metrics are available for the Atlas product. Would love to be able to use the metric mongodb.replset.health in MongoDB Atlas for both monitoring and alerting so that we can see the replica set member state on a dashboard as well as get alerted if it changes.
2 votes -
The Atlas Disk IOPs Read/Write alerts for data/index/journal partitions should be combined & not reference partitions.
The current Atlas Disk IOPs Read/Write alerts are for data/index/journal partitions.
However, Atlas does not use seperate partitions for data/index/journal so it can be misleading to rely on the alert message.The Atlas Disk IOPs Read/Write alerts for data/index/journal partitions should be combined & not reference partitions.
Alerts like:
Host - of any type - Disk write IOPS
Host - of any type - Disk read IOPS2 votes -
Project Alerts: show details about "Closed Alerts"
In "Project Alerts" we can only see certain details about "Closed Alerts," e. g. for an "Index Suggestion" we can only see the timestamp and the fact, that there was an index suggestion. You can't see what the specific suggestion was. So if you look through the history of alerts, you cannot tell if for multiple alerts it was always about the same index to be created, or whether it was for different indexes.
Likewise, for "Daily amount billed ($) is above threshold" you can see that the threshold was exceeded, but you can't see what the specific billed amount…
2 votes -
alert
While setting up alert allow additional text to be added. This would help to write SOP for action needed on such alert
2 votes -
Add Alert for outdated Agents
Add an alert type for outdated agents
2 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)
1 vote
- Don't see your idea?