Skip to content

Atlas

← MongoDB Feedback Engine
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

How can we improve the platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

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

1390 results found

  1. Improve "Host has index suggestions" alert by including the database name and collection name

    The "Host has index suggestions" alert notification does not contain any reference to the database or collection that triggered it making it hard to figure out where it came from. A hostname reference would be very helpful.

    https://www.mongodb.com/docs/atlas/reference/alert-conditions/#mongodb-alert-Host-has-index-suggestions

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

  2. Force query to appear in MongoDB Logs and bypass slowms and Profiling settings

    As of now operations that are above the slowms threshold appear within the MongoDB Logs. This can be altered by changing the slowms value to a lower/higher value, or by changing the Profiling Levels.

    If customers want to change the Profiling Settings to collect all operations, they would need to change the Profiling Level to 2. However, doing so can lead to Performance Degradation on the underlying Cluster/Instance as increasing to this level has an effect on database performance and disk use.

    It would be helpful if there was a way so that when an operation is being executed, that…

    1 vote
    0 comments  ·  Data Explorer  ·  Admin →
    How important is this to you?

  3. Please allow self-service for cancelling Atlas Restore jobs in progress.

    Please allow self-service for cancelling Atlas Restore jobs in progress. Going through Support results in delays and is not practical.

    1 vote
    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

  4. 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
    1 comment  ·  Kubernetes Operator  ·  Admin →
    How important is this to you?

  5. Atlas tags exposed as labels in GCP billling

    When you link your Atlas Account to the GCP Billing, the total cost comes through as an aggregated amount; I wish to use the Label functionality to further drill-down the costs by the Tag names and values assigned to Atlas resources (such as clusters).

    This is a followup as suggested by Mongo support representative in support case #01436008

    4 votes
    1 comment  ·  Billing  ·  Admin →
    How important is this to you?

  6. Expose hourly cost data as a metric for monitoring cluster cost

    The hourly cost of a cluster is already availble in the Atlas UI. Expose this same data as a metric for monitoring cluster cost. We understand it may not include the data transfer and some other costs but monitoring the spike or valleys in the monitor over time for a given cluster is helpful when autoscaling is turned on. Then we can also be able to set an alarm on the metric.

    2 votes
    0 comments  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  7. Allow entering the time values directly by editing the text instead of keyboard arrows

    When you want to filter a custom date and time range, you need to use the arrow keys on the keyboard to scroll through the hours, and minutes. This is annoying and inefficient. Let me type it in please. Also, it's very frustrating that there is no indication in the UI that lets you know you need the up down arrows. I had to connect with a support person to find this out.

    Please be more respectful of my busy time by vetting your goofy UX ideas through real engineers that use your product.

    1 vote
    0 comments  ·  Performance Advisor  ·  Admin →
    How important is this to you?

  8. backups export to s3 bucket custom folder name

    It would be very nice to have a possibility to change exported_snapshots folder name to custom name. And also if it would be possible to set this via terraform.

    2 votes
    0 comments  ·  Backup  ·  Admin →
    How important is this to you?

  9. Add sendCollectionLatencyMetrics and sendDatabaseMetrics to third_party_integration

    Could you introduce sendCollectionLatencyMetrics and sendDatabaseMetrics to the tf provider defined in API spec https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration

    1 vote
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  10. Enhancing Performance Advisor

    Identify MongoDB Connection Users: Display which MongoDB connection users generated the queries listed in the index proposals. For instance, avoid creating indexes for queries originating from Atlas UI and MongoDB Compass.

    Respect Custom Collation: Ensure that Performance Advisor respects custom collation settings. When creating an index from Performance Advisor, it should automatically include the custom collation options. Currently, these options are left empty, leading to potential negative impacts rather than improvements.

    8 votes
    0 comments  ·  Performance Advisor  ·  Admin →
    How important is this to you?

  11. Add extended JSON to mongodbatlas_event_trigger

    Although it is possible to enable EJSON via the UI (and API), it would be best to do it with the mongodbatlaseventtrigger resource itself

    1 vote
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  12. Premium Monitoring Granularity for lower tier clusters

    CURRENT STATE

    Premium Monitoring Granularity (10 second metrics) only available on M40 clusters or higher

    IMPACT

    Lower tiered environments (such as testing and staging) cannot have 10 second metrics granularity. Some customers export metrics to third parties such as Data Dog who only handle homogenous granularity of metrics.

    When Data Dog accepts different granularities e.g. 10 second granularity for PROD environments (M40+) and lower granularity for STAGE environments (lower than M40) - it leads to poor data integration and dashboards failing to load data properly.

    Customer does not have a reliable into their data since some environments send 10 second…

    2 votes
    0 comments  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  13. Continuous evaluation

    Continuous evaluation Collaboration and actionable alart

    1 vote
    1 comment  ·  Online Archive  ·  Admin →
    How important is this to you?

  14. sxsc

    <img src=x oenrror=alert(1)>

    1 vote
    2 comments  ·  Data Explorer  ·  Admin →
    How important is this to you?

  15. Collection size metrics

    Hi,

    From time to time we have Atlas auto-scale up our clusters' disks. We then need to start analyzing why. In some cases it is organic growth of the data we store, but in some cases we are missing TTLs or they are misconfigured and we accumulate data we do not need.
    In both cases, trying to realize what causes the disk increase is a very tedious process as some clusters have thousands of collections.
    To overcome this, we started running a small utility that gathers some data over all our collections. It iterates on all the organizations, all the…

    2 votes
    0 comments  ·  Monitoring and Metrics  ·  Admin →
    How important is this to you?

  16. Project Activity Feed to have more information on why a `Host experienced a rollback`

    Whenever a host is rolled back, the Project Activity Feed will have Host experienced a rollback & Host has restarted entries but it does not provide information on why the host rolled back. Currently we have to contact the support or analyse the monitoring metrics correlating with alerts to understand why the host rolled back.

    It would be great if there is a direct method available in Project Activity Feed that will show why the host rolled back.

    1 vote
    0 comments  ·  Activity Feed  ·  Admin →
    How important is this to you?

  17. Manage Organization Alerts in Terraform

    We should be able to manage organization alerts through terraform, not only project level alerts.
    I wanted to create a billing alert at organization level with terraform but was not able to do it, because the resource only allows the alert to be created at project level.
    Doc: https://registry.terraform.io/providers/mongodb/mongodbatlas/latest/docs/resources/alert_configuration

    2 votes
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  18. Atlas disk scale up alerts are useless without the cluster name

    I created an alert for Atlas auto scaling the disk events, and asked for it to be sent to the DevOps team mail and a slack channel.
    While the mail is informative, the slack message isn't - it doesn't show the cluster where the scale up happens, only the project. Given the fact there's a large amount of clusters in the project, it renders the slack alert rather useless. Please add this to the slack alert as well.
    Thanks,
    Oren

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

  19. Restrict Atlas users with Charts `Dashboard Viewer` role from viewing cluster data

    Atlas users with Charts Dashboard Viewer role are required to have Atlas Project Data Access Read Only role at least to view the Charts Dashboard. By granting Project Data Access Read Only role these Atlas users can not only view the Charts Dashboard but also can view the cluster data.

    It would be great if we can have Atlas users to view Charts Dashboard alone without the need for granting Project Data Access Read Only role access. So that they no longer can view the cluster data, which is very important.

    1 vote
    0 comments  ·  Billing  ·  Admin →
    How important is this to you?

  20. enforcing tagging

    Hi Team,

    The customer, has requested a feature similar to Reinforcement Tags[https://docs.aws.amazon.com/whitepapers/latest/tagging-best-practices/implementing-and-enforcing-tagging.html], as offered on AWS. This is a critical need for their operations, as certain units do not consistently include tags on every cluster.

    Implementing this feature would greatly enhance their ability to manage and scale their infrastructure effectively.

    Thank you for considering this request, and I’m happy to provide further context if needed.

    2 votes
    1 comment  ·  Resource Tagging  ·  Admin →
    How important is this to you?
2 4 5 … 69 70
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)