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

1392 results found

  1. Enable Terraform export of HCL for existing Atlas configurations

    Allow for a standardized export tool that outputs Terraform HCL from existing, manually provisioned Atlas resources (e.g., projects, clusters, users, role mappings, et cetera). This would be similar to GCP's Terraformer or Azure's Export for Terraform.

    10 votes
    0 comments  ·  Administration API  ·  Admin →
    How important is this to you?

  2. 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
    1 comment  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

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

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

  5. 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
    0 comments  ·  Alerts  ·  Admin →
    How important is this to you?

  6. 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
    3 comments  ·  Online Archive  ·  Admin →
    How important is this to you?

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

  8. 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
    1 comment  ·  Terraform Provider  ·  Admin →
    How important is this to you?

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

  10. Use Semantic Versioning

    Hi,

    My problem is that the terraform provider doesn't use semantic versioning.

    This has caused me quite a few problems.
    Firstly - it's difficult when scrolling through your version releases to understand what's breaking and what's not (I lost an hour today having to check all the releases for updates, and then applying every couple of versions from an outdated provider to make sure there were no breaking changes).
    Secondly, it means I have to pin a specific version in my terraform provider rather than leaving it to auto-update to the latest minor version "~> 1.0".
    Lastly, it makes using…

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

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

    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
    1 comment  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  12. Add sendCollectionLatencyMetrics and sendDatabaseMetrics switches for Datadog Integration

    Atlas API supports (https://www.mongodb.com/docs/atlas/reference/api-resources-spec/v2/#tag/Third-Party-Integrations/operation/createThirdPartyIntegration) two (relatively new) keys for Datadog integration:
    * sendCollectionLatencyMetrics
    * sendDatabaseMetrics

    We need to have these switches in the terraform provider as well.

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

  13. 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
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  14. 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
    0 comments  ·  Administration API  ·  Admin →
    How important is this to you?

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

  16. 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
    0 comments  ·  Terraform Provider  ·  Admin →
    How important is this to you?

  17. 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
    1 comment  ·  Administration API  ·  Admin →
    How important is this to you?

  18. 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
    0 comments  ·  Other  ·  Admin →
    How important is this to you?

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

  20. Make Atlas UI aggregation pipeline builder limitations configurable

    There is currentl an aggregation pipeline builder limitation on $group, $bucket, and $bucketAuto which cannot be changed or increased in the Atlas UI. Make the limit configurable just like it is MongoDB Compass.

    2 votes
    0 comments  ·  Data Explorer  ·  Admin →
    How important is this to you?
← Previous 1 3 4 5 … 69 70
  • Don't see your idea?

Atlas

Categories

Feedback and Knowledge Base

(thinking…)