1258 results found

1. Allow maintenance window definition per cluster

   Currently maintenance windows are defined per project. With multiple clusters in a project, maintenance will be performed at the very same time.

   We would like to space out maintenance windows per cluster in the same project, to prevent replica set election on multiple clusters taking place simultaneously.

   17 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

   2 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

2. Get all databases from one cluster

   Add a new Admin API to Atlas: Get all databases from one cluster

   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

3. Granular archiving window - schedule archiving at multiple times

   At present online archiving can only be sceduled once per day/week/month. There should be an option to add multiple scheduling windows in a day/week/month to enable schedules such as "every Saturday and Sunday", or "at 3AM and 10PM".

   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

4. Add option to "Explain" a query from the "Profiler" page.

   The profiler page shows a list of queries with metadata about them. It would be great to have the option to "explain" any query from this view, or in the slide-out view after clicking on a query.

   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

5. Restore atlas cluster backup to differently encrypted Project

   If we take a volume snapshot backup from one project which is encrypted with encryption key A, we need to restore it into another project with Encryption key B .
   If we use Live migrate for this, it may take more time than volume snapshot restore.
   We need this feature for quicker refreshes of database cluster.

   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

   1 comment  ·  Backup  ·  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

6. Query Online Archive over Web UI

   There is currently no possibilty to query a collection of an Online Archive via the Web UI of Atlas. This is only possible for the "normal" collections.
   It would be great if it would be possible to also query Online Archivce collections similar.

   This is related to the request of https://feedback.mongodb.com/forums/924277-data-federation-and-data-lake/suggestions/40949902-access-online-archive-in-customer-data-lake

   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

7. show the reason why you can't increase oplog

   in the settings=>additional settings=>More Configuration Options=>Set Oplog Size
   show the reason why you can't increase this parameter (let's say you have insufficient free space etc.)

   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

8. Basic operational metrix support with instana and grafana

   Hi MongoDB Team,

   We are using grafana and instana SRE tools for application monitoring.

   But MongoDB did not exposing the basic statistics like Total number of records and record insertion / updation / selection rates (over a sepcific period of time ) with grafana and instana .

   Kindly note that grafana and instana are widely used as industry standard SRE tool and it will be really helpful if MongoDB team could also expose these kind of detailed statistics with grafana and instana.

   I would request you to prioritize this request since lack of these reports is creating an empty space in our SRE reporting side.

   Hi MongoDB Team,

   We are using grafana and instana SRE tools for application monitoring.

   But MongoDB did not exposing the basic statistics like Total number of records and record insertion / updation / selection rates (over a sepcific period of time ) with grafana and instana .

   Kindly note that grafana and instana are widely used as industry standard SRE tool and it will be really helpful if MongoDB team could also expose these kind of detailed statistics with grafana and instana.

   I would request you to prioritize this request since lack of these reports is creating an empty space… 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  ·  Monitoring and Metrics  ·  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

9. prometh

   Hi MongoDB Team,

   We are using grafana and instana SRE tools for application monitoring.

   But MongoDB did not exposing the basic statistics like Total number of records and record insertion / updation / selection rates (over a sepcific period of time ) with grafana and instana .

   Kindly note that grafana and instana are widely used as industry standard SRE tool and it will be really helpful if MongoDB team could also expose these kind of detailed statistics with grafana and instana.

   I would request you to prioritize this request since lack of these reports is creating an empty space in our SRE reporting side.

   Hi MongoDB Team,

   We are using grafana and instana SRE tools for application monitoring.

   But MongoDB did not exposing the basic statistics like Total number of records and record insertion / updation / selection rates (over a sepcific period of time ) with grafana and instana .

   Kindly note that grafana and instana are widely used as industry standard SRE tool and it will be really helpful if MongoDB team could also expose these kind of detailed statistics with grafana and instana.

   I would request you to prioritize this request since lack of these reports is creating an empty space… 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  ·  Monitoring and Metrics  ·  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

10. Reconciliation resources flag improvement

    atlas-reconciliation-policy=skip flag provide ability do not sync k8s object status with atlas. But in case when we need to make reference on objects in Atlas (Aka project) and do not create or modify this resource - this flag not very useful nothing. In this case i would be good if
    - or operator sync object from API to k8s resources ( grub id by name so k8s resource will be valid )
    - or at least provide opportunity to set id ( for new resources with atlas-reconciliation-policy=skip set by default )
    Aka:

    • Follow the pattern of reading data from the objects even if not doing reconciliation for them. This is the norm for controllers
    • Support referencing api paths rather than just object references for the AtlasDeployments

    atlas-reconciliation-policy=skip flag provide ability do not sync k8s object status with atlas. But in case when we need to make reference on objects in Atlas (Aka project) and do not create or modify this resource - this flag not very useful nothing. In this case i would be good if
    - or operator sync object from API to k8s resources ( grub id by name so k8s resource will be valid )
    - or at least provide opportunity to set id ( for new resources with atlas-reconciliation-policy=skip set by default )
    Aka:

    • Follow the pattern of reading data from the… more
    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  ·  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

11. When Adding new CKM key/role Atlas should validate if it can safely change existing CKM key

    When we create new CKM key with new role and update credentials on project level, Atlas validates that new role can read new key. But it does not validate if new role can read existing CKM key.

    When Atlas starts re-encrypting existing cluster, first node goes down but can't be started because new role can't read old key. There is no way to restore/rollback this change unless raise a ticket for MongoDB support.

    Suggestion: when we upgrade credentials/role/KMS key in UI, Atlas should validate if it can finish this change BEFORE applying changes to nodes.

    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

12. Enable Private Link for Azure Data Factory

    Private Link for Azure Data Factory is not currently supported. This appears to be the most secure way for ADF to connect to Atlas / MongoDB, and support for this feature would be ideal for our use-case.

    14 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

    4 comments  ·  Integrations  ·  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

13. Support NVMe for Atlas Azure

    Support NVMe disk for MongoDB Atlas Azure.

    3 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

14. Atlas Administration API: Expose more information on cluster status

    We are using the Atlas Administration API in order to automate scaling a production database cluster deployment in a more fine-grained way than the existing autoscaling offer. The specific database cluster is deployed as a replica set, so there is a number of electable nodes (one primary + 2, 4 or 6 secondaries) and any number of read-only (RO) nodes.

    The goal is to be able to tune the number of nodes in a specific region, and being able to monitor the progress of the change being rolled out. Currently, the API offerings are too limited to do this effectively, but the web console clearly has access to the information we need.

    The current implementation of the returnAllMongodbProcessesInOneProject operation in the administration API lists all processes in the project, which would need to be filtered down to the processes that apply to just the specific cluster. The specific cluster processes do have a unique replicaSetName string in common but that name appears to be internal to Atlas and only appears in the connectionString -> standard URI for the given cluster. This information doesn't distinguish electable nodes from read-only nodes or analytics nodes, nor will it indicate if a machine is in the process of being deployed or decommissioned.

    Because of this the public administration API only gets you part of the way there, as it won't let a process on our side recover from being restarted during a cluster adjustment operation: there is no way of detecting a machine being decommissioned (which will delay deploying a new change), nor would a net-zero machine count change (e.g. moving from RO nodes to electable nodes) be observable.

    The web console on the other hand, has access to much more information, via the (private) https://cloud.mongodb.com/nds/clusters/{groupId}/{name} and https://cloud.mongodb.com/nds/clusters/{groupId}/{name}/instances endpoints; these are, respectively, a more detailed version of the public returnOneCluster operation and an array of process states specific to the cluster (so a filtered version of returnAllMongodbProcessesInOneProject) . These APIs lets us monitor cluster change operations much, much better, as they include more detailed node role information (electable vs read-only vs analytics).

    To properly manage scaling via the public API, we'd really need to have that information available in the public API too.

    We are using the Atlas Administration API in order to automate scaling a production database cluster deployment in a more fine-grained way than the existing autoscaling offer. The specific database cluster is deployed as a replica set, so there is a number of electable nodes (one primary + 2, 4 or 6 secondaries) and any number of read-only (RO) nodes.

    The goal is to be able to tune the number of nodes in a specific region, and being able to monitor the progress of the change being rolled out. Currently, the API offerings are too limited to do this effectively,… 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  ·  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

15. Atlas UI enhancement

    Hi,

    Atlas UI is displaying "Database Deployments" earlier it used to be as cluster or clusters.

    1. When we hit the create button all it talks about "CLUSTERS > CREATE NEW CLUSTER"
    2. Right side top corner, we can also see it states "All Clusters"
    3. Terraform resources/attributes talks about Clusters
    4. Only place we see in the home page "Database Deployments"

    Our customers are getting confused with Database Deployments with Databases within the clusters. Customers are thinking they need to create more database (database deployments) if they want to have for their application, which is not true. They can create multiple database in single "Database Deployments/Clusters" , it would be helpful it can be changed it back to Clusters instead of "Database Deployments" to align with other places. This will help customers more clarity.

    Thanks,
    Suresh

    Hi,

    Atlas UI is displaying "Database Deployments" earlier it used to be as cluster or clusters.

    1. When we hit the create button all it talks about "CLUSTERS > CREATE NEW CLUSTER"
    2. Right side top corner, we can also see it states "All Clusters"
    3. Terraform resources/attributes talks about Clusters
    4. Only place we see in the home page "Database Deployments"

    Our customers are getting confused with Database Deployments with Databases within the clusters. Customers are thinking they need to create more database (database deployments) if they want to have for their application, which is not true. They can create multiple database in… more

    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

16. Copy/Duplicate Cluster configuration

    It would be really useful to create a new cluster based on an existing configuration.

    Snapshots are supposed to be loaded into clusters of the same configuration, but having to set up the configuration manually is prone to human error. Having an option to copy the cluster configuration would be helpful.

    Support suggested the following workarounds, but the option should really exist in the UX, given that snapshots can be taken and loaded in the UX.
    - use the API to create all clusters so that the config exists in code
    - use terraform to create clusters

    3 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

17. webhook

    Have the ability to specify template for the webhook being send. Currently this is static information and it would be better if it is possible to customize it. This will also make the integrations with not supported 3rd parties more easier and it doesn't have to create a mitm service that translates the atlas webhook to some other format.

    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  ·  Integrations  ·  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

18. Add ability to chose the new primary node when you perform a test election

    There's a "test failover" option, which shuts down the primary and forces an election. However, you have no control over which new primary will be elected (just the preferred region) which sometimes does not work as expected.

    It would be really useful if you have the possibility to manually chose which node will be elected as the new primary.

    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

    1 comment  ·  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

19. invoice

    Invoice should show the ClusterName combined with Cluster Tier and Server Hours same with Data Transfer. With these, it is easy to determine how much cost we are spending per ClusterName. Right now it only shows per ClusterTier which is hard to separate the cost if you have 2 same ClusterTier.

    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

    0 comments  ·  Billing  ·  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

20. Improve OpsGenie alert mis-categorization

    We noticed that alerts sent to Opsgenie using the Integrations is using "https://api.opsgenie.com/v2/alerts" URL, which causes Opsgenie to mis-categorize the alerts for all customers, according to Opsgenie themselves.

    Issue re-production steps:
    * Create a team in Opsgenie or use an existing team (use a team that is NOT used for the Default API integration)
    * Create a MongoDB integration in that team and take note of the API key
    * Create an Opsgenie Integration in MongoDB and use that API key
    * Generate an alert or Test the integration
    * Verify in Opsgenie that the test alert did NOT get assigned to the team you created the integration for, but instead, it got assigned to the team that is set as the team for the Default API integration

    Please use https://api.opsgenie.com/v1/json/mongodbcloud?apiKey=[your api key] URL to resolve the issue, so OpsGenie can properly categorize the alerts.

    We noticed that alerts sent to Opsgenie using the Integrations is using "https://api.opsgenie.com/v2/alerts" URL, which causes Opsgenie to mis-categorize the alerts for all customers, according to Opsgenie themselves.

    Issue re-production steps:
    * Create a team in Opsgenie or use an existing team (use a team that is NOT used for the Default API integration)
    * Create a MongoDB integration in that team and take note of the API key
    * Create an Opsgenie Integration in MongoDB and use that API key
    * Generate an alert or Test the integration
    * Verify in Opsgenie that the test alert did… 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  ·  Integrations  ·  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