462 results found

1. Allow scheduling grooms

   Add the ability to schedule groom jobs at a specific point in time. Also expose this functionality through the API for easy modifications through configuration management tools.

   10 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  ·  Ops Manager  ·  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. disk iops

   Can you please revert the change to metrics view for disk iops? It it completely unreadable and meaningless now.

   There used to be 2 lines that made sense. Now there are 4... but looks like a bar chart. Anyway. Can't read it.

   I would suggest.
   1. have 1 view with 3 lines: 1 for the average read and 1 average write and 1 average BOTH.

   1. have a second view showing the "burst" performance. Draw this as a LINE or scatter plot. Whatever you are drawing now is inscrutable.

   thanks!

   •  

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

3. Add filters to Global alert screen in Ops Manager

   Add a filter for Global alert Configuration Page. It would be nice to have the ability to search for the specific alert to see if you have it configured and for which environments.

   A filter similar to what is seen on the "Open Alert" view would be sufficient.

   Since we are managing upwards of 50 deployments via Global Alerts this would be a useful feature.

   •  

   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  ·  Ops Manager  ·  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. Allow the Kubernetes Operator to delete a project

   Currently it is not possible to delete a project via kubectl command.

   As the Kubernetes Operator allows one to create a project (configmap) and deploy a replica set, we would expect it to also allow the deletion of a project so that we can fully automate the solution.

   10 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  ·  Enterprise 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
   planned  ·  AdminDan (Admin, MongoDB) responded

   While deletion of a deployment is possible via Kubernetes, deleting a MongoDB resource doesn’t remove it from the Ops Manager UI. You must remove the resource from Ops Manager manually. To learn more, see Remove a Process from Monitoring.

   
   

   Deleting a MongoDB resource for which you enabled backup doesn’t delete the resource’s snapshots. You must delete snapshots in Ops Manager.

   
   

   Find out more.

   
   

   Work is planned to remove Ops Manager as a prerequisite (though it's use will still be optional and supported) and as part of that we hope to address this deletion aspect.

5. Change MongoDB Log Settings via API

   You can set MongoDB log rotation for mongod process on project level in the Ops Manager through: Deployment -> More -> MongoDB Log Settings. However there is no option to set it via API.
   It looks like there is option to set this parameters on process level (in the Automation Config), but Ops Manager is not accepting new value, like it does when setting values for Monitoring Log rotation and Backup Log rotation.
   It would be great to have option to automate this when creating a new project via API and setting all other attributes with script.

   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  ·  Ops Manager  ·  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. Use separate tls.crt and tls.key items in a kubernetes secret for certificates instead of a combined item named server.pem for a MondoDB rep

   There should be a way to use separate tls.crt and tls.key items in a kubernetes secret for certificates instead of a combined item named server.pem.

   We request our certs using cert-manager which generates secrets from the cert CRD and will get auto renewed every so often. These secrets have 2 items, tls.crt and tls.key.

   So far the only way I have seen to enable tls is to combine these 2 items and rename it into a new secret in kubernetes as item called server.pem. This however means that when a cert auto renews that the wrong secret is being used. So our replicaSets would break on each renewal (every 90 days).

   If some flexibility was built in on how to provide certificates to the replicaSet, there would be no issue and auto renewing our certs would not break MongoDB in production every 90 days.

   There should be a way to use separate tls.crt and tls.key items in a kubernetes secret for certificates instead of a combined item named server.pem.

   We request our certs using cert-manager which generates secrets from the cert CRD and will get auto renewed every so often. These secrets have 2 items, tls.crt and tls.key.

   So far the only way I have seen to enable tls is to combine these 2 items and rename it into a new secret in kubernetes as item called server.pem. This however means that when a cert auto renews that the wrong secret… 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  ·  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
   planned  ·  Andrey responded

   Support for Cert Manager as well as support for separate crt and key is on a roadmap.
   We will look into updating our docs to describe cert rotation.

7. Ops Manager: more precise firewall configuration documentation

   Currently, it is not clear from the documentation what are the source hosts for each port to open. The diagram fills in a bit this imprecision, but it is not formal enough. Also, some ports need to be open only if certain features are needed (eg. download link for snapshots).

   This makes firewall configuration imprecise and experimental (or not as secure as it could be).

   Suggestion: each table of the the Ops Manager firewall configuration webpage should document those columns:
   - source component: client component(s)
   - target component: server component(s)
   - protocol: tcp/udp
   - port
   - feature: to specify if the port is needed only for some optional feature

   Currently, it is not clear from the documentation what are the source hosts for each port to open. The diagram fills in a bit this imprecision, but it is not formal enough. Also, some ports need to be open only if certain features are needed (eg. download link for snapshots).

   This makes firewall configuration imprecise and experimental (or not as secure as it could be).

   Suggestion: each table of the the Ops Manager firewall configuration webpage should document those columns:
   - source component: client component(s)
   - target component: server component(s)
   - protocol: tcp/udp
   - port
   - feature: to specify if… 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  ·  Ops Manager  ·  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

8. Allow to generate/download MongoDB Server Audit process logs

   Problem Statement,
   What is the problem? As of now (2021-03-17) Ops Manager does not support downloading MongoDB Server Audit process logs via UI/API. Atlas does have support for it (via GET /groups/{GROUP-ID}/clusters/{HOSTNAME}/logs/{LOG-NAME} API call).

   Why is this a problem? Users needs to be able to download MongoDB Server Audit process logs via Ops Manager, same way as they do for MongoDB Server process logs/FTDC and MongoDB Agent logs (this significantly simplify troubleshooting, when required). Some users require to download MongoDB Server Audit process logs programmatically to store them in Security Information and Event Management (SIEM) system.

   Proposal,
   * Add MongoDB Server Audit process logs option support in POST /groups/{PROJECT-ID}/logCollectionJobs and in GET /groups/{PROJECT-ID}/logCollectionJobs/{JOB-ID}/download Public API calls as well as in Ops Manager Project UI. This will align functionality between Atlas and Ops Manager.

   Problem Statement,
   What is the problem? As of now (2021-03-17) Ops Manager does not support downloading MongoDB Server Audit process logs via UI/API. Atlas does have support for it (via GET /groups/{GROUP-ID}/clusters/{HOSTNAME}/logs/{LOG-NAME} API call).

   Why is this a problem? Users needs to be able to download MongoDB Server Audit process logs via Ops Manager, same way as they do for MongoDB Server process logs/FTDC and MongoDB Agent logs (this significantly simplify troubleshooting, when required). Some users require to download MongoDB Server Audit process logs programmatically to store them in Security Information and Event Management (SIEM) system.

   Proposal,
   * Add MongoDB… 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  ·  Ops Manager  ·  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. Support Service Binding Specification for Kubernetes

   Service Binding Specification for Kubernetes standardizes exposing backing service secrets to applications. The spec is available here: https://github.com/servicebinding/spec

   This blog post would be helpful: https://muthukadan.net/kubernetes/binding/support-service-binding-specification-for-kubernetes/

   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  ·  Enterprise 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
   under review  ·  AdminDan (Admin, MongoDB) responded

   Low customer demand. Potentially in the future if we hear sufficient demand.

10. Automated rotation of the Keyfile

    Hello,

    I have an idea about the Keyfile rotation. So actually you can rotate the Keyfile only through the ops manager manually. But I would recommend to do this automatically with an API. This would help us alot since we have alot of mongoDB instances and this would save alot of time.

    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  ·  Automation  ·  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. Supported Ansible module for MongoDB

    Supported Ansible modules for MongoDB. Maybe a module for self managed and Atlas.

    7 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

12. Display the feature compatibility version (FCV) in Cloud Manager/Ops Manager UI

    The FCV could be different than the MongoDB version. Also, sometime the FCV on different shards/CSRS in a sharded cluster might be different (e.g. FCV is upgraded on the shards, but for some reason FCV is not upgraded on the CSRS), and this could cause issues.

    It would be nice if FCV is displayed next to the MongoDB version information. So that we can spot out the discrepancy quickly.

    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  ·  Cloud Manager  ·  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

13. Add ability to configure Pod Distruption Budget for STS

    During maintenance work EKS admins may need to evict nodes. This should not cause outage for MongoDB cluster/replicaset running on these nodes. we can create manually PDB for STS, but it would be nice to have an option to do it as part of MongoDB Kubernetes Operator.

    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

    2 comments  ·  Enterprise 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
    under review  ·  AdminDan (Admin, MongoDB) responded

    Supporting Pod Disruption Budget natively is something we do hope to do at some point. 

    
    

    But for now it is still possible by creating the PodDisruptionBudget resource and targeting the deployment using labels. (As per https://kubernetes.io/docs/tasks/run-application/configure-pdb/)

14. Add MongoDB user discovery via the API

    For users running DBaaS MongoDB products powered by Ops Manager automation, it would be useful if the API provided a way to replicate the cluster import behavior where MongoDB users are automatically discovered. This would help in scenarios where an existing Ops Manager deployment fails, and hundreds of deployments need to be moved to a different Ops Manager without knowing what MongoDB credentials the end user of that deployment had created. Having this API would allow the DBaaS provider's own scripting/automation to orchestrate moving these deployments to a new Ops Manager stack with reduced downtime.

    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  ·  Ops Manager  ·  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. Support migrations to different snapshot stores

    Currently it is not possible to transition between snapshot store types.

    There are two options currently when transitioning to the new one.

    1. Terminate backups (deleting all previous snapshots)
    2. Create a new project and abandon the previous one to allow automated restores at a later time

    Both of these options are difficult to manage for large deployments. The first option requires you to store the snapshots elsewhere and disallows automated restores. The second option requires many operations and clutters the Ops Manager project list.

    Ideally we should be able to transition from any store location/type to any other location/type. One of the following features would be viable for this request.

    1. Leaving snapshots on the previous snapshot store, and continuing backups on a new one
    2. Migrating all snapshots from one snapshot store to the new snapshot store

    Tangentially related - https://feedback.mongodb.com/forums/924355-ops-tools/suggestions/40622959-do-not-delete-backups-of-deleted-deployments

    Currently it is not possible to transition between snapshot store types.

    There are two options currently when transitioning to the new one.

    1. Terminate backups (deleting all previous snapshots)
    2. Create a new project and abandon the previous one to allow automated restores at a later time

    Both of these options are difficult to manage for large deployments. The first option requires you to store the snapshots elsewhere and disallows automated restores. The second option requires many operations and clutters the Ops Manager project list.

    Ideally we should be able to transition from any store location/type to any other location/type. One of… more

    31 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  ·  Ops Manager  ·  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. Reset duplicates button for Ops Manager Admin System overview page

    Sometimes customer want to clean up the System Overview page and/or the application db from because:
    - They dismissed one or more Ops Manager server running Application servers or backup daemon components
    - Their hostnames / domains have changed over the time
    - Their hostnames have changed from lowercase to capital letters or vice versa because upgrading Ops Manager brought a JVM providing different values for getHostname() (this happens often in Windows environment).

    It would be nice to have a button or at least an API call similar to the project reset duplicates that forces Ops Manager to refresh the internal host mappings and the appstate.

    Sometimes customer want to clean up the System Overview page and/or the application db from because:
    - They dismissed one or more Ops Manager server running Application servers or backup daemon components
    - Their hostnames / domains have changed over the time
    - Their hostnames have changed from lowercase to capital letters or vice versa because upgrading Ops Manager brought a JVM providing different values for getHostname() (this happens often in Windows environment).

    It would be nice to have a button or at least an API call similar to the project reset duplicates that forces Ops Manager to refresh the… more

    5 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  ·  Ops Manager  ·  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. Warn if deploying changes will require a rolling restart

    When reviewing changes in automation, warn if deploying changes will require a rolling restart.

    As an example, look at the documentation for server parameters. Many parameters include the description "You can only set THIS during start-up", but the the warning that setting this parameter necessitates a restart is missing from Ops Manager (or Cloud Manager).

    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

    2 comments  ·  Automation  ·  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. Allow disabling Blockstore for assignment through the Ops Manager CRD

    By default, when enabling backups and configuring a Blockstore for an Ops Manager custom object, the specified Blockstore will be set as "Assignment enabled" in the UI.

    It would be helpful to expose the enable/disable button for the blockstore through the CRD since disabling it through the UI, results in the parameter being reverted every time the operator consolidates. This is useful for the case when more than a single store is configured and as a user you would like to disable the blockstore to make it unavailable for new backup jobs.

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

19. Terraform adapter to deploy self managed MongoDB Enterprise Advance
    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

    1 comment  ·  Automation  ·  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. Add the ability for the backup daemon to download and validate snapshots

    In order to test snapshots automatically, create a new job type that allows the Backup Daemon to download the snapshot from the snapshot store, then run validate on each collection.

    If any collection fails validation, send an alert to the Backup Admin with the list of corrupted data.

    18 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  ·  Ops Manager  ·  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