Skip to content

Atlas

Share your idea. In order to help prioritize, please include the following information

  1. A brief description of what you are looking to do
  2. How you think this will help
  3. Why this matters to you

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

119 results found

  1. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 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.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Mongo DB alerts for latest version or release

    Automatic alerts from Mongo DB Team for the latest releases / versions available similar to the EOL(End of Life) alerts.
    This helps in planning the changes and upgrades reducing the manual effort on searching for latest versions.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Atlas alerts - include duration and date/time alert was closed

    currently alerts (sent to SLACK but probably other formats as well) reads this:

    Project: OS1

    Organization: SE Atlas

    CLOSED
    Host is down
    OS1-g-shard-18-05.bxxxxq.gcp.mongodb.net
    Created: 2020/06/11 03:44 BST

    Type: Mongos

    It would be helpful to also include:
    Closed: 2020/06/11 07:44 BST
    Duration: 1h 53m

    As the slack is usually set to each users timezone it creates a confusion when one is looking at how long issue lasted.
    This should be easy to implement and it would improve end user experience a lot.

    Same would be nice on Atlas 'closed alerts' tab - there seems to be no way currently to get…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Alerts change from time based pattern to include actual alert in subject

    So far we are receiving atlas alerts in time based manner which are difficult to undersatnd/analyze just by looking at email subject.

    We are expecting a model in which we want to Separate alerts for each instance instead of combining alerts on a single time frame and Changing email alert subject to include alert description. This will allows us to understand the alert by looking at email subject , combine/view all alerts in email client (for example outlook) , write some rules on them and analyze the alert timing pattern by sorting and group by alert description.

    For example,

    Present…

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. AWS CMK rotation alert should be changed from 90 to 365 days

    Originates from https://github.com/mongodb/terraform-provider-mongodbatlas/issues/805#issuecomment-1241569555

    Short: The created default alert for encryption key rotation is configured to 90 days, also when using AWS KMS CMK. The automatic rotation for CMK is 365 on AWS side. So, I would vote for creating the default alert with 365 days, when AWS KMS CMK is selected.

    Otherwise we get false alerts, as we rely on the automatic rotation of AWS KMS.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Add option to alert on "degraded" state of cluster

    I would like to setup an alert for the cluster state 'degraded', which isn't available as an option at the moment. Could you consider adding this as an option?

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. 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: Blue

    Bonus: Leverage Slack App capabilities and have a / command to acknowledge an alert directly from Slack.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. alerts on specific database

    I'd like to setup an alert on my cluster for specific database but currently I can only setup alerts for all databases on my cluster. for example, send alerts when "Document Metrics: Deleted above 1" on zyz database

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. Don't cut alert names

    This is very hard to figure out what these alert mean, I have to go to the documentation and match them somehow, but it also looks like the documentation is not up to date.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  15. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Include more actionable data in Alert emails

    Currently the alert emails just link to the profiler page with nothing selected. This makes it guess work if there are multiple items in the profiler to examine. If you are unable to check the profiler within 24 hours of the email, no data could exist specifically for the alert email.

    It would be much more actionable if the email alerts mentioned the collection that was being queried, the appName that triggered the query, and a direct link to the query in the profiler showing complete details of the query that triggered the alert.

    This would make triage near instant…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. mTLS for Atlas Alert Webhook Integration

    Atlas currently does not support mTLS on HTTPS traffic to Alert webhooks. Some customers whose alerting services are on-premises may require this per their security policy. We should support mTLS on webhook integrations to enable those customers to use their on-premises alerting systems.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base