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
-
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 -
Display better Slack notifications
Currently, MongoDB Atlas Slack integration only send RAW text.
For easier reading, it would be nice (if not a must have) to leverage Slack notification format to have colors that represent at least the state of an alert.
Here is a suggestion from common things we can see in other tools:
* alert.open: Red
* alert.close: Green
* alert.update: Yellow
* alert.acknowledge: Grey
* alert.cancel: Brown
* alert.inform: BlueBonus: Leverage Slack App capabilities and have a
/
command to acknowledge an alert directly from Slack.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 IOPS
2 votes -
Billing Alerts Improvement
We find the conditions for billing alerts to be very limited. We were hoping we would be able to setup an alert that triggers when a certain threshold of our total subscription amount has been used for better monitoring. For example, >= 75% of the total subscription amount is used.
2 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 -
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 -
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 -
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 -
Atlas Alerting with greater granularity
more granularity for Atlas Alerting including database creation, collection creation, user creation, etc..
1 vote -
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 -
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?