Skip to content

Ops Tools

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

481 results found

  1. Currently the OM App server has the secrets to connect to S3. This is a security issue for many organizations.Can a secure vault be used t

    Currently the OM App server has the secrets to connect to S3. This is a security issue for many organizations.Can a secure vault be used to store the secret?

    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  ·  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)
  2. Opsmanager API: Include Backup Id in List Restore Jobs Response that restore was triggered for

    Hello,

    there is already a snapshot id included in the list restore jobs response, BUT the problem arises with sharded instances: If you restore a sharded instance to a specific backup, multiple restore jobs are created (one for config server, one for each shard). Thus, the snapshot id in the list restore jobs response refers to the backup of the single component (either config server or shard) and not to the overall backup of the entire sharded instance the restore was initiated for.

    Hence, you cannot map those restore jobs to the backup the restore was triggered for, which makes…

    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)
  3. 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)
  4. Allow OPS Manager to export as CSV or JSON All projects page information

    All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.

    Add export as CSV or JSON All projects page information.

    Current MongoDB Usage report doesn't fit due:
    1. It doesn't report backup, encryption information
    2. Cluster name could be not right if the cluster was unmanaged and added back to OPS manager as managed. (Cluster_0 bogus names)

    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)
  5. Allow to select columns visible on OPS Manager All projects page

    All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.

    We need ability to select only few columns visible on this page.
    Example:
    cluster name, data size

    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  ·  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. All projects page in MongoOPS should show if encryption at rest is enabled

    All projects page in MongoOPS shows cluster name, data size, version, nodes, backup, SSL, Auth, Alerts.

    We need to see if encryption-at-rest is enabled.

    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  ·  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)
  7. The Backup Daemon auto downloads all old Mongodb versions

    If "Backup Versions Auto Download" is set to true on the Admin > General > Ops Manager Config > MISCELLANEOUS tab, then the backup daemon automatically downloads all older major versions of the software.
    In my opinion, it would be better if you could either select the version/s which you want or it only downloaded versions equal to or higher than your current version.
    All the old versions take up disk space and can only be deleted if the setting is changed to false.
    thanks

    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. Publish Ops Manager deployments to Slack

    It would be nice if the Slack integration could be used to post deployment notices to a Slack channel.

    We have a channel where our other tooling posts about changes that have been made, and there isn't an easy way to have Ops Manager do the same.

    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  ·  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)
  9. Mongo Atlas: create backup before updating version

    If I upgrade Atlas cluster, Atlas automatically creates a backup with the new version.
    I'd rather have a backup of the cluster with original version.
    It will allow to restore to the previous version.
    Current workaround: create a backup manually before upgrade.

    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)
  10. Add a possibility to download all snapshots for deployment/project/organisation

    Currently, it is not possible to move between S3 buckets without to terminate the job. It would be great to have possibility to download all the snapshots before to delete backup job.

    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  ·  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)
  11. encryption at rest

    Right now there is only option to encrypt the key used to encrypt the database. There is no way we can choose which encryption technology is being used to encrypting the database and its backups. The default protocol being used by mongodb may not align with the security policy of the company.

    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. 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)
  13. Alert for even number of voting members of a Replica Set

    Alert for even number of voting members of a Replica Set

    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  ·  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)
  14. mongosync filtered sync update

    Currently we cannot modify a filter that is in use without wiping all user data in the target cluster.
    For exclusion filters, where we exclude collections NOT to copy, adding more collections to exclude should not require wiping all user data.
    This is very cumbersome otherwise.

    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)
  15. Show better diff for changes to setParameter json blob

    The "review and deploy" step only shows that there IS a diff in the setParameter json, but it does not make it clear what is actually changing.

    It would be very helpful to show the diff between the two json payloads in an easy-to-read way.

    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  ·  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)
  16. Authentication mode MONGODB-OIDC

    Support for authentication: MONGODB-OIDC

    security:
    authentication:
    enabled: true
    modes:
    - "MONGODB-OIDC"

    currently we get the following error wir kuberntes operator 1.26.0, OpsManager 7.0.7 and RS 7.0.11:
    Unsupported value: "MONGODB-OIDC"

    13 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)
  17. mongoimport should explain why documents fail schema validation

    Currently, with mongoimport 100.9 and MongoDB 7.0 with schema validation enabled, mongoimport will only report that a document failed to import due to schema validation. It would be useful if it could explain why it violates the schema (e.g. which fields are missing, which datatypes are incorrect, etc.). This is similar to the feature request for MongoDB Compass2

    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)
  18. Add specific label to Arbiter deployment to distinguish it label-wise

    As per https://github.com/mongodb/mongodb-kubernetes-operator/issues/1442 we would like to request to either and/or:

    a) have the operator add a new label to replica and arbiter statefulset deployments to distinguish them from each other
    b) have the ability to add your own labels to specifically the replica OR the arbiter statefulset deployments

    Having the ability to easily filter arbiter statefulsets from non-arbiter statefulsets would be great. This is useful for example for backup tools that run commands on pods based on a combination of labels, to exclude any arbiters from backup.

    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)
  19. Operator crashes when it doesn't have permissions to watch a namespace

    If one of many namespaces does not set the permissions for the operator to watch the namespace, it throws exceptions and goes to crashLoopBackOff state.
    This is clearly a bug. One misconfigured namespace should never be able to take the operator down with it.

    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)

    This is expected behavior and common among operators; it can't function and do what's needed if it lacks the permissions needed.


    I know we have an open support case around this to try and understand more about your use case, and we're hoping that we'll be able to offer some guidance to avoid this problem and still achieve what you need. It may even be a new use case that we look to support.

  20. Identify the snapshot of each project and its size in S3 blockstore

    Calculating the storage size consumed by snapshots for each projects deployments for the storage size consumed individually in S3 Blockstore. However, on the S3 snapshot store the data will be stored in the below format which doesn't include any project id to identify the specific project.
    s3://bucket_name/0E3AA1971D5CF1CA52F9AF22A4228F10293AE9804D43FBF7EB5DDE38DB06B74A/5b27b0e4083826088f259f28_A s3://bucket_name/1860B12165FB7ED336DDAB9D306EF38E18FCBD36BF695904C497B825F83581DC/5b27b0e4083826088f259f28_A

    This feature is helpful for the customers to understand and segregate the storage consumption by each deployments

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