Atlas
- A brief description of what you are looking to do
- How you think this will help
- Why this matters to you
123 results found
-
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 -
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 When Cluster Nodes Not Regionally Fault Tolerant
If a cluster is not regionally fault tolerant, generate alert to associated email address(es). Since regional fault tolerance is typically only a concern in production environments, provide the ability to only alert on clusters that contain specific tag values. Also, it would be helpful to see the lack of regional fault tolerance as an icon in the console screen for the end user.
1 vote -
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 -
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 -
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 -
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 -
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 -
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 -
Add alerts for long Index building
Add an alert that is triggered if the time it takes for and index to build is higher than X minutes
1 vote -
1 vote
-
BLACKOUT Period to avoid outage
set up blackout period to avoid sending those alert while performing any index rebuilding in a rolling fashion or disk expansion activity ?
1 vote -
Additional metadata for alerts through the API
The lack of metadata is blocking us from having parity with opsmanager on our production alerting capability. Currently, when some alerts come through the API, there is no information to parse so you can't tell where the issue is happening. Even adding just the cluster would be helpful. As of now there is so little information that alerts using the data dog integration are worthless.
1 vote -
Support Authentication Triggers upon user update
We would be happy to see Authentication Trigger support for UPDATES in user management. For now it seems these triggers are limited to user creation and deletion (https://www.mongodb.com/docs/atlas/app-services/triggers/authentication-triggers/). We had an incident recently where a user was edited by mistake. Having these alerts on user update could have aided to alert us of a potential issue much sooner.
1 vote -
Create new Atlas Alerts integration - Integrate with Atlas App Services HTTPS Endpoints with Authentication
Today we can integrate Atlas Alerts with Atlas App Services HTTPS Endpoints (App Services function) using an Atlas webhook but the process is not easy and the use of webhook requires the alert data traverses the internet. Instead, create an built-in integration that does not traverse the internet but instead uses a private secure communication channel, that also uses Atlas App Services authentication including App Services user definitions.
1 vote -
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
- Don't see your idea?