1358 results found

1. Configuring provider with shared credentials file for secrets manager

   Currently the provider allows configuration for secrets manager for the API key, however it looks like only static AWS credentials can be used which require assuming a role first and exporting environment variables. It would be much cleaner if you could support shared profiles, much like the AWS provider does https://registry.terraform.io/providers/hashicorp/aws/latest/docs#profile-1.
   https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html
   Specifically https://github.com/mongodb/terraform-provider-mongodbatlas/blob/master/internal/provider/credentials.go#L49 is static credentials, but would be great to add profile as an option as well.

   8 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Include “Tag” Field in the Cost Explorer API Response

   We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
   https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage

   Background

   Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
   • Organization ID
   • Project ID
   • Cluster Name

   To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing us to categorize costs accurately.

   Challenge

   While the current CSV file approach works, it requires downloading, parsing, and managing files, which introduces unnecessary complexity and file management overhead. Including the tag field directly in the API response would allow us to streamline this process and avoid handling files entirely.

   Request

   We kindly request the addition of a “tag” field in the response of the API endpoint mentioned above. This enhancement will enable us to:
   1. Automate our cost categorization and reporting process.
   2. Eliminate the need for manual file parsing and management.
   3. We can calculate costs by department or application and use resources more efficiently.

   We would like to request an enhancement to the API functionality to better support our reporting needs. Specifically, we are asking for a “tag” field to be included in the response from the following endpoint:
   https://cloud.mongodb.com/api/atlas/v2/orgs/%s/billing/costExplorer/usage

   Background

   Our team generates detailed monthly reports on departmental usage costs using the API. Each month, we provide information such as:
   • Organization ID
   • Project ID
   • Cluster Name

   To categorize costs, we use tags to assign each cluster to specific internal department categories. These tags are already included in the CSV file available at billing > invoices > download > csv, allowing… more

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Create One Rolling Index in Terraform

   This is a request to add our One Rolling Index request to our Terraform.

   References:
   * https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Rolling-Index/operation/createRollingIndex

   • https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs

   Benefits:

   Many teams interact with Atlas via automation using Terraform. This has been highlighted as one of the important ones to have in Terraform.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Update the regex used to split a database user import id to match the database name constraint

   Hello,

   While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.

   The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.

   I've got the following error when i launch my terraform import:
   Error: error splitting database User info from ID
   │ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}

   Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
   => https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349

   Is it possible to update the regex to allow others characters like my underscore in this case, and maybe match only the constraints that are set on database's name creation ?

   Thanks

   Best regards

   Hello,

   While doing terraform import of the mongo db users, i'm facing an issue with the mongo terraform provider.

   The database name contains an underscore so my imported user ID is 5ceClusterId-username-my_database.

   I've got the following error when i launch my terraform import:
   Error: error splitting database User info from ID
   │ import format error: to import a Database User, use the format {projectid}-{username}-{authdatabase_name}

   Indeed the mongo tf provider uses a regex to split this ID and doesn't allow characters for db name others than $a-z.
   => https://github.com/mongodb/terraform-provider-mongodbatlas/blob/ebb67f86165e0a364e486e769678377db507f005/internal/service/databaseuser/resource_database_user.go#L349

   Is it possible to update the regex to allow others… more

   6 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. DataBases Prices

   Several clients from Brazil frequently complain that MongoDB is expensive. One of the reasons is the need to create separate clusters (even M10-sized clusters) for development and/or staging for each production cluster.

   One alternative they are using to reduce MongoDB costs is to share DEV and/or staging clusters among multiple teams. However, this introduces another challenge: how to split these costs internally between different departments.

   To address this demand, which has been raised by several clients—including Ambev, Anhanguera, DASA, and Digibee—my suggestion is for Atlas to provide a way for customers to see the cost per database within a cluster. In other words, if a cluster hosts five databases and costs USD 25K in total, it should be possible to identify the share of that USD 25K attributable to each database.

   Several clients from Brazil frequently complain that MongoDB is expensive. One of the reasons is the need to create separate clusters (even M10-sized clusters) for development and/or staging for each production cluster.

   One alternative they are using to reduce MongoDB costs is to share DEV and/or staging clusters among multiple teams. However, this introduces another challenge: how to split these costs internally between different departments.

   To address this demand, which has been raised by several clients—including Ambev, Anhanguera, DASA, and Digibee—my suggestion is for Atlas to provide a way for customers to see the cost per database within a cluster.… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Billing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Atlas GovCloud Archival

   Please add the online archive feature for GovCloud

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Online Archive  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Add single link between workload identity provider and organization via Terraform

   We currently have multiple Terraform workspaces for different environments that each set up their own MongoDB Atlas workload identity provider (AKS cluster). In order to link these providers to the organization you have to manage a "mongodbatlasfederatedsettingsorgconfig" resource and pass a list of ALL identitiy provider ids. The Terraform workspace only knows (or rather: should only know) about its own identity provider, so it would be nice to have a single Terraform resource that manages a single workload identity provider <-> organization link.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Terraform Provider  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. API - Version 2

   We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

   We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
   Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

   to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
   "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

   What I need to change is only the "instanceSize":"M10", but I need to use IN A PATCH all this other parameters. It doesn't make any sense to need to inform all of this if I'm using a PATCH (it is not a PUT, it should work fine receiving only what I'm about to change)

   It would be great if this could be fixed so it would work just receiving what we want to change, or at least just receiving the parameters that v1 needed.

   We saw that the api version is now in v2 for some resources (as clusters) - https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Clusters/

   We tried to change some App services functions from v1 to v2, but ended resulting in some errors (or needing to add more parameters than the original one - in version 1).
   Using version 1, we only inform what we need to change ("instanceSize") plus the providerName.

   to use version 2, we need to inform all this parameters (if it's a replica-set. If it is a sharding we also need to inform the numShards):
   "replicationSpecs":[{"regionConfigs":[{"electableSpecs":{"instanceSize":"M10","nodeCount":"3"},"priority":"7","providerName":"GCP","regionName":"CENTRAL_US"}]}]}

   What I need to change is only the… more

   38 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Administration API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Expose PSC connection details in Atlas

   Allowing the users to view the details of PSC connections like GCP project id, VPC, Subnets once after the PSC is in available state which will help us in troubleshooting if there are any issue from the cloud providers side.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Allow user to be able to download queries in Query Insights. Also a search bar in Query Insights to find certain queries

    Allow user to be able to download queries in Query Insights would be nice. Also a search bar in Query Insights to find certain queries. Clicking through each operation to look at each query takes too much time. I want to be able to search any queries with any specific criteria so I don't have to click on each one to check for collection or index scan or duration time etc.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Performance Advisor  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. Export Aggregation Results as Metrics to Prometheus

    Add support for exporting MongoDB aggregation results as Prometheus metrics. This would allow users to track custom queries and dynamic data, enabling more granular and meaningful monitoring and alerting in Prometheus and Grafana.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Monitoring and Metrics  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Improvement to Atlas API - return the cluster name in the json

    Hi,
    We use Atlas administration API extensively in some admin apps we created over Atlas. For example, we use the get all processes in project to get all the node names in a project and then iterate over them to perform various operations. For some of the operations, we need also the cluster name.
    Until recently, we could count on the userAlias part of the returned json to get the cluster name. It is an anti-pattern to rely on string manipulations but it was working. Now, when some clusters are migrated from serverless and/or flex and stay with the shared node names, this is broken.
    I think it would be great it you would just add to the returned json (at least for this API, but for others as well) - the cluster name the node / disk belong to. As this is an additional field in the json and not a change in one, this should not be a breaking change so it should be easy to add with little risk.

    Thanks,
    Oren

    Hi,
    We use Atlas administration API extensively in some admin apps we created over Atlas. For example, we use the get all processes in project to get all the node names in a project and then iterate over them to perform various operations. For some of the operations, we need also the cluster name.
    Until recently, we could count on the userAlias part of the returned json to get the cluster name. It is an anti-pattern to rely on string manipulations but it was working. Now, when some clusters are migrated from serverless and/or flex and stay with the shared… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Administration API  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. When migrating shared/serverless/flex to dedicated - name the nodes correctly

    We recently had a few clusters migrated from serverless and flex to dedicated clusters. In some of them - the nodes of the new dedicated cluster were still the automatic, hashed names of the previous type.
    I think it would be a super great idea to create the new nodes in the same way they are created for new dedicated clusters - with the cluster name as their prefix and not ac-XXXXX like we got.

    Thanks,
    Oren

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. general cpu class for M400 and M600

    Currently when selecting M400 or M600 only "Low CPU" class is available. Our only option to increase CPU is going back to M300 with "General" class to get 96cpu. We would benefit a lot from "General" option of 128cpu and 160cpu.

    8 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. MongoDB Atlas UI in mobile devices

    I used to use my mobile phone to manage my Mongo Atlas cluster, using Safari and Chrome web browsers. Recently, you added a button called "copy configuration code" to the website's footer, between the "save draft" and "save changes" buttons.
    With this new button added, I can't see the "Review changes" button, either with the phone in portrait or landscape mode. I can't access it by expanding or reducing the image or activating Desktop mode in the browser.

    I know that de UI is optimized for desktop use, but sometimes, a Mongo admin must manage on the go and can't use a desktop device. Please, keep in mind this behaviour and think whether would be possible to modify the mobile UI to apply cluster changes, or to develop a mobile app to manage it.

    But in the meantime, could you change the footer configuration back to or swap "copy configuration code" and "Review changes" to allow applying changes in mobile devices?

    I used to use my mobile phone to manage my Mongo Atlas cluster, using Safari and Chrome web browsers. Recently, you added a button called "copy configuration code" to the website's footer, between the "save draft" and "save changes" buttons.
    With this new button added, I can't see the "Review changes" button, either with the phone in portrait or landscape mode. I can't access it by expanding or reducing the image or activating Desktop mode in the browser.

    I know that de UI is optimized for desktop use, but sometimes, a Mongo admin must manage on the go and can't… more

    •  

    •  

    •  

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Billing breakdown by usage dimension for private endpoints

    Since private endpoint billing is based on a "capacity unit" that has three dimensions (new connections, active connections, and processed bytes), and the bill is determined by the highest of the three, it is important to know how much of each of these three dimensions is being used in order to make engineering decisions on how to control cost.

    For example, if the main driver of usage is processed bytes and the other two dimensions are barely being used at all, then how we would go about how to control this cost would be very different than if all three dimensions are roughly being used equally. Not knowing how the usage breaks down between the three dimensions means there is no real way to plan for engineering efforts to control this cost.

    Since private endpoint billing is based on a "capacity unit" that has three dimensions (new connections, active connections, and processed bytes), and the bill is determined by the highest of the three, it is important to know how much of each of these three dimensions is being used in order to make engineering decisions on how to control cost.

    For example, if the main driver of usage is processed bytes and the other two dimensions are barely being used at all, then how we would go about how to control this cost would be very different than if all three… more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Billing  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Node specific defaultMaxTimeMS

    As this new functionality in 8.0 is intended to set a fixed time limit on all nodes across the cluster.
    Is there a possibility to set it different for each node?

    Our non-operational (Analytics) or secondaries may be capable to tolerate higher limits than Primary.
    Yes, 'maxTimeMS()' would overwrite this but adding it to all the queries is not feasible & occasionally the same deployed query may need to run little longer to retrieve/scan more docs than it was originally supposed to.

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. MongoDB Query Debugger Assistant

    Overview
    Introduce an AI-powered query debugger within MongoDB Atlas to help developers identify performance bottlenecks and syntax inefficiencies in real time as they write queries.

    Problem

    MongoDB’s flexibility sometimes leads to overly complex or inefficient queries, especially when aggregation pipelines or indexes are involved. Developers often need to switch contexts between the query editor, documentation, and performance tools like Atlas Profiler.

    Proposed Solution

    Build a MongoDB Query Debugger Assistant inside Atlas with the following features:

    Inline Warnings & Suggestions: As a user types a query, the assistant highlights potential issues (e.g., full collection scan, missing index usage) and suggests alternatives.

    Index Recommendation Engine: Based on historical workload, recommend the most efficient index for the query.

    Explain Plan Simplification: Convert verbose explain plans into plain English explanations, along with visual representations.

    One-Click Optimization: For common patterns, offer one-click fixes like creating a suggested index or rewriting a query.

    Value to Users

    Reduces debugging time and learning curve for new MongoDB users.

    Improves performance and reduces infrastructure costs by encouraging better query practices.

    Encourages usage of best practices natively within the platform.

    Monetization Angle

    This could be a premium feature for teams on higher-tier Atlas plans, or a value-add to increase conversion to paid tiers.

    Overview
    Introduce an AI-powered query debugger within MongoDB Atlas to help developers identify performance bottlenecks and syntax inefficiencies in real time as they write queries.

    Problem

    MongoDB’s flexibility sometimes leads to overly complex or inefficient queries, especially when aggregation pipelines or indexes are involved. Developers often need to switch contexts between the query editor, documentation, and performance tools like Atlas Profiler.

    Proposed Solution

    Build a MongoDB Query Debugger Assistant inside Atlas with the following features:

    Inline Warnings & Suggestions: As a user types a query, the assistant highlights potential issues (e.g., full collection scan, missing index usage) and suggests alternatives.

    … more

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    0 comments  ·  Data Explorer  ·  Edit…  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. fix example at https://www.mongodb.com/docs/atlas/operator/current/atlascustomrole-custom-resource/#basic-example

    in the example at spec:
    - "name" indentation is wrong
    - also action should be specified as in API example connPoolStats should be actually "CONNPOOLSTATS" (with underscores, seems they disappear here when I post)
    - at inheritedRoles there is no "role" as child field, should be database

    a correct manifest would be:

    apiVersion: atlas.mongodb.com/v1
    kind: AtlasCustomRole
    metadata:
    name: tester
    namespace: tester
    labels: {}
    annotations:
    mongodb.com/atlas-resource-policy: keep
    spec:
    projectRef:
    name: tester
    namespace: tester
    role:
    name: tester
    actions:
    - name: CONNPOOLSTATS
    resources:
    - cluster: true
    database: tester-database
    collection: tester-collection
    inheritedRoles:
    - name: operator-role-1
    database: tester-database

    2 votes

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Kubernetes Operator  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Maintenance alerts should be warnings

    I frequently receive alerts about maintenance jobs being scheduled. While I do want to receive those notifications, the title says “Alert - X - [date]” like all the other real and serious alarms I have. So filtering those maintenance warnings and real alerts that require immediate action is hard.
    It would make much more sense to include the type of the alert in the email subject (e.g. “Alert - X - maintenance scheduled” to make things easier or at least rename the maintenance alerts to warnings.

    1 vote

    Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

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

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating