Skip to content

Ops Tools

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

446 results found

  1. Disable point-in-time restores

    It would be nice to have the ability to set the parameter "Allow point-in-time restores going back" to ZERO (disabling PIT restores). This could be useful in situation where a database is producing a lot of oplog and DBA wants to avoid the saturation of oplog-store. In other words: "I want to mantain shapshot backup functionality, but deactivate PIT functionality".

    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

    under review  ·  0 comments  ·  Backup  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Incremental backup with reduced snapshots size

    The actual size of EACH snapshot is equal to datapath filesystem size. Every snapshot is essentially a copy of all db files. This prevents the use of OPS Manager Backup for large databases. It would be desirable to have a "real" incremental backup, based on one "baseline-snapshot" plus "delta-snapshots" of reduced size.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Ops Manager: API endpoint for /databases should not require host

    Currently the Ops Manager API to list databases requires a hostname: /groups/{PROJECT-ID}/hosts/{HOST-ID}/databases

    It would useful to gather databases on a project or cluster level instead as the databases are the same across replica set members.

    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

    0 comments  ·  Ops Manager  ·  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. reencrypt existing snapshot with new kmip key

    Customer may decide to migrate from one KMIP provider to another or from one KMIP server to another. If you need store backups for a long period of time (7 years for compliant reason is not an exception), it becomes difficult to make sure that you can restore snapshots from old keys and all old KMIP servers still up and running.

    it turns out that it's not possible to export old keys from one kmip provider and import into another kmip provider due to security reasons.

    But at the same time - it looks like much easier to implement option…

    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

    0 comments  ·  Backup  ·  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. Add an option to GUI to rotate Certificates

    Add an option to GUI to rotate Certificates for each or all instances of replicaset for MongoDB.

    Should include options:

    1) rotate certificates for one instances on one server.
    2) rotate certificates for all instances belonging to a replicaset.
    3) rotate certificates for all instances on one server.
    4) rotate certificates for all instances on all servers for a project.

    Similar to https://www.mongodb.com/docs/manual/reference/command/rotateCertificates/#mongodb-dbcommand-dbcmd.rotateCertificates

    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

    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. Replica Set size Alert

    Have an Alert in Ops Manager to notify that a Replica Set is approaching the maximum recommended size (ie: 2TB) and that it should be converted into a Sharded Cluster.

    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)
  7. Add a cross reference of all projects and roles to user profile

    I must click on projects to display all the projects in my list, click the Users link for a project, then search for my ID to see the roles assigned to my ID.

    My idea is to consolidate this information and display it under my user profile similar to the Organization page. 3 clicks display my roles for each project on a single page.

    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

    0 comments  ·  Ops Manager  ·  Admin →
    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 Enterprise Kubernetes Operator PVC expansion

    The enterprise operator should be capable of performing all the steps necessary to increase the PVC after the end-user has adjusted the storage values within the MongoDB custom resource.

    Reference:
    https://www.mongodb.com/docs/kubernetes-operator/stable/tutorial/resize-pv-storage/

    Why is the Operator incapable of doing the steps starting from step 3 by itself if I simply do step 5?

    So what we think should be the case:

    We update the database resource with a new storage value.

    Then should perform the following steps:

    • Patch each persistence volume which can be found in the sts / pod spec.
    • Remove the sts with --orphan because the name should be…
    9 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)
  9. add organisation name to project name when project name is not unique

    There are multiple places where we need choose project. for example, to create global alerts we can exclude some projects from this alert.

    The issue is project name is not unique and there could be projects with the same name in different organisations. For example, every organisation may have project dev or test.

    it comes to the issue that you will see in the list of projects "dev,dev,dev,dev" and you don't understand which one you want to use.

    it will be much better to display them in the format "org/project", so the example above would be "org1/dev, org2/dev, org3/dev" which…

    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

    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  10. Add options to the connection string through the MongoDBUser

    We would like to add options to the connection string that is generated by the operator when creating a new MongoDBUser.
    The idea is to include these options in the MongoDBUser CRD so the operator can then add them to the connectionString stored in the generated secret.

    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)
  11. Ability to export/import index definition from mongoexport/mongoimport and/or mongodump/mongorestore

    Mongodump/mongorestore and/or mongoexport/mongoimport (whichever makes more sense) should provide an option to export/import only indexes. This would aid in non-conventional migration approaches, moving data to lower environments, etc.

    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

    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)
  12. Instantly Release Storage of collection after Remove the data from the collection

    It should provide an attribute when removing a document, inquiring whether you want to release storage immediately or later, instead of executing the compact command. This feature is helpful when you want to retain only the latest 6 months of data and remove older records. For example, I have IoT devices that fetch vehicle GPS locations, and each device has its own separate collection in MongoDB.

    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

    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)
  13. Add a variable for set the RS name

    Add own variable to set the RS name so that the deployment name can be used to name the pod

    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)
  14. allow mongocli read configs from stdin rather than from file

    To deploy new cluster we need prepare config file and put there all sensitive data, like automation user password, ssl cert passwords etc.
    Then we have to specify -f flag to point to this config during mongocli call.

    Currently this file has to persist somewhere on the disk during call to CLI which makes it insecure (and file has to be carefully removed after cli call finished, proper access to the file has to be set etc)

    It would be safer to send this config to stdin of mongocli - as a pipe from another command which can generate the…

    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. Make all metrics used in the Atlas dashboard available for the prometheus integration

    Make all metrics used in the Atlas dashboard available for the prometheus integration (https://www.mongodb.com/docs/cloud-manager/tutorial/prometheus-integration/#mongodb-metric-labels).
    Also describe how the current Atlas dashboard metrics are build from those.
    I'm looking especially for the metrics:
    - Max Disk IOPS
    - Queues

    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)
  16. Supporting the installation of mongosh in Ops Manager Local Mode

    Ops Manager v6.0+ supports installing the new mongo shell (mongosh) to the deployment nodes. This feature is not supported in Ops Manager Local Mode.

    It would be convenient to the Ops Manager Automation user if they could upload the mongosh binary to the Ops Manager Versions Directory and Ops Manager will install the binary to the deployment nodes similar to the MongoDB Binary and MongoDB Database Tools.

    Currently, the customer with Local Mode needs to manage the installation of mongosh outside of Ops Manager Automation.

    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  ·  Ops Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  17. Added features to improve backup performance on filesystem

    Currently, the ability to use multiple workers in Ops Manager is only available for S3. If possible adding this capability, or additional enhancements, to filesystem storage would be beneficial.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Backup Daemon should check for the available filesystem before starting a groom job

    When a groom job starts, it might get stuck or fail if the available disk space is not enough to copy all live blocks to another directory.

    It would be helpful if the Backup Daemon checks the available disk space before starting a groom job, and notifies the user:
    1. via Ops Manager UI
    2. report it in the logs
    3. sends an alert that the upcoming/scheduled groom job would not start due to low disk space.

    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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. monitoring opt

    Allow to configure startupOptions for monitoring/backup agent logs in yaml for deployments. Similar as we have for AppDB - spec.applicationDatabase.monitoringAgent.startupOptions

    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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. clear text password for mongodb ldap authorization

    Add the feature to Encrypt the queryPassword parameter for LDAP in the config file directly via Ops Manager , so that text password should not be present in config file.
    Keeping direct password is a security concern.
    Sample format of the config file:

    ldap:
    authz:
    queryTemplate: '{USER}?memberOf?base'
    bind:
    method: simple
    queryPassword: <Password>
    queryUser: <username>
    servers: serevername:port
    transportSecurity: tls
    userToDNMapping: '[ { match : "xxxxx)))"
    } ]

    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

    0 comments  ·  Ops Manager  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base