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

1379 results found

  1. Provide state import capability on mongodbatlas_organization resource

    The mongodbatlas_organization resource does not have state import capabilities and I don't understand why. This doesn't seem to be a difficult one to implement and for us it will greatly help, because we have a need to import into state existing organisations which were created (unfortunately) outside terraform.

    12 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Tags on databases and use these tags in Billing dashboards

    I want to be able to tag databases inside clusters and be able to build my custom Billing dashboards using these tags.

    I have multiple databases within a cluster and each database serves a different feature or microservice. I'd like to know how much I spend by a tag for compute, storage and data transfer, etc.

    I want to be able to apply the same tag across multiple clusters on multiple databases, so Billing can be calculated on multiple databases across multiple clusters.

    This feature would greatly improve Mongo's FinOps capabilities.

    8 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  ·  Billing  ·  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. Improve "Query Targeting Alerts" alert by including the database name and collection name

    The "Query Targeting Alerts" 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/#query-targeting-alerts

    6 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. Request for Addition of Seoul Region to Reduce Latency

    Sure! Here's the translation of your request:

    A brief description of what you are looking to do
    I would like to request the addition of the Seoul region because there is currently only the Japan region, which results in a 2-second delay for requests.

    How you think this will help
    Adding the Seoul region will reduce the latency and improve the overall performance of our application.

    Why this matters to you
    This matters to me because the current delay is affecting the user experience and efficiency of our services. Reducing latency is crucial for maintaining high performance and user satisfaction.

    17 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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  ·  Billing  ·  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. Adding description in user database using Terraform

    I'm not able to set description on user database using terraform. This feature is available on API but not in the terraform provider.

    7 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

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

    7 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    37 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. Support Google IdP for OIDC Workforce Federation

    The Atlas supports federated login with external Identity Providers via OIDC (https://www.mongodb.com/docs/atlas/workforce-oidc/) for authenticating human users in tools like mongosh or Mongo Compass.

    Unfortunately the OIDC login doesn't work with the GCP IdP: OAuth2 clients in Google IdP always have a client secret (even clients considered as "public"). There is no way to specify the client secret in Atlas UI in the Workload Federation configuration and this leads to "invalidrequest (clientsecret is missing.)" error returned from the IdP as it always expects a client secret to be present.

    The support of an optional client secret in…

    11 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  ·  IAM  ·  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. 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…

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    7 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  ·  Other  ·  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. sxsc

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

    1 vote

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Add connection pooling metrics for sharded clusters

    We recently ran into an issue where we hit the internal mongoS -> mongoD connection pool limit when reading from secondary's requiring Atlas support to increase the value of ShardingTaskExecutorPoolMaxSize.

    As a result it would be great to be able to monitor the internal mongoS -> mongoD connection pool usage so we can monitor it and set up alarms if it gets near the limit.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    6 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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. Allow API key with project owner rights the update of project API keys

    We would like to use the terraform provider mongodbatlas_access_list_api_key to maintain the access list of our existing API keys.
    We don't have an API key with organization owner rights. We have only an API key with project owner rights.
    When I do the changes via web ui project owner rights are enough. I don't understand why the terraform provider needs organization owner rights.
    In my understanding it should be possible to execute the provider mongodbatlas_access_list_api_key also with project owner rights.

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 68 69
  • Don't see your idea?

Feedback and Knowledge Base